On Fri, May 04, 2001 at 10:39:51PM -0400, Chris BeHanna wrote:
> On Fri, 4 May 2001, Tadayuki OKADA wrote:
[...]
> > I've heard that it always keeps consistency.
> > So you can skip fsck after the crash.
> > #I don't know the detail, so please someone correct me if I'm wrong.
>
> I've had a num
[EMAIL PROTECTED] said:
>WCE very dangerous. WCE very dangerous. WCE very dangerous.
True, but since the new ATA driver was installed in STABLE about February 25,
WCE has also become mandatory for my NEC Versa 6050 MX laptop. If I don't set
hw.ata.wc=1, kernel buffers become corrupted. Per
> Date: Sat, 05 May 2001 09:31:09 -0700
> From: Nick Sayer <[EMAIL PROTECTED]>
> Sender: [EMAIL PROTECTED]
>
> That may be the original intent, but cheap IDE drives let you turn on
> write caching, and they're for sure not battery-backed (nor do they
> attempt to store enough power at power-off
Nick Barnes wrote:
> This sounds as if there isn't _any_ way for the kernel (or, better, an
> application) to make sure that its bits have got written. Is that
> really true? Shouldn't the man pages for fsync(1), fsync(2), and
> sync(8) reflect this? sync(2) has something under "BUGS"
Sur
