Why doesn't modules.conf persist after reboot?

[sunburnt]

I added lines to /root/.etc/modules.conf but rebooting copies the old file over it.
Shouldn't the non "0" ending files save into the pup file & be restored.
/root/.etc/rc.d/rc.local persisted when I wrote to it, why not /root/.etc/modules.conf?
I thought the "0" ending files were the ones that were copied over from image.gz on reboot.

[jmarsden]

I think you need to specify which version of Puppy you are running, and possibly your overall boot setup.

I just did

Code: Select all

echo "# `date`" >>/etc/modules.conf

verified the comment line was in there, and then rebooted. It stayed in there. This is in Puppy 1.0.8, booting from CD using a pup001 file on /dev/hda3 which is an ext3 partition.

Maybe this was fixed in 1.0.8?

Jonathan

[sunburnt]

Sorry... Puppy105, PizzaPup, & EmptyCrust - poormans, all seem to write over the modules.conf file.
Must be a boot script bugaboo, pup001 is made on first run, but it keeps getting written over after that.
I could try to find & fix it, but putting a command in rc.local to copy a link over the file is a lot simpler.
With a link, any changes will go to the real file that isn't copied over, so it'll persist.

[BarryK]

Yes, versions before 1.0.8 do overwrite modules.conf.

For 1.0.8, also puppy2, you can edit modules.conf and it will persist.