From owner-freebsd-hackers Tue Jan 14 05:48:19 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id FAA12970 for hackers-outgoing; Tue, 14 Jan 1997 05:48:19 -0800 (PST) Received: from whale.gu.kiev.ua (whale.gu.net [194.93.190.4]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id FAA12955 for ; Tue, 14 Jan 1997 05:48:13 -0800 (PST) Received: from trifork.gu.net (trifork.gu.net [194.93.190.194]) by whale.gu.kiev.ua (8.7.5/8.7.3) with SMTP id PAA57298; Tue, 14 Jan 1997 15:47:45 +0200 Date: Tue, 14 Jan 1997 18:51:47 +0200 (EET) From: Andrew Stesin To: Mikael Karpberg cc: Brian Somers , hackers@freebsd.org Subject: Re: Cyclic filesystem (WAS: Re: truss, trace ??) In-Reply-To: <199701140207.DAA12321@ocean.campus.luth.se> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 14 Jan 1997, Mikael Karpberg wrote: > > I for one couldn't care less how good the implementation is. I would just > like a nice efficient way of making any logfile max out at a certain size, > plus minus a little. Exactly. I'm sure that even if your requested arbitrary size of a cyclic file will be rounded to a FS blocksize boundary by the implementation -- no problem at all. > I think you could just say that when you filled one > block (no matter what blocksize you run on the disk) and you need to > add a new one to the file, just grab the first block, remove it from the > front, clear it, append it to the end and start filling in data. Mininum > cyclic filesize, two blocks. Always cut at full blocksizes. I wholeheartly second your approach. > No matter what you might think of this, in terms of uggliness of such a hack, > I think it would be a really nice extention to the normal file system, if Be it "ugly" or not -- it's useful... [...] Best regards, Andrew Stesin nic-hdl: ST73-RIPE