From: Demi Marie Obenour <demiobenour@gmail.com>
To: Alyssa Ross <hi@alyssa.is>,
Spectrum OS Development <devel@spectrum-os.org>
Subject: Re: [PATCH] host/rootfs: add /dev/fd and /dev/std*
Date: Fri, 8 Aug 2025 14:06:29 -0400 [thread overview]
Message-ID: <c133dee0-fc4c-4101-93db-d4fb19eb67c6@gmail.com> (raw)
In-Reply-To: <87wm7d4rnz.fsf@alyssa.is>
[-- Attachment #1.1.1: Type: text/plain, Size: 895 bytes --]
On 8/8/25 14:03, Alyssa Ross wrote:
> Demi Marie Obenour <demiobenour@gmail.com> writes:
>
>> This is the same as 14483e1a690c (img/app: add /dev/fd and /dev/std*),
>> but for the host.
>>
>> Signed-off-by: Demi Marie Obenour <demiobenour@gmail.com>
>> ---
>> host/rootfs/etc/s6-linux-init/scripts/rc.init | 5 +++++
>> 1 file changed, 5 insertions(+)
>
> Hmm. I did it only for img/app on purpose, because that's the only
> place we run arbitrary executables. In host/rootfs (and vm/sys/net),
> we only run a limited set of code that we control. WDYT?
We control the code to some degree, but third-party dependencies might
depend on these files existing, and failures due to these being
missing could be extremely difficult to debug. In particular,
portable code might use /dev/fd intentionally, as the BSDs have it.
--
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 --]
next prev parent reply other threads:[~2025-08-08 18:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-07 16:54 [PATCH] host/rootfs: add /dev/fd and /dev/std* Demi Marie Obenour
2025-08-08 18:03 ` Alyssa Ross
2025-08-08 18:06 ` Demi Marie Obenour [this message]
2025-08-31 11:06 ` 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=c133dee0-fc4c-4101-93db-d4fb19eb67c6@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).