I'm also curious as to why such old docs are still included with the
raidtool distro. They're rather pointless since nothing seems to take
that type of mold any longer. Like what said below, a few emails from
this list pretty much makes the old documentation rather useless.
Just my thoughts. I'll go away now.
-jeremy
>
> Yet another victim of the lagging documentation! Ingo's messages of 4 Sept
> on "HOW TO use the newest RAID stuff..." and 8 Sept on "Re: kernel 2.0.35 &
> raid0145-19980905-2.0.35-c" are more useful guides to the latest RAID scheme
> than the documentation. Maybe they should be included (with a couple of
> modifications to take account of the 0.90 changes) in the raidtools package
> until the documentation catches up? Can I also suggest that files like
> HOWTO, README and Quickstart.RAID which are probably doing more harm than
> good in their current condition either be removed from raidtools or have a
> warning added at the top of each file stating that the information is
> out-of-date.
>
> Basically, there was nothing wrong with this compilation. raidadd, raidrun
> and ckraid are defunct (functions now performed by the kernel, mkraid or
> raidstart). raidstop, raidhotadd and raidhotremove, which are now the only
> other tools besides mkraid and raidstart, are all symlinks to raidstart
> (links created when you do make install). So mkraid and raidstart are the
> only executables you need in this version of raidtools.
>
> Briefly, to summarize the steps you need to take:
>
> In raidtools-0.90: ./autogen.sh; make; make install; make install_dev
>
> Create /etc/raidtab (you can base this on raidtab.sample in raidtools-0.90)
>
> mkraid -f /dev/md* (to initialize the RAID devices. Do each md device
> separately, don't type md* literally. This destroys all data on constituent
> partitions.)
>
> fdisk each disk with partitions which will be included in a RAID device, and
> set those partitions to type 0xfe
>
> Use tar to copy whichever bits of the existing filesystem you want to move
> to the RAID devices (I assume you want to do this as you were looking at
> Root-RAID)
>
> Edit /etc/fstab (or RAID-root/mountpoint/etc/fstab if you are switching to
> root-RAID) to indicate mountpoints of RAID devices (remember the kernel
> cannot be on a RAID0/4/5 partition, so you will probably want a small
> unRAIDed /boot partition for your kernel images)
>
> If you are switching to root-RAID, edit /etc/lilo.conf so that root points
> to the RAID device, then run lilo.
>
> Reboot. You should be in business.
>
> Forget about your problems with the earlier versions of raidtools. Seems
> like you shouldn't have a problem using the latest version, and as the patch
> and raidtools versions are intended to go hand in hand, you don't want to be
> trying to build earlier raidtools with the latest patch anyway.
>
> > BTW, do I still need "Gadi's raid stop patch" as described in
> > ROOT-RAID-HOWTO?
>
> No, thank God. The kernel now handles stopping the md devices at shutdown.
> The advice in the ROOT-RAID-HOWTO is almost completely out-of-date. RAID
> (root or otherwise) is much simpler now, thanks to Ingo's work.
>
> > The other thing is that I already installed linuxthreads. I added
> > flags for gcc
> >
> > -D_REENTRANT -lpthread
> >
> > in kernel Makefile. The following message shows up repeatedly:
> >
> > gcc:-lpthread: linker input file unused since linking not done
> >
> > Will this create any trouble?
>
> Don't know much about linuxthreads, but I believe if you are using a
> glibc-based distribution, you don't need linuxthreads as threads are already
> built into glibc.
>
> Cheers,
>
>
> Bruno Prior [EMAIL PROTECTED]
>
http://www.xxedgexx.com | [EMAIL PROTECTED]
| pgp available from:
| http://www.xxedgexx.com/pgp.html
