Puppy Linux Discussion Forum

KLV-Airedale-rc15
Kennel Linux Void Airedale Release Candidate 15 789 MiB download size ↓
KLV-Airedale-rc15
SHA1-MD5.txt
Download from SOURCEFORGE

Full system upgrade.and added full SAMBA support and managed by a modified for KLV Samba Simple Management GUI script, borrowed from F96-CE_3.

The team fine tuned login/logout with a long term solution utilizing the Void Linux service manager runit to fix a conflict after upgrades to the runit-void package added a service directory agetty-tty1 that conflicts with KLV's custom agetty-autologin-tty1 during logout/login causing difficultiy in changing user. Adding a file called : /etc/sv/agetty-tty1/down instructs runit to disable the service which is persistant across reboots.

Complete system update/upgrade and outfitted with a Void Linux kernel 6.1.20_1 on 03/23/2023

The initrd.gz and w_init are upgraded to version 7.0.1-rc1 which are constructed from the latest FirstRib skeleton-initrd.

Added the symlink gtk2dialog that targets the binary gtkdialog-8.5 which is compiled against GTK2 which gives access to either gtk2 or gtk3.

@fredx181 has repaired a bug in save2flash and modified swapper.sh to adapt for the /mnt/home device showing directly in Thunar and on the desktop. swapper.sh activates any swap partitions available to KLV-Airedale during system start.

From a suggestion by @wiak added in a modification to w_init that will display icons for /mnt/home partition in Thunar and on the desktop.

New and improved tuning of the /boot directory boot stanza's. improving the reliability of booting in QEMU, Ventoy and S2SG.

Improved and rebuilt initrd.qz including expanded support for SD cards.

Routine system update/upgrade. And wallpapers from @Sofiya are included, replacing some of the stock xfce4 backgrounds.

@wiak has again done more work improving the boot system menus and further improvement to the initrd.gz boot mechanisms :

The iso config file boot/grub/menu.lst is used to boot from cdrom using that internal to iso provided menu.lst (i.e. he currently uses grub4dos for that purpose).
The iso config file boot/grub/loopback.cfg is used (per usual) to provide the boot menu for SG2D
The iso config file boot/grub/grub.cfg is used by Ventoy (but included no Ventoy-compatible entries until my alterations below)

I have made some modifications to all of the above (though have left previous entries in place for later experimentation and possible modification or deletion).
In particular I have provided the ability when booting via SG2D or Ventoy of using the FR modes:

a. RAM0 for session changes in RAM only (i.e. no save persistence)
b. RAM2 save on demand mode back to upper_changes folder (or ucimg savefile) in same directory iso is stored (or in subdirectory if symlink manually made to iso).
c. RAM2 save on demand mode back to upper_changes folder in, Clarity suggested, partition with LABEL 'Persistence' and directory 'Sessions'
d. Direct save (not in RAM) back to upper_changes folder (or ucimg savefile) in same directory iso is stored (or in subdirectory if symlink manually made to iso).
e. Direct save (not in RAM) back to upper_changes folder in, Clarity suggested, partition with LABEL 'Persistence' and directory 'Sessions'

No editing of the presented SG2D or Ventoy boot menus will be required to achieve these most useful FR initrd modes. User just needs to put the KLV iso in BOOTISOS (or wherever it is put usually) and boot...

starting of the pulseaudio system for any user that is logged in has been fixed and improved. Thanks wiak, Sofiya and fredx181 for the exact steps.

Upgraded to a new version of @fredx181 's save2flash, and set LANG=en_US.UTF-8 in /etc/environment as default localization.

Thanks to @Sofiya for the poorercputemp and Display Control packages that also have been added to desktop.

• Grub4Dos is now included in the System menu. Making KLV-Airedale capable of setting up a boot-able device using GParted and Grub4Dos.

• CUPS starting as a service has been added and is working thanks to @rcrsn51 spotting missing components!

This is constructed from KLV-Airedale-beta27->rc1->rc2->rc3->rc4->rc4.1 and is equipped with a Void Linux kernel version 6.0.12_1 SMP PREEMPT_DYNAMIC constructed with @wiak 's scripts that will extract the Void Linux kernel for KLV. Also has had a system wide upgrade. Uses an initrd.gz based on the FirstRib skeleton initrd.gz constructed by the kernel/module creation script. Firmware SFS is from a woof-CE kernel-kit built huge 6.0.0-1 kernel.

KLV-Airedale-rc5 is just as at home on FAT32, NTFS prtitions as it is running from ext2/3/4 formatted partitions.

Also included is wiak's generate a set of boot stanzas script. fredx181's mksplash has a menu entry and the remaster script is installed.

With the addition of a xfce4 desktop tiling configuration. A tip from wiak for configuring Tiling windows done with the Super (Windows) key and an up, down, left, right, home, pgup, pgdown or end key.

gxmessage in the default rootfs.

save2flash has been expanded to handle persistence on FAT32 and NTFS partitions.
The mksplash GUI utility to create splash notification banners.

The latest initrd.gz brings vFat and NTFS formatted partition support to KLV, allowing persistence on NTFS/vFat systems as well as the usual /ext2/ext3/ext4/swap support.

• included htop, Grub4Dos, CUPS

• created a symlink /root/spot with the target /home/spot

• Auto login cleaned up.

• includes also the logout logic provided by fredx181 gives true mulit-user support.

• replaced loop.cfg to the most recent modifications.

• Debian kernel 6.0.0-3-KLV SMP PREEMPT DYNAMIC is used.

• added gtkhash

Plus the other important improvements contributed by the KLV team.

Added @fredx181's save2flash utility that can be used when KLV is started in RAM2 mode to perform session saves on demand for persistence.
This is similar to PUPMODE13 in Puppy Linux.

fredx181's swap partition enable script includes the latest revisions and also added are the packages

• mime-add-1.0_0.noarch.xbps

• edit-sfs-1.0_0.noarch.xbps

KLV-Airedale-beta25 is able to load squash SFS packages on the fly or during the boot sequence.
Squash files and ISO images can be opened from the file manager and the read the contents.

• can run with rootfs, 01fimware and 00module SFS files as uncompressed directories.

• Also able to load compressed and/or decompressed directories,
  once a 2 digit prefix is added to the file name.

• It is possible to mix using compressed squash files and uncompressed directories.

Also can be downloaded from https://rockedge.org/kernels in ISO->Kennel_Linux->Airedale

To set the SAMBA user password use:

smbpasswd -a root

Example screenshot running Applications->Internet->Samba Simple Management and the samba daemon on by default at boot :

Just tested RC15.

By now, I'm sure that everyone knows that when using the stanzas that I provide, you can exchange information from your VM with the HOST PC using the VM's utilities. If the HOST has its SAMBA server running, the VM OS can see it on IP address 10.0.2.2.

smbclient is not showing resources that the HOST is sharing. This is a bug.

But the resources are there as this picture shows: And using the filemanager you can see the mounted resources.

The VM stanza used is

qemu-system-x86_64 -enable-kvm -vga cirrus -m 2G -smp 2 -device AC97 -net nic -net user -rtc base=localtime -name "KLV-Airedale-rc15 via QEMU" -cdrom KLV-Airedale-rc15.iso

P.S. This is UNRELATED: F96 operates with normal results.

HOST PC is sharing this:

#this is a very simple smb.conf to get you started
#coutesy rcrsn51 and gcmartin
[global]
	workgroup = Workgroup
	netbios name = FossaPUP64
	server string = Puppy Samba Server
	security = user
	map to guest = Bad Password
	printing = cups
	printcap name = cups
	load printers = yes

[Multimedia]
	path = /mnt/sda2/Multimedia
	writable = yes

[printers]
	comment = All Printers
	path = /var/spool/samba
	browseable = no
	guest ok = yes
	writable = no
	printable = yes

I am having trouble booting RC15 ISO file on my platforms via Ventoy & SG2D. I am booting bare-metal. Could be due to a recent power outage for couple days closing down everything in the home. I am seeing couple other anomalies on other home units; but that just may be coincidental. No boot issue in QEMU booting from the ISO file.

Anyone else having RC15 boot issues?

Is there anything I can provide before it traps that would be useful?

I'm still running RC-13, but it looks like the only significant change is Samba and the login fix.

OctoXBPS is not finding one of the repos, the non-free repo: https://mirror.vofr.net/voidlinux/curre ... 4-repodata:

I think this happened one time before.

I was still able to successfully do system updates on two machines.

Just a heads up.

@geo_c Yes that's correct! Only the Samba and the GUI and the login fix to ensure the agetty-tty1 service is down.

I have been able to run the repo updates so far successfully today so far......but that does happen on occasion and it is during a repo update done on the upstream side of things.

xbps consists of several utilities. The main ones are:

xbps-install -Su - system update.
xbps-install- is a utility for installing, reinstalling, and updating packages.
xbps-query- is a utility for getting information about packages and information about repositories.
xbps-remove- is a utility for removing packages.
xbps-reconfigure- is a utility for configuring installed packages.
xbps-pkgdb- is a utility for troubleshooting, reporting, and modifying the package database.
xbps-rindex- is a utility for managing local repositories of binary packages.
xbps-alternatives- is a utility for working with alternatives.

@rockedge
Read the "Summary" of this distribution on Sourceforge and...

unique ability to load uncompressed physical directories into the layers hierarchy

It sounds interesting so a few questions:
1. This would work like mounting an sfs file (drive at startup or loaded during a session (on the fly)?
2. Any impact on RAM usage (apart from copying to RAM at bootup, I suppose) compared to loading/mounting an sfs file. I know the loading of an sfs file uses a small amount of RAM (neglectable really.
3. Any obvious advantages compared to using sfs files instead especially in terms of performance. Why should one want to go this route since obviously contents of a folder can be corrupted unlike an sfs file which has the advantages of being read-only (and compact in size)? Also - in my experience applications packed as sfs's starts faster for me when the sfs has been loaded on the fly compared to the same application run from a folder in uncompressed state from the same partition.

Thanks.

@amethyst,

This would work like mounting an sfs file (drive at startup or loaded during a session (on the fly)?

Yes, exactly

Any impact on RAM usage (apart from copying to RAM at bootup, I suppose) compared to loading/mounting an sfs file. I know the loading of an sfs file uses a small amount of RAM

a small increase in RAM usage but increased load speeds because there is no file compression,

Any obvious advantages compared to using sfs files instead especially in terms of performance. Why should one want to go this route since obviously contents of a folder can be corrupted unlike an sfs file which has the advantages of being read-only (and compact in size)? Also - in my experience applications packed as sfs's starts faster for me when the sfs has been loaded on the fly compared to the same application run from a folder in uncompressed state from the same partition.

The biggest advantage is that because one can mix using SFS and uncompressed components. Meaning while working on development of the distro it is possible to directly modify the file system and see the results immediately. Often I'll work this way and then once satisfied with the work I can squash the directories again.

Then there is the "pseudo full install" which is the entire 07KLV-airedal_rootfs.sfs decompressed and renamed to /upper_changes and a empty dummy rootfs directory named 07Dummy_rootfs to replace the SFS. This all in a frugal install directory/ the biggest advantage is the system acts like a fully installed Linux and all updates and changes are directly written to the /upper_changes. A file deleted is actually deleted and updates are written.

It is possible at any time to take the /upper_changes in this case and squash it to 07KLV-airedal_rootfs.sfs at any time. It is possible to mix compressed and decompressed SFS.

This adds to a nice way for example to experiment with the 01firmware and 00modules directly by adding and removing parts while the distro is up and running.

Any directory or SFS file with a 2 digit prefix (0 - 99) will be loaded and layered in sequence during the system boot. i.e. 30upper_changes, 52some.sfs

@wiak can really explain this all in great detail and has quite bit of documentation but is kind of scattered around still at the moment.

Hope this helps and please ask any questions on what is unclear. I can't type as fast as I think of what I intend to say!