John Pierce:
>>> title Mandriva GRUB
>>> rootnoverify (hd1,0)
>>> chainloader +1
>>> makeactive
>>> boot
Tim:
>> Just by the by, it started booting with the chainloader line, so never
>> got as far as touching the next two commands. If you need to add
>> commands, like makeactive, they have to come earlier in the piece.
John Summerfield:
> That's interesting. When i tested at the grub commandline, it didn't
> boot until I said 'boot.'
I think you might find the command line behaves a bit differently than
the boot menus.
-- Command: boot
Boot the OS or chain-loader which has been loaded. Only necessary
if running the fully interactive command-line (it is implicit at
the end of a menu entry).
My new Laptop came with Windows Vista (gawd, but it's painful), to run
it this is all that I have in the grub.conf file to launch it:
title Windows Vista
lock
rootnoverify (hd0,1)
chainloader +1
There's no "boot" in it. I added the "lock" because I don't want
someone else to be able to run it.
I might be wrong in that chainloader, itself, starts it. It could
simply be that reaching the end of the list starts booting, but that
would be easy enough to test (e.g. stick a password lock command in,
after the chainloader command, for instance). I just don't want to
reboot at the moment.
In John Pierce's example, the boot line is redundant, so it doesn't
really matter. But if he needed the makeactive line, logically speaking
you'd expect it to need to come before chainloader (you'd want to set
it before you started booting). It also makes sense for it to need to
come after rootnoverify, since it's going to act on the partition set by
rootnoverify, or just root.
He may not actually need to make the partition active, anyway.
--
(This box runs FC7, my others run FC4, FC5 & FC6, in case that's
important to the thread.)
Don't send private replies to my address, the mailbox is ignored.
I read messages from the public lists.
