Wary schedule

Just to let everyone know what is happening...

I am mighty pleased with the latest Wary. It is now 2am and I have been working on it since 6am the previous day, with a small break for lunch and a short siesta.

Better sleep now, but after I get up, I have a shortlist of things to do, further testing, then probably upload about 12 - 18 hours from now.

After releasing this Wary, which I will give version number 0.9, I will open discussion about how Wary fits into the "scheme of things".

Posted on 8 Oct 2010, 3:06


Posted on 8 Oct 2010, 4:26 by adi
Puppy official release
Will wary be a puppy official release? And if so it will have 5.2 number or it will be a fork with 1.0 number...

Posted on 8 Oct 2010, 8:03 by BarryK
Re open discussion
I don't want to venture into discussing this until you guys have played with the new Wary and evaluated it.

A couple of comments though. I chose the name "Wary" as this is in many ways a conservative Puppy, and the main aim is to run well on older hardware.

As to numbering, and whether it will be released officially, probably 5.0, and yes, likely to be an official release. This is all perhaps, after we have discussed it.

I kind of see this as niche area to keep my hand in, supporting older hardware.

Hmmm, I am starting to discuss this already...

Not long to wait. I'm doing lots of testing today, before uploading.

Posted on 8 Oct 2010, 8:04 by Raffy
"Official" Release
I guess that whether it's called Wary Puppy or numbered 0.9 won't matter. Its attributes would be what Puppy should be (as you defined), so it will be a welcome development to users.

Posted on 8 Oct 2010, 14:33 by Terryphi
Long Term Support?
It seems incongruous that 'conservative' Wary has the later Linux kernel while 'cutting-edge' Quirky has an older one. There is also the question what exactly do we mean by 'old hardware'?

I would like to see a Long Term Support version of Quirky or Wary which sticks with a tried and tested kernel and just gives users the opportunity to upgrade programs when available - if they want to.

Posted on 8 Oct 2010, 15:39 by mavrothal
geode 2.11.9
Looking at your sources I see that you are up to xf86-video-geode-2.11.8.tar.bz2.
However, xf86-video-geode-2.11.9 offers up to 10fold speed improvement!
Any chance to be included in Wary 0.9?

Posted on 8 Oct 2010, 16:24 by Raffy
Forum Thread
Tronkel put up a related forum thread.

Posted on 8 Oct 2010, 16:58 by BarryK
Re xf86-video-geode
Well, latest Wary has xf86-video-geode 2.11.3.

It will be necessary to experiment later, compile and test later versions of many of the Xorg drivers, find the most recent drivers that will work with the xorg-server

I think it was Patriot who has done this already for Puppy 4.3.1 -- somewhere in the forum. The drivers that he compiled should also work in Wary 0.9+.

Posted on 8 Oct 2010, 21:18 by technosaurus
easy ram usage reduction
I reduced RAM usage by 8-10Mb by simply making a separate uclibc busybox binary for the always running processes:
getty, {k,sys}logd, init ... its only about90kb uncompressed so it seems worth it.

they can be named anything as long as the symlink has the proper name so you can use as many as you'd like - I just put all the daemonized processes together for convenience.

Posted on 8 Oct 2010, 23:18 by BarryK
re ram reduction
Yes, I saw your forum post. That is extremely interesting, and would be good to put into Wary. Will check it out after 0.9 released.