Return to BSD News archive
Xref: sserve comp.os.386bsd.misc:1280 comp.os.linux:56458 Newsgroups: comp.os.386bsd.misc,comp.os.linux Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!usenet.ins.cwru.edu!wariat.org!kf8nh!bsa From: bsa@kf8nh.wariat.org (Brandon S. Allbery) Subject: Re: FYI.. benchmarks on linux and 386bsd References: <HSU.93Oct15200852@laphroaig.cs.hut.fi> <DERAADT.93Oct15124106@newt.fsa.ca> <1993Oct18.011943.21250@finbol.toppoint.de> <1993Oct18.132419.21519@cm.cf.ac.uk> Organization: Brandon's Linux box and AmPR node, Mentor, OH Date: Mon, 18 Oct 1993 15:51:23 GMT Message-ID: <1993Oct18.155123.26638@kf8nh.wariat.org> Distribution: inet Lines: 23 In article <1993Oct18.132419.21519@cm.cf.ac.uk> paul@myrddin.isl.cf.ac.uk (Paul) writes: >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. > >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 Nope. If anything, current Linux releases tend to fsck a bit more often than they really need to (e.g. ignore the "clean" flag in the superblock). ++Brandon -- Brandon S. Allbery kf8nh@kf8nh.ampr.org bsa@kf8nh.wariat.org "MSDOS didn't get as bad as it is overnight -- it took over ten years of careful development." ---dmeggins@aix1.uottawa.ca