From owner-freebsd-small  Sun Jul 16  9:32:44 2000
Delivered-To: freebsd-small@freebsd.org
Received: from astart2.astart.com (astart2.astart.com [206.71.174.194])
	by hub.freebsd.org (Postfix) with ESMTP id 4A2AE37C369
	for <freebsd-small@FreeBSD.ORG>; Sun, 16 Jul 2000 09:32:39 -0700 (PDT)
	(envelope-from papowell@astart.com)
Received: from h4.private (papowell@h4.private [10.0.0.4])
	by astart2.astart.com (8.9.3/8.9.3) with ESMTP id JAA40205;
	Sun, 16 Jul 2000 09:36:34 -0700 (PDT)
Received: (from papowell@localhost)
	by h4.private (8.9.3/8.9.3) id JAA15582;
	Sun, 16 Jul 2000 09:32:34 -0700 (PDT)
Date: Sun, 16 Jul 2000 09:32:34 -0700 (PDT)
From: papowell@astart.com
Message-Id: <200007161632.JAA15582@h4.private>
To: aedmonds@digitalconvergence.com, albert@achtung.com
Subject: Re: Any new PicoBSD's based on 4.0??
Cc: freebsd-small@FreeBSD.ORG
Sender: owner-freebsd-small@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hi,  I have been lurking in the background for a bit.
I have some suggestions for interested folks.

Project:
   Convert all of the existing 'standard' items to
 Makefile versions.   This will get rid of the script
 stuff.

Project:
   Add a project.conf or some other file at the
 project level,  and put necessary configuration
 information into this file,  AND PASS ITS LOCATION
 IN THE MAKEFILE PARAMETERS.  Also,  be brave:
 put the various configuration files in the top level
 as well

   Example:

  /usr/.../picobsd/myproject/Makefile
                             project.conf
                             crunch.conf


Contents of project.conf:

MFS=3500
....
     
In the top level Makefile you can do:

  PROJECT?=${.CURDIR}/project.conf
  CRUNCH?=${.CURDIR}/crunch.conf
  CONFIG?=${.CURDIR}/PICOBSD-C

  ... make PROJECT=${PROJECT} CRUNCH=${CRUNCH} CONFIG=${.CWD}

Now, you might wonder why this stuff -
  so you can have different projects use the same
  directory and have different versions for testing, etc.

> I've been playing with it.  I need to send-pr in some changes
> for 4.0.  I'll do it tomorrow.  I did manage to get dhclient in
> there, but it wasn't easy.  I have a kludge in mfs.rc to move 
> the dhclient-script file into /sbin and chmod +x it.  Ugly.
>
> I'm still learning the picobsd build process....
>
> Cheers,

Have you ever considered putting in a symbolic link to the
file?  Much easier.

Patrick


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-small" in the body of the message