From owner-freebsd-current Wed Oct 13 18:14:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id B7E471528A; Wed, 13 Oct 1999 18:14:30 -0700 (PDT) (envelope-from chuckr@picnic.mat.net) Received: from localhost (localhost [127.0.0.1]) by picnic.mat.net (8.9.3/8.9.3) with ESMTP id VAA64183; Wed, 13 Oct 1999 21:14:10 -0400 (EDT) (envelope-from chuckr@picnic.mat.net) Date: Wed, 13 Oct 1999 21:14:10 -0400 (EDT) From: Chuck Robey To: Warner Losh Cc: David Scheidt , Kirk McKusick , Julian Elischer , Bruce Evans , Matthew Dillon , freebsd-arch@FreeBSD.org, committers@FreeBSD.org, current@FreeBSD.org Subject: Re: The eventual fate of BLOCK devices. In-Reply-To: <199910122211.QAA99359@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 12 Oct 1999, Warner Losh wrote: > In message David Scheidt writes: > : It doesn't run on FreeBSD, but Sybase uses block devices for its dedicated > : disk devices. There may be other RDBMSes that do this. > > EVERY RDBMS that I've ever seen or had to make work with my drivers > has been on the raw partition. This is because the database writers > DO NOT LIKE OR TRUST the buffer cache due to its non-deterministic > nature of disk writing. Are you sure that Sybase uses BLOCK devices > and not CHAR devices? Gawd, now that I think of it, about my Informix post, you're right, they use a raw partition, and their own buffering. > > Warner > > ---------------------------------------------------------------------------- Chuck Robey | Interests include C programming, Electronics, 213 Lakeside Dr. Apt. T-1 | communications, and signal processing. Greenbelt, MD 20770 | I run picnic.mat.net: FreeBSD-current(i386) and (301) 220-2114 | jaunt.mat.net : FreeBSD-current(Alpha) ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message