From: Ninti Systems <office@ninti.com.au>
To: Guy <bugzilla@watkins-home.com>
Cc: RAID Linux <linux-raid@vger.kernel.org>
Subject: RE: /boot RAID1
Date: 31 Mar 2004 12:55:37 +0930 [thread overview]
Message-ID: <1080703536.10119.35.camel@localhost> (raw)
In-Reply-To: <200403310306.i2V36lW16729@dns1.watkins-home.com>
Yes, I've used RedHat for a few years and still like RH9.0 as a desktop
machine. I could set RAID up easily on RedHat but I never really
understood anything much about it, and especially how to manage, tweak,
fix or monitor it later on.
I've tried several distros out as the basis of a server project I'm
working on and have found Slackware 9.1 to be the best all-round
solution in terms of speed, stability and *overall* simplicity.
I'm comfortable on the command line (the server has no GUI) and am
actually keen to learn how to use the command line tools. When I get the
process right, I'll simply script it as much as possible.
:-)
On Wed, 2004-03-31 at 12:36, Guy wrote:
> I can't answer your question, but...
>
> RedHat 9.0 makes it real easy to configure RAID during the install.
> You can also configure LVM during the install if you want.
> So, no need to do these post-install things you now need to do.
> I am using RedHat 9.0 myself.
>
> I bet RedHat's Fedora is as easy.
>
> Guy
>
> -----Original Message-----
> From: linux-raid-owner@vger.kernel.org
> [mailto:linux-raid-owner@vger.kernel.org] On Behalf Of Ninti Systems
> Sent: Tuesday, March 30, 2004 9:34 PM
> To: RAID Linux
> Subject: /boot RAID1
>
> I've set up everything to switch my fresh Slackware 9.1 install on
> /dev/hda over to RAID1 devices set up on /dev/hda (currently 'missing')
> and /dev/hdc.
>
> Before I switch, I need to check one thing which isn't clear to me from
> the Software RAID HowTo:
>
> I currently have a separate partition (/dev/hda1) for /boot. Can this
> partition also be switched over to RAID1 (on /dev/md1) or must the /boot
> partition always be on a non-RAID device?
>
> RAID1 support appears to compiled into the Slackware bare.i kernel I am
> using. Autodetection on boot is working.
>
> Thanks
> Mick
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
--------------------------------------
Ninti Systems: Smart IT Solutions
Michael Hall
Mobile: 0429 095 392
Ph/Fax: 08 8953 1442
Email: office at ninti dot com dot au
Web: http://ninti.com.au
--------------------------------------
next parent reply other threads:[~2004-03-31 3:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200403310306.i2V36lW16729@dns1.watkins-home.com>
2004-03-31 3:25 ` Ninti Systems [this message]
2004-03-31 2:34 /boot RAID1 Ninti Systems
2004-03-31 3:42 ` Daniel Pittman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1080703536.10119.35.camel@localhost \
--to=office@ninti.com.au \
--cc=bugzilla@watkins-home.com \
--cc=linux-raid@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).