Hi Paul,

This is exactly what you are "supposed" to do, comment out all the hardware
you don't have and aren't using and then build the smallest possible kernel
(which maximizes memory availability).

For the CPU it helps to know the model VAX you are using. However, if it
says KA41/42 when you boot then the VAX410 is the correct CPU choice. (if
you want to see the source look in /usr/src/sys/arch/vax/vax/*cpu.c) 

Once you have your new config file, type 'config XXX' (where XXX is the
name you used) and then cd to ../compile/XXX and type 'make depend ; make '
and you're off to the races.

A couple of bits of advice:
	1) ALWAYS leave a working copy of the generic kernel on your root disk so
	   that you have something to boot to when your new kernel fails.
	2) You probably want a 20 - 30MB root partition if you are going to
	   be playing around with kernels.
	3) Build your kernels as a user other than root.

--Chuck

At 10:18 PM 8/1/99 -0400, paul yaskowski wrote:
>hello again,
>
>  i'm pathetically attempting to compile a kernel right now, and i'm
>wondering if there is a howto, or even a single page with some pointers
>on it.
>
>  my main question is, besides what is half of that stuff ;>, can i
>comment out hardware that i know that i do not have?  for instance,
>network cards:
>
># Ethernet cards
>#de0            at uba? csr 0174510     # DELUA/DEUNA
>#qe0            at uba? csr 0174440     # DEQNA/DELQA
>ln0             at vsbus0 csr 0x200e0000# LANCE
>
>  is that ok to comment out?  i know the network card is ln0.  and, for
>the cpu type, can i comment out everything except what i think my cpu
>is?
>
>options         "VAX410"        # VS 2000
>
>  i used that line, since when the generic kernel boots, i see this:
>
>cpu0 at mainbus0: KA41/42
>
>  both those numbers had a 41 in them, so i decided to go for it. ;)
>even better than a few pointers would be a vaxstation3100/m30 user's
>config.  thanks in advance.
>
>-- 
> paul yaskowski [a paradigm of a paramount failure]