Subject: Re: Call for review: The New Block/Character Device Switch Configuration Framework
From: Ignatios Souvatzis <email@example.com>
Date: 06/28/2001 14:40:02
Content-Type: text/plain; charset=us-ascii
On Thu, Jun 28, 2001 at 07:22:38PM +0700, Robert Elz wrote:
> Date: Thu, 28 Jun 2001 12:50:09 +0200
> From: Ignatios Souvatzis <firstname.lastname@example.org>
> Message-ID: <20010628125009.A28656@theory.cs.uni-bonn.de>
> | Well, but as long as the userland problem isn't solved, you can't use=
> | changed kernel at all...
> I think that you and mjacob were both missing ...
> 4.2. Userland - config(8)
> 4.2.1. Grammer
> device-switch <name> chr <num> [blk <num>] [<options>]
> name - The prefix of bdevsw/cdevsw entry (required)
> chr - A character major number (required)
> blk - A block major number (optional)
> options - Conditions to determine whether should be attached or not
> That is, the major device numbers are still being wired into the
> kernel, they're not being dynamically allocated - just now that info
> is coming from the config machinery, rather that someone hand editing
> the conf.c file and corectly positioning the list of functions in the
> [cb]devsw tables.
> Really, if Matt Thomas looks at this and says "real cool" or something,
> it really can't be a totally broken design, can it?
I didn't want to say "broken", just "we need to specify/implement the other
But as you write, I hadn't looked close enough. Ok, then.
-----BEGIN PGP SIGNATURE-----
-----END PGP SIGNATURE-----