Re: Move BSD and multiboot boot helper out of the kernel to their respective modules

[phcoder]

I agree. Such workarounds take boot time and create situations when 
first action of kernel is to undo last action of booter.
Sometimes it can't be avoided but if we can we should try. Also it adds 
some flexibility since last action of booter is
performed in nice unix-like environment and kernel starts in "tabula 
rasa". An example is my system with widescreen. To init
widescreen special commands specific to my framebuffer controller are 
necessary. So if grub2 sets it kernel can start in
undistorted video mode.

Thanks
Vladimir 'phcoder' Serbinenko


> Or perhaps we could avoid grub_dl_unload_all_modules altogether.  For example,
> gfxterm might think that graphical mode needs to be disabled when it's
> unloaded, but the OS loader knows better.  You could want to tell your OS
> about the framebuffer state so it can be used by it without glitches.
>
> The same would apply, for example, to stopping the floppy drive.  Instead
> of waiting for the drive to tell us it has stopped, we could tell the OS
> it's still spinning if our loader knows how to do that (and the OS knows
> how to receive this information).