Rizal Martin

It seems mount/umount/eject command was a called in hard-coded path instead of following $PATH environment variable. Is there anyway to fix this issue on pup-volume-monitor?

Forking sc0ttman's pkg

9

sc0ttman's pkg was great and powerful tool however his code was too outdated lag behind PPM with huge improvements such as package downgrade/upgrade. What if I fork the pkg?

Since the announcement of nvidia open source driver. Using modesetting might be feasible.

Dynamic path for updating system cache files

This is a response on merged PR #2680 in order to make encryption of savefile using luks worked perfectly

Try to unmount luks block devices using static build from initrd first in response on merged PR #2680 if unmount fails use the cryptsetup from main puppy sfs file

This suggest might cause disruptive changes but very useful. I suggest that Puppy core scripts (rc.sysinit, rc.shutdown, rc.services, rc.country, rc.network, sfs_load, eventmgr, resizep.sh, puppy universal installer, remasterpup) to specific location...