Puppy Linux Discussion Forum

Hi.

A few hours ago I created a new Puppy Linux from scratch using the current Woof-CE build system.
This one is created from the Ubuntu Noble 24.04 64bit packages.
I temporarily named it to NobleStudio64_1.0.

My first steps to get a working result after doing it twice is to be found here:
Results of the first go.
Results of the second go. Created again completely from scratch.

I will see, how far I can get with that version to make a new LazY Puppy.
By now there's nothing yet to download available. It's just an announcement
by doing constant message at larger intervals about the progress made.

I can only work some hours at the weekend on this. So, it will take some time.

This is how the current desktop is looking by now.

By now it seems to work fine, internet is working, audio and video is working.

Thanks for the interest, if there's any...

Edit:

Added by request. Has nothing to do yet with the new LazY Puppy!

Ok,

I got QJackCtl and Qtractor installed and running.
Did not made any tests further, as I need to download lots of plugins first
to get my compositions played in Qtractor.

That's all for now...

I would be keen to try booting an iso or whatever format you make available.
Are you building just for your own specific needs or would you be interested in feedback on other hardware?
Cheers!
(These days i mostly look for the core ability to boot on multiple machines. More interested in testing hardware compatibility rather than needing a lot of inbuilt software)

@greengeek

I would be keen to try booting an iso or whatever format you make available.
Are you building just for your own specific needs or would you be interested in feedback on other hardware?

Hi.

At the moment I'm running just the created version in original by
installing programs into the save folder. So, there's no additional
programs inside the base .sfs. Only four libraries added to get MPV working.

I could create a .tar.gz archive to make a manual install as usual.
But first I need to find out if I still can login to archive.org.
Otherwise I need to create a new account.

Will check it out and return later...

*

I'm building for my specific needs, though I plan to modify the original
files only on the necessary parts. Everything else shall be in additional .sfs
files. My ArtStudio64 has lots of them: a, b, c, g, m, n, s, u, v, x and ydrv.
There's the plan to add some of this to the NobleStudio64.

*

If everything works fine one day, I will publish the complete NobleStudio64.
We will see...

For a first go I downloaded this program
Simple SFS Builder 0.3
to create some .sfs files from downloaded .deb packages.
Hopefully it will work on a plain Puppy...?

Created .sfs file from Ardour 8 packages using the Simple SFS Builder 0.3.
Both seem to work fine.

My ArtStudio64 has lots of them: a, b, c, g, m, n, s, u, v, x and ydrv.
There's the plan to add some of this to the NobleStudio64.

I always thought this feature was excellent. Looking forward to the progress on this project. Rock and Roll.

rockedge wrote: ↑Fri Jun 21, 2024 3:22 pm

My ArtStudio64 has lots of them: a, b, c, g, m, n, s, u, v, x and ydrv.
There's the plan to add some of this to the NobleStudio64.

I always thought this feature was excellent. Looking forward to the progress on this project. Rock and Roll.

A Github pull request to get this added to Woof-CE would be welcomed...

What order do they get added to the stack?

@greengeek
I was able to recall one old e-mail address AND password to login to my
account at archive.org. I'm somehow surprised...
This one was registered during the OFINSIS era.
The older one from LazY Puppy era I couldn't recall.

Currently uploading a .tar.gz file.
Will send link by pm.

This is the list of stuff I needed to install:

libjack-jackd2-0_1.9.21~dfsg|libjack-jackd2-0|1.9.21~dfsg|3ubuntu3||||libjack-jackd2-0_1.9.21~dfsg-3ubuntu3_amd64.deb|||
libxcb-icccm4_0.4.1|libxcb-icccm4|0.4.1|1.1build3||||libxcb-icccm4_0.4.1-1.1build3_amd64.deb|||
libxcb-image0_0.4.0|libxcb-image0|0.4.0|2build1||||libxcb-image0_0.4.0-2build1_amd64.deb|||
libxcb-keysyms1_0.4.0|libxcb-keysyms1|0.4.0|1build4||||libxcb-keysyms1_0.4.0-1build4_amd64.deb|||
libxcb-render-util0_0.3.9|libxcb-render-util0|0.3.9|1build4||||libxcb-render-util0_0.3.9-1build4_amd64.deb|||
ffmpeg_6.1.1|ffmpeg|6.1.1|3ubuntu5||||ffmpeg_6.1.1-3ubuntu5_amd64.deb|||
libavc1394-0_0.5.4|libavc1394-0|0.5.4|5build3||||libavc1394-0_0.5.4-5build3_amd64.deb|||
libavdevice60_6.1.1|libavdevice60|6.1.1|3ubuntu5||||libavdevice60_6.1.1-3ubuntu5_amd64.deb|||
libcaca0_0.99.beta20|libcaca0|0.99.beta20|4build2||||libcaca0_0.99.beta20-4build2_amd64.deb|||
libdc1394-25_2.2.6|libdc1394-25|2.2.6|4build1||||libdc1394-25_2.2.6-4build1_amd64.deb|||
libiec61883-0_1.2.0|libiec61883-0|1.2.0|6build1||||libiec61883-0_1.2.0-6build1_amd64.deb|||
libopenal1_1.23.1|libopenal1|1.23.1|4build1||||libopenal1_1.23.1-4build1_amd64.deb|||
libopenal-data_1.23.1|libopenal-data|1.23.1|4build1||||libopenal-data_1.23.1-4build1_all.deb|||
libraw1394-11_2.1.2|libraw1394-11|2.1.2|2build3||||libraw1394-11_2.1.2-2build3_amd64.deb|||
libsdl2-2.0-0_2.30.0+dfsg|libsdl2-2.0-0|2.30.0+dfsg|1build3||||libsdl2-2.0-0_2.30.0+dfsg-1build3_amd64.deb|||
libslang2_2.3.3|libslang2|2.3.3|3build2||||libslang2_2.3.3-3build2_amd64.deb|||
libsndio7.0_1.9.0|libsndio7.0|1.9.0|0.3build3||||libsndio7.0_1.9.0-0.3build3_amd64.deb|||
tas-1.17|tas|1.17||X-GraphicUtility|36K||tas-1.17.pet||Screenshot utility||||
tas_NLS-1.17|tas_NLS|1.17||BuildingBlock|40K||tas_NLS-1.17.pet||no description provided||||
packit-1.24|packit|1.24||Utility|120K||packit-1.24.pet||Archiving/Compressing GUI||||
uextract-4.13|uextract|4.13||Utility|452K||uextract-4.13.pet||Ultimate Extractor||||

@peebee

What order do they get added to the stack?

Starting with the zdrv after the main .sfs is loaded it is added this way:

First is ydrv, then x, v, u, s, n, m, g, c, b and adrv on top.

A Github pull request to get this added to Woof-CE would be welcomed...

1. I don't know how to do such a pull request, never did this
2. I don't think this could be added to Woof-CE without huge work

I have done these modifications inside the init script of bionic puppy 64 8.0. There was also a modification of sfs_load 3.0 necessary to get those drives out of the list of loaded .sfs files in sfs_load.

I don't know about the current version of sfs_load and its other mods.
However, the init script from fossa pup is already different to the one from bionic.
My current Noble64 built doesn't have any of this at the moment.

I could attach a .tar.gz file containing those scripts (init & sfs_load), if interested.

I could attach a .tar.gz file containing those scripts (init & sfs_load), if interested.

Yes! That would be great

@rockedge
Attached at the end of first post.

Announcement