From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev /sys
Date: Wed, 10 Dec 2003 21:12:15 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-107109104406766@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-107106464202164@msgid-missing>
On Wed, Dec 10, 2003 at 10:03:53PM +0100, dd@daemond.com wrote:
> > So in short, just mount sysfs at /sys and everyone will be happy :)
>
> everyone expect me :-)
>
> I was talking about Filesystem Hierarchy standard, as described in
> http://www.pathname.com/fhs/
No, please read that document. It doesn't even require /proc :)
So we are free to create /sys without invalidating the document.
> I thought that sysfs and procfs are both for the same thing (you can see
> inside the kernel by using programs or even shell scripts), so I just
> thought sysfs could be a part of procfs, or procfs could offer for example
> /proc/sysfs directory which is empty everytime and allows users like me (who
> don't like /sys) to mount sysfs there :-)
No, they are not the same. That is why they are different, and mounted
in different places.
> Maybe you are asking _why?_, but I am asking _why not?_ :-)
Because they have nothing to do with each other. Yeah, they both show
kernel information, but different information. Eventually almost
everything that does not deal with proccess will move to sysfs, as
procfs is not the place for them.
thanks,
greg k-h
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id\x1278&alloc_id371&op=click
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2003-12-10 21:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-10 13:56 udev /sys dd
2003-12-10 20:22 ` Greg KH
2003-12-10 21:08 ` dd
2003-12-10 21:12 ` Greg KH [this message]
2003-12-10 21:56 ` dd
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=marc-linux-hotplug-107109104406766@msgid-missing \
--to=greg@kroah.com \
--cc=linux-hotplug@vger.kernel.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).