Searched hist:d7fb353a4328df9c8f3d2b4735313e36f794538e (Results 1 – 1 of 1) sorted by relevance
| /freebsd/share/man/man5/ |
| H A D | rc.conf.5 | diff d7fb353a4328df9c8f3d2b4735313e36f794538e Thu Dec 27 14:41:27 CET 2001 Sheldon Hearn <sheldonh@FreeBSD.org> Re-introduce the fix that delays mounting of network filesystems until
the network is initialized. This was first implemented in rev 1.268
of src/etc/rc, but was backed out at wollman's request.
The objection was that the right place for the fix is in mount(8).
Having looked at that problem, I find it hard to believe that
the hoops one would have to jump through can be justified by the
desire for purity alone.
Note that there are reported issues surrounding nfsclient kernel
support and mount_nfs(8), which currently make NFS an ugly exception
to the general case.
With this change, systems with non-NFS network filesystems configured
for mounting on startup in /etc/fstab are no longer guaranteed to
fail on startup.
diff d7fb353a4328df9c8f3d2b4735313e36f794538e Thu Dec 27 14:41:27 CET 2001 Sheldon Hearn <sheldonh@FreeBSD.org> Re-introduce the fix that delays mounting of network filesystems until
the network is initialized. This was first implemented in rev 1.268
of src/etc/rc, but was backed out at wollman's request.
The objection was that the right place for the fix is in mount(8).
Having looked at that problem, I find it hard to believe that
the hoops one would have to jump through can be justified by the
desire for purity alone.
Note that there are reported issues surrounding nfsclient kernel
support and mount_nfs(8), which currently make NFS an ugly exception
to the general case.
With this change, systems with non-NFS network filesystems configured
for mounting on startup in /etc/fstab are no longer guaranteed to
fail on startup.
|