Date: Tue, 7 Dec 1999 23:32:14 -0800 (PST) From: Matthew Jacob <mjacob@feral.com> To: Mike Smith <msmith@FreeBSD.org> Cc: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/kern kern_shutdown.c Message-ID: <Pine.BSF.4.10.9912072331160.35786-100000@beppo.feral.com> In-Reply-To: <199912080726.XAA04037@mass.cdrom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> > Yes, it is in fact. If you cannot guarantee data integrity, you shouldn't > > be running on it. If you have to run on it, don't expect data integrity. > > I thought your argument was "we ought to work properly where it's > possible, rather than pursue some golden ideal of perfection"? No- not quite. We should claim to support sane hardware, but shrug and hand the user the bullets if they want to end it all for themselves. > > > (okay, so it's a couple of buffers at shutdown- in any case, perhaps the > > driver that sees Synchronize Cache not working should do something else- > > maybe calculate the Pareto for the first occurence of a y3k bug) > > You could just delay for a couple of seconds and guarantee that even if > the Synchronise Cache command didn't work, the drive will still have > flushed it's cache. Oops, looks like that's what I committed the other > day. You're toying with me, aren't you? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.10.9912072331160.35786-100000>