Woof uploaded, August 22, 2011

Commit number '20110822214018'.

This one needs testing, as there is major infrastructure change, see blog posts over last 5 days. Maybe someone could try a complete build of Slacko in Woof, starting from 0setup, then 1download, etc.

The previous upload of Woof was August 17, 2011:
http://bkhome.org/blog/?viewDetailed=02413

There was a blog post recently on how to download a recent snapshot tarball of Woof and use that as the reference to download Woof changes since then, without the full history:
http://bkhome.org/blog/?viewDetailed=02306

To download and use Woof, please read the Bones intro page:
http://bkhome.org/bones/
And the Woof intro page:
http://bkhome.org/woof/


Posted on 22 Aug 2011, 21:51


Comments:

Posted on 22 Aug 2011, 24:12 by mavrothal
rc.sysinit addition
Bummer, I just missed it :-)

I was wondering if it would be possible in the next woof to add the following in /etc/rc.d/rc.sysinit just before the end of the "LOAD KERNEL MODULES" section (around line 382) .

# Check if it is an OLPC XO and add the devices

ISITANXO=`cat /sys/class/dmi/id/product_name`
if [ "$ISITANXO" = "XO" ] && [ $UDEVVER -gt 150 ] ; then
udevadm trigger --action=add --subsystem-match="input" \
--subsystem-match="sound"
udevadm settle
fi


This is one change that would allow almost any puppy build to work properly on the OLPC XOs (provided that an OLPC kernel and specific packages are added)

I could do it manually of course, but hopefully is not too much trouble

Thank you


Posted on 23 Aug 2011, 7:49 by BarryK
OLPC XO
Ok, it is done. The next upload of Woof should be in a few days.



Posted on 23 Aug 2011, 7:56 by BarryK
Kernel choice in Woof
One thing to note about this release of Woof, the support/findpkgs script looks in file DISTRO_SPECS for the kernel version to be used in the build, variable DISTRO_KERNEL_PET, needs to know that to resolve dependencies that have linux_kernel version dependency.

So, in woof_gui, the kernel selection has been moved to the first tab, and when a selection is saved, it writes to DISTRO_SPECS.

However, if you are not using the GUI and running the scripts only, the kernel is still asked for in 3builddistro. Um, this morning I will fix that, move the kernel selection from 3builddistro to 0setup.



Posted on 23 Aug 2011, 7:58 by 01micko
running now
Hi Barry

I left all settings pristine.

1download is up to "geany"... been running an hour, no fails yet. usually takes me about 3 hours on average for 1download.


Posted on 23 Aug 2011, 8:03 by 01micko
re XO
Ah, nice about the XO.

I intend to do a woof build for that soon. Next woof most likely. Mavrothal already has SlaXO (tm lol) in the works!


Posted on 23 Aug 2011, 11:35 by BarryK
Woof broken
Well, I was half expecting it, with so many changes. I was testing a Wary build, found something broken in 3builddistro. Affects all Puppy builds.

Will fix soon and re-upload Woof.



Posted on 23 Aug 2011, 13:58 by 01micko
oh well
2createpackages ran through ok with one issue (my fault) I have gtrayicon but the entry in the common repo is gtrayicon_network, needs to fixed in PACKAGES_DISTRO_SPECS-Slackware-13.37 while your at it. Weird errors with hackinstall.sh, such as "chroot: command not found, line 82 hackinstall.sh" (and others, only caught the hackinstall one) when processing glibc.


Posted on 23 Aug 2011, 18:57 by BarryK
Woof fix
Yes, 1download and 2createpackages run ok, but you will run into trouble with 3buildistro, and you will have to do a "bones download" to sync with latest Woof upload that I have just done, August 23. Thanks for testing.

Those errors with "hackinstall", about missing "chroot" and "ldconfig" have always been there, perhaps you never saw them before.
Some Slackware post-install scripts try to run 'chroot' or 'ldconfig' and this is deliberately disabled as these packages are not being installed into a running system as they would normally be.
Nor are they being installed into a complete filesystem, rootfs-complete, each package is installed into sandbox2b individually and the post-install script run, so chroot and ldconfig cannot be used. There has never been any problem with this.



Posted on 23 Aug 2011, 19:22 by BarryK
slacko-hack
01micko,
Note also that you don't have to run your "slacko hack" script, as it is builtin, see support/slacko, and is called from 3builddistro.



Posted on 23 Aug 2011, 20:18 by 01micko
ok, got it
yeah figured that one :)

I'm running the whole lot (copied over compressed pets/txz/tgz dirs), will run 2createpackages and bed for me.

I reckon take Chris' advice and go see Red Dog! (I plan to soon)

Cheers