Hi, Mary
I didn't answer your earlier posts because I am expert neither in SMP nor in
Red Hat. So you'll need to get answers to the RH-specific parts of your
questions elsewhere. I would mention that the current RH is 6.2, the current
kernel 2.2.15 (the 2.2.15-pre series *just* ended). For both performance and
security reasons, you might want to consider stepping up to te newer version.
You wrote:
>But how do i extend the version number?
At the top of the Makefile are variables like the following:
VERSION = 2
PATCHLEVEL = 2
SUBLEVEL = 13
EXTRAVERSION =
To distinguish local kernels, you put a value in EXTRAVERSION .
>Is it by
>selecting "set version info on all symbols..." during make config? if it is,
>i think i enabled it (but then i must have missed it).
No. This is *supposed* to make the kernel insensitive to module mismatches.
I don't find it reliable. In any case, you are getting the mismatch (as I
understand it) with your stock kernel, not your custom kernel, and that one
probably did not have this option set.
>1. is there a way i can make smp support during a fresh install of redhat
>6.1?
>2. if not, i see an image with an smp extension under /boot.. is this
>something i can readily use to have smp support?
I don't know, specifically. See if /boot contains a file called "config" or
something similar. If it does, copy it over to /usr/src/linux, and start
from it when you do a "make config" (I'm not just sure how; I use "make
menuconfig", which provides an interface I like better, and makes loading a
configuration very wasy). Then just change the SMP setting (under "processor
type and features") and you should be set.
>i compiled a new kernel with SMP support as described in the
>smp-howto, which said i'll have to do "make modules; make modules_install".
The author may have been careless in omitting this instruction, taken from
/usr/src/linux/README
"Keep a backup kernel handy in case something goes wrong. This is
especially true for the development releases, since each new release
contains new code which has not been debugged. Make sure you keep a
backup of the modules corresponding to that kernel, as well. If you
are installing a new kernel with the same version number as your
working kernel, make a backup of your modules directory before you
do a "make modules_install"."
At 11:17 PM 6/3/00 +0800, Mary Christie Generalao wrote:
[relevant portions excerpted above; rest deleted]
>
>Thanks a lot. Really im starting to feel the difficulties of administering
>remote machines (with no tech support onsite).
Yeah, I bet. Tough problem. Requires some careful, specialized setup work at
install time to make this approach workable.
------------------------------------"Never tell me the odds!"---
Ray Olszewski -- Han Solo
Palo Alto, CA [EMAIL PROTECTED]
----------------------------------------------------------------
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.linux-learn.org/faqs
