Date: Sat, 19 Jul 2003 17:32:41 -0700 (PDT) From: Nate Lawson <nate@root.org> To: Ian Dowse <iedowse@FreeBSD.org> Cc: cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sbin/umount umount.c Message-ID: <20030719173209.E31036@root.org> In-Reply-To: <20030720001135.8D2CC37B497@hub.freebsd.org> References: <20030720001135.8D2CC37B497@hub.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 19 Jul 2003, Ian Dowse wrote: > Modified files: > sbin/umount umount.c > Log: > Take advantage of the use of file system IDs to simplify umount(8) > and make it work more reliably in a number of cases that have > traditionally been troublesome. The new behaviour is: > 1) If the filesystem can be determined by the fsid or device, > or uniquely identified by the mountpoint, then just go ahead > and call unmount(2) using the file system ID. > 2) Otherwise use fstatfs(2) to resolve the path into a file system > ID (checking with stat(2) that it is a filesystem root directory). > > Case 2 can potentially block if an NFS server is down, but it can > always be avoided by using an unambiguous specification. It handles > all the hard cases such as symlinks and mismatches between the mount > list and reality. For example, if a filesystem was mounted as /mnt > inside a chroot, it will show up in the mount list as /mnt, but now > you can unmount it from outside the chroot with "umount /chroot_path/mnt". > > Revision Changes Path > 1.39 +144 -298 src/sbin/umount/umount.c Excellent stuff! -Nate
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030719173209.E31036>