From owner-freebsd-commit Sat Apr 29 22:08:17 1995 Return-Path: commit-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id WAA08985 for commit-outgoing; Sat, 29 Apr 1995 22:08:17 -0700 Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id WAA08972 for cvs-user-outgoing; Sat, 29 Apr 1995 22:08:14 -0700 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id WAA08954 ; Sat, 29 Apr 1995 22:07:48 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id PAA13717; Sun, 30 Apr 1995 15:04:31 +1000 Date: Sun, 30 Apr 1995 15:04:31 +1000 From: Bruce Evans Message-Id: <199504300504.PAA13717@godzilla.zeta.org.au> To: paul@isl.cf.ac.uk, pst@shockwave.com Subject: Re: cvs commit: src/release/libdisk Makefile blocks.c change.c chunk.c create_chunk.c disk.c disklabel.c libdisk.h tst01.c Cc: CVS-commiters@freefall.cdrom.com, cvs-user@freefall.cdrom.com, phk@freefall.cdrom.com Sender: commit-owner@FreeBSD.org Precedence: bulk >Can we wait until it's used and understood first? I'm really concerned >about these libraries that we keep putting in that are used by only >one piece of software. Yes. >It makes the "tiny FreeBSD" project a real bitch. >One of the things I've been doing is trying to get FreeBSD on really small >drives to use it for embedded applications. libc having almost everything in it is more of a problem for that. You can easily leave out separate pieces. Bruce