On Wed, 9 May 2001 12:14:59 +0200 (MEST), you wrote:
Agreed. For those of us who don't use SuSE default kernels, it would be very convenient though if SuSE would provide the sources for the newer kernels, with all (suse-specific etc) modules included. I think a large part of this
Hi. I've always had a question about vendor rpm kernel vs custom (non rpm) compiled kernel. After a fresh install of SuSE, the vendor kernel rpm is installed. Then I always download the latest kernel from ftp.kernel.org or equivalent mirror and built it by myself. It's the only way of being up to date and have a more or less optimized kernel [disable non used options, choose the appropiate processor type, ...] (in my opinion). Now let's suppose than I want to use a script to update automatically packages: basically it should keep an eye on ftp.suse.com/......./updates, comparing version numbers with the currently installed packages and install those that are newer (and old versions were found to be installed on system). If I set up conf like this, when a new kernel package arises the script tries to update the kernel and in some cases when this is done, lilo conf is altered and my custom kernel is not used. The machine could not to reboot indeed (rpm/tarballs mixture is not very good.. :-)). I think the right solution is not to compile and build the recent kernel but build the RPM package and then install the built package. But this is tedious and not trivial, I think. Is there any other way of solve this "tarball vs rpm" troubles? Things like dependencies are added problems... (rpm thinks you have an old kernel installed although you have the last one compiled from tarball). Greetz. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= ** RoMaN SoFt / LLFB ** roman@madrid.com http://pagina.de/romansoft ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~