From: karl@aspodata.se
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [PATCH] 2024-01-02-separate-usr-now-requires-an-initramfs: add news item
Date: Tue, 2 Jan 2024 10:15:43 +0100 (CET) [thread overview]
Message-ID: <20240102091543.7EA08863780A@turkos.aspodata.se> (raw)
In-Reply-To: <20240102041018.585420-1-eschwartz93@gmail.com>
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.
Regards,
/Karl Hammar
-----------------------------------------------------------------------
Aspö Data
Lilla Aspö 148
S-742 94 Östhammar
Sweden
next prev parent reply other threads:[~2024-01-02 9:15 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 [this message]
2024-01-02 9:41 ` Arsen Arsenović
2024-01-02 19:26 ` karl
2024-01-02 12:53 ` Eli Schwartz
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=20240102091543.7EA08863780A@turkos.aspodata.se \
--to=karl@aspodata.se \
--cc=gentoo-dev@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