You are not logged in.
Pages: 1
Okay - it's been a good long time since I compiled my own kernels (as evident by my previous thread I suppose..) but when I did it was on Slackware, Gentoo and Crux so things might've changed.
All I did was copy the image from the src directory to /boot, install the very few modules I needed and then edit grub.
Now, reading over the Arch Wiki it recommends I make a ramdisk. Why is this? I always compile in almost everything since I'm only compiling the kernel for myself the size doesn't really matter.
Perhaps I'm missing something in this.
Favorite Software:
Openbox3 - Mutt - Vim - GNU Screen
Offline
If your compiling your own kernel which doesnt need to be portable then you can just compile the relevant bits into your hardware and not use a ramdisk. Though I would use makepkg and pacman to install/build the kernel image.
Offline
Absolutely. Using pacman to package the kernel seems to make it much easier to manage the nvidia driver and other firmware files.
Also, I love your avatar. I'm a big In Flames and Anders fan.
Favorite Software:
Openbox3 - Mutt - Vim - GNU Screen
Offline
After reviewing the package lists and what is required for boot, is it possible to remove the klibc cruft if one is not using the ARCH compiled kernel or a ramdisk?
Favorite Software:
Openbox3 - Mutt - Vim - GNU Screen
Offline
Pages: 1