public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Eli Schwartz <eschwartz93@gmail.com>
To: gentoo-dev@lists.gentoo.org, pr@gentoo.org
Cc: sam@gentoo.org
Subject: [gentoo-dev] [PATCH] 2024-01-02-separate-usr-now-requires-an-initramfs: add news item
Date: Mon,  1 Jan 2024 23:10:05 -0500	[thread overview]
Message-ID: <20240102041018.585420-1-eschwartz93@gmail.com> (raw)

Revival of commit a79dd69b0cca439bc0c483c9193c79e0554819d0.

Bug: https://bugs.gentoo.org/868306#c10
Bug: https://bugs.gentoo.org/902829
Bug: https://bugs.gentoo.org/915379
Bug: https://bugs.gentoo.org/825078
Signed-off-by: Eli Schwartz <eschwartz93@gmail.com>
---
 ...separate-usr-now-requires-an-initramfs.txt | 47 +++++++++++++++++++
 1 file changed, 47 insertions(+)
 create mode 100644 2024-01-02-separate-usr-now-requires-an-initramfs/2024-01-02-separate-usr-now-requires-an-initramfs.txt

diff --git a/2024-01-02-separate-usr-now-requires-an-initramfs/2024-01-02-separate-usr-now-requires-an-initramfs.txt b/2024-01-02-separate-usr-now-requires-an-initramfs/2024-01-02-separate-usr-now-requires-an-initramfs.txt
new file mode 100644
index 0000000..bfcbd87
--- /dev/null
+++ b/2024-01-02-separate-usr-now-requires-an-initramfs/2024-01-02-separate-usr-now-requires-an-initramfs.txt
@@ -0,0 +1,47 @@
+Title: Separate /usr now requires an initramfs
+Author: Eli Schwartz <eschwartz93@gmail.com>
+Content-Type: text/plain
+Posted: 2024-01-02
+Revision: 1
+News-Item-Format: 2.0
+Display-If-Installed: sys-apps/baselayout[split-usr]
+
+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.
+
+Historically, Gentoo has tried to make the separate filesystems use case work
+anyway. Despite all our efforts, it is broken and continues to get more broken
+under various configurations. The only workable solution is to support
+separate /usr but only when an initramfs is present. For more details on why
+this is broken, see:
+
+- https://bugs.gentoo.org/868306#c10
+- https://bugs.gentoo.org/902829
+- http://freedesktop.org/wiki/Software/systemd/separate-usr-is-broken
+- https://bugs.gentoo.org/915379
+- https://github.com/trofi/nix-guix-gentoo/commit/43d84cc00af530ef912d9c98448b64d6b5282907
+- https://github.com/trofi/nix-guix-gentoo/commit/8f194519982fbfabb6b3ca84c0806b1a379b5d06
+- https://bugs.gentoo.org/825078
+
+In 2013, Gentoo policy determined that separate /usr without an initramfs was
+officially no longer supported:
+
+- https://projects.gentoo.org/qa/policy-guide/filesystem.html#pg0202
+- https://gitweb.gentoo.org/data/gentoo-news.git/tree/2013/2013-09-27-initramfs-required/2013-09-27-initramfs-required.en.txt?id=a79dd69b0cca439bc0c483c9193c79e0554819d0
+
+11 years later, the support is being withdrawn. On 2024-02-01, we plan to
+begin work on decommissioning existing workarounds and will not accept any
+more.
+
+User Action Required
+====================
+
+If you have separate /usr and are not currently using an initramfs, you have
+until 2024-02-01 to set up an initramfs. If you do not, then at some point on
+or after this date, routine system upgrades will leave your system unbootable.
+
+For details on setting up an initramfs, see:
+
+https://wiki.gentoo.org/wiki/Initramfs/Guide
-- 
2.41.0



             reply	other threads:[~2024-01-02  4:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-02  4:10 Eli Schwartz [this message]
2024-01-02  8:22 ` [gentoo-dev] [PATCH] 2024-01-02-separate-usr-now-requires-an-initramfs: add news item 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
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=20240102041018.585420-1-eschwartz93@gmail.com \
    --to=eschwartz93@gmail.com \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=pr@gentoo.org \
    --cc=sam@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