Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
multi-boot+grub2+separate boot partition
29 views
Skip to first unread message
Russell L. Harris
Nov 10, 2012, 1:40:01 AM11/10/12
to
I wish to use grub2 to multi-boot the following systems:
=> Debian "stable" (Squeeze) on /dev/sda6
=> Debian "testing" (Wheezy) on /dev/sda7
=> Ubuntu (10.x) on /dev/sda8
This is a "work" machine and my primary interest is "stable". But I
need to become familiar with Wheezy, which is about to become
"stable". I am installing Ubuntu as a safety net, because Ubuntu
developers seem to find a way to get all of the peripheral devices
working, even if it the resulting configuration is non-standard.
I have read the Debian installation manual and I have searched with
Google, but thus far I have not found a HOWTO for such an arrangement
using a separate boot partition.
I plan to update "testing" from time to time. Once Wheezy becomes
"stable", I plan to drop Squeeze and install the new "testing". I may
even update Ubuntu.
It seemed to me that the proper approach would be to use a separate
boot partition on /dev/sda1, and to make it policy always to run
"update-grub" from "stable".
I instructed the Squeeze installer to install grub2 to /dev/sda1.
I instructed the Wheezy installer to install grub2 to /dev/sda7.
I instructed the Ubuntu installer to install grub2 to /dev/sda8.
I booted into Squeeze and executed "update-grub". The messages were:
=> found linux-image /boot/vmlnuz-2.6.32-5-686 (this is Squeeze)
=> found linux-image /boot/initrd-2.6.32-5-686 (this is Squeeze)
=> found Debian GNU/Linux (Wheezy/Sid) on /dev/sda7
=> Ubuntu 10.10 on /dev/sda8
But upon rebooting, the grub menu contains only entries for Squeeze
and Ubuntu.
Is it reasonable to use a separate boot partition? Can this scheme be
made to work?
RLH
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/2012111006...@gospelbroadcasting.org
=> Debian "stable" (Squeeze) on /dev/sda6
=> Debian "testing" (Wheezy) on /dev/sda7
=> Ubuntu (10.x) on /dev/sda8
This is a "work" machine and my primary interest is "stable". But I
need to become familiar with Wheezy, which is about to become
"stable". I am installing Ubuntu as a safety net, because Ubuntu
developers seem to find a way to get all of the peripheral devices
working, even if it the resulting configuration is non-standard.
I have read the Debian installation manual and I have searched with
Google, but thus far I have not found a HOWTO for such an arrangement
using a separate boot partition.
I plan to update "testing" from time to time. Once Wheezy becomes
"stable", I plan to drop Squeeze and install the new "testing". I may
even update Ubuntu.
It seemed to me that the proper approach would be to use a separate
boot partition on /dev/sda1, and to make it policy always to run
"update-grub" from "stable".
I instructed the Squeeze installer to install grub2 to /dev/sda1.
I instructed the Wheezy installer to install grub2 to /dev/sda7.
I instructed the Ubuntu installer to install grub2 to /dev/sda8.
I booted into Squeeze and executed "update-grub". The messages were:
=> found linux-image /boot/vmlnuz-2.6.32-5-686 (this is Squeeze)
=> found linux-image /boot/initrd-2.6.32-5-686 (this is Squeeze)
=> found Debian GNU/Linux (Wheezy/Sid) on /dev/sda7
=> Ubuntu 10.10 on /dev/sda8
But upon rebooting, the grub menu contains only entries for Squeeze
and Ubuntu.
Is it reasonable to use a separate boot partition? Can this scheme be
made to work?
RLH
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/2012111006...@gospelbroadcasting.org
Brian
Nov 10, 2012, 8:20:02 AM11/10/12
to
On Sat 10 Nov 2012 at 06:34:27 +0000, Russell L. Harris wrote:
> I wish to use grub2 to multi-boot the following systems:
>
> => Debian "stable" (Squeeze) on /dev/sda6
>
> => Debian "testing" (Wheezy) on /dev/sda7
>
> => Ubuntu (10.x) on /dev/sda8
>
> This is a "work" machine and my primary interest is "stable". But I
> need to become familiar with Wheezy, which is about to become
> "stable". I am installing Ubuntu as a safety net, because Ubuntu
> developers seem to find a way to get all of the peripheral devices
> working, even if it the resulting configuration is non-standard.
>
> I have read the Debian installation manual and I have searched with
> Google, but thus far I have not found a HOWTO for such an arrangement
> using a separate boot partition.
I cannot think of a reason for having such a separate partition.
> I wish to use grub2 to multi-boot the following systems:
>
> => Debian "stable" (Squeeze) on /dev/sda6
>
> => Debian "testing" (Wheezy) on /dev/sda7
>
> => Ubuntu (10.x) on /dev/sda8
>
> This is a "work" machine and my primary interest is "stable". But I
> need to become familiar with Wheezy, which is about to become
> "stable". I am installing Ubuntu as a safety net, because Ubuntu
> developers seem to find a way to get all of the peripheral devices
> working, even if it the resulting configuration is non-standard.
>
> I have read the Debian installation manual and I have searched with
> Google, but thus far I have not found a HOWTO for such an arrangement
> using a separate boot partition.
> I plan to update "testing" from time to time. Once Wheezy becomes
> "stable", I plan to drop Squeeze and install the new "testing". I may
> even update Ubuntu.
>
> It seemed to me that the proper approach would be to use a separate
> boot partition on /dev/sda1, and to make it policy always to run
> "update-grub" from "stable".
>
> I instructed the Squeeze installer to install grub2 to /dev/sda1.
> I instructed the Wheezy installer to install grub2 to /dev/sda7.
> I instructed the Ubuntu installer to install grub2 to /dev/sda8.
Then, if Squeeze was not the last installation done and I wanted it to
head the GRUB menu, I'd have booted into it and run
grub-install /dev/sda
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Russell L. Harris
Nov 10, 2012, 10:30:02 AM11/10/12
to
* Brian <ad...@cityscape.co.uk> [121110 13:18]:
If my understanding of grub is correct, the execution of
"grub-install /dev/sda":
(1) writes the various grub files to the "/boot/grub" directory of
the partition corresponding to the operating system which executes
"grub-install", then
(2) writes a short instruction phrase to the master boot record
(MBR) of /dev/sda, which phrase terminates in a link to the grub
code in the "/boot/grub" directory of the partition corresponding
to the operating system which last invoked "install-grub".
RLH
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/2012111015...@gospelbroadcasting.org
> On Sat 10 Nov 2012 at 06:34:27 +0000, Russell L. Harris wrote:
...
> > I instructed the Squeeze installer to install grub2 to /dev/sda1.
> > I instructed the Wheezy installer to install grub2 to /dev/sda7.
> > I instructed the Ubuntu installer to install grub2 to /dev/sda8.
...
> > I instructed the Wheezy installer to install grub2 to /dev/sda7.
> > I instructed the Ubuntu installer to install grub2 to /dev/sda8.
> I'd have installed GRUB to /dev/sda each time.
>
> Then, if Squeeze was not the last installation done and I wanted it to
> head the GRUB menu, I'd have booted into it and run
>
> grub-install /dev/sda
Thanks, Brian.
>
> Then, if Squeeze was not the last installation done and I wanted it to
> head the GRUB menu, I'd have booted into it and run
>
> grub-install /dev/sda
If my understanding of grub is correct, the execution of
"grub-install /dev/sda":
(1) writes the various grub files to the "/boot/grub" directory of
the partition corresponding to the operating system which executes
"grub-install", then
(2) writes a short instruction phrase to the master boot record
(MBR) of /dev/sda, which phrase terminates in a link to the grub
code in the "/boot/grub" directory of the partition corresponding
to the operating system which last invoked "install-grub".
RLH
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Brian
Nov 10, 2012, 10:40:02 AM11/10/12
to
On Sat 10 Nov 2012 at 15:20:33 +0000, Russell L. Harris wrote:
> If my understanding of grub is correct, the execution of
> "grub-install /dev/sda":
>
> (1) writes the various grub files to the "/boot/grub" directory of
> the partition corresponding to the operating system which executes
> "grub-install", then
>
> (2) writes a short instruction phrase to the master boot record
> (MBR) of /dev/sda, which phrase terminates in a link to the grub
> code in the "/boot/grub" directory of the partition corresponding
> to the operating system which last invoked "install-grub".
"Yes" to both. Tom H wrote a nice short account of this a couple of days
> If my understanding of grub is correct, the execution of
> "grub-install /dev/sda":
>
> (1) writes the various grub files to the "/boot/grub" directory of
> the partition corresponding to the operating system which executes
> "grub-install", then
>
> (2) writes a short instruction phrase to the master boot record
> (MBR) of /dev/sda, which phrase terminates in a link to the grub
> code in the "/boot/grub" directory of the partition corresponding
> to the operating system which last invoked "install-grub".
ago. Here's the thread:
http://lists.debian.org/debian-user/2012/11/msg00280.html
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
0 new messages