summaryrefslogtreecommitdiffstats
path: root/lib/libipsec
diff options
context:
space:
mode:
authorkensmith <kensmith@FreeBSD.org>2008-01-22 16:35:10 +0000
committerkensmith <kensmith@FreeBSD.org>2008-01-22 16:35:10 +0000
commit284acd07811df2f3bec640e57f13586c261e76e0 (patch)
treea982f48a042139d56d2e58cfb8f615e9518504a6 /lib/libipsec
parent59177070da4fe5da5fe34ad596dc48ee403da034 (diff)
downloadFreeBSD-src-284acd07811df2f3bec640e57f13586c261e76e0.zip
FreeBSD-src-284acd07811df2f3bec640e57f13586c261e76e0.tar.gz
In 'fixit mode' running "fsck /dev/ad0s1a" typically complains that it
can't find fsck_4.2bsd because there was no fstab file saying what filesystem type it is looking at so it got the filesystem type from the disk's label. When that fails admins who haven't been in this situation before are most likely to try "fsck -t ufs /dev/ad0s1a" because ufs is the type used in fstab files on working systems but that also fails complaining it can't find fsck_ufs. This just sets it up so /stand in the MFS image (/sbin is a symlink to /stand) includes hard links pointing fsck_4.2bsd and fsck_ufs to fsck_ffs which is what is present in /sbin on installed systems. Prodded by: obrien MFC after: 1 day
Diffstat (limited to 'lib/libipsec')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud