Oliver Fromme wrote: > Actually, I was thinking about that myself. But the problem > is that the code is very closely integrated into the existing > syscons code (with a lot of #ifdef's, of course). 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. - Donn To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
- Re: syscons extension: "propellers" Jordan K. Hubbard
- Re: syscons extension: "propellers" Oliver Fromme
- Re: syscons extension: "propellers" Luigi Rizzo
- Re: syscons extension: "propellers" Jordan K. Hubbard
- Re: syscons extension: "propellers" Donn Miller
- Re: syscons extension: "propellers&q... Thomas David Rivers
- Re: syscons extension: "propellers" Sheldon Hearn
- Re: syscons extension: "propellers" Sheldon Hearn
- Re: syscons extension: "propellers&q... Nik Clayton
- Re: syscons extension: "propelle... Sheldon Hearn
- Re: syscons extension: "propellers" Donn Miller
- Re: syscons extension: "propellers" Andrzej Bialecki
- Re: syscons extension: "propellers" Nik Clayton
- Re: syscons extension: "propellers" Oliver Fromme
- Re: syscons extension: "propellers" Jordan K. Hubbard
- Re: syscons extension: "propellers" Kazutaka YOKOTA
- Re: syscons extension: "propellers" Sheldon Hearn
- Re: syscons extension: "propellers" Oliver Fromme
- Re: syscons extension: "propellers" jack
- Re: syscons extension: "propellers" Warner Losh
- Re: syscons extension: "propellers" Oliver Fromme