--- B Higginbottom
Yes, you're right there. However, the point about stock kernels is that they are compiled with *everything* in them, so that they support all hardware types, etc, so that installation is not a problem on the older architectures.
Not any longer, yes just about everything is in there, but Suse does have different kernels for pentiums, athlons, celerons and so on. Non X86 based architectures usually have totally different requirements and so Suse have
I was generalising, and not limiting myself to talking about one specific distribution.
the iso's available for download; they lag far behind the X86 releases (Alpha, PPC and Sparc are at 7.3 I think). Anything below 586 then it wont install at all.
So SuSE are going the same way as Mandrake in that their default stock kernel won't support pre-intel architectures? Tut tut.
By compiling your own kernel, you customise it completely to your own computer's hardware, thus removing all the unnecessary components from the kernel, thus increasing the speed as well (less things to load, if they've been statically compiled in).
Yes, I pointed that out in my previous message, although with current processors and memory savings will be minimal other than at boot. For more performance savings you should also compile all your programs from source, editing the makefile (sensitive beasts at the best of times) for high optimisation and processor type. These things are fine for home systems, however to do these things in a production enviroment surrounded by critical services and the most important thing is for it to work, no matter how sub-optimal their function.
Yes, hence also embedded architectures.
No, not true. You compile your own kernel *after* installation.
Well I'm guessing your not familiar with the distros that do require you to configure and compile your own kernel during install. However as the problem
You assume wrong, however for all the *linux* distros that I have used, I have never had to configure multiple kernels in this way. I have only ever done this *post* installation.
was with a Suse system failing to update, we have to deal with the restrictions on installation support, which states, to paraphrase, that if you start messing with your own kernels, and especially with test kernels, your on your own.
Yes, but anyone who has the knowledge of compiling their own kernel ought not to worry about SuSE's support system.
I think you're missing the point. Assuming that one is using LILO (or GRUB), then this is not a problem because you can have multiple stanzas in say, /etc/lilo.conf, thus meaning that you DON'T need to mess around with the system.map file. Try it, I assure it is quite simple. How do you think developers test multiple kernels?
Yes, I'm well aware that you can and my GRUB config is filled with them, however if the original poster in a moment of insanity actually went ahead and rolled his own, he would have turned to one of the many 'helpful' articles and howto's on the subject. All of those that I've read advocate the complete replacement of both the kernel and the map without prior testing; leaving him up the proverbial creek without the equally proverbial paddle.
TMTOWTDI.
Done -- a discussion is now in progress.
He'll never forgive me :)
:) Oh, I think he will... -- Thomas Adam ===== Thomas Adam "The Linux Weekend Mechanic" -- www.linuxgazette.com ________________________________________________________________________ Want to chat instantly with your online friends? Get the FREE Yahoo! Messenger http://mail.messenger.yahoo.co.uk