๑๑/๑๔/๒๕๕๒

Disable Autorun.inf run on any medium

Earlier we saw how to remove a AutoRun Virus that abuse the autorun.inf file, to spread itself.Now, let us see how to turn off AutoRun.inf and thus protect your PC from AutoRun viruses and malwares.Windows had a bug in the way it handled AutoRun related Registry entries. When AutoRun is disabled, Windows operating system should not go past the Registry check. However, Windows continued to parse autorun.inf found on the removable media and did everything except the final action to invoke AutoPlay or execute an application.
How to Disable AutoRun.inf?
Nick Brown came up with a solution to prevent AUTORUN.INF files from being used on a PC, from any medium. This method involved using an initialisation file mapping, to create a mapping between the AUTORUN.INF initialisation file and the Registry. IniFileMapping is a key which tells Windows how to handle the .INI files which those applications typically used to store their configuration data (before the registry existed).This procedure relied on the fact that an autorun.inf file is a standard Windows INI file and so the appropriate API calls are used by Windows, when fetching its settings. These API calls can be redirected using the INI file mapping method. In this case, it says “whenever you have to handle a file called AUTORUN.INF, don’t use the values from the file. You’ll find alternative values at HKEY_LOCAL_MACHINE\SOFTWARE\DoesNotExist.” So how is this done?
Create a Registry file with the following contents and save it as DISABLEAUTORUN.REG.


Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
NT\CurrentVersion\IniFileMapping\Autorun.inf]
@="@SYS:DoesNotExist"


Double click DISABLEAUTORUN.REG to make the relevant changes to Windows Registry. Now whenever Windows tries to read a file called “autorun.inf” using the INI programming calls, it is forbidden from reading from the actual file. Instead, all settings are read from the HKEY_LOCAL_MACHINE\Software\DoesNotExist Registry key. As this key does not exist, it is as if the autorun.inf file contains no settings information. This applies to any autorun.inf in any location and on any drive.
The only drawback with this approach is you need to manually trigger the setup program in any inserted CD or USB Stick. But isn’t it better to live with this than with AutoRun viruses?

credit: http://techblissonline.com/disable-autorun/

๑๑/๑๒/๒๕๕๒

mythtv Open source PVR

http://www.mythtv.org/
http://www.pvrweb.com/
##
Ubuntu 9.10
sudo apt-get build-dep mythtv

๑๑/๐๕/๒๕๕๒

software raid url

http://slacksite.com/slackware/raid.html
using mdadm new raidtool
http://linuxdevcenter.com/pub/a/linux/2002/12/05/RAID.html 

๑๐/๒๘/๒๕๕๒

Install Slackware Hardware RAID SCSI CDROM

My system: Dell Poweredge 4300, 2x-PII-350's, 6-4.3gb raided with the Dell/AMI MegaRAID II card, Floppy and SCSI CD-ROM on the second Adaptec embedded UW controller on the MOBO. This should work for other types of SCSI Raid cards (If supported by the raid.s kernel) and Adaptec controlled SCSI-CD-Rom drives.

Here are the steps:

A. Do a Google search for "kernel-modules-2.4.22-i486-2" download
the .gz from one of the "hits".

B. Un-tar and save module aic7xxx.o to a floppy. You will need this later in step "5" below.

1. Boot your system and enable your CD-ROM device as bootable in the
SCSI Bios setup.

2. Boot up your Slackware 9.1 Install CD-I (You did download an burn them
from the ISO's right?)

3. Select kernel image "raid.s" this will allow recognition of your SCSI drives.

4. Log in as "root"...

5. Insert the floppy with aic7xxx.o on it into your floppy drive.

6. Do "mount /mnt/fd0 /mnt"

7. cd to /mnt

8. Do "insmod aic7xxx.o" (this sets up the adaptec SCSI support in the
kernel insmod - "install loadable module").

9. Run "setup" normally, select your mount points, etc. (I'm presuming you
have run fdisk or cfdisk ).

10. Select your "source" as CD-ROM and allow setup to search for it...

11. VIOLA!! Slackware "sees" your CD-Rom drive running on the Adaptec
controller and your RAID drives are still recognized!

12. Continue with the installation normally!

enj

Slackware 9.1 & 10.1 on software raid-1

Slackware 9.1 & 10.1 on software raid-1 : HOWTO

6th May 2006, version 1.5
© David Fletcher
The original of this document can be found at: www.megapico.co.uk/linuxdocs/slackware_raid.html
If you have updates or suggestions for this document, please send them to "linuxdocs at megapico dot co dot uk"
Latest updates are at the bottom

HOWTO!

Installing Slackware with software raid-1 is surprisingly easy to do - once you know how! Although the installer doesn't do everything for you like some other distributions, there are only a few extra steps required relative to a standard Slackware install.
I assume that you have two identical ide hard drives, one each on the primary and secondary controllers. I'll also assume that you don't have any data you want to keep on these drives, and that you are installing using a Slackware CD.
The steps are:
  1. Boot from the install cd. I found the "bare.i" kernel did everything I needed
  2. Log in as root and use fdisk to partition both drives in exactly the same way. Set all the partitions to type "fd" (linux raid auto-detect) except for any extended partitions, which should be left as type "linux extended".
    Set the active or bootable partition on both drives to whichever partition contacts /boot.
  3. Create the file /etc/raidtab using vi, or copy it in from a floppy or CD (see below). Typical contents of this file are:
    raiddev       /dev/md0
    raid-level    1
    chunk-size    64k
    persistent-superblock 1
    nr-raid-disks 2
        device    /dev/hda1
        raid-disk 0
        device    /dev/hdb1
        raid-disk 1
    raiddev       /dev/md1
    raid-level    1
    chunk-size    64k
    persistent-superblock 1
    nr-raid-disks 2
        device    /dev/hda5
        raid-disk 0
        device    /dev/hdb5
        raid-disk 1
    
    for as many raid devices as you want to create.
  4. Ensure there are enough raid device files in /dev. Four are present by default, but you can create more using
    mknod /dev/md4 b 9 4
    mknod /dev/md5 b 9 5
    
    etc.
  5. Start the first raid device using
    mkraid /dev/md0
    and repeat for the higher numbered ones. If you have data on the discs which you want to keep, ensure it is on the first disc of each pair as defined in /etc/raidtab. If you need to, try --really-force to wipe filesystems on the second drive of each pair.
  6. Check progress by looking at /proc/mdstat using "more".
  7. Copy /etc/raditab to a floppy now. You will loose it if you switch off at this stage since it is on a ram drive.
  8. If you want to use tagfiles to set-up the system automatically (perhaps if setting up several identical systems) this can be done easily if you have a floppy which can be mounted to read the files. You can also copy in /etc/raidtab and /etc/lilo.conf if you have them already written (see above).
    For a system without a floppy I found that a USB flash drive is not supported by the installation CD, but a CD with the required files can be mounted and read before typing "setup". If the CD is /dev/hdc use:
    mount /dev/hdc /var/log/mount
    and then copy the files you want. Remember that with the exception of directories below /mnt which are the hard drive partitions onto which the installation will take place, you are copying to a filesystem which exists only in RAM. Don't turn the machine off until the installation is completed! Finish off with
    umount /dev/hdc
    and put the installation CD back in the drive.
  9. You can now start "setup" as usual, but you will find it is slow if you don't wait for all the raid discs to finish synchronising.
  10. Go through setup as normal, but note that you can't set up a swap partition yet - you will get an error about not having partition marked as swap. Just ignore this and set up the swap partition later.
  11. When you are asked about setting up Lilo, choose "skip". You need to add some special lines to lilo.conf, which setup can't cope with.
  12. Exit setup, but don't reboot yet! First, copy /etc/raidtab to /mnt/etc/raidtab
  13. Also before rebooting, set up the swap partition. If you plan to use /dev/md1 for swap, type
    mkswap -c /dev/md1
    This includes checking for bad blocks, so it is quite slow.
  14. To ensure swap works the next time you boot up, edit /mnt/etc/fstab to add this line:
    /dev/md1   swap   swap   defaults 0 0
    where /dev/md1 is the raid device on which you have set-up swap.
  15. Now install lilo using a lilo.conf file of the type shown below. This file can be created with vi as /mnt/etc/lilo.conf. The example assumes that that the root of the filesystem is on /dev/md3, and that /boot is on /dev/md0, and that the two discs making up the raid are /dev/hda and /dev/hdc.
    The "raid-extra-boot" line ensures that both discs of the raid pair have boot code placed on them, so if either fails the system should still boot. However, if the usual start-up disc is the one which fails, you might need to manually set the bios to boot from the remaining good disc.
    boot = /dev/md0
    raid-extra-boot="/dev/hda,/dev/hdc"
    timeout = 50
    vga = normal
    
    image = /boot/vmlinuz
      root = /dev/md3
      label = linux
      read-only 
    
    This needs to be installed using the lilo -r option because the filesystem which will be the root is mounted under /mnt during setup.
    lilo -r /mnt/ -C /etc/lilo.conf
    
    An alternative that seems to work is just to copy the file you have edited from /mnt/etc/lilo.conf to /etc/lilo.conf and then run lilo without any options. To try out what lilo is going to do use options -t -v to do a test run without really writing to the disc. Any warnings like
    Warning: dev/hdc is not on the first disk
    can be ignored - they are just for information.
  16. Now take out the setup cd and reboot. The system should start-up from the hard disc. You can check the raid devices by reading /proc/mdstat

Updates

  1. Steve Husted in West Sacramento, CA, USA contacted me to say that these instructions work on Slackware Current 23rd December 2004 (pretty much equates to Slackware 10.1) on a board with an Intel 865G chipset with 2 Maxtor SATA drives.
    Steve also passed on some links to more information at:
    http://www.oxnardcollege.edu/it/howto/slacksoftraid.asp
    http://slacksite.com/slackware/raid.html
    A complication of Serial ATA with the Slackware installation is that the 2.4 kernel series doesn't seem to support SATA as well as the 2.6, (e.g. the ICH5 I/O controller gets stuck in PIO mode) but the installation is currently designed to use the 2.4 kernel. As of Jan 2005 you need to decide if a post-install upgrade to the 2.6 series will be stable enough for you, otherwise use SCSI or traditional ATA hardware. If using SCSI, remember to replace the bare.i krenel image with adaptec.s, or whichever corresponds to your SCSI card.
    Steve found out the hard way that while you can build a RAID 0, 1, 5, or span, you can't BOOT to anything but RAID1.
  2. Nick Coons from RedSeven Computer Co (http://www.red7usa.com) let me know on 28th Aug 2005 of a mistake in the lilo command line which is hopefully now correct, but things otherwise went well on Slackware 10.1. The lilo command previously read lilo -r /mnt/ /mnt/etc/lilo.conf
  3. Installation onto SCSI discs. I found a problem with installation into SCSI discs connected to the Adaptec AIC7892 controller in an IBM x330 server. I don't know if the problem is general to all SCSI controllers, but it is worth noting here.
    Although the partition on which lilo was installed (/dev/sda1) was set 'active' using fdisk, and the SCSI bios was set to boot from the disc, the system would not boot. Installing lilo onto the Master Boot Record (MBR) rather than a partition of the drive solved the problem. This required using the line below in lilo.conf:
    boot = /dev/sda
    
  4. Some experiments with 'raid-extra-boot = mbr' might also be useful. I'll add details here which they are available.

Disclaimer

Neither the author nor the distributors, or any other contributor of this HOWTO are in any way responsible for physical, financial, moral or any other type of damage incurred by following the suggestions in this text.

credit:  http://www.megapico.co.uk/linuxdocs/slackware_raid.html

Slackware Creating The Boot Disk

Once you have selected a boot disk image file from the list below, you will need to create the disk. If you are creating the image from a Linux system, the following command should work just fine:

dd if=[image file name] of=/dev/fd0
You may need to change /dev/fd0 depending on your configuration. If you are creating the image from a DOS system, the included program RAWRITE will help you make the disk. Here is the syntax for RAWRITE:

C:\>RAWRITE [image file name] [destination drive letter]:
For example, if I wanted to make a boot disk from the net.i image on a DOS system with the floppy drive as A:, I would use the following command.

C:\>RAWRITE bare.i a:
You should now have a working boot disk to use during the Slackware Linux installation.

IDE bootdisks (.i suffix)
bare.i This is the disk to use for installation on most IDE based PCs, with support for nearly all IDE controllers and support for IDE/ATAPI CD-ROM/DVD drives. Most CD-ROM drives made today fall into this category.
bareacpi.i This is similar to the bare.i bootdisk, but the kernel also contains support for ACPI (Advanced Configuration and Power Interface). If you aren't using a laptop, then you probably will not need ACPI (or APM) support.
ataraid.i This is a bootdisk with support for IDE RAID controllers. The install disks now have preliminary support for these controllers as well. The drivers included are: 3ware Hardware ATA-RAID controllers. Promise Fasttrak(tm) IDE RAID. Highpoint 370 software RAID. Many of these controllers will require some degree of do-it-yourself setup before and/or after installation.
lowmem.i This is a really stripped-down Linux kernel which might be useful for installing on IDE systems with a low amount of RAM (less than 8MB). It's also the only Slackware kernel that supports old 386 machines. If bare.i runs into problems, you might try this. NOTE: On systems with extremely low memory (4MB), ZipSlack plus the fourmeg.zip add-on (found in the zipslack directory) may boot and run even in cases where lowmem.i doesn't. If you have to use lowmem.i to install, you'll then probably have to compile a custom kernel with the minimal additional features that your machine requires.
old_cd.i This is a version of bare.i with additional support for old CD-ROM drives on non-standard proprietary interfaces. The CD-ROM drives supported by this bootdisk are: Aztech CDA268-01A, Orchid CD-3110, Okano/Wearnes CDD110, Conrad TXC, CyCDROM CR520, CR540. Sony CDU31/33a CD-ROM. Sony CDU531/535 CD-ROM. Philips/LMS cm206 CD-ROM with cm260 adapter card. Goldstar R420 CD-ROM (sometimes sold in a 'Reveal Multimedia Kit'). ISP16/MAD16/Mozart CD-ROM drives. NON-IDE Mitsumi CD-ROM support. Optics Storage 8000 AT CD-ROM (the 'DOLPHIN' drive). Sanyo CDR-H94A CD-ROM support. Matsushita, Kotobuki, Panasonic, CreativeLabs (Sound Blaster), Longshine and Teac NON-IDE CD-ROM support.
pportide.i This is an extended version of bare.i with support for a wide variety of parallel-port IDE devices. Supports parallel-port products from MicroSolutions, Hewlett-Packard, SyQuest, Imation, Avatar, and other manufacturers.
sata.i This is a version of bare.i with support for SATA controllers made by Promise, Silicon Image, SiS, ServerWorks / Apple K2, VIA, and Vitesse.

SCSI bootdisks (.s suffix)
adaptec.s This bootdisk supports most Adaptec SCSI controllers, including these models: AHA-1510, AHA-1520, AHA-1522, AHA-1522, AHA-1740, and AHA-2825. The AIC7xxx models, which include the 274x EISA cards; 284x VLB cards; 2902, 2910, 293x, 294x, 394x, 3985 and several other PCI and motherboard based SCSI controllers from Adaptec. Adaptec's I2O based RAID controllers (including OEM Adaptec RAID controllers used by HP and Dell, Adaptec branded AAC964/5400 RAID controllers, and DPT SmartRaid V cards)
ibmmca.s This is a bootdisk based on a development kernel which supports MicroChannel Architecture, found in some IBM PS/2 machines and laptops. It is a bus system similar to PCI or ISA. Support for most MCA SCSI, Ethernet, and Token Ring adapters is included.
jfs.s A version of bare.i with support for IBM's Journaled Filesystem as well as Adaptec AIC7xxx SCSI support.
raid.s This is a bootdisk with support for some hardware SCSI and ATA RAID controllers. The install disks now have preliminary support for these controllers as well. The drivers included are: AMI MegaRAID 418, 428, 438, 466, 762, 490 and 467 SCSI host adapters, Compaq Smart, Compaq Smart Array 5xxx, IBM ServeRAID hardware RAID, LSI Logic Fusion(TM) MPT devices (not really RAID, but added since there was room for this driver here), Mylex DAC960, AcceleRAID, and eXtremeRAID controllers. Many of these controllers will require some degree of do-it-yourself setup before and/or after installation.
scsi.s This is a SCSI bootdisk with support for various controllers. Note that this disk does not include Adaptec support any longer -- you must use the adaptec.s bootdisk for that. This disk supports these SCSI controllers: AM53/79C974 PCI SCSI, BusLogic SCSI, EATA ISA/EISA/PCI (DPT and generic EATA/DMA-compliant boards), Initio 91XXU(W) and Initio 91XXU(W), SYM53C8XX Version 2, Qlogic ISP SCSI, Qlogic QLA 1280 SCSI.
scsi2.s This is a SCSI bootdisk with support for various controllers. This disk supports these SCSI controllers: AdvanSys SCSI (supports all AdvanSys SCSI controllers, including some SCSI cards included with HP CD-R/RW drives, the Iomega Jaz Jet SCSI controller, and the SCSI controller on the Iomega Buz multimedia adapter), ACARD 870U/W SCSI host adapter, Compaq Fibre Channel 64-bit/66Mhz HBA, Domex DMX3191D SCSI Host Adapters, DTC 3180/3280 SCSI Host Adapters, Future Domain 16xx SCSI/AHA-2920A, NCR53c7, 8xx, NCR53C8XX
scsi3.s This is a SCSI bootdisk with support for various controllers. This disk supports these SCSI controllers: Western Digital 7000FASST SCSI support, Always IN2000, Intel/ICP (former GDT SCSI Disk Array) RAID Controller, PCI2000I, PCI2220i, PSI240i EIDE interface card, Qlogic FAS SCSI, QLogic ISP FC (ISP2100 SCSI-FCP), Seagate ST01/ST02, Future Domain TMC-885/950 SCSI, SYM53c416 SCSI host adapter, UltraStor 14F, 24F and 34F SCSI-2 host adapters, Workbit NinjaSCSI-32Bi/UDE
speakup.s This is like the bare.i (standard IDE) disk, but has support for Speakup (and since there was space, support for Adaptec's AIC7xxx SCSI controllers is also included) Speakup provides access to Linux for the visually impaired community. It does this by sending console output to a number of different hardware speech synthesizers. It provides access to Linux by making screen review functions available. For more information about speakup and its drivers check out: http://www.linux-speakup.org. To use this, you'll need to specify one of the supported synthesizers on the bootdisk's boot prompt:
ramdisk speakup_synth=synth
where 'synth' is one of the supported speech synthesizers: acntpc, acntsa, apolo, audptr, bns, decext, dectlk, dtlk, ltlk, spkout, txprt
xfs.s This is an extended version of bare.i with support for SGI's XFS filesystem. Support for Adaptec's AIC7xxx SCSI controllers is also included.

Slackware 9.1 & 10.1 on software raid-1

Slackware 9.1 & 10.1 on software raid-1 : HOWTO

6th May 2006, version 1.5
© David Fletcher
The original of this document can be found at: www.megapico.co.uk/linuxdocs/slackware_raid.html
If you have updates or suggestions for this document, please send them to "linuxdocs at megapico dot co dot uk"
Latest updates are at the bottom

HOWTO!

Installing Slackware with software raid-1 is surprisingly easy to do - once you know how! Although the installer doesn't do everything for you like some other distributions, there are only a few extra steps required relative to a standard Slackware install.
I assume that you have two identical ide hard drives, one each on the primary and secondary controllers. I'll also assume that you don't have any data you want to keep on these drives, and that you are installing using a Slackware CD.
The steps are:
  1. Boot from the install cd. I found the "bare.i" kernel did everything I needed
  2. Log in as root and use fdisk to partition both drives in exactly the same way. Set all the partitions to type "fd" (linux raid auto-detect) except for any extended partitions, which should be left as type "linux extended".
    Set the active or bootable partition on both drives to whichever partition contacts /boot.
  3. Create the file /etc/raidtab using vi, or copy it in from a floppy or CD (see below). Typical contents of this file are:
    raiddev       /dev/md0
    raid-level    1
    chunk-size    64k
    persistent-superblock 1
    nr-raid-disks 2
        device    /dev/hda1
        raid-disk 0
        device    /dev/hdb1
        raid-disk 1
    raiddev       /dev/md1
    raid-level    1
    chunk-size    64k
    persistent-superblock 1
    nr-raid-disks 2
        device    /dev/hda5
        raid-disk 0
        device    /dev/hdb5
        raid-disk 1
    
    for as many raid devices as you want to create.
  4. Ensure there are enough raid device files in /dev. Four are present by default, but you can create more using
    mknod /dev/md4 b 9 4
    mknod /dev/md5 b 9 5
    
    etc.
  5. Start the first raid device using
    mkraid /dev/md0
    and repeat for the higher numbered ones. If you have data on the discs which you want to keep, ensure it is on the first disc of each pair as defined in /etc/raidtab. If you need to, try --really-force to wipe filesystems on the second drive of each pair.
  6. Check progress by looking at /proc/mdstat using "more".
  7. Copy /etc/raditab to a floppy now. You will loose it if you switch off at this stage since it is on a ram drive.
  8. If you want to use tagfiles to set-up the system automatically (perhaps if setting up several identical systems) this can be done easily if you have a floppy which can be mounted to read the files. You can also copy in /etc/raidtab and /etc/lilo.conf if you have them already written (see above).
    For a system without a floppy I found that a USB flash drive is not supported by the installation CD, but a CD with the required files can be mounted and read before typing "setup". If the CD is /dev/hdc use:

    mount /dev/hdc /var/log/mount
    and then copy the files you want. Remember that with the exception of directories below /mnt which are the hard drive partitions onto which the installation will take place, you are copying to a filesystem which exists only in RAM. Don't turn the machine off until the installation is completed! Finish off with

    umount /dev/hdc
    and put the installation CD back in the drive.

  9. You can now start "setup" as usual, but you will find it is slow if you don't wait for all the raid discs to finish synchronising.
  10. Go through setup as normal, but note that you can't set up a swap partition yet - you will get an error about not having partition marked as swap. Just ignore this and set up the swap partition later.
  11. When you are asked about setting up Lilo, choose "skip". You need to add some special lines to lilo.conf, which setup can't cope with.
  12. Exit setup, but don't reboot yet! First, copy /etc/raidtab to /mnt/etc/raidtab
  13. Also before rebooting, set up the swap partition. If you plan to use /dev/md1 for swap, type
    mkswap -c /dev/md1
    This includes checking for bad blocks, so it is quite slow.
  14. To ensure swap works the next time you boot up, edit /mnt/etc/fstab to add this line:
    /dev/md1   swap   swap   defaults 0 0
    where /dev/md1 is the raid device on which you have set-up swap.
  15. Now install lilo using a lilo.conf file of the type shown below. This file can be created with vi as /mnt/etc/lilo.conf. The example assumes that that the root of the filesystem is on /dev/md3, and that /boot is on /dev/md0, and that the two discs making up the raid are /dev/hda and /dev/hdc.
    The "raid-extra-boot" line ensures that both discs of the raid pair have boot code placed on them, so if either fails the system should still boot. However, if the usual start-up disc is the one which fails, you might need to manually set the bios to boot from the remaining good disc.

    boot = /dev/md0
    raid-extra-boot="/dev/hda,/dev/hdc"
    timeout = 50
    vga = normal
    
    image = /boot/vmlinuz
      root = /dev/md3
      label = linux
      read-only 
    
    This needs to be installed using the lilo -r option because the filesystem which will be the root is mounted under /mnt during setup.
    lilo -r /mnt/ -C /etc/lilo.conf
    
    An alternative that seems to work is just to copy the file you have edited from /mnt/etc/lilo.conf to /etc/lilo.conf and then run lilo without any options. To try out what lilo is going to do use options -t -v to do a test run without really writing to the disc. Any warnings like
    Warning: dev/hdc is not on the first disk
    can be ignored - they are just for information.
  16. Now take out the setup cd and reboot. The system should start-up from the hard disc. You can check the raid devices by reading /proc/mdstat

Updates


  1. Steve Husted in West Sacramento, CA, USA contacted me to say that these instructions work on Slackware Current 23rd December 2004 (pretty much equates to Slackware 10.1) on a board with an Intel 865G chipset with 2 Maxtor SATA drives.
    Steve also passed on some links to more information at:
    http://www.oxnardcollege.edu/it/howto/slacksoftraid.asp
    http://slacksite.com/slackware/raid.html
    A complication of Serial ATA with the Slackware installation is that the 2.4 kernel series doesn't seem to support SATA as well as the 2.6, (e.g. the ICH5 I/O controller gets stuck in PIO mode) but the installation is currently designed to use the 2.4 kernel. As of Jan 2005 you need to decide if a post-install upgrade to the 2.6 series will be stable enough for you, otherwise use SCSI or traditional ATA hardware. If using SCSI, remember to replace the bare.i krenel image with adaptec.s, or whichever corresponds to your SCSI card.
    Steve found out the hard way that while you can build a RAID 0, 1, 5, or span, you can't BOOT to anything but RAID1.
  2. Nick Coons from RedSeven Computer Co (http://www.red7usa.com) let me know on 28th Aug 2005 of a mistake in the lilo command line which is hopefully now correct, but things otherwise went well on Slackware 10.1. The lilo command previously read lilo -r /mnt/ /mnt/etc/lilo.conf
  3. Installation onto SCSI discs. I found a problem with installation into SCSI discs connected to the Adaptec AIC7892 controller in an IBM x330 server. I don't know if the problem is general to all SCSI controllers, but it is worth noting here.
    Although the partition on which lilo was installed (/dev/sda1) was set 'active' using fdisk, and the SCSI bios was set to boot from the disc, the system would not boot. Installing lilo onto the Master Boot Record (MBR) rather than a partition of the drive solved the problem. This required using the line below in lilo.conf:

    boot = /dev/sda
    
    Some experiments with 'raid-extra-boot = mbr' might also be useful. I'll add details here which they are available.

Disclaimer

Neither the author nor the distributors, or any other contributor of this HOWTO are in any way responsible for physical, financial, moral or any other type of damage incurred by following the suggestions in this text.

Get if from: http://www.megapico.co.uk/linuxdocs/slackware_raid.html