From owner-freebsd-current Wed Jun 24 10:48:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA20855 for freebsd-current-outgoing; Wed, 24 Jun 1998 10:48:12 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.133.1] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA20769 for ; Wed, 24 Jun 1998 10:47:44 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.5) with ESMTP id TAA00661; Wed, 24 Jun 1998 19:44:16 +0200 (CEST) To: Chuck Robey cc: Peter Wemm , freebsd-current@FreeBSD.ORG Subject: Re: Heads up: block devices to disappear! In-reply-to: Your message of "Wed, 24 Jun 1998 08:14:04 EDT." Date: Wed, 24 Jun 1998 19:44:16 +0200 Message-ID: <659.898710256@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >One last question, I think, ought to be asked. One application I used >to program for was the Informix SQL database ... it used to manage it's >own storage. You'd set up a partition that it would be solely >responsible for, and it would control it directly (no filesystem mounted >at all, no programmer access via filesystem). As long as your >modifications don't block this type of application from working it this >way, then I think that'd be the last complaint I could see. > >Does it? no. If you check your RDBMS manuals you will see that they all stress that you should use char devices, this is so that they can get the error if a write doesn't succeed. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message