Return to BSD News archive
Xref: sserve comp.os.386bsd.misc:1313 comp.os.linux:56611 Newsgroups: comp.os.386bsd.misc,comp.os.linux Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!elroy.jpl.nasa.gov!usc!cs.utexas.edu!uunet!math.fu-berlin.de!xlink.net!subnet.sub.net!flatlin!bad From: bad@flatlin.ka.sub.org (Christoph Badura) Subject: Re: FYI.. benchmarks on linux and 386bsd Date: Fri, 22 Oct 1993 01:46:10 GMT Message-ID: <CF9zKy.D8s@flatlin.ka.sub.org> References: <2CB12A8D.17397@news.service.uci.edu> <MYCROFT.93Oct6054959@duality.gnu.ai.mit.edu> <29klpf$8ae@kralizec.zeta.org.au> <HSU.93Oct15200852@laphroaig.cs.hut.fi> <DERAADT.93Oct15124106@newt.fsa.ca> Organization: Guru Systems/Funware Department Lines: 14 In <DERAADT.93Oct15124106@newt.fsa.ca> deraadt@fsa.ca (Theo de Raadt) writes: >fsck and the filesystem are supposed to work together; the filesystem >must gaurantee that writes (especially during directory operations) >are done in a repeatable order so that fsck can figure out where in >the sequence of writes the crash occurred. fsck's purpose is simple: >it is supposed to back out of those unfinished operations. So who said that these ordered writes need to be done synchronously? -- Christoph Badura --- bad@flatlin.ka.sub.org -- +49 721 606137 Wer soll denn die Automatik bedienen, wenn die sich nicht per Funk melden. -- Cliff Allistair McLane