Porteus Kernel Builder

[benjibasson]

Hi,
I have forgoten to update initrd befor removing iso. can someone push inird in the mirror in updated kernel's folder please?

[ncmprhnsbl]

can someone push inird in the mirror in updated kernel's folder please?

the latest initrds are in the <mirror>/x86_64/Porteus-v5{.01,1}/install-skeleton-64.tar.xz

[benjibasson]

Thanks

[Blaze]

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

7.0.12 <-- NEW : "All patches" patching was done.
32bit-ALL-kernel7.0.12.tar (~262M)
https://disk.360.yandex.ru/d/hnfmPGhwO70T-g (click on the button - Скачать)
73daa096e118b0ed7f10910d9e789716 32bit-ALL-kernel7.0.12.tar

Simple package (vmlinuz, 000-kernel-NNN-XXbit.xzm, 06-crippled_sources-NNN-XXbit.xzm, 64bit.config)

7.0.12 <-- NEW : "All patches" patching was done.
64bit-ALL-kernel7.0.12.tar (~282M)
https://disk.360.yandex.ru/d/9F0b2_Rwb2dypQ (click on the button - Скачать)
f3b7f2af202eb6670410914758d4e7a9 64bit-ALL-kernel7.0.12.tar

Note 1: Compiler that was used.
for kernel 7.0.12: 11.2.0

Note 2: Compilated under Porteus 5.01 (Slackware 15.0 base)

Note 3: Cryptsetup 2.8.3

Note 4: BORE (Burst-Oriented Response Enhancer) CPU Scheduler patch has been applied.
More info is here https://github.com/firelzrd/bore-scheduler

Thanks

[AcnapyxoB]

Thanks Blaze.
Everything is working on Porteus 5.01 x86_64.
There's no problem with the VirtualBox compilation either (that's usually what I complain about)

[fu11m00n]

@ Blaze... thanks.

fu11m00n, do you want Aarch64 (ARM) kernel version?

I'm ready for your Aarch64 (ARM) kernel.
Let me know where I can download.

My OS is based on Slackware 15.0 stable version.
https://mirrors.dotsrc.org/porteus/x86_ ... .0/kernel/

I'm almost finished with the Q3 release (v2.63) of my OS.
https://oreivd96v420wee4.umso.co/

I am currently @ #15 (out of > 175) on the DistroWatch waiting list.

@ the end of the year (Q4) I will pay DistroWatch the $250/USD fee to advance from it's waiting list to the main list.
Your kernel will be key to my OS moving up the DistroWatch rankings so I can join PorteuX in introducing users to Porteus.

Once I'm in the top 100 DistroWatch rankings... YouTube influencers will consider seriously reviewing my project.

Again... thank you in advance for your creation.

[Blaze]

Hi fu11m00n,
I compiled kernel for Aarch64 (ARM64) under Porteus 5.1 (Slackware-current)
I hope it works since I used cross compilation with Arm GNU Toolchain 13.3.Rel1 (Build arm-13.24)) 13.3.1 20240614

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

7.0.12 <-- NEW : "All patches" patching was done.
64bit-ALL-kernel7.0.12.tar (~262M)
https://disk.360.yandex.ru/d/jVF8JwQITEuhnQ (click on the button - Скачать)
0cd8b5ed206e3471cc8fd2b54f40d252 64bit-ALL-kernel7.0.12.tar

Note 1: Compiler that was used.
for kernel 7.0.12: aarch64-none-linux-gnu-gcc (Arm GNU Toolchain 13.3.Rel1 (Build arm-13.24)) 13.3.1 20240614

Note 2: Compilated under Porteus 5.1 (Slackware-current)

Note 3: Cryptsetup 2.8.3

Note 4: BORE (Burst-Oriented Response Enhancer) CPU Scheduler patch has been applied.
More info is here https://github.com/firelzrd/bore-scheduler

Thanks

[fu11m00n]

@ Blaze... thanks.

Because of your creation it may now be possible to bring ARM to Porteus.
I will contact Stuart Winter (Slackware ARM) to integrate your creation into his project.
I am trying to release my refactored Q3 version of my OS so I will try to test your kernel in July.

Note 4: BORE (Burst-Oriented Response Enhancer) CPU Scheduler patch has been applied

Is SELinux kernel and/or "huge pages" functionality possible?

And perhaps preempt-rt and possibly the "Nest" scheduler instead of BORE?
https://www.youtube.com/watch?v=s5-UbeuJfbk

Thanks in advance for any solutions.

PS: Could you PM me for info to ship you a Pinetab (Aarch64/ARM) to test?
https://pine64.com/product/pinetab2-10- ... -keyboard/

I have not shipped in over 10 yrs but I will attempt.
Last time I shipped a GPU to Brazil for Brokenman.

[Blaze]

Is SELinux kernel and/or "huge pages" functionality possible?

Yes, Huge Pages is fully activated and will work by default.

Code: Select all

CONFIG_CGROUP_HUGETLB=y
CONFIG_HAVE_ARCH_TRANSPARENT_HUGEPAGE=y
CONFIG_HAVE_ARCH_HUGE_VMAP=y
CONFIG_HAVE_ARCH_HUGE_VMALLOC=y
CONFIG_ARCH_WANT_HUGE_PMD_SHARE=y
CONFIG_ARCH_ENABLE_HUGEPAGE_MIGRATION=y
# CONFIG_PERSISTENT_HUGE_ZERO_FOLIO is not set
CONFIG_TRANSPARENT_HUGEPAGE=y
CONFIG_TRANSPARENT_HUGEPAGE_ALWAYS=y
# CONFIG_TRANSPARENT_HUGEPAGE_MADVISE is not set
# CONFIG_TRANSPARENT_HUGEPAGE_NEVER is not set
CONFIG_TRANSPARENT_HUGEPAGE_SHMEM_HUGE_NEVER=y
# CONFIG_TRANSPARENT_HUGEPAGE_SHMEM_HUGE_ALWAYS is not set
# CONFIG_TRANSPARENT_HUGEPAGE_SHMEM_HUGE_WITHIN_SIZE is not set
# CONFIG_TRANSPARENT_HUGEPAGE_SHMEM_HUGE_ADVISE is not set
CONFIG_TRANSPARENT_HUGEPAGE_TMPFS_HUGE_NEVER=y
# CONFIG_TRANSPARENT_HUGEPAGE_TMPFS_HUGE_ALWAYS is not set
# CONFIG_TRANSPARENT_HUGEPAGE_TMPFS_HUGE_WITHIN_SIZE is not set
# CONFIG_TRANSPARENT_HUGEPAGE_TMPFS_HUGE_ADVISE is not set
CONFIG_PGTABLE_HAS_HUGE_LEAVES=y
CONFIG_ARCH_SUPPORTS_HUGE_PFNMAP=y
CONFIG_ARCH_SUPPORTS_HUGETLBFS=y
CONFIG_HUGETLBFS=y
CONFIG_HUGETLB_PAGE=y
CONFIG_HUGETLB_PMD_PAGE_TABLE_SHARING=y

but SELinux is not activated

Code: Select all

# CONFIG_SECURITY_SELINUX is not set

this is philosophy of Slackware.

And perhaps preempt-rt and possibly the "Nest" scheduler instead of BORE?

No reason for this coz

Nest — An abandoned academic experiment: The project made a striking debut at the Linux Plumbers Conference but ran into implementation difficulties. Custom kernel developers (including the CachyOS team) attempted to integrate its support; however, the patch proved unstable, causing boot failures on certain CPU configurations and requiring manual process pinning via taskset. Currently, the development of the original Nest patch is effectively frozen.

Could you PM me for info to ship you a Pinetab (Aarch64/ARM) to test?

Oh, thanks, but it's not worth it.

Last time I shipped a GPU to Brazil for Brokenman.

I hope brokenman is okay.

[fu11m00n]

@ Blaze thanks...

Is SELinux kernel and/or "huge pages" functionality possible?

but SELinux is not activated

Code: Select all

# CONFIG_SECURITY_SELINUX is not set

this is philosophy of Slackware.

Is it possible to activate preempt-rt and SELinux? If so how would it be done (perhaps /etc/sysctl.conf)?
Some of the documentation I've read says it requires the respective kernel modules.
My project's use case departs from both Slackware and Porteus.
I'm building a 1u Aarch64 Beowulf cluster (2 nodes = 14 processors = 56 cores)...
The "Captain Howdy" Project (Post by fu11m00n #105431)

My interest in mission critical preempt-rt (RTOS and Nest style) schedulers is to mitigate resource
contention and starvation under load in servers instead of reducing gaming latency (eg. CachyOS)...
https://www.youtube.com/watch?v=hRsWi4HIENc&t=122s
https://www.youtube.com/watch?v=FJcc8X4MUxM

SELinux is a custom security feature (used by Alpine Linux) for users like me that need that security feature.
The GNU ecosystem is a major part of Slackware yet my custom project mostly departs from it's use case.
In my current release I'm refactoring to replace all third party packages (eg. SlackDCE) with OpenMandriva (Musl/Clang).
The future roadmap for my project is to introduce the microkernel that I discussed with Brokenman 10 yrs ago.
That along with numerous other features I plan to introduce intentionally... makes my 6yr project an outlier.

I fully agree with the (Slackware) upstream philosophy's use case in which the goal is mainstream use.
My project however is focused on custom use case.
That said... all of the "mainstream" benefits from my project I intend to fully share with Porteus.
However... before I can share I have to build my custom project 1st to attain my goals.

Patrick Volkerding (the Slackware maintainer) and Stuart Winter (Slackware Aarch64) are aware of what I am doing and support it (for my use case).
They are both mentoring me @ Linux Questions forum. I last discussed my project philosophy with Patrick on his birthday last Fall.

Many thanks for your very important contribution and thanks in advance for any new solutions.

[Blaze]

fu11m00n, I updated this post Porteus Kernel Builder (Пост Blaze #105539)

Code: Select all

#
# No trust source selected!
#
CONFIG_ENCRYPTED_KEYS=y
# CONFIG_USER_DECRYPTED_DATA is not set
CONFIG_KEY_DH_OPERATIONS=y
CONFIG_SECURITY_DMESG_RESTRICT=y
CONFIG_PROC_MEM_ALWAYS_FORCE=y
# CONFIG_PROC_MEM_FORCE_PTRACE is not set
# CONFIG_PROC_MEM_NO_FORCE is not set
# CONFIG_MSEAL_SYSTEM_MAPPINGS is not set
CONFIG_SECURITY=y
CONFIG_HAS_SECURITY_AUDIT=y
CONFIG_SECURITYFS=y
CONFIG_SECURITY_NETWORK=y
CONFIG_SECURITY_NETWORK_XFRM=y
CONFIG_SECURITY_PATH=y
CONFIG_LSM_MMAP_MIN_ADDR=32768
# CONFIG_STATIC_USERMODEHELPER is not set
CONFIG_SECURITY_SELINUX=y
CONFIG_SECURITY_SELINUX_BOOTPARAM=y
CONFIG_SECURITY_SELINUX_DEVELOP=y
CONFIG_SECURITY_SELINUX_AVC_STATS=y
CONFIG_SECURITY_SELINUX_SIDTAB_HASH_BITS=9
CONFIG_SECURITY_SELINUX_SID2STR_CACHE_SIZE=256
CONFIG_SECURITY_SELINUX_AVC_HASH_BITS=9
# CONFIG_SECURITY_SELINUX_DEBUG is not set
# CONFIG_SECURITY_SMACK is not set
# CONFIG_SECURITY_TOMOYO is not set
# CONFIG_SECURITY_APPARMOR is not set
# CONFIG_SECURITY_LOADPIN is not set
# CONFIG_SECURITY_YAMA is not set
# CONFIG_SECURITY_SAFESETID is not set
# CONFIG_SECURITY_LOCKDOWN_LSM is not set
CONFIG_SECURITY_LANDLOCK=y
# CONFIG_SECURITY_IPE is not set
# CONFIG_INTEGRITY is not set
# CONFIG_IMA_SECURE_AND_OR_TRUSTED_BOOT is not set
# CONFIG_DEFAULT_SECURITY_SELINUX is not set
CONFIG_DEFAULT_SECURITY_DAC=y
CONFIG_LSM="landlock,lockdown,yama,loadpin,safesetid,integrity,selinux"

[fu11m00n]

@ Blaze thanks...

Note 2: Compilated under Porteus 5.1 (Slackware-current)

I'm using Slackware "stable" kernel 5.0 (07/03/22).
Perhaps kernel 5.0 will work better than 5.1.
https://mirrors.dotsrc.org/porteus/x86_ ... .0/kernel/

Also do you have a matching x86_64 modified kernel with the same preempt-rt and SELinux features?
I can use it in my current Q3 (June) fu11m00n/OS x86_64 release when I modify /etc/sysctl.conf.

I forgot to mention my API... CLI and GUI are not 100% Slackware.

But my toolchain... Linux From Scratch... X11 and Slackware minimal install ("/a" directory) xzm modules are 100% Slackware.
Last month I repeatedly broke my system trying to force OpenMandriva (for 3 weeks) into those modules.
So you are correct... some things require 100% Slackware. Going forward I'm only using OpenMandriva for 3rd party.

Thanks in advance for any new solutions.

[Blaze]

Also do you have a matching x86_64 modified kernel with the same preempt-rt and SELinux features?

I don't have it.

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

7.1.1 <-- NEW : "All patches" patching was done.
64bit-ALL-kernel7.1.1.tar (~264M)
https://disk.360.yandex.ru/d/xp8eRj-6dDynOQ (click on the button - Скачать)
3a82015b69bb1d88004e10abe56c950b 64bit-ALL-kernel7.1.1.tar

Note 1: Compiler that was used.
for kernel 7.1.1: aarch64-none-linux-gnu-gcc (Arm GNU Toolchain 13.3.Rel1 (Build arm-13.24)) 13.3.1 20240614

Note 2: Compilated under Porteus 5.1 (Slackware-current)

Note 3: Cryptsetup 2.8.3

Note 4: BORE (Burst-Oriented Response Enhancer) CPU Scheduler patch has been applied.
More info is here https://github.com/firelzrd/bore-scheduler

Note 5: The default security settings are set to SELinux

Code: Select all

CONFIG_SECURITY_SELINUX=y
CONFIG_SECURITY_SELINUX_BOOTPARAM=y
CONFIG_SECURITY_SELINUX_DEVELOP=y
CONFIG_SECURITY_SELINUX_AVC_STATS=y
CONFIG_SECURITY_SELINUX_SIDTAB_HASH_BITS=9
CONFIG_SECURITY_SELINUX_SID2STR_CACHE_SIZE=256
CONFIG_SECURITY_SELINUX_AVC_HASH_BITS=9
# CONFIG_SECURITY_SELINUX_DEBUG is not set
# CONFIG_SECURITY_SMACK is not set
# CONFIG_SECURITY_TOMOYO is not set
# CONFIG_SECURITY_APPARMOR is not set
# CONFIG_SECURITY_LOADPIN is not set
# CONFIG_SECURITY_YAMA is not set
# CONFIG_SECURITY_SAFESETID is not set
# CONFIG_SECURITY_LOCKDOWN_LSM is not set
CONFIG_SECURITY_LANDLOCK=y
# CONFIG_SECURITY_IPE is not set
# CONFIG_INTEGRITY is not set
# CONFIG_IMA_SECURE_AND_OR_TRUSTED_BOOT is not set
CONFIG_DEFAULT_SECURITY_SELINUX=y
# CONFIG_DEFAULT_SECURITY_DAC is not set
CONFIG_LSM="landlock,lockdown,yama,loadpin,safesetid,integrity,selinux"

Thanks

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

7.1.1 <-- NEW : "All patches" patching was done.
64bit-ALL-kernel7.1.1.tar (~274M)
https://disk.360.yandex.ru/d/31-JoREMwI_lkw (click on the button - Скачать)
1e0cdab872f94ca7638f4df5e549d8e1 64bit-ALL-kernel7.1.1.tar

Note 1: Compiler that was used.
for kernel 7.1.1: 15.2.0-x86_64

Note 2: Compilated under Porteus 5.1 alpha 4 (Slackware-current base)

Note 3: Cryptsetup 2.8.3

Note 3: BORE (Burst-Oriented Response Enhancer) CPU Scheduler patch has been applied.
More info is here https://github.com/firelzrd/bore-scheduler

Thanks

[fu11m00n]

@ Blaze... thanks.

Ok.

I'm using Stuart Winter's Slackware ARM Aarch64 15.0 repo.
Stuart uses Slackware 15.0 stable for his ARM repo.
https://slackware.uk/slackwarearm/slack ... slackware/

I'm not sure if your 15.1 kernel is compatible.

A almost finished my x86_64 release. I will be ready to start on Aarch64 in about 2 weeks.

Thanks in advance for any new solutions.