data loss by improper unmount of savefile

[MU]

Muppy meanwhile uses ext3 as filesystem in the savefile, and in addition runs fsck.ext3 at startup.
This solved several issues, we still encountered problems though.

Firefox freezed after a while, especially, if you ran several other applications.
Also Wine (Internet Explorer) showed such behaviour.

I think, Barry cannot reproduce this, as Puppy is much smaller than Muppy (100 MB vs 600 MB).
Maybe unionfs gets "broken", if a certain amount of files is reached.
The solution seems to be pretty simple:
use "aufs" instead.
More:
http://murga-linux.com/puppy/viewtopic. ... 675#203675

Mark

[Dingo]

So, I, booting Puppy 3.01 from CD can use aufs instead unionfs typing these lines at boot screen?

puppy layerfs=aufs

[MU]

Yes, this should work.
I just tested it with the Grub entry myself.
You can check it like this:
after you booted with that option, type in a consolewindow:
lsmod

You now should see such a line:

aufs 105988 1

Mark

[Dingo]

Thanks, now I will try. if fully working it's a way to avoid to typing this command

puppy layerfs=aufs

any time I boot from CD?

[MU]

Thanks, now I will try. if fully working it's a way to avoid to typing this command

puppy layerfs=aufs

any time I boot from CD?

No, I don't think so.
I have no knowledge, how syslinux works, or other ways to boot a CD.
So I must look at this until weekend, so that I can modify Muppy to use aufs as default.
It might be required to patch initrd.gz for this, so that it is fooled to believe, that the option "layerfs=aufs" was passed by the boot-mechanism.

I will add a note on how I changed it, when it is done.
Mark

[MU]

ok, concerning the CD it should be easy.
I am not sure, but this might work:
Copy all files from the CD to a folder called "iso-files".
Then edit isolinux.cfg
from:

Code: Select all

append initrd=initrd.gz pmedia=cd

to:

Code: Select all

append initrd=initrd.gz pmedia=cd layerfs=aufs

Then rebuild the iso:

Code: Select all

mkisofs -o test.iso -l -b isolinux.bin -c boot.cat -no-emul-boot -boot-load-size 4 -boot-info-table iso-files/ 

Mark

[jcoder24]

Thanks, now I will try. if fully working it's a way to avoid to typing this command

puppy layerfs=aufs

any time I boot from CD?

1. mount the iso and make a copy of isolinux.cfg
2. edit isolinux.cfg and add layerfs=aufs to the end of the line that starts with append
3. use isomaster to delete the old isolinux.cfg and add your new isolinux.cfg
4. burn the updated iso

[MU]

yes, works with that entry, just tested it with qemu.
I checked it with "lsmod" without running X, as qemu is very slow on my 256 MB machine.
Mark

[Dingo]

I have tried booting from CD with option

puppy layerfs=aufs

typing lsmod aufs is showed as running, the system works fine, the speed is pratically the same, all seems work better and more fine, I think that next days I will biuld my custom ISO adding this boot parameter

[urban soul]

Maybe unionfs gets "broken", if a certain amount of files is reached.

I use unionfs with 1GB in the union (3.02alpha1.sfs, muppy8.sfs, kde3.sfs, devx.sfs) and I don't have problems with it. It would be a very poor design if unionfs fails at 1GB, if so.

I see severe problems with unionfs and (the various flavours of) ntfs, however.

Urban