From: Rob Landley <landley@trommello.org>
To: Oliver Neukum <Oliver.Neukum@lrz.uni-muenchen.de>,
Patrick Mochel <mochel@osdl.org>, Adam Belay <ambx1@netscape.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] integrate driverfs and devfs (2.5.28)
Date: Mon, 5 Aug 2002 02:26:35 -0400 [thread overview]
Message-ID: <200208051225.g75CP4v316564@pimout4-ext.prodigy.net> (raw)
In-Reply-To: <200207292326.g6TNQcI19062@fachschaft.cup.uni-muenchen.de>
On Monday 29 July 2002 07:25 pm, Oliver Neukum wrote:
> Am Dienstag, 30. Juli 2002 00:21 schrieb Patrick Mochel:
> > 1) devfs imposes a default naming policy. That is bad, wrong and unjust.
> > There shalt not be a default naming policy in the kernel. Period.
>
> Why not? Who really needs the ability to name anything in /dev ?
> You can always use a symlink if you realy, realy want.
Okay, I'll bite.
So what's root_dev_names in init/do_mounts.c? If a default naming policy is
so unacceptably evil, is that being removed in 2.5 and everybody being told
to use major/minor for the root device?
By the way, why doesn't imposing consistent predefined major/minor numbers
(0x0301 instead of "hda1") count as "policy"? I'm honestly curious...
Rob
next prev parent reply other threads:[~2002-08-05 12:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-28 21:03 Adam Belay
2002-07-29 13:47 ` Adam Belay
2002-07-29 19:33 ` Patrick Mochel
2002-07-29 16:47 ` Adam Belay
2002-07-29 22:21 ` Patrick Mochel
2002-07-29 23:25 ` Oliver Neukum
2002-07-30 16:32 ` Patrick Mochel
2002-07-30 14:02 ` Adam Belay
2002-08-05 6:26 ` Rob Landley [this message]
2002-08-05 23:19 ` Greg KH
2002-08-05 23:51 ` Policy vs API (was Re: [PATCH] integrate driverfs and devfs (2.5.28)) Rob Landley
2002-08-06 16:34 ` Greg KH
2002-08-06 17:43 ` Patrick Mochel
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=200208051225.g75CP4v316564@pimout4-ext.prodigy.net \
--to=landley@trommello.org \
--cc=Oliver.Neukum@lrz.uni-muenchen.de \
--cc=ambx1@netscape.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@osdl.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
all inboxes | Powered by JetHome®