From: Peter Humphrey <peter@prh.myzen.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Separate /usr partition
Date: Thu, 15 Sep 2022 09:57:44 +0100 [thread overview]
Message-ID: <12071369.O9o76ZdvQC@wstn> (raw)
In-Reply-To: <20220914230945.489ac907@digimed.co.uk>
On Wednesday, 14 September 2022 23:09:59 BST Neil Bothwick wrote:
> On Wed, 14 Sep 2022 16:50:45 +0100, Peter Humphrey wrote:
> > I'm thinking of separating /usr onto its own partition so that I can
> > have it mounted read-only except while updating it. I'd prefer not to
> > have to make an init thingy, not having needed one up to now. Besides,
> > some machines have things like early-ucode or amd-uc.
>
> Most of this has already been answered, except for your final point. You
> can load more than one initrd at boot, so you can still apply microcode
> updates. For example, with systemd-boot
>
> title Desktop
> version 5.15.59-gentoo
> linux /vmlinuz-5.15.59-gentoo
> options root=LABEL=blah blah
> initrd /amd-uc.img
> initrd /initramfs-5.15.59-gentoo.img
>
> I use dracut to create the initrd, which is so straighforward even Dale
> can't break it ;-)
:)
That seems to be the way to go then - even dinosaurs die out in the end.
Perhaps Dale will show us the command he referred to.
Thank you all for your help.
--
Regards,
Peter.
next prev parent reply other threads:[~2022-09-15 8:57 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-14 15:50 [gentoo-user] Separate /usr partition Peter Humphrey
2022-09-14 16:12 ` karl
2022-09-14 16:17 ` Laurence Perkins
2022-09-14 16:30 ` Rich Freeman
2022-09-14 17:04 ` Dale
2022-09-14 20:38 ` karl
2022-09-14 22:09 ` Neil Bothwick
2022-09-15 8:57 ` Peter Humphrey [this message]
2022-09-15 10:00 ` Dale
2022-09-15 10:48 ` Peter Humphrey
2022-09-15 11:15 ` Dale
2022-09-15 17:32 ` Neil Bothwick
2022-09-15 17:35 ` Neil Bothwick
2022-09-15 18:15 ` Laurence Perkins
2022-09-15 19:54 ` Neil Bothwick
2022-09-16 15:16 ` Peter Humphrey
2022-09-16 15:25 ` Dale
2022-09-16 15:49 ` Peter Humphrey
2022-09-16 17:57 ` Rich Freeman
2022-09-17 7:54 ` Peter Humphrey
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=12071369.O9o76ZdvQC@wstn \
--to=peter@prh.myzen.co.uk \
--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