Puppy Linux Discussion Forum

So... belatedly discovered that vanilla-dpup/woof-CE doesn't produce ISOs, so I'm having a go at the run_woof flow (vanilla-dpup was otherwise very easy to use, but only produces raw disk image outputs, which are a world away from an ISO image).

I'm running a fresh Ubuntu 24.04 VM, and have cloned run_woof. I'm accessing this VM over ssh, and building in a bash terminal. 24.04 (like, I think, every other modern Linux distro) has overlayfs in the kernel. run_woof_helper doesn't pick up on this, so I've manually edited run_woof.conf to set 'LAYER_TYPE="overlayfs"' (although I think the right setting might actually be 'overlay'). If I now run run_woof_helper, I get an option to select '1 other' with no explanation.

I'm clearly doing this wrong, but I can't find any instructions for run_woof_helper or the run_woof script itself. run_woof does have a usage function:

echo "Usage: $0 ISO|PUPPY_SFS DEVX_SFS SHARE [bashrc]"

Would someone mind filling in the details?

@dimkr should be able to fill in the details and how to manage a successful run.

My woof-CE fork doesn't produce ISO images because I decided I don't want it to. Running it with the run_woof wrapper won't change this.

Sorry, wasn't asking about that. The base woof-CE does claim to produce ISOs, and the builddistro script does include a lot of ISO-related stuff which isn't in your builddistro, so I was asking about that one.

A "regular" woof-CE run will produce a finished ISO.

Ok, I've got that, but my problem is that run_woof and run_woof_helper don't have any documentation on how to use them.

It has several dependencies, look at .github/workflows/build.yml for a list of steps you need to do before you can run woof-CE on an Ubuntu machine. Most important one is mkisofs or xorriso.

If you want to use run_woof instead of running woof-CE directly, you'll need to download a Puppy ISO so it can run woof-CE inside it.