From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Separate /usr partition
Date: Wed, 14 Sep 2022 12:04:49 -0500 [thread overview]
Message-ID: <1d3cf402-5697-ab85-a880-72791149f4c2@gmail.com> (raw)
In-Reply-To: <5874509.lOV4Wx5bFT@wstn>
Peter Humphrey wrote:
> Hello list,
>
> 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.
>
> I've found a few guides on the Web, but I'm still confused. Is there a simple
> guide to doing this? I know of at least one subscriber here who's done it. :)
>
I read the other replies but want to add this. I use grub for my boot
loader. I use dracut to build the init thingy. It's really easy and I
only had a bad init thingy once very early on, could have been my fault
and most likely was. Since then, updating a kernel takes a lot longer
than building the init thingy and updating grub. To be honest, if the
linux link is pointing to the right kernel, one could likely script the
dracut and grub update part. My point is, if you want to be sure you
can boot without resorting to some rescue options, I'm sure any of us
would help walk you through this. I actually have notes and I think it
was Neil that shared his command and it is just plain easy. So far,
Neil's command has not failed me once. I do mine by hand. I name my
own kernels and the init thingy as well. Others have what is most
likely a even easier and less time consuming method.
You may can do it the way you are wanting to but for how long is the
question. Odds are high that at some point, you will have a system that
won't boot because something that's needed isn't there. I think Rich
points that out pretty good.
Just something to think on from a guy that really hates the init
thingy. ;-)
Dale
:-) :-)
next prev parent reply other threads:[~2022-09-14 17:04 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 [this message]
2022-09-14 20:38 ` karl
2022-09-14 22:09 ` Neil Bothwick
2022-09-15 8:57 ` Peter Humphrey
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=1d3cf402-5697-ab85-a880-72791149f4c2@gmail.com \
--to=rdalek1967@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