Karl Larsen wrote:
> Well I just got my updates from a few weeks worth and it included a
> kernel and Gutsy is up and running after a re-boot. What you say Nils
> is Frank may have put a Debian kernel in his Ubuntu? I thought he got
> the update and it didn't work after a re-boot.

No, what I say is that he is possibly looking for the problem at the wrong
place, i.e. if it is the menu.lst from Debian, Ubuntu has nothing to do
with the problem because Ubuntu doesn't change that file due to a kernel
update. It would only be changed by a Debian update.


Nils

--
ubuntu-users mailing list
ubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Sun, 29 Jun 2008 20:32:25 +0200
Nils Kassube <kassube@gmx.net> wrote:

> Karl Larsen wrote:
> > Well I just got my updates from a few weeks worth and it
> > included a kernel and Gutsy is up and running after a re-boot. What
> > you say Nils is Frank may have put a Debian kernel in his Ubuntu? I
> > thought he got the update and it didn't work after a re-boot.
>
> No, what I say is that he is possibly looking for the problem at the
> wrong place, i.e. if it is the menu.lst from Debian, Ubuntu has
> nothing to do with the problem because Ubuntu doesn't change that
> file due to a kernel update. It would only be changed by a Debian
> update.


No it is the menu.lst from Ubuntu. Every time Grub updates it because
of a Kernel update I have to ensure both match. Debian hasn't updated
the Kernel for several weeks at least. I have been looking for a way
around this PITA for sometime but have been unsuccessful.


Cheers
- --
Frank
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFIZ9hIO/2kt/1jPOIRAtKnAKCBR1F7tG+ZNboeIO4HJtqKzKTGrQCg3Emq
5eMg8wQ8JjlGdyHwphkKY24=
=/s1i
-----END PGP SIGNATURE-----

--
ubuntu-users mailing list
ubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Sun, 29 Jun 2008 11:47:50 -0600
Karl Larsen <k5di@zianet.com> wrote:

> >
> Here is how you get a uuid id:
>
> When you know which partitions you want to get a UUID word for
> you just do this:
>
> sudo vol_id /dev/hda2 and it will print out this:
>
> karl@karl-desktop:~$ sudo vol_id /dev/hda2
> [sudo] password for karl:

/snipped/

OK did that. For some reason fstab already had the UUID in it. It was
menu.lst which referred to the drive as hda3 which I had to change to
sda3. Now it is referred to as the UUID. After a few false starts
(typos) Gutsy boots fine. I also ensured the menu.lst in the Debian Sid
partition is identical to the one in the Gutsy partition. I do wish
there were a simpler way of booting the two systems.

Thanks for the fix Karl.

Cheers
- --
Frank
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFIZ+DaO/2kt/1jPOIRArP5AKDpSJDUqjRLPY78meOmcgOOLeFwWgCeKt+q
faZU9J7v2WLTqxv1lpFa9WM=
=cx83
-----END PGP SIGNATURE-----

--
ubuntu-users mailing list
ubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users

On Sun, 29 Jun 2008 20:00:16 +0200
Nils Kassube <kassube@gmx.net> wrote:

> Frank McCormick wrote:
> > It's Gutsy and has been used since I updated it was released.
> > I had to change menu.lst after the last update as the machine
> > wouldn't boot because the old menu.lst referred to root as hda3 when
> > Ubuntu wanted sda3 ( it's an IDE drive ).
> > This is the current menu.lst.
> > The first items are for my Debian Sid system.
>
> Is this the file /boot/grub/menu.lst of your Ubuntu installation or
> is it from your Debian installation? There is a huge difference
> because if it is from your Debian installation, the update-grub
> script for Ubuntu shouldn't touch it at all. It looks like it isn't
> from Ubuntu Gutsy because otherwise the kernel used in the automagic
> kernel list would be 2.6.22-* not 2.6.24-*. If it is from Debian, you
> would have to manage the Ubuntu part manually, and your problem
> doesn't come from Ubuntu but from Debian because the Ubuntu script
> wouldn't see your menu.lst.


In thinking about it..it's possible the lst came from the wrong
partition. But I know the Ubuntu lst did refer to hda3, not sda3. As I
said to Karl both lsts (the one in the Debian partition and the one in
Gutsy now both refer to the Gutsy partition via its UUID. Wish there
were a simpler way than keeping the two menus synchronized!!

Cheers
--
Frank

--
ubuntu-users mailing list
ubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users

Frank McCormick wrote:
> In thinking about it..it's possible the lst came from the wrong
> partition. But I know the Ubuntu lst did refer to hda3, not sda3. As I
> said to Karl both lsts (the one in the Debian partition and the one in
> Gutsy now both refer to the Gutsy partition via its UUID.

Well, now that you changed it to use UUIDs it doesn't matter where it came
from. Anyway, I think it is rather strange that your devices were changed
from sda3 to hda3. If I understand the update-grub script correctly, it
looks for the current device name and uses that name for the new
menu.lst. If it was previously sda3, it should be sda3 now.

> Wish there
> were a simpler way than keeping the two menus synchronized!!

You could modify the update-grub scripts of both installations - but that
would not necessarily make it simpler.


Nils

--
ubuntu-users mailing list
ubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users

Frank McCormick wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On Sun, 29 Jun 2008 20:32:25 +0200
> Nils Kassube <kassube@gmx.net> wrote:
>
>> No, what I say is that he is possibly looking for the problem at the
>> wrong place, i.e. if it is the menu.lst from Debian, Ubuntu has
>> nothing to do with the problem because Ubuntu doesn't change that
>> file due to a kernel update. It would only be changed by a Debian
>> update.
>
>
> No it is the menu.lst from Ubuntu. Every time Grub updates it because
> of a Kernel update I have to ensure both match. Debian hasn't updated
> the Kernel for several weeks at least. I have been looking for a way
> around this PITA for sometime but have been unsuccessful.
>

Why must both match? I have both Debian and Ubuntu installed; Debian's
Grub is in the MBR, and Ubuntu's Grub in a partition's bootsector. I
boot Ubuntu through the chainloading mechanism.

One Linux installation has basically nothing to do with the other. If
you setup your system this way, your need to synchronize menu.lst files
will probably disappear.



--
ubuntu-users mailing list
ubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Mon, 30 Jun 2008 00:22:10 -0500
"Mumia W." <paduille.4062.mumia.w+nospam@earthlink.net> wrote:

> > updated the Kernel for several weeks at least. I have been looking for
> > a way around this PITA for sometime but have been unsuccessful.
> >
>
> Why must both match? I have both Debian and Ubuntu installed; Debian's
> Grub is in the MBR, and Ubuntu's Grub in a partition's bootsector. I
> boot Ubuntu through the chainloading mechanism.
>

Never thought of that!
Can you let me see your menu.lst(s) ?

Thanks

Cheers

- --
Frank
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkho52oACgkQnQV1aTcQlJvfRQCghzALS8wpVJ s3f5NQKJJpKDNd
YasAn02JBonYgZY3CDUwbPY82waAv/4o
=9mwb
-----END PGP SIGNATURE-----

--
ubuntu-users mailing list
ubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users

Frank McCormick wrote:
> [...]
> Can you let me see your menu.lst(s) ?
>
> Thanks
>
> Cheers

It's better for you to let Grub do most of the work in creating
menu.lst's, but place Ubuntu's Grub in the "superblock" of its
partition, so you'll have two installations of Grub; let's call them A
and B.

"A" is in the MBR (e.g. /dev/sda) and contains two "important" boot
stanzas: one for Debian (/dev/sda1) and one for chainloading (/dev/sda2).

"B" is in the superblock (bootsector) of /dev/sda2, and it contains one
"important" boot stanza--the one for booting Ubuntu in /dev/sda2.

-----menu.lst for "A"--------
title Debian on /dev/sda1
root (hd0,0)
kernel /boot/vmlinuz-2.6.18-6-486 root=/dev/sda1 ro
boot

title Chainloading /dev/sda2 (probably Ubuntu)
rootnoverify (hd0,1)
chainloader +1
boot

-----menu.lst of "B"--------
title Ubuntu on /dev/sda2
root (hd0,1)
kernel /boot/vmlinuz-2.6.24-19-generic root=/dev/sda2 ro
boot

----------------end-----------

Do not copy those directly! Let Grub make the menu.lst files and make
appropriate adjustments. I could never have done it had not Grub made
very good template files for me.

Installing Grub to the two different locations could get tricky.

Grub installation "A" might be put in the MBR like so:
grub-install --root-directory=/mounts/sda1 /dev/sda

And Grub installation "B" might be placed in /dev/sda2 like so:
grub-install /dev/sda2

However, I'm not sure about that. When I installed Ubuntu, I told the
installer to install grub to /dev/sda2, so I never had to execute
grub-install myself.

Others on the list can help you be sure you give the right options to
grub-install. Although it sounds a little complicated, once it's set up
you don't have to worry about the two Grub installations conflicting or
clobbering each other. Good luck.



--
ubuntu-users mailing list
ubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Mon, 30 Jun 2008 12:32:39 -0500
"Mumia W." <paduille.4062.mumia.w+nospam@earthlink.net> wrote:

> Frank McCormick wrote:
> > [...]
> > Can you let me see your menu.lst(s) ?
>
> It's better for you to let Grub do most of the work in creating
> menu.lst's, but place Ubuntu's Grub in the "superblock" of its
> partition, so you'll have two installations of Grub; let's call them A
> and B.
>
> "A" is in the MBR (e.g. /dev/sda) and contains two "important" boot
> stanzas: one for Debian (/dev/sda1) and one for chainloading (/dev/sda2).
>
> "B" is in the superblock (bootsector) of /dev/sda2, and it contains one
> "important" boot stanza--the one for booting Ubuntu in /dev/sda2.
>
> -----menu.lst for "A"--------
> title Debian on /dev/sda1
> root (hd0,0)
> kernel /boot/vmlinuz-2.6.18-6-486 root=/dev/sda1 ro
> boot
>
> title Chainloading /dev/sda2 (probably Ubuntu)
> rootnoverify (hd0,1)
> chainloader +1
> boot
>
> -----menu.lst of "B"--------
> title Ubuntu on /dev/sda2
> root (hd0,1)
> kernel /boot/vmlinuz-2.6.24-19-generic root=/dev/sda2 ro
> boot
>
> ----------------end-----------
>
> Do not copy those directly! Let Grub make the menu.lst files and make
> appropriate adjustments. I could never have done it had not Grub made
> very good template files for me.
>
> Installing Grub to the two different locations could get tricky.
> Others on the list can help you be sure you give the right options to
> grub-install. Although it sounds a little complicated, once it's set up
> you don't have to worry about the two Grub installations conflicting or
> clobbering each other. Good luck.


I think I'll wait to see if any Grub experts can explain this whole
process!!

Thanks
Cheers



- --
Frank
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkhqNJgACgkQnQV1aTcQlJsxXQCfQ1A3m7mf6K FRsVWQ9KAEgJwh
ci4AnRpgbvOE1cXCSZ6adqfVgULLjHXj
=YQfl
-----END PGP SIGNATURE-----

--
ubuntu-users mailing list
ubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users

Frank McCormick wrote:
>
> I think I'll wait to see if any Grub experts can explain this whole
> process!!
>
> Thanks
> Cheers
>

I forgot to mention that you should also install 'grub-doc' and read
'info grub'. That'll work even if the Grub experts don't come around too
quickly ;-)


--
ubuntu-users mailing list
ubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users