"Okay, here's my plan. Over the next few installments in
this series, we're going to visit another one of those topics that
nobody seems to want to talk about (like printing - well, can you
blame them?). Back a million years ago when I first started working
with UNIX systems, we always had to compile our own kernels (as in
the early days of Linux). We did this because every system was
different in terms of hardware, drivers, number of users, etc., and
all these parameters had to be taken into consideration before you
ever booted your system. Otherwise, the 20th person would log in
and the system would go down in flames. Resource and capacity
planning as well as performance tuning were low-level issues that
had to be considered. Not so much with today's systems. For the
most part, when someone asks me when they should rebuild their
kernels, I answer this way.
"Unless you have to, that is. No, this series is not about
rebuilding your kernel. It's about not rebuilding your kernel. It's
also about not rebooting."
Some of the products that appear on this site are from companies from which QuinStreet receives compensation. This compensation may impact how and where products appear on this site including, for example, the order in which they appear. QuinStreet does not include all companies or all types of products available in the marketplace.