From: Otto Wyss <otto.wyss@bluewin.ch>
To: Alex Stewart <alex@foogod.com>
Cc: "'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>
Subject: Re: How errorproof is ext2 fs?
Date: Fri, 14 Sep 2001 22:37:58 +0200 [thread overview]
Message-ID: <3BA26AA6.CAC6D2D9@bluewin.ch> (raw)
In-Reply-To: <3BA1258F.5CC18A2C@bluewin.ch> <3BA1E670.9010300@foogod.com>
> > it does not need a good error proof fs. Still can't ext2 be made a little more
> > error proof?
>
> First, you seem to be making quite a few assumptions which are not
> necessarily correct:
>
> 1) Just because an OS does not _tell_ you there was a problem does not
> necessarily mean there wasn't one. In particular, MacOS is notorious
> for not "bothering" users with detailed (or in many cases any)
> information about problems. I don't know about HFS fragility in
>
Well I can assure you I used DiskFirstAid and Norton Utilities on the Mac.
Neither found any problems. Since I use MacOS9, my Mac crashes at least once a
month but I never ever lost anything. Most of the time my USB-keyboard/-mouse
doesn't react anymore after switching back from my Linux system. Usually I
simply press the reset switch after a few minutes.
Besides Linux also does not react occasionally when switching my
USB-keyboard/-mouse but since I also have an AT-keyboard handy I don't have to
reset it.
> 3) You're basing your linux experience on (apparently) only one
> incident. As a professional sysadmin, I've experienced many many
I'm not bashing linux, I'm only stating that MacOS9 (or HFS+) has a nice feature
Linux (or its fs's) lacks. My experience shows clearly that I had at least 10
craches on the Mac durning the last year but I never lost anything. During the
same time I had 2 crashes on my linux, one due to the USB-problem without a
handy AT-keyboard, the second now due to a malfunction el3diag.
O. Wyss
next prev parent reply other threads:[~2001-09-14 20:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-13 21:30 How errorproof is ext2 fs? Otto Wyss
2001-09-13 21:53 ` Joel Jaeggli
2001-09-13 22:05 ` Alan Cox
2001-09-14 19:16 ` Otto Wyss
2001-09-14 20:39 ` Mike Fedyk
2001-09-16 8:58 ` Rogier Wolff
2001-09-16 10:00 ` Frank Schneider
2001-09-16 10:14 ` Luigi Genoni
[not found] ` <3BA1E670.9010300@foogod.com>
2001-09-14 20:37 ` Otto Wyss [this message]
2001-09-14 23:09 ` Alan Cox
2001-09-14 13:09 Jesse Pollard
[not found] <Pine.LNX.4.10.10109140953100.24181-100000@coffee.psychology.mcmaster.ca>
2001-09-14 20:47 ` Otto Wyss
2001-09-14 21:38 ` Andreas Dilger
2001-09-15 6:39 Timothy A. Seufert
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3BA26AA6.CAC6D2D9@bluewin.ch \
--to=otto.wyss@bluewin.ch \
--cc=alex@foogod.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).