Re: Debian 8 and Debian 9 Dual Boot
- Date: Wed, 29 Nov 2017 18:19:13 +0000
- From: Joe <joe@xxxxxxxxxxxxxx>
- Subject: Re: Debian 8 and Debian 9 Dual Boot
On Wed, 29 Nov 2017 13:07:01 -0500
Dan Norton <dnorton@xxxxxxxxxxxxxx> wrote:
> On 11/16/2017 03:13 PM, Felix Miata wrote:
> > Joe composed on 2017-11-16 19:27 (UTC):
> >> I see the date of the page is 2015,
> > IIRC, that 2015 update was all about updating and/or replacing
> > broken links.
> >> Multiple OSes will still use one overall bootloader, which may or
> >> may not redirect to other bootloaders. It is common, therefore, to
> >> use a single physical partition for /boot, common to all *nix
> >> OSes....
> > Mounting the same single primary partition as /boot to all *nix
> > OSes invites virtually the same trouble that installing Grub to MBR
> > causes. Absent user intervention, each OS thinks it owns the space,
> > so at updates times, each stomps on whatever is there at the time,
> > eventually exhausting its freespace with a multitude of diverse
> > kernels and initrds. Only one OS, or no OS, should mount the
> > bootable physical partition to /boot. Others can either have their
> > own bootloader installed to their own / filesystem, or be used
> > without their own bootloader.
> > On most of my PCs, the bootable primary is never mounted to /boot.
> > I manage it manually myself, providing direct loading of kernels
> > and initrds, as well as chainloading entries, and configfile
> > entries, the latter two used primarily when prior kernels are to be
> > booted, the former for most booting.
> > For someone doing multiboot the first time, it's easiest, if not a
> > requirement, for the first installation to have the primary mounted
> > to /boot. The subsequent installations either need to have no
> > bootloader or bootloader only installed to /; or, the newer can be
> > configured to mount the primary on /boot, and the original, prior
> > to its next boot, preferably immediately prior to starting the new
> > installation, reconfigured to not mount the primary on /boot, not
> > manage the bootloader installed there, and relocate its content to
> > its own / filesystem.
> After POST, the following appears:
> PXE-E53: No boot filename received
> PXE-MOF: Exiting PXE ROM.
> ERROR:No boot disk has been detected or the disk has failed.
> Isn't that because the primary is not mounted to /boot?
> Sorry to be so dense, but how do I "have the primary mounted
> to /boot?"
> > Multiboot setup is complex, one of the reasons why virtualization
> > became popular. There is no single right way to get where you want
> > to go. For a beginner it helps a lot to have an extra PC to do the
> > learning, and for doc access while doing the installations and
> > configurations on the other. :-)