From owner-freebsd-small Mon Nov 16 03:15:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA22663 for freebsd-small-outgoing; Mon, 16 Nov 1998 03:15:27 -0800 (PST) (envelope-from owner-freebsd-small@FreeBSD.ORG) Received: from smtp05.wxs.nl (smtp05.wxs.nl [195.121.6.57]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA22651 for ; Mon, 16 Nov 1998 03:15:25 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from chronias.ninth-circle.org ([195.121.58.190]) by smtp05.wxs.nl (Netscape Messaging Server 3.6) with ESMTP id AAA3FF8; Mon, 16 Nov 1998 11:14:53 +0100 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Mon, 16 Nov 1998 12:19:08 +0100 (CET) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: picoBSD , Andrzej Bialecki Subject: Modular set-up Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG OK, time to get some ideas flowing again ;) Biggest problem we now have is the maintenance of four versions instead of providing a modular set-up script/thinghy. I was discussing this with a friend of mine who is a freelance consultant for UNIX systems and he suggested m4. After some thinking about how and why, I think that this might be a good idea. This way we can provide the user with a frontend/menu in which he/she can select options which then result in the creation of a file which can build the necessary `package' into a workdir/picobsd/ and which is ready for tftp'ing/ftp'ing/cp'ing to the specified device. Any ideas/thoughts/suggestions/additions? --- Jeroen Ruigrok van der Werven/Asmodai asmodai(at)wxs.nl | Cum angelis et pueris, Junior Network/Security Specialist | fideles inveniamur *BSD & picoBSD: The Power to Serve... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message