From owner-freebsd-current Mon Feb 8 20:31:48 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA01476 for freebsd-current-outgoing; Mon, 8 Feb 1999 20:31:48 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail1.atl.bellsouth.net (mail1.atl.bellsouth.net [205.152.0.28]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA01466; Mon, 8 Feb 1999 20:31:46 -0800 (PST) (envelope-from wghicks@bellsouth.net) Received: from wghicks.bellsouth.net (host-209-214-71-83.atl.bellsouth.net [209.214.71.83]) by mail1.atl.bellsouth.net (8.8.8-spamdog/8.8.5) with ESMTP id XAA29599; Mon, 8 Feb 1999 23:31:38 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by wghicks.bellsouth.net (8.9.2/8.9.2) with ESMTP id XAA12856; Mon, 8 Feb 1999 23:48:55 -0500 (EST) (envelope-from wghicks@wghicks.bellsouth.net) To: obrien@FreeBSD.ORG, obrien@NUXI.com Cc: wghicks@bellsouth.net, current@FreeBSD.ORG Subject: Re: adding DHCP client to src/contrib/ In-Reply-To: Your message of "Mon, 8 Feb 1999 19:50:55 -0800" <19990208195055.A14870@relay.nuxi.com> References: <19990208195055.A14870@relay.nuxi.com> X-Mailer: Mew version 1.93 on XEmacs 20.4 (Emerald) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19990208234849T.wghicks@wghicks.bellsouth.net> Date: Mon, 08 Feb 1999 23:48:49 -0500 From: W Gerald Hicks X-Dispatcher: imput version 980905(IM100) Lines: 31 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From: "David O'Brien" > > Make sysinstall be able to pkg_add? We do something similar to that > > And just WHERE is the package?? Often on an NFS or FTP server, no?? > And just HOW am I to communicate with that NFS or FTP server?? Sorry. It's got to go somewhere offline. If not in the crunched /stand I'd guess it could live on the mfsroot floppy as an archive. I agree that DHCP is very important to have *somewhere* easy to use for both pre- and post- install purposes. We've produced a deviant PicoBSD that uses a different scheme for and uses shared libraries for greater flexibility. Of course, the price you pay is the static memory footprint required. As Jordan has mentioned, what we really need is a new dynamically sizable memory filesystem. I see that Eivind is doing something with getting NULLFS fixed. This is probably a very good step toward a more flexible setup environment. Cheers, Jerry Hicks wghicks@bellsouth.net > > -- > -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message