Woof: Dpup Debian Squeeze progress

This post is some notes on what I'm currently doing.

I am using Woof2 to build an x86 Dpup, and using it every day to discover and fix any issues.

I am not doing anything fancy, just a build that uses as many Debian Squeeze .deb packages as possible rather than my own PETs -- getting ready for when I do an ARM-target build.

I know that there are others building Dpups. My Dpup would be a good starting point for other Dpup developers who will substitute many of their own PETs for more compact builds.

I do not intend to develop my x86 Dpup to an official release Puppy. The other guys who are building Dpups can do that (and have done). But, for the curious, I might upload one of my Dpup builds soon.

I am discovering some interesting things, for example the Debian Squeeze 'tar' utility gives error reports when it should not, so I replaced it with my tar from Wary.

Something that I will be looking at very soon is how developers can contribute to Woof2.


Posted on 7 Dec 2011, 8:47


Comments:

Posted on 7 Dec 2011, 3:03 by bigpup
loosing sound
Barry,

There is an on going issue with sound being lost in Lucid Puppy 5.2.8 and other recent versions of Puppy. Your input could help in fixing this bug.
A good example of what is being found is here:
http://www.murga-linux.com/puppy/viewtopic.php?p=587422#587422


Posted on 7 Dec 2011, 8:08 by BarryK
Re losing sound
There are major differences in how sound is detected in Lucid and all current Woof-built puppies. Lucid is built from an older version of Woof, after which I significantly changed the sound and module-loading logic.

Slacko is built from a recent Woof, so should have the same behaviour as Racy. Unless the problem is caused by something else.

I recall one problem, to do with /dev/snd, that was fixed in Woof, see this blog post:
http://bkhome.org/blog/?viewDetailed=02168

Regarding module-loading and sound differences of current Woof with Lucid, it goes back to my "zzz" PET merged into Woof in March 2011:
http://bkhome.org/blog/?viewDetailed=02163

I don't seem to have posted details in my blog, but with "zzz" (or soon there-after) I introduced a more dynamic way of detecting sound at bootup. My thinking was that if you boot from say a usb-stick on different computers, the sound hardware will be different, so sound really should be detected freshly at each boot. The pre-zzz way did not do this, it made assumptions after the first detection, so might not work properly if sound hardware changes.



Posted on 7 Dec 2011, 8:16 by BarryK
Re more about sound
I am trying to recall just what I did back then...

To help with automatic loading of modules and setting up sound correctly, I introduced this file, got from Ubuntu:
/etc/modprobe.d/alsa-base.conf

See also script /sbin/pup_event_backend_modprobe, changes around 2011-05-16.



Posted on 8 Dec 2011, 4:57 by playdayz
Disappearing Sound
Thanks Barry. As you say, Lucid is the last "non-zzz" Puppy. Maybe there is some virtue in having a landmark at that point in Puppy development. That was how it was tested at any rate. As you also have said, newcomers to Puppy should make their "first stop" at Slacko 5.3. This recommendation is displayed on the main Lucid 5.2.8 thread. However, there are still quite a few people using Lucid for day to day computing and many of them are pitching in on this issue--which is not widespread. In fact, it is easier to find people to work on the problem than to find testers who can recreate it! We have narrowed it down to something that changed between development version 526 and the release of 528. Cheers, Larry



Posted on 8 Dec 2011, 6:49 by BarryK
Re disappearing sound
We have narrowed it down to something that changed between development version 526 and the release of 528.

Ah, so it might not have anything to do with the "zzz" stuff.



Posted on 11 Dec 2011, 7:24 by pemasu
tar problem with dpup
I have also needed to replace tar binary with other working tar binary. I had to replace synclient and syndaemon from wheezy before my touchpad worked alright. Wget also didnt work right for me with some script. I dont remember anymore what app/script needed the wget change.