From 10a7ec0db4a7f373ec0fd3e347eda634e1190eac Mon Sep 17 00:00:00 2001 From: Giorgos Keramidas Date: Fri, 11 Jan 2002 02:50:21 +0000 Subject: [PATCH] Break up the description of `dumpfreq' and `passno' fields of fstab(5) to two separate items. The text of `passno' is a bit more verbose now than the old one. PR: docs/33043 Submitted by: Ashley Penney --- .../books/handbook/basics/chapter.sgml | 26 +++++++++++++++---- 1 file changed, 21 insertions(+), 5 deletions(-) diff --git a/en_US.ISO8859-1/books/handbook/basics/chapter.sgml b/en_US.ISO8859-1/books/handbook/basics/chapter.sgml index 49651903bf..53534befee 100644 --- a/en_US.ISO8859-1/books/handbook/basics/chapter.sgml +++ b/en_US.ISO8859-1/books/handbook/basics/chapter.sgml @@ -535,11 +535,27 @@ dumpfreq - The number of days the filesystem should be - dumped, and passno is the pass number - during which the filesystem is checked during the boot - sequence. - + This is used by dump to determine which + filesystems require dumping. If the field is missing, + a value of zero is assumed. + + + + + passno + + + This determines the order in which filesystems should + be checked. Filesystems that should be skipped should have + their passno set to zero. The root + filesystem (which needs to be checked before everything + else) should have it's passno set to + one, and other filesystems' passno + should be set to values greater than one. If more than one + filesystems have the same passno then + &man.fsck.8; will attempt to check filesystems in parallel + if possible. +