public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: karl@aspodata.se
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Separate /usr partition
Date: Wed, 14 Sep 2022 18:12:18 +0200 (CEST)	[thread overview]
Message-ID: <20220914161218.CB45983BDE11@turkos.aspodata.se> (raw)
In-Reply-To: <5874509.lOV4Wx5bFT@wstn>

Peter:
> 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'm using separate /usr, it was the default historically and I just
continued useing it, partly because it is unconvenient to repartion
long running remote systems.

There are a few things to look out for.
If you are not using initrd/initramfs, you need all drivers to access 
/ to be compiled in. Easiest is if don't use devices with dynamic
minors. Once / is mounted you have all drivers available
in /lib/modules, then the next possible hurdle is to survive long 
enought till /usr is mounted. For that you a suitable mount command 
which does not depend on /usr, i.e. it or any programs previous it
in the bootup cannot depend on libs in /usr. The easiest way to
accomplish that is to use busybox.

It is also possible to use sys-fs/static-dev, if you want to opt
to not use udev.

Regards,
/Karl Hammar




  reply	other threads:[~2022-09-14 16:12 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 [this message]
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
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=20220914161218.CB45983BDE11@turkos.aspodata.se \
    --to=karl@aspodata.se \
    --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