Re: Raid problems

["Paul Nelson" <p_nelson-br@xxxxxxxxxxxx>]

IMHO, Rochester IS the most cost effective vendor for the systems with which
we work. Has it occurred to you that the microcode/firmware is written to
tightly integrate the hardware with the operating system? Do we want to
start playing the game of having to go all over the web looking for hardware
drivers like we do with the MS operating systems? I think not! We're
techies, so we can get away with thinking about the kinds of things you are
talking about.

The iSeries SYSTEMS (read tightly integrated hardware and software) are
built to run businesses. If they are anything like my clients, the owners of
those businesses prefer to do one-stop shopping.

Paul Nelson
Braxton-Reed, Inc.
630-327-8665 Cell
708-923-7354 Home
pnelson@braxton-reed.com
----- Original Message -----
From: "Konrad Underkofler" <kdunderk@hoshizaki.com>
To: <midrange-l@midrange.com>
Sent: Thursday, August 29, 2002 3:31 PM
Subject: RE: Raid problems


> And unfortunately with IBM as sole supplier with:
> 1) an attempted class action against their faulty drives
> 2) disk ptfs that address drive problems
>
> I guess we are stuck either way. Anyone in manufacturing
> would have to admit that a sole source is a problem.
> Alternate sources increase innovation and allow you to
> pick the most realiable, cost effective vendor. At one
> time or another all the big mfgs have attempted to kill
> off each other by excluding alternate vendor products from
> the premises.
>
> Standards are great, with Linux on the iSeries, the hardware
> is the last great proprietary holdout. It certainly is a
> major disincentive in wider adoption of the iSeries to promote
> open systems on one hand but make the hardware exclusive.
>
> Regards
>
> Konrad
>
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> To post a message email: MIDRANGE-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> or email: MIDRANGE-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
>