public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ian Zimmerman <itz@very.loosely.org>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: USE flag 'split-usr' is now global
Date: Tue, 6 Aug 2019 16:39:08 -0700	[thread overview]
Message-ID: <20190806233908.4hofcmthqkxgddg3@matica.foolinux.mooo.com> (raw)
In-Reply-To: <CAGfcS_muZwPT478iATyWp7TYixk3eTzz=C0B25eAQDyy7xk5aA@mail.gmail.com>

On 2019-08-06 12:28, Rich Freeman wrote:

> > Arguing against this trivial (and IMHO, elegant) solution is tilting
> > at windmills. Specially if it is for ideological reasons instead of
> > technical ones.

> Some of the solutions I've seen tossed out in this thread are more
> complex than just building your own initramfs from scratch.
> 
> An initramfs is just a userspace bootloader that runs on top of linux.
> Nobody has any problem with conventional bootloaders, and if you want
> to do anything with one of those you have to muck around in low-level
> C or assembly.

There is a difference, and that difference is the reason I dislike
initramfs, not one of the other possible reasons you hypothesize.  The
difference is that real Unix processes (not just kernel threads and not
just PID 1) survive from the initramfs stage into the "real Unix"
stage.  It's like being able to trace matter back before the Big Bang.

-- 
Please don't Cc: me privately on mailing lists and Usenet,
if you also post the followup to the list or newsgroup.
To reply privately _only_ on Usenet and on broken lists
which rewrite From, fetch the TXT record for no-use.mooo.com.


  reply	other threads:[~2019-08-06 23:39 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
2019-08-06 16:28                   ` Rich Freeman
2019-08-06 23:39                     ` Ian Zimmerman [this message]
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=20190806233908.4hofcmthqkxgddg3@matica.foolinux.mooo.com \
    --to=itz@very.loosely.org \
    --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