Slashdot Mirror


Building ATA RAID and SMP Support into Slackware 9

TheMadPenguin writes "This HOWTO will describe the steps necessary to build support into Slackware Linux 9.0 for Symmetric multiprocessing (SMP) and a Promise Ultra ATA RAID redundant drive array. By default, there is no support for these configurations unless specified through a kernel recompilation after the initial install."

4 of 171 comments (clear)

  1. Uhm... by ciryon · · Score: 5, Interesting

    If you choose to run Slackware, wouldn't you know how to do this?

    There are so many people that wanna run Linux and heard that slack is the coolest and most "pro" way to do it. Sickens me. :-P

    Ciryon

  2. HOW WILL LINUX EVER BE A CONSUMER OS. . . by Fritz+Benwalla · · Score: 5, Funny

    . . . if my Mom has to recompile the kernel just to get symmetric multiprocessing support and a working ATA raid array for chrissake??!!!

    -----

    --

    Believe me, I'm as surprised by my comment as you are.
  3. Use Slackware's kernel source package. by volkerdi · · Score: 5, Informative

    It's better to use Slackware's kernel-source-2.4.20-noarch-5.tgz package, since it already contains patches for some ext3 bugs as well as the recent ptrace exploit.

    If you do use the original 2.4.20 tarball in the source/k directory, you will need to apply the linux-2.4.20.ptrace.diff.gz that you'll find in the same directory, and if you use ext3, you'll also want to apply the patches from the ext3-patches directory.

  4. mistake, imho by doodleboy · · Score: 5, Informative
    article says: #> mv /lib/modules/2.4.20 /lib/modules/orig
    Bad bad bad. Now the original config is unbootable, a bad thing when you're monkeying around with the kernel. What you do is edit the kernel Makefile and add something to the extraversion parameter, i.e.:

    EXTRAVERSION = -smp_raid

    Then you'll have two entries under /lib/modules, 2.4.20 and 2.4.20-smp_raid. Make the appropriate entries in /etc/lilo.conf and you can boot either one. Disabling a stock, working kernel config is lunacy. Using extraversion is obviously the safer method, that's what it's for. This is all mentioned in the kernel HOWTO, iirc.