...note the delta files are very small, very easy to upgrade from 5.1.3 if you are on dial-up.
5.1.4 is intended to be a bugfix and minor upgrade from 5.1.3. More extensive upgrades of applications are targeted for 5.2.
Here is the blog announcement for the public-released 5.1.3:
Forum thread for feedback, go to page 20 for discussion of 188.8.131.52:
Posted on 24 Aug 2011, 6:14 - Category: Wary - Comments - href="?edit=02432">Edit - Delete
Wary is our 'flavour' of Puppy that targets older hardware. Version 5.1.3 is mostly bugfixes and minor upgrades to 5.1.2. There have been some significant improvements at the Woof level, such as a close-box on desktop drive icons and faster bootup. New applications: Default Applications Chooser, Urxvtset. New utilities: picscale, pngoverlay, yad. I decided to stay with SeaMonkey 1.1.18, as 2.2 has a badly broken Composer module. Also, 1.1.18 is smaller and better suited to older hardware -- FlashBlock and AddBlock plugins are included to suit those on dialup and download-limited Internet connection. A couple of projects that have been upgraded in Wary and are worthy of special mention: BaCon and gtkdialog. BaCon is a superb BASIC compiler, and gtkdialog provides sophisticated GUIs for shell scripts. Both of these are extremely active projects, with very keen developers and users.
Further announcement and release notes:
Download ISO live-CD (120.6MB):
'devx' SFS for complete compiler environment (109.1MB):
For those on dialup and/or restricted download capability, we have xdelta files, smaller files for upgrading from an earlier Wary download:
...ideally, you need a running Puppy, as the Utility menu has a simple drag-and-drop GUI for updating with an xdelta file.
Posted on 13 Aug 2011, 14:51 - Category: Wary - Comments - href="?edit=02399">Edit - Delete
This is really bad. I had hoped to release Wary 5.1.3 with SM 2.2, however, I am going to stay with 1.1.18 as in Wary 5.1.2.
Hopefully I will be able to upgrade SM for Wary 5.2.
Posted on 12 Aug 2011, 17:17 - Category: Wary - Comments - href="?edit=02397">Edit - Delete
The kernel PET (for Woof developers only) (29.1MB):
Wary 5.1.2 has kernel 2.6.32-40 and this is built in such a way that it identifies itself as version 2.6.32 and the modules are in /lib/modules/2.6.32. This latest, 2.6.32-44, has also been configured like this so identifies itself as 2.6.32.
The above potentially causes a problem when upgrading a pupsave file. Upgrading from 2.6.32-40 to 2.6.32-44 is not intended to be any problem, however I have configured the latter with inbuilt HID and USB drivers, which may make other modules incompatible. In other words, if you had compiled or installed a module compiled for the 2.6.32-40 kernel, it might not work with the 2.6.32-44 kernel, or it might. In future, I will keep the same configuration, so older modules will continue to work when the kernel is upgraded (to 2.6.32-45 etc).
I have edited the 'init' script in the initrd, and /etc/rc.d/rc.update to take care of some possible old incompatible modules when there is an upgrade of a pupsave, as described in previous paragraph.
Posted on 11 Aug 2011, 19:04 - Category: Wary - Comments - href="?edit=02395">Edit - Delete
Download from here:
The kernel is version 184.108.40.206, and if you need the source:
Us#er#na#me: pu#pp#y Pa#ss#wo#rd: li#nu#x
Note, my Telstra 3G connection is so poor recently. I uploaded the .iso file yesterday morning, then the Internet became unusable from about 3pm until 10pm, after which I completed the upload. Right now it is 3.45am local time.
To find out everything in this release, scan my blog. Note, it has SeaMonkey 2.2 -- I have some reservations about this on old hardware.
If you want to read about the last official release, 5.1.2, here is the blog announcement:
To read about the concept behind Wary:
Posted on 9 Aug 2011, 5:11 - Category: Wary - Comments - href="?edit=02390">Edit - Delete
Wary 5.2 will have many more package upgrades, and that is a bit further away.
There have been many improvements to Woof since the last upload, so I intend to upload Woof in a couple of days also.
Posted on 5 Aug 2011, 21:04 - Category: Wary - Comments - href="?edit=02386">Edit - Delete
Originally, I was thinking that glibc and gcc should stay at the same versions for the life of the Wary project, to help to ensure that packages stay working in later releases of Wary.
But, I'm not quite sure.
Glibc is currently version 2.10.1, latest in T2 is 2.13.
Gcc is currently 4.3.4, latest in T2 is 4.6.1.
The big question is, would bumping either of these packages to the latest version, break anything, in particular break any of the current collection of packages in the Wary repository?
I will send a pm to tempestuous, as I think that he know a lot about this topic.
Bumping glibc, and the libstdc++ in gcc, can break packages, especially libsdtc++. Yes, perhaps I should leave them at the current versions.
Posted on 31 Jul 2011, 20:52 - Category: Wary - Comments - href="?edit=02372">Edit - Delete
Yes, this is because Puppy 4.3.1 and Wary 5.1.2 were originally compiled from source in T2, and T2 is stuck on using a very old version -- 3.1.8. I just checked the T2 website, yep they are still using that old version (released in 2007).
I downloaded the latest, 5.2.12, and configured it like this (these are the recommended options for Linux):
# ./configure --libexecdir=/lib/dhcpcd --dbdir=/var/lib/dhcpcd --sysconfdir=/etc
Here is the PET (46KB):
Something is tugging at my memory about this... yes, I did compile dhcpcd 5.2.5 in Wary late last year. But, it wasn't put into Wary 5.1.2, must have forgot about it.
Posted on 15 Jul 2011, 11:14 - Category: Wary - Comments - href="?edit=02352">Edit - Delete
I'm running 2.2 right now. Starts fast, snappy performance. So, I reckon this will be in the next release of Wary.
But, if you want it now (16MB, 4.8MB):
I now consider Wary to be the "base system", and applications compiled in Wary should work in other puppies such as Lucid, Drake, Spup and Dpup.
Posted on 11 Jul 2011, 24:46 - Category: Wary - Comments - href="?edit=02343">Edit - Delete
I had hoped that I might be able to get Firefox and BlueGriffon to work together, sharing many common files, but that isn't so simple.
I compiled in Wary 5.1.2. I did install my libpng with animation PET, however the Firefox/BlueGriffon configure complained that is not suitable, so BlueGriffon is using internal libpng still.
Download the PET (14.9MB):
Here is the BlueGriffon home page:
Posted on 7 Jul 2011, 8:23 - Category: Wary - Comments - href="?edit=02338">Edit - Delete