PB

slacko-8.2.2-174.iso the DISTRO_SPECS in the savefile / folder is different to the version in the puppy.sfs leading to an upgrade request every reboot.

No thats not the problem - the update happens EVERY REBOOT not just when a version changes.... The problem is also that the update is trying to be from 8.2.2-174...

Again - thats not the problem....... These are REBOOTS of -174 which are exhibiting a desire to update every time NOT version changes

BTW.... build-x86-slackware-14.2-174 also exhibits this problem - and this is not an "experimental" system..... [bootsysinit.log](https://github.com/puppylinux-woof-CE/woof-CE/files/8574881/bootsysinit.log)

OK it definitely has a breaking change!

> However, the people producing the other Puppy versions, would have to be willing to produce the fix files, that Quickpet uses and provide the pet packages, that it provides....

> I would suggest a third option, use the "ydrv" as a "patch" layer Nice idea - but I struggle to see how it could be automated given the available...

UPupBB - BionicPup32 uses: :rp_pppoe_cli:|pet|Packages-puppy-tahr-official|rp_pppoe_cli-3.8-patched4-p4|rp_pppoe_cli|3.8-patched4-p4||Network|440K||rp_pppoe_cli-3.8-patched4-p4.pet||roaring penguin pppoe internet connection|puppy|4|| rp_pppoe_cli-3.8-patched4-p4.pet 2014-Mar-03 17:50:15 149.9K application/octet-stream http://distro.ibiblio.org/puppylinux/pet_packages-tahr/rp_pppoe_cli-3.8-patched4-p4.pet It has a real (but almost empty) /etc/resolv.conf with a valid link in /etc/ppp/resolv.conf and...

> and these come from /rootfs-skeleton not the .pet https://github.com/puppylinux-woof-CE/woof-CE/tree/testing/woof-code/rootfs-skeleton/etc/ppp

3.10 is in http://distro.ibiblio.org/puppylinux/sources/r/ and is used by petbuild: https://github.com/puppylinux-woof-CE/petbuilds/tree/slacko_142/rp-pppoe