These are mostly Woof-level fixes, so will apply to all future puppies.
I have reached the end of that thread (page 16), and now will go on to reading the Wary 5.2.1 feedback thread.
Comments:Posted on 10 Nov 2011, 10:56 by bigpup
Woof Test Version
Just an idea, but it seems like something that would be useful.
After you do a major update/change to Woof, make a test version of Puppy with it, to see if the fixes really fix the bugs.
I am sure many people would be willing to test this Woof Puppy.
Then when it checks out, release the new Woof so Puppy versions can be made from it.
This would also give you a central location to look for Woof bugs.
Posted on 10 Nov 2011, 14:29 by pemasu
for me flash downloader does not work anymore in delayedrun script. The ping to the google does not respond. I am not sure if my delayedrun is latest, but thought to post my finding so that people could test is it universal problem or just me. Anyway...I
changed the ping target and it works now.
Flash downloader script section in delayedrun needs that you are using fresh install like pfix=ram.
Posted on 10 Nov 2011, 14:42 by 01micko
I just changed the ping adress to 18.104.22.168, which is still google, but one of their main ones.
Posted on 10 Nov 2011, 15:10 by mavrothal
It would appear that recent puppies do not have kernel-headers in the devx or the source sfs.
As far as I can see the 1kernel.sh makes the headers and 3package.sh does not include them in the sfs or package them in any way.
So maybe is a woof/kernel building issue?
Posted on 10 Nov 2011, 16:11 by BarryK
Thanks for that info. It no longer works for me either. I have changed it to 22.214.171.124.
Posted on 10 Nov 2011, 16:16 by BarryK
Re Kernel headers
Wary and Racy have the headers in the devx, this package:
linux_header_t2-2.6.32|linux_header_t2|2.6.32||BuildingBlock|4236K||linux_header_t2-2.6.32.pet||header files for 126.96.36.199 kernel||||
As far as I am aware, all puppies have the kernel headers in the devx.
Posted on 10 Nov 2011, 16:44 by mavrothal
Re Kernel headers
You are right.
I thought so because of some problem I had compiling the latest aufs-util.
But Racy does not have aufs and slacko has a very old aufs version for the kernel that is using.
Posted on 10 Nov 2011, 19:14 by scsijon
on the otherhand, for those that don't like using google, I have approval from the "boss" of Skymesh to allow use of one of their spare ip's. The allocated one for us is 188.8.131.52, it belongs to a core router so should be always up and quick!
Posted on 11 Nov 2011, 6:08 by BarryK
Re kernel headers
I think that I know what has happened in your case. It is the famous "scsi.h" problem. Search my blog for more details.
That's nice! I have already put 184.108.40.206 into delayedrun, and released Wary/Racy.