I've recently started using grub (it's been "on the list" for a long time and it was the fact that SuSE 8.1 uses it by default that got it off the list) and I must admit to being very impressed. It reminds me of OpenBoot (a Forth based ROM boot monitor program used on Sun and recent Apple hardware) in its abilities to control the boot process, and makes me wish that one could get a PC BIOS with the controllability of OpenBoot.
But (isn't there always a but ?) I've found a buglet. Nothing huge, and workable around, but here it is anyway. I made a mistake in my initial menu.lst (which is easy to do because, frustratingly, uses a syntax for disk partitions which is quite different from linux and is zero based where the linux model is one based - hda1 => hd(0,0)). One of the benefits of grub is of course that such an error doesn't require reaching for the boot floppy but simply editing the command lines and this is where the buglet lives. When I press 'e' to edit a command line I get the grub prompt and the command line like: grub> Grub command line goes here - editable via readline but readline isn't working right - the command line isn't correctly displayed, and edits aren't correctly reflected. It's an easy buglet to work around - press ^U to erase the command line, press Enter to get a new command line, press Esc to get back to the menu, and then 'e' to again edit the command line and now editing works, and it's all done in quarter of the time it took to read this, but nonetheless it's a little messy. I'm using grub 0.92. Kindest regards, Niall O Broin _______________________________________________ Bug-grub mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-grub
