Return to BSD News archive
Xref: sserve comp.os.386bsd.misc:1277 comp.os.linux:56449 Newsgroups: comp.os.386bsd.misc,comp.os.linux Path: sserve!newshost.anu.edu.au!munnari.oz.au!constellation!osuunx.ucc.okstate.edu!moe.ksu.ksu.edu!vixen.cso.uiuc.edu!howland.reston.ans.net!pipex!uknet!cf-cm!paul From: paul@myrddin.isl.cf.ac.uk (Paul) Subject: Re: FYI.. benchmarks on linux and 386bsd Message-ID: <1993Oct18.132419.21519@cm.cf.ac.uk> Sender: news@cm.cf.ac.uk (Network News System) Organization: Intelligent Systems Lab, ELSYM, University of Wales, Cardiff References: <HSU.93Oct15200852@laphroaig.cs.hut.fi>> <DERAADT.93Oct15124106@newt.fsa.ca> <1993Oct18.011943.21250@finbol.toppoint.de> Distribution: inet Date: Mon, 18 Oct 1993 13:24:17 +0000 Lines: 33 In article <1993Oct18.011943.21250@finbol.toppoint.de> jschief@finbol.toppoint.de writes: >deraadt@fsa.ca (Theo de Raadt) writes: > >>No thanks. I want reliability of my filesystems during a crash. > >We tried to setup X11 for Linux needed to switch off about 15 times, >no problem. >I swiched off a system compiling a new kernel, no problem for >ex2fs & Linux. >I call this a good filesystem. >Joerg I noticed in a previous posting that a Linux'er was whacking his reset button and then not fsck'ing his system when it came back up. Is this normal for Linux. Your filesystem may well appear to work when you do resets but unless you do check the filesystem you're not going to notice any problems until they trash your disk badly. When doing kernel testing I often do fastboots and everything appears ok but every two or three I make sure I do a fsck to clean up the mess that occurs when you crash your system. (Not a very sane practice but I get fed up of waiting when doing lots of kernel hacking). Claiming the Linux filesystem is rock solid because it seems to work after a reset, without doing a fsck to really chech this is the case, is simply deluding yourselves. -- Paul Richards, University of Wales, College Cardiff Internet: paul@isl.cf.ac.uk JANET: RICHARDSDP@CARDIFF.AC.UK