9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "David Arroyo" <david@arroyo.cc>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] Re: Solo factotum (was: Enterable namespaces: /proc/pid/$ns/srv)
Date: Tue, 30 Dec 2025 04:18:14 -0500	[thread overview]
Message-ID: <afcf8604-6989-4ee7-ac3b-6d4484a3f1e3@app.fastmail.com> (raw)
In-Reply-To: <d52fe5f0399a38c73267c4f4a3d77f4f@boddie.org.uk>

On Mon, Dec 29, 2025, at 19:46, David Boddie wrote:
> I would make it a USB serial device to start with and test that you
> can send and receive data reliably, then implement something that
> sends and receives 9P messages over that connection.

As a proof-of-concept, I ran an instance of u9fs on my laptop:

        s6-ipcserver -v /tmp/u9fs.sock u9fs -n -a none -D -l /dev/stderr -u $USER /

then I started a 9front VM with QEMU, with the following flags:

        -chardev socket,path=/tmp/u9fs.sock,id=u9fs
        -device qemu-xhci
        -device usb-serial,chardev=u9fs,id=usb-solo1,always-plugged=true

I was able to mount the serial device directly from the 9front VM:

        cpu% mount /shr/usb/eiaU1dd73 /n/u9fs
        cpu% ls /n/u9fs | sed 5q
        /n/u9fs/.lastweek
        /n/u9fs/acpid.log
        /n/u9fs/bin
        /n/u9fs/boot
        /n/u9fs/dev

So 9front should not require any changes. I expect to get the device
some time next week, I'll report back then.

David

------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/Te5078cfc0acc3fdf-Mfbc2dfc4e0b8b21f9f3c8c43
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

      reply	other threads:[~2025-12-30 13:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-30  0:46 [9fans] Re: Solo factotum (was: Enterable namespaces: /proc/pid/$ns/srv) David Boddie
2025-12-30  9:18 ` David Arroyo [this message]

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=afcf8604-6989-4ee7-ac3b-6d4484a3f1e3@app.fastmail.com \
    --to=david@arroyo.cc \
    --cc=9fans@9fans.net \
    /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;
as well as URLs for NNTP newsgroup(s).