Date: Wed, 13 Oct 1999 21:12:36 -0400 (EDT) From: Chuck Robey <chuckr@picnic.mat.net> To: David Scheidt <dscheidt@enteract.com> Cc: Kirk McKusick <mckusick@flamingo.McKusick.COM>, Julian Elischer <julian@whistle.com>, Bruce Evans <bde@zeta.org.au>, Matthew Dillon <dillon@apollo.backplane.com>, freebsd-arch@freebsd.org, committers@freebsd.org, current@freebsd.org Subject: Re: The eventual fate of BLOCK devices. Message-ID: <Pine.BSF.4.10.9910132111540.46069-100000@picnic.mat.net> In-Reply-To: <Pine.NEB.3.96.991012165540.65198B-100000@shell-1.enteract.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 12 Oct 1999, David Scheidt wrote: > On Tue, 12 Oct 1999, Kirk McKusick wrote: > > > I would like to take a step back from the debate for a moment and > > ask the bigger question: How many real-world applications actually > > use the block device interface? I know of none whatsoever. All the > > filesystem utilities go out of their way to avoid the block device > > and use the raw interface. Does anyone on this list know of any > > programs that need/want the block interface? If there are none, or > > It doesn't run on FreeBSD, but Sybase uses block devices for its dedicated > disk devices. There may be other RDBMSes that do this. Informix, should a miracle occur and they decide to suport FreeBSD, definitely want the same. ---------------------------------------------------------------------------- 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-arch" 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.9910132111540.46069-100000>