Apparently, GRUB's network capabilities are only designed to be
loaded as an etherboot/PXE image itself. There is currently no
possibility (at least, none that I could derive) to install GRUB on a
host, obtain a DHCP config and TFTP-boot a remotely served kernel
that attaches its
GRUB severely misses the ability to boot from *ANY* available data
media that the host's firmware is aware of. The restrictions
regarding optical media being required to be booted from to have the
(cd) device is ridiculous.
___
Bug-grub
There is no possibility to install GRUB and its base directories onto
a small (say, 10--20MB) filesystem and use this as a CRAMFS- or
SqueezeFS boot image in a dedicated partition (alike to the /boot
partition of many Linux distros) or as a flashed boot image in CMOS/
NVRAM.
On 04.09.2011 20:38, René Kuligowski wrote:
There is no possibility to install GRUB and its base directories onto
a small (say, 10--20MB) filesystem and use this as a CRAMFS- or
SqueezeFS boot image in a dedicated partition (alike to the /boot
partition of many Linux distros) or as a flashed
On 04.09.2011 20:42, René Kuligowski wrote:
GRUB severely misses the ability to boot from *ANY* available data
media that the host's firmware is aware of. The restrictions
regarding optical media being required to be booted from to have the
(cd) device is ridiculous.
Please, look around
On 04.09.2011 20:33, René Kuligowski wrote:
Apparently, GRUB's network capabilities are only designed to be loaded
as an etherboot/PXE image itself. There is currently no possibility
(at least, none that I could derive) to install GRUB on a host, obtain
a DHCP config and TFTP-boot a
