From: Christoph Hellwig <hch@infradead.org>
To: "Bhat, Vinod" <vinod.bhat@hp.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: Fibre Channel state of the union
Date: Wed, 20 Apr 2005 23:51:22 +0100 [thread overview]
Message-ID: <20050420225122.GA8292@infradead.org> (raw)
In-Reply-To: <48D2F90F2962FC48852540179EC444F605E699C0@tayexc18.americas.cpqcorp.net>
On Wed, Apr 20, 2005 at 02:43:23PM -0400, Bhat, Vinod wrote:
> Hi,
>
> Here are few thoughts. On sourceforge there is a hbaapi project.
> http://sourceforge.net/projects/hbaapi/ This is old project. Is it
> possible to update that one or create a new project for hbaapi?
first major problem is that it's licensed under an SNIA opensource license
which it links to but doesn't exist anymore on their website. To be
easily redistributable for Linux Distribution it should be licensed
under the LGPL or a BSDish license.
Also it contains lots of unessecary bloat like the dlopen-based plugin
loading and windows support that wouldn't be nessecary for something
that's simply a shim from the SNIA apis to the Linux native mechanisms.
> If we have a open source project and supported by major HBA vendors, we
> can build tools(open source) on this project. That will help bigger
> community. Here is the SN Ping and Traceroute project proposal. This is
> one example.
>
> http://www.t11.org/ftp/t11/admin/project_proposals/05-225v0.pdf
> http://www.t11.org/ftp/t11/admin/project_proposals/05-177v1.txt
These are good ideas for an fc-tools package or something like that.
I'd rather write them directly to native APIs instead of going through
the needless complication and obsfucations of the SNIA APIs.
next prev parent reply other threads:[~2005-04-20 22:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-20 18:43 Fibre Channel state of the union Bhat, Vinod
2005-04-20 22:51 ` Christoph Hellwig [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-04-19 5:05 James.Smart
2005-04-18 15:40 Christoph Hellwig
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=20050420225122.GA8292@infradead.org \
--to=hch@infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=vinod.bhat@hp.com \
/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