public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
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 15:49:08 -0000 (UTC)	[thread overview]
Message-ID: <uraepk$142k$1@ciao.gmane.io> (raw)
In-Reply-To: 20240223071614.1e8ae072@wolf

On 2024-02-23, Wojciech Kuzyszyn <wkuz@op.pl> wrote:

> I guess most (all) of the distro's you are talking about use GRUB (or
> at least they allow to do it).

Yes, I belive that they are all now using Grub2.

> If that's true, I'm pretty sure you can happily let them overwrite
> the GRUB in MBR as many times as they want, since it's the same (or
> just probably minor version differences) bootloader. Just make a
> copy of /boot/grub/grub.cfg and make sure it's the same on every
> partition.

That means I have to update all of those grub.cfg files manually every
time I install or update a distro. That's a lot of work.

> Or, even better, if that's possible right now, make a common /boot
> partition and after installing the new distro just merge the
> (probably new) /boot/grub/grub.cfg with your old one.

"just merge the new grub.cfg file with the old one" is the problem.

I tried that for a while: every time a distro got installed, I would
add it to the "main" grub config file. Every time a distro got a
kernel update, I'd modify the main grub config file. It was a lot more
work that my current scheme (and a lot more error prone).

> I really think that *should* work!

It would work, but maintaining the grub.cfg files is a lot of
work. The scheme I'm using now doens't require me to mess with any of
the grub.cfg files when distros get updated or installed.

--
Grant



  reply	other threads:[~2024-02-23 15:49 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 [this message]
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
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='uraepk$142k$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