From owner-freebsd-current Mon Feb 8 18:01:51 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA13311 for freebsd-current-outgoing; Mon, 8 Feb 1999 18:01:51 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA13301; Mon, 8 Feb 1999 18:01:47 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.9.2/8.9.1) id SAA64401; Mon, 8 Feb 1999 18:02:05 -0800 (PST) (envelope-from sgk) From: Steve Kargl Message-Id: <199902090202.SAA64401@troutmask.apl.washington.edu> Subject: Re: adding DHCP client to src/contrib/ In-Reply-To: from Mike Holling at "Feb 8, 1999 4:53:54 pm" To: myke@ees.com (Mike Holling) Date: Mon, 8 Feb 1999 18:02:05 -0800 (PST) Cc: des@flood.ping.uio.no, jabley@clear.co.nz, obrien@FreeBSD.ORG, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Holling wrote: > > > If we want FreeBSD to have any credibility as a workstation OS, we > > > need DHCP. It should be possible for a user or admin to smack in the > > > boot floppy, have it autoconfigure the selected network interface, and > > > perform an FTP installation. > > > > So, we'll import a pop server, apache, g77, ad nauseam > > to increase the credibility of FreeBSD as a workstation OS. > > Here are the regular (dynamically linked) versions of the ISC client and > server: > > phluffy% ls -l =dhclient =dhcpd > -rwxr-xr-x 1 root wheel 86016 Nov 20 20:47 /usr/local/sbin/dhclient > -rwxr-xr-x 1 root wheel 90112 Nov 20 20:47 /usr/local/sbin/dhcpd It will probably go into /sbin, /bin, or /stand. These are statically linked exacutables. > I built a static version of the WIDE client and server, both were only > around 140K. What's the problem? It's not like putting emacs in the base > install or anything. I still run FreeBSD on a 386/40 with a 40M MFM main > drive, and even so I'm not worried about the "bloat" of adding DHCP. Lots Bloat by any other name is still bloat. > Windows comes with DHCP. Heck, even my old Mac IIci running System 7.5.5 > comes with DHCP. It's small and increasingly useful, why not make it part > of the base distribution? Or would you rather have FreeBSD be like > RedHat, where you have to install an RPM for just about everything? Where do you draw the line on the base system? Security is important so add tcp_wrappers? More and more documentation is released in html, so add apache? Once something is added to the base distribution, it seldomly gets removed? -- Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message