From: Adam Joseph <adam@westernsemico.com>
To: devel@spectrum-os.org
Cc: Ville Ilvonen <ville.ilvonen@unikie.com>, Alyssa Ross <hi@alyssa.is>
Subject: Re: [PATCH] Documentation: Architecture Decision Record
Date: Mon, 02 Jan 2023 23:03:43 -0800 [thread overview]
Message-ID: <167272942335.19302.1324067862019435223@localhost> (raw)
In-Reply-To: <20220708110215.92996-1-ville.ilvonen@unikie.com>
Quoting Ville Ilvonen (2022-07-08 04:02:15)
> +++ b/Documentation/decisions/006-drivers-on-host.adoc
> ...
> +## Consequences
> +No networking on the host. Responsibilities of the host are expected to get
> +smaller over time.
I know you're probably a long, long way from worrying about wifi, but when you
get to that point, I suggest taking a look at running `eiwd` in the netvm:
https://github.com/illiliti/eiwd/
https://github.com/NixOS/nixpkgs/pull/208844
- It is way more robust than wpa_supplicant.
- (unlike iwd) it does not require plumbing a dbus connection from the hostvm to
the netvm (nor all the attack surface that would entail).
- You control it by simply editing its state files, which it watches with
`inotify()`.
- It has zero runtime dependencies!
- `pkgsStatic.eiwd` builds (caveat: I have not tested it)
- You should be able to boot a VM with `init=/nix/store/...-eiwd/bin/eiwd`
and run it as PID 1 (note: I have not tried this).
I've been running this on my daily driver laptop for the last few weeks and am
extremely happy with it.
- a
next prev parent reply other threads:[~2023-01-03 7:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-08 11:02 [PATCH] Documentation: Architecture Decision Record Ville Ilvonen
2022-07-12 18:11 ` Alyssa Ross
2022-07-13 9:35 ` Ville Ilvonen
2022-07-13 9:53 ` Alyssa Ross
2022-07-13 11:04 ` Ville Ilvonen
2022-07-22 11:32 ` Alyssa Ross
2022-07-22 11:37 ` Alyssa Ross
2022-07-13 10:04 ` Alyssa Ross
2023-01-03 7:03 ` Adam Joseph [this message]
2023-01-06 13:27 ` 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=167272942335.19302.1324067862019435223@localhost \
--to=adam@westernsemico.com \
--cc=devel@spectrum-os.org \
--cc=hi@alyssa.is \
--cc=ville.ilvonen@unikie.com \
/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).