From: "Andrew Kinney" <andykinney@advantagecom.net>
To: Ryan <ryan@nmt.edu>
Cc: linux-scsi@vger.kernel.org
Subject: Re: aacraid on Dell PowerEdge 1800
Date: Fri, 11 Mar 2005 10:24:42 -0800 [thread overview]
Message-ID: <423171EA.368.2C2CE275@localhost> (raw)
In-Reply-To: <20050311165201.GA19314@nmt.edu>
On 11 Mar 2005 at 9:52, Ryan wrote:
> Hello,
> I've been through several of the news groups over the past few days
> and
> haven't found an exact answer to my question.
>
> I'm trying to install Fedora Core 3 on a Dell PowerEdge 1800 server
> that
> I just purchased, but the version of the aacraid driver for the SATA
> raid controller changed and I can't install.
>
> Just like the newsgroups state, Fedora Core 2 installs just fine.
> My
> problem is that I can't afford to run software that is outdated.
> There have been several security issues lately and FC3 seems to have
> fixes for them.
>
> Any help is greatly appreciated.
>
> Thank you.
>
> -Ryan
> -
> To unsubscribe from this list: send the line "unsubscribe linux-scsi"
> in the body of a message to majordomo@vger.kernel.org More majordomo
> info at http://vger.kernel.org/majordomo-info.html
>
This is somewhat off-topic, so I'll be brief. If you can install
Fedora Core 2 and the only reason you want Fedora Core 3 is newer
software, "man yum" after installing the 'yum' package (or choose a
different updater to suit your prefs) will be your friend. In other
words, a newer OS isn't the only way to get newer software,
especially on an OS that has a decent package management system (RPM
in this instance). FWIW.
Sincerely,
Andrew Kinney
President and
Chief Technology Officer
Advantagecom Networks, Inc.
http://www.advantagecom.net
prev parent reply other threads:[~2005-03-11 18:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-11 16:52 aacraid on Dell PowerEdge 1800 Ryan
2005-03-11 18:24 ` Andrew Kinney [this message]
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=423171EA.368.2C2CE275@localhost \
--to=andykinney@advantagecom.net \
--cc=linux-scsi@vger.kernel.org \
--cc=ryan@nmt.edu \
/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.