summaryrefslogtreecommitdiffstats
path: root/crypto/README
diff options
context:
space:
mode:
authorgreen <green@FreeBSD.org>1999-10-17 16:26:58 +0000
committergreen <green@FreeBSD.org>1999-10-17 16:26:58 +0000
commitfea15770edcdff7ce933973243e21a3cde03c773 (patch)
treecbcad7ca365948dc2181af18311692c2602d9e66 /crypto/README
parent0054e68b0112e09023c8f744c1afc2fffeaee597 (diff)
downloadFreeBSD-src-fea15770edcdff7ce933973243e21a3cde03c773.zip
FreeBSD-src-fea15770edcdff7ce933973243e21a3cde03c773.tar.gz
quoting << Martin_Blapp
- Completly changed the internals of umount(8). We do three checks now to see if 'argv' is in the mounttable. It they all fail, we return to main and print a warning. - fixed the umount mount-order. The checks are rather complex to do this. Cause umount(8) should also be able to unmount several devices at once ('umount -a', 'umount -A', 'umount /mnt /mnt2'), the mount-order get's important. I added checks to mark and unmark already unmounted devices. - Various fixes with nfs-unmounts (no rpc-calls were done, or they were done although there was an existing mount). Since we allow overlay-mounts, we should also handle them properly. - Translate the deprecated nfs-syntax with '@' to ':' like mount_nfs does. The ':' syntax has now precedence, but '@' still works. - 'umount -v' is now fixed for all cases and doesn't print garbage like two times the mountpoint etc. - removed non documented and useless umount '-F'. - hanged nfsmounts can now unmounted 'without' any problems. I've removed stat() and realpath() checks on the mountpoint. Instead we just do a realpath() on the basedir of the mountpath and add the dirname again. Implemented this as an idea from phk. But there are still vfs-restrictions if the nfs_mount is busy. If there are unwritten metadata on a hanged nfs-mount, and we modify nfs_vfsops.c to not return EBUSY, we get a deadlock :( The problem has now moved from userland to kernel. - removed the BUGS part from the umount(8) manpage. - Converted it to ANSI C (more than 60% of the code have changed). Martin_Blapp Fixed PR's ---------- o [1999/02/03] bin/9893 NFS umount of regular file impossible s [1995/11/27] bin/841 stale nfs mounts cannot be umounted o [1999/08/01] bin/12911 alfred NFS umounts are not properly done if just the mountpoint gets umounted Only partially solved: ---------------------- The problem is now in kernel: o [1999/04/07] bin/11005 `umount -f' does not work if the NFS-server is down. PR: bin/9893 bin/841 bin/12911 bin/11005 Submitted by: Martin Blapp <mb@imp.ch>
Diffstat (limited to 'crypto/README')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud