From: Grant Edwards <grant.b.edwards@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: How to set up drive with many Linux distros?
Date: Fri, 23 Feb 2024 18:58:30 -0000 (UTC) [thread overview]
Message-ID: <urapsm$ip3$1@ciao.gmane.io> (raw)
In-Reply-To: deed5bdd-24a3-43b6-b266-b1d1bb7c0d43@youngman.org.uk
On 2024-02-23, Wols Lists <antlists@youngman.org.uk> wrote:
> On 23/02/2024 00:28, Grant Edwards wrote:
>> In my experience, <distro>'s bootloader does not boot other
>> installations by calling other bootloaders. It does so by rummaging
>> through all of the other partitions looking for kernel images,
>> intird files, grub.cfg files, etc. It then adds menu entries to
>> the config file for <distro>'s bootloader which, when selected,
>> directly load the kernel image and initrd from those other
>> partitions. Sometimes, it works -- at least until those other
>> installations get updated without the knowlege of the distro that
>> currently "owns" the MBR's bootloader config. Then it stops working
>> until you tell that bootloader to re-do it's rummaging about
>> routine.
>
> IME distros that try that (SUSE, anyone!) generally get confused as
> to which kernel belongs to which root partition.
>
> Hence needing to boot with a live distro to edit the resulting mess
> and get the system to actually come up without crashing ...
IIRC, all of the big distros used to do that. It didn't work very
well, but at least it took a really long time.
However, I read recently that Ubuntu had disabled the os-prober by
default in 22.04. Disabling it was always one of the first things I
did after installing a new distro.
The simple solution is to give up on multi-booting a dozen different
distros on a single disk and buy a pocketful of USB 3 thumb drives.
--
Grant
next prev parent reply other threads:[~2024-02-23 18:58 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-22 19:17 [gentoo-user] How to set up drive with many Linux distros? Grant Edwards
2024-02-22 21:25 ` Wol
2024-02-22 21:45 ` [gentoo-user] " Grant Edwards
2024-02-22 22:58 ` Wol
2024-02-23 0:28 ` Grant Edwards
2024-02-23 6:16 ` Wojciech Kuzyszyn
2024-02-23 15:49 ` Grant Edwards
2024-02-23 12:06 ` Michael
2024-02-23 16:04 ` Grant Edwards
2024-02-23 17:05 ` Wols Lists
2024-02-23 18:58 ` Grant Edwards [this message]
2024-02-23 19:11 ` Mark Knecht
2024-02-23 19:51 ` Grant Edwards
2024-02-23 20:03 ` Mark Knecht
2024-02-23 21:14 ` Grant Edwards
2024-02-26 11:57 ` [gentoo-user] " gentoo-user
2024-02-26 17:10 ` eric
2024-02-26 18:01 ` [gentoo-user] " Grant Edwards
2024-02-26 18:12 ` eric
2024-02-26 20:51 ` Grant Edwards
2024-02-26 21:44 ` Wol
2024-02-26 23:44 ` Grant Edwards
2024-02-27 0:12 ` Mark Knecht
2024-02-27 11:40 ` Peter Humphrey
2024-03-08 23:24 ` Grant Edwards
2024-03-10 12:58 ` Michael
2024-03-10 18:35 ` Grant Edwards
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='urapsm$ip3$1@ciao.gmane.io' \
--to=grant.b.edwards@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox