Subject: Re: Reworking minirot/ramdisk build tools
To: Jonathan Stone <jonathan@DSG.Stanford.EDU>
From: David Brownlee <abs@anim.dreamworks.com>
List: tech-install
Date: 09/06/1999 10:02:18
Actually on a realtaed note - you might want to look at
distrib/sparc/ramdisk.sysinst
I modified it to use m4 so I could build i386 and sparc ramdisk
kernels from the same directory. My intentionw as to migrate
it into an MI area and expand it to other ports.
btw - I like the idea of your crunchgen changes, but would
an 'include' directive be more generic?
David/absolute
-=- "Why am I seething with this animosity" -=-
On Sun, 5 Sep 1999, Jonathan Stone wrote:
>
> Our setup for building miniroots and install-kernel ramdisk images
> have gotten messy. Too much is duplicated: Multiple,
> not-quite-consistent copies of runlist. No central place to list the
> MI utilities which sysinst or the sh-script update/install require,
> multiple list inputs, ...
>
> I'd like to clean that up. Below are some (trivial) diffs to crunchgen
> which let it read multiple .conf files. The idea is to break out
> 1. stuff needed to boot: init,
> 2. a) MI stuff needed by install/upgrade scripts
> b) MD stuff needed by install/upgrade scripts
> 3 a) MI stuff needed by sysinst (or Perry's too)
> b) MD stuff needed by sysinst (or Perry's too)
>
> and the same for the `list' run to populate the file.
>
> This could be generalized to allow other configs for turnkey boot
> floppies for "xterminal", "router" &c.
>
> Anyway, here's the crunchgen diff. I've tested it by breaking
> out `tip' from the pmax ramdiskbin.conf into a ramdiskbin.pmax.conf,
> adding that to the ramdisk Makefile CRUNCHCONF. all goes OK.
> Anyone care to review it before committing?