9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Thorn Avery <ta@p7.co.nz>
To: 9fans@9fans.net
Subject: [9fans] Creating alternative network directories
Date: Fri, 07 Oct 2022 13:46:05 +1100	[thread overview]
Message-ID: <D746E9C0-A071-4ECA-9288-EBDD7296AA99@p7.co.nz> (raw)

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

Hello all!

I recently got a NIC for my tower, and I've been trying to no avail to mount the devices as /net is.

I have the following devices:
#l and #I, the motherboards inbuilt port
#l0 and #I0, with #l0/ether0
#l1 and #I1, with #l1/ether1

My goal is to end up with /net.alt.0 and /net.alt.1, which i then intend to bind over /net as needed.

I currently have the following in /rc/bin/cpurc.local (im creating in usr directory while tinkering):
for(n in 0 1)
    if(! test -e $NETPATH^net.alt.$n)
        mkdir $NETPATH^net.alt.$n
    bind -a '#l'^$n $NETPATH^net.alt.$n
    bind -a '#I'^$n $NETPATH^net.alt.$n
    mount -a /srv/cs $NETPATH^net.alt.$n
    mount -a /srv/dns $NETPATH^net.alt.$n
rm /env/NETPATH

which is what I saw in my namespaces file was being done for /net

after this, ip/ipconfig returns "no success with DHCP", whether i supply the details or not.

My questions are:
1: what are the important steps that go into creating a network stacks directory?
2: is the way Im doing so the correct course, or is there a best practice i should be following instead?

Thank you :) This is my first time on the mailing list so please be kind!
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/Tc515db30bf944ee3-M54e602d1b4fd45f1690b4687
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

[-- Attachment #2: Type: text/html, Size: 2083 bytes --]

             reply	other threads:[~2022-10-07  2:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-07  2:46 Thorn Avery [this message]
2022-10-07  3:08 ` Lucio De Re
2022-10-07  3:08   ` Lucio De Re

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=D746E9C0-A071-4ECA-9288-EBDD7296AA99@p7.co.nz \
    --to=ta@p7.co.nz \
    --cc=9fans@9fans.net \


* 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).