Re: Update the kernel of Porteus v3.1
Posted: 07 Nov 2015, 04:48
Hello neko. You have nothing to say about the future of porteus?
http://forum.porteus.org/viewtopic.php?f=53&t=5187
http://forum.porteus.org/viewtopic.php?f=53&t=5187
1.Is it possible to build linux-4.2.3 with the kernel headers that come with?A simple question here. Is it possible to build linux-4.2.3 with the kernel headers that come with? And then could I use these kernel headers with another distribution with the same kernel version?
Code: Select all
% su
# /usr/share/live-usb/bin/live-usb
Code: Select all
guest@porteus:~$ md5sum upkernel-4.2.6-noarch-1.xzm
5fe60909cb29070cd434183d0fa3c45c upkernel-4.2.6-noarch-1.xzm
5fe60909cb29070cd434183d0fa3c45c upkernel-4.2.6-noarch-1.xzm
root@porteus:/home/guest/p10/tmp/iso_tmp# upkernel4 Por-KDE4-v3.1-4.2.5-i486.iso
mount: block device /home/guest/p10/tmp/iso_tmp/Por-KDE4-v3.1-4.2.5-i486.iso is write-protected, mounting read-only
Setting input-charset to 'UTF-8' from locale.
3.01a16 (i686-pc-linux-gnu)
Scanning UP.Por-KDE4-v3.1-4.2.5-i486
...
Max brk space used 44000
150159 extents written (293 MB)
Code: Select all
guest@porteus:~$ ls -lh p10/tmp/iso_tmp/UP.*.iso
-rw-r--r-- 1 root root 294M Nov 13 19:30 p10/tmp/iso_tmp/UP.Por-KDE4-v3.1-4.2.5-i486.iso
ln p10/tmp/iso_tmp/UP.Por-KDE4-v3.1-4.2.5-i486.iso p10/tmp/iso/Por-KDE4-v3.1-4.2.6-i486.iso
Code: Select all
sudo mount p10/tmp/iso/Por-KDE4-v3.1-4.2.6-i486.iso z -t iso9660 -o loop
cp -a z/boot/syslinux/vmlinuz /mnt/sda1/por/up3.1/k4.2.6
cp -a z/boot/syslinux/initrd.xz /mnt/sda1/por/up3.1/k4.2.6
ls -lh /mnt/sda1/por/up3.1/k4.2.6
total 4.2M
-rw-r--r-- 1 guest guest 1.6M Oct 28 15:51 initrd.xz
-rw-r--r-- 1 guest guest 2.6M Oct 28 04:27 vmlinuz
Code: Select all
guest@porteus:~$ ls -i p10/tmp/iso_tmp/UP.Por-KDE4-v3.1-4.2.5-i486.iso
2941700 p10/tmp/iso_tmp/UP.Por-KDE4-v3.1-4.2.5-i486.iso
guest@porteus:~$ ls -i p10/tmp/iso/Por-KDE4-v3.1-4.2.6-i486.iso
2941700 p10/tmp/iso/Por-KDE4-v3.1-4.2.6-i486.iso
guest@porteus:~$ ls -lh /mnt/sda1/por/up3.1/k4.2.{5,6}
/mnt/sda1/por/up3.1/k4.2.5:
total 4.2M
-rw-r--r-- 1 guest guest 1.6M Oct 28 15:51 initrd.xz
-rw-r--r-- 1 guest guest 2.6M Oct 28 04:27 vmlinuz
/mnt/sda1/por/up3.1/k4.2.6:
total 4.2M
-rw-r--r-- 1 guest guest 1.6M Oct 28 15:51 initrd.xz
-rw-r--r-- 1 guest guest 2.6M Oct 28 04:27 vmlinuz
Because I'm thinking for 4.2.6 need to runDESCRIPTION
upkernel4/upakernel4 is the tool of Updating the Kernel of Porteus ISO.
upkernel4/upakernel4 must be executed by root.
Code: Select all
upkernel4/upakernel4 Por-KDE4-v3.1-4.2.5-i486.iso
DESCRIPTION
upkernel4 & upakernel4 are the tool of Updating the Kernel of Porteus ISO.
upkernel4 & upakernel4 must be executed by root.
Code: Select all
root@porteus:/home/guest/p10/tmp/iso_tmp# ls
FVWM_ja-kernel.v4.2.5-i486-1.iso upkernel-4.2.6-noarch-1.xzm
root@porteus:/home/guest/p10/tmp/iso_tmp# md5sum upkernel-4.2.6-noarch-1.xzm
5fe60909cb29070cd434183d0fa3c45c upkernel-4.2.6-noarch-1.xzm
root@porteus:/home/guest/p10/tmp/iso_tmp# mv FVWM_ja-kernel.v4.2.5-i486-1.iso Por-KDE4-v3.1-4.2.5-i486.iso
root@porteus:/home/guest/p10/tmp/iso_tmp# activate upkernel-4.2.6-noarch-1.xzm
Updating shared library links: /sbin/ldconfig
root@porteus:/home/guest/p10/tmp/iso_tmp# upkernel4 Por-KDE4-v3.1-4.2.5-i486.iso
mount: block device /mnt/sda3/live/porteus/persist/home/guest/p10/tmp/iso_tmp/Por-KDE4-v3.1-4.2.5-i486.iso is write-protected, mounting read-only
3.01a16 (i686-pc-linux-gnu)
Scanning UP.Por-KDE4-v3.1-4.2.5-i486
...
Max brk space used 1d000
99588 extents written (194 MB)
Code: Select all
guest@porteus:~$ ls -lh p10/tmp/iso_tmp/UP.*.iso
-rw-r--r-- 1 root root 195M Nov 15 10:37 p10/tmp/iso_tmp/UP.Por-KDE4-v3.1-4.2.5-i486.iso
guest@porteus:~$ ln p10/tmp/iso_tmp/UP.Por-KDE4-v3.1-4.2.5-i486.iso p10/tmp/iso/Por-KDE4-v3.1-4.2.6-i486.iso
ln: failed to create hard link 'p10/tmp/iso/Por-KDE4-v3.1-4.2.6-i486.iso' => 'p10/tmp/iso_tmp/UP.Por-KDE4-v3.1-4.2.5-i486.iso': No such file or directory
guest@porteus:~$ mkdir -p p10/tmp/iso/
guest@porteus:~$ ln p10/tmp/iso_tmp/UP.Por-KDE4-v3.1-4.2.5-i486.iso p10/tmp/iso/Por-KDE4-v3.1-4.2.6-i486.iso
guest@porteus:~$ mkdir z
guest@porteus:~$ sudo mount p10/tmp/iso/Por-KDE4-v3.1-4.2.6-i486.iso z -t iso9660 -o loop
Password:
mount: block device /mnt/sda3/live/porteus/persist/home/guest/p10/tmp/iso/Por-KDE4-v3.1-4.2.6-i486.iso is write-protected, mounting read-only
guest@porteus:~$ mkdir -p /mnt/sda13/porteus/up3.1/k4.2.6
guest@porteus:~$ cp -a z/boot/syslinux/vmlinuz /mnt/sda13/porteus/up3.1/k4.2.6
guest@porteus:~$ cp -a z/boot/syslinux/initrd.xz /mnt/sda13/porteus/up3.1/k4.2.6
guest@porteus:~$ ls -lh /mnt/sda13/porteus/up3.1/k4.2.6
total 4.2M
-rw-r--r-- 1 guest guest 1.6M Nov 11 16:49 initrd.xz
-rw-r--r-- 1 guest guest 2.6M Nov 11 16:41 vmlinuz
guest@porteus:~$ mkdir -p /mnt/sda13/porteus/up3.1/k4.2.5
guest@porteus:~$ sudo umount z
Password:
guest@porteus:~$ sudo mount p10/tmp/iso_tmp/Por-KDE4-v3.1-4.2.5-i486.iso z -t iso9660 -o loop
mount: block device /mnt/sda3/live/porteus/persist/home/guest/p10/tmp/iso_tmp/Por-KDE4-v3.1-4.2.5-i486.iso is write-protected, mounting read-only
guest@porteus:~$ cp -a z/boot/syslinux/vmlinuz /mnt/sda13/porteus/up3.1/k4.2.5
guest@porteus:~$ cp -a z/boot/syslinux/initrd.xz /mnt/sda13/porteus/up3.1/k4.2.5
guest@porteus:~$ ls -lh /mnt/sda13/porteus/up3.1/k4.2.{5,6}
/mnt/sda13/porteus/up3.1/k4.2.5:
total 4.2M
-rw-r--r-- 1 guest guest 1.6M Oct 28 14:51 initrd.xz
-rw-r--r-- 1 guest guest 2.6M Oct 28 03:27 vmlinuz
/mnt/sda13/porteus/up3.1/k4.2.6:
total 4.2M
-rw-r--r-- 1 guest guest 1.6M Nov 11 16:49 initrd.xz
-rw-r--r-- 1 guest guest 2.6M Nov 11 16:41 vmlinuz
guest@porteus:~$ md5sum /mnt/sda13/porteus/up3.1/k4.2.5/*
92491bffaff77934080e8194c9cc7363 /mnt/sda13/porteus/up3.1/k4.2.5/initrd.xz
547a504a8da635af0b63e1d1413a18e3 /mnt/sda13/porteus/up3.1/k4.2.5/vmlinuz
guest@porteus:~$ md5sum /mnt/sda13/porteus/up3.1/k4.2.6/*
0087edd3d4561580ad54579b33e30dc9 /mnt/sda13/porteus/up3.1/k4.2.6/initrd.xz
cfecb7913394543a6e7f270fb545e050 /mnt/sda13/porteus/up3.1/k4.2.6/vmlinuz
Code: Select all
root@porteus:/home/guest/p10/tmp/iso_tmp# which upkernel4
/usr/local/sbin/upkernel4
root@porteus:/home/guest/p10/tmp/iso_tmp# ls -l /usr/local/sbin/upkernel4
lrwxrwxrwx 1 root root 36 Nov 11 16:50 /usr/local/sbin/upkernel4 -> ../share/upkernel/bin/upkernel.4.2.6*
Code: Select all
guest@porteus:~$ sudo mount p10/tmp/iso_tmp/UP.Por-KDE4-v3.1-4.2.5-i486.iso z -t iso9660 -o loop
mount: block device /home/guest/p10/tmp/iso_tmp/UP.Por-KDE4-v3.1-4.2.5-i486.iso is write-protected, mounting read-only
guest@porteus:~$ ls -lh z/boot/syslinux/vmlinuz z/boot/syslinux/initrd.xz
-rw-r--r-- 1 root root 1.6M Nov 11 17:49 z/boot/syslinux/initrd.xz
-rw-r--r-- 1 root root 2.6M Nov 11 17:41 z/boot/syslinux/vmlinuz
guest@porteus:~$ md5sum z/boot/syslinux/vmlinuz z/boot/syslinux/initrd.xz
cfecb7913394543a6e7f270fb545e050 z/boot/syslinux/vmlinuz
0087edd3d4561580ad54579b33e30dc9 z/boot/syslinux/initrd.xz