Re: Whats in the wings for 2.5 (when it opens)
Crutcher Dunnavant (firstname.lastname@example.org)
Sat, 22 Sep 2001 10:31:00 -0400
++ 22/09/01 12:59 +1000 - Keith Owens:
> On Fri, 21 Sep 2001 15:58:06 -0400,
> Crutcher Dunnavant <email@example.com> wrote:
> >A cleaner handling of module parameters/cmd line options.
> That comes out as a side effect of kernel build 2.5, every object gets
> -DKBUILD_OBJECT to define the name it is known by. From
> -DKBUILD_OBJECT=module, the name of the module the object is
> linked into, without the trailing '.o' and without any paths.
> If the object is a free standing module or is linked into
> vmlinux then the "module" name is the object itself.
> Automatically generated.
> Post kbuild 2.5 I will be writing a generic parameter/command line
> interface so you can insmod foo bar=99 or boot with foo.bar=99. You
> will even be able to boot with foo.bar=99 when foo is a module, insmod
> will use the command line as a default set of values.
Well, that certainly is clean. How deep does it go? For instance, can
we you define it as:
foo.bar.baz.bat.quux=99 -> mod 'foo.bar.baz.bat', parm 'quux'
so we get naming schemes like:
This would help much with keeping some of the namespaces cleaner. Do you
want any help with this?
GCS d--- s+:>+:- a-- C++++$ UL++++$ L+++$>++++ !E PS+++ PE Y+ PGP+>++++
R-(+++) !tv(+++) b+(++++) G+ e>++++ h+>++ r* y+>*$
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to firstname.lastname@example.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/