-----Original Message-----
From: Stephen Liu <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date: Tuesday, August 15, 2000 8:50 AM
Subject: Tech Terms applied in Make Menuconfig
>
>Kindly assist me to understand the function of following terms found and
>applied in "make menuconfig"
>
>- What will be the major difference between selecting <*> /yes and <M>
>/module
If you select the */yes, that feature will be included in the compiled
kernel. If you select module for that feature, it will be compiled into a
loadable module. If the feature is in the kernel, it increases the size of
the kernel a bit, but can reduce headaches when you include those things you
will need to have at all times. For example, you probably want to have the
ext2 filesystem code in your kernel, since you will rarely not be using that
code anyway. If you put a feature in a module, it gets loaded whenever you
first use the feature and unloads after a short time of no usage. It tends
to reduce the size of your kernel and can make it a little easier to upgrade
certain features. An example here might be a module for your zip drive.
You wouldn't need to use that code all the time, so it would be reasonable
to not add it to the kernel.
>
>- Kernel hacking. What shall be its function
This is for playing with experimental features, or even for trying to stress
test kernel features. It's not something you would usually want to make use
of in a production machine.
>
>Under Console drivers
>- Support only 8 pixels wide fonts
>- Select compiled-in fonts
>
>What will be their function
>
I'm not as familiar with this one, but it looks like a choice between a few
fixed fonts for your text screen modes or a larger selection of fonts. I'd
take the defaults if I were you. Anyone else know a bit more here?
Hope this helped.
Jeff Hogg
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
