From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: References: Date: Sat, 19 Apr 2014 23:18:35 +0100 Message-ID: From: Riddler To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=001a11349f4cb868e704f76ca5d0 Subject: Re: [9fans] Missing /dev/etherX ? Topicbox-Message-UUID: da087d50-ead8-11e9-9d60-3106f5b1d025 --001a11349f4cb868e704f76ca5d0 Content-Type: text/plain; charset=UTF-8 > > there shouldn't be any /dev/etherX entries. do you mean /net/ether? I do indeed bind -a '#l1' /net > That has indeed done it, thanks! Out of curiosity, what is it that is binding the first one automatically and not the second? It that just the standard behavior, or is it perhaps a script that was generated during installation with only one bind entry? --001a11349f4cb868e704f76ca5d0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
there shouldn't be any /dev/etherX entries. = =C2=A0do you mean /net/ether?=C2=A0
I do indeed

bind -a '#l1' /net
Tha= t has indeed done it, thanks!

Out of curiosity, what is it that is binding the first one a= utomatically and not the second?
It that just the standard be= havior, or is it perhaps a script that was generated during installation wi= th only one bind entry?

--001a11349f4cb868e704f76ca5d0--