It is my intention to document here how I got killX installed and configured.
This document is best read with emacs and org-mode installed.
Why killX?
Well, it is really slackware64 thrown on the BBQ by our excellent
grillmeister machinebacon.
Now I am using linux for a long long time, but I had never before
installed any slackware version, so it is totally new to me, which
means I may be using for instance package install tools that are not
the most appropriate for the situation. If that is so, dear
reader, do not hesitate to let me know. Learning all there is to know
about venerable slackware is one of the reasons I am starting this
write-up.
Let me tell you up front that I am already very fond of it. It does
not come with the newest and shiniest in linux land, but it seems to
me like it is an excellent system to learn everything you always
wanted to know about installing and configuring a linux system from
the command line.
Since all we have to start with is an archive, we will have to do the
install from a working linux system.
Here are some details on the system I will be installing from and to:
Now I am peculiar about the disk usage on this system. I use Logical
Volume Manager (LVM) to manage all my Hard Disk disk space, and I do
not want to change that for any reason in the world, unless someone
can convince me that it is bad, bad, bad...
So we impose ourselves an additional hurdle. KillX has to go to a
Logical Volume (LV).
I am using a pretty standard Debian Jessie system to do the install
from.
** Preparations on the jessie system
*** create a new logical volume
Setting up the Physical Volumes is outside the scope of this report.
el_koraco has an excellent tutorial on it over at the #! forum.
Creating the logical volume:
Creating a 20GB logical volume here because I am not short on space.
If you are followingd this just for testing, 6GB is probably more
than enough.
BTW: I use _ as an alias for 'sudo'. It is the command I use more
than any other command, so a one-character alias is handy. You get
used to it.
Code: Select all
_ lvm
lvm> lvcreate -L 20G -n killX-nietzsche /dev/mapper/VG10
Logical volume "killX-nietzsche" created
lvm> lvs
LV VG Attr LSize Pool Origin Data% Move Log Copy% Convert
VG10-waldorf VG10 -wi-a---- 20.00g
arch VG10 -wi-a---- 40.00g
jessy VG10 -wi-ao--- 10.00g
killX-nietzsche VG10 -wi-a---- 20.00g
linuxBBQ-rice VG10 -wi-a---- 20.00g
linuxBBQ-yuebing VG10 -wi-a---- 20.00g
livarp VG10 -wi-a---- 10.00g
vsido VG10 -wi-a---- 24.00g
waldorf-fresh-install VG10 -wi-a---- 30.00g
lvm>
Code: Select all
_ mkfs.ext4 /dev/mapper/VG10-killX--nietzsche
create a temporary directory to store everything related to killx and
cd to that directory. Then run
Code: Select all
wget http://iso.killx.org/killX-nietzsche-64.tar.bz2
_ mkdir -p /mnt/killx
_ mount /dev/mapper/VG10-killX--nietzsche /mnt/killx
_ tar xf killX-nietzsche-64.tar.bz2 -C /mnt/killx/
_ umount /mnt/killx
*** run update-grub
Code: Select all
_ update-grub
Verify that there is a stanza for booting into killX> _ update-grub
Generating grub.cfg ...
Found background image: /usr/share/images/desktop-base/desktop-grub.png
Found linux image: /boot/vmlinuz-3.10-2-amd64
Found initrd image: /boot/initrd.img-3.10-2-amd64
Found linux image: /boot/vmlinuz-3.9-1-amd64
Found initrd image: /boot/initrd.img-3.9-1-amd64
Found Windows 7 (loader) on /dev/sda2
Found Slackware Linux (Slackware 14.0) on /dev/sdb3
Found Debian GNU/Linux (jessie/sid) on /dev/mapper/VG10-VG10--waldorf
Found Arch on /dev/mapper/VG10-arch
Found killX 0.1 R1 (Wagner) (killX 0.1 R1) on /dev/mapper/VG10-killX--nietzsche
Found LinuxBBQ Rice 64 (3.3) on /dev/mapper/VG10-linuxBBQ--rice
Found LinuxBBQ Yuebing (3.5) on /dev/mapper/VG10-linuxBBQ--yuebing
Found Debian GNU/Linux (7.1) on /dev/mapper/VG10-livarp
Found VSIDO 1_2 (1_2) on /dev/mapper/VG10-vsido
Found Debian GNU/Linux (7.1) on /dev/mapper/VG10-waldorf--fresh--install
done
Code: Select all
_ grep -EA8 '^menuentry "killX' /boot/grub/grub.cfg
You can use the output of> _ grep -EA8 '^menuentry "killX' /boot/grub/grub.cfg
menuentry "killX 0.1 R1 (Wagner) (killX 0.1 R1) (on /dev/mapper/VG10-killX--nietzsche)" --class gnu-linux --class gnu --class os {
insmod lvm
insmod part_msdos
insmod ext2
set root='(VG10-killX-nietzsche)'
search --no-floppy --fs-uuid --set=root b14b6e29-6398-4e11-a629-1cde281b8d5f
linux /vmlinuz root=/dev/dm-10
initrd /initrd.img
}
menuentry "killX 0.1 R1 (Wagner) (killX 0.1 R1) (on /dev/mapper/VG10-killX--nietzsche)" --class gnu-linux --class gnu --class os {
insmod lvm
insmod part_msdos
insmod ext2
set root='(VG10-killX-nietzsche)'
search --no-floppy --fs-uuid --set=root b14b6e29-6398-4e11-a629-1cde281b8d5f
linux /vmlinuz root=/dev/dm-10
initrd /initrd.img
}
menuentry "killX 0.1 R1 (Wagner) (killX 0.1 R1) (on /dev/mapper/VG10-killX--nietzsche)" --class gnu-linux --class gnu --class os {
insmod lvm
insmod part_msdos
insmod ext2
set root='(VG10-killX-nietzsche)'
search --no-floppy --fs-uuid --set=root b14b6e29-6398-4e11-a629-1cde281b8d5f
linux /boot/vmlinuz-huge-3.10.9 root=/dev/dm-10
}
menuentry "killX 0.1 R1 (Wagner) (killX 0.1 R1) (on /dev/mapper/VG10-killX--nietzsche)" --class gnu-linux --class gnu --class os {
insmod lvm
insmod part_msdos
insmod ext2
set root='(VG10-killX-nietzsche)'
search --no-floppy --fs-uuid --set=root b14b6e29-6398-4e11-a629-1cde281b8d5f
linux /vmlinuz root=/dev/dm-10
initrd /initrd.img
}
menuentry "killX 0.1 R1 (Wagner) (killX 0.1 R1) (on /dev/mapper/VG10-killX--nietzsche)" --class gnu-linux --class gnu --class os {
insmod lvm
insmod part_msdos
insmod ext2
set root='(VG10-killX-nietzsche)'
search --no-floppy --fs-uuid --set=root b14b6e29-6398-4e11-a629-1cde281b8d5f
linux /vmlinuz root=/dev/dm-10
initrd /initrd.img
}
Code: Select all
_ blkid
Try to boot into any of these grub2 entries. They will all fail with
either a kernel panic or by spitting out some errors, dropping you into
a shell and telling you that you can solve it from there. Press
Control-D when you are done.
Is that so?
More...