Woof Alpha2

[big_bass]

Note about runnign woof from other distros:

In the README.txt of the woof alpha2 archive, Barry sayd we can build woof on other versions of linux providing we have the dpkg-deb in /bin and lzma in /usr/bin.

The download script calls for pet2tgz however to deal with pet packages, which is puppy specific. Am downloading now in Ubuntu, and of course I don't have it. So I pulled it from a puppy sfs file, along with truncate, the program Barry wrote to go along with it. Download is working fine now. Would be good to put this in the docs for the next woof release.

~dinky

Hey dinky

I don't use ubuntu but
I do have a puppy package build environment on slackware 12.1

since there are no how to s
you will need to step though each line of script and see whats called

in my case I had to recompile the kernel for squashfs support
and also add scripts to handle sfs and 2fs
also note some scripts are called that are used only on puppy
and others are installed in different locations so you may need some symlinks too


you may run into problems if any modules are built with a different kernel
so you need to know how to hack around that
that one took me a few days to figure out

aufs and unifons may be called

but that could be made as just a standard folder

the burner setup will have to be adjusted to your system


but anyway that's just some of what I went through

hope that can be of some help

I already had this set up for a few months as I was compiling
package from source on slackare then converting the packages to pets
there arent many around here doing this sort of stuff

so its a lonely road I just found out yesterday that my USB memory is large enough
but my RAM isnt so I have to build on slackware 'cause I was running out of RAM space

I will let you know what snags I run into the package part I had worked out
and the building of the packages

~dinky don't forget that hack I added to 2createpackage or you'll be building a few extra times : D

big_bass

[dinky]

Thanks mate, sounds like there is some more documentation that needs to be made for that feature... for now I'll stick with building woof from inside puppy. On that note, once I've made a version of woof once, can I make another one without having to download everything from scratch, then run the scripts again? Seems like the documentation points to this being able to be done, however when building from unleashed I ran into troubles if i didn't start from scratch again... anyone have any thoughts on this? Cheers.

~dinky

[Lobster]

I've made a version of woof once, can I make another one without having to download everything from scratch, then run the scripts again?

Yes. If you have the files on your hard disk for a particular version a new Wooflet/Puplet is made from those files. I should imagine that autochecking and updating only those files outdated will come later - remember we are not even into beta with Woof . . .

[dinky]

Ta. found that script. Basically copies all the pet packages across, then the static scripts used to build it.

~dinky

[sue]

EEE 900A -
upup runs very nicely.
It found the non-std atheros wifi out of the box - yay! one less pet.
gparted fails due to missing libgtkmm-2..4,so.1; used fdisk.
Probably what extra-modules is for.
lI loaded the roxfiler pet - thanks!

Toshiba Satellite E105 - my new lappy
Still no joy on Intel video. xvesa goes into an infinite loop, and xorg goes black. Same problem with about ten other puppies and two weeks of failed forum fixes. Finally got it working with latest lxde, so I can get back to woof!

[dinky]

Hi Sue, any luck with compiz-fusion on the eee? I've been trying to get it running on my 701, without much luck. Been difficult to install anything from the package manager... I'm trying a cutom build now (or will when it finishes), with the idea of installing apt or synaptic so I can graphically see what I'm doing. The package manager is a great step, but still too basic. Any thoughts on this?

~dinky

[sue]

Well, I thought it was running nicely.
/tmp/xerrs.log says "Could not load i910_dri.so; using SW acceleration".
I checked /lib/modules and /usr/X11R6/lb and couldn't find it. devx and extramodules didn't have it either. Any ideas?

I'm building apup right now. As soon as it finishes, I'll switch back to upup. upup should be able to run ubuntu's compiz-fusion directly, w/o a custom build. That's the whole point of woof. Of course, if ubuntu patched the kernel modules, then it won't work. Is that your custom build?

A thread on ArchLinux says compiz is leaking memory.
http://bbs.archlinux.org/viewtopic.php?pid=516854
I wouldn't trust fusion to run correctly until that's fixed.

[dinky]

Not fussed about leaking memory, haven't found this to compromise performance. Puppy isn't created by default to support compiz-fusion, and support for dri is disabled in the xorg.conf script. You'll need to change that. Single line near the beginning of it, I think. As far as I know, xorg 7.4 autoconfigures xorg to work with compiz-fusion... this is untested for me though.

Also, in puppy 4.1.2 (and all other puppies) xorg is cut down to what's needed for puppy.... in the puppy 4 series we had to install the full xorg_dri package to get compositing to work. Not sure how Barry has built woof, but stands to reason some of xorg is left out. Wow has gotten compositing working under xcompmgr with his unnamed pupplet, and has posted up all the packages he's used in xorg 7.4 to get this happening. He's using a patched Ubuntu kernal, so am assuming it's Ubuntu packages he's used for xorg, but not positive. In any event, we can probably look at what he's done, and make sure to include the same things in the next woof build... something to try anyway. Perhaps none of this is necessary if in woof alpha 3 (out in a few days, according to Barry) the pakcage manager works so that we can just tell it to install compiz-fusion... however we might need to do other stuff first. Good luck.

~dinky

[big_bass]

progress report

I first tried woof alpha 2
USB and was a no go because
it wouldnt chroot into /sandbox3/rootfs-complete even after I overcame some snags with USB and RAM


so.... I cleaned up my hard drive made some space and did a frugal woof install from the official cd

proceed to build woof alpha2
and all the packages were downloaded at least there were no
error reports *and I did try this several times * I opened each folder in packages-spup
and everything seemed fine there
but I got the same error about chroot in script 3

so....I discovered that /lib and /usr/lib
were not complete in /sandbox3/rootfs-complete
since I had a final CD to compare with
for some reason /lib and /usr/lib
arent complete thus bash cant run the new chroot



then I copied everything over manually ...
I did some chroot environments before they are tricky to troubleshoot
and that fixed the chroot problem
but that wont help me with a custom build in the future

well I am hard headed at times when I want something to work
so I deleted everything and tried woof 1 alpha instead
all the packages downloaded but I got hung up at the chroot in the third script called 3builddistro again

I will wait for alpha3
and I will go at it with the same energy
I really like where you are going with woof
and I cant wait to build again
I know you are still in alpha
and I usually don't do alphas unless
it really gets my attention


I am using woof alpha 2 official live CD
I just want to build it too

updated post in blue text for clarity
big_bass

[BarryK]

I will probably upload alpha3 on 23rd or 24th of March.

[big_bass]

I am running some tests for clearing up caches

after the problem I had with USB and RAM forced me
to look for some other options

I dont know all the hoops info goes though before getting to
the save file so I posted what I did here
so that you could take a look at it

this is just a simple script I manually click

big_bass

[dinky]

This may have already been noted, but the puppy package manager is broken in Ubuntu woof version of alpha 2. Neither the intrepid main or intrepid universe repositories work. I've tried several times booting into ram, as well as with a save file. Happy to debug this through the console, but what command do I run to see what's happening? Also, clicking on a deb package doesn't work to install it. I'm told it's installing, but nothing happens. (when the deb package is on my local computer. Hoping this issue are fixed for the next release.

~dinky

[big_bass]

hey dinky

BarryK commented that he was re writing 0setup using vala

because ubuntu was taking a long time format the "package.txt"

for the woof build using bash


I dont use arch or ubuntu but it is good that others do
so there are more testers *I don't use them because I spent so much time tying to figure out puppy and slackware* not because I have anything against them they are still linux

funny thing I was looking for some code snippets today
and I found some good info in ubuntu

arch also has good documentation
I did a diff of the woof alfa 1 and alfa2 there were many changes
better to start over clean the first time around

then when you get a successful complete build
modify what ever you wish

here is a simple code snippet I made for checking the "on"
packages

Code: Select all

!#/bin/sh
#find on packages woof
#big_bass
grep 'yes|' /root/.packages/DISTRO_PKGS_SPECS| cut -f 2 -d '|'>/root/packages_on.txt
geany /root/packages_on.txt

console for launching petget on woof

Code: Select all

/usr/local/petget/pkg_chooser.sh

big_bass

[dinky]

Thanks mate, that will come in useful. For now I'll stick with the Intrepid build... it's using the latest xorg, and I'm able to test certain pacages on my desktop system... be great to try some of your slackware work when it comes along. I look forward to trying those scripts.

Alpha 3 is out! Yay!!! Get it here:

http://distro.ibiblio.org/pub/linux/dis ... of-alpha3/
I also recommend seeing the recent posts on Barry's blog, as he describes this release in several posts:
http://www.puppylinux.com/blog