Andrzej Bialecki wrote in list.freebsd-current:
> On Tue, 14 Dec 1999, Donn Miller wrote:
> > I think another way (instead of ifdefs) would be to provide some
> > hooks into syscons, so that the "propellers" code can be loaded
> > or unloaded via kldload/unload.
I'm not yet 100% convinced that it would make sense to separate
the propellers code into a module. Is 5 Kbyte of kernel code
really that much of a problem? Please note that
1. without the kernel option SC_PROPELLERS, none of the code
gets compiled into the kernel. So someone who doesn't
need the propellers and doesn't want the 5 Kbyte "bloat"
simply doesn't include that option in his kernel.
2. the option should probably not be in GENERIC.
3. once you have the code in your kernel, you can arbitrarily
enable and disable (hide) the propellers. When they're
disabled, you get the full screen resolution back (25 rows
or whatever). You can even enable them on some VTYs and
disable them on others, if you want.
So the only drawback is 5 Kbyte of kernel growth, once someone
has included the option SC_PROPELLERS. Does this justify a
rewrite of syscons to divide it into KLDs? Frankly, I don't
think so.
> Another way to customize various strings, colors and variables could be
> via sysctl. It's easy e.g. to set up the "propeller" string via sysctl.
Currently it uses ioctls, which is more appropriate for these
things, IMO.
Regards
Oliver
--
Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany
(Info: finger userinfo:[EMAIL PROTECTED])
"In jedem Stück Kohle wartet ein Diamant auf seine Geburt"
(Terry Pratchett)
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
