9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Lucio De Re <lucio.dere@gmail.com>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] Creating alternative network directories
Date: Fri, 7 Oct 2022 05:08:26 +0200	[thread overview]
Message-ID: <CAJQ9t7inw+UY_5w5JhNkCxhhQKnGAoWqi_5wV4gnQFFOrod7Tg@mail.gmail.com> (raw)
In-Reply-To: <CAJQ9t7houov6mfsZFzTu+qBoLXVcvpNHsPaLiBh5uG1ZNNxd9A@mail.gmail.com>

On 10/7/22, Lucio De Re <lucio.dere@gmail.com> wrote:
> #l and #l0 are identical, the latter is the software (for want of a
> better term) instance of the latter, #1 is the second and #2 is the
> third.
>
> If you read the man page carefully - and I'm answering this not out of
>  experience, but because I presume you want to at least try a
> suggestion and go from there - you'll see that you may need to
> describe each net adapter in the plan9.ini file. If you read the
> /dev/kmesg file, you ought to find mention of #l0, #l1 and #l2 in it,
> if the adapters are recognise.
>
> (Careful now, I'm still drinking my first coffee of the day - but
> everything you need is in the man pages.)
>
> Lucio.
>
> On 10/7/22, Thorn Avery <ta@p7.co.nz> wrote:
>> 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):
>> #!/bin/rc
>> NETPATH=/usr/glenda/
>> 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!
>
>
> --
> Lucio De Re
> 2 Piet Retief St
> Kestell (Eastern Free State)
> 9860 South Africa
>
> Ph.: +27 58 653 1433
> Cell: +27 83 251 5824
>


-- 
Lucio De Re
2 Piet Retief St
Kestell (Eastern Free State)
9860 South Africa

Ph.: +27 58 653 1433
Cell: +27 83 251 5824

------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/Tc515db30bf944ee3-M9480d8049ff35448494c4a00
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

      reply	other threads:[~2022-10-07  3:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-07  2:46 Thorn Avery
2022-10-07  3:08 ` Lucio De Re
2022-10-07  3:08   ` Lucio De Re [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=CAJQ9t7inw+UY_5w5JhNkCxhhQKnGAoWqi_5wV4gnQFFOrod7Tg@mail.gmail.com \
    --to=lucio.dere@gmail.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).