🚀 go-pugleaf

kkk@jybox.jyu.fi (Kristo Kulju) writes:

>Ja sitten kaipaisin v{h{n ohjeita fsck-ohjelman k{ytt||n, kuinka usein se 
>kannattaa ajaa, ja mit{ ne eri parametrit siin{ tekev{t? Minulla on viel{
>Minix-filesysteemi k{yt|ss{.

V{s{sin taannoin omiin tarpeisiin man-sivun fsck:sta. Se sis{lt{{ tasan
tarkkaan vain Linusin omat kommentit fsck.c:st{, joka oli aika vanha.
Mik{li on niin ik{v{sti, ett{ t{m{ on vanhentunutta tietoa, joku antanee
kuulua asiasta? T{ss{ tulee:

--leikkaa--
.TH FSCK 1L \" -*- nroff -*-
.SH NAME
fsck \- file system consistency check and maintenance
.SH SYNOPSIS
.B fsck
[\-larvsm] device
.SH DESCRIPTION
(C) 1991 Linus Torvalds. This file may be redistributed as per
the Linux copyright.
.PP
I've had no time to add comments - hopefully the function names
are comments enough. As with all file system checkers, this assumes
the file system is quiescent - don't use it on a mounted device
unless you can be sure nobody is writing to it (and remember that the
kernel can write to it when it searches for files).
.SS OPTIONS
.TP
.I "\-l"
for a listing of all the filenames
.TP
.I "\-a"
for automatic repairs
.TP
.I "\-r"
for repairs (interactive)
.TP
.I "\-v"
for verbose (tells how many files)
.TP
.I "\-s"
for super-block info
.TP
.I "\-m"
for minix-like "mode not cleared" warnings
.PP
The device may be a block device or a image of one, but this isn't
enforced (but it's not much fun on a character device :-). 
--leikkaa--

rw
-- 
widenius@cc.helsinki.fi "But now there was worse." -Bernard Levin