Jim Kannengieser wrote:
> 
> I've heard a lot on the list about compiling special kernals. For instance,
> the current thread about netatalk mentions that GENERICSBC#48 needs to be
> compiled with that feature enabled. Well, my questions are just how does
> one go about compiling a new kernal, and under what circumstances is doing
> so usually necessary?

There should be some pretty straightforward instructions on compiling your
very own kernel on puma:

http://www.macbsd.com/macbsd/howto/

should be the URL.  There's a document there called the kernel-HOWTO, I
think.  If it happens to have disappeared, let me know and I'll generate a
new copy.

As for why it's necessary to compile a custom kernel, it's pretty rare
that it's necessary, but it's almost always useful.  This should also be
explained in the HOWTO, but basically, you can create a much leaner and
meaner kernel if you cut out all the unnecessary device support, turn off
unneeded options, and nail down your configuration.  The GENERIC kernels
are built in such a way that they should handle every Mac made (well, all
the ones we support ;-).  You usually don't need that much stuff, so you
can usually get rid of a large portion of it, resulting in a slight
speedup and decrease in memory usage.

I hope this explains things some.

Later.

-- 
Colin Wood                                 cwood@ichips.intel.com
Component Design Engineer - MD6                 Intel Corporation
-----------------------------------------------------------------
I speak only on my own behalf, not for my employer.