From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Pierre Ossman <drzeus-list@drzeus.cx>
Cc: Russell King <rmk+lkml@arm.linux.org.uk>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: MMC block major dev
Date: Wed, 01 Sep 2004 13:16:30 +0100 [thread overview]
Message-ID: <1094040990.2399.56.camel@localhost.localdomain> (raw)
In-Reply-To: <4134D5EF.9080903@drzeus.cx>
On Maw, 2004-08-31 at 20:47, Pierre Ossman wrote:
> >Registering with the block layer with a major number of zero means
> >"find me a free major number and assign that to me." This is nothing
> >new. If devfs can't cope with that, devfs is buggy. Use udev instead.
Registering with an ID of 0 is bad because you've no idea what existing
device node you may reallocate and thus what permissions may be present
for access unless you sweep all of storage.
> Ok. Please excuse my ignorance =)
> My point was that I do not use a dynamic system for /dev so it would be
> nice to have a static major number. Since MMC now is a part of Linus'
> kernel maybe it's time for a permanent allocation?
Agreed. It also needs reigstering with LANANA to avoid /dev namespace
collisions irrespective of the device numbering and to ensure the
namespace is common across all vendors regardless of their dev
management tools. Without LANANA we'll get
#if UDEV_REDHAT
#elif UDEV_SUSE
#elif DEVFS_SUSE
#elif GENTOO
#endif
type stuff in programs .. 8(
Send the proposed /dev naming for the device and details in the same
format as Documentation/devices.txt to device@lanana.org, and Torben
will either disagree with you or assign name and possibly numbers.
Alan
next prev parent reply other threads:[~2004-09-01 13:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-31 19:13 MMC block major dev Pierre Ossman
2004-08-31 19:15 ` Russell King
2004-08-31 19:47 ` Pierre Ossman
2004-09-01 12:16 ` Alan Cox [this message]
2004-09-01 21:55 ` Russell King
2004-09-01 21:28 ` Alan Cox
2004-09-01 12:18 ` Alan Cox
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=1094040990.2399.56.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=drzeus-list@drzeus.cx \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk+lkml@arm.linux.org.uk \
/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.