Commit Graph

6 Commits

Author SHA1 Message Date
apb b80ac66c04 Don't try to fsck root device if "/" is not mentioned in fstab.
Also don't assume that all network mounts are "nfs".
2011-09-20 12:13:21 +00:00
bad 712189440d Treat empty or missing fs_passno field like it has a value of 0 as fstab(5)
specifies.
Related to PR misc/43905 but does not fix the underlying issues.
2010-09-25 15:10:14 +00:00
mrg c291955dfd only fsck / if we find it in /etc/fstab. diskless systems don't need
a / entry.

XXX: still get an error from "mount /" in etc/rc.d/root itself.
2010-02-16 02:46:02 +00:00
christos 87fc4e29f5 1. centralize the fsck error handling
2. don't check if root is on nfs
3. reboot -n if root was modified as the manual page suggests
2009-07-10 20:02:21 +00:00
apb 49e8137612 Do nothing if root file system has fs_passno=0 in /etc/fstab.
(It might be better to change fsck(8) so that "fsck -p" always checks
fs_passno, whether or not file systems are specified on the command
line.)
2009-04-28 13:08:51 +00:00
joerg e7f29a3386 Split fsck during boot into two phases. Check the root file system
first, mount root and run the various disk providers. Add swap and
check the remaining file systems after that.
This breaks the dependency cycle for lvm, which needs writeable /dev.
Depend on rndctl in cgd.
2009-04-21 16:08:57 +00:00