home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!charon.amdahl.com!pacbell.com!decwrl!sun-barr!cs.utexas.edu!qt.cs.utexas.edu!yale.edu!ira.uka.de!math.fu-berlin.de!mailgzrz.TU-Berlin.DE!cs.tu-berlin.de!news.netmbx.de!Germany.EU.net!mcsun!sunic!chalmers.se!cs.chalmers.se!augustss
- From: augustss@cs.chalmers.se (Lennart Augustsson)
- Newsgroups: comp.unix.bsd
- Subject: Re: 386BSD or LINUX?
- Keywords: n
- Message-ID: <1992Nov17.045443.20013@cs.chalmers.se>
- Date: 17 Nov 92 04:54:43 GMT
- References: <Nov.2.20.33.38.1992.18690@remus.rutgers.edu> <1992Nov4.052106.29266@menudo.uh.edu> <1992Nov4.131541.15661@prism.poly.edu>
- Sender: news@cs.chalmers.se (News administrator)
- Organization: Chalmers University of Technology
- Lines: 16
-
- In article <1992Nov4.131541.15661@prism.poly.edu> kapela@prism.poly.edu (Theodore S. Kapela) writes:
- >Yes. I had the problem with the fsck also. It looks like fsck exits
- >before the system is rebooted (after fsck modifies the root fs). This
- >allows the rc scripts to continue, and a sync ends up being done. This flushes
- >the bad buffers back to disk, writing over the fixes made by fsck (using the
- >raw partition). I haven't really had a chance to check this out yet.
- Add the line
- trap : 15
- at the start of /etc/rc to fix the problem. reboot send SIGTERM to all
- processes and it is not ignored by default by the shell. (One one the 58
- patches caused this behaviour.)
-
- --
-
- -- Lennart Augustsson
- [This signature is intentionally left blank.]
-