My First Experiment with Woof-CE

[jaje]

Just thought I'd play around with Woof-CE yesterday, having never attempted it before. I have very limited knowledge, but I am interested in this type of stuff.
It took hours, but everything seemed to be going okay. When it got done with "./3builddistro-Z" I couldn't find a "woof-output" directory in the "woof-out_x86_x86_debian_buster" directory. (I tried the Debian Buster compatible distro).

I went through the steps 0-3, did I forget to do something? I did a search, but can't find an .ISO file anywhere.

One other question: On the Puppy Linux Woof-CE page where the procedure is described, it lists 10 compatible distros - when I did it, it only listed three: Debian, Slackware, and Ubuntu. Might this be a clue as to what I did wrong?

Thanks!

[rockedge]

Hello! Great you started giving woof-CE a run.

What did ./3builddistro-Z report when it completed? It sounds like the 3builddistro-Z script stopped or failed some where. Did you use the merge2out-gui script to set up the output directory?

The main thing is did the 3builddistro-Z scrpt complete it's run? HOw did 0setup and 1download 2setup finish? Error free?

What system are you running woof-CE in?

[jaje]

Okay, I am running it in Xenialpup (32-bit). I used the merge2out from the command line, not the -gui.

I just ran the "./3builddistro" step again, this time without the -Z (first time I used the -Z). Here are the last few lines. It looks like there are a few "404 Not Found"s. This was the case the first time also. I wasn't sure if it was normal:

Configuring ROX Filer...

pinstall.sh finished OK
Now setting /etc/os-release file

Installing HUGE kernel to build/
--2019-11-24 17:27:34-- http://smokey01.com/radky/Woof/kernel-4 ... er.tar.bz2
Resolving smokey01.com (smokey01.com)... 162.241.169.11
Connecting to smokey01.com (smokey01.com)|162.241.169.11|:80... connected.
HTTP request sent, awaiting response... 404 Not Found
2019-11-24 17:27:35 ERROR 404: Not Found.

--2019-11-24 17:27:35-- http://smokey01.com/radky/Woof/kernel-4 ... er.tar.bz2
Resolving smokey01.com (smokey01.com)... 162.241.169.11
Connecting to smokey01.com (smokey01.com)|162.241.169.11|:80... connected.
HTTP request sent, awaiting response... 404 Not Found
2019-11-24 17:27:35 ERROR 404: Not Found.

root#

Thanks for responding!

[Terry H]

The kernel your build is trying to download is 4.19.56-buster, it no longer exists in the radky's repository. Try using the download from this repository for kernel 4.19.74-buster, which does exist in the repository.

[rockedge]

Hello jaje,

I agree with Terry H. The script is attempting to download a kernel that is no longer available on that repo. You must select kernel 4.19.74-buster. The errors caused the script to stop, so no iso was produced or any of the output files and directory.

You are close to success, I think it will work with Terry H's suggestion.

[jaje]

How do I go about doing that? Should I download it from:

http://smokey01.com/radky/Woof/kernel-4 ... er.tar.bz2

(The above address with 74s replacing the 56s.)?

Or do I alter a line in a script somewhere?

Thanks again!

[Terry H]

I haven't attempted to use wood-CE in a long time, so I can't advise how to proceed. You can directly download from the repository.

[rockedge]

Download the huge kernel file directly.
http://smokey01.com/radky/Woof/kernel-4 ... er.tar.bz2

use merge2out again create a new output directory

Open up the directory /woof-out_x86_64_x86_64_debian_buster64 (in your case 32)


you will see the directory /huge_kernel

copy the downloaded kernel file to this directory

now start with ./0setup and continue on until finished. The build process will include the kernel.

[rockedge]

Also there should be a prompt somewhere along the line during the manual process, that allows selection of a kernel.

[peebee]

You can set the kernel url in _00build_2.conf

KERNEL_TARBALL_URL=http://smokey01.com/radky/Woof/kernel-4 ... er.tar.bz2

also github update request:
https://github.com/puppylinux-woof-CE/woof-CE/pull/1676

[jaje]

Okay, that sounds good. I tried running it through the night with the same result - it still looks to download the old kernel.

I would just add that line to _00build_2.conf, right? And that would override the following line in _00build.conf, if I understand correctly?

## Kernel tarball URL - avoid being asked questions about downloading/choosing a kernel
KERNEL_TARBALL_URL=http://smokey01.com/radky/Woof/kernel-4 ... er.tar.bz2

[rockedge]

Yes that is correct.
Also you could download woof-CE again or clone woof-CE using git, which should reflect the correct path...but changing it manually is pretty easy as well.

[jaje]

Hey, it worked! I let it run and woke up through the night and checked and there was the ISO, right where it should be. I booted it with ISOBooter and it came up with no problems at all.

Edit: All I did was make the above change manually this time. I'll try downloading Woof again later.