From: Olaf Hering <olh@suse.de>
To: linux-hotplug@vger.kernel.org
Subject: Re: blessed location of device nodes
Date: Mon, 01 Dec 2003 21:08:50 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-107033874117862@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-107034877724660@msgid-missing>
On Mon, Dec 01, Greg KH wrote:
> On Mon, Dec 01, 2003 at 09:51:21PM +0100, Olaf Hering wrote:
> >
> > /udev is not an official place according to FHS. Did you ever try to
> > get this into the 'standard'?
> > Or can the location be moved from /udev/ to /dev/udev/ or whatever?
>
> How about /dev :)
> That's where it will eventually move to, once we have everything in the
> early boot process working properly. I'm just using /udev now so that
> people can test, and develop, and still have a working system...
>
> > Can you make a decision?
>
> Sure, /dev it is. Ok with you?
Sure, the point is that its not only a matter of udev. The userland has
to find the nodes. Imagine if the major:minor which is usually known as
/dev/null would have different names across the vendors. Maybe we will
have a *.config that works for everyone, one day.
--
USB is for mice, FireWire is for men!
sUse lINUX ag, n√úRNBERG
-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive? Does it
help you create better code? SHARE THE LOVE, and help us help
YOU! Click Here: http://sourceforge.net/donate/
_______________________________________________
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-01 21:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-01 20:51 blessed location of device nodes Olaf Hering
2003-12-01 21:00 ` Greg KH
2003-12-01 21:08 ` Olaf Hering [this message]
2003-12-02 9:03 ` Marco d'Itri
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-107033874117862@msgid-missing \
--to=olh@suse.de \
--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 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.