patches and low-level development discussion
 help / color / mirror / code / Atom feed
From: Demi Marie Obenour <demiobenour@gmail.com>
To: Alyssa Ross <hi@alyssa.is>,
	Spectrum OS Development <devel@spectrum-os.org>
Subject: Re: [PATCH 1/3] host/initramfs: Use util-linux switch_root
Date: Thu, 18 Sep 2025 15:41:05 -0400	[thread overview]
Message-ID: <4dafb64b-7ded-4eb3-a8fb-1fd7224f11a3@gmail.com> (raw)
In-Reply-To: <87seglxq0g.fsf@alyssa.is>


[-- Attachment #1.1.1: Type: text/plain, Size: 989 bytes --]

On 9/17/25 07:44, Alyssa Ross wrote:
> Demi Marie Obenour <demiobenour@gmail.com> writes:
> 
>> Busybox switch_root doesn't move /proc, /dev, and /sys mounts, whereas
>> the switch_root from util-linux does.
>>
>> Signed-off-by: Demi Marie Obenour <demiobenour@gmail.com>
>> ---
>>  host/initramfs/default.nix | 3 ++-
>>  host/initramfs/etc/init    | 4 ----
>>  2 files changed, 2 insertions(+), 5 deletions(-)
> 
> So on the whole, I'm in favour of getting rid of Busybox wherever
> possible, because its implementations tend to be bad.  In the case of
> initramfs though, the potential for unexpected circumstances is very
> constrained, and we need something to implement mkfifo, head, kill, and
> rm.  So given we're using Busybox for that anyway, we might as well use
> Busybox's smaller implementation of switch_root, right?

I think so, unless we care about eliminating calls to /usr/bin/if and
/usr/bin/mount.
-- 
Sincerely,
Demi Marie Obenour (she/her/hers)

[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 7253 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2025-09-18 19:41 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-15  0:18 [PATCH 0/3] Minor improvements to the Spectrum OS boot process Demi Marie Obenour
2025-09-15  0:18 ` [PATCH 1/3] host/initramfs: Use util-linux switch_root Demi Marie Obenour
2025-09-17 11:44   ` Alyssa Ross
2025-09-18  2:39     ` Demi Marie Obenour
2025-09-19  9:12       ` Alyssa Ross
2025-09-18 19:41     ` Demi Marie Obenour [this message]
2025-09-15  0:18 ` [PATCH 2/3] Add /dev/fd and /dev/std* Demi Marie Obenour
2025-09-17 11:29   ` Alyssa Ross
2025-09-15  0:19 ` [PATCH 3/3] host/rootfs: Avoid redundant mounts of /proc and /sys Demi Marie Obenour
2025-09-17 11:31   ` Alyssa Ross
2025-09-18  2:42     ` Demi Marie Obenour
2025-09-19  9:16       ` Alyssa Ross
2025-09-18 19:45 ` [PATCH v2] Add /dev/fd and /dev/std* Demi Marie Obenour
2025-09-19  9:29   ` Alyssa Ross

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=4dafb64b-7ded-4eb3-a8fb-1fd7224f11a3@gmail.com \
    --to=demiobenour@gmail.com \
    --cc=devel@spectrum-os.org \
    --cc=hi@alyssa.is \
    /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.
Code repositories for project(s) associated with this public inbox

	https://spectrum-os.org/git/crosvm
	https://spectrum-os.org/git/doc
	https://spectrum-os.org/git/mktuntap
	https://spectrum-os.org/git/nixpkgs
	https://spectrum-os.org/git/spectrum
	https://spectrum-os.org/git/ucspi-vsock
	https://spectrum-os.org/git/www

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).