mirror of https://github.com/tLDP/LDP
Updated docs
This commit is contained in:
gleblanc
parent
a8000c0f0c
commit
0eefd2dd9a
|
|
@ -1,6 +1,6 @@
|
|||
<!doctype linuxdoc system>
|
||||
|
||||
<!-- LinuxDoc file was created by hand by <Dan Kuykendall> Wed April 19 -->
|
||||
<!-- LinuxDoc file was created by hand by <Dan Kuykendall> Wed April 23 -->
|
||||
<article>
|
||||
<title>
|
||||
Qmail VMailMgr and Courier-Imap HOWTO
|
||||
|
|
@ -9,14 +9,13 @@
|
|||
Dan Kuykendall <dan@kuykendall.org>
|
||||
</author>
|
||||
<date>
|
||||
v1.2, 19 April 2000
|
||||
v1.4, 23 April 2000
|
||||
</date>
|
||||
<abstract>
|
||||
This document is about building a mail server that will
|
||||
support virtual domain hosting and provide smtp, pop3 and imap services,
|
||||
using a powerful alternative to sendmail.
|
||||
</abstract>
|
||||
|
||||
<toc>
|
||||
<sect>Introduction<label id="Introduction" >
|
||||
<p>
|
||||
|
|
@ -134,8 +133,8 @@
|
|||
get your email system up and running.
|
||||
Combinations that work for me are:
|
||||
<itemize>
|
||||
<item> RedHat 6.2, Linux 2.2.14, Qmail 1.03+patches-12, VMailMgr 0.96.5, Courier-imap 0.31
|
||||
<item> Mandrake 7.0, Linux 2.2.13, Qmail 1.03+patches-12, VMailMgr 0.96.5, Courier-imap 0.31
|
||||
<item> RedHat 6.2, Linux 2.2.14, Qmail 1.03+patches-12, VMailMgr 0.96.6, Courier-imap 0.31
|
||||
<item> Mandrake 7.0, Linux 2.2.13, Qmail 1.03+patches-12, VMailMgr 0.96.6, Courier-imap 0.31
|
||||
</itemize>
|
||||
|
||||
<sect1>History<label id="History" >
|
||||
|
|
@ -145,7 +144,7 @@
|
|||
</p>
|
||||
<sect1>New versions
|
||||
<p>
|
||||
The newest version of this can be found on my homepage <url url="http://www.clearrivertech.com/linux"> in its SGML source.
|
||||
The newest version of this can be found on my homepage <url url="http://www.clearrivertech.com/linux/HOWTO"> as SGML source, as HTML and as TEXT.
|
||||
Other versions may be found in different formats at the LDP homepage <url url="http://www.linuxdoc.org/">.
|
||||
</p>
|
||||
<sect1>Comments
|
||||
|
|
@ -195,34 +194,26 @@
|
|||
<item>Built proper SGML version.
|
||||
</itemize>
|
||||
</p>
|
||||
<sect1>Copyrights and Trademarks
|
||||
<p>
|
||||
(c) 2000-2001 Dan Kuykendall
|
||||
</p>
|
||||
<p>
|
||||
This manual may be reproduced in whole or in part, without fee, subject
|
||||
to the following restrictions:
|
||||
v1.4 (April 23, 2000)
|
||||
</p>
|
||||
<p>
|
||||
<itemize>
|
||||
<item>The copyright notice above and this permission notice must be preserved
|
||||
complete on all complete or partial copies
|
||||
<item>Any translation or derived work must be approved by the author in writing
|
||||
before distribution.
|
||||
<item>If you distribute this work in part, instructions for obtaining the complete
|
||||
version of this manual must be included, and a means for obtaining a complete
|
||||
version provided.
|
||||
<item>Small portions may be reproduced as illustrations for reviews or quotes
|
||||
in other works without this permission notice if proper citation is given.
|
||||
<item>Updated the Courier-IMAP setup information for new VMailMgr version.
|
||||
<item>Switched the license to the GNU FDL.
|
||||
<item>Other minor additions and corrections.
|
||||
</itemize>
|
||||
</p>
|
||||
<sect1>Copyrights and Trademarks
|
||||
<p>
|
||||
Exceptions to these rules may be granted for academic purposes: Write to
|
||||
the author and ask. These restrictions are here to protect us as authors, not
|
||||
to restrict you as learners and educators. Any source code (aside from the
|
||||
SGML this document was written in) in this document is placed under the GNU
|
||||
General Public License, available via anonymous FTP from
|
||||
<url url="ftp://ftp.gnu.org/GNU/COPYING" name="the GNU archive">.
|
||||
Copyright (c) Dan Kuykendall.
|
||||
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
|
||||
</p>
|
||||
<p>
|
||||
A copy of the license is available at
|
||||
<url url="http://www.gnu.org/copyleft/fdl.txt" name="GNU Free Documentation License">.
|
||||
</p>
|
||||
<sect1>Acknowledgements and Thanks
|
||||
<p>
|
||||
|
|
@ -252,7 +243,7 @@
|
|||
<item> daemontools-0.70-1.src.rpm - <url url="http://em.ca/~bruceg/rpms/daemontools/">
|
||||
<item> supervise-scripts-2.4-1.src.rpm - <url url="http://em.ca/~bruceg/supervise-scripts/">
|
||||
<item> qmail-1.03+patches-12.src.rpm - <url url="http://em.ca/~bruceg/qmail+patches/">
|
||||
<item> vmailmgr-0.96.5-1.src.rpm - <url url="http://em.ca/~bruceg/vmailmgr/">
|
||||
<item> vmailmgr-0.96.6-1.src.rpm - <url url="http://em.ca/~bruceg/vmailmgr/">
|
||||
<item> courier-imap-0.31.tar.gz - <url url="http://www.inter7.com/courierimap/">
|
||||
</itemize>
|
||||
For Courier-imap you must build the source rpm from the tar
|
||||
|
|
@ -273,7 +264,7 @@
|
|||
<item> daemontools-0.70-1.i386.rpm - <url url="http://em.ca/~bruceg/rpms/daemontools/">
|
||||
<item> supervise-scripts-2.4-1.i386.rpm - <url url="http://em.ca/~bruceg/supervise-scripts/">
|
||||
<item> qmail-1.03+patches-12.src.rpm - <url url="http://em.ca/~bruceg/qmail+patches/">
|
||||
<item> vmailmgr-0.96.5-1.src.rpm - <url url="http://em.ca/~bruceg/vmailmgr/">
|
||||
<item> vmailmgr-0.96.6-1.src.rpm - <url url="http://em.ca/~bruceg/vmailmgr/">
|
||||
<item> courier-imap-0.31.tar.gz - <url url="http://www.inter7.com/courierimap/">
|
||||
</itemize>
|
||||
For Courier-imap you must build the binary rpm from the tar
|
||||
|
|
@ -287,7 +278,7 @@
|
|||
<item> daemontools-0.70.tar.gz - <url url="http://cr.yp.to/daemontools/daemontools-0.70.tar.gz">
|
||||
<item> supervise-scripts-2.4.tar.gz - <url url="http://em.ca/~bruceg/supervise-scripts/">
|
||||
<item> qmail-1.03.tar.gz - <url url="http://cr.yp.to/software/qmail-1.03.tar.gz"> (*)
|
||||
<item> vmailmgr-0.96.5.tar.gz - <url url="http://em.ca/~bruceg/vmailmgr/">
|
||||
<item> vmailmgr-0.96.6.tar.gz - <url url="http://em.ca/~bruceg/vmailmgr/">
|
||||
<item> courier-imap-0.31.tar.gz - <url url="http://www.inter7.com/courierimap/">
|
||||
</itemize>
|
||||
|
||||
|
|
@ -478,76 +469,39 @@
|
|||
make install
|
||||
</code>
|
||||
</p>
|
||||
|
||||
<sect1>Install VMailMgr
|
||||
<p>
|
||||
At the time of this writing Bruce had not released a binary version of VMailMgr
|
||||
that included Courier-imap support. This means until the next version of
|
||||
VMailMgr is release, you will be required to build the RPMS yourself.
|
||||
|
||||
<sect2>Install with RPMS
|
||||
<sect3>Compiling SRC.RPM's
|
||||
<p>
|
||||
Now for the fun part, since VMailMgr needs the courier-imap sources during
|
||||
its compile to build the auth lib, I had to take the following steps.
|
||||
(please edit to suit your environment)
|
||||
|
||||
1) copy the courier-imap-0.31.tar.gz to non-root users home dir
|
||||
|
||||
<tt>cp courier-imap-0.31.tar.gz ~user1/ </tt>
|
||||
|
||||
2) with my user account: untar, run config and make
|
||||
<verb>
|
||||
su user1
|
||||
cd ~/
|
||||
tar zxf courier-imap-0.31.tar.gz
|
||||
cd courier-imap-0.31
|
||||
./configure
|
||||
make
|
||||
</verb>
|
||||
|
||||
3) Install the VMailMgr sources and modify the spec file to support courier-imap
|
||||
<verb>
|
||||
rpm -ivh VMailMgr-0.96.5-1.src.rpm
|
||||
edit /usr/src/redhat/SPECS/VMailMgr-0.96.5.spec
|
||||
on the ./configure line (line 49) add the following text to the end
|
||||
--with-courier-imap=/home/user1/courier-imap-0.31/
|
||||
</verb>
|
||||
|
||||
4) Compile VMailMgr based on the modified spec file
|
||||
<tt>rpm -bb /usr/src/redhat/SPECS/VMailMgr-0.96.5.spec</tt>
|
||||
|
||||
* I will mention again, that I have built the binaries, and if you email me *
|
||||
* at dan@kuykendall.org, I will email them back to you. *
|
||||
|
||||
Simply run the following command
|
||||
<verb>rpm --rebuild <package.src.rpm></verb>
|
||||
-Example-
|
||||
<code>
|
||||
rpm --rebuild vmailmgr-0.96.6-1.src.rpm
|
||||
</code>
|
||||
</p>
|
||||
<sect3>Installing RPM's
|
||||
<p>
|
||||
After compiling the source rpms, the binaries will be located
|
||||
If you compiled the source rpm, the binaries will be located
|
||||
in <tt>/usr/src/redhat/RPMS/i386/</tt> or something similar.
|
||||
|
||||
Simply run the following command for each package
|
||||
<verb>
|
||||
rpm -ivh <location>/<package.i386.rpm>
|
||||
</verb>
|
||||
<verb>rpm -ivh <location>/<package.i386.rpm></verb>
|
||||
|
||||
-Example-
|
||||
<code>
|
||||
rpm -ivh /usr/src/redhat/RPMS/i386/VMailMgr-0.96.5-1.i386.rpm
|
||||
rpm -ivh /usr/src/redhat/RPMS/i386/VMailMgr-daemon-0.96.5-1.i386.rpm
|
||||
rpm -ivh /usr/src/redhat/RPMS/i386/vmailmgr-0.96.6-1.i386.rpm
|
||||
rpm -ivh /usr/src/redhat/RPMS/i386/VMailMgr-daemon-0.96.6-1.i386.rpm
|
||||
</code>
|
||||
|
||||
</p>
|
||||
<sect2>Install with source
|
||||
<p>
|
||||
Since VMailMgr needs the courier-imap sources during its compile to build the
|
||||
auth lib, and since your using the compiling source, you will need to have kept
|
||||
your courier-imap sources from where you compiled it. If you deleted them, redo
|
||||
the steps up to the make command.
|
||||
<p>
|
||||
Run the following command
|
||||
Run the following commands
|
||||
<verb>
|
||||
(As non-root user)
|
||||
tar zxf <package.tar.gz>
|
||||
cd <newly created dir>
|
||||
./configure --with-courier-imap=<courier-imap sources>
|
||||
./configure
|
||||
make
|
||||
(As root)
|
||||
make install
|
||||
|
|
@ -555,12 +509,12 @@
|
|||
-Example-
|
||||
<code>
|
||||
(As non-root user)
|
||||
tar zxf vmailmgr-0.96.5.tar.gz
|
||||
cd vmailmgr-0.96.5
|
||||
./configure --with-courier-imap=/home/user1/courier-imap-0.31/
|
||||
tar zxf vmailmgr-0.96.6.tar.gz
|
||||
cd vmailmgr-0.96.6
|
||||
./configure
|
||||
make
|
||||
(As root)
|
||||
make install
|
||||
make setup check or make install
|
||||
</code>
|
||||
That should do it.
|
||||
</p>
|
||||
|
|
|
|||
|
|
@ -1,6 +1,12 @@
|
|||
<!doctype linuxdoc system>
|
||||
|
||||
<!--
|
||||
v1.12 add pointer to BootRootRaidLilominihowot
|
||||
and obsolete message
|
||||
v1.11 add RedHat info
|
||||
v1.10 update raid resource html links
|
||||
v1.09 minor typographic additions
|
||||
v1.08 add warning about rc.S 'ro' test
|
||||
v1.07 add generic 'linuxrc' and raid5 support
|
||||
v1.06 add 'rm /etc/mtab' to fail over rescue boot
|
||||
in 'linuxrc'
|
||||
|
|
@ -14,12 +20,20 @@
|
|||
<title>Root RAID HOWTO cookbook
|
||||
<author>Michael A. Robinton, <url url="mailto:michael@bzs.org"
|
||||
name="michael@bzs.org">
|
||||
<date>v1.07, 25 March 1998
|
||||
<date>v1.12, May 2, 2000
|
||||
<abstract>
|
||||
This document provides a cookbook for creating a root mounted raid
|
||||
filesystem and companion fallback rescue system using linux initrd. There
|
||||
are complete step-by-step instruction for both raid1 and raid5 md0 devices.
|
||||
Each step is accompanied by an explanation of it's purpose.
|
||||
This document only applys to the <bf/OLD/ raidtools, versions 0.50 and
|
||||
under. The workarounds and solutions addressed in this write up have largely
|
||||
been made obsolete by the vast improvment in the 0.90 raidtools and
|
||||
accompanying kernel patch to the 2.0.37, 2.2x and 2.3x series kernels. You
|
||||
may find the detailed descriptions useful, particularly if you plan to run
|
||||
root raid or use initrd. Read on for a reference to set up of Boot Root Raid
|
||||
using conventional LILO and accompanying initrd working scripts. What
|
||||
follows is the description of the now <bf/OBSOLETE Root RAID HOWTO/.
|
||||
This document was originally written to provide a cookbook for creating a
|
||||
root mounted raid filesystem and companion fallback rescue system using
|
||||
linux initrd. There are complete step-by-step instruction for both raid1 and
|
||||
raid5 md0 devices. Each step is accompanied by an explanation of it's purpose.
|
||||
Included with this revision is a generic <bf/linuxrc/ initrd file which may
|
||||
be configured with a single three line <ref id="raidboot-conf"
|
||||
name="/etc/raidboot.conf"> file for
|
||||
|
|
@ -39,19 +53,36 @@ of the information necessary to become familiar with linux raid is listed
|
|||
here directly or by reference, please read it before send e-mail questions.
|
||||
|
||||
<sect1>Where to get Up-to-date copies of this document.
|
||||
|
||||
<p>
|
||||
Root-RAID-HOWTO
|
||||
Click here to browse the <url
|
||||
url="ftp://ftp.bizsystems.com/pub/raid/Root-RAID-HOWTO.html"
|
||||
name="author's latest version"> of
|
||||
this document. Corrections and suggestions welcome!
|
||||
<p>
|
||||
Root-RAID-HOWTO -- OBSOLETE
|
||||
<p>
|
||||
Available in LaTeX (for DVI and PostScript), plain text, and HTML.
|
||||
<quote> <url url="http://sunsite.unc.edu/mdw/HOWTO/"
|
||||
name="sunsite.unc.edu/mdw/HOWTO/">
|
||||
<quote> <url url="http://www.linuxdoc.org/HOWTO/Root-RAID-HOWTO.html"
|
||||
name="http://www.linuxdoc.org/HOWTO/Root-RAID-HOWTO.html">
|
||||
</quote>
|
||||
Available in SGML and HTML.
|
||||
<quote> <url url="ftp://ftp.bizsystems.com/pub/raid/"
|
||||
name="ftp.bizsystems.com/pub/raid/">
|
||||
<quote> <url url="ftp://ftp.bizsystems.net/pub/raid/"
|
||||
name="ftp.bizsystems.net/pub/raid/">
|
||||
</quote>
|
||||
|
||||
<sect1>More up-to-date Boot Root Raid with LILO minihowto
|
||||
|
||||
<p>
|
||||
Available in LaTeX (for DVI and PostScript), plain text, and HTML.
|
||||
<quote> <url url="http://www.linuxdoc.org/HOWTO/Root-RAID-HOWTO.html"
|
||||
name="http://www.linuxdoc.org/HOWTO/Root-RAID-HOWTO.html">
|
||||
</quote>
|
||||
Available in SGML and HTML.
|
||||
<quote> <url url="ftp://ftp.bizsystems.net/pub/raid/"
|
||||
name="ftp.bizsystems.net/pub/raid/">
|
||||
</quote>
|
||||
|
||||
|
||||
<sect1>Bugs
|
||||
<p>
|
||||
As of this writing, the problem of stopping a root mounted RAID device has
|
||||
|
|
@ -109,6 +140,10 @@ url="mailto:bochal@apollo.karlov.mff.cuni.cz"> <it> for implementing the
|
|||
re-boot 'workaround' that allows
|
||||
</it> <bf>root-mounted-raid</bf><it> to
|
||||
work in a production environment.</it>
|
||||
<item><url url="mailto:kwrohrer@ce.mediaone.net" name="Keith W."> <it> for
|
||||
his explaination of setting up root raid with </it><bf/ RedHat/.
|
||||
|
||||
|
||||
<p>
|
||||
<item>and many others who contributed to this work in one way or another.
|
||||
</itemize>
|
||||
|
|
@ -220,8 +255,9 @@ You may also wish to review:
|
|||
|
||||
<p>
|
||||
<itemize>
|
||||
<item><url url="http://sunsite.unc.edu/mdw/HOWTO/mini/Software-RAID"
|
||||
name="sunsite.unc.edu/mdw/HOWTO/mini/Software-RAID">
|
||||
<item><url
|
||||
url="http://http://www.linas.org/linux/Software-RAID/Software-RAID.html"
|
||||
name="www.linas.org/linux/Software-RAID/Software-RAID.html">
|
||||
<item><url url="http://www.ssc.com/lg/issue17/raid.html"
|
||||
name="www.ssc.com/lg/issue17/raid.html">
|
||||
<item><url url="http://linas.org/linux/raid.html"
|
||||
|
|
@ -250,6 +286,10 @@ Mailing lists can be joined at:
|
|||
|
||||
<sect>Quick Start for ROOT RAID
|
||||
<p>
|
||||
If you use <bf/RedHat/, see the <ref id="RedHat" name="Howto set up RedHat">
|
||||
section in Appendix H. I have not tried this. If you use it successfully,
|
||||
please let me know so I can update this document.
|
||||
<p>
|
||||
If you don't want to try and build and debug the rescue system, you can get
|
||||
a generic one created from Slackware-3.4 from:
|
||||
<quote><url url="ftp://ftp.bizsystems.com/pub/raid/"
|
||||
|
|
@ -283,6 +323,10 @@ copy these files
|
|||
{or as appropriate for your system}
|
||||
cp -a /lib/modules/* mnt/lib/modules
|
||||
</verb>
|
||||
Some Linux distributions include a test for the <bf>ro/rw</bf> status of the
|
||||
root file system. The <bf/rc startup/ files need to
|
||||
have this test removed for the initrd rescue system. See the instructions in
|
||||
the section on <ref id="corrections" name="Correctons for Rescue System">.
|
||||
</itemize>
|
||||
Correct the entries in <bf/fstab/ to show <bf>/dev/md0</bf> as the root
|
||||
device. Make sure that the partition(s) you use for booting is included in
|
||||
|
|
@ -300,7 +344,7 @@ raidboot.conf
|
|||
# comments may only be placed 'after' the three
|
||||
# configuration lines.
|
||||
#
|
||||
# This is 'raidboot.conf'
|
||||
# This is '/etc/raidboot.conf'
|
||||
#
|
||||
# line one, the partition(s) containing the 'initrd' raid-rescue system
|
||||
# It is not necessary to boot from these partitions, however,
|
||||
|
|
@ -346,7 +390,7 @@ raid array.
|
|||
|
||||
|
||||
|
||||
<sect>initrd‐ Cookbook for root mounted RAID
|
||||
<sect><it>initrd</it> Cookbook for root mounted RAID
|
||||
|
||||
<p>
|
||||
This is the procedure to make an 'initrd' ramdisk with rescue tools for raid.
|
||||
|
|
@ -400,7 +444,7 @@ This installation process gives me a 'bare' system
|
|||
/dev/md*</verb>
|
||||
<p>
|
||||
from my current system to customize it for the particular kernel
|
||||
and machine that it is/will-be running on.
|
||||
and machine that it is/will-be running on.
|
||||
<p>
|
||||
This makes the boot/rescue system the same system that is running
|
||||
on the root mounted raid device, just skinnyed down a bit, while
|
||||
|
|
@ -736,7 +780,11 @@ The next 2 commands creates some warning messages, ignore them.
|
|||
mkdir mnt/lib/modules
|
||||
cp -a /lib/modules/2.x.x mnt/lib/modules <--- your current 2.x.x
|
||||
</verb>
|
||||
Edit the following files to correct them for your rescue system.
|
||||
<sect2>Corrections for the Rescue System <label id="corrections">
|
||||
<p>
|
||||
Edit the following files to correct them for your rescue system. Some file
|
||||
names listed below are Slackware specific but have equivalents in other
|
||||
distributions.
|
||||
<verb>
|
||||
cd mnt
|
||||
|
||||
|
|
@ -1127,7 +1175,7 @@ My dos root system contains a small editor among the utilities so I can modify
|
|||
the boot parameters of loadlin if necessary, allowing me to reboot the
|
||||
linux system on my swap disk while testing.
|
||||
<p>
|
||||
The dos system contains this tree for linux
|
||||
The dos system contains this tree for linux"
|
||||
<verb>
|
||||
c:\raidboot.bat
|
||||
c:\raidboot\loadlin.exe
|
||||
|
|
@ -2328,4 +2376,68 @@ from the primary system that are transferred to the
|
|||
<item><bf/raidstat.ro/ created at each shutdown by the shutdown rc file,
|
||||
saving the exit status of the raid array.
|
||||
</itemize>
|
||||
|
||||
<!-- RedHat Stuff -->
|
||||
<sect>Appendix H. Setting up ROOT RAID on RedHat<label id="RedHat">
|
||||
|
||||
<p>
|
||||
From the <url url="mailto:linux-raid@vger.rutgers.edu"
|
||||
name="linux-raid@vger.rutgers.edu"> mail list.
|
||||
|
||||
<verb>
|
||||
! Has anyone figured out how to do root-mounted RAID (as per
|
||||
! the Root-RAID HOWTO) using RedHat? The problem is that there
|
||||
! is no equivalent of Slackware's setup to install the root
|
||||
! filesystem to the RAID device. All RedHat installs have to
|
||||
! run from the install floppy, which makes it almost
|
||||
! impossible to get at the md devices and utilities during the
|
||||
! install.
|
||||
!
|
||||
! I think it's much easier to go out of the distribution and do it by
|
||||
! hand!!
|
||||
|
||||
Assuming you have enough RAM (or a spare hard disk), install a minimal
|
||||
system onto what will be your swap space (or onto your spare hard disk)
|
||||
and/or /boot. Now do your mkraid, your mke2fs, mdrun, and mount. Next, do:
|
||||
|
||||
tar clf - / | tar xpfC - /mnt/raidwasmountedhere
|
||||
|
||||
(you may want a "v" in the second tar's flags)
|
||||
Once this is done, you can set up lilo (or whatever) so that the new
|
||||
raid partition is root. Then go in with RPM and/or glint (I hate
|
||||
glint's behavior in the face of failed dependencies, which was fixed
|
||||
but they broke it again for RH5.0 plus you can go back and forth
|
||||
forever between an old and a new version of a package without
|
||||
realizing the other version is installed) and install what you
|
||||
really wanted.
|
||||
|
||||
All this assuming you couldn't sneak in at some point in the install
|
||||
and do your mkraid then at the VC with the shell prompt...
|
||||
|
||||
! I'm building a server at the moment and I think it would be tidier
|
||||
! and less likely to cause problems in the future if I start with
|
||||
! glibc2, rather than move to it later.
|
||||
!
|
||||
! Me too.
|
||||
!
|
||||
! The reason I'd like to be able to use RedHat is that they
|
||||
! are the only major distribution that I know of with a
|
||||
! glibc2-based release.
|
||||
!
|
||||
! Debian works fine with me. There isn't a CD yet, but you can grab the
|
||||
! distribution by ftp.
|
||||
|
||||
I avoided root-raid like the plague, largely because initrd is an
|
||||
extra, very fragile step (having to rdev, and having lilo depend on
|
||||
the bios' ID number to find the kernel's partition, are bad enough!).
|
||||
However, Red Hat does have a nice mkinitrd script, needed since they
|
||||
left all their SCSI drivers modular. Hack that to include your
|
||||
raid utils, make sure your mdadd -ar is in the right spot in
|
||||
/etc/rc.d/rc.sysinit (before any fscking) and make sure mdstop -a is
|
||||
in /etc/rc.d/init.d/halt after the RO-remount of /, and go for it!
|
||||
</verb>
|
||||
<quote>
|
||||
Keith <url url="mailto:kwrohrer@enteract.com"
|
||||
name="kwrohrer@enteract.com">
|
||||
</quote>
|
||||
</article>
|
||||
|
|
|
|||
Loading…
Reference in New Issue