If you downloaded everything, you have the full set of pre-compiled kernels
somewhere in what you got. I don't know where, since I've never gotten a
complete Slackware by download -- the CD has a drectory /kernels at the top
level. Basic ide and scsi kernels are also part of the A package set - if
you just keep whichever you installed from the A series, you will probably
be okay.
I did mean compile a custom kernel when I said "build your own".
Why did they do it? Beats me. Maybe 2.2.x is too big for a bootdisk?
(Probably not; splitting the load into bootdisk and rootdisk should give
them plenty of room to work with.) I do know that Slackware 3.9 (2.0.37
kernel) and 4.0 (2.2.6 kernel) use the same bootdisk/rootdisk sets, so they
had to pick one to match.
At 10:46 AM 8/30/99 -0300, Ted Gervais wrote [in part]:
>On Sun, 29 Aug 1999, Ray Olszewski wrote:
>
>> Sorry to jump in here ... but are you *sure* you are running kernel 2.2.6?
>> While that's the kernel that Slackware 4.0 uses, it is NOT the kernel on the
>> Slackware 4.0 bootdisk imagess -- the bootdisks use 2.0.something (I think
>> .37). If, near the end of your install, you selected the option that says
>> something like "use the kernel from the bootdisk", that's what fouled you
>> up.
>
>Hi Ray... and yes that is what I chose. I took the kernel from the
>bootdisk. Holy cow. Why would they do that?
[rest deleted]
------------------------------------"Never tell me the odds!"---
Ray Olszewski -- Han Solo
Palo Alto, CA 94303-3603 [EMAIL PROTECTED]
----------------------------------------------------------------
