Image Modification

Hi,
I'm trying to include my own config.xml in a custom 1.23 image with workon.sh on a FreeBSD 6.2 machine.
When I write my image to a CF card and install the card on a system, it always seems to have the default config, and not "my" config.xml. I don't quite understand this as I deleted the default one and put mine into place. (in /conf.default of the M0n0wall root) When I look at the config.xml before I repack the image, my changes are definately there.
As a test I also changed some images and the rc.banner file in my custom image and those changes are
perfectly included in the new created image. Only the config.xml doesn't seem to do it, all configuration settings are default.

Am I overlooking something? All help is greatly appreciated.

Many tnx
Yves

I still can't find a decent solution to this.
I tried to include my config.xml in the /cf/conf/ dir of my image, but still no luck.
The initial config loaded at startup with a fresh written image is still the default one.
When I hit "reset to default" in the CLI it does load "my" config.xml though, as it takes the one from conf.default then,
but I would like to have it right in place at the first boot. (so I don't have to configure the interfaces everytime)
Anyone can help me out here?

Many tnx

It should be /conf/config.xml I believe. If that doesn't work, I'm not sure what to tell you.

It should be /conf/config.xml I believe. If that doesn't work, I'm not sure what to tell you.

Thanks for your answer Chris.
But in the m0n0wall root /conf is a symlink to /cf/conf, so it should work with config.xml in /cf/conf, but it doesn't.
I guess I'm overlooking something, but I don't know what.

Kind regards,
Yves

Yeah I'm trying the same thing right now, with the same result. Did you ever come up with a way to do this? If I come up with something I'll post back here.

Yeah I'm trying the same thing right now, with the same result. Did you ever come up with a way to do this? If I come up with something I'll post back here.

Hi Chris,
No, i never found the solution for this. But honestly, I didn't search that long anymore.

I include my config.xml in /conf.default and repack the image.
I found out that after the initial boot hitting 4 "restore default settings" on the console loaded "my" config.xml.
So what I do now is just write my custom image to a CF card, add that CF into a new system, boot from it, hit 4
and after a reboot my config is there :-) It's not really how I wanted it to be, but I can live with it.

PS I also changed the script which resets the default passwd and included my own passwd in it.
This way I don't have to disable the console menu anymore, if someone ever connects a monitor/keyboard
they can hit whatever they want, it won't change a single setting ;-)

Kind Regards,

Yves

Yeah I just ended up replacing the default config with my custom config as well, then reset to defaults once it was up and running.

Yeah I just ended up replacing the default config with my custom config as well, then reset to defaults once it was up and running.

This keeps playing on my mind.
Where does it get that default config at initial boot? 
It has to be there somewhere... 

Kind regards

I tried this before, here's how it's done.
Put your config.xml in /conf.default in your mfsroot image, so that when you reset to default, your settings come up, and put it in /conf on your cf card image, so that you get the from the first boot.

Remember, put it on /conf.default in mfsroot, and /conf in cf image.

This keeps playing on my mind.
Where does it get that default config at initial boot?  Huh
It has to be there somewhere...  Shocked

it is there in mnt1 not mnt2.
mnt1/config/config.xml   <!-- m0n0wall default system configuration -->