On Fri, 9 Jun 2000, Tim Jones wrote:
> Kristine Rogers wrote:
> >
> > Wolfgang Weisselberg wrote:
> >
> > > Hi, Kristine!
> > >
> > > Trying to kill the keyboard, Kristine Rogers
> > > ([EMAIL PROTECTED]) produced 0,9K in 23 lines:
> > >
> > > > from a command-line. After that there were several complaints about
> > > > "/usr/src/linux/.configure" missing so I created a blank file by that
> > > > name.
> > >
> > > Actually, you are supposed to have the configuration of your
> > > current kernel in that file! ...
> >
> > If I'm using a "stock" RedHat 6.1 kernel (2.2.12-20), and the
> > /usr/src/linux/.config file does not appear to be installed, is there a to
> > create a copy from the currently-running kernel?
>
> Negative - you must have the kernel sources installed and AT least
> perform a 'make menuconfig' and save the kernel settings (.config) and
> ensure that the links to the appropriate headers are built.
Actually, for RedHat, they include the config files for the various
kernels they build in the kernel-headers package, which can be installed
without the whole source. These files are found in the
/usr/src/linux/configs/ directory: all you really need to do is copy the
appropriate one to /usr/src/linux/.config
OTOH, even that should not be necessary. I have made a working generic
source rpm spec file for RedHat 6.[12], which requires no hand editing
of MCONFIG, or anything else, and automates the process of copying the
.config file, as above, if it does not exist (may not work for SMP
systems). If anyone is interested, I could send them a copy for
testing, or even upload it somewhere. If it works on a variety of
systems, someone could post binary rpms for different architectures
(i486, i586, i686), and thus eliminate a lot of traffic on this list.
Then we could ask RedHat to stop shipping junk ftape modules with their
kernels, and ship separate ftape driver rpms that work, instead. Linux
will not progress as fast onto the desktop until/unless we insist that
distributors ship stuff that works pretty much out of the box. The
present way of doing things is absurd: every day we see people wading
through this arcane process, again and again -- what a waste.
We also need an interactive ftape configure script to help with setting
up /etc/conf.modules for the particular hardware configuration in use.
LCR
--
L. C. Robinson
reply to [EMAIL PROTECTED]
People buy MicroShaft for compatibility, but get incompatibility and
instability instead. This is award winning "innovation". Find
out how MS holds your data hostage with "The *Lens*"; see
"CyberSnare" at http://www.netaction.org/msoft/cybersnare.html
