>> 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
>
>I certainly wouldn't argue this based on size, no. To understand the
>point I was arguing, consider what would have been the case if the
>very first screen saver had been hacked straight into syscons rather
>than making it an optional component. We'd probably have 2 or 3
[...]
>So I see it with "propellers" - they're an optional feature component
>and there should be a way of bolting such optional features into
>syscons without having to recompile the kernel. It's not a question
>of size, it's a question of design and flexibility and I can argue
>from such a purist's perspective because I'm not doing any of the work
>involved and it's thus really easy to do so. :-)
I am looking at Oliver Fromme's code. It is interesting.
I am currently preparing the final stage of syscons clean-up (which
was outlined a year ago), and will think about reasonably generalized
way of adding extentions to syscons.
Kazu
PS: As for screen savers, there have been a plan to move screen savers
out of the kernel to userland. A part of the necessary infrastructure
is there, but it's not fininished...
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
