1 Feb
2010
1 Feb
'10
7:57 p.m.
Hi Paul,
On Mon, Feb 01, 2010 at 06:17:09PM +0000, Paul Tansom wrote:
** Andy Smith <andy(a)bitfolk.com> [2010-02-01
14:49]:
Yes, dpkg -i on both the above .debs should just install them.
Hello,
Maybe it is something in userland, but I would be interested to know
what happens if you switched to a kernel from Debian Lenny e.g.:
http://packages.debian.org/lenny/linux-image-2.6.26-2-xen-686
http://packages.debian.org/lenny/linux-modules-2.6.26-2-xen-686
or an upstream kernel.org.one.
** end quote [Andy Smith]
Is this just a case of downloading and installing with dpkg? Possibly using a
custom line in the apt sources to pick up updates as well (obviously avoiding
any other packages being pulled in!).
I think this is possible but haven't looked into how.
Just wondering whether updating the
kernel is a little more controlled than other packages,
Kernel updates in debian/ubuntu are just updated packages with the
package pre/post install scripts handling initrd, grub etc.
You could for example just subscribe to the Debian security mailing
list then you would know when a new kernel .deb was out.
but I may be used to my old UML setup and the even
more restricted
system I was on before (which one escapes me!) where the kernel
was updated as part of the VPS hosting platform.
Your previous emails suggest Bytemark's UML setup.
I could enforce usage of one kernel on everyone which would make it
my problem, but then that's a bit less flexible for everyone else.
I am still considering doing something a bit like slicehost where
you have to request a kernel upgrade and it happens during a
boot/shutdown (don't forget that modules need installing in the
filesystem).
Any pointers or suggestions as to ones to try, or good
references on compiling
Xen kernels? I can experiment a bit on my VPS to see whether it improves
things.
I have successfully compiled an upstream kernel.org kernel like
this:
1. Download kernel source from kernel.org, unpack, cd into it.
2. apt-get install build-essential fakeroot libncurses5-dev kernel-package
3. Obtain a .config from somewhere. You could try your existing
kernel's config that you might find somewhere in /boot/config*
then do "make oldconfig" to update it, though the difference
between something like 2.6.18 and 2.6.32 will be quite
long-winded. I've attached one that I have used successfully
with 2.6.32.7.
4. fakeroot make-kpkg --arch=i386 --revision=pauls-kernel.1 --initrd kernel_image
kernel_headers
The "pauls-kernel.1" part will appear in the package name but not
in the name of the kernel so if you made another kernel from the
same source it would overwrite this one. If you want to make
different packages that can co-exist, use --append-to-version=...
Avoid using "_" in these strings.
You should end up with linux-image and linux-headers .debs in the
directory above the current one.
5. Install the .debs, make sure you have an initrd created. If not
you can make one with e.g.
update-initramfs -v -k 2.6.32.7 -c
6. update-grub and check it appears correctly in the
/boot/grub/menu.lst. If using an upstream kernel then avoid
clocksource=jiffies in the kernel command line.
7. Go to xen shell, shut down, boot, select appropriate kernel, hope
it works. :)
Cheers,
Andy
--
http://bitfolk.com/ -- No-nonsense VPS hosting