Ben Hutchings wrote:
> It not only inhibits umount from updating /etc/mtab, but also means that
> it never uses /etc/mtab to canonicalize the given path.
That seems very doubtful. Especially since I tried applying your patch and
pbuilder --create still fails:
I: mounting /proc filesystem
mount: /proc already mounted or /var/cache/pbuilder/build//3625/proc busy
mount: according to mtab, /proc is mounted on /proc
As well, when I try -n by hand, it doesn't help:
joey@gnu:~/tmp>mkdir proc
joey@gnu:~/tmp>sudo mount -n -t proc proc proc
joey@gnu:~/tmp>sudo umount -n `pwd`/proc
umount: /proc: device is busy.
(In some cases useful info about processes that use
the device is found by lsof(8) or fuser(1))
It seems to only get confused when the cwd is the parent of the mount point.
joey@gnu:~/tmp>cd ..
joey@gnu:~>sudo umount `pwd`/proc
joey@gnu:~>
> > Also, portability is a concern. busybox umount does not support -n,
> > for example.
> >
> > When I run debootstrap, it ends successfully with $chroot/proc not being
> > mounted. Is there something about it being run by pbuilder that triggers
> > this bug?
>
> Don't know.
pbuilder runs "debootstrap ." --- so the bug could actually be worked
around by doing a cd / before umount.
--
see shy jo
Attachment:
signature.asc
Description: Digital signature