Xref: utzoo comp.sys.amiga:19995 comp.sys.amiga.tech:975
Path: utzoo!attcan!uunet!lll-winken!lll-tis!helios.ee.lbl.gov!pasteur!agate!eris!mwm
From: mwm@eris.berkeley.edu (Mike (I'm in love with my car) Meyer)
Newsgroups: comp.sys.amiga,comp.sys.amiga.tech
Subject: Re: Disk corrupt - task held
Message-ID: <10922@agate.BERKELEY.EDU>
Date: 14 Jun 88 08:39:46 GMT
References: <1657@vaxb.calgary.UUCP> <7416@swan.ulowell.edu> <2115@sugar.UUCP>
Sender: usenet@agate.BERKELEY.EDU
Distribution: na
Organization: Missionaria Phonibalonica
Lines: 29

In article <2115@sugar.UUCP> peter@sugar.UUCP (Peter da Silva) writes:
<Bob, that's misleading. Yes, the Amiga handles disks that are full of
<garbage a whole lot better than UNIX. On the other hand, we're talking
<of disks that are just slightly damaged. Once you mount the disk
<successfully, UNIX will stay up even in the face of *rampant* disk
<corruption

But Unix when it was several times older than AmigaDOS is now had
those kinds of problems; Berkeley and AT&T (and thousands of hackers
around the world) have been beating on the Unix file system(s), and
fixing those things since the early '70s. Even as late as 1980,
running out of space on a file system could panic a Unix.

Even now, the validator & diskdocter do well by fsck -p standards, and
disksalve is something that just flat doesn't exist. Nuts - Unix got to
v6 (or was it v7) without having tools for fixing broken file systems.
Unless you think adb and clri qualify.

True, AmigaDOS is still a bit paranoid about things. I want a system
like VMS, that will run with the disks drives smoking, cables not
properly plugged in and the system pack and swap areas write
protected. I suspect that AmigaDOS will get there before any Unix
does.

	<mike
--
Must have walked those streets for hours,		Mike Meyer
In the dark and in the cold,				mwm@berkeley.edu
Before I really could accept,				ucbvax!mwm
There's no place called hope road.			mwm@ucbjade.BITNET