From: "Devon H. O'Dell" <devon.odell@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net>,
"Russ Cox" <rsc@swtch.com>
Subject: Re: Help with device and clone?
Date: Thu, 18 Dec 2008 12:17:43 -0500 [thread overview]
Message-ID: <9ab217670812180917j7230c2bbt76c426c314fa19df@mail.gmail.com> (raw)
In-Reply-To: <9ab217670812172149j3f949775u747fbf0725da46cb@mail.gmail.com>
Hey all,
So the problem turned out to be that somehow, when ethermediumlink()
is called, its view of the namespace doesn't include /net as a
separate mount. So I figured the devroot reset routine was getting
called somehow after all the ip stuff attached. I reordered stuff to
attempt to guarantee this wasn't the case, but didn't have much luck
with that either. However, manually changing all the chandial lines to
use #l/ether0 (instead of argv[2], which was /net/ether0) causes stuff
to `just work'.
Clearly my idea of what's happening in what order is kind of screwy.
I've plopped things in various orders, but the only way things are
running is if I use that hack. I see that '#l' is bound to /net in
/lib/namespace, so it's happening before rio starts (and even if
that's not where that happened; I put a bind -a '#l' /net in
/usr/glenda/lib/profile prior to rio starting and that didn't help).
Regarding the order of things:
I'm calling links() after initseg() as it is in Plan 9's main.c;
inside links(), I call ethervelink() (my virtual ethernet driver),
ethermediumlink(), netdevmediumlink() and loopbackmediumlink().
Any ideas now that the issue is a bit less arcane?
--dho
next prev parent reply other threads:[~2008-12-18 17:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-18 5:49 [9fans] " Devon H. O'Dell
2008-12-18 17:17 ` Devon H. O'Dell [this message]
2008-12-18 18:03 ` Russ Cox
2008-12-18 18:13 ` [9fans] " Devon H. O'Dell
2008-12-18 18:34 ` erik quanstrom
2008-12-18 19:12 ` Devon H. O'Dell
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=9ab217670812180917j7230c2bbt76c426c314fa19df@mail.gmail.com \
--to=devon.odell@gmail.com \
--cc=9fans@9fans.net \
--cc=rsc@swtch.com \
/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).