From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <20030306215848.25459.qmail@mail.dirac.net> To: 9fans@cse.psu.edu From: Keith Nash Subject: [9fans] bind, ns weirdness Date: Thu, 6 Mar 2003 21:58:48 +0000 Topicbox-Message-UUID: 7bc358ee-eacb-11e9-9e20-41e7f4b1d025 If, on my 4th Edition terminal, I run unmount / then the binds bind / / bind -a /root / mount -a '#s/boot' / get removed from the output of ns, as expected; the command ls -l / shows that, indeed, the directories originally bound from the kfs disk /root are no longer there: only the files from '#/' are present. There are two strange outcomes, which are probably related: (1) 'man 1 ns' describes the output of ns as a script that could, in principle, recreate the name space. The commands bind /386/bin /bin bind -a /rc/bin /bin are still in the output from ns. But /386 and /rc no longer exist; more importantly, /386 and /rc do not exist at the stage in the script when these binds would be run. (2) ls and other commands in /bin that came from /386/bin can still be executed, although the bind that provides them is now nonsense; and ls -l /bin reports that the files from /386/bin and /rc/bin are still there - although only the former can be executed. This situation persists even if I also unmount /root; but if I unmount /bin, the commands all disappear, as expected. I have tried removing the -C flag from mount -aC #s/boot /root $rootspec in /lib/namespace, and rebooting, in case caching is having unexpected results. This has no effect. I would be grateful for any explanations! Keith.