From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <599f06db0709260129j39ab7cbake0b1ff5b4676daac@mail.gmail.com>
Date: Wed, 26 Sep 2007 10:29:14 +0200
From: "Gorka Guardiola" <paurea@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] bind and namespace
In-Reply-To: <10b109140709260056s6b055d5bqf054d74005edec6c@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <10b109140709252332j10c66f7bx2db455cf9224c73f@mail.gmail.com>
	<599f06db0709252355q43334f74u344f78d60b1a4f50@mail.gmail.com>
	<10b109140709260056s6b055d5bqf054d74005edec6c@mail.gmail.com>
Topicbox-Message-UUID: c3d9451a-ead2-11e9-9d60-3106f5b1d025

On 9/26/07, Antonin Vecera <antonin.vecera@gmail.com> wrote:
> Why 1 bind command adds 2! lines with bind command to my namespace?
> Why is added "bind /sys/man/4 /sys/man/4" to namespace?
> Why is one dir mounted to itself?
>

say you run:

bind -a /bla /tiki

This means "add an entry in the table under /tiki after what already exists=
".
If this is the first entry you have for /tiki, after doesn=B4t make
sense, you need
something already there. Hence, another entry binding /tiki in /tiki is add=
ed
before yours.


--=20
- curiosity sKilled the cat