Another Jammy64pup

[Clarity]

Hello @user1234 I downloaded your Jammy64pup and am booting it via its ISO file.

Nice PUP. Booted quickly in QEMU without issues.

Yes this has Pipewire. There are 2 ways to test a distro for Pipewire via this PUPs terminal
"ps ...'

Code: Select all

root@puppypc12811:~$ ps -A | grep ipewire   # test for pipewire via 'ps' command
   3447 tty1     00:00:01 pipewire   <=== Pipewire seen here
   3546 tty1     00:00:00 pipewire-pulse

"pactl ..."

Code: Select all

root@puppypc12811:~$ pactl info   # test for pipewire via 'pactl' command
Server String: unix:/tmp/runtime-spot/pulse/native
Library Protocol Version: 35
Server Protocol Version: 35
Is Local: yes
Client Index: 53
Tile Size: 65472
User Name: spot
Host Name: puppypc12811
Server Name: PulseAudio (on PipeWire 0.3.48)   <=== Pipewire seen here
Server Version: 15.0.0
Default Sample Specification: float32le 2ch 48000Hz
Default Channel Map: front-left,front-right
Default Sink: alsa_output.pci-0000_00_04.0.analog-stereo
Default Source: alsa_input.pci-0000_00_04.0.analog-stereo
Cookie: 8137:a7e3

I will test bare-metal later today and report.

[Jasper]

@user1234

Can you DM your build instructions?

[dimkr]

The increase in ISO size is due to the change from firmware downloaded and chosen by https://github.com/puppylinux-woof-CE/w ... _picker.sh to Ubuntu firmware packages, which are maintained by Canonical.

This script is very problematic, the way it trims down the selection of firmware is very generic and it doesn't handle many corner cases. The result is small fdrv that doesn't work on very old or very new hardware.

Using Ubuntu's firmware is a very safe bet if you want broad hardware support, at the cost of big size. IMO it's better to provide users with a large ISO that "just works", and let users who want to save some space craft a small fdrv with the firmware their computer needs and nothing more. As a user, you can delete what you don't need, but if you get a small fdrv you can't add missing firmware you don't have.

[Clarity]

Bare-metal boots the ISO file via my boot-launcher USB. SG2D has no problem launching this to desktop as is the usual case with WoofCE ISOs. At desktop all is well.

This bare-metal test 'mirrors' exactly what I tested when booting in QEMU with the following stanza

Code: Select all

qemu-system-x86_64 -enable-kvm -vga std -m 2G -smp 2 -device AC97 -net nic -net user -rtc base=localtime -name "USER1234's JammyPup64 via Ventoy USB in QEMU"  /dev/sdb

This distro runs well but is cut-down and lacking many OOTB features of the mainline WoofCE PUPs. Desktop, below, shows some of typical programs or subsystems that are usually found. Manual installation of missings, such as SAMBA, introduces issues.

JammyPup64 by user1234.jpg (32.25 KiB) Viewed 1059 times

Thanks. Enjoy

[user1234]

The increase in ISO size is due to the change from firmware downloaded and chosen by https://github.com/puppylinux-woof-CE/w ... _picker.sh to Ubuntu firmware packages, which are maintained by Canonical.

This script is very problematic, the way it trims down the selection of firmware is very generic and it doesn't handle many corner cases. The result is small fdrv that doesn't work on very old or very new hardware.

Using Ubuntu's firmware is a very safe bet if you want broad hardware support, at the cost of big size. IMO it's better to provide users with a large ISO that "just works", and let users who want to save some space craft a small fdrv with the firmware their computer needs and nothing more. As a user, you can delete what you don't need, but if you get a small fdrv you can't add missing firmware you don't have.

Can we do something like providing a small fdrv by default in the ISO and providing a larger replacement fdrv later on separately? This way, many users may not even need to use space on a larger fdrv since space sometimes is important (I mean if people had whole 100s of GB partitions devoted to Linux, why would they use Puppy and not something mainline like Ubuntu? In my case, I came to use Puppy only because my earlier Laptop's hard drive had crashed and I had only a single 4GB pendrive to run some OS).

Just a thought, if it is possible. I really haven't a single idea if this is possible.

BTW, I read your retirement from woof-CE message. Thanks for all the work you have done till now ! Hope that you will still do some reviews .

Regards
Lakshay Rohila

[user1234]

Bare-metal boots the ISO file via my boot-launcher USB. SG2D has no problem launching this to desktop as is the usual case with WoofCE ISOs. At desktop all is well.

This bare-metal test 'mirrors' exactly what I tested when booting in QEMU with the following stanza

Code: Select all

qemu-system-x86_64 -enable-kvm -vga std -m 2G -smp 2 -device AC97 -net nic -net user -rtc base=localtime -name "USER1234's JammyPup64 via Ventoy USB in QEMU"  /dev/sdb

This distro runs well but is cut-down and lacking many OOTB features of the mainline WoofCE PUPs. Desktop, below, shows some of typical programs or subsystems that are usually found. Manual installation of missings, such as SAMBA, introduces issues.JammyPup64 by user1234.jpg

Thanks. Enjoy

@Clarity, thanks for that infomation! It's how it should be! - test and report issues. That is the only way we can develop a Jammy64!

I'll try to solve the samba issue but am unsure if I will be able to fix its issues (this command currently overwhelms me ). Maybe, just enabling it at build-time is a solution, as we do have a SAMBA_FIXUPHACK in woof-CE, but I am unsure about that as well.

Once again, thanks for pointing the issue out! Please suggest other applications that need to be added in Jammy64 and I'll try to do my best to add them.

[Jasper]

@user1234

As I mentioned before, I do understand the decision for the inclusion of these files are necessary.

My initial approach was different when I used the E1 iso

viewtopic.php?p=109433#p109433

Time and patience permitting I might attempt building synaptic-gtk ........ it does require apt-headers.

There is a Samba SFS in #1

https://drive.google.com/file/d/16ArltM ... sp=sharing

[dimkr]

Can we do something like providing a small fdrv by default in the ISO and providing a larger replacement fdrv later on separately?

It can be done but from my experience, users will complain about broken network or sound. Newer computers need more firmware than old ones: post-802.11n WiFi cards need firmware and there's a big variety of vendors and models, newer DSPs need firmware (SOF) while older ones didn't, and so on. And, no matter how you select which firmware to include in the small fdrv, you'll miss firmware required by some common piece of hardware and you'll find yourself adding more and more "important" things to the small fdrv.

I don't think that fdrv size is a concern because today's init script won't copy fdrv to RAM in a computer without enough RAM, and if RAM is limited but enough to copy only some SFSs the init script will prefer to copy something more important (like the main SFS or adrv) and keep fdrv out. fdrv is used rarely, so the user won't feel anything if it's big and doesn't get copied to RAM.

Both approaches (more firmware, less firmware) are valid but I believe that what's good for advanced users who try to optimize and shrink their system is a very bad default.

[user1234]

I believe that what's good for advanced users who try to optimize and shrink their system is a very bad default.

I agree. It was just an idea, and now I see why this configuration is important .

---

@Clarity,

In Jammy64 in QEMU, I ran the following to install samba client:

Code: Select all

apt update
apt install smbclient

and was able to successfully transfer files between my host OS (Kubuntu) and client (Jammy64). What exact problems did you have while installing smbclient?

[Clarity]

Hello @user1234

... In Jammy64 in QEMU, I ran the following to install samba client:
... What exact problems did you have while installing smbclient?

The console I showed was merely there to show a few of the components I think the community has in many of the other forum distros. Using @peebee's PUPs of the past, these are a few of the packages that are both useful and help in seeing the system behaviors and is 'why' I showed the console messages.

smbclient console message was merely to show that the traditional SAMBA packaging is missing. 'smbclient', 'findsmb', and several others are items that have become traditional for forum since introduction by @01micko quite some years ago. These are particularly helpful, as you show, when needed to accesss or share (the normal "PUP samba" required) info-data-media within users home network. The PUP's SAMBA stack is what I think you want in this PUP.

Those are not new to most WoofCE PUPs, KLs or forum DOGs.

If I find other missing subsystems I will share thing to be helpful.

I dont find the size of the PUP important. My only concern is its usefulness, stability, and performance. Size is merely the packaging...not the "PUP".

@Jasper I ask: Could you compile QEMU v8+ PET ... should you have a moment? (not urgent) Its not available in either the Puppy Repo or apt YET.

Thanks for all the efforts

[user1234]

The console I showed was merely there to show a few of the components I think the community has in many of the other forum distros.

I asked that because, you had written:

Manual installation of missings, such as SAMBA, introduces issues.

This made me think that we will require to use some hack to add samba to this build . I haven't tested samba yet, but I have tried to add tldr and btop - only testing is remaining .

[Clarity]

Manual installation of missings, such as SAMBA, introduces issues.

This made me think that we will require to use some hack to add samba to this build . I haven't tested samba yet ...

I seem to remember @peebee has/had done something in WoofCE to automate the SAMBA process. Seemed that he has filled in for @01micko with the SAMBA offerings we see in WoofCE PUPs, IIRC. He's good at it as his offering has the useful utilities OOTB, such as 'findsmb', as well.

Can't remember 'what', though.

[Jasper]

@user1234

For testing ............... minimised options available for speedy compilation.

[Jasper]

@user1234

The new ISO you provided does not include a MTP device mounter.

So, have decided to mix & match both ISO's in the interim.

[user1234]

@Clarity, btop and tldr tests are succesfull! Gonna open a PR to woof-CE.

Here are the screenshots:

Screenshot_20240126_164751.png (75.41 KiB) Viewed 890 times

Screenshot_20240126_164826.png (110.13 KiB) Viewed 890 times

Next to work on... samba! (I think this will probably be easy because, as you said earlier, peebee has already done something regarding it)

---

@peebee, can you please review woof-CE#4219 (Geany update to 2.0)?

[Jasper]

DAIR-Log-1.4.1

DAIR stands for Decisions-Actions-Issues-Risks.

This small tool allows you to keep track of

decisions / actions
risks / opportunities
issues

along with ownership, probability, impact, participants, notes, deadlines, history, etc.

It is especially useful for

risk management
project management
regular reviews
to-do lists

https://www.mediafire.com/file/4y5b7t7g ... 1.pet/file

[Clarity]

For testing ............... minimised options available for speedy compilation.

@Jasper this look good.

Did you PET this somewhere? I like to give it a run.

Thanks muchly

[Jasper]

btop-1.3.0 .... includes the theme pack
https://www.mediafire.com/file/sal71ijp ... 4.pet/file

ncurses-6.4 - Library and set of utilities that allows you to use terminfo format, colour, multiple highlights and function-key mapping in your applications
https://www.mediafire.com/file/6uvtisdq ... 4.pet/file

@user1234

Did you test out the application?

I did find this gui available in the EasyOS secton.

It is called Qemu Control Center by Mikeb and works well.

Line 21 I added the additional comments and this is something each user would have to edit (or not - does not affect the program) to run the script.

[user1234]

Did you test out the application?

Which one, btop and tldr? Yes! I used a slightly different version of tldr-py though - tldr-py. Works exactly like tldr, except that it's a lot smaller (and does not depend on git).

[Jasper]

@user1234

[Jasper]

chkrootkit is a tool to locally check for signs of a rootkit (Release Date: Jul 05 2023)

https://www.chkrootkit.org/

It contains:

chkrootkit: shell script that checks system binaries for rootkit modification
ifpromisc.c: checks if the interface is in promiscuous mode
chklastlog.c: checks for lastlog deletions
chkwtmp.c: checks for wtmp deletions
check_wtmpx.c: checks for wtmpx deletions (Solaris only)
chkproc.c: checks for signs of LKM trojans
chkdirs.c: checks for signs of LKM trojans
strings.c: quick and dirty strings replacement
chkutmp.c: checks for utmp deletions

NB I did get a warning " Warning: Possible LKM Trojan installed" ......... however looking online, people do say that it is a false positive.

[Jasper]

@user1234

Can you let me know which version of these applications is used in the DevX?

Automake
Autoconf
Make

Thanks

[user1234]

@user1234

Can you let me know which version of these applications is used in the DevX?

Automake
Autoconf
Make

Thanks

Screenshot_20240127_154105.png (99.67 KiB) Viewed 762 times

---

BTW, due to some reasons, the tldr-py is rejected and won't be included in Jammy (btop still can be added) .

[Jasper]

@Clarity

qemu-8.2.0-x86_64
https://www.mediafire.com/file/cwsilf55 ... 4.pet/file

[Jasper]

autoconf-2.72-x86_64
https://www.mediafire.com/file/9zmz42vd ... 4.pet/file

autoconf-archive-2023.02.20-x86_64
https://www.mediafire.com/file/tjm1x1ch ... 4.pet/file

I added them to the FP95 DevX previously and have had no issues with compiling applications

https://www.forum.puppylinux.com/viewto ... ke#p103114

https://www.forum.puppylinux.com/viewto ... nf#p107198

[Jasper]

Searches for patterns in files

[Jasper]

Updates for the DevX SFS

[Jasper]

Updated the DevX from #1

devx_upup_22.04-jrb-E1
https://www.mediafire.com/file/ptwo4hbn ... 1.sfs/file

md5 ec402c466c2693b21e59c4af2f2b2e51
sha1 76eee6a3298b35c936b49b7cda3410971cce0e6a
sha3 e63ab7e64011a1396d6e8767e1aea5c72757c91c8f00003c42f6092b
sha256 b15d45547ec5fc7c29e44a25e5acb697592ae8061a0624543d78b86d640aa3cd
sha512 3990c9f1b35a6bb59a5ea57639805044e37f218b780545a11f2f504dedf3f71060813e9537d6fb984373b039674483891924fd7f5d7a9553bf49ebc991cd77ba

[sonny]

Searches for patterns in files

@Jasper, afaik, the last good version of grep's 3.7.
3.8 and higher will generate lines of "error" when updating PPM in fossapup64 9.5.

[Jasper]

@user1234

As GCC-12 is available in the PPM and Synaptic to download and install.

Would a future update include this and not the older 11 build?