สิ่งที่น่าทึ่งในชีวิต

Magic

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

Magic

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:

Boot from the install cd. I found the "bare.i" kernel did everything I needed
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.

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.

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.
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.
Check progress by looking at /proc/mdstat using "more".
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.
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.
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.
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.
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.
Exit setup, but don't reboot yet! First, copy /etc/raidtab to /mnt/etc/raidtab
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.
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.
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.
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

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.
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
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
```

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

Magic

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.

Magic

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:

Boot from the install cd. I found the "bare.i" kernel did everything I needed
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.

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.

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.
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.
Check progress by looking at /proc/mdstat using "more".
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.
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.
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.
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.
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.
Exit setup, but don't reboot yet! First, copy /etc/raidtab to /mnt/etc/raidtab
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.
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.
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.
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

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.
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
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

Magic

INSTALLING SLACKWARE LINUX version 8.1 WITH ROOT PARTITION ON
A SOFTWARE RAID level 0 DEVICE.

20021009  v 1.0.1



      Copyright (c)  2002  Karl Magnus Kolst๘.
      Permission is granted to copy, distribute and/or modify this document
      under the terms of the GNU Free Documentation License, Version 1.1
      or any later version published by the Free Software Foundation;
      with no Invariant Sections, no Front-Cover Texts, and no
      Back-Cover Texts.
      A copy of the license can be found here;
        http://www.gnu.org/licenses/fdl.txt

If you screw up something (like your data and/or your hardware)
while using this document it is your fault, not mine.
You should know what you are doing.  Reading some documentation
on software RAID is highly recommended.
(I.e the Software-RAID-HOWTO;
 http://www.tldp.org/HOWTO/Software-RAID-HOWTO.html )


Document History:

 v 1.0.1 20021009 Fix up the wording of a couple of sentences.
 v 1.0 20020913 Initial release.



This document is a small write-up on how I did install Slackware 8.1
on a software raid 0, aka striping.
Note that this document does not cover troubleshooting, only the
exact steps that should be nessesary to put Slack 8.1 on /
At least they where the steps I had to do to make it work.

This write-up should be usable for setting up software raid 
level 4 or 5 on Slackware too (with some tweaking).
As for raid level 1 the configuration should be similar too,
but different enought to say that this write-up doesn't cover it.

My disk setup was 7 disks on one SCSI channel.
(yes, I _know_ you shouldn't have that many drives on one channel :)
The computer could boot from those drives.

First I booted from the Slackware 8.1 CD.
Had to use kernel scsi.s because of my scsi setup.

At the prompt I started partitioning the drives with fdisk.
All my drives where identical, so I decided to partition them identically.
Partition 1 on each disk I put a 15MB partition.
Partition 2 on each disk I put the partition to be raided.
Partition 4 on each disk I put a swap partition.
(Why 4 and not 3?  Just a personal convention.  I always put swap
 on the forth primary partition on a disk.)

Then I set partition types 83, FD and 82 respectively.

Why that 15MB partition?  Linux can't boot the kernel directly
off of a software raided partition (raid1 is another story) so
it needs a partition to get the kernel from which is not a part of
a raid set.

That first partition on first drive (/dev/sda1 in my case)
I wanted to mount under /boot.  But why waste disk space?
I ended up setting up first partition on all the other drives
to type 82 (linux swap).  That way I ended up with 13(!) swap partitions.
A better way would probably be to set up the raid partitions on the end
of the drive and make a larger swap partition on the beginning of
each drive.  But then take 10-20MB of the the swap partition on the
first drive and use that for /boot.

Anyway I now have 7 drives partitioned the way I want.

First I must configure the raid.

Check if /dev/md0 exists.  (like 'ls -l /dev/md0')

If it doesn't exist, create it;
 mknod /dev/md0 b 9 0

I created a /etc/raidtab which looked like this;

-------- cut ---------
raiddev /dev/md0 
 raid-level 0
 nr-raid-disks 7
 nr-spare-disks 0
 chunk-size 32
 persistent-superblock 1
 device  /dev/sda2
 raid-disk 0
 device  /dev/sdb2
 raid-disk 1
 device  /dev/sdc2
 raid-disk 2
 device  /dev/sdd2
 raid-disk 3
 device  /dev/sde2
 raid-disk 4
 device  /dev/sdf2
 raid-disk 5
 device  /dev/sdg2
 raid-disk 6
-------- cut ---------

Then we need to start the raid set;
 mkraid /dev/md0
(if you have an already started set you must stop that and
 restart with option --force. (read the instructions))

Now it's time to create a filesystem on the "new" device.

 mke2fs -j -c -b 4096 -R stride=8 /dev/md0

I want ext3 (-j) I want to check the filesystem (-c) I want 4k block size
(-b 4096, which is default by the way) and I want to tell the formatting
tool something about my raid chunk size.
Calculate it this way;  stride = chunk-size / block-size
(all values in kilobytes)
For me the calculation is;  32 / 4 = 8


I must not forget to format the partition which is going to be /boot

 mke2fs -j -c /dev/sda1

Instead of letting the Slackware setup mount the partitions I do it myself.
(the setup is *not* aware of raid devices anyway, so this needs to be done
 manually.)

 mount /dev/md0 /mnt
 mkdir /mnt/boot
 mount /dev/sda1 /mnt/boot

Then we can run 'setup'

Do a regular install, but be sure to *not* add any partitions
to install on.  Just choose;  
 "---  (done adding partitions, continue with setup"
I also chose simple lilo install on mbr.

When the install is done, exit 'setup' and do the following;

 cp /etc/raidtab /mnt/etc/raidtab

edit /mnt/etc/fstab and add;
 /dev/md0 / ext3 defaults 1 1
 /dev/sda1 /boot ext3 defaults 1 2

edit /mnt/etc/lilo.conf

be sure that;
 root = /dev/fd2
gets changed to;
 root = /dev/md0


Then run
 lilo -C /mnt/etc/lilo.conf


Now you should be able to boot the machine with / on a RAID 0 device.


When trying to follow my own write-up I had the following problem
when trying to boot up the newly installed Slackware.
(This happend once of the 4 times I tested.)

For every partition I got;
 md: /dev/sda2's has invalid sb, not importing!
(Or a similar error message, at that point I didn't take notes, sorry.)

The computer halted with a Kernel Panic during boot.

I then booted from the CD again, created /etc/raidtab again
(equal to the first one), and reran mkraid /dev/md0.
After that I could mount /dev/md0, and everything looked
ok there.  Slackware was installed.
I did reboot, and everything came up as it should.

I still wonder if I followed this write-up to the letter or if
something strange happened.


Suggestions and error corrections are welcome.

Karl Magnus Kolst๘  karl.kolsto@geo.uib.no


Thanks to John Jenkins and Erik Jan Tromp for looking through this doc
and comming with suggestions.

# end of file


Get it from : http://userlocal.com/articles/raid0-slackware-linux.php

Magic

NAME
       tune2fs - adjust tunable filesystem parameters on ext2/ext3 fi
lesystems

SYNOPSIS
       tune2fs [ -l ] [ -c max-mount-counts ] [ -e errors-behavior ]
[ -f ] [
       -i interval-between-checks ] [ -j ] [ -J journal-optio
ns ] [ -m
       reserved-blocks-percentage ] [ -o [^]mount-options[,...]
] [ -r
       reserved-blocks-count ] [ -s sparse-super-flag ] [ -u user ] [
-g group
       ] [ -C mount-count ] [ -E extended-options ] [ -L volume-name
] [ -M
       last-mounted-directory ] [ -O [^]feature[,...]   ] [ -T t
ime-last-
       checked ] [ -U UUID ] device

DESCRIPTION
       tune2fs allows the system administrator to adjust various
tunable
       filesystem parameters on Linux ext2/ext3 filesystems.

Magic

เรียกใช้ตัวอักษรหรือตัวอักขระพิเศษด้วยปุ่ม Alt

เคย เห็นไหมครับ ว่าเวลาที่คุย IM ไม่ว่าจะเป็น MSN, Live Messenger, Skype, Goolgle Talk, Yahoo Messenger หรือโปรแกรมสนทนาออนไลน์อื่นๆ เราจะเห็นว่าบางคนหรือคู่สนทนาของเราพิมพ์สัญลักษณ์ต ัวอักษร หรือตัวอักขระพิเศษๆ แปลกๆส่งมา หรือแม้กระทั่งตกแต่งเว็บ Social หรือบล็อกต่างๆ เช่น Facebook, Myspace, Hi5, Exteen, Bloggang เป็นต้น แล้วเราจะเรียกใช้ตัวอักษรหรือตัวอักขระพิเศษเหล่านั ้นได้อย่างไร?

วันนี้ผมจะมาแนะนำวิธีเรียกใช้งานตัวอักษร หรือตัวอักขระพิเศษเหล่านั้นด้วยปุ่ม Alt คีย์ ซึ่งมีวิธีการดังต่อไปนี้

วิธี การ ก็คือ ให้กดปุ่ม Alt คีย์ค้างไว้ ตามด้วยกดปุ่มตัวเลข 4 หลักบนคีย์บอร์ด เมื่อกดปุ่มตัวเลข 4 หลักบนคีย์บอร์ดที่ต้องการเรียบร้อยแล้ว ให้ปล่อยปุ่ม Alt คีย์ที่กดค้างไว้ จากนั้นคุณก็จะเห็นตัวอักษร หรือตัวอักขระพิเศษ ปรากฏขึ้นมาแล้วหล่ะครับ

อ้างอิง:

Alt-0128 €	Alt-0252 ü	Alt-0129 �	Alt-0130 ‚	Alt-0131 ƒ
Alt-0132 „	Alt-0253 ý	Alt-0133 …	Alt-0134 †	Alt-0135 ‡
Alt-0136 ˆ	Alt-0254 þ	Alt-0137 ‰	Alt-0138 Š	Alt-0139 ‹
Alt-0140 Œ	Alt-0255 ÿ	Alt-0141 �	Alt-0142 Ž	Alt-0143 �
Alt-0144 �	Alt-0248 ø	Alt-0145 ‘	Alt-0146 ’	Alt-0147 “
Alt-0148 “	Alt-0249 ù	Alt-0149 •	Alt-0150 –	Alt-0151 —
Alt-0152 ˜	Alt-0250 ú	Alt-0153 ™	Alt-0154 š	Alt-0155 ›
Alt-0156 œ	Alt-0251 û	Alt-0157 �	Alt-0158 ž	Alt-0159 Ÿ
Alt-0160	Alt-0244 ô	Alt-0161 ¡	Alt-0162 ¢	Alt-0163 £
Alt-0164 ¤	Alt-0245 õ	Alt-0165 ¥	Alt-0166 ¦	Alt-0167 §
Alt-0168 ¨	Alt-0246 ö	Alt-0169 ©	Alt-0170 ª	Alt-0171 «
Alt-0172 ¬	Alt-0247 ÷	Alt-0173	Alt-0174 ®	Alt-0175 ¯
Alt-0176 °	Alt-0240 ð	Alt-0177 ±	Alt-0178 ²	Alt-0179 ³
Alt-0180 ´	Alt-0241 ñ	Alt-0181 µ	Alt-0182 ¶	Alt-0183 ·
Alt-0184 ¸	Alt-0242 ò	Alt-0185 ¹	Alt-0186 º	Alt-0187 »
Alt-0188 ¼	Alt-0243 ó	Alt-0189 ½	Alt-0190 ¾	Alt-0191 ¿
Alt-0192 À	Alt-0236 ì	Alt-0193 Á	Alt-0194 Â	Alt-0195 Ã
Alt-0196 Ä	Alt-0237 í	Alt-0197 Å	Alt-0198 Æ	Alt-0199 Ç
Alt-0200 È	Alt-0238 î	Alt-0201 É	Alt-0202 Ê	Alt-0203 Ë
Alt-0204 Ì	Alt-0239 ï	Alt-0205 Í	Alt-0206 Î	Alt-0207 Ï
Alt-0208 Ð	Alt-0232 è	Alt-0209 Ñ	Alt-0210 Ò	Alt-0211 Ó
Alt-0212 Ô	Alt-0233 é	Alt-0213 Õ	Alt-0214 Ö	Alt-0215 ×
Alt-0216 Ø	Alt-0234 ê	Alt-0217 Ù	Alt-0218 Ú	Alt-0219 Û
Alt-0220 Ü	Alt-0235 ë	Alt-0221 Ý	Alt-0222 Þ	Alt-0223 ß
Alt-0224 à	Alt-0231 ç	Alt-0225 á	Alt-0226 â	Alt-0227 ã
Alt-0228 ä	Alt-0230 æ	Alt-0229 å

นอก จากนี้ คุณยังสามารถใช้โปรแกรม Character Map Utility ซึ่งเป็นยูทิลิตีฟรีตัวหนึ่งที่มาพร้อมกับวินโดวส์ ซึ่งคุณสามารถคัดลอก และวางตัวอักษรหรือตัวอักขระพิเศษเหล่านั้น เพื่อนำไปใช้งานในโปรแกรมอื่นๆได้ เช่น Microsoft Word, Microsoft Frontpage หรือโปรแกรมอื่นๆ เป็นต้น ซึ่งวิธีการเรียกใช้ Character Map Utility ทำได้ดังนี้
1. ให้ไป Start > Programs > Accessories > System Tools > Character Map
2. หรือไปที่ Start > Run > จากนั้นพิมพ์ว่า Charmap แล้ว OK หรือกดปุ่ม Enter
3. หลังจากที่เปิดโปรแกรมขึ้นมาเรียบร้อยแล้ว ให้เลือกรูปแบบตัวอักษร แล้วคลิกที่ตัวอักษรพิเศษที่คุณต้องการ จากนั้นก็คลิก Copy แล้วเอาไปวางในโปรแกรมที่คุณต้องการ
เห็นไหมหล่ะครับ วิธีการง่ายๆเพียงเท่านี้ คุณก็จะสามารถใช้งานตัวอักษรหรือตัวอักขระพิเศษได้แล ้วหล่ะครับ

เครดิต:Webmonster
ที่มา http://webmonster.sapaan.net/archives/90#comment-282

หรือจะลองดูตารางอันนี้ประกอบด้วยได้ครับ
Special Characters — Alt Keyboard Sequences
ที่มา http://tools.oratory.com/altcodes.html

Character	Sequence
backspace†	Alt 8
tab†	Alt 9
line break†	Alt 10
¤	Alt 15
¶	Alt 20
§	Alt 21
paste†	Alt 22
space†	Alt 32
!	Alt 33
"	Alt 34
#	Alt 35
$	Alt 36
%	Alt 37
&	Alt 38
'	Alt 39
(	Alt 40
)	Alt 41
*	Alt 42
+	Alt 43
,	Alt 44
-	Alt 45
.	Alt 46
/	Alt 47
0	Alt 48
1	Alt 49
2	Alt 50
3	Alt 51
4	Alt 52
5	Alt 53
6	Alt 54
7	Alt 55
8	Alt 56
9	Alt 57
:	Alt 58
;	Alt 59
<	Alt 60
=	Alt 61
>	Alt 62
?	Alt 63
@	Alt 64
A	Alt 65
B	Alt 66
C	Alt 67
D	Alt 68

Character	Sequence
E	Alt 69
F	Alt 70
G	Alt 71
H	Alt 72
I	Alt 73
J	Alt 74
K	Alt 75
L	Alt 76
M	Alt 77
N	Alt 78
O	Alt 79
P	Alt 80
Q	Alt 81
R	Alt 82
S	Alt 83
T	Alt 84
U	Alt 85
V	Alt 86
W	Alt 87
X	Alt 88
Y	Alt 89
Z	Alt 90
[	Alt 91
\	Alt 92
]	Alt 93
^	Alt 94
_	Alt 95
`	Alt 96
a	Alt 97
b	Alt 98
c	Alt 99
d	Alt 100
e	Alt 101
f	Alt 102
g	Alt 103
h	Alt 104
i	Alt 105
j	Alt 106
k	Alt 107
l	Alt 108
m	Alt 109
n	Alt 110
o	Alt 111
p	Alt 112

Character	Sequence
q	Alt 113
r	Alt 114
s	Alt 115
t	Alt 116
u	Alt 117
v	Alt 118
w	Alt 119
x	Alt 120
y	Alt 121
z	Alt 122
{	Alt 123
\|	Alt 124
}	Alt 125
~	Alt 126
	Alt 127
Ç	Alt 128
ü	Alt 129
é	Alt 130
â	Alt 131
ä	Alt 132
à	Alt 133
å	Alt 134
ç	Alt 135
ê	Alt 136
ë	Alt 137
è	Alt 138
ï	Alt 139
î	Alt 140
ì	Alt 141
æ	Alt 145
Æ	Alt 146
ô	Alt 147
ö	Alt 148
ò	Alt 149
û	Alt 150
ù	Alt 151
ÿ	Alt 152
¢	Alt 155
£	Alt 156
¥	Alt 157
P	Alt 158
ƒ	Alt 159
á	Alt 160
í	Alt 161

Character	Sequence
ó	Alt 162
ú	Alt 163
ñ	Alt 164
Ñ	Alt 165
	Alt 166‡
	Alt 167‡
¿	Alt 168
¬	Alt 170
½	Alt 171
¼	Alt 172
¡	Alt 173
«	Alt 174
»	Alt 175
¦	Alt 179
ß	Alt 225
µ	Alt 230
±	Alt 241
°	Alt 248
•	Alt 249
·	Alt 250
²	Alt 253
€	Alt 0128
„	Alt 0132
…	Alt 0133
†	Alt 0134
‡	Alt 0135
ˆ	Alt 0136
‰	Alt 0137
Š	Alt 0138
‹	Alt 0139
Œ	Alt 0140
‘	Alt 0145
’	Alt 0146
“	Alt 0147
”	Alt 0148
–	Alt 0150
—	Alt 0151
˜	Alt 0152
™	Alt 0153
š	Alt 0154
›	Alt 0155
œ	Alt 0156
Ÿ	Alt 0159
¨	Alt 0168

Character	Sequence
©	Alt 0169
®	Alt 0174
¯	Alt 0175
³	Alt 0179
´	Alt 0180
¸	Alt 0184
¹	Alt 0185
¾	Alt 0190
À	Alt 0192
Á	Alt 0193
Â	Alt 0194
Ã	Alt 0195
Ä	Alt 0196
Å	Alt 0197
È	Alt 0200
É	Alt 0201
Ê	Alt 0202
Ë	Alt 0203
Ì	Alt 0204
Í	Alt 0205
Î	Alt 0206
Ï	Alt 0207
Ð	Alt 0208
Ò	Alt 0210
Ó	Alt 0211
Ô	Alt 0212
Õ	Alt 0213
Ö	Alt 0214
×	Alt 0215
Ø	Alt 0216
Ù	Alt 0217
Ú	Alt 0218
Û	Alt 0219
Ü	Alt 0220
Ý	Alt 0221
Þ	Alt 0222
ã	Alt 0227
ð	Alt 0240
õ	Alt 0245
÷	Alt 0247
ø	Alt 0248
ü	Alt 0252
ý	Alt 0253
þ	Alt 0254

เอามาจาก: http://www.thaigaming.com/articles/49378.htm

สิ่งที่น่าทึ่งในชีวิต

๑๐/๒๘/๒๕๕๒

Install Slackware Hardware RAID SCSI CDROM

Slackware 9.1 & 10.1 on software raid-1

Slackware 9.1 & 10.1 on software raid-1 : HOWTO

HOWTO!

Updates

Disclaimer

Slackware Creating The Boot Disk

Slackware 9.1 & 10.1 on software raid-1

Slackware 9.1 & 10.1 on software raid-1 : HOWTO

HOWTO!

Updates

Disclaimer

INSTALLING SLACKWARE LINUX version 8.1 WITH ROOT PARTITION ON A SOFTWARE RAID level 0 DEVICE.

tune2fs

๑๐/๒๑/๒๕๕๒

เรียกใช้ตัวอักษรหรือตัวอักขระพิเศษด้วยปุ่ม Alt