Service Pack, upgrade Wary 5.1 to 5.1.1

If you have Wary 5.1 installed, here is the easy way to upgrade to 5.1.1 (93KB):

...yes, a massive 93KB download!

One thing it does not do though, is fix the duplicate-listing problem of save-files at bootup, as described here: fix that, you need to download the complete 5.1.1 live-CD.

Posted on 26 Feb 2011, 8:26


Posted on 27 Feb 2011, 4:36 by Iguleder
Barry, I'm currently working on my own distro, while T2 is running I work on the skeleton and build system.

I found out that the best way to create device nodes in the initramfs stage is mdev (part of Busybox), the magic is "mdev -s" and that's it. The Puppy initramfs has many device nodes and it's hard to guess which ones stand for real devices once the system is up.

Here's a piece of code from my init script:
# run mdev to create device nodes

echo "Creating device nodes"
mdev -s

This thing is simply wonderful. You can even make it apply permissions and create links through a configuration file and everything is documented well. This could be useful if you want to create a device node that points to the partition Puppy booted from, etc'.

Posted on 27 Feb 2011, 6:32 by GCMartin
Does the 5.1.1 ISO upgrade a 5.1 existence
Does the ISO upgrade a WARY instance?

And, if it does, what would an advantage be to this PET vs the ISO path, especially when a reboot is required for validation?

Just trying to understand

Posted on 27 Feb 2011, 14:31 by Terryphi
Service Pack pet
GCMartin: The pet was provided for those who already have Wary 5.1 installed and appreciate a small download. In other words it is an alternative quick and easy upgrade. However, Barry says it does not fix the duplicate listing of save-files at bootup which some have reported. (I have not experienced that problem on my system.)

Posted on 28 Feb 2011, 15:26 by Sage
...are the other two comments?!

Posted on 28 Feb 2011, 15:28 by Sage
...odd! Add the above comment and the missing two comments suddenly showed up. Check on several browsers so must be a blog glitch.

Posted on 29 Feb 2011, 5:05 by GCMartin
Does the 5.1.1 ISO upgrade a 5.1 existence
The question was asked because I'm looking at a 122MB+ ISO with no problems and a 93+MB PET which could carry over a problem or 2.

The question is "Does this WARY ISO upgrade an existing WARY instance?" This is asked to determine which might be a safer approach to getting to a stable system that will bring forward past individual changes. That all.

Is my logic flawed on this? What might I be missing?

Posted on 1 Mar 2011, 14:50 by Terryphi
Service Pack pet
GCMartin: it is a 93KB pet - not 93MB! When Barry described it as 'massive' he was joking about how tiny it is. Although an Aussie he displays a very British sense of humour. (Oh yes, that is the way we spell humour.)

Posted on 4 Mar 2011, 8:13 by BarryK
SP 5.1-to-5.1.1 PET reuploaded
I fixed something in this PET and re-uploaded it.

When it installs, it updates DISTRO_VERSION variable in /etc/DISTRO_SPECS, however hat causes a potential problem at the next boot. One of the version tests in the 'init' script in initrd tests if version number in DISTRO_VERSION is not-equal to that in the wary_510.sfs file, whereas it should really test if the version of wary_*.sfs is greater-than. It can partially undo the upgrade.

I have fixed the test in init, from "-ne" to "-gt", but for now have changed the Service Pack to not change DISTRO_VERSION value.