Stephan Assmus <superstippi@xxxxxx> wrote: > > scott mc wrote: > > The trick here is that I boot from the hard drive as the master and > > the > > CF card is on the slave port. I need to make the CF card bootable > > and > > then on restart I want to move it to master and remove the > > harddrive. So > > if I am booting from the hard drive will I still be able to run > > makebootable on the CF card? And if I can is there a way to tell > > it > > which drive it's supposed to be or will it just know? I'll be > > trying this > > out in a few hours here. > > Yes, it should work fine. I think what happens when you run > makebootable is > that the bootsector of the partition gets the executable code for the > BIOS > (which loads zbeos) and the partition offset of the partition is > written to > a magic offset. So it should not depend on how the harddrive is > attached. It would be nice if one could target 'bootman' at -any- drive, like in Scott's case, his CF card @ primary slave. I've wanted that sometimes. +1 for renaming bootman to BootMenu. It should, IMO, live with the other preferences, have a proper icon and /bin/bootman symlinked to it, for legacy support. BTW, one might be able to have it recognize GRUB and allow editing its settings, as an alternative to replacing it. If the settings format is stable enough, bootman could show a GRUB config panel, with sanity checks. Perhaps the GRUB version can be figured out somehow. If not, BootMenu could still allow manual editing of GRUB's menu.lst file as plain text, if the (Linux-) filesystem where it lives is writable. (Or the tweaked file is equal length or shorter than the original. :)) /Jonas.