Very Computer

I remember I first learned of `fsck -f -y /` after `umount /` in the
thread:

Newsgroups: comp.unix.shell
Subject: fsck fsck say I
http://groups.google.com/groups?threadm=2695edf1.0312021221.72f242a3%...

Speaking again now of fsck'ing on demand, eventually I also noticed,
...

My `man -k fsck` does not yet, but could/ should, point to:

--- http://www.google.com/search?q=linux+man+shutdown
--- http://www.die.net/doc/linux/man/man8/shutdown.8.html
...
-f
Skip fsck on reboot.
-F
Force fsck on reboot.
...
---

Pat LaVarre

Quote:> I remember I first learned of `fsck -f -y /` after `umount /` in the
> thread:

> Newsgroups: comp.unix.shell
> Subject: fsck fsck say I
> http://groups.google.com/groups?threadm=2695edf1.0312021221.72f242a3%...

> Speaking again now of fsck'ing on demand, eventually I also noticed,
> ...

> My `man -k fsck` does not yet, but could/ should, point to:

> --- http://www.google.com/search?q=linux+man+shutdown
> --- http://www.die.net/doc/linux/man/man8/shutdown.8.html
> ...
> -f
> Skip fsck on reboot.
> -F
> Force fsck on reboot.
> ...
> ---

> Pat LaVarre

Reading this remind me of the 15 year old program jive
that can filter text, for example a manpage into this:

WARNINGS
      De opuh'tin' system  buffers stash  system  data. Runnin' fsck
      on some mounted   stash  system  kin  cause da damn opuh'tin'
      system's buffers t'become out uh date wid respect t'de disk.
      Fo'  dis reason, de  stash system should be unmounted when fsck
      be used. If dis be not possible, care should  be snatchn dat de
      system be quiescent and dat it be rebooted immediately afta'
      fsck be run. Quite often, however, dis gots'ta not be sufficient.
      'S coo', bro. A panic gots'ta probably occur if runnin' fsck on
      some  stash system modifies de  stash system.  Sheeeiit.

/bb