Update the kernel of Porteus v3.1

[neko]

***************************************************
Today Porteus new version 3.2.2 is released.
This update kernel tool is for version 3.1 and not for Version 3.2.
Therefore this thread will be closed.

Thank you very much for your interests.

***************************************************



1. Tool of Updating the Kernel of Porteus ISO
1.1. Tool of Updating the Kernel of Porteus v3.1 to the Kernel v3.18.46.

upkernel-3.18.46-noarch-1.xzm (43 M)
http://www.mediafire.com/file/1pme0x9fx ... arch-1.xzm
md5sum: 25e4005a06e7b304ddd0baa579c30625 upkernel-3.18.46-noarch-1.xzm

============================================================================
NAME
upkernel - Updating the Kernel of Porteus ISO file
upakernel - Updating the Kernel of Porteus ISO file and
formatting 000-kernel.xzm on the ArchLinux style.

SYNOPSIS
upkernel Porteus-ISO
upakernel Porteus-ISO

DESCRIPTION
upkernel & upakernel are the tools of Updating the Kernel of Porteus ISO.
upkernel & upakernel must be executed by root.

The updated ISO file will be created in a current directory.
The name of updated ISO file is UP."original ISO file name without pathe" .

The current directory,
it is necessary there is a free space more than twice the target ISO.

the ArchLinux style formatting:
000-kernel.xzm@lib --> usr/lib : symbolic link
000-kernel.xzm@usr/lib

cf.Porteus style formatting:
000-kernel.xzm@lib

example 1.
ISO is 32 bit.
ISO with a path is input.

Code: Select all

# upkernel ../abc/Porteus-XFCE-v3.1-i486.iso
# ls
UP.Porteus-XFCE-v3.1-i486.iso
UP.Porteus-XFCE-v3.1-i486.iso.md5

example 2.
ISO is 64 bit.
ISO without a path is input.
Original ISO is not deleted.

Code: Select all

# upkernel Porteus-KDE4-v3.1-x86_64.iso
# ls
Porteus-KDE4-v3.1-x86_64.iso
UP.Porteus-KDE4-v3.1-x86_64.iso
UP.Porteus-KDE4-v3.1-x86_64.iso.md5

example 3.
Upgraded ISO can be upgraded more.
It doesn't need to increase the number of version in one by one order.
You can skip.(example: skip 3.18.18 and 3.18.19 ; from 3.18.17 to 3.18.20)

Code: Select all

% ls
Porteus-KDE4-v3.1-x86_64.iso
upkernel-3.18.17-noarch-1.xzm
upkernel-3.18.20-noarch-1.xzm
% su
# activate upkernel-3.18.17-noarch-1.xzm
# upkernel Porteus-KDE4-v3.1-x86_64.iso
# ls
Porteus-KDE4-v3.1-x86_64.iso
UP.Porteus-KDE4-v3.1-x86_64.iso
UP.Porteus-KDE4-v3.1-x86_64.iso.md5
upkernel-3.18.17-noarch-1.xzm
upkernel-3.18.20-noarch-1.xzm
# deactivate upkernel-3.18.17-noarch-1.xzm
# activate upkernel-3.18.20-noarch-1.xzm
# upkernel UP.Porteus-KDE4-v3.1-x86_64.iso
# ls
Porteus-KDE4-v3.1-x86_64.iso
UP.Porteus-KDE4-v3.1-x86_64.iso
UP.Porteus-KDE4-v3.1-x86_64.iso.md5
UP.UP.Porteus-KDE4-v3.1-x86_64.iso
UP.UP.Porteus-KDE4-v3.1-x86_64.iso.md5
upkernel-3.18.17-noarch-1.xzm
upkernel-3.18.20-noarch-1.xzm

note)
UP.Porteus-KDE4-v3.1-x86_64.iso is updated to kernel 3.18.17.
UP.UP.Porteus-KDE4-v3.1-x86_64.iso is updated to kernel 3.18.20 from 3.18.17.

============================================================================

1.2. Tool of Updating the Kernel of Porteus v3.1 to the Kernel v4.1.37.

upkernel-4.1.37-noarch-1.xzm (42 M)
http://www.mediafire.com/file/teier6tba ... arch-1.xzm
md5sum: 4e2081fd13d0c969f269fd22ece42a23 upkernel-4.1.37-noarch-1.xzm

============================================================================
NAME
upkernel4.1 - Updating the Kernel of Porteus ISO file
upakernel4.1 - Updating the Kernel of Porteus ISO file and
formatting 000-kernel.xzm on the ArchLinux style.

SYNOPSIS
upkernel4.1 Porteus-ISO
upakernel4.1 Porteus-ISO

DESCRIPTION
upkernel4.1 & upakernel4.1 are the tools of Updating the Kernel of Porteus ISO.
upkernel4.1 & upakernel4.1 must be executed by root.

The updated ISO file will be created in a current directory.
The name of updated ISO file is UP."original ISO file name without pathe" .

The current directory,
it is necessary there is a free space more than twice the target ISO.

the ArchLinux style formatting:
000-kernel.xzm@lib --> usr/lib : symbolic link
000-kernel.xzm@usr/lib

cf.Porteus style formatting:
000-kernel.xzm@lib

example.
ISO is 32 bit.
ISO with a path is input.

Code: Select all

# upkernel4.1 ../abc/Porteus-XFCE-v3.1-i486.iso
# ls
UP.Porteus-XFCE-v3.1-i486.iso
UP.Porteus-XFCE-v3.1-i486.iso.md5

============================================================================

1.3. Tool of Updating the Kernel of Porteus v3.1 to the Kernel v4.4.39.

upkernel-4.4.39-noarch-1.xzm (44 M)
http://www.mediafire.com/file/164etv1bz ... arch-1.xzm
md5sum: 671a28b00f7a03caaf57b2141f07fff4 upkernel-4.4.39-noarch-1.xzm

============================================================================
NAME
upkernel4.4 - Updating the Kernel of Porteus ISO file
upakernel4.4 - Updating the Kernel of Porteus ISO file and
formatting 000-kernel.xzm on the ArchLinux style.

SYNOPSIS
upkernel4.4 Porteus-ISO
upakernel4.4 Porteus-ISO

DESCRIPTION
upkernel4.4 & upakernel4.4 are the tools of Updating the Kernel of Porteus ISO.
upkernel4.4 & upakernel4.4 must be executed by root.

The updated ISO file will be created in a current directory.
The name of updated ISO file is UP."original ISO file name without pathe" .

The current directory,
it is necessary there is a free space more than twice the target ISO.

the ArchLinux style formatting:
000-kernel.xzm@lib --> usr/lib : symbolic link
000-kernel.xzm@usr/lib

cf.Porteus style formatting:
000-kernel.xzm@lib

example.
ISO is 32 bit.
ISO with a path is input.

Code: Select all

# upkernel4.4 ../abc/Porteus-XFCE-v3.1-i486.iso
# ls
UP.Porteus-XFCE-v3.1-i486.iso
UP.Porteus-XFCE-v3.1-i486.iso.md5

============================================================================

1.4. Tool of Updating the Kernel of Porteus v3.1 to the Kernel v4.8.15.

upkernel-4.8.15-noarch-1.xzm (47 M)
http://www.mediafire.com/file/wp35kzdkx ... arch-1.xzm
md5sum: 9a24c652dafe9edd97d6af2b9e380ac1 upkernel-4.8.15-noarch-1.xzm

============================================================================
NAME
upkernel4.8 - Updating the Kernel of Porteus ISO file
upakernel4.8 - Updating the Kernel of Porteus ISO file and
formatting 000-kernel.xzm on the ArchLinux style.

SYNOPSIS
upkernel4.8 Porteus-ISO
upakernel4.8 Porteus-ISO

DESCRIPTION
upkernel4.8 & upakernel4.8 are the tools of Updating the Kernel of Porteus ISO.
upkernel4.8 & upakernel4.8 must be executed by root.

The updated ISO file will be created in a current directory.
The name of updated ISO file is UP."original ISO file name without pathe" .

The current directory,
it is necessary there is a free space more than twice the target ISO.

the ArchLinux style formatting:
000-kernel.xzm@lib --> usr/lib : symbolic link
000-kernel.xzm@usr/lib

cf.Porteus style formatting:
000-kernel.xzm@lib

example.
ISO is 32 bit.
ISO with a path is input.

Code: Select all

# upkernel4.8 ../abc/Porteus-XFCE-v3.1-i486.iso
# ls
UP.Porteus-XFCE-v3.1-i486.iso
UP.Porteus-XFCE-v3.1-i486.iso.md5

============================================================================

1.5. Tool of Updating the Kernel of Porteus v3.1 to the Kernel v4.9.

upkernel-4.9-noarch-2.xzm (47 M)
http://www.mediafire.com/file/xia5yocdx ... arch-2.xzm
md5sum: b57b84bfdad054a39d0b0c11b416c276 upkernel-4.9-noarch-2.xzm

============================================================================
NAME
upkernel4.9 - Updating the Kernel of Porteus ISO file
upakernel4.9 - Updating the Kernel of Porteus ISO file and
formatting 000-kernel.xzm on the ArchLinux style.

SYNOPSIS
upkernel4.9 Porteus-ISO
upakernel4.9 Porteus-ISO

DESCRIPTION
upkernel4.9 & upakernel4.9 are the tools of Updating the Kernel of Porteus ISO.
upkernel4.9 & upakernel4.9 must be executed by root.

The updated ISO file will be created in a current directory.
The name of updated ISO file is UP."original ISO file name without pathe" .

The current directory,
it is necessary there is a free space more than twice the target ISO.

the ArchLinux style formatting:
000-kernel.xzm@lib --> usr/lib : symbolic link
000-kernel.xzm@usr/lib

cf.Porteus style formatting:
000-kernel.xzm@lib

example.
ISO is 32 bit.
ISO with a path is input.

Code: Select all

# upkernel4.9 ../abc/Porteus-XFCE-v3.1-i486.iso
# ls
UP.Porteus-XFCE-v3.1-i486.iso
UP.Porteus-XFCE-v3.1-i486.iso.md5

============================================================================

2. Kernel
Kernels were built by "mkKernel" command of the APorteus ISO builder.
About "mkKernel" command, please refer to http://forum.porteus.org/viewtopic.php? ... 997#p36689

2.1. Kernel v3.18.46
(1) source
linux-3.18.46.tar.xz
https://www.kernel.org/pub/linux/kernel ... .46.tar.xz
sha256sum: cb404757b727faceae9fe1a436ef0cd12d37d54c67df4814f36b00c4bad17b4a linux-3.18.46.tar.xz

(2) aufs patch
is gotten by the following commands.

Code: Select all

# git clone git://git.code.sf.net/p/aufs/aufs3-standalone aufs3-standalone.git
# cd aufs3-standalone.git
# git checkout origin/aufs3.18.1+

Those command lines are gotten from the tutorial of "Compilation and usage of custom Porteus kernel".
"origin/aufs3.7" in shell script of the tutorial is for 3.7.x kernel.

git clone git://git.code.sf.net/p/aufs/aufs3-standalone aufs3-standalone.git
cd aufs3-standalone.git
# uncomment line below to get aufs for stable kernel
git checkout origin/aufs3.7

Please refer to
Porteus home page -> INFO -> Tutorials -> Development -> Compilation and usage of custom Porteus kernel
http://www.porteus.org/component/conten ... ernel.html

Getting script get.aufs.3.18.patch and
the result aufs-3.18.patch (AUFS_VERSION "3.18.1+-20160822") are offered
in upkernel-3.18.46-noarch-1.xzm.

(3) config
Almost new functions are not included.
note) main changes
CONFIG_USB_UAS=y
CONFIG_NAMESPACES=y

By activating upkernel-3.18.46-noarch-1.xzm, there are
/usr/local/share/upkernel/config/32bit-v3.18.46-config .... config for 32 bit
/usr/local/share/upkernel/config/64bit-v3.18.46-config .... config for 64 bit
/usr/local/share/upkernel/config/get.aufs.3.18.patch ...... getting aufs patch script
/usr/local/share/upkernel/config/aufs-3.18.patch .......... created aufs patch
============================================================================

2.2. Kernel v4.1.37
(1) source
linux-4.1.37.tar.xz
https://www.kernel.org/pub/linux/kernel ... .37.tar.xz
sha256sum: da139c1a78a0d4e37931de33030c73d8e4a2a2e155eeface9a50f7692b263bee linux-4.1.37.tar.xz

(2) aufs patch
is gotten by the following commands.

Code: Select all

# git clone git://github.com/sfjro/aufs4-standalone.git aufs4-standalone.git
# cd aufs4-standalone.git
# git checkout origin/aufs4.1.13+

Getting script get.aufs4.1.13.patch and
the result auf4.1.13.patch (AUFS_VERSION "4.1.13+-20161219") are offered
in upkernel-4.1.37-noarch-1.xzm.

(3) config
Almost new functions are not included.
note) main changes
CONFIG_USB_UAS=y
CONFIG_NAMESPACES=y *)note 1:

By activating upkernel-4.1.37-noarch-1.xzm, there are
/usr/local/share/upkernel/config/32bit-v4.1.37-1.config .... config for 32 bit
/usr/local/share/upkernel/config/64bit-v4.1.37-1.config .... config for 64 bit
/usr/local/share/upkernel/config/get.aufs4.1.13.patch ...... getting aufs patch script
/usr/local/share/upkernel/config/auf4.1.13.patch ........... created aufs patch

*) note 1:
CONFIG_NAMESPACES was set.
But when Google Chrome browser is executed without option "--disable-gpu", it will be fault.
============================================================================

2.3. Kernel v4.4.39
(1) source
linux-4.4.39.tar.xz
https://www.kernel.org/pub/linux/kernel ... .39.tar.xz
sha256sum: 864bc186b02bf62974676efa282eda775fe12e5729a3416cfe4b17f0c59111a1 linux-4.4.39.tar.xz

(2) aufs patch
is gotten by the following commands.

Code: Select all

# git clone git://github.com/sfjro/aufs4-standalone.git aufs4-standalone.git
# cd aufs4-standalone.git
# git checkout origin/aufs4.4

Getting script get.aufs4.4.patch and
the result aufs4.4.patch (AUFS_VERSION "4.4-20160912") are offered
in upkernel-4.4.39-noarch-1.xzm.

(3) config
kernel config is converted from the one of "Porteus-XFCE-v3.2-i586.iso"/"Porteus-XFCE-v3.2-x86_64.iso" kernel.
Almost new items are set in 'N' when are converted.

By activating upkernel-4.4.39-noarch-1.xzm,
there are
/usr/local/share/upkernel/config/32bit-v4.4.39-1.config ... config for 32 bit
/usr/local/share/upkernel/config/64bit-v4.4.39-1.config ... config for 64 bit
/usr/local/share/upkernel/config/get.aufs4.4.patch ........ getting aufs patch script
/usr/local/share/upkernel/config/aufs4.4.patch ............ created aufs patch
============================================================================

2.4. Kernel v4.8.15
(1) source
linux-4.8.15.tar.xz
https://www.kernel.org/pub/linux/kernel ... .15.tar.xz
sha256sum: 1605260913729b7b72a64a0598b782725e365dab57d49dec188373d634538fee linux-4.8.15.tar.xz

(2) aufs patch
is gotten by the following commands.

Code: Select all

# git clone git://github.com/sfjro/aufs4-standalone.git aufs4-standalone.git
# cd aufs4-standalone.git
# git checkout origin/aufs4.8

Getting script get.aufs4.8.patch and
the result aufs4.8.patch (AUFS_VERSION "4.8-20161010") are offered
in upkernel-4.8.15-noarch-1.xzm.

(3) config
kernel config is same as the one of "Porteus-XFCE-v3.2-i586.iso"/"Porteus-XFCE-v3.2-x86_64.iso" kernel.

By activating upkernel-4.8.15-noarch-1.xzm,
there are
/usr/local/share/upkernel/config/32bit-v4.8.15-1.config ...... config for 32 bit
/usr/local/share/upkernel/config/64bit-v4.8.15-1.config ...... config for 64 bit
/usr/local/share/upkernel/config/get.aufs4.8.patch .......... getting aufs patch script
/usr/local/share/upkernel/config/aufs4.8.patch .............. created aufs patch
============================================================================

2.5. Kernel v4.9
(1) source
linux-4.9.tar.xz
https://www.kernel.org/pub/linux/kernel ... 4.9.tar.xz
sha256sum: 029098dcffab74875e086ae970e3828456838da6e0ba22ce3f64ef764f3d7f1a linux-4.9.tar.xz

(2) aufs patch
is gotten by the following commands.

Code: Select all

# git clone git://github.com/sfjro/aufs4-standalone.git aufs4-standalone.git
# cd aufs4-standalone.git
# git checkout origin/aufs4.9

Getting script get.aufs4.9.patch and
the result aufs4.9.patch (AUFS_VERSION "4.9-20161219") are offered
in upkernel-4.9-noarch-2.xzm.

(3) config
kernel config is converted from the one of "Porteus-XFCE-v3.2-i586.iso"/"Porteus-XFCE-v3.2-x86_64.iso" kernel.
Almost new items are set in 'N' when are converted.
"overlayfs" is statically linked to kernel.(CONFIG_OVERLAY_FS=y)
CONFIG_NAMESPACES=y, CONFIG_UTS_NS=y, CONFIG_IPC_NS=y, CONFIG_PID_NS=y, CONFIG_NET_NS=y

By activating upkernel-4.9-noarch-2.xzm,
there are
/usr/local/share/upkernel/config/32bit-v4.9-2.config ........ config for 32 bit
/usr/local/share/upkernel/config/64bit-v4.9-2.config ........ config for 64 bit
/usr/local/share/upkernel/config/get.aufs4.9.patch ............. getting aufs patch script
/usr/local/share/upkernel/config/aufs4.9.patch ..................... created aufs patch
============================================================================

3. Initrd
The original source 'linuxrc' of initrd.xz has been rewritten.
ISO@/boot/syslinux/initrd.xz ... updated (add a new cheatcode)
Executable entities of 'initrd.xz' were replaced with ones that were gotten from 'ArchLinux' packages.

3.1. Initrd of kernel v3.18.xx
(32 bit)
ISO@/porteus/kernel-v3.18.46-i486.sgn ..... ISO identification for boot
(64 bit)
ISO@/porteus/kernel-v3.18.46-x86_64.sgn ... ISO identification for boot

(1) separate the relation of 001-core.xzm from initrd.xz.
Please refer to
http://forum.porteus.org/viewtopic.php?f=53&t=4990

(2) include new cheatcodes.
============================================================================

3.2. Initrd of kernel v4.1.x
(32 bit)
ISO@/porteus/kernel-v4.1.37-1-i486.sgn ..... ISO identification for boot
(64 bit)
ISO@/porteus/kernel-v4.1.37-1-x86_64.sgn ... ISO identification for boot

(1) include new cheatcodes.
============================================================================

3.3. Initrd of ISO created by 'upkernel4.4'/'upakernel4.4' command
(32 bit)
ISO@/porteus/kernel-v4.4.39-1-i486.sgn ..... ISO identification for boot
(64 bit)
ISO@/porteus/kernel-v4.4.39-1-x86_64.sgn ... ISO identification for boot

(1) include new cheatcodes.
============================================================================

3.4. Initrd of ISO created by 'upkernel4.8'/'upakernel4.8' command
(32 bit)
ISO@/porteus/kernel-v4.8.15-1-i486.sgn ..... ISO identification for boot
(64 bit)
ISO@/porteus/kernel-v4.8.15-1-x86_64.sgn ... ISO identification for boot

(1) include new cheatcodes.
============================================================================

3.5. Initrd of ISO created by 'upkernel4.9'/'upakernel4.9' command
(32 bit)
ISO@/porteus/kernel-v4.9-2-i486.sgn ..... ISO identification for boot
(64 bit)
ISO@/porteus/kernel-v4.9-2-x86_64.sgn ... ISO identification for boot

(1) include new cheatcodes.
============================================================================

3.6. New cheatcodes
(1) a new cheatcode 'retry' (described in ISO@/boot/docs/cheatcodes.txt)

... Retry the load only once, if the load of the Porteus data faled.
Before retry, reset USB2/USB3 ports.
This cheatcode is usefull for unstable booting from the storage via USB.

(2) a new cheatcode 'systemd' (described in ISO@/boot/docs/cheatcodes.txt)

systemd=/path/new-init-program
... This cheatcode specifies the new first program.
In place of the default program to start the first time after Porteus space setting,
the specified program is running.
Example: 'systemd=/usr/lib/systemd/systemd'

upkernel4.4: default program 'init'
upakernel4.4: default program '/usr/lib/systemd/systemd'

(3) a new cheatcode 'persist' (simple persistence method. described in ISO@/boot/docs/cheatcodes.txt)

... This cheatcode sets the symbolic links as followed.
If there is the directory '/live/porteus/persist' on ext4 file system partition,
the '/home' directory will be symbolic link to
the directory '/live/porteus/persist/home' on ext4 file system partition.
and
the '/etc/NetworkManager' directory will be symbolic link to
the directory '/live/porteus/persist/etc/NetworkManager' on ext4 file system partition.

Examples:
/dev/sdb3 is a ext4 file system partition.
1. 1st. boot without 'persist' and prepare as followed.
% su
$ mkdir -p /mnt/sdb3/live/porteus/persist/etc
$ mkdir -p /mnt/sdb3/live/porteus/persist/home
$ cp -a /etc/NetworkManager /mnt/sdb3/live/porteus/persist/etc/.
$ cp -a /home/* /mnt/sdb3/live/porteus/persist/home/.
2. 2nd. boot with 'persist'

============================================================================

4. Tools for a new ISO test
4.1. "ISO to USB" conversion tool module
live-usb-3.1-noarch-7.xzm (352 K)
http://www.mediafire.com/download/jq6o4 ... arch-7.xzm
md5sum: 1b968454f535df3545db3e9b94ec8c21 live-usb-3.1-noarch-7.xzm

[for the Porteus that is constructed with ArchLinux packages]
Alive-usb-16.02.07-noarch-1.xzm (864 K)
http://www.mediafire.com/download/v98w4 ... arch-1.xzm
md5sum: 9e2d341b59ec8fa1479fe379e00b3d7a Alive-usb-16.02.07-noarch-1.xzm

If the 1st partition size is selected MAX(USB size),
one partition will be created in USB.
Otherwise, 2 partitions will be created in USB.
The 2nd partition is used by only linux users.

The 1st partition file system is FAT/ext4.
The contents of ISO will be set in the 1st partition.

The 2nd partition file system is one of FAT, ext3, ext4.
The 2nd partition may be used for general purpose.
If the 2nd partition file system is a linux file system (ext4 ,ext3) ,
it can be used for a persistence directory.
It can be used for a persistence loop file data setting area.

-------------------------------------------------------------------
[updated on 2015.07.22] tool for all (KDE,MATE,LXQT,XFCE,LXDE,FVWM)
[updated on 2015.08.01] add new functions
[updated on 2015.08.09] Bug fix:If the 1st. partition size is max, this program will abort.
[updated on 2015.08.22] Instead of a EFI boot loader from ISO, set a simplified version (bootx64.efi) in EFI/boot.
[updated on 2015.11.12]improvement: live-usb can be executed without /opt/porteus-scripts/xorg/psu.
[updated on 2016.01.17]Improvement: set an icon for missing case.
[updated on 2016.02.07] add Alive-usb-16.02.07-noarch-1.xzm for the Porteus that is constructed with ArchLinux packages.

-------------------------------------------------------------------

4.2. Benchmarks test tool modules
[32 bit]
hardinfo-i686.xzm (422 K)
http://www.mediafire.com/download/54wxt ... o-i686.xzm

[64 bit]
hardinfo-x86_64.xzm (397 K) note) not include "GPU Drawing"
http://www.mediafire.com/download/7olo2 ... x86_64.xzm




Thanks.


[archive]
3.18.45 http://www.mediafire.com/file/2s7rbqkbx ... arch-1.xzm
4.1.36 http://www.mediafire.com/file/hafvx3p35 ... arch-1.xzm
4.2.8 http://www.mediafire.com/download/vmx8y ... arch-1.xzm
4.3.6 http://www.mediafire.com/download/l8d17 ... arch-1.xzm
4.4.38 http://www.mediafire.com/file/pq1pjxspt ... arch-1.xzm
4.5.7 http://www.mediafire.com/download/w6cp5 ... arch-1.xzm
4.6.7 http://www.mediafire.com/download/ki5i2 ... arch-1.xzm
4.7.10 http://www.mediafire.com/file/q9v5xjxx0 ... arch-1.xzm
4.8.14 http://www.mediafire.com/file/kl5gk6ykj ... arch-1.xzm
4.9 http://www.mediafire.com/file/ubul6we49 ... arch-1.xzm

4.3.3-v3.5.upnkernel http://www.mediafire.com/download/ysjaq ... arch-1.xzm
---------------------------------------------------
[updated on 2015.07.10]
[updated on 2015.07.13]
[updated on 2015.07.23]
[updated on 2015.07.24]
[updated on 2015.08.09] updated to kernel v3.18.20
[updated on 2015.09.03] updated to kernel v3.18.21
[updated on 2015.10.09] updated to kernel v3.18.22
[updated on 2015.10.13] add new commands "upkernel4,upakernel4"
[updated on 2015.10.28] updated to kernel v4.2.5
[updated on 2015.11.03] updated to kernel v3.18.23. And add new command "upakernel"
[updated on 2015.11.07] updated to kernel v3.18.24
[updated on 2015.11.11] updated to kernel v4.2.6
[updated on 2015.11.16] add upkernel4.3, upakernel4.3, upnkernel commands
[updated on 2015.11.19] change a set of firmware in kernel v4.3.0.
[updated on 2015.12.14] update to kernel v4.2.7, v4.3.2
[updated on 2015.12.19] update to kernel v3.18.25, v4.2.8, v4.3.3
[updated on 2016.01.08] update to kernel nemesis-v3.5 v4.3.3
[updated on 2016.01.23] add upkernel4.4, upakernel4.4 commands
[updated on 2016.01.28] update to kernel v4.3.4
[updated on 2016.01.29] delete v4.2.x. add v4.1.x.
[updated on 2016.02.05] update to kernel v4.1.17, v4.3.5, v3.18.26, v4.4.1
[updated on 2016.02.17] update to kernel v3.18.27, v4.1.18
[updated on 2016.02.18] update to kernel v4.4.2
[updated on 2016.02.21] update to kernel v4.3.6.
[updated on 2016.02.29] update to kernel v4.4.3.
[updated on 2016.03.04] update to kernel v4.4.4.
[updated on 2016.03.06] update to kernel v3.18.28, v4.1.19
[updated on 2016.03.10] update to kernel v4.4.5.
[updated on 2016.03.17] update to kernel v4.4.6.
[updated on 2016.03.18] update to kernel v3.18.29, v4.1.20.
[updated on 2016.04.08] update to kernel v3.18.30, v4.1.21.
[updated on 2016.04.13] update to kernel v4.4.7. add upkernel4.5, upakernel4.5 commands.
[updated on 2016.04.22] update to kernel v3.18.31, v4.1.22, v4.4.8, v4.5.2.
[updated on 2016.04.29] update to kernel v3.18.32, v4.1.23.
[updated on 2016.05.07] update to kernel v4.4.9, v4.5.3.
[updated on 2016.05.13] update to kernel v4.5.4, v4.4.10, v4.1.24, v3.18.33.
[updated on 2016.05.17] add upkernel4.6, upakernel4.6 commands.
[updated on 2016.05.20] update to kernel v4.4.11, v4.5.5.
[updated on 2016.05.26] update to kernel v3.18.34, v4.1.25
[updated on 2016.06.04] update to kernel v4.4.12, v4.5.6, v4.6.1.
[updated on 2016.06.09] update to kernel v3.18.35, v4.1.26, v4.4.13, v4.5.7, v4.6.2.
[updated on 2016.06.24] update to kernel v3.18.36, v4.1.27.
[updated on 2016.06.27] update to kernel v4.4.14, v4.6.3.
[updated on 2016.07.13] update to kernel v4.4.15, v4.6.4.
[updated on 2016.07.14] update to kernel v3.18.37, v4.1.28.
[updated on 2016.07.29] update to kernel v4.4.16, v4.6.5.
[updated on 2016.08.01] update to kernel v3.18.38, v4.1.29.
[updated on 2016.08.09] add upkernel4.7, upakernel4.7 commands. delete upkernel4.5, upakernel4.5 commands.
[updated on 2016.08.11] update to kernel v3.18.39, v4.1.30, v4.4.17, v4.6.6.
[updated on 2016.08.17] update to kernel v4.4.18, v4.6.7, v4.7.1.
[updated on 2016.08.21] update to kernel v4.4.19, v4.7.2.
[updated on 2016.08.27] update to kernel v3.18.40, v4.1.31.
[updated on 2016.09.07] update to kernel v3.18.41, v4.1.32.
[updated on 2016.09.15] update to kernel v4.4.20, v4.7.3. add upkernel4.8/upakernel4.8 command.
[updated on 2016.09.18] update to kernel v4.4.21, v4.7.4.
[updated on 2016.09.19] update to kernel v3.18.42, v4.1.33.
[updated on 2016.09.19] update to kernel v4.8-rc7.
[updated on 2016.09.25] update to kernel v4.4.22, v4.7.5.
[updated on 2016.09.27] update to kernel v4.8-rc8.
[updated on 2016.10.07] update to kernel v4.4.23, v4.7.6, v4.8.
[updated on 2016.10.08] update to kernel v4.4.24, v4.7.7, v4.8.1.
[updated on 2016.10.13] update to kernel v3.18.43, v4.1.34.
[updated on 2016.10.18] update to kernel v4.4.25, v4.7.8, v4.8.2.
[updated on 2016.10.22] update to kernel v4.4.26, v4.7.9, v4.8.3.
[updated on 2016.10.23] update to kernel v4.4.27, v4.7.10, v4.8.4.
[updated on 2016.10.25] update to kernel v3.18.44, v4.1.35.
[updated on 2016.10.29] update to kernel v4.4.28, v4.8.5.
[updated on 2016.11.02] update to kernel v4.4.30, v4.8.6.
[updated on 2016.11.07] update config of v4.8.6.
[updated on 2016.11.11] update to kernel v4.4.31, v4.8.7.
[updated on 2016.11.15] update to kernel v4.4.32, v4.8.8.
[updated on 2016.11.19] update to kernel v4.4.33, v4.8.9.
[updated on 2016.11.22] update to kernel v4.4.34, v4.8.10.
[updated on 2016.11.26] update to kernel v4.4.35, v4.8.11.
[updated on 2016.12.01] update to kernel v3.18.45, v4.1.36.
[updated on 2016.12.03] update to kernel v4.4.36, v4.8.12.
[updated on 2016.12.09] update to kernel v4.4.37, v4.8.13.
[updated on 2016.12.09] update to kernel v4.4.38, v4.8.14.
[updated on 2016.12.17] update to kernel v4.4.39, v4.8.15.
[updated on 2016.12.18] add upkernel4.9, upakernel4.9 commands.
[updated on 2016.12.25] update to kernel v4.9 (config change)
[updated on 2016.12.01] update to kernel v3.18.46, v4.1.37.

[ztrapl]

I updated kernel. Everything is alright. Thank you.

[neko]

@ztrapl
Thank you for your interest.
Please enjoy the taste of a new kernel.

Thanks.

[Ed_P]

A very interesting concept neko. But when I tried it tonight the resulting ISO, once defragged, didn't support any Wi-Fi connections on my machine.

Code: Select all

guest@porteus:~$ ./bootmode.sh
Boot device: /mnt/sda5
OS: Porteus-v3.1
ARCH: x86_64
Kernel: Linux porteus 3.18.18-porteus
quiet from=/ISOs/UP.Porteus-LXQT-v3.1-x86_64.iso changes=EXIT:/porteus3.1/changes/porteussave.dat extramod=/porteus3.1/Modules volume=40 ramsize=80%  
guest@porteus:~$

[neko]

@Ed_P
I apologize that multiplied by the trouble to You in an incomplete examination.
If you have time, you can tune the 'upkernel' command in the following way.


[tuning 'upkernel' command]
1. prepare 05-devel.xzm
32 bit
http://dl.porteus.org/i486/current/modules/05-devel.xzm
64 bit
http://dl.porteus.org/x86_64/current/mo ... -devel.xzm

2. set resources in the work directory.
(1)linux-3.18.18.tar.xz
https://www.kernel.org/pub/linux/kernel ... .18.tar.xz
(2)v3.18.18-config.tgz (276 K)
http://www.mediafire.com/download/qo5tx ... config.tgz

---------------------------------------
% su
# xz -dc linux-3.18.18.tar.xz | tar -x
# tar -xzf v3.18.18-config.tgz
# cd linux-3.18.18/
# patch -p1 < ../v3.18.18-config/aufs-3.18.14.patch

[32 bit]
# cp ../v3.18.18-config/32bit-v3.18.18-config .config

[64 bit]
# cp ../v3.18.18-config/64bit-v3.18.18-config .config
---------------------------------------

3. reconfigure (to your WiFi device)
---------------------------------------
# make menuconfig
---------------------------------------

4. rebuild kernel
---------------------------------------
# make
# cp arch/x86/boot/bzImage ../vmlinuz
# make modules_install INSTALL_MOD_PATH=../
# make firmware_install INSTALL_MOD_PATH=../
# cd ../
---------------------------------------

5. change the kernel of 'upkernel' command
[32 bit]
---------------------------------------
# mloop /usr/share/upkernel/Kernel.v3.18.18-i486-1/porteus/base/000-kernel.xzm
# mkdir 000
# cp -a /mnt/loop/* 000/.
# uloop
# rm -fr 000/lib
# mv lib 000/.
# mksquashfs 000 000-kernel.xzm -b 256K -comp xz -Xbcj x86
# rm -fr 000
# cp 000-kernel.xzm /usr/share/upkernel/Kernel.v3.18.18-i486-1/porteus/base/.
# cp vmlinuz /usr/share/upkernel/Kernel.v3.18.18-i486-1/boot/syslinux/.
---------------------------------------

[64 bit]
---------------------------------------
# mloop /usr/share/upkernel/Kernel.v3.18.18-x86_64-1/porteus/base/000-kernel.xzm
# mkdir 000
# cp -a /mnt/loop/* 000/.
# uloop
# rm -fr 000/lib
# mv lib 000/.
# mksquashfs 000 000-kernel.xzm -b 256K -comp xz -Xbcj x86
# rm -fr 000
# cp 000-kernel.xzm /usr/share/upkernel/Kernel.v3.18.18-x86_64-1/porteus/base/.
# cp vmlinuz /usr/share/upkernel/Kernel.v3.18.18-x86_64-1/boot/syslinux/.
---------------------------------------


Thanks.

[Bogomips]

1. 'upkernel' command
upkernel-3.18.18-noarch-1.xzm (40 M)
http://www.mediafire.com/download/7w1uw ... arch-1.xzm
md5sum: ac8969b78e09203947740aba625240d0 upkernel-3.18.18-noarch-1.xzm

'upkernel-3.18.18-noarch-1.xzm' has the 'upkernel' command
that updates the kernel of Porteus v3.1 to the kernel v3.18.18.

usage: execute by root
upkernel "v3.1 Portesu ISO name with/without path"

result:
New ISO that kernel version is 3.18.18 is created in a current directory.
The name is 'UP."v3.1 Portesu ISO name without path"' .

example 1.
------------------------------------------------------
# upkernel ../abc/Porteus-XFCE-v3.1-i486.iso
# ls
UP.Porteus-XFCE-v3.1-i486.iso
------------------------------------------------------

Am I right in thinking that all I need to get from the UP iso are

• vmlinuz
• initrd.xz
• kernel.xzm ?

[neko]

@Bogomips
No, not enough.

vmlinuz
initrd.xz
kernel.xzm
kernel-v3.18.18-i486.sgn or kernel-v3.18.18-x86_64.sgn

You can see ones that are replaced.
-----------------------------------
[32 bit]
% cd /usr/share/upkernel/Kernel.v3.18.18-i486-1
% ls -R

[64 bit]
% cd /usr/share/upkernel/Kernel.v3.18.18-x86_64-1
% ls -R
-----------------------------------
note: 'cheatcodes.txt' is not essence.


Thanks.

[francois]

@neko:
Thanks for this strategy to upgrade the kernel. In the following thread the pros and cons as presented (especially in the second answer provided):
http://askubuntu.com/questions/303977/w ... -in-ubuntu

With your method is the old kernel kept somewhere ready to be used in case of problems with the new kernel?

[neko]

@francois wrote:
1. With your method is the old kernel kept somewhere ready to be used in case of problems with the new kernel?

Yes, it is kept in the original ISO.
The original ISO not be deleted.
----------------------------------------
# upkernel OriginalISO
# ls
OriginalISO
UP.OriginalISO
----------------------------------------


2. the pros and cons ...
I think so too.
Therefor I said by using emotional words 'taste' and 'feel'.


Thanks.

[Bogomips]

Trying out the Iso by booting from iso image file. Found tutorial and a topic. To be absolutely clear about it, the kernel parameter (cheatcode) has to be set like so: from=/<Top level directory>/[<Intervening directories>/]<upgraded iso name>.iso. For example:

Code: Select all

    guest@porteus:~$ cat /proc/cmdline
    quiet from=/tmp/iso/UPrmPor-KDE4-v3.1-i486.iso copy2ram ramsize=30% noauto timezone=Europe/London volume=80%

Not being able to discern any perceptible difference with the new kernel, remastered iso to existing setup. Got rid of firefox from base, replaced modules, optional and rootcopy directories. And the situation at startup changed:

Code: Select all

Before 3.18.18
guest@porteus:~$ df  -h .
Filesystem      Size  Used Avail Use% Mounted on
aufs            265M  9.7M  255M   4% /

After
guest@porteus:~$ df -h .
Filesystem      Size  Used Avail Use% Mounted on
aufs            265M  1.1M  264M   1% /

Running AF with copy2ram.

Suppose that having just 880MiB ram and cpu at 800MHz, differences become perceptible. KDE Settings routine is faster and PaleMoon starts up quicker. Also feel PM responses to be swifter.

Whilst in upgrade mode, C++ library could also be bumped up from .18 to .20. libstdc++6-gcc49-4.9.0+r211729-2.1.7.i586.rpm 32 bits running a few days now. Corresponding 64 bits libstdc++6-gcc49-4.9.0+r211729-2.1.7.x86_64.rpm

Code: Select all

guest@porteus:~$ ls -lh /usr/lib/libstdc++.so.6
lrwxrwxrwx 1 root root 19 Jul 16 15:02 /usr/lib/libstdc++.so.6 -> libstdc++.so.6.0.20*

[neko]

@Bogomips
Thank you for your report.

1. About 'initrd'
If there were something wrong about cheatcode,
please replace new 'initrd.xz' with original one.
The quality of original 'initrd.xz' is better than of new one.

If original 'initrd.xz' is used on this kernel v3.18.18,

boot
[32 bit]
with cheatcode 'sgnfile=kernel-v3.18.18-i486.sgn'
[64 bit]
with cheatcode 'sgnfile=kernel-v3.18.18-x86_64.sgn'

or
[32 bit]
replace ISO@/porteus/kernel-v3.18.18-i486.sgn with porteus-v3.1-i486.sgn .
[64 bit]
replace ISO@/porteus/kernel-v3.18.18-x86_64.sgn with porteus-v3.1-x86_64.sgn .

note)
The new 'initrd' has a new cheatcode 'retry' for unstable USB devices.


2. "df -h ." comparison on my environment
[before] kernel 3.17.4
---------------------------------------------------------
guest@porteus:~$ df -h .
Filesystem Size Used Avail Use% Mounted on
aufs 1.1G 852K 1.1G 1% /
---------------------------------------------------------

[after] kernel 3.18.18
---------------------------------------------------------
guest@porteus:~$ df -h .
Filesystem Size Used Avail Use% Mounted on
aufs 1.1G 868K 1.1G 1% /
---------------------------------------------------------


3. 'libstdc++.so.6'
I am using 'libstdc++.so.6' of 'cxxlibs-6.0.18-i486-1' package in original v3.1 '001-core.xzm'.
It is linked to 'libstdc++.so.6.0.18' .


Thanks.

[Bogomips]

Quantitative Evaluation

Times from Stopwatch

Code: Select all

3.17.0	PaleMoon startup with 4 tabs to Restore		40 secs
3.18.18							                          15 secs

3.17.0	KDE System Settings routine startup		15 secs
3.18.18							                       4 secs

Memory Usage
openoffice.org startup took up all swap space, leaving nothing over on 3.17.0
3.18.18

Code: Select all

guest@porteus:~$ free -m
             total       used       free     shared    buffers     cached
Mem:           880        789         90          0         31        250
-/+ buffers/cache:        507        373
Swap:          644        376        268

Leaves 268 MB of free swap space

A plausible conclusion could be that memory is more effectively used, meaning less swapping and could explain the drastic reduction in PaleMoon startup time. On 3.17.0 disk light glowed constantly, this could have been caused by excessive swapping.

So it seems clear that older less powerful systems like mine (800MiB RAM, 800MHz) will find the kernel upgrade of real benefit.

[Jack]

I'm running Porteus Mate 3.1 off of a USB thumb drive can I just copy "upkernel-3.18.18-noarch-1.xzm" but rename it to "000-kernel.xzm" to the thumb drive and replace the "000-kernel.xzm" that on the thumb drive? Hope it will work that way.

Jack

[Bogomips]

I'm running Porteus Mate 3.1 off of a USB thumb drive can I just copy "upkernel-3.18.18-noarch-1.xzm" but rename it to "000-kernel.xzm" to the thumb drive and replace the "000-kernel.xzm" that on the thumb drive? Hope it will work that way.

Jack

In a Terminal as root

1. activate upkernel-3.18.18-noarch-1.xzm
2. Change to folder where you already have Porteus Mate 3.1 iso: cd /Path to the Iso/
3. upkernel <Porteus Mate 3.1 iso>.iso
4. UP iso will be created in this folder
5. Use this as your new iso

[Jack]

I'm running Porteus Mate 3.1 off of a USB thumb drive can I just copy "upkernel-3.18.18-noarch-1.xzm" but rename it to "000-kernel.xzm" to the thumb drive and replace the "000-kernel.xzm" that on the thumb drive? Hope it will work that way.

Jack

In a Terminal as root

1. activate upkernel-3.18.18-noarch-1.xzm
2. Change to folder where you already have Porteus Mate 3.1 iso: cd /Path to the Iso/
3. upkernel <Porteus Mate 3.1 iso>.iso
4. UP iso will be created in this folder
5. Use this as your new iso

I don't have a iso on my thumb drive. I unpack the iso on a ext4 formated thumb drive. That how I use it