From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <8ccc8ba40805061311w692c6e30p63eacb4ccf5605c2@mail.gmail.com> Date: Tue, 6 May 2008 22:11:03 +0200 From: "Francisco J Ballesteros" To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net> In-Reply-To: <811359db30f90fa2a0f86b7edbf68d1c@9srv.net> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <811359db30f90fa2a0f86b7edbf68d1c@9srv.net> Subject: Re: [9fans] fs(3) not bound at boot Topicbox-Message-UUID: a0340f54-ead3-11e9-9d60-3106f5b1d025 did you write the config? On Tue, May 6, 2008 at 9:01 PM, 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. > >