sanderdog-2.0: the chrooted underdog

[mistfire]

sanderdog is a chrooted underdog linux. It doesn't mount directly under the rootfs layer but instead creates another aufs rootfs and run its applications in chroot it has desktop integration except file associations (this might need workaround). It doesn't ruin the existing linux installation because it was mounted as read-only.

How to use:
1. Install sanderdog pet package and reboot the computer
2. enable rc.sanderdog in puppy service manager or make /etc/init.d/rc.sanderdog executable
3. Goto sanderdog gui to select linux partition
4. Click start

NOTE: Sanderdog works only if save was loaded or using PUPMODE 2

[Luluc]

It doesn't ruin the existing linux installation because it was mounted as read-only.

What happens if I install the puppy/dog on say, sda1 (so sda1 is mounted) with changes on a file or directory also on sda1 (so sda1 is mounted), and I want to run something off an existing Linux also installed on sda1, which Sanderdog is supposed to mount read-only?

[mistfire]

It doesn't ruin the existing linux installation because it was mounted as read-only.

What happens if I install the puppy/dog on say, sda1 (so sda1 is mounted) with changes on a file or directory also on sda1 (so sda1 is mounted), and I want to run something off an existing Linux also installed on sda1, which Sanderdog is supposed to mount read-only?

sanderdog was a just a chrooted aufs mountpoint consists of two folders, the writable folder and read-only mounpoint. any changes on chroot environment was stored on writable folder

[Luluc]

sanderdog was a just a chrooted aufs mountpoint consists of two folders, the writable folder and read-only mounpoint. any changes on chroot environment was stored on writable folder

What do you mean, "was"? It's included in quickpup64, which is in active development.

I still would like to know what happens when a rw file system is supposed to be mounted ro.

[mistfire]

I still would like to know what happens when a rw file system is supposed to be mounted ro.

The file system will just works fine because the file system was mounted on lower layer of aufs as read-only. There is an upper layer that act as writable. Any changes on the merged mountpoint will be isolated on the upper layer.