site  contact  subhomenews

Service Pack, upgrade Wary 5.1 to 5.1.1

February 26, 2011 — BarryK
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.


Username: 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: [code]# run mdev to create device nodes echo "Creating device nodes" mdev -s[/code] 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'.

Does the 5.1.1 ISO upgrade a 5.1 existence
Username: GCMartin
"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

Does the 5.1.1 ISO upgrade a 5.1 existence
Username: GCMartin
"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?

SP 5.1-to-5.1.1 PET reuploaded
Username: BarryK
"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.

Tags: wary