01 Nov 2024 - puppy_vpup64_22.02 only'

[Jasper]

A new ISO has been released on 01 Nov 2024 and it features an older kernel 6.1.x

If you want to continue with the existing kernel from the last release k6.6.53 - (09 Oct 2024), here is the puppy_vpup64_22.02 from the 01 Nov 2024 ISO.

puppy_vpup64_22.02.sfs

https://www.mediafire.com/file/qgvcbs37 ... 2.sfs/file

Thanks to Peebee

[Wiz57]

Are you sure you want to use this as an "adrv.sfs"? To be clear, the kernel is vmlinuz, and the corresponding drivers are in the zdrv.sfs.
The adrv.sfs should be reserved for "applications", and most of peabee's ISOs contain an adrv.sfs consisting of the "Light" web browser
for viewing the respective documentation and basic web browsing. The drivers need to be compiled with the kernel, that's why when
I do a kernel swap, I copy not only the vmlinuz, but also the matching zdrv.sfs.
It is possible to change the adrv.sfs, or even delete it completely. The precaution here is that some default links, such as to the "help"
documents no longer work, as the "default application" is not included (the Light browser). In the past, I have renamed the adrv.sfs to
like adrv-s15pup22.12.bak, then renamed something like a palemoon.sfs to adrv-s15pup22.12.sfs, reboot and Palemoon is loaded
instead of Light...but you still have to edit the links and default applications for HTML viewer and web browser. I've also just renamed
the adrv.sfs to adrv.bak and rebooted, this saves a tiny bit of RAM, functions same as deleting it.

[Jasper]

@Wiz57

Thanks for pointing out my error, it was the 'core' file I meant not the supplemental 'adrv' in this instance.

Changed the title now.

Luckily ......... I added screenshots

[Wiz57]

In this case, you may as well use the previous ISO, as the "puppy_vpup_XXX" contains the actual
Puppy distro. If you want to change the kernel, follow my directions above, I would suggest not
doing those copy, rename etc procedures while the target Pup is booted! What I do is boot to another
Pup, something like old Slacko 6.3.2 32 bit...then open my file manager (Rox or PcManFM), to the
frugal install directory of target Pup, rename vmlinuz as vmlinuz.bak, rename the zdrv-XXX.sfs as
zdrv-XXX.bak (where XXX is the name of the Puppy target) then copy and paste the desired vmlinuz
and zdrv-XXX.sfs from my stash directory of alternate kernels, lol, to the target folder. Rename
the zdrv.XXX.sfs to the target zdrv, then reboot, choosing the now kernel swapped pup. I'm running
an S15Pup32 right now that I did that with, from 4-13-2024, but I swapped the kernel and zdrv from
an old ArchPup32 which the NTFS-3G driver seems more responsive to me on this old Acer Aspire One,
since it multi-boots a variety of Pups, as well as Windows XP Pro SP3! I also use the LXDE desktop
via ydrv.sfs from peabee, with a 1 gig swap file on the NTFS drive. Newer 5X 32 bit kernels seem to
be a bit better, but the first 5X 32 bit kernels were very slow with the newer NTFS3 drivers. Here is
the results of "free" in Lxterminal immediately after bootup to desktop on this old netbook...
# free
total used free shared buff/cache available
Mem: 1009764 96708 408572 23268 504484 865812
Swap: 1048572 0 1048572
#

And here is the current, runnning Palemoon 33.4.0.1 32 bit GTK3, 2 tabs open ...
# free
total used free shared buff/cache available
Mem: 1009764 324532 76604 44672 608628 665604
Swap: 1048572 0 1048572
#

Not bad! I've had as many as 10 tabs open, and only used about 5kb swap!

[Jasper]

@Wiz57

I swapped the kernel and zdrv from an old ArchPup32 which the NTFS-3G driver seems more responsive

I am a bit intrigued ........... can you let me know what kernel you are currently using and which build of NTFS-3g you have installed?

On my FP-95 .... older kernel but newer NTFS-3g driver

[Wiz57]

# uname -a
Linux puppypc20561 4.14.173-lxpup-32-pae #1 SMP Fri Mar 13 07:42:34 GMT 2020 i686 Intel(R) Atom(TM) CPU N270 @ 1.60GHz GenuineIntel GNU/Linux
# ntfs-3g
ntfs-3g: No device is specified.

ntfs-3g 2022.10.3 integrated FUSE 27 - Third Generation NTFS Driver
Configuration type 1, XATTRS are on, POSIX ACLS are off

Copyright (C) 2005-2007 Yura Pakhuchiy
Copyright (C) 2006-2009 Szabolcs Szakacsits
Copyright (C) 2007-2022 Jean-Pierre Andre
Copyright (C) 2009-2020 Erik Larsson

Usage: ntfs-3g [-o option[,...]] <device|image_file> <mount_point>

Options: ro (read-only mount), windows_names, uid=, gid=,
umask=, fmask=, dmask=, streams_interface=.
Please see the details in the manual (type: man ntfs-3g).

Example: ntfs-3g /dev/sda1 /mnt/windows

Plugin path: /usr/lib/ntfs-3g

News, support and information: https://github.com/tuxera/ntfs-3g/
#

It appears I'm using the same NTFS-3G driver, SO, perhaps peabee has changed to using NTFS-3G
instead of the later NTFS3 driver, due to speed issues I've noted above. As I mentioned, the newer
releases of the 5X kernels don't seem to have the extreme slowdowns I noticed a few years back
with the first 5X kernels on NTFS drives. At the time, ScPup32 was "latest" Slackware release from
peabee, still have it on this old netbook too! That's when I started swapping kernels. I am testing
peabee's latest S15Pup32 (as usual)...if it continues to perform as desired, I'll eventually make it
my "daily driver".

[Jasper]

@Wiz57

Thanks for sharing

The final release of your kernel was 4.14.334. (...........maybe someone could compile this for you or might be able to source it elsewhere)

This was published late Dec 2023 / Jan 2024, so I would say it's still a recent kernel.

https://cdn.kernel.org/pub/linux/kernel ... 334.tar.xz
https://cdn.kernel.org/pub/linux/kernel ... 4.tar.sign
https://cdn.kernel.org/pub/linux/kernel ... g-4.14.334

The branch 4.19.xxx will be retired at the end of this year.

Something you might want to consider is an update to your I/O library.

Info from ArchWiki

https://man.archlinux.org/man/extra/libuv/libuv.1.en

For me this does make my OS more responsive.

Libuv

https://github.com/libuv/libuv

Linux >= 3.10 with glibc >= 2.17

[Clarity]

Hi @Jasper

Did you notice the PC @Wiz57 is showing for the changes?

You use 64bit PCs in your work over the years along with current v6+ kernels and @peebee's distros all use v6+ kernels as well.

[Wiz57]

Hi @Jasper

Did you notice the PC @Wiz57 is showing for the changes?

You use 64bit PCs in your work over the years along with current v6+ kernels and @peebee's distros all use v6+ kernels as well.

Regarding peebee's releases, the 64bit are using version 6.X kernels, but the 32bit Pups are still version 5.X. I don't know if
ANYONE is doing version 6.X 32bit kernels??

[rockedge]

I don't know if ANYONE is doing version 6.X 32bit kernels??

I am having trouble compiling 32 bit versions of 6.X kernels in general and with AUFS in particular.

Still trying to do a build successfully. I am thinking of reactivating a DELL Optiplex which is 32 bit only made for Windows XP and running the compiling attempts on that computer using a 32 bit distro like Bionicpup32 or a newly made 32 bit KLV-jwm for 32 Bit package and huge kernel building.

See how that goes time wise.......

[Jasper]

@Wiz57

the 32bit Pups are still version 5.X. I don't know if
ANYONE is doing version 6.X 32bit kernels??

That's interesting, might be worth asking in the main 'Users' section.

[rockedge]

you can get Void Linux 32 bit kernels in the 6.X series. But you need a huge 32 Bit for Puppy Linux?

You know for 4-5 years I had a whole repo of 32 bit kernels including full real time versions.....no downloads. Now threatened with account suspension because of using the server as a repo I have deleted all those to bring down the Gigabytes.

Which kernel version would be interesting?

[peebee]

NoblePup32 was using k6.6 - had to drop back to k6.1 for 241101 release - but will be back to k6.6 for next release now that aufs for k6.6 is fixed