![](https://seccdn.libravatar.org/avatar/1f76eeb33b5a366be0beb80fa632bbc5.jpg?s=120&d=mm&r=g)
Hi! Trying to kill the keyboard, hettar@teleport.com produced:
Well whats cool it that you can do make menuconfig as many times as you like and spend all day looking at it, learning and reading the help on each thing you can add to the kernel.
And there's xconfig, too :) But as a beginner you'd better start X as root (or log into xdm as root), cause else you'd have to tell the thing to use your xserver (export DISPLAY=localhost:0.0 as root) and tell the server to allow it (xhost + localhost as the user who started it).
Just try not to bloat your kernel with things you will never use nor need.
exactly. And always have a backup kernel that works.
things to note: SCSI should be compiled directly
... if you have SCSI disks and use them, especially if your / is on SCSI. If you are on (E)IDE and have a SCSI-CDROM or ZIP or something, leave it as modules. (remember, you need SCSI-Support, support for the type (i.e. Disk) and support for the Adapter, too.)
filesystems can be mounted mostly as modules too
but not ext2, cause you need that for your / (unless you have an UMSDOS system :-) so you can get the modules.
a.out binary support (you can do this a module too)
Does not hurt as a module.
ppp should be direct compiled too
Nope. Works perfectly as module.
Thing about todays Kernels is they are hightly moduleized (or can be) for sleek,quickness, and non bloat.
... so put everything you need not 990f the time as module, if you can (and are allowed, see ext2). -Wolfgang -- PGP 2 welcome: Mail me, subject "send PGP-key". If you've nothing at all to hide, you must be boring. Unsolicited Bulk E-Mails: *You* pay for ads you never wanted. Is our economy _so_ weak we have to tolerate SPAMMERS? I guess not. -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e