From owner-freebsd-small Thu Dec 2 16:31:53 1999 Delivered-To: freebsd-small@freebsd.org Received: from server.baldwin.cx (jobaldwi.campus.vt.edu [198.82.67.146]) by hub.freebsd.org (Postfix) with ESMTP id E1DB014BCC for ; Thu, 2 Dec 1999 16:31:48 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: from john.baldwin.cx (john [10.0.0.2]) by server.baldwin.cx (8.9.3/8.9.3) with ESMTP id TAA00226; Thu, 2 Dec 1999 19:31:38 -0500 (EST) (envelope-from jhb@FreeBSD.org) Message-Id: <199912030031.TAA00226@server.baldwin.cx> X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <19991202185200.28958@mojave.sitaranetworks.com> Date: Thu, 02 Dec 1999 19:31:38 -0500 (EST) From: John Baldwin To: Greg Lehey Subject: Re: Rearranging PicoBSD build Cc: FreeBSD-small@FreeBSD.org Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 02-Dec-99 Greg Lehey wrote: > On Thursday, 2 December 1999 at 18:37:59 -0500, John Baldwin wrote: >> >> On 02-Dec-99 Greg Lehey wrote: >>> I've almost completed some Makefiles for building PicoBSD images, and >>> I was planning on committing them in the near future. If anybody >>> would like to review them, please contact me. They're not quite >>> finished yet, so if you have any input, it would be welcome. >>> >>> A couple of changes: >>> >>> - As well as the four static images (dial, install, isp, router), I'm >>> adding a fifth one (custom). By default, custom will be low on >>> features, so that you can add your own. >> >> What about the 'net' image? I assume you actually do have it, but >> just forgot it? > > Sort of :-) I started playing with it, then renamed the directory to > custom, so when I looked through the directory names, I didn't see it. > But yes, I have no intention of removing it. Ok, just making sure. >> Also, Do you have support for building a custom, home-grown floppy >> that doesn't live in src/release/picobsd/custom? > > Why would you want to do that? There's no reason why custom shouldn't > be a symlink. But the way I build requires a number of files in > custom, and it's easier to do things in place. So that I can blow away /usr/src and not lose my custom picoBSD config. Mainly, I just want to make sure that your makefiles will work with custom being a symlink (as the system does now). When the new interface was first put in, it assumed that custom was a hard link and not a soft link, and I'm just trying to avoid that. >>> - I've added support for a second floppy disk which can be read to the >>> MFS in at boot time. >> >> I think the new GUI interface already supports this. In any case, are you >> going to take this new interface and use it to move the sysinstall >> installation >> floppy under picoBSD? > > I'm not sure what you mean by the "new GUI interface". Do you mwan > the files in release/picobsd/build? I don't see any support for it > there. Woops, I think it was on the wishlist for the new build scripts and I thought I had seen it earlier, but I don't see any type of support for that now. > Greg -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message