|
From: <ke...@et...> - 2003-08-01 09:36:03
|
>Well, since grub is a full replacement for etherboot menus for me now, >which disappeared from 5.1, I thought, it would be interesting for In 5.1 and above menus are devolved to a loadable image which uses the redirection capability of Etherboot to specify which image to load. I didn't feel that menus should be part of the core functionality of Etherboot, mainly because of the issue of updating ROMs, which is slower than updating disk images. Have a look at mkelf-nfl, which doesn't take the entries from the DHCP packet and has no limitations on menu entries due to packet size. While I have no philosophical objections to Etherboot code being used in GRUB, and certainly no objections on licence grounds---it's GPL after all---I do not want Etherboot to evolve towards becoming a disk bootloader and certainly not splash screens and all that. We have enough work as it is trying to keep up with ideas in network booting. If however these capabilities can be provided by a general mechanism, or Etherboot can be invoked as a subsystem to do network booting, then I'll listen to the proposal. In short, like the kernel developers, I like to push bells and whistles into user space; and I prefer interoperability to feature bloat. >For the record: when I started experimenting with diskless linux setups >back in 1997 [fiddling with netboot and packet drivers], I couldn't >imagine, how far this could go. The progress made since then is >absolutely impressive (especially from the etherboot point of view). > >I looks to me, that the future of netbooting gets brighter and brighter. > >Thanks to all contributors, And thanks for your kind words. |
