Arch kernel on Linode, was Upgraded kmod, but --ignored linux & glibc, modules still in /lib - can I reboot safely?
-----BEGIN PGP SIGNED MESSAGE-----
On 07/15/12 18:09, C Anthony Risinger wrote:
> On Sun, Jul 15, 2012 at 4:14 PM, David Benfell
> <firstname.lastname@example.org> wrote:
>> I'd have to look into using a not-so-custom kernel (presumably
>> from the Arch package). Ten years ago, I used to build kernels
>> routinely. But it's not trivial anymore.
> nah none of that :-) i detest compiling things.
Whew! I mean it used to be fun. And I don't mind much when it's the
./configure-make-make install sequence. But kernel building never was
quite that simple and I'd have to say it's become a lot more
> i run the standard Arch kernel, same as any other machine -- you
> just have to configure your instance to use pv-grub.
> ... basically, you just need to make a grub-legacy menu.lst file,
> put it in the normal place on an ext3 partition, and go from there.
> no real work in the end.
I went to the Arch Wiki (or, more precisely, my copy of it, since the
original one often fails to answer), went to the Linode wiki (which
doesn't talk about Arch Linux), and came up with the following
(comments elided) /boot/grub/menu.1st:
color light-blue/black light-cyan/blue
title Arch Linux
kernel /vmlinuz-linux root=/dev/xvda ro
But I missed something because when I went to boot, it still thought
it was supposed to boot from (hd0,0).
> the arch kernel has all the necessary CONFIG_* bits to run
> unmodified in the Linode XEN environment.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/