9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Richard Miller <9fans@hamnavoe.com>
To: 9fans@9fans.net
Subject: Re: [9fans] USB3 1Gb ethernet card working on 9legacy (rpi 4)
Date: Mon, 1 Aug 2022 10:16:26 +0100	[thread overview]
Message-ID: <093ec4619e7568c054a825f5d5d8cc7f@hamnavoe.com> (raw)
In-Reply-To: <16592903190.8e7cccc4d.691312@composer.9fans.topicbox.com>

> Other programs expect the devices mounted in
> /net. I'm binding the device inside a directory in /tmp and then
> binding this directory to /net. I would appreciate if someone shares
> the correct way of doing this.

Two ideas come to mind:

% mount -a /srv/usb /net
  (then all usb devices appear in /net as well as /dev)
% aux/stub -d /net/etherU0 && bind /dev/etherU0 /net/etherU0
  (for a single alias without extra clutter)

But I think anything expecting a device in /net can be given an explicit
alternative, eg

% ip/ipconfig ether /dev/etherU0 [...params]

Are there exceptions I'm missing?

Note that we can even boot with a fileserver connection via usb ether
by passing extra ipconfig args in cmdline.txt eg
  bootargs='tcp ether /dev/etherU0'
(same thing with plan9.ini on other platforms, without the quotes)


------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T668643d11149fab4-M64be1cd32d8d81cd3dfcf1f0
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

  parent reply	other threads:[~2022-08-01  9:16 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-31 17:58 adr
2022-07-31 18:08 ` hiro
2022-07-31 18:09   ` adr
2022-07-31 21:35 ` Richard Miller
2022-08-01  9:16 ` Richard Miller [this message]
2022-08-01 16:29   ` adr
2022-08-02  8:50     ` Richard Miller
2022-08-03  0:34       ` adr
2022-08-03  3:00         ` adr
2022-08-03 10:57           ` Richard Miller
2022-08-03 18:46             ` adr
2022-08-04 10:13               ` Richard Miller
2022-08-04 11:56                 ` ori
2022-08-04 19:34                 ` adr
2022-08-05 12:14                   ` ori
2022-08-01 16:43   ` adr
2022-08-01 17:06     ` adr
2022-08-02  3:45       ` Lucio De Re
2022-08-02  9:07     ` Richard Miller
2022-08-03  0:52       ` adr
2022-08-03  1:08         ` adr
2022-08-03 12:41           ` Richard Miller
2022-08-03 18:47             ` adr

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=093ec4619e7568c054a825f5d5d8cc7f@hamnavoe.com \
    --to=9fans@hamnavoe.com \
    --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).