From owner-freebsd-questions Tue Oct 8 15:00:10 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA02817 for questions-outgoing; Tue, 8 Oct 1996 15:00:10 -0700 (PDT) Received: from cube.i-pi.com (cube.i-pi.com [198.49.217.1]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id PAA02799 for ; Tue, 8 Oct 1996 15:00:05 -0700 (PDT) Received: (from ingham@localhost) by cube.i-pi.com (8.6.12/8.6.12) id QAA20719 for questions@freebsd.org; Tue, 8 Oct 1996 16:00:02 -0600 Message-Id: <199610082200.QAA20719@cube.i-pi.com> MIME-Version: 1.0 (NeXT Mail 3.3 v118.2) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Received: by NeXT.Mailer (1.118.2) From: Kenneth Ingham Date: Tue, 8 Oct 96 16:00:00 -0600 To: questions@freebsd.org Subject: worm drives Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I just read the 2.1.5 man pages related to worm (Write Once, Read Many) = drives, of which the notable example is CD-R. What I want is to have a device for writing log files to which cannot be = altered. The worm driver wants a steady stream of data with a fixed block = size. However, log files tend to grow a line at a time. I realize that I = could have something collect up a block's worth of log entries and write = it. I was hoping for something a bit easier. Is anyone aware of something that would work? Kenneth ingham@i-pi.com