Puppy Linux Discussion Forum

[peebee]

[mikeslr]

Thanks peebee,

Probably could have used your first suggestion, but your second method worked fine with Xenialpup64.

Ally, changing the "pfs" ending to "sfs" does, in fact, enable their contents to be viewed and perhaps used with non-Russian-built Puppies. However, I have some doubts about the later. An examination of the included files revealed several with suffixes I'm not familiar with from my dissection of other Puppies and applications.

I didn't test, nor expend the time which would have been necessary to ascertain how those files functioned within their system.

mikesLr

[ozsouth]

I've made a 64bit Slacko compatible 4.9.94 kernel via Puppy kernel-kit, with the cutdown firmware option. Is Spectre/Meltdown mitigated.
Adding needed firmware to (or using another) fdrv will be helpful. Uses performance cpu governor by default (max speed).
Have swapped it into Slacko64 6.9.9.9 and LxpupSc64 18.03. Works ok in both. As usual, use at own risk.

Kernel: http://archive.org/download/Puppy_Linux_Huge-Kernels/huge-4.9.94-s64.tar.bz2
md5: a84bf520693321ffa78062fe9335097e huge-4.9.94-s64.tar.bz2

Sources: https://archive.org/download/Puppy_Linux_Kernels/kernel_sources-4.9.94-s64.sfs
md5: 25c7d6be2f67188d98b7e2f3e339f94b output/kernel_sources-4.9.94-s64.sfs

Thanks to ally for mirroring.
.

[ally]

mirrored here: http://archive.org/details/Puppy_Linux_Huge-Kernels

http://archive.org/download/Puppy_Linux_Huge-Kernels/huge-4.9.94-s64.tar.bz2

[musher0]

[peebee]

[ozsouth]

Info on 4.9.94 64bit kernel 4 posts up, as I should have done it at first.
.

[ozsouth]

I've made a 64bit Slacko compatible 4.14.35 kernel via Puppy kernel-kit, with the no firmware option. Is Spectre/Meltdown mitigated.
Needs firmware by making own (or using another) fdrv . Uses performance cpu governor by default (max speed). As usual, use at own risk.

Kernel: https://archive.org/download/Puppy_Linux_Huge-Kernels/huge-4.14.35-s64oz.tar.bz2
md5: bcfb60c7cb3aeccc725656078ef7726d huge-4.14.35-s64oz.tar.bz2

Sources: https://archive.org/download/Puppy_Linux_Kernels/kernel_sources-4.14.35-s64oz.sfs
md5: 79db21861a5d2d9be9a94c11de5822ab output/kernel_sources-4.14.35-s64oz.sfs
.

[ally]

mirrored here: http://archive.org/details/Puppy_Linux_Huge-Kernels

and here:

http://archive.org/details/Puppy_Linux_Kernels

[ozsouth]

I made a 64bit Slacko compatible 4.14.47 kernel via Puppy kernel-kit, with the no firmware option. Need firmware by making (or using another) fdrv.
Is Spectre/Meltdown mitigated. Uses performance cpu governor by default (max speed).
Have swapped it into Slacko64 6.9.9.9 and LxpupSc64 18.03. Works ok in both. As usual, use at own risk.

Kernel: https://archive.org/download/Puppy_Linux_Huge-Kernels/huge-4.14.47-s64oz.tar.bz2
md5: 5f7f80ffa2ba8250fc0beba240cbb002

Sources: https://archive.org/download/Puppy_Linux_Kernels/kernel_sources-4.14.47-s64oz.sfs
md5: 92af983e8df7a9bfa807d5fc914bdfe8
.

[ozsouth]

I've made a 64bit Slacko compatible 4.14.69 kernel via Puppy kernel-kit, with the no firmware option.
Is Spectre/Meltdown mitigated - except microcode update is needed for spectre 3a, for some processors.

Needs firmware by making own (or using another) fdrv . Uses performance cpu governor by default (max speed).
Have swapped it into Slacko64 6.9.9.9 and LxpupSc64 18.03. Works ok in both. As usual, use at own risk.

Kernel: https://archive.org/download/Puppy_Linux_Huge-Kernels/huge-4.14.69-s64oz.tar.bz2
md5: 4b7d415d8b9cd469a2530212fba51214 huge-4.14.69-s64oz.tar.bz2

Sources: https://archive.org/download/Puppy_Linux_Kernels/kernel_sources-4.14.69-s64oz.sfs
md5: 5a20cef507725ee2068016cdc3d723f5 kernel_sources-4.14.69-s64oz.sfs
.

[ozsouth]

Kernels are not directly interchangeable between slacko & ubuntu derivatives. Problem is /usr/lib64. In slacko it is a physical directory; in ubuntu it is a symlink to /usr/lib. In bionic64, zdrv uses /usr/lib64 as a physical directory, which contains the libau.* files (that would be correct for a slacko derivative). They should be in /usr/lib and /usr/lib64 should be a symlink of that. This was the case in xenial64. Loading .pets in the wrong base often causes the same problem. For those with issues in ubuntu derivatives, try moving /usr/lib64 files into /usr/lib, deleting /usr/lib64, then symlinking /usr/lib to /usr/lib64.

[mikeslr]

Although the workaround he suggested should work, I'm not sure ozsouth is entirely correct. I've been employing kernel version 4.15.0-lxpup64 in Xenialpup64 for several months now without a problem running any application: originally under Xenialpup64-7.0.8, the last week or two under Xenialpup64-7.5. Tahrpup64 also uses that kernel.

Slackos, which are binary-compatible with Slackware, use of /lib64 folders to hold 64-bit libraries. The problem with the "Ubuntu-Pups" is that they are binary-compatible with either Ubuntu Trusty Tahr or Ubuntu Xenial Xerus with access to their respective Ubuntu repos. Ubuntu published those to locate 64-bit libraries in folders bearing the names x86_64-linux-gnu*. I think its a 'woof' problem, but neither Tahrpup64 nor Xenialpup64 have ever been able to recognize the existence of those folders. Applications created for Ubuntu when used under "Ubuntu-Pups" are unable to find the libraries located in such folders. So, the 'work-around' was to move libs from them into /lib and create symbolic links named x86_64-linux-gnu to /lib.

It should be noted that Tahrpup and Xenialpup will recognize /lib64 folders and find files placed in them. As a result applications built for 64-bit Slackos which placed libraries in /lib64 can be used in "Ubuntu-Pups" without having to move such libs ['though they may require other libs and some tweaking].

I think only with Xenialpup64-7.5 were the symlinks named x86_64-linux-gnu built into the structure of puppy_xenialpup64-7.5.sfs. This may cause a problem with packages obtained by accessing Ubuntu repos directly using a web-browser or via PPM: those packages may not be able to follow the symbolic link to place libs in /lib. [That's not the case if PaDS is used to create SFSes or Pets, as it is constructed to move such libs 'behind the scenes' during the build process].

The real solution would be to modify woof and pet-get so that “Ubuntu Pups” were consistent with Slacko Pups: use /lib64 for 64-bit libraries, and automatically –behind the scene-- relocate libs from x86_64-linux-gnu to /lib64. [My suggestion to modify woof so that 'Ubuntu-Pups' handle multi-arch the same way as Ubuntu either having fallen on deaf ears or been 'cries in the wilderness'. But on reflection, providing consistency among Puppies would, in fact, be the better course].

* There are actually several folders bearing that name: at least one under /lib, one under /usr/lib, and another under /usr/local/lib. I’m not sure about “sbin” folders. Although Ubuntu uses three folders, it would probably suffice if Ubuntu-Pups use one, perhaps /usr/lib64.

[peebee]

Woof-CE:
get rid of the multiarch symlink #1224

[ozsouth]

I've made a 64bit Xenial/Bionic compatible 4.14.79 kernel via Puppy kernel-kit, with the no firmware option. Is Spectre/Meltdown mitigated (except 3a). Needs firmware by making own (or using another) fdrv . Uses performance cpu governor by default (max speed). Tested OK in Xenialpup64-7.5. As usual, use at own risk.

Kernel: https://archive.org/download/Puppy_Linux_Huge-Kernels/huge-4.14.79-u64oz.tar.bz2
md5: efaf5d0ee64d9858da35123c8ed84932

Sources: http://www.filepup.net/files/983617521541749886.html (until about 23/11).
md5: e0a3ea28b2438788e7ebca5877efcd46
.