From: Greg KH <greg@kroah.com>
To: Witukind <witukind@nsbm.kicks-ass.org>
Cc: "J.A. Magallon" <jamagallon@able.es>,
linux-kernel@vger.kernel.org,
linux-hotplug-devel@lists.sourceforge.net
Subject: Re: udev - please help me to understand
Date: Sat, 03 Jan 2004 21:56:46 +0000 [thread overview]
Message-ID: <20040103215646.GE11061@kroah.com> (raw)
In-Reply-To: <20040103135433.09eb97b7.witukind@nsbm.kicks-ass.org>
On Sat, Jan 03, 2004 at 01:54:33PM +0100, Witukind wrote:
> On Sat, 3 Jan 2004 02:00:10 +0100
> "J.A. Magallon" <jamagallon@able.es> wrote:
> > IE, I want a working and race free devfs, and this is udev.
>
> Well udev != devfs. I think it's two different ways to solve a same problem.
> What I wonder now is why do we need both /proc and sysfs?
procfs is for process information.
sysfs is for system information. Slowly, over time, things that are
currently in procfs will be moving to sysfs.
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
WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <greg@kroah.com>
To: Witukind <witukind@nsbm.kicks-ass.org>
Cc: "J.A. Magallon" <jamagallon@able.es>,
linux-kernel@vger.kernel.org,
linux-hotplug-devel@lists.sourceforge.net
Subject: Re: udev - please help me to understand
Date: Sat, 3 Jan 2004 13:56:46 -0800 [thread overview]
Message-ID: <20040103215646.GE11061@kroah.com> (raw)
In-Reply-To: <20040103135433.09eb97b7.witukind@nsbm.kicks-ass.org>
On Sat, Jan 03, 2004 at 01:54:33PM +0100, Witukind wrote:
> On Sat, 3 Jan 2004 02:00:10 +0100
> "J.A. Magallon" <jamagallon@able.es> wrote:
> > IE, I want a working and race free devfs, and this is udev.
>
> Well udev != devfs. I think it's two different ways to solve a same problem.
> What I wonder now is why do we need both /proc and sysfs?
procfs is for process information.
sysfs is for system information. Slowly, over time, things that are
currently in procfs will be moving to sysfs.
thanks,
greg k-h
next prev parent reply other threads:[~2004-01-03 21:56 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-02 11:48 udev - please help me to understand Steve Youngs
2004-01-02 11:48 ` Steve Youngs
2004-01-02 13:00 ` Michael Buesch
2004-01-02 13:00 ` Michael Buesch
2004-01-03 3:52 ` Steve Youngs
2004-01-03 3:52 ` Steve Youngs
[not found] ` <20040102123636.GA29909@mark.mielke.cc>
2004-01-02 20:21 ` Greg KH
2004-01-02 20:21 ` Greg KH
2004-01-02 20:39 ` T'aZ
2004-01-02 20:39 ` T'aZ
2004-01-03 3:56 ` Steve Youngs
2004-01-03 3:56 ` Steve Youngs
2004-01-02 20:23 ` Greg KH
2004-01-02 20:23 ` Greg KH
2004-01-03 1:00 ` J.A. Magallon
2004-01-03 1:00 ` J.A. Magallon
2004-01-03 12:54 ` Witukind
2004-01-03 12:54 ` Witukind
2004-01-03 21:56 ` Greg KH [this message]
2004-01-03 21:56 ` Greg KH
2004-01-04 16:02 ` Kevin P. Fleming
2004-01-04 16:02 ` Kevin P. Fleming
2004-01-03 3:28 ` Steve Youngs
2004-01-03 3:28 ` Steve Youngs
2004-03-29 15:39 ` T'aZ
2004-03-29 15:39 ` J.A. Magallon
2004-03-29 15:39 ` Steve Youngs
2004-03-29 15:39 ` Steve Youngs
2004-03-29 15:39 ` Steve Youngs
2004-03-29 15:40 ` Witukind
2004-03-29 15:40 ` Greg KH
2004-03-29 15:42 ` Kevin P. Fleming
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=20040103215646.GE11061@kroah.com \
--to=greg@kroah.com \
--cc=jamagallon@able.es \
--cc=linux-hotplug-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=witukind@nsbm.kicks-ass.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.