Newbie Question: Slack 2.3

Newbie Question: Slack 2.3

Post by Rey Ban » Thu, 18 Jan 1996 04:00:00

Newbie question:

When installing Slackware 2.3, I'm prompted to select which kernel I'd like
to install from the 'Q' series (ie: bare, idecd1,idecd2,idenet, aztech,
etc.).  If I chose to install all of them by entering 'Y', would I be
creating one big kernel with support for all of the devices listed in these
selections (ie: if I said yes to idecd1,idecd2,idenet, aztech, etc.) or would
I simply be making a copy of each of these kernels & their source to my
machine (basically, seperate files that reside on my system and basically do
nothing but take up space)?  

Additionally, if I needed to ad support for a device that wasn't supported by
one of the kernels provided by Slackware, how would I go about including that
support into my kernel? For example, lets assume that I needed to use the  
kernel X that only supports IDE devices.  But also needed to add in support
for a SCSI tape. The kernel X doesn't support the SCSI device so I need to
add a driver to my kernel in order to support the SCSI tape. What would I
compile into my kernel?  Is it a C program that would need to be added?

Finally, are there any FAQs on how to use loadable modules?




Newbie Question: Slack 2.3

Post by Ralph L. Meye » Thu, 18 Jan 1996 04:00:00

On installation, you select a kernel that has built into it support for
the devices you have on your machine, even if its a large one with
support for lots of other devices.  Slackware will install only one
kernel, not a bunch, but the kernel will have built into it the support
for the devices (including those you don't need) and may indeed be large.
 On first installation, you need to install the kernel that will access
your peripherals, even if it has other stuff you don't need.  AFTER linux
is installed, boots properly, etc., THEN you compile a new kernel that
contains only the support for the various devices you have and need to
access.  It will generally be smaller than the installation kernel.  
Information on kernel compilation can be found in Welsh's _Running Linux_
and in a number of other manuals.  I believe there is also information
available in the Linux documentation project materials at sunsite and


Newbie Question: Slack 2.3

Post by Stephen Farlo » Fri, 19 Jan 1996 04:00:00

Excellent reply!
Re-compiling the kernel after a new installation is a must, in my opinion.
Read the "linux Kernel HOWTO" by Brian Ward, v0.36, dated 10 Sept 1995.

1. Slack 2.3 to 3.0 - no color console

I decided to do a complete reinstall of Slackware 3.0 from 2.3 and lost color
on  the console.  DIR_COLOR is set and works ok, ls output is colorized but
apps like Midnite Commander are in text mode b/w with no reverse video on the
cursor location.  Mouse pointer is active.  SW 2.3 console was blue
background with yellow foreground.  Setterm will work but only on cuurent
session.  New logins loose color even after setterm -store.  

Any clues?  Thanks in advance...

R Cooper

2. looking for PD CMS-type software for unix

3. glibc-2.2.3 on slack (was: recompiling glibc under slackware)

4. 3Com (3C905) - Urgent

5. Cannot Boot Slack 2.3


7. Slack 2.3 Install problems

8. fix incorrect ext2 partition table?

9. tar, gzip, foreach in Slack 2.3

10. gpm problems in Slack 2.3

11. SECURITY: in.rlogind -l flag doesn't work in Slack 2.3

12. Slack 2.3: X can't find my mouse!!

13. Slack 2.3 less/X and adduser script