Bug#344547: [Pkg-sysvinit-devel] Bug#344547: please use -f in umount

2005-12-24 Thread Robert Millan
On Fri, Dec 23, 2005 at 10:36:41PM +0100, Thomas Hood wrote:
 Robert Millan wrote:
  I think it'd be a good thing if -f was always passed to umount
 
 umount(8) says:
 
-f Force unmount (in case of an unreachable NFS system).  (Requires
   kernel 2.1.116 or later.)
 
 So the -f option has an effect on kFreeBSD too?

Yes.  Though we don't use the same mount/umount command, most basic flags are
the same.

From http://www.freebsd.org/cgi/man.cgi?query=umount

 -f  The file system is forcibly unmounted.  Active special devices
 continue to work, but all other files return errors if further
 accesses are attempted.  The root file system cannot be forcibly
 unmounted.

From  http://www.freebsd.org/cgi/man.cgi?query=mount

 -f  Forces the revocation of write access when trying to downgrade a
 file system mount status from read-write to read-only.  Also
 forces the R/W mount of an unclean file system (dangerous; use
 with caution).

-- 
Robert Millan


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#344547: [Pkg-sysvinit-devel] Bug#344547: please use -f in umount

2005-12-23 Thread Thomas Hood
Robert Millan wrote:
 I think it'd be a good thing if -f was always passed to umount

umount(8) says:

   -f Force unmount (in case of an unreachable NFS system).  (Requires
  kernel 2.1.116 or later.)

So the -f option has an effect on kFreeBSD too?

-- 
Thomas Hood


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]