All of lore.kernel.org
 help / color / mirror / Atom feed
From: "George  Iosif" <giosif@ase.ro>
To: john.lange@bighostbox.com
Cc: linux-raid@vger.kernel.org
Subject: Re: Please review: Slackware RAID How-To
Date: Fri, 14 May 2004 09:21:05 +0300	[thread overview]
Message-ID: <s0a48f9e.019@nsa.ase.ro> (raw)

OK.
Glad to be of some help.
If I get any more (hopefully good) ideas, I'll post them in this list.


George Iosif

>>> John Lange <john.lange@bighostbox.com> 05/14/04 6:46 AM >>>
Thank you George.

I am reviewing the LILO section. Despite the what I've read I could not
get my RAID array to boot from any drive except the primary drive so I'm
going to have to do more research to figure out why this is a problem.

Of course, thanks for the grammar fixes as well.

I'll post to the list again when I've sorted out the lilo issue and made
revisions to the how-to.

Regards,

-- 
John Lange
BigHostBox.com
(204) 885 0872

On Thu, 2004-05-13 at 04:46, George Iosif wrote:
> I've read the documentation you wrote and I believe it's quite good.
> I've tried to find possible improvements, but came out with some lame
> ones: 2 typos to correct (1-chapter 2.1, first phrase, delete the
"are"
> verb; 2-chapter 5, first phrase, replace "thing" with "think") and a
> possible reccomendation for a more detailed LILO setup (if it requires
> some special parameters).
> 
> Thank you for your efforts to make Linux a more understandable world !
> 
> Yours,
> 
> George Iosif
> 
> >>> John Lange <john.lange@bighostbox.com> 05/11/04 6:42 PM >>>
> As mentioned, I have created a Slackware RAID How-To and an initial
> draft is located here:
> 
> http://www.langefamily.ca/howto/SlackwareRaidHowTo.html
> 
> This document covers getting Slackware installed on a system with
RAID.
> This technique does not require a temporary hard drive or anything
other
> than a Slackware boot CD.
> 
> I am fairly new to linux software RAID so I really hope some more
> experienced people will take some time to read it and give me some
> feedback. I would hate to have some glaring errors inflicted on
others!
> 
> Thanks.




             reply	other threads:[~2004-05-14  6:21 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-14  6:21 George  Iosif [this message]
     [not found] <s0a48f9e.018@nsa.ase.ro>
2004-05-14  6:47 ` Please review: Slackware RAID How-To John Lange
  -- strict thread matches above, loose matches on Subject: below --
2004-05-13  9:46 George  Iosif
2004-05-11 15:42 John Lange
2004-05-11 23:51 ` Ninti Systems
2004-05-16  5:43 ` Ninti Systems
2004-05-16  6:40 ` Ninti Systems
2004-05-17  2:36 ` Ninti Systems
2004-05-17  4:51   ` Guy
2004-05-17  9:02     ` Ninti Systems
2004-05-20  1:42     ` John Lange
2004-05-20  2:06       ` Ninti Systems
2004-05-20  3:27         ` Guy
2004-05-20  3:33         ` John Lange
2004-05-20  5:02           ` Guy
2004-05-20  7:58             ` John Lange
2004-05-20 13:37               ` Guy
2004-05-21  2:25               ` Ninti Systems
2004-05-21  2:55                 ` Guy
2004-05-21  2:47               ` Ninti Systems
2004-05-20  3:11       ` Guy
2004-05-20  4:35         ` Guy

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=s0a48f9e.019@nsa.ase.ro \
    --to=giosif@ase.ro \
    --cc=john.lange@bighostbox.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.