[ previous ] [ next ] [ threads ]
 From:  Manuel Kasper <mk at neon1 dot net>
 To:  Bernie O'Connor <Bernie dot OConnor at sas dot com>
 Cc:  m0n0wall dash dev at lists dot m0n0 dot ch
 Subject:  Re: [m0n0wall-dev] 1.3a3 Wrap image development
 Date:  Wed, 25 Oct 2006 21:54:13 +0200
On 25.10.06 10:06 -0400, Bernie O'Connor wrote:

> What is the best way to handle source file changes for 1.3a3
> specific to the wrap?  I'm thinking specifically about the
> /etc/platform file and the defaults for the wrap in
> conf.default/config.xml.  Also, how has wrap image development been
> handled in the past?  Was it always built from scratch or did the
> maintainers work with the generic-pc binaries and
> extracted/inserted wrap specific files (kernel, etc.)?

Except for /etc/platform, the contents of mfsroot.gz in wrap and
generic-pc images are identical. What's different is just the boot
loader and kernel. Even config.xml is the same for all platforms
(since both Soekris and WRAP boards conveniently use NS DP8381x NICs).

Therefore, all that was needed in the past was a shell script to
build the image that accepted paths to the boot loader and kernel
that were to be used, as well as the string to write to /etc/platform.

- Manuel