Woof uploaded, May 6, 2011

The last upload of Woof was on April 16, 2011:
http://bkhome.org/blog/?viewDetailed=02219

This latest upload is commit '20110506184859'

Please note that this release is not suitable for building Lucid Puppy 5.2.5+. We have yet to merge the changes. In the meantime, if you do want to build Lucid 5.2.5, please see this blog post:
http://bkhome.org/blog/?viewDetailed=02234

...note though, it is an older Woof, with some customizations specific to the Lucid 5.2.5 build.

For introduction and instructions to download Woof, go here:
http://bkhome.org/woof/

So, if you have previously downloaded Woof, all you have to do this time is run this in the Woof project directory to update to the latest Woof files:

# bones download

Bones also has a GUI, just type "bones<RETURN>".

It is preferable to download Woof with the full history, but people on dialup or otherwise limited download capability, a tarball without history is available (17MB):
http://bkhome.org/bones/woof/archive/woof-20110506184859.tar.gz

fido
If you build a puppy with Woof and don't want the 'fido' non-root option, open /etc/rc.d/rc.shutdown and remove or comment-out the dialog that asks whether you want to run as administrator or fido. That's all, then your pup will work as per normal, as root.

You will notice that some scripts, such as /usr/sbin/pmount, have an extra line at the beginning:

[ "`whoami`" != "root" ] && exec sudo -A ${0} ${@} #110505

...that does nothing when you are running as root, so leave it there.


Posted on 6 May 2011, 23:44


Comments:

Posted on 7 May 2011, 5:20 by Iguleder
Suggestion
Barry, can you create a separate repository for all the Puppy-specific or "special" packages, such as mingetty, autologin, 915resolution, usb-modeswitch, desk_icon_theme_*, etc'?

You stated previously that you intended to do an overhaul in the "-woof" repository and I think it could be a good idea.

The main reason I believe this is a good thing is the fact each Woof-built Puppy takes those packages from various repositories. This can be problematic - for instance, if gtk-ctheme is in the 4 repository and a user wants it, he or she has to add that repository to DISTRO_PET_REPOS.

At the moment I'm doing a T2 build and I want to build a tpup for experiments, pretty much like Quirky. It seems that T2 misses some of those "special" packages, that's why I'm writing this comment.

I'd like to have some repo available with either static versions of all those packages (compiled against recent GCC and dietlibc) or ones that were used through Puppy's history (like 4's gtk-chtheme), to be used with my T2 packages and future Woof builds of Puppy developers.


Posted on 7 May 2011, 8:07 by BarryK
Re generic pkgs
Iguleder,
Yeah, that has been on my to-do list for sometime. I have just been lazy. I have just been bunging such PETs into the Quirky repo (folder pet_packages-quirky), as the PET search order in Woof looks there first.

I had a note in my notebook, I'll make another reminder.



Posted on 7 May 2011, 8:50 by technosaurus
essential pets
I've had pretty good success porting apps into busybox applets ... did most of the additional binaries that were in the 4 series initrd already. If any have been changed let me know & I'll add them to my todo.


Posted on 7 May 2011, 11:37 by TazOC
to change back to root
Hi Barry,
I know you asked not to post bugs on fido, but this one has an easy fix: in /usr/sbin/loginmanager I think the sed command at the end needs
' /etc/inittab' appended or users might not be able to change back to root...
sed -i -e "$rootEXPR"



Posted on 7 May 2011, 13:53 by BarryK
/etc/inittab
TazOC,
Oops, fixed. Thanks.



Posted on 7 May 2011, 24:49 by TazOC
Thanks for fido
Thank you for developing fido. One key feature missing from multi-user in Lighthouse was prompting for the root password so an unprivileged user can run a root task. I see how you've done this with fido, so if and when I work on multi-user in Lighthouse 64 that will be helpful.

I will see if wcpufreq needs a 'fido-friendly' update, and remove /home/spot from the package.

Thanks again Barry,
TazOC


Posted on 8 May 2011, 2:19 by pemasu
10alsa
From forum post, which I copied
http://www.murga-linux.com/puppy/viewtopic.php?p=520528#520528

About alsa sound level problems. Stu90 pm me and I searched the problem based on stu90 innovation.
The first part of the script does not work in Barry`s 10alsa script. 525 has alsa script which is quite the same from the innards. It has the same problem with these first code rows:
case "$1" in
start|restart)
Code:
#!/bin/sh
#Barry Kauler april 2009, puppylinux.com
#110113 tweak delay. 110216 tweak delay.
#110506 /usr/sbin/alsaconf has 'restart' option, might need to reprobe modules. for now, just 'start|restart'.

case "$1" in
start|restart)
rm -f /var/lock/subsys/alsasound 2> /dev/null #or alsa will not start.
modprobe snd-mixer-oss
modprobe snd-seq-oss
modprobe snd-pcm-oss
for I in $(seq 4); do #110111 shinobar: for reliable sound detection on HP Compac nc4010.
sleep 0.5 #110113 reduce 1 to 0.5. 110216 move up.
[ -c /dev/mixer ] && break #note, /dev/mixer is deleted in /etc/rc.d/rc.sysinit.
done
if [ ! -f /etc/asound.state ];then
amixer -s -q <<EOF
set Master 75% unmute
set Master -12dB
set 'Master Mono' 75% unmute
Snipped off............
EOF

else
alsactl -f /etc/asound.state restore #from /etc/asound.state.
fi
;;
stop)

Cut of the rest of the script............

Removing the first 2 code rows makes the sound level to be leveled as it should according to the script.
Now it would need that script wizard to tell why Barry`s first rows make the script non working.
So, the fixed script should be easy to create.
Playdayz alsa 1.0.24 packages has alsa binaries in different location, under /sbin which needs to remembered if people updates to it. /usr/sbin/alsactl for example does not work in scripts with newer alsa. just alsactl works fine of course.


Posted on 8 May 2011, 8:27 by BarryK
Re 10alsa
pemasu,
I have no idea why removing those two lines would fix anything. If it does, it indicates something is wrong elsewhere.

10alsa is called at bootup with the 'start' param:

/etc/init.d/10alsa start

And the case-statement in 10alsa is required.

However, the Alsa Wizard is another story, it may have problems with 10alsa. Are you specifically referring to problems when the Alsa Wizard is run?



Posted on 8 May 2011, 9:07 by 01micko
filtering out drivers
Hi Barry
I think there should be some code (perhaps in /etc/rc.d/rc.update) that filters out wrong kernel version drivers from PPM. It wouldn't be much code I think, just a quick kernel version test and sed out the offending lines in $HOME/.packages/Packages-puppy-*-*. Would be a bit more newbie friendly I think.


Posted on 10 May 2011, 9:10 by 01micko
0setup bugfix
Hi Barry
Just a couple of bugfixes for the slackware branch of woof in 0setup.
When the database conversion was happening lots of "+PACKAGES" entries were getting through to the Packages-slackware-13.37-* files. I put in a filter to remove those.
Also, in some of the entries in PACKAGES.TXT there is often a pipe (|) char in between "cxxlibs" and "gcc" using PACKAGES.TXT from salix, as slacky is a bit slow to update, which resulted in an entry "+cxxlibs+gcc". I put in a preprocess removing "|" chars from PACKAGES.TXT. Does no harm if and when slacky.eu update.
The important one is the "+PACKAGES" hack.
File here:
http://www.murga-linux.com/puppy/viewtopic.php?p=521296#521296


Posted on 10 May 2011, 15:21 by BarryK
Re 0setup
01micko,
Thanks for that, I have put it into Woof.



Posted on 12 May 2011, 20:04 by 01micko
thunar.desktop file in woof???
Hi Barry
I got a report of Thunar in the menu in the latest spup. I was bamboozled!
Turns out there is a stray thunar.desktop file in ./rootfs-skeleton/usr/share/applications/. It's right there in a pristine woof straight from bones.
Cheers



Posted on 12 May 2011, 21:53 by BarryK
Re thunar.desktop
Er, yes, delete that.

You will find some other new entries in rootfs-skeleton/usr/share/applications, such as pupzip.desktop, petget.desktop. These provide send-to support for Thunar (if installed), they don't appear in any normal menu.

However, Thunar.desktop got there by accident.

Notice also usr/share/applications/defaults.list, also used by Thunar.

I put these files into Woof, as they may suport mime-handling and application launching for other apps as well as Thunar.