 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Sat, 08 Nov 2008 17:45:16 +0100, Darren New <dne### [at] san rrcom> wrote:
> Fredrik Eriksson wrote:
>> I think you may have to chroot into the Linux installation before
>> setting up GRUB if the installed version is not the same as the one on
>> the CD. GRUB will crap out if stage1 and stage2 are from different
>> versions.
>
> Hmmm. Fair enough. But I didn't do any updates on at least some of the
> tests, so I'm assuming the two versions were the same.
The version that gets installed from the CD might not be the same as the
one installed *on* the CD.
> I want Vista to chain-load GRUB. (More precisely, I want Vista to chain
> load Linux, but LILO wasn't happy either.)
Personally I use grub4dos for that. That way, I do not need to change
anything on the Windows side when I update GRUB on the Linux side. Not
sure how well it works with Vista though; setting it up on XP is trivial.
Also, should you not be doing "setup (hd0,1)" if you want to chain-load
from the Vista boot-loader?
--
FE
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Fredrik Eriksson wrote:
> The version that gets installed from the CD might not be the same as the
> one installed *on* the CD.
Good point, good point. I never ran into that before, but you could be
right there.
> Personally I use grub4dos for that. That way, I do not need to change
> anything on the Windows side when I update GRUB on the Linux side.
Unless GRUB rewrites the per-sector partition, I don't need to change
anything on the Vista side either. I didn't have trouble changing, for
example, the menus, IIRC. I'll check it out.
There's also a program called EditBCD or some such that can install a
variety of boot loaders. I was just trying to do it all with native code.
> Also, should you not be doing "setup (hd0,1)" if you want to chain-load
> from the Vista boot-loader?
Should I? What GRUB actually does when it sets up is still kind of
mysterious to my. I'm basing my commands on what I did when I set up a
bunch of 32-bit machines at work - after restoring the dump, the script
ran those grub commands and then it would boot. (Well, not exactly,
because it was a RAID at work, so it had to do it with two different
devices as root.)
I'll try it with setup (hd0,1) next, and with a chroot first. Thanks for
the advice!
--
Darren New / San Diego, CA, USA (PST)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Sat, 08 Nov 2008 18:22:44 +0100, Darren New <dne### [at] sanrrcom> wrote:
>> Personally I use grub4dos for that. That way, I do not need to change
>> anything on the Windows side when I update GRUB on the Linux side.
>
> Unless GRUB rewrites the per-sector partition, I don't need to change
> anything on the Vista side either. I didn't have trouble changing, for
> example, the menus, IIRC. I'll check it out.
Changing the config is not a problem. Updating GRUB to a newer version is.
Anytime you re-setup the GRUB boot-loader you have to update the copy you
keep on the Windows side.
>> Also, should you not be doing "setup (hd0,1)" if you want to chain-load
>> from the Vista boot-loader?
>
> Should I? What GRUB actually does when it sets up is still kind of
> mysterious to my.
"setup (hd0)" installs GRUB to the MBR of hd0, i.e. it overwrites the
first stage of the Vista boot-loader. If you want to chain-load Linux, you
should install GRUB to the boot sector of the Linux boot partition.
--
FE
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Fredrik Eriksson wrote:
> Changing the config is not a problem. Updating GRUB to a newer version
> is. Anytime you re-setup the GRUB boot-loader you have to update the
> copy you keep on the Windows side.
Yes, that I'm aware of. Fortunately easy to fix from the SuSE rescue
disk, if it updates and I don't notice.
> "setup (hd0)" installs GRUB to the MBR of hd0, i.e. it overwrites the
> first stage of the Vista boot-loader. If you want to chain-load Linux,
> you should install GRUB to the boot sector of the Linux boot partition.
Mwa ha! Very good! Thanks! I'll give that a try as soon as I get
stuff reinstalled. :-)
{I guess I should have put off the wipe until I got an answer. ;-)
--
Darren New / San Diego, CA, USA (PST)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Darren New wrote:
> Mwa ha! Very good! Thanks! I'll give that a try as soon as I get
> stuff reinstalled. :-)
Using setup (hd0,1) seems to have done the trick. Thanks!
I can't chroot, since /tmp/root/dev doesn't seem to be set up, but that
shouldn't be much of a problem, methinks. I wouldn't think grub gets
updated incompatibly very often. :-) Given that it's pretty trivial to
back up every file on a partition under Linux and to frob the results
off a live or rescue CD, I don't expect even a disaster where I have to
reinstall would be that much of a problem.
Thanks for the clue!
--
Darren New / San Diego, CA, USA (PST)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Sat, 08 Nov 2008 12:09:10 +0100, Fredrik Eriksson wrote:
> I think you may have to chroot into the Linux installation before
> setting up GRUB if the installed version is not the same as the one on
> the CD. GRUB will crap out if stage1 and stage2 are from different
> versions.
Yeah, I would concur with that - have had that experience myself.
Jim
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Jim Henderson wrote:
> Yeah, I would concur with that - have had that experience myself.
My stumbling block here is that if I use chroot, I no longer have /dev
for GRUB to write things to. If it comes to that much of a disaster,
I'll reinstall stuff and rescue things on a per-file/per-directory
basis. :-)
--
Darren New / San Diego, CA, USA (PST)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Sun, 09 Nov 2008 19:00:24 +0100, Darren New <dne### [at] sanrrcom> wrote:
> My stumbling block here is that if I use chroot, I no longer have /dev
> for GRUB to write things to.
You must bind /dev in the new environment before chrooting.
Gentoo users know how to chroot properly, as it is a required step when
installing Gentoo:
http://www.gentoo.org/doc/en/handbook/handbook-amd64.xml?part=1&chap=6
--
FE
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Fredrik Eriksson wrote:
> You must bind /dev in the new environment before chrooting.
>
> Gentoo users know how to chroot properly, as it is a required step when
> installing Gentoo:
> http://www.gentoo.org/doc/en/handbook/handbook-amd64.xml?part=1&chap=6
Thanks. I figured it was merely a stumbling block rather than a wall. ;-)
I'll put that into my instructions file under "in case of complete user
screw-up..."
I'm learning way more about system administration than I ever wanted to
know, you know? :-)
--
Darren New / San Diego, CA, USA (PST)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Sun, 09 Nov 2008 10:00:24 -0800, Darren New wrote:
> Jim Henderson wrote:
>> Yeah, I would concur with that - have had that experience myself.
>
> My stumbling block here is that if I use chroot, I no longer have /dev
> for GRUB to write things to. If it comes to that much of a disaster,
> I'll reinstall stuff and rescue things on a per-file/per-directory
> basis. :-)
I also mount /dev/ in the chrooted environment.
Jim
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
