There are a couple of important reasons for this:
1. Direct save
When Puppy is installed to a Flash drive, the working top-layer of the filesystem is in RAM, however when a package is installed it gets written direct to the save-file on the Flash drive (at least this is how it works in all recent Woof-built puppies). Aufs needed to be upgraded to support this properly.
2. PUPMODEs 6/7
There are a couple of PUPMODEs in which the main Puppy SFS file (exs: wary-070.sfs, pup-431.sfs) is resident on one layer of the layered filesystem but also needs to be mounted via a loop device as another layer. Aufs needs to be especially patched to allow this.
The latest 220.127.116.11 source is to be found here, including an SFS source file:
Username: p#up#py Password l#in#ux (remove the #'s)
The site also has a README:
Comments:Posted on 23 Sep 2010, 12:00 by scsijon
18.104.22.168 rebuild problems
Hi, I seem to have a lot of missing libraries with trying to install any puppy5 or lucid pets with the rebuilt directory version? At least with a frugal.
On the other hand, using the later kernal core 34.1 version was ok.
was there something missed?
Posted on 23 Sep 2010, 15:12 by BarryK
I don't understand the question.