LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Jan Engelhardt <jengelh@computergmbh.de>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Mikael Pettersson <mikpe@it.uu.se>,
	Andi Kleen <andi@firstfloor.org>,
	Pavel Emelyanov <xemul@openvz.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Al Viro <viro@zeniv.linux.org.uk>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Alexey Dobriyan <adobriyan@openvz.org>
Subject: Re: [PATCH] Make sysctl a separate filesystem
Date: Fri, 15 Feb 2008 18:18:15 +0100 (CET)	[thread overview]
Message-ID: <Pine.LNX.4.64.0802151813480.30301@fbirervta.pbzchgretzou.qr> (raw)
In-Reply-To: <20080215083428.07246720.randy.dunlap@oracle.com>


On Feb 15 2008 08:34, Randy Dunlap wrote:
>> >
>> >Doing it automatically is the only acceptable way, IMO.
>> 
>> For time being only.
>> 
>> The kernel (currently) only auto-mounts invisible filesystems.
>
>like /root, sysfs, futexfs, pipefs, anon_inodefs, bdev, devpts,
>hugetlbfs, inotifyfs ?

Yes?

/ (double case - initramfs or kernel), sysfs, devpts and
hugetlbfs can be mounted using mount(8) (or mount(2)), so
userspace can - and distro scripts do just that - mount them.

futexfs, pipefs, anon_inodefs, bdev and inotifyfs are 'invisible'
filesystems in that you cannot mount them yourself and that you
do not usually get to see them except probably when readlink(2)ing
on /proc/X/fd/N.

  reply	other threads:[~2008-02-15 17:18 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-15 10:39 [PATCH] Make sysctl a separate filesystem Pavel Emelyanov
2008-02-15 10:47 ` Andi Kleen
2008-02-15 11:35   ` Mikael Pettersson
2008-02-15 12:44     ` Jan Engelhardt
2008-02-15 16:34       ` Randy Dunlap
2008-02-15 17:18         ` Jan Engelhardt [this message]
2008-02-15 16:57       ` Oliver Pinter
2008-02-15 18:27         ` Jan Engelhardt
2008-02-22  1:25     ` Al Viro
2008-02-22  9:40       ` Andi Kleen
2008-02-22  9:52       ` Mikael Pettersson
2008-02-19 14:24 ` Stephen Smalley

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.4.64.0802151813480.30301@fbirervta.pbzchgretzou.qr \
    --to=jengelh@computergmbh.de \
    --cc=adobriyan@openvz.org \
    --cc=akpm@linux-foundation.org \
    --cc=andi@firstfloor.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikpe@it.uu.se \
    --cc=randy.dunlap@oracle.com \
    --cc=viro@zeniv.linux.org.uk \
    --cc=xemul@openvz.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).