Porteus

Blaze, can you share ufsd.ko for kernel 5.4.53

babam, ufsd-k.5.4.53-x86_64.xzm

Sorry. I messed up your message. But, what you want is contained in it. Look your post above ^^^

Blaze wrote: ↑

27 Jul 2020, 06:19

[Updated kernel Examples]
==== AUFS Kernel only for Porteus ====
Simple package (vmlinuz, 000-kernel.xzm, 06-crippled_sources-NNN-XXbit.xzm)

[5.4.53] <-- NEW : "All patches" patching was done.
64bit-ALL-kernel5.4.53.tar (92 M)
http://www.mediafire.com/file/ngwwxilis ... 5.4.53.tar
a6e670df08cf9aa9dd76147ca91c0ad9 64bit-ALL-kernel5.4.53.tar

...

Is the logout dialog's "Save session for future logins" radio button disregarded when Porteus boots with the "change=" cheatcode? All I know is that substituting your kernel for the original in Porteus 5.0rc1 caused networking to fail (no devices found). I had used copy2ram to load /base, so I replaced your 001-kernel.xzm with the original one and rebooted through the logout dialog, carefully deselecting "Save session for future logins" when I did so, but I still had no network devices upon reboot. Forty minutes later, after re-installing my desktop, I'm ready to proceed again. This isn't the tenth time this has happened. I'd like to update my kernel; I'd like to understand the process -- I don't want to have to delete /changes over and over again.

Blaze, having manually downloaded the packages needed to update the 001-core module (in /tmp/update), how would I do so in the terminal? I have a general idea of the process, but I still have very little command of Linux syntax -- I don't know how to automate the removal of the old packages or the installation of the new ones. I would also like to update the kernel -- it seems to me networking has failed before when I have attempted to. I see that kernel version 5.8 (maintained by Linus Torvalds) was just released -- any chance you could post a new 000-kernel.xzm of it (that would work)?

rchase wrote: ↑

07 Aug 2020, 00:01

001-core module (in /tmp/update)

ROOT=/patch/to/001-core removepkg name-of-package

Seems aufs.patch http://aufs.sourceforge.net/ is not ready for Kernel version 5.8

Thanks; I guess I'm just going to have to learn some bash. In reference to my complaint above, I had failed to use all three of your files when I booted and had no network devices. I have gotten an otherwise unaltered copy of Porteus 5.0 to boot with network access, but when I tried to replace the kernel on my desktop, it wouldn't boot -- the screen immediately started cycling off and on (displaying nothing); including "debug" in the cheatcodes had no visible effect. Am I doing something wrong, or should upgrading the kernel to 5.4.53 be considered a work in progress?

rchase wrote: ↑

07 Aug 2020, 14:14

Am I doing something wrong,

disregard if you're already doing this:
when upgrading the kernel:
swap out <usb drive>/boot/syslinux/vmlinuz
and <usb drive>/porteus/base/000-kernel.xzm
the vmlinuz is the kernel and 000-kernel.xzm contains the drivers and firmware etc..

[Updated kernel Examples]
==== AUFS Kernel only for Porteus ====
Simple package (vmlinuz, 000-kernel.xzm, 06-crippled_sources-NNN-XXbit.xzm)

[5.4.57] <-- NEW : "All patches" patching was done.
32bit-ALL-kernel5.4.57.tar (91.1 M)
http://www.mediafire.com/file/zn0r6tz79 ... 5.4.57.tar
23131eae2d3885ddb8eff23fd70dd9bf 32bit-ALL-kernel5.4.57.tar

[5.4.57] <-- NEW : "All patches" patching was done.
64bit-ALL-kernel5.4.57.tar (96.4 M)
http://www.mediafire.com/file/qtsvky4o5 ... 5.4.57.tar
7bb737760b7d1fee8e9d1910960b7d27 64bit-ALL-kernel5.4.57.tar

Note : Compiler that was used.
for kernels 5.4.57: 10.2.0-x86_64
Firmware database is made from kernel-firmware-20200803_9bc3789-noarch-1.txz



Thanks to neko for his support.

Blaze Thanks a lot for supporting the 32 bit kernel. )

Anybody managed to obtain AUFS patches for 5.8?

From: J. R. Okajima <hooanon05g@gm...> - 2020-07-01 01:59:39
Hello aufs-users,

I was going to start supporting linux-v5.8-rcN, but unfortunately I have
to suspend it due to some personal issues. For something new in aufs
development, I set its priority lower in my todo list. But bugfix,
supporting users, such like answering the questions, etc. are still have
higher priority.
I shall return to aufs5.x-rcN in a few months.

Thanx for your patience.
J. R. Okajima

from: https://sourceforge.net/p/aufs/mailman/ ... /37050373/

I tried to compile version 5.8.3 with the Neko script, apparently it compiled without problems but I was not lucky. AUFS did not work when starting the system.
I am currently using 5.4.60

withdrawn - sorry

Is this patch fully functional?

[later] threw "bus errors" with chromium so withdrawn

Well............. it performs the patches and the resulting patched code compiles successfully and produces a kernel which boots and runs without any apparent errors.....
But whether it is "fully functional" - it has not had the same testing and level of experience that would be provided by the aufs author J. R. Okajima so should be used with caution and at your risk.
I was able to build 5.8.3 with it.