Is it a compulsary to update our system ? core ? backend ? The answer is yes! Let's say we just install a new operating system in our box. After installation process, everything went fine, you can browse and surf the internet, wifi work like a charm, mouse functioning and what in the world we should update ? Well, this is to ensure the driver and some of the code that we use are correct, free error, and free bugs that may counter some flaw to your system. Worst come to worst.. it may give attacker a point to own your box or some execution code that may put your system down. So, what can we do in Arch ? simple..
we have pacman :-) pacman can do it.. and we all trust in pacman :-P
bash# pacman -Syu
S - Synchronize
y - Install
u - Upgrade
Things that you have to consider :
First and for most, updating or upgrading the system is kind of you change the system and all the dependencies that may depends on something that can cause a failure to your system and application. I got an experience after upgrading my system with pacman, some how it won't reboot. After do some research, some of Arch user face this kind of problem.
You will get error after rebooting when finished upgrading process from Mr.Pacman
Kinit: init not found!
Kernel Panic - Not Synching: Attempted to kill init!
I try my best to troubleshoot this kind of kernel panic.. it just like a nightmare to me when my box won't bootup anymore :-(
I have knoppix dvd, which I got from the linux magazine. It's called "Linux For You" from India. As we all know knoppix is one of in the market for rescue your system and it's quite famous in the past. But somehow I'm not using Knoppix because something I can't do with knoppix :), so if you have Arch Linux cd you also can do that as rescue cd to repair your system. When finish bootup the cd, login as root and what I have in my fstab is something like this :
/dev/sda
/dev/sda1 ( boot )
/dev/sda2 ( swap )
/dev/sda3 ( root )
/dev/sda4 ( home )
Open the terminal and as root :
root# mkdir /mnt/sda1
root# mount -o rw /dev/sda1 /mnt/sda1
This will enable read/write option to the partition. The default type is read only file system. Once done we cd to the mounted partition and investigation start :
root# cd /mnt/sda1
root# cd grub
root# nano menu.lst
Weird, the root path is different and not in an order, example for the fallback menu, because the real one I already change and fixed :
# (1) Arch Linux
title Arch Linux Fallback
root (hd0,0)
kernel /vmlinuz26 root=/dev/disk/by-uuid/c9f9ab15-576a-4195-af42-89e56d598a29 ro
initrd /kernel26-fallback.img
I googling and digging in Arch forum and found out we have to fix it manually and the solutions is :
- mount root partition
- use mkinitcpio -p kernel26
Now the root partition is in sda3, mount it first
root# mkdir /mnt/sda3
root# mount -o rw /dev/sda3 /mnt/sda3
root# chroot /mnt/sda3
chroot is an operation that changes the apparent disk root directory for the current running process and its children. This make you are working in the Arch partition :-)
root# mkinitcpio -p kernel26
let they do their job and at the end it will create 2 file :
- kernel26-fallback.img
- kernel26.img
And I have to copied the vmlinuz26 from the boot partition to root partition which make life more easier
root# cp /mnt/sda1/vmlinuz26 /mnt/sda3/boot/
Last ly, we have to edit the menu.lst from boot partition to match with our new setting :
# (0) Arch Linux
title Arch Linux
root (hd0,2)
kernel /boot/vmlinuz26 root=/dev/sda3 ro
initrd /boot/kernel26.img
(hd0,2) - Hard disk 0 with partition no 2, 0 is 1st ( which is the root, sda3 )
kernel /boot/vmlinuz26 root=/dev/sda3 ro - Partition no 2 in /boot folder that consist of vmlinuz26
After finish editing, unmounted the partition
root# umount /mnt/sda1
root# umount /mnt/sda3
Reboot, and try to boot the Arch
|
Contributor's Note
Arch Forum & my experience
|
