site  contact  subhomenews

Woof uploaded October 29, 2010

October 29, 2010 — BarryK
This is the version used to build Wary 0.9.4.

For introduction and instructions to download Woof, go here:

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>".


Building Wary
Username: Grumpywolfe13
Hi Barry I was playing with the Wary5 build with woof and was able to build Wary-094 but when I tried to boot it I got this when trying to start xwin. [code]lib/modules/ lib/modules/ no dir found[/code] Any help if you please

Checked wary_094.sfs
Username: Grumpywolfe13
"Should of checked this before I posted. Check in the wary_094.sfs and found that all the kernel drivers and there dirs are not in lib/modules/

Woof problem
Username: playdayz
"A new version (luci-234) built just now with the latest bones download had the same problem as previously. When it booted it left a blank line after Searching for Puppy Files and then it somehow found one and proceeded to update it. The luci-234 files were in a directory with no save file. If I tried to boot pfix=ram then it also skipped a line after searching for Puppy files, but then went on to Setting up layered file system, after which there was Dumping last lines of /tmp/bootinit Three lines Dumping last lines of kernel log Three lines

checked again
Username: playdayz
"This time I did not receive the same error message while building the distro as on the previous Woof, but I did it again and got the same results as above. I then built with an older Woof and did not have the problem.

Rebuild it again
Username: Grumpywolfe13
"Ok rebuilt it again but when I got to this part [code]Would you like to delete all the 'modules.*' files in lib/modules/ This means tht 'depmod' has to be ran at first boot, but that is usually ok. Those files occupy 600KB - 2MB uncompressed Press ENTER only to delete them:[/code] of the build procces just hit return and not to keep the modules. It booted but had to use xvesa for xorg would not work not error message.

SFS files inside initramfs
Username: steve p
"Hi Barry I was playing around with having SFS files inside the initramfs today. The reason this feature interests me is because it would allow directly booting Puppy from the ISO image using Grub4dos' ISO mapping feature. The main SFS file is loaded fine, but zdrv.sfs isn't loaded. If I extract the modules from zdrv.sfs and put them in the initrd.gz, they're copied into the layered filesystem on boot and everything works fine, but simply putting zdrv.sfs inside the initrd doesn't work. Is this a bug, or is zdrv.sfs inside the initrd just not supported? I also had to create a file called 'vmlinuz' containing the 16 byte id string (I guess puppy uses this to figure out which drive you booted from?), then booting the Puppy ISO with Grub4dos worked.

re home
Username: BarryK
"After I get back home, in a day or so, I'll see if I can reproduce these situations.

Username: Grumpywolfe13
"Barry I can conform of the download failures I found that you can only get the files from I myself have not been able to get woof to keep that url in the download file. I had to download by hand to build my Wary and it is not working like yours, I am running your Wary-094 and I like it.

Tags: woof