Scott Ullrich wrote:
Why can you not run the script again?   Do you get an errror?   It works here.

as you can see from the script I posted, build_embedded.sh stops at couple of places.

$CVS_CO_DIR/conf already exists when building for a second time and build_embedded.sh stops at mkdir -p $CVS_CO_DIR/conf for example:

Warning: Object directory not changed from original /usr/src/sbin/devd
install -s -o root -g wheel -m 555   devd /home/pfsense/pfSense/sbin
mkdir: /home/pfsense/pfSense/conf: No such file or directory

this is because the mkdir -p $CVS_CO_DIR/conf/ in around line 35 of builder_common.sh fails. likewise $CVS_CO_DIR/boot/device.hints_wrap is moved in fixup_wrap, so they are not present when building the second time

I am also having trouble with

(cd /var/db/pkg && ls | grep lighttpd) > $CVS_CO_DIR/conf/packages

in ./build_embedded.sh I am only able proceed if I comment out that line. I am checking that right now.

raj

On 12/28/05, Rajkumar S <[EMAIL PROTECTED]> wrote:
Scott Ullrich wrote:
I followed and fixed
http://wiki.pfsense.com/wikka.php?wakka=BuildingpFSense while building
it.
I am also following this doc to create an embedded image, One problem I
noted was that once an image is built, I cannot run the
build_embedded.sh again. So I created this script which puts some files
back again.

# cat ./regen_embedded.sh

#!/bin/sh
# Prepare an for an embedded rebuild

. ./pfsense_local.sh

rm -rf  $CVS_CO_DIR/conf
cp $CVS_CO_DIR/boot/device.hints $CVS_CO_DIR/boot/device.hints_wrap
cp $CVS_CO_DIR/boot/loader.conf $CVS_CO_DIR/boot/loader.conf_wrap
cp $CVS_CO_DIR/etc/ttys $CVS_CO_DIR/etc/ttys_wrap
touch $CVS_CO_DIR/boot/label.proto_wrap

raj

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to