"Robert G. Brown" wrote:
>
> On Fri, 9 Apr 1999, Jonathan Glass wrote:
>
> > I'm very new to Linux, and as such am very cautious. My Director of IS
> > volunteered me to learn all about Linux, and to order a new Linux server. I
> > called Dell and ordered a Poweredge 2300 w/3 9.1 GB UltraLVD-2 SCSIs running in
> > Raid 5. We paid Dell to install linux (RH5.2, 2.0.36) and they managed to get
> > the autoraid controller working, as well as recognition of the 256MB of RAM.
> > This machines performs fairly well, despite having only 2 PII350's. Here is
> > the problem: Only one processor is enabled. I've called Dell, and they say no
> > support, and to call RH. Called them, no support either. So, I'm turning to
> > alternative resources: Anyone have any suggestions for where to find
> > documentation pertaining to compiling a Kernel, and/or, compiling a kernel
> > w/SMP support? Any help would be greatly appreciated.
>
> Simple enough. Go get a clean 2.0.36 kernel source (or go to red hat's
> website and get the full source for the kernel they installed).
> Uncomment SMP=1 in the Makefile. Read the README in the source
> directory (usually /usr/src/linux) and follow the instructions for a
> kernel build.
Note that if you have the CDs then the source is right there. The
kernel-2.0.36-3.i386.rpm is the binary kernel,
kernel-source-2.0.36-3.i386.rpm is the actual /usr/src/linux tree in
complete form (minus the /usr/src/linux/include directory which is in
the kernel-headers RPM). The kernel-2.0.36-3.src.rpm is what we
actually use to build all the other rpms from, and the source tree as it
stands after patching and copying around of config files, etc. is what's
located in the kernel-source rpm.
> It sounds like you may need a bit of help actually putting the kernel
> and modules that you build in the right places (unless Red Hat cleverly
> edited the Makefile so a make install does the Right Thing).
Not really an option. We keep things like modules in directories that
are named after the kernel RPM version number. That way we keep modules
from 2.0.36-0.7 in a different directory than the modules from
2.0.36-3. If we didn't do that, then we run into module version
problems and the like between the two 2.0.36 kernel rpms. Putting that
into the kernel Makefiles isn't possible since it would require rpm spec
file information for each build and that doesn't make sense when doing
hand builds. So, the rpm build process does the magic of putting files
where they go. When doing things manually, the various make commands
that try to install the kernel and run lilo won't work. The module
install make command works fine. The installkernel script is included
for installing the actual kernel.
> You should
> be able to get help from, say, a local linux user's group or a nearby
> University or from Red Hat. When you're done, rerun lilo and reboot.
>
> If all else fails you, I'd be happy enough to build a monolithic SMP
> kernel for you. I've got a small stack of Poweredge 2300's but no RAID
> support installed. I for one wish that Red Hat installed the kernel
> sources they used to build the distribution kernel they give you right
> there in /usr/src/linux, with the .config file and all intact and ready
> to run, by default. Not doing this, in fact, seems somewhat
> Microsoftish and very definitely increases the problems they encounter
> with users rather than decreases them, as rebuilding kernels is a
> common solution to problems but building them without the right sources
> and configuration handy makes it very difficult to duplicate.
I disagree. First, with the 2.2.x kernel sources your talking about
installing over 50+ MB of kernel source by default. Not only that, but
we are striving to provide a system where the average user should never
need to compile their own kernel. In that case they don't need/want
those sources installed by default. They are always available through
the kernel-source-.... rpm though, so it isn't like we aren't providing
them. That includes all patches pre-applied and the .config file
intact, just like you are asking for.
--
Doug Ledford <[EMAIL PROTECTED]>
Opinions expressed are my own, but
they should be everybody's.
-
Linux SMP list: FIRST see FAQ at http://www.irisa.fr/prive/mentre/smp-faq/
To Unsubscribe: send "unsubscribe linux-smp" to [EMAIL PROTECTED]
