From: Yaroslav <yarikos@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] namec() dislikes #M - why?
Date: Tue, 4 Oct 2011 22:59:37 +0300 [thread overview]
Message-ID: <CAG3N4d_2OYYmW5TscQJfr+Yd64=W8wweMi7k4eiiCarhPLzJJw@mail.gmail.com> (raw)
In-Reply-To: <CAOw7k5jGqiOedqud+SGJzq2Gv-r7gWsp1s_k++uc9Lt4iFEzMQ@mail.gmail.com>
Perhaps, Steve wants rio-simulated /dev/cons.
Steve, doesn't mount -b $wsys /dev in the new ns do the trick?
2011/10/4 Charles Forsyth <charles.forsyth@gmail.com>:
> #M, but devcons? devcons is #c
>
> On 4 October 2011 14:34, Steve Simon <steve@quintile.net> wrote:
>>
>> then build a new one including some bits of devcons.
>
> ...
>>
>> Also, why is this done here and not in fsattach() of devcons
>> (with a refcount)?
--
- Yaroslav
next prev parent reply other threads:[~2011-10-04 19:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-04 13:34 Steve Simon
2011-10-04 13:43 ` Russ Cox
2011-10-04 13:54 ` Charles Forsyth
2011-10-04 19:59 ` Yaroslav [this message]
2011-10-06 21:06 ` Steve Simon
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='CAG3N4d_2OYYmW5TscQJfr+Yd64=W8wweMi7k4eiiCarhPLzJJw@mail.gmail.com' \
--to=yarikos@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).