Superseded.
If you still want to try it (with old puppies only), it is in Kernel archive:
https://archive.org/download/Puppy_Linux_Huge-Kernels
Moderator: Forum moderators
Superseded.
If you still want to try it (with old puppies only), it is in Kernel archive:
https://archive.org/download/Puppy_Linux_Huge-Kernels
Your .config and mine (from fatdog DOTconfig) are fairly similar where it comes to aufs. Both builds work well and no problems might be obvious running standard puppies. However, in Lighthouse, up to 40 sfs modules can be loaded via aufs. This kernel version balks and only loads 12 in three different builds. I've done some googling and the only thing I could come up with is that CONFIG_BLOCK_LEGACY_AUTOLOAD is no longer supported. This has caused boot and shutdown and raid problems according to both arch-wiki and LQ-slackware forum. May not be my problem though. I'm moving back to kernel version 5 (5.19.17 builds and runs well).
df
@Dry Falls - wow! another trap for the unwary. Is kernel 5.15 (LTS & hence more secure due to updates) no use to you? It's EOL has been extended to Oct 2026 (was originally this year).
@debianfan - should be OK for Puppies from about 2017-2022 (will default to aufs). If in doubt, test with a plain usb frugal install first.
I've been testing more the last few days. It seems LTS is meaningless for aufs-patched kernels. I built 5.15.27 with your kernel kit. Earlier 5.15 versions built with suuk (Stemsee's kit). Then 5.16-5.19 all build ok. Tried latest 5.10 and no luck, even though earlier ones built fine. Mr Okajima has pulled support for < aufs5 so testing latest 4.19 failed. From what I understand, we'll have to rebuild old kernels from previously patched kernel sources. Means upgrading will be problematic unless we go to the newest kernel version as Mr Okajima provides an aufs patch for it. The longer LTS lasts, the less likely we'll be able to patch it.
Call me paranoid, but it seems to me security for linux now means what it meant for ms: protect the system from its users. That is to say, it's become proprietary. Consider wayland. You can't even log in as root!
df
@Dry Falls - I'll pm you my last good kernel-kit - used to make this 6.1.14 & other aufs/overlayfs kernels. My chromebook kernels are over a month behind - stops them being caught out - might be a good mitigation for late aufs patches.
We still have bi-weekly 4.19.x, 5.4.x, 5.10.x and 5.15.x builds at https://github.com/puppylinux-woof-CE/w ... el-kit.yml, with the latest longterm releases. Although they still build fine, nobody is actively maintaining aufs for 4.19.x and 5.4.x. Nothing guarantees that aufs is still stable and safe to use (= no data loss or kernel panics) with all the kernel changes since aufs was declared EOL for these branches. I no longer use these kernels in my builds because they're not true LTS kernels, as you say - they have big changes from EOL patches.
(Off-topic comment: dpup already has usable development builds with dwl and labwc)
Indeed @dimkr. Just attempted my quarterly kernel update today for bionicpup64, from your biweekly kernel-kit at github, and the recent build (4.19.275) no longer boots (fails to create an empty aufs stack). 4.19.264 works fine.
Above are reasons I personally use overlayfs only. However, as there is little interest in it in the community, & I was encouraged to make a quarterly aufs/overlayfs kernel, I produced the original post's offering.
One day, when aufs (or GTK+ 2, or X.Org, or other legacy stuff used by most Puppy releases) is no longer an option, Puppy as we know it will die and the winner in this struggle for existence will be a Puppy that defaults to overlay.
Not arguing. Lots has changed since 2005 and we're still here. At this point I'm roughly 50/50, overlay vs AUFS, and its quite nice to have one good LTS kernel that supports both and can be used in all my pups. Toggling is simple via a kernel parameter and the AUFS overhead in the kernel isn't bad so to me it makes sense to support both for now.
My pups: LxPupSc64 and Voidpup64 with LXDE ydrv and synaptics touchpad drivers, both using small savefiles for customizations. Ydrv based NoblePup64 and Fossapup64-small (both LXDE/PCManFM with no savefiles). No fdrvs throughout.
I also build kernels that have both overlayfs built in and are patched with AUFS so both mechanisms are available. Sure eventually AUFS will fade out because SFS-load-on-the-fly is no longer really needed and has been replaced by portable applications.
I sometimes use Puppy Linux huge kernels with specialized Kennel Linux builds so the overlayfs makes that possible. Is there a real need to do this? No there is not....but it seems pretty cool to do.
Is it possible that you can upload the file/s to Mediafire?
I am unable to view Archive.org as my browser/ISP does not allow me to do so.
If not, you might want to edit your first post and remove the last line re: Mediafire
Thanks in advance!
@Jasper - I can - which of the 5 files do you particularly want? The mediafire reference is there because I initially upload to mediafire & wait a couple of days, a) until Ally copies to archive.org & b) to gauge the level of interest in that time. Then I remove them & update links in first post.
sorry to hear you cannot access the archive
feel free to shout me with file requests and I'll send them to gdrive or mega if it helps
It's been a long time since I changed this. So, I had to look again at the files that I downloaded previously.
I believe the only file I need is:
Code: Select all
https://archive.org/download/Puppy_Linux_Huge-Kernels/huge-6.1.14-ubun64oz-ao.tar.bz2
Many thanks to both of you