--vbzKE9fGfpHIBC6T
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Sat, Jun 17, 2006 at 04:54:59PM +0200, Pavel Cahyna wrote:
> On Sat, Jun 17, 2006 at 10:52:06AM +0200, Quentin Garnier wrote:
> > The kernel options description files could have stuff like this:
> >=20
> >     modular defattr foo
> >=20
> >     modular device bar
> >=20
> >     device baz
> >     modular attach baz at fol with baz_fol
> >=20
> > which would mark repectively the attributes foo, bar and baz_fol as
> > potentially modular.  Then the user would have e.g.:
> >=20
> >     module baz* at fol?
> >=20
> > which would have the module baz_fol.o created.
>=20
> In this example, "baz" itself is not modular? It has to be compiled
> statically?
>=20
> If you had instead "modular device baz", you should be able to create
> modules baz.o and baz_fol.o, right?

Yes.  The example was meant to underline the granularity.  The side
effect of that is that it produces a lot of modules.  However, each of
them is in turn very specific.

Dependency between modules would be at the attribute level too, of
course.

--=20
Quentin Garnier - cube@cubidou.net - cube@NetBSD.org
"When I find the controls, I'll go where I like, I'll know where I want
to be, but maybe for now I'll stay right here on a silent sea."
KT Tunstall, Silent Sea, Eye to the Telescope, 2004.

--vbzKE9fGfpHIBC6T
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (NetBSD)

iQEVAwUBRJQffdgoQloHrPnoAQKkkAgAwGr0RDIKoN49zrtCm6thOUa9GtRQN0/7
jz9fcrEfVGUu/awFOUQIV0/rjgPzcFTnAwyUCEFnJrioAnPHr+8sAsOuu2xNiUok
6A/cz2gdyOsQ7RHI5PHJHmxfjqw7LzHcAiVuLWp8TyXVawSxlG32LeYNgr+Rl6hb
y1Me3mLeFEUxj4IuIf35ABjJJBtQpG1mTBYaGoI1DEQxoYI53H/ERAgvvut9g4eF
WaQwpYW9adfHCIEIBpK1uKbCMy/hw4oU7vAGOVoZvVl9mZPjrdccAujdu75NV8Vj
fXG8mLFOFZeLTMNBpZDpijCQKg39VnbDPflGOLizLKhDilF3yp/06w==
=pbwp
-----END PGP SIGNATURE-----

--vbzKE9fGfpHIBC6T--