more robust free space checking for sandboxes. See: http://www.murga-… #1758
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
…linux.com/puppy/viewtopic.php?p=1051204#1051204
If you run puppylinux in a chroot system (e.g. my psandbox script), then this isn't an issue at first since PUPMODE=2. However, if you then boot the created save file as your actual system then /etc/rc.d/PUPSTATE might be left over and it might have a PUPMODE different than "2". In my case it was 12, when testing arch32pup. This broke puppies package manager when I tried to reload the puppy in a sandbox since the PUPSTATE was left over (from my real boot) with PUPMODE=12.
For further discussion see:
More Robust Free Space Checking for ppm @ http://www.murga-linux.com/
This changed fixed the ppm (puppy package manager) in chroot system.