From: Rick Hohensee <humbubba@smarty.smart.net>
To: linux-kernel@vger.kernel.org
Subject: Re: LANANA: Getting out of hand?
Date: Tue, 15 May 2001 12:26:21 -0400 (EDT) [thread overview]
Message-ID: <200105151626.MAA16354@smarty.smart.net> (raw)
Torvalds sez
>On Mon, 14 May 2001, Alan Cox wrote:
>>
>> Except that Linus wont hand out major numbers, which means I can't even boot
>> simply off such a device. I bet the vendors in question dont think the sun
>> shines out of linus backside any more.
>
>Actually, it does. It's just that some people have gotten so blinded by my
>a** that they can no longer see it any more ;)
>
>The problem I have is that there are lots of _good_ solutions, but they
>all imply a bit more work than the bad ones.
>
>What does that result in? Everybody continues to use the simple old setup,
>which required no thought at all, but that is a pain to maintain.
>
>For example, the only thing you need in order to boot is to have a nice
>clean "disk" major number. That's it. Nothing fancy, nothing more.
To what extent do the code of the various drivers reflect that? i.e. is there
some code that is common to all block devices, and that is used by code that
is common to all disk devices, that further is used by all drivers pretending
to be IDE devices, which is further used by all code pretending to be EIDE
devices, etc. ? If you look at majors, say, as a binary tree which you
walk in accordance with the bits in the major, can drivers nest like that?
I've wondered about that for a long time for various reasons.
Rick Hohensee
www.clienux.com
next reply other threads:[~2001-05-15 16:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-15 16:26 Rick Hohensee [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-05-14 22:30 LANANA: To Pending Device Number Registrants Alan Cox
2001-05-15 4:12 ` LANANA: Getting out of hand? God
2001-05-15 4:30 ` Linus Torvalds
2001-05-15 5:17 ` Linus Torvalds
2001-05-15 8:24 ` Geert Uytterhoeven
2001-05-15 8:48 ` Alan Cox
2001-05-15 21:16 ` Martin Dalecki
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=200105151626.MAA16354@smarty.smart.net \
--to=humbubba@smarty.smart.net \
--cc=linux-kernel@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).