KLV-Airedale-beta+ Released, Ready for Download

[wiak]

Sorry, I've been slow doing anything at all of late. My partner on international business trip so too busy at home looking after the kids and keeping in touch with the travellor.
I was working on slightly modified built scripts, but then the business trip began and temporary put to one side; now I forget what stage that was at so a bit of extra work coming up re-reading and testing it all again - such is my bad organisation (which is exactly what I am trying very hard to improve...).

[geo_c]

I have uploaded it to https://rockedge.org/kernels

How sound is it to run KLV-16 with my upper_changes from KLV-14?

[rockedge]

@geo_c If you have updated beta14 recently it should be okay to just copy the upper_changes from beta14 into beta16 OR just take the 07KLV-airedale_rootfs.sfs from beta16 and copy it into your beta14 directory.

As long as the beta14 is close enough in age with the update/upgrades it will be alright in theory. Try it out and if no good remove it from beta16.

as soon as your upper_changes in the beta16 you could again run xbps-install -Suy to check.

Please let us know how you make out!

[fredx181]

@rockedge continue from here https://forum.puppylinux.com/viewtopic. ... 901#p61901 but posting here as it's intended specially for KLV.
To support scripts that are made for gtkdialog GTK2 (and won't work really as expected with gtkdialog GTK3), perhaps a sort of portable GTK2 gtkdialog setup could be useful.
Attached gtk2-apps.tar.gz, extract it somewhere (e.g. in /usr/local), to try as example: mmview by MochiMoppel, run "run-mmview" (as included), or edit "run-script*" etc.. to run any other script based on gtkdialog GTK2, and rename run-script* as preferred).

Code: Select all

.....
# run /path/to/script written for gtk2 gtkdialog ...
</path/to/script/here> 

The gtkdialog-8.5 in ./bin is the the one you provided in KLV but I did strip --unneeded on it to make it smaller.

EDIT: Similar can be done for "yad" by placing gtk2 yad in ./bin and edit run-script* to make use of GTK2 yad
EDIT2: Some views in mm_view aren't supported as it requires "urxvt" which is not in KLV (but perhaps can be fixed in some way by symlinking to xterm ?, didn't test that).

[rockedge]

I have had this odd problem of the Xserver crashing when the xfce4-screensaver engages on a particular machine I develop on. It has a Matrox MGA G200eW WPCM450 graphics card in a DELL PowerEdge R210 II blade server. To recover I CTRL-ALT-F2 and then CTRL-ALT-F1 immediately and login as root which restarts Xorg. killall xfce4-screen saver helps for just a while, disabling the screensaver and power manager lock screen isn't the solution either.

xserver-crash.jpg (84.57 KiB) Viewed 1339 times

Only machine it happens on, so I decided to build a KLV-Airedale with the PLUG file and this time include and use the current latest Void Linux kernel.

This has fixed it. No more Xserver crash and having to drop to console to recover!

Question is now should I make an ISO of this KLV-Airedale-beta16 with the Void Linux kernel instead of the custom Puppy Linux kernel-kit created one?

KLV-Airedale with the Void Linux kernel 5.18.14_1 SMP PREEMPT DYNAMIC is running well and fast. But the boot time seems long. I have it running as a frugal pseudo full install, which is using an uncompressed root_fs at the beginning of the boot cycle.

[wiak]

Question is now should I make an ISO of this KLV-Airedale-beta16 with the Void Linux kernel instead of the custom Puppy Linux kernel-kit created one?

Depending on your time constraints there is probably value in both. I presume you include some kernel modules directly inside the initrd and embed them into 07KLV-airedale_rootfs.sfs (or whatever you call it in KLV-Airedale. Using official Void kernel/modules/firmware is likely to be more bug resistant I'd imagine.

On another matter, I was searching this thread last night to see what the results were of trying CUPS printing on KLV-Airedale. In particular I am using CUPS with hplip. In past many years hardly needed or used printing, but now it becomes essential for business purposes here. I had settled on Zorin (full install) for business machine, to save me having to maintain - but last night discovered it refused to consistently work with our old HP2540 inkjet. DIdn't find anyone describing use of any hplip version with KLV-a, so quickly made a quick weedogit WDL_endeavourOS install since previously I was always successful using CUPS and hplip with WDL_Arch64 (but didn't have time to make a new WDL_Arch64 build - and Endeavour is an Arch-based distro). So printing turned out to work fine with EndeavourOS latest release... which is good and bad since Zorin great and well setup for all our main business needs... problem with EndeavourOS is that like all Arch-based distros it isn't designed to work with Secure Boot, and this newish business laptop (HP Probook G8 430) requires Secure Boot enabled, and with nvme drive is really fussy in needing signed kernels and more, which EndeavourOS doesn't provide... I can boot EndeavourOS on this machine via an external usb key, but the grub2 on the hard drive is from Zorin (probably really from Ubuntu) and has these fussy secure boot needs - and I don't wish to experiment further on a business-critical machine. Anyway, at least we managed to print last night, when needed for an urgent document... I will explore other distros (including building a new WDL_Arch64 later).

I think there is a habit on Puppy forum of not ensuring CUPS (and the likes of hplip) will work, but in some situations printing is a necessity and not always easy to install cups and so on later and get them to work reliably (depends on the distro and its package management and init management - I hate to admit I'm a fan of systemd's systemctl now...!, but void's runit is similar in overall use; just not quite so easy in terms of enabling/disabling services; i.e. needing to make symbolic links to enable services for boot time activation as far as I remember)

[Clarity]

Tovalds has released kernel v5.19...

[rockedge]

I presume you include some kernel modules directly inside the initrd and embed them into 07KLV-airedale_rootfs.sfs

I used build_firstrib_rootfs_401rc1.sh script to build the KLV-Airedale root_fs then used build_weedog_initrd-latest.sh to create the initrd.gz, extract the vmlinuz and put the kernel modules in the right places.

This worked well with the PLUG file ->
f_00_Void_KLV_XFCE_WDLteam-rc5.plug

Code: Select all

# f_00_Void_KLV_XFCE_WDLteam-rc5.plug
# version="2.8.0"; revision="-beta16"
# Kennel Linux Void outfitted with a xfce4 desktop and Void Linux kernel
# Creation date 24Sep2021; Revision date: 30Jul2022
# Copyright Kennel Linux team; License MIT

# build this via terminal commands:build_firstrib_rootfs_401rc1.sh
# export CONNECTION_TIMEOUT=-1  **not needed with v501**
# ./build_firstrib_rootfs_501rc1.sh void default amd64 f_00_Void_KLV_XFCE_kernel_WDLteam-rc4.plug
# Architecture i386 will probably successfully build too as an alternative to amd64

# login is user=root passwd=root

# All the parameters/commandlines can be appropriately changed:
# Simply comment in or comment out till you have what you desire
# or add new packages to the xbps-install lists.
# You can add as many valid commandlines as you want in here.
#
# base system
xbps-install -y base-minimal ncurses-base bash eudev
xbps-install -y file mc xterm xauth
xbps-install -y shadow wpa_supplicant  # needed for most wifi
xbps-install -y ntfs-3g zstd
xbps-install -y linux linux-firmware-network wifi-firmware


# set up passwd system
pwconv
grpconv
printf "root\nroot\n" | passwd >/dev/null 2>&1 # Quietly set default root passwd to "root"

# set root to use /bin/bash
usermod --shell /bin/bash root

# Set locale to en_US.UTF-8 
sed -i 's/#en_US.UTF-8 UTF-8/en_US.UTF-8 UTF-8/' /etc/default/libc-locales
xbps-reconfigure -f glibc-locales

# Set Bash as shell
xbps-alternatives --set bash

## --------------------------------------------------------------------------
## Xorg server, xfce4 Desktop configuration

xbps-install -y xorg xfce4 xfce4-panel xfce4-plugins compton picom
xbps-install -y gvfs yad
xbps-install -y gvfs-smb gvfs-mtp gvfs-cdda

# Optional packages
#
xbps-install -y geany gftp rox ffmpeg mtpaint xfce4-screenshooter
xbps-install -y octoxbps fox guvcview putty
xbps-install -y e2fsprogs yelp gparted
xbps-install -y dosfstools mtools cherrytree
xbps-install -y squashfs-tools wget

# Browser selection
xbps-install -y firefox

# Fix Firefox Fonts 
#
ln -s /usr/share/fontconfig/conf.avail/70-no-bitmaps.conf /etc/fonts/conf.d/
xbps-reconfigure -f fontconfig


# Install Audio
#
xbps-install -y pulseaudio pulseaudio-utils alsa-plugins-pulseaudio alsa-utils
ln -s /etc/sv/pulseaudio /etc/runit/runsvdir/default/pulseaudio

# Install Network Manager
#
xbps-install -y NetworkManager network-manager-applet
ln -s /etc/sv/NetworkManager /etc/runit/runsvdir/default/NetworkManager

# Set locale to en_US.UTF-8
sed -i 's/#en_US.UTF-8 UTF-8/en_US.UTF-8 UTF-8/' /etc/default/libc-locales
xbps-reconfigure -f glibc-locales

# Add ~/Startup directory
#
mkdir -p /root/Startup
cat <<'EOF' >> /usr/local/bin/start-up
#!/bin/bash
sleep 5
user_home=$(eval echo ~${SUDO_USER})
ls $user_home/Startup/* | while read J
do
   "$J" &
done
EOF

chmod +x /usr/local/bin/start-up
 
# Setup autologin on tty1
#
cp -a /etc/X11/xinit/xinitrc /root/.xinitrc
cp -R /etc/sv/agetty-tty1 /etc/sv/agetty-autologin-tty1
sed -i 's/GETTY_ARGS.*/GETTY_ARGS="--autologin root --noclear"/' /etc/sv/agetty-autologin-tty1/conf  # editing for autologin root

# Arrange to startx in user's .bash_profile (per Arch Wiki)
# Remove this section if not wanting boot straight into X
touch ~/.bash_profile
cat <<'AUTOLOGIN' > /etc/profile.d/autologin.sh
# autologin on tty1
if [ -z "$DISPLAY" ] && [ "$(fgconsole)" -eq 1 ]; then
exec startx  # remove the exec if you want back to tty1 on exit X

fi
AUTOLOGIN

# Get and install autologin fix
#
cd /etc/sv
wget https://rockedge.org/kernels/data/XBPS_packages/agetty-autologin-tty1.tar.gz
tar xvfz agetty-autologin-tty1.tar.gz

# Use agetty-autologin-tty1 instead of agetty-tty1 
rm -f /etc/runit/runsvdir/default/agetty-tty1
ln -s /etc/sv/agetty-autologin-tty1 /etc/runit/runsvdir/default/agetty-autologin-tty1

# enable dbus service
ln -s /etc/sv/dbus /etc/runit/runsvdir/default/dbus

# Auto-editing .xinitrc to use xfce4 instead of twm
# Because I'm using exec here the script will end there so no xterms started
#
# sed -i 's/twm &/exec xfce4-session/' ~/.xinitrc

sed -i '51,$d' /root/.xinitrc
echo "/usr/local/bin/start-up &" >>/root/.xinitrc 
echo "# exec xfce4-session" >>/root/.xinitrc
echo "xfce4-session" >>/root/.xinitrc  # removed exec to allow dropping out of Xorg to console

## USER CONFIGS: Copy main configs to /etc/skel for all normal users later added
#
xbps-install -y sudo
cp -af /root/. /etc/skel
mkdir -p /etc/skel/.config /etc/skel/.cache /etc/skel/.local/share
echo Still some extra to do here re the likes of runit starting pulseaudio
echo among other user needed config bits and pieces,
echo so probably a few user-config issues noted as needing fixed here

# Give wheel group nopasswd sudo rights and create weedog as wheel group member
echo '%wheel ALL=(ALL) NOPASSWD: ALL' | (VISUAL="tee -a" visudo) # wheel group added to sudo no password required
useradd -m -G wheel -s /bin/bash weedog  # weedog in wheel group so has elevated sudo permissions
printf "weedog\nweedog\n" | passwd weedog >/dev/null 2>&1 # Quietly set default weedog passwd to "weedog"

# Give wheel group nopasswd sudo rights and create spot as wheel group member
echo '%wheel ALL=(ALL) NOPASSWD: ALL' | (VISUAL="tee -a" visudo) # wheel group added to sudo no password required
useradd -m -G wheel -s /bin/bash spot  #spot in wheel group so has elevated sudo permissions
printf "spot\nspot\n" | passwd spot >/dev/null 2>&1 # Quietly set default spot

# Create /home/spot directories
#
mkdir -p /home/spot/Desktop
mkdir -p /home/spot/Documents
mkdir -p /home/spot/Downloads
mkdir -p /home/spot/Music
mkdir -p /home/spot/my-applications
mkdir -p /home/spot/Pictures
mkdir -p /home/spot/Public
mkdir -p /home/spot/Startup
mkdir -p /home/spot/Templates
mkdir -p /home/spot/Videos


# Set permissions
#
chown -R spot:spot /home/spot
chown -R weedog:weedog /home/weedog

# add users to groups and change permissions
#
usermod -a -G audio weedog
usermod -a -G audio spot
usermod -a -G video weedog
usermod -a -G video spot
xhost +
chmod 755 /
chmod 755 /bin
chmod 755 /lib

# add sudo -spot to .desktop files
cd /usr/share/applications
sed -i 's/^Exec=/&sudo -uspot /' octoxbps.desktop
sed -i 's/^Exec=/&sudo -uspot /' octoxbps-notifier.desktop
cp /usr/share/applications/thunar.desktop /usr/share/applications/thunar-spot.desktop
sed -i 's/^Exec=/&sudo -uspot /' thunar-spot.desktop
sed -i 's/^Name=/&spot-/' thunar-spot.desktop

#### Get KLV custom packages ####
#
# Create and switch to build directory
mkdir -p /root/Build
cd /root/Build

wget ‐‐continue https://rockedge.org/kernels/data/XBPS_packages/libfontconfig1-1.12_0.x86_64.xbps
wget ‐‐continue https://rockedge.org/kernels/data/XBPS_packages/gparted-shell-1.0_0.noarch.xbps
wget ‐‐continue https://rockedge.org/kernels/data/XBPS_packages/mime-add-1.1_0.noarch.xbps
wget ‐‐continue https://rockedge.org/kernels/data/XBPS_packages/xbps-tools-1.0_3.noarch.xbps
wget ‐‐continue https://rockedge.org/kernels/data/XBPS_packages/pfind-howbig-tca-1.0_0.noarch.xbps
wget ‐‐continue https://rockedge.org/kernels/data/XBPS_packages/uextract-4.7_1.noarch.xbps
wget ‐‐continue https://rockedge.org/kernels/data/XBPS_packages/tzupdate2-2.0_2.noarch.xbps
wget ‐‐continue https://rockedge.org/kernels/data/XBPS_packages/xluncher-1.0_0.noarch.xbps
wget ‐‐continue https://rockedge.org/kernels/data/XBPS_packages/default-scripts-1.0_1.noarch.xbps
wget ‐‐continue https://rockedge.org/kernels/data/XBPS_packages/dropbear-0.81_1.x86_64.xbps
wget ‐‐continue https://rockedge.org/kernels/data/XBPS_packages/SFS-Load-2.0_1.noarch.xbps
wget ‐‐continue https://rockedge.org/kernels/data/XBPS_packages/tas-1.15_1.noarch.xbps
wget ‐‐continue https://rockedge.org/kernels/data/XBPS_packages/packit-pfind-1.0_1.noarch.xbps
wget ‐‐continue https://rockedge.org/kernels/data/XBPS_packages/gettext-1.0_1.noarch.xbps
wget ‐‐continue https://rockedge.org/kernels/data/XBPS_packages/swapper-1.2_1.noarch.xbps
wget ‐‐continue https://rockedge.org/kernels/data/XBPS_packages/backgrounds-1.0_1.noarch.xbps
wget ‐‐continue https://rockedge.org/kernels/data/XBPS_packages/run-as-users-1.5_1.noarch.xbps
wget ‐‐continue https://rockedge.org/kernels/data/XBPS_packages/inst-xbps-1.8_1.noarch.xbps
wget ‐‐continue https://rockedge.org/kernels/data/XBPS_packages/gtkhash-1.1.1_1.x86_64.xbps
wget ‐‐continue https://rockedge.org/kernels/data/XBPS_packages/pure-ftpd-1.0.50_1.x86_64.xbps
wget ‐‐continue https://rockedge.org/kernels/data/XBPS_packages/syndownload-2.0_1.x86_64.xbps
wget ‐‐continue https://rockedge.org/kernels/data/XBPS_packages/desktop-config-1.0_1.x86_64.xbps
wget ‐‐continue https://rockedge.org/kernels/data/XBPS_packages/sClock-1.5_1.x86_64.xbps


#### Install KLV custom packages ####

# Register and index packages
cd /root
xbps-rindex -a Build/*.xbps

# Install libfontconfig cache fix
xbps-install -y --repository=Build/ libfontconfig1-1.12_0

# Install gparted-shell
xbps-install -y --repository=Build/ gparted-shell-1.0_0

# Install MIME definitions 
xbps-install -y --repository=Build/ mime-add-1.1_0

# Install pfind-howbig-tca
xbps-install -y --repository=Build/ pfind-howbig-tca-1.0_0

# Install xbps-tools 
xbps-install -y --repository=Build/ xbps-tools-1.0_3

# Install uextract
xbps-install -y --repository=Build/ uextract-4.7_1

# Install tzupdate
xbps-install -y --repository=Build/ tzupdate2-2.0_2

# Install xLunch
xbps-install -y --repository=Build/ xluncher-1.0_0
xbps-pkgdb -m hold  xlunch-4.1_3

# Install default launch scripts
xbps-install -y --repository=Build/ default-scripts-1.0_1

# Install dropbear
xbps-install -y --repository=Build/ dropbear-0.81_1

# Install SFS-Load
xbps-install -y --repository=Build/ SFS-Load-2.0_1

# Install tas
xbps-install -y --repository=Build/ tas-1.15_1

# Install Packit and pFind
xbps-install -y --repository=Build/ packit-pfind-1.0_1

# Install gettext
xbps-install -y --repository=Build/ gettext-1.0_1

# Install swapper
xbps-install -y --repository=Build/ swapper-1.2_1

# Install  backgrounds
xbps-install -y --repository=Build/ backgrounds-1.0_1

# Install run-as-spot and run-as-weedog
xbps-install -y --repository=Build/ run-as-users-1.5_1

# Install inst-xbps
xbps-install -y --repository=Build/ inst-xbps-1.8_1

# Install gtkhash
xbps-install -y --repository=Build/ gtkhash-1.1.1_1

# Install pure-ftpd
xbps-install -y --repository=Build/ pure-ftpd-1.0.50_1

# Install Syndownload
xbps-install -y --repository=Build/ syndownload-2.0_1

# Install desktop configuration
xbps-install -y --repository=Build/ desktop-config-1.0_1

# Install sClock
xbps-install -y --repository=Build/ sClock-1.5_1



# Set execution permissions recursivly for binaries and scripts
chmod +x -R /usr/local/bin

# Clean Up
#

rm -r /root/Build
rm /var/cache/xbps/*

#-----------------------------------------------------------------------
echo "desktop build process finished"

The entire build run was on a KLV-Airedale-beta16 and then repeated on a Puppy Linux Bionic64-8 and the runs were under 25 minutes.

I also renamed the first_rootfs created by the first script to upper_changes and added an empty 07dummy_rootfs directory to make it a frugal pseudo full install

[wiak]

I did a tiny bit of work on the new build_firstrib_rootfs.sh and build_weedog_initrd.sh scripts I was working on a while back. Most of the work on build_firstrib_rootfs is not concerned with Void builds though - and I haven't finished it because Arch builds need some work again because arch-bootstrap developed issues. Actually I can't remember what it was I changed in build_weedog_initrd.sh!... but it wasn't much - problem is I'm super busy at the moment (business-related and also preparing for move to other country though over a year to prepare for the latter) - basically I need a quiet period where I can finish it off and upload to gitlab/github for use and more testing - it's coming along though. I expect what I added to it will come back to me once I take a closer look at the code again - I roughly remember most details I have in the WDL init script, which is the main thing.

I can't remember if you said if you resolved the 'certificates' issue - I was planning to look into that since wasn't happy with the original way I dealt with it.

[Clarity]

Testing Beta16:

1. Booted ISO file, directly after download, via SG2D

2. selecting RAM0 at KLV Menu, for a pristine boot

3. minor desktop changes

4. Issues shown in the terminal log (please advise)

   Code: Select all

   root# whoami
   root
   root# pwd
   /root/Desktop
   root# 
   root# # start Pristine routine checks
   root# mkdir -p  /mnt/LocalPublicNAS/Downloads
   root# mount -o username=root,password=woofwoof //192.168.1.10/Downloads /mnt/LocalPublicNAS/Downloads
   root# echo "Accessing LAN shares works, as expected"
   Accessing LAN shares works, as expected
   root# 
   root# smbclient -U% -L 192.168.1.10
   bash: smbclient: command not found
   root# findsmb
   bash: findsmb: command not found
   root# smbd -V
   bash: smbd: command not found
   root# echo "No ability to share local files with LAN neighbors"
   No ability to share local files with LAN neighbors
   root# 
   root# find / -name bootinit.log
   find: File system loop detected; '/mnt/layers/merged' is part of the same file system loop as '/'.
   find: '/proc/897/task/897/net': Invalid argument
   find: '/proc/897/net': Invalid argument
   find: '/proc/1050/task/1050/net': Invalid argument
   find: '/proc/1050/net': Invalid argument
   root# echo "May or May-NOT be a problem for some"
   May or May-NOT be a problem for some
   root#
   oot# find / -name Xorg.?.log
   /var/log/Xorg.0.log
   /var/log/Xorg.1.log
   /var/log/Xorg.2.log
   /mnt/layers/07/var/log/Xorg.0.log
   /mnt/layers/07/var/log/Xorg.1.log
   /mnt/layers/07/var/log/Xorg.2.log
   find: File system loop detected; '/mnt/layers/merged' is part of the same file system loop as '/'.
   /mnt/layers/RAM/upper_changes/var/log/Xorg.0.log
   find: '/proc/897/task/897/net': Invalid argument
   find: '/proc/897/net': Invalid argument
   find: '/proc/1050/task/1050/net': Invalid argument
   find: '/proc/1050/net': Invalid argument
   root#

5. Boot LOG presented to see system's boot processing

   Code: Select all

   [    27.515] 
   X.Org X Server 1.21.1.3
   X Protocol Version 11, Revision 0
   [    27.516] Current Operating System: Linux void-live 5.16.14-KLV #1 SMP PREEMPT Sun May 1 19:35:37 EDT 2022 x86_64
   [    27.516] Kernel command line: BOOT_IMAGE=/vmlinuz w_bootfrom=/boot-isos/KLV-Airedale-beta16.iso w_changes=RAM0 net.ifnames=0
   [    27.516]  
   [    27.516] Current version of pixman: 0.40.0
   [    27.516] 	Before reporting problems, check http://wiki.x.org
   	to make sure that you have the latest version.
   [    27.516] Markers: (--) probed, (**) from config file, (==) default setting,
   	(++) from command line, (!!) notice, (II) informational,
   	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
   [    27.519] (==) Log file: "/var/log/Xorg.0.log", Time: Tue Aug  2 14:50:37 2022
   [    27.527] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
   [    27.551] (==) No Layout section.  Using the first Screen section.
        o
        o
        o    
   

   Xorg.0.log

   (34.71 KiB) Downloaded 26 times

6. Will Shutdown saving the session on a Linux filesystem of the System drive in its /Sessions folder along with all other sessions

7. Drivers loaded

   LSPCI.txt

   (798 Bytes) Downloaded 43 times

8. Boot errors

   DMESG_failure.txt

   (1.51 KiB) Downloaded 26 times

   Although no connection attempts, this 2016 AIO system has Bluetooth

Thanks. If additional concerns for more info, please ask. If there is any helpful advice, please share.
Again, thanks.

[rockedge]

I can't remember if you said if you resolved the 'certificates' issue - I was planning to look into that since wasn't happy with the original way I dealt with it.

I just ran a build using a KLV-Airedale-type-K and no certificate issues. I do not know why it is okay now but it is.

[wiak]

The other matter I want to get back to eventually is WDLGO - i.e. mini-builds. I still have some script variants (incomplete) relating to that, but I have temporarily still to track down some pieces of that again (on my old machine I think) - problem was it was very experimental and I was building a lot of stuff at the time to do with it including dpkg/apt sfs addon for Fossapup which was side-product of main WDLGO weedog focal build. Nowadays, dimkr has Upup that uses its own dpkg/apt sfs, so a Jammy-based build, and no-one thus far has come up with a more conventional Jammy Pup to replace Fossapup (if they did I'd probably assemble another dpkg/apt sfs addon for it, though probably easier for that to come out of existing dimkr Upup build I'd think).

[Clarity]

...including dpkg/apt sfs addon for ...

Does the work of @mistfire in package management accomplish this for PUPs across the board?

Curious

[rockedge]

Here is KLV-Airdale-Test-G ->
This KLV is using a Void Linux kernel 5.18.19_1 SMP PREEMPT DYNAMIC

This is a KLV-Airedale built similar to beta16 using the WDL build scripts and a PLUG file recipe. Has Firefox 103.0.1 for a browser on board.
KLV-Airdale-Test-G
SHA1-MD5.txt

KLV-Airdale-Test-G is packaged as a .tar.bz2 file and is a 1.1 GiB download. This package is meant to be in a frugal install directory.

Boot stanza example (replace UUID with your own) :

Code: Select all

title KLV-Airdale-Test-G (uuid)
  uuid 8a8ea99d-a1b0-4c43-b1a0-d4ce5c9c7dfa
  kernel /KLV-Airdale-Test-G/vmlinuz-5.18.19_1  w_bootfrom=UUID=8a8ea99d-a1b0-4c43-b1a0-d4ce5c9c7dfa=/KLV-Airdale-Test-G net.ifnames=0
  initrd /KLV-Airdale-Test-G/initrd.gz

Test-G is 1.1 GiB which comes from an increase in size of both the initrd.gz and the root_fs because of the Void Linux Kernel and it's huge collection of firmware and modules.

[rockedge]

@Clarity
Here is an ISO version of KLV-Airedale-G

KLV-Airedale-G.iso
SHA1-MD5.txt

Because the Void Linux kernel 5.18.14_1 SMP PREEMPT DYNAMIC includes so much firmware and modules the initrd.gz is around 135 Gb and the rootfs is around 970 Mb which results in an ISO approximately 1.1 Gb in size.

[Clarity]

All test are done, pristine on an AMD AIO PC of 2017

The Beta 16 version boots via SG2D without issue.

But for "G", Boot failure for both RAM0/RAM2 Menu selection.

boot failure.jpg (98.01 KiB) Viewed 1058 times

Intel PC not tested, as yet.

[rockedge]

@Clarity there is something wrong with "G" and I am discontinuing that model for now.

The boot time is very long and I think it involves determining partitions but not sure yet. One thing though is the xfce4-screensaver does not freeze up and seg fault the X server using the Void Linux kernel.

beta16 performs overall better at this time continuing to use the custom KLV kernel. I will test also with some newer Puppy Linux huge kernels built by some members of the community. Interested in seeing if I can eliminate the segmentation fault caused by xfce4-screensaver by swapping in a different kernel and/or firmware.

[Clarity]

+1. Same result on Intels.

[rockedge]

@Clarity So the tar.bz2 version works but the beta-G ISO is not booting correctly and ending up in a console?

beta-G might just need some work on the /boot directory contents.

[fredx181]

Tested the G version by extracting the ISO and made a frugal install.
No problems booting to the Desktop, perhaps it has to do with SG2D combined with some change in the ISO that @Clarity has problem booting.
Huge increase of size BTW ! (but I noticed that you mentioned the problems with the custom kernel).

[rockedge]

@fredx181 Just adding the Void Linux kernel at build time added a hefty amount of megs. Just the firmware is 135 MB making the initrd.gz really big also. I have been testing one of @ozsouth's 5.15.59 kernels and using the same firmware as the 5.16.14-KLV custom kernel and the xfce4-screensaver crash is not happening. Plus the KLV kernel and the huge Puppy Linux kernels are a fraction of the size of the Void Linux kernel.

The crash is only happening on a machine with MATROX graphics. But if I killall xfce4-screensaver the Xorg screen blanking seems to take over. Not sure though.

the ISO of beta-G is over 1 gig so the isohybrid command has an error, too many blocks. That might play a role in Clarity's problem to boot but everything I read about it says the error or warning does not effect overall operation of the ISO.

[Clarity]

... perhaps it has to do with SG2D combined with some change in the ISO that @Clarity has problem booting.
...

Hi Fred. If you still have your USB that you used to test you DOGs from couple years ago, add BOTH the beta 16 and the 'G" to the ISO stick. In a few moments you'll see what we see that b16 (and the other prior betas) boots while G abends.

I have tested over 40 PUPs, DOGs, and 'buntus, etc and their versions (thus its in the hundreds in total) since 2019 and MANY of them have been much-much larger than any PUP/DOG from this forum. And, on a few occasions, like what's happening here, the distro owners which provide loopback.cfg figured it. For KLV, this is our 1st like this.

The problem is unlikely to be the size. It could be something else, as, the message suggest it is waiting then abends when it doesn't find what its looking for and tries to continue.

You gave me an Idea though as it should have been my first test; namely using the stick and booting via QEMU, then also checking that against a non-stick boot using QEMU direct boot of just the ISO file without SG2D stick to compare outcomes.

I'll give a test and get back when I can later today. If you can, in the meantime, test it by adding the ISO file to your stick.
Unlike Ventoy, SG2D is out of the way when the user selects his ISO choice and starts the selected distro to boot,iIIRC. As such, all processing falls on the distro and its INIT.

[Clarity]

QEMU boot of G ISO file crashes like it does booting on bare-metal. Just to summarize my priors..."Beta boot OK, G has this problem".

BTW, G exhibits the same boot speed as seen in Ubuntu, DebianDOG, etc. under QEMU. In observation, it pre-loads contents to ram and starts it setup.

Lastly, I DID NOT use SG2D's USB to boot within QEMU, only the ISO file.

QEMU boot KLV-G.jpg (22.45 KiB) Viewed 693 times

Hope the observations are helpful

[fredx181]

@Clarity Why you only want to test booting ISO ? I'd say that testing the system (however way) could be valuable too.

[fredx181]

Will PM a response, soon. Most importantly, though, 'productivity' as, it reduces setup errors and TIME to desktop.

Well, ISO booting directly can be nice way, but IMHO just a small part of the whole picture of how well (or not) the system works, but it's appreciated of course if that's your way of helping development.

EDIT: Sorry, clumsy posting I did accidentally, your last message is removed I see now, anyway, it's quoted above.

[Clarity]

The ISO file has always been thought of as a shipping container since 1995. But over the years we have learned that it is NOW the actual Linux Operating System and can be launched as such.

Several of the mainline distros (distrowatch) employ the SG2D method of direct ISO
file booting, PUPs and FATDOG starting same boot stanza to allow such in 2019. This does not appear to be done to keep up with others, INSTEAD, it appears they did so for its productivity value to benefit themselves and users.

In 2020, Ventoy jump onto ISO file booting and goes much further along than SG2D. But some PUPs stuggle in booting via Ventoy, but ALL WoofCE PUPs plus DOGs boot flawlessly in SG2D. So, I add the SG2D ISO file to all my Ventoy USBs to overcome any struggling issues and boot SG2D when encountering such.

I continue SG2D and QEMU use as I do not need to do setup because the ISO file already is THE Frugal setup. Thus, there is no need for a bare-metal setup to get to a PUP-DOG desktop...boot the ISO file directly.

Therefore I merely download and boot the distros in PUPPYLAND directly from their ISO file(s).

Hope this provides the primary understanding I have found over the years.

Finally, for PUPs, when I post booting, it intends to affirm for the distro developer the success and the environment their distros continue to operate in. Many other users announce their Frugal structuring success, WHEREAS, I announce the FRUGAL Built-into the ISO success. Its gives the distro developer knowledge that their distro boots, frugally, from bare-metal or from its ISO file.

@fredx181 I will continue other aspects via PM.

[fredx181]

Well, why PM instead of discuss this openly here. (not really want to discuss it BTW, it's just a matter of difference in opinion / preference).
IMO it's *gold* to have learned the way to install a bootloader and edit menu.lst , grub.cfg or whatever is preferred , the "manual way" (not saying it's easy, btw ).
(but maybe I'm a bit strange compared to others, I never use programs that try to do things automatically, like Ventoy, Etcher, Unetbootin etc...)
As I think I said earlier, booting ISO directly has it's disadvantages, e.g. you have no control of setting save storage path (and other parameters), unless you edit by pressing 'e' every time you boot (grub and grub4dos) , which is very inconvenient IMO.

[Clarity]

... setting save storage path (and other parameters), unless you edit by pressing 'e' every time you boot ...

I agree, although not sure if this is a general disadvantage for persistence.

WoofCE architecture (although I KNOW DOGs and our KLV does not use WoofCE) has a feature which was introduced and maintained by @gyrog to address common boot issues associated with USB stick/hdds booting PUPs; namely the SAVESPEC file. The WoofCE distro builds and places this file, AND, as well, a user can update it. This was introduced in WoofCE couple years ago, IIRC, and addresses your concern. When present, it is found and used upon the PUPs boot; thereby there is NO NEED to edit the PUP's Menu to boot, pristine or otherwise for persistence. Just 1 hour ago, this worked flawlessly as expected booting the most current WoofCE PUPs from @PeeBee. It's persistence pathways are discovered and used silently by design.

For FATDOG, it finds it persistence file/folder while also allowing users to specify locations for persistence using its built-in algorithm.

KLV and DebianDog, etc, allow me to specify where persistence is to exist by the edit feature. Ubuntus and other distrowatch distros afford me the same advantage.

I agree, that it is a departure from what we might have learned in the past, but, in no way does it restrict our use OR our understanding of the process to get to a distro's desktop.

My use is simple, easy, speed to get to desktop or to report problems if cannot. I dont have a downside in its ability to do so and the PUP-DOG allows persistence as expected and normal.

So, without changing anything in the PUP or its files or the local PC, I have a verifiable frugal use by booting directly from the ISO file.

[Clarity]

The ISO file is merely a frugalOS.

[rockedge]

I think that the initrd.gz is the problem in KLV-Airedale-G which is built using an older build initrd script to extract the vmlinuz and set up the initrd.

I am leaning towards that being what is causing the failure to boot the ISO in QEMU in my tests.

Testing later if using the latest WeeDog skeleton initrd modified with the Void Linux kernel modules will fix the boot problems.

@Clarity I am pretty sure that the initrd.gz is causing boot failure and we might be able to fix it.