1. Configure update problem
@roadie
Porteus Kernel Builder (Post by roadie #81422)
I did ordinary configs.
But neko-configs were not done.
It will be updated together with the ID change ("-newAUFif" --> "-porteus").
As a result, even neko-config becomes the conventional AUFS interface.
Support for the new AUFS interface is no longer required.
2. *.c32 problem
@martomlub
ArchLinux packages manager for Porteus (Post by martomlub #81449)
I changed it in response to the indication.
OLD
Code: Select all
# file APorteus-v21.02.12-x86_64/boot/syslinux/*.c32
APorteus-v21.02.12-x86_64/boot/syslinux/chain.c32: COM executable (32-bit COMBOOT, relocatable)
APorteus-v21.02.12-x86_64/boot/syslinux/reboot.c32: COM executable (32-bit COMBOOT, relocatable)
APorteus-v21.02.12-x86_64/boot/syslinux/vesamenu.c32: COM executable (32-bit COMBOOT, relocatable)
#
# md5sum APorteus-v21.02.12-x86_64/boot/syslinux/*.c32
b18960c5d608f4c6aca16e13c9009c2e APorteus-v21.02.12-x86_64/boot/syslinux/chain.c32
c250e917d0b7ff29355b50ce3938efe3 APorteus-v21.02.12-x86_64/boot/syslinux/reboot.c32
dd1de2b0eb02d717de8ff2c0b2fb13af APorteus-v21.02.12-x86_64/boot/syslinux/vesamenu.c32
Code: Select all
# file APorteus-v21.02.19-x86_64/boot/syslinux/*.c32
APorteus-v21.02.19-x86_64/boot/syslinux/chain.c32: ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), dynamically linked, stripped
APorteus-v21.02.19-x86_64/boot/syslinux/ldlinux.c32: ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), dynamically linked, stripped
APorteus-v21.02.19-x86_64/boot/syslinux/libcom32.c32: ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), dynamically linked, stripped
APorteus-v21.02.19-x86_64/boot/syslinux/libutil.c32: ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), dynamically linked, stripped
APorteus-v21.02.19-x86_64/boot/syslinux/reboot.c32: ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), dynamically linked, stripped
APorteus-v21.02.19-x86_64/boot/syslinux/vesamenu.c32: ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), dynamically linked, stripped
#
# md5sum APorteus-v21.02.19-x86_64/boot/syslinux/*.c32
54714afcd298df93dd4335768d84d1fe APorteus-v21.02.19-x86_64/boot/syslinux/chain.c32
f9bb3b4cefdd0308f951dbc6d7532f85 APorteus-v21.02.19-x86_64/boot/syslinux/ldlinux.c32
3629d61c32dd49a23a907a8e7956a2c9 APorteus-v21.02.19-x86_64/boot/syslinux/libcom32.c32
3117264d409f2526cdefad7cf47c53a5 APorteus-v21.02.19-x86_64/boot/syslinux/libutil.c32
7cbb406dc353aa555c0f88e220e297fb APorteus-v21.02.19-x86_64/boot/syslinux/reboot.c32
915521e8588cbc32ca2ef435dbb07e96 APorteus-v21.02.19-x86_64/boot/syslinux/vesamenu.c32
@Blaze
1.
{Including the "compile item ON" at GUI setting, and get the shell script "perform" file.}1) If this option is on - compile of kernel is started automaticly and I am not able to hack perform script
not bad if you set for the perform script kernel options that fulalas shared by deffault in this post
is meening that
{Including the "compile item ON" at GUI setting, and press the "help" button instead of the "OK" button.}
2.
Please tell me which APorteus ISO is the ISO that caused the problem.2) Your ISO is have old *.c32 files at the /boot/syslinux and boot up of APorteus is faile.
Replace all *.c32 files from Porteus 5.0 RC2
Thanks.