public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Markus Lidel <Markus.Lidel@shadowconnect.com>
To: "Salyzyn, Mark" <mark_salyzyn@adaptec.com>
Cc: Christoph Hellwig <hch@infradead.org>,
	Ross Macintyre <raz@macs.hw.ac.uk>,
	Mark Haverkamp <markh@osdl.org>,
	linux-scsi <linux-scsi@vger.kernel.org>,
	matt_domsch@dell.com
Subject: Re: adaptec 2120S software under RedHat 8.0 and FC2
Date: Wed, 23 Mar 2005 18:43:31 +0100	[thread overview]
Message-ID: <4241AAC3.7050702@shadowconnect.com> (raw)
In-Reply-To: <60807403EABEB443939A5A7AA8A7458BED3211@otce2k01.adaptec.com>

Hello,

Salyzyn, Mark wrote:
 > [...]
>>note that if adaptec simply opensourced their managment tools we wouldn't
>>have this problem at all. I wonder why Adaptec did that for the old
>>i2o-based controllers but not aacraid.  
> Oh yes, that, worked hard on the powers-that-be to permit this. Could
> not release a substantial majority of it because it would violate
> licensed libraries (Zinc, being one of them, I am sorry to admit). So we
> release the engine and the raidutil. No logger, no remote communication
> engine, no GUI and no browser engine either. It was the best we could
> do.
> Once released, and under a BSD license, the open source community failed
> to contribute one change to the sources. All it did was permit the tools
> to be packaged, archived and to continue in-perpetuity when
> compatibility libraries failed to work on newer installations.

Hmmm, IMHO that's not 100% correct... It's true that currently there is 
no new version. I'm working on the 64-bit version and a rewrite of the 
kernel-interface to get rid of the ioctl's... Because i'm still working 
on the interface, i haven't released both the kernel as well as the 
raidutils yet. But you could look into subversion to see that there *is* 
developement. Also IMHO it is be better to provide documentation for how 
to program the controller instead of releasing the source of the 
management tool itself.

 > [...]



Best regards,


Markus Lidel
------------------------------------------
Markus Lidel (Senior IT Consultant)

Shadow Connect GmbH
Carl-Reisch-Weg 12
D-86381 Krumbach
Germany

Phone:  +49 82 82/99 51-0
Fax:    +49 82 82/99 51-11

E-Mail: Markus.Lidel@shadowconnect.com
URL:    http://www.shadowconnect.com

  reply	other threads:[~2005-03-23 17:42 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-23 15:37 adaptec 2120S software under RedHat 8.0 and FC2 Salyzyn, Mark
2005-03-23 17:43 ` Markus Lidel [this message]
2005-03-28 21:57 ` Christoph Hellwig
  -- strict thread matches above, loose matches on Subject: below --
2005-03-22 17:43 Salyzyn, Mark
2005-03-23 11:05 ` Christoph Hellwig
2005-03-17 13:41 Salyzyn, Mark
2005-03-20  9:12 ` Christoph Hellwig
2005-03-22 16:32   ` Ross Macintyre
2005-03-23 11:04     ` Christoph Hellwig
2005-03-23 17:53       ` Markus Lidel
2005-03-24 17:19       ` Ross Macintyre
2005-03-16 13:02 Salyzyn, Mark
2005-03-16 21:52 ` Mark Haverkamp
2005-03-20  9:09   ` Christoph Hellwig
2005-03-16 11:20 Ross Macintyre

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=4241AAC3.7050702@shadowconnect.com \
    --to=markus.lidel@shadowconnect.com \
    --cc=hch@infradead.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mark_salyzyn@adaptec.com \
    --cc=markh@osdl.org \
    --cc=matt_domsch@dell.com \
    --cc=raz@macs.hw.ac.uk \
    /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