From: "Canek Peláez Valdés" <caneko@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: USE flag 'split-usr' is now global
Date: Tue, 6 Aug 2019 10:54:46 -0500 [thread overview]
Message-ID: <CADPrc81Ctzsr=Ce3ZLXgefe8xq1ZauUSVU757YUViLKdfJkA7A@mail.gmail.com> (raw)
In-Reply-To: <7264cb95-6c1f-560b-e04e-2b9303e1485e@spamtrap.tnetconsulting.net>
[-- Attachment #1: Type: text/plain, Size: 1552 bytes --]
On Mon, Aug 5, 2019 at 9:38 PM Grant Taylor <
gtaylor@gentoo.tnetconsulting.net> wrote:
[...]
> I don't have any current first hand experience with /usr being a
> separate file system without using an initramfs / initrd. So I'm going
> to have to take what you, and others, say on faith that it can't
> /currently/ be done. But I've got to say, that I find that idea
> disturbing and highly suspicious.
If it's computable it can be done, of course. Therefore it can be done,
currently. I don't think nobody has said it absolutely cannot be done.
The thing is:
1. How much work implies to get it done.
2. Who is gonna do said work.
The answer to 1 is "a lot", since (as someone mentioned in the thread) it
involves changing not only the init (nevermind systemd; *ALL* init
systems), but all applications that may require to use binaries in /usr
before it's mounted.
The answer to 2 is, effectively, "nobody", since it requires a big
coordinated effort, stepping into the toes of several projects,
significantly augmenting their code complexity for a corner case[1] that
can be trivially be solved with an initramfs, which it just works.
Arguing against this trivial (and IMHO, elegant) solution is tilting at
windmills. Specially if it is for ideological reasons instead of technical
ones.
Regards.
[1] I firmly believe that's the situation nowadays.
--
Dr. Canek Peláez Valdés
Profesor de Carrera Asociado C
Departamento de Matemáticas
Facultad de Ciencias
Universidad Nacional Autónoma de México
[-- Attachment #2: Type: text/html, Size: 1917 bytes --]
next prev parent reply other threads:[~2019-08-06 15:55 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-04 10:23 [gentoo-user] USE flag 'split-usr' is now global Kai Peter
2019-08-04 11:29 ` Mick
2019-08-04 17:07 ` [gentoo-user] " Ian Zimmerman
2019-08-04 18:01 ` Dale
2019-08-05 8:05 ` Kai Peter
2019-08-04 18:03 ` Mick
2019-08-05 1:26 ` Grant Taylor
2019-08-05 10:49 ` Mick
2019-08-05 16:17 ` Grant Taylor
2019-08-05 23:34 ` Mick
2019-08-06 2:37 ` Grant Taylor
2019-08-06 15:54 ` Canek Peláez Valdés [this message]
2019-08-06 16:28 ` Rich Freeman
2019-08-06 23:39 ` Ian Zimmerman
2019-08-07 0:14 ` Rich Freeman
2019-08-06 23:41 ` Grant Taylor
2019-08-07 0:31 ` Rich Freeman
2019-08-07 10:11 ` Mick
2019-08-08 3:56 ` Grant Taylor
2019-08-06 22:54 ` Grant Taylor
2019-08-06 23:05 ` Canek Peláez Valdés
2019-08-07 10:48 ` Neil Bothwick
2019-08-07 10:58 ` Mick
2019-08-07 11:48 ` Neil Bothwick
2019-08-07 13:24 ` Mick
2019-08-08 7:43 ` Neil Bothwick
2019-08-08 9:53 ` Kai Peter
2019-08-06 0:06 ` Ian Zimmerman
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='CADPrc81Ctzsr=Ce3ZLXgefe8xq1ZauUSVU757YUViLKdfJkA7A@mail.gmail.com' \
--to=caneko@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