9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Christopher Nielsen" <cnielsen@pobox.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net>
Subject: Re: [9fans] fs(3) not bound at boot
Date: Tue,  6 May 2008 14:15:15 -0600	[thread overview]
Message-ID: <e0ac85f90805061315h169bab0ft6e3ab12eec5bdc0a@mail.gmail.com> (raw)
In-Reply-To: <811359db30f90fa2a0f86b7edbf68d1c@9srv.net>

Hrm. This looks familiar, and I think I had a similar problem a long
time ago when I was trying to do the same. I think I had to modify
local.c. I can't check right now, but I will later this evening. If
you haven't found a solution, I'll let you know.

On 5/6/08, a@9srv.net <a@9srv.net> wrote:
> Right, but how do you get your root file system if it's on a fs(3)
> device? It looks like it should work, with connectlocalfossil
> just a few lines after the bind in connectlocal, but that doesn't
> seem to actually work for me. init.c (and thus /cfg/*) are much
> later in the process.
> Anthony
>
>
> ---------- Forwarded message ----------
> From: geoff@plan9.bell-labs.com
> To: 9fans@9fans.net
> Date: Tue, 6 May 2008 14:13:27 -0400
> Subject: Re: [9fans] fs(3) not bound at boot
> On the machines where it matters, mostly file servers, we have
>
> bind -a '#k' /dev
>
> in /cfg/$sysname/namespace.  There's a newns() in init.c, at least.
>
>


--
Christopher Nielsen
"They who can give up essential liberty for temporary
safety, deserve neither liberty nor safety." --Benjamin Franklin



  parent reply	other threads:[~2008-05-06 20:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-06 12:03 a
2008-05-06 18:13 ` geoff
2008-05-06 19:01   ` a
2008-05-06 20:11     ` Francisco J Ballesteros
2008-05-06 20:14       ` a
2008-05-06 20:15     ` Christopher Nielsen [this message]
     [not found] <92bbc277fe295e3ecff469570b8dccb0@plan9.bell-labs.com>
2008-05-13 22:30 ` a

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=e0ac85f90805061315h169bab0ft6e3ab12eec5bdc0a@mail.gmail.com \
    --to=cnielsen@pobox.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).