This pup is still classified as beta, not yet for mass consumption, but hopefully getting very close to an RC.

I have built it with an interesting twist this time. It has a "zrdv" file, 'zw096114.sfs', however the main .sfs, 'wary_096.sfs', has all the kernel modules that most people would need -- about 4MB (compressed) of them. Another 18MB are in the zdrv, but they are exotic and less-likely-to-be-needed modules, such as the analog dialup drivers.

What the above means is that you can leave out 'zw096114.sfs' and Wary will still work. So, install to Flash, hd or whatever and delete the zw096114.sfs, and you probably won't even miss it.

Another twist to the above, I also built Wary with the SCSI drivers in the initrd.gz, so this Wary can boot off ye old true SCSI drives (and of course mount them).

It is not mentioned in the filenames, but this Wary is built with the 2.6.31.14 kernel, my new "standard" kernel for the Wary series.

Posted on 7 Nov 2010, 15:55

Comments:

Posted on 7 Nov 2010, 17:21 by BarryKWary 096 forum feedbackI have started a forum thread for feedback:

Posted on 7 Nov 2010, 17:30 by DaveSAll GoodAll good so far. Great to be able to do a minimal install without modem drivers, this is a great feature.

Posted on 7 Nov 2010, 18:56 by tempestuousmissing SCSI driversAh, SCSI, very timely. I discovered on the forum just recently that the Puppy kernel has a major gap in its otherwise extensive SCSI driver support: the "Fusion MPT" SCSI drivers are not enabled. These devices are quite popular in the SCSI world, and are found on many older motherboards as onboard SCSI controllers. The relevant kernel configuration is found at
Device Drivers > Fusion MPT device support
Once this setting is enabled, the sub-menu then allows the following 3 SCSI modules to be built: mptspi, mptfc, mptsas.
And this will change the kernel image, itself. I don't think the size difference will be much.
It's unfortunate we didn't discover this earlier, given the latest Wary kernel seems quite settled, with its 3rd party dialup modules.

Posted on 7 Nov 2010, 19:05 by SageDownloading......is stalling at ~42Mb every time from ibilio, this morning! Mirrors desperately needed.
[Dashing down to Perth to catch the cricket?! Oz & Kiwis doing rather well over here with the oval ball.]

I had to set pdev1 to something fake (It's ignored anyway with pmedia=usbflash, right?)

This only works with a "humongous" ISO, and there is probably no advantage of booting Puppy this way instead of a frugal install in a subdir, but I thought it was an interesting thing to do :)

Anyway, thank you for the new release.

Posted on 7 Nov 2010, 19:47 by SageDownloading - repriseSuccess. The all-wired exchange-box is just too fast around here, especially on a Sunday morning. Re-routed through an old slower network hub and this throttling seemed to work, albeit taking four times longer. Mirrors are still a good idea, though.
So - there you have it.

Posted on 7 Nov 2010, 20:37 by SageStuffDid you switch off 'woof woof'? Critical for testing systems. Otherwise, sound seems OK.
Agree with Terryphi - let's keep this thing in the family! Nobody over here would object to defaulting to Oz settings.

When I ran the Video upgrade wizard it only recommended that I install the Mesa dri had a Internet connection so click to install and when it got to the end said that something had gone wrong and it did not install.

Posted on 7 Nov 2010, 22:03 by drblock2geany and nico problemsBlindly fast, upgraded my Wary 090 pupsave file without incident, everything seems to work except:
The Geany bug (absent from 'Wary 090) is back. Geany will not open files on remote drives mounted with smb/cifs.
Nico edit closes summarily when you try to open or close files.

Posted on 7 Nov 2010, 23:20 by SageNo installer?The Universal installer doesn't appear to work - it shows all partitions as /sdaGUID ?? Is this an HW issue? with this disc?

Posted on 7 Nov 2010, 23:50 by SageNo installer?Must've been an artifact of HD. Wiped entire disc with low level utility. Everything working now except 'woof woof' at start up.

Posted on 7 Nov 2010, 23:50 by SageNo installer?Must've been an artifact of HD. Wiped entire disc with low level utility. Everything working now except 'woof woof' at start up.

Posted on 8 Nov 2010, 3:39 by rudytalsa broken againalsa never worked on my Panasonic Toughbook until Wary 090, then broke again in 094 and 096. Modules load OK (snd_intel8x0), but alsaconf fails with:

I used CFLAGS="-Os -finline-small-functions -findirect-inlining -finline-functions-called-once -march=i586 -mtune=i686" (I know -march=i486 is preferred, but really those need something even lighter than puppy these days)

Speaking of low resource machines, if you are ever looking for an ultra-lite window manager, try mcwm - it only needs xcb and xcb-utils (no libX11) - resource usage was only 1.5mb with shared glibc and xcb (it would be much less with static uclibc base and make a good fall-back wm)

btw with the recent split of gdk-pixbuf, all of gtk's dependencies can be built on xcb, but unfortunately the gtk-xcb fork has been dead for 4 years :( really sad, it could really speed things up and cut out 1MB of dependencies - I tried building all the dependencies first and then x11-xcb , but the gtk configure script fails because it uses -lpango-1.0 to test for X11 (not sure why)

But, I don't want to know about it just now. My to-do list has got a bit long, and I don't want to tackle anything other than what is really essential for awhile. Best to wait until I have got Wary 5.0-final out, then there will hopefully be time to tidy up a few things like that.

Posted on 9 Nov 2010, 5:24 by adion line storageI started to use dropbox in order to move from an os to another while having access to the same preferred files stored on line. Dropbox (www.dropbox.com) has its own installer for different operating sistems. Could it have a pet for puppy?. It can be accessed in browser too.

Posted on 10 Nov 2010, 10:38 by rudyt[FIXED] alsa broken againHappy to report an explanation for the alsa problem I reported a couple of posts above. It seems that the auto-upgrade of my warysave file from 090 to 094 broke alsa, because when I tried 096 from a clean slate (i.e. no warysave), alsa works perfectly. Hope this helps narrow down the problem.