patches and low-level development discussion
 help / color / mirror / code / Atom feed
From: Alyssa Ross <hi@alyssa.is>
To: Demi Marie Obenour <demiobenour@gmail.com>,
	Spectrum OS Development <devel@spectrum-os.org>
Subject: Re: [PATCH 3/3] host/rootfs: Avoid redundant mounts of /proc and /sys
Date: Wed, 17 Sep 2025 13:31:02 +0200	[thread overview]
Message-ID: <87v7lhxqmh.fsf@alyssa.is> (raw)
In-Reply-To: <20250914-util-linux-switch-root-v1-3-9cf9349cbca3@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1384 bytes --]

Demi Marie Obenour <demiobenour@gmail.com> writes:

> The initramfs already mounted both of them.
>
> Signed-off-by: Demi Marie Obenour <demiobenour@gmail.com>
> ---
> It's true that this does increase the reliance on an initramfs, but it
> is also trivial to revert if Spectrum OS ever stops using one.  Linux
> supports creating dm-verity devices via dm-mod.create= and (if needed)
> dm-mod.waitfor=, so eliminating an initramfs might be possible but is a
> separate project.

I'd still prefer we don't rely on initramfs behaviour any more than we
need to — it just makes things more brittle and difficult to understand.

IIRC I tried using those kernel parameters before, but they weren't
workable for what we needed.  I don't remember the details.

> ---
>  host/rootfs/etc/fstab | 2 --
>  1 file changed, 2 deletions(-)
>
> diff --git a/host/rootfs/etc/fstab b/host/rootfs/etc/fstab
> index 6a82ecc85090a37b13603b29f74ca6e554a28c33..4d303d277409279976bc102969d902466bc39c47 100644
> --- a/host/rootfs/etc/fstab
> +++ b/host/rootfs/etc/fstab
> @@ -1,6 +1,4 @@
>  # SPDX-License-Identifier: CC0-1.0
>  # SPDX-FileCopyrightText: 2020-2021 Alyssa Ross <hi@alyssa.is>
> -proc	/proc		proc	defaults		0	0
>  devpts	/dev/pts	devpts	defaults,gid=4,mode=620	0	0
>  tmpfs	/dev/shm	tmpfs	defaults		0	0
> -sysfs	/sys		sysfs	defaults		0	0
>
> -- 
> 2.51.0

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]

  reply	other threads:[~2025-09-17 11:31 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
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 [this message]
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=87v7lhxqmh.fsf@alyssa.is \
    --to=hi@alyssa.is \
    --cc=demiobenour@gmail.com \
    --cc=devel@spectrum-os.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.
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).