* unmounting
@ 1996-11-21 11:41 miller
0 siblings, 0 replies; 2+ messages in thread
From: miller @ 1996-11-21 11:41 UTC (permalink / raw)
A clue to the reason why
bind -a '#|' /net
unmount '#|' /net
gives the result
unmount: not in union
can be found by performing the experiment
ls -qd '#c'; ls -qd '#c'; ls -qd '#|'; ls -qd '#|'
which gives the result
80000000 0 .
80000000 0 .
80002e00 0 pipe
80002e40 0 pipe
Note that the qid (which uniquely identifies a file on a given server)
is consistent for the console device, but different each time for the
pipe device. Each reference to '#|' is creating a new pipe, which
is why the unmount doesn't work -- the '#|' in the unmount command
refers to a different file from the '#|' in the mount command.
-- Richard Miller
^ permalink raw reply [flat|nested] 2+ messages in thread
* unmounting
@ 1996-11-21 9:00 Nigel
0 siblings, 0 replies; 2+ messages in thread
From: Nigel @ 1996-11-21 9:00 UTC (permalink / raw)
My reading of the bind(1) page suggests that
bind -a '#|' /net
unmount '#|' /net
ought to bind a pipe into /net, and then remove it. Unfortunately,
the error is
unmount: not in union
Any elucidations gratefully received.
Nigel Roles
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~1996-11-21 11:41 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
1996-11-21 11:41 unmounting miller
-- strict thread matches above, loose matches on Subject: below --
1996-11-21 9:00 unmounting Nigel
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).