The only problem that I see with this (maybe buildkernel solves this, which is what I want to find out) is pathces made to the kernel. Mandkake ships with a kernel patched, patched, patched, ............ compiled to support a lot of features only available on the 2.3.x and 2.4.0 text official sources by backporting. Does buildkernel take patching into account in any way. For example, mandrake supports the ov511 webcam chip on the Creative Webcam III. The page for this driver only lists patches aviable for 2.3.x, no 2.2.x !! The only machines I have that I would build kernels for are the ones with new hardware, thus needing patches (ide patch for example) until 2.4.0 comes out. Praedor Tempus wrote: > > mrweb wrote: > > > > Praedor Tempus wrote: > > > > > > I would like to strongly advocate dispensing with doing > > > an rpm install of kernels and, instead, download the > > > buildkernel rpm and use that. It is a wonderful app that > > > makes building your own kernel painless and simple. > [...] > > > > praedor, > > > > Thanks, for all that 'good stuff', I am excited to get the buildkernel > > app and put it to good use! Your description is so good I feel as if I > > already have a > > familiarity with buildkernel, thanks again. > > A few more things... > > I have had several kernels I have built via buildkernel on my system, > each with different settings/features. I can test them each out and > then make a determination which one I want to keep, deleting the > rest (all entries in /boot that refer to the kernel I am removing, > including > any symlinks that point to the kernel I am removing). > > I always keep an rpm-installed kernel and all it's stuff in /boot as > well (usually the kernel that was installed during my initial system > install - right now that is kernel-2.2.14 from Mandrake 7.0). Don't > remove anything having to do with the rpm kernel, doing so tends to > screw up your system even though you have a new, home-built kernel > installed and running. You can get around this but it does require > a bit of homework and knowledge on your part. > > Anyway, one thing to keep in mind after you have a kernel built and > installed via buildkernel: it is not an rpm install so nothing about > it shows up in your rpm database. What this means is that whenever > you download an app that has dependencies like "kernel-headers" or > "kernel-source", YOU CAN IGNORE THIS and just install it anyway using > the --nodeps switch. The headers and source exist, from your > buildkernel > build, but they do not show up in your rpm database. > > This doesn't hurt anything, it is simply something to keep in mind > when installing future rpms. They will work anyway, despite the > dependency, because everything that rpm needs from the kernel is > there. Just don't be upset, shocked, or dismayed that some rpm > says it needs kernel-headers, kernel-source, etc. Ignore it and > do not install the kernel-headers or kernel-source rpms after the > fact. You will be overwriting the same stuff that buildkernel and > the kernel source bzip or gzip file deposited on your system (in > the correct locations too) for no good reason. You may also dick > up your new kernel, though of this I am not certain. I have never > done it, nor considered it. > > praedor > > ------------------------------------------------------------------------ > Keep in touch with http://mandrakeforum.com: > Subscribe the "[EMAIL PROTECTED]" mailing list. -- |--------------------------------------------------------------| Buchan Milne Mechanical Engineer, Network Manager Cellphone +27824722231 email mailto:[EMAIL PROTECTED] Centre for Automotive Engineering http://www.sun.ac.za/cae South Africas first satellite: http://sunsat.ee.sun.ac.za Control Models http://www.control.co.za |----------------Registered Linux User #182071-----------------|
Keep in touch with http://mandrakeforum.com: Subscribe the "[EMAIL PROTECTED]" mailing list.
