From: Eli Schwartz <eschwartz93@gmail.com>
To: gentoo-dev@lists.gentoo.org, karl@aspodata.se
Subject: Re: [gentoo-dev] [PATCH] 2024-01-02-separate-usr-now-requires-an-initramfs: add news item
Date: Tue, 2 Jan 2024 07:53:09 -0500 [thread overview]
Message-ID: <5e329eab-3156-4602-a973-d89a9365706f@gmail.com> (raw)
In-Reply-To: <20240102091543.7EA08863780A@turkos.aspodata.se>
[-- Attachment #1.1.1: Type: text/plain, Size: 1637 bytes --]
On 1/2/24 4:15 AM, karl@aspodata.se wrote:
> Eli Schwartz:
> [...]
>> +Systems which have /usr and / on separate filesystems have always required a
>> +dedicated initramfs to bring up both partitions. Systems where both /usr and /
>> +are on the same filesystem may use an initramfs if they wish, or choose not
>> +to.
> [...]
>
> Well, that is not technically correct, just have the required kernel
> drivers (eg. AHCI and ext2/4) compiled in and use the same busybox
> commands as in the initrd, but placed in /, to bring up the system
> to the point that /usr is mounted.
>
> I have a static dev, compiled in drivers, busybox init and mount, and
> separate / and /usr on a box here, works perfectly well.
> Soo, add a clause about what gentoo supports out of the box and that
> you can make it work if you wish.
> If there is a general wish I can write an article about how to make
> it work.
You need the required kernel drivers regardless of having /usr on a
separate partition.
The problem here is solely about after the kernel has booted, mounted
the / filesystem, and run init -- init needs to fully bring the system
up. While it's no doubt possible to do this with finely-crafted busybox
usage, there's a lot of ways it could break if you aren't *very*
careful, and that should not require ongoing support.
It's firmly in the "you break it, you bought it" category. But I have no
objection if it's mentioned on the wiki in the initramfs article or
somewhere similar.
I don't think this is a blocker for dropping hacks like
usr-ldscript.eclass usage, though.
--
Eli Schwartz
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 18399 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-01-02 12:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-02 4:10 [gentoo-dev] [PATCH] 2024-01-02-separate-usr-now-requires-an-initramfs: add news item Eli Schwartz
2024-01-02 8:22 ` Ulrich Mueller
2024-01-02 8:30 ` Ulrich Mueller
2024-01-02 8:32 ` Sam James
2024-01-02 12:47 ` Eli Schwartz
2024-01-02 9:15 ` karl
2024-01-02 9:41 ` Arsen Arsenović
2024-01-02 19:26 ` karl
2024-01-02 12:53 ` Eli Schwartz [this message]
2024-01-02 13:28 ` Peter Böhm
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=5e329eab-3156-4602-a973-d89a9365706f@gmail.com \
--to=eschwartz93@gmail.com \
--cc=gentoo-dev@lists.gentoo.org \
--cc=karl@aspodata.se \
/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