Official Woof-CE Puppy Linux build system

[RSH]

@dimkr
Wouldn't it be better included into the zdrv then?

[RSH]

Woof-CE merge2out addition.
viewtopic.php?p=124099#p124099

[dimkr]

@dimkr
Wouldn't it be better included into the zdrv then?

What? Firmware?

[RSH]

Yes.

[dimkr]

Somebody decided long ago that they should be in two separate SFSs. On the one hand, this makes sense because you need a compatible set, so it makes sense to tie them together. On the other hand, some replace their fdrv because the stock one misses some firmware they need (or they want to minimize the contents of fdrv), and having two separate SFSs means that if RAM is too low to copy both kernel modules and firmware to RAM, maybe RAM is sufficient for the SFS with kernel modules. It's a classic monolith vs. modular dilemma.

[rockedge]

We have used many variants of the fdrv SFS from Puppy Linux directly in Kennel Linux kernel setups. I've personally swapped in and out fdrv's until one worked with the firmware combination that particular machine needed to operate properly. So with KLV's the modular kernel is useful.

But KLV can also use the native Void Linux kernels that have the zdrv extracted during the system build to stay inline with the modular kernel design so we can use Puppy Linux type huge kernels or use the Void Linux kernels. This is in the initrd design from @wiak who has shared the scripts to do the kernel extraction after the build script run is completed that included the Void Linux kernel.

Puppy Linux still can use either modular or monolithic kernels which is a strong point.

I have used the woof-CE firmware picker script on a Void Linux firmware extraction to bring that down from just 400 M to around 100-110 M and produce a fdrv that worked. I didn't like including it in the ISO for KLV-Airedale or KLV-Spectr due to size limit goals.

[Jasper]

Is it possible to create a new build with a Ubuntu derivative?

I was thinking of Rhino Linux which is a rolling release Ubuntu-based distribution with Pacstall & XFCE at its core.

I have not tried this OS, but was intrigued as it is a rolling release and @peebee already has worked with Void which is a 'rolling release'.

I see the default Slackware, Ubuntu, Debian, Devuan and Void 'working' options.

I see that @mistfire has created a Manjaro hybrid.

[rockedge]

I was thinking of Rhino Linux which is a rolling release Ubuntu-based distribution with Pacstall & XFCE at its core.

interesting proposal!

I need to polish KLV-Boxer before anything else but it is something to look at.

[peebee]

Is it possible to create a new build with a Ubuntu derivative?

I was thinking of Rhino Linux which is a rolling release Ubuntu-based distribution with Pacstall & XFCE at its core.

I have not tried this OS, but was intrigued as it is a rolling release and @peebee already has worked with Void which is a 'rolling release'.

I see the default Slackware, Ubuntu, Debian, Devuan and Void 'working' options.

I see that @mistfire has created a Manjaro hybrid.

Yes - as long as Rhino Linux has either its own complete repos or possibly a repo for the addons for Rhino

but........... it is only interesting to use Rhino as the base if you are going to include some components specific to Rhino - otherwise you might as well just use the Ubuntu that Rhino is based on - which is??

[Jasper]

@peebee

My thinking was that Ubuntu is working as a base and therefore this should follow the same (fingers crossed).

The introduction of a different desktop environment Unicorn might pique some interest............... it's very purple

I have seen earlier builds utilising XFCE and know that this could be possible eg Fussili-XFCE-F96-CE. Also, I know that you have had some experience with working with XFCE

So, those two steps potentially could work.

Finally, the introduction of using Pacstall might be interesting for people who want to add additional repo's on GitHub & GitLab alongside the existing Ubuntu repo's.

This last part might need some head scratching.