From owner-freebsd-libh Wed Oct 10 12:21:23 2001 Delivered-To: freebsd-libh@freebsd.org Received: from tomts8-srv.bellnexxia.net (tomts8.bellnexxia.net [209.226.175.52]) by hub.freebsd.org (Postfix) with ESMTP id D7C6337B403 for ; Wed, 10 Oct 2001 12:21:18 -0700 (PDT) Received: from khan.anarcat.dyndns.org ([65.94.128.156]) by tomts8-srv.bellnexxia.net (InterMail vM.4.01.03.16 201-229-121-116-20010115) with ESMTP id <20011010192118.ZTIJ13446.tomts8-srv.bellnexxia.net@khan.anarcat.dyndns.org>; Wed, 10 Oct 2001 15:21:18 -0400 Received: from shall.anarcat.dyndns.org (shall.anarcat.dyndns.org [192.168.0.1]) by khan.anarcat.dyndns.org (Postfix) with ESMTP id 0E6001A00; Wed, 10 Oct 2001 15:21:14 -0400 (EDT) Received: by shall.anarcat.dyndns.org (Postfix, from userid 1000) id D1DCD20B50; Wed, 10 Oct 2001 15:21:25 -0400 (EDT) Date: Wed, 10 Oct 2001 15:21:25 -0400 From: The Anarcat To: Alexander Langer , Libh Subject: Re: adding Disk::freespace to lib[h]disk Message-ID: <20011010152124.A1233@shall.anarcat.dyndns.org> Mail-Followup-To: The Anarcat , Alexander Langer , Libh References: <20011010124341.C531@shall.anarcat.dyndns.org> <22961.1002736882@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="a8Wt8u1KmwUX3Y2C" Content-Disposition: inline In-Reply-To: <22961.1002736882@critter.freebsd.dk> User-Agent: Mutt/1.3.22.1i Sender: owner-freebsd-libh@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --a8Wt8u1KmwUX3Y2C Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed Oct 10, 2001 at 08:01:22PM +0200, Poul-Henning Kamp wrote: >=20 > Just for the record: I'm not actively interested in libdisk... Noted. phk removed from cc: :) Ok, then I guess libdisk is left to itself now? I think libdisk should be rewritten, maybe keeping a compatibility layer with the current libdisk. This is because I think there are some fundamental designs flaws in libdisk. For example, it mixes "undo management" with low-level disk writing routines. libdisk should be low-level, that is, not an "image" of the current that gets written only when write() is called, but a set of clearly defined operations that operate directly on the disk. An additional "upper level" layer might be implemented to provide the kind of facilities libdisk provides (undo(), write()). The problem with current implementation is that the disk contains implementation-specific data (ie, subtype codes) that are undocumented and sometimes conflict with library specific data (ie type codes: [0-6]). So what do you people think? Am I making any sense? A. --a8Wt8u1KmwUX3Y2C Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjvEn7MACgkQttcWHAnWiGckjACfQu2URAu3eLo5O1QbEQ4qo1kS 25MAmgPNzLJCETcLsU4PUycAl25+nBh7 =tHCO -----END PGP SIGNATURE----- --a8Wt8u1KmwUX3Y2C-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-libh" in the body of the message