And, I've been able to add a Recover entry to lilo.cfg, run lilo, and have the entry appear in the LILO menu at boot time.

I've been able to copy grldr to root of sda1. My assumption is that it must write the block address of the PBR therefore the PBR must contain some boot code, which in my case I would like to be Grub4dos. But what I have not been able to find anywhere, is a description of what lilo writes into the map, for each of the 'other=' entries. Then the block address of the map is written to LILO in the MBR (is this close to accurate ?). The understanding of LILO that I've been able to accumulate so far, is that running lilo against lilo.cfg, builds the map, which is stored in /boot of whichever Linux partition is currently active, and which contains the block addresses of the kernel for each of the 'image=' entries of lilo.cfg. All of this is working in the Windows machines. And, as a local repository to store Clonezilla images of the Linux partitions, before the images get copied to NAS. So, I'm confident it can be done.Īnd as I'm sure someone will ask 'Why?,' it is because I wish to use the Recover partition (with Grub4dos) to boot various live CD's, such as Clonezilla, GParted, etc. On another machine (all Windows), I've installed Grub4dos both to MBR of USB stick, and to PBR of HDD partition, using RMPrepUSB, a Windows tool, without issue. What I want to do is, install Grub4dos to the sda1 partition boot record, using only Linux tools (no Windows), and then boot it from LILO.

LILO is installed in the MBR, and it boots both Salix partitions without issue.

File Grldr Mbr Org