mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Nicholas A. Bellinger" <nab@linux-iscsi.org>
To: Andy Grover <agrover@redhat.com>
Cc: Andreas Steinmetz <ast@domdv.de>,
	linux-kernel@vger.kernel.org, hch@infradead.org,
	torvalds@linux-foundation.org,
	target-devel <target-devel@vger.kernel.org>,
	Ritesh Raj Sarraf <rrs@debian.org>
Subject: Re: LIO - the broken iSCSI target implementation
Date: Thu, 17 Jan 2013 15:00:56 -0800	[thread overview]
Message-ID: <1358463656.18551.158.camel@haakon2.linux-iscsi.org> (raw)
In-Reply-To: <50F87BCA.10201@redhat.com>

On Thu, 2013-01-17 at 14:31 -0800, Andy Grover wrote:
> On 01/17/2013 12:56 PM, Nicholas A. Bellinger wrote:
> > On Thu, 2013-01-17 at 02:19 +0100, Andreas Steinmetz wrote:
> >> This is not a technical point of view. This is a more or less political
> >> and user point of view. And for any replies, I'm not subscribed (haven't
> >> been now for years).
> >>
> >> As a user, I was in need for an iSCSI target. Actually, I needed to
> >> export a SAS tape device (Ultrium 5) - which is one of the devices still
> >> sufficiently expensive to go the iSCSI target way) - well, not any disks
> >> (cheap enough, NFS available) or CD/DVD writers (I'd call these penny
> >> targets nowadays).
> >>
> >> Thus, lio (http://www.linux-iscsi.org/) seemed to be the politically and
> >> technically favoured solution. Except: it simply doesn't work, userspace
> >> utilities are seemingly not maintained,
> > 
> > I'm not sure what you mean.  There are targetcli+rtslib packages are
> > available for virtually every distribution
> > 
> > http://www.linux-iscsi.org/wiki/Targetcli#Linux_distributions
> 
> [CCing rrs@debian.org]
> 
> No... actually upstream targetcli/rtslib are not very well maintained.
> Around 5 patches each in the last year.
> 
> Meanwhile, I have been actively maintaining branches at
> github.com/agrover/targetcli-fb and github.com/agrover/rtslib-fb. We
> have a man page and screencasts even. Feel free to file bugs against
> them and I'll respond.
> 
> But I'm only packaging for Fedora/RHEL, so random people on Debian etc.
> get a bad experience. I'd like to see upstream accept my AGPLv3-licensed
> patches, or have Debian package the -fb versions, either instead or in
> addition to the upstream versions.
> 

So would I, but we've (RTS) been too busy having to work on other stuff
to pay the extensive legal bills from the fallout that your previous
public accusations have wrought. 

Even though your over it, it doesn't mean other opportunists did not try
to take advantage of the situation once you got tired and moved onto
other target userspace related things.

> (I'd kinda been waiting to bring it up until upstream had no commits in
> a year, but since you mentioned it...)

In any event, I don't really have a problem with merging the two if your
finally over the fact the userspace code is AGPL licensed. 

But please do this in a separate thread than piling on here.  Of course,
your more than welcome to fix rtslib for pSCSI, which is broken on
recent v3.x kernels.

(Hint: it's because /sys/class/scsi_device/H:C:T:L/device/block/$BLOCK_DEV
 no longer exists in upstream sysfs, which is what we use to match the passed
 /dev/$SCSI_DEV to H:C:T:L, and nothing related to TCM ABI changes)

Thanks,

--nab


  parent reply	other threads:[~2013-01-17 23:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-17  1:19 Andreas Steinmetz
2013-01-17 20:56 ` Nicholas A. Bellinger
2013-01-17 21:21   ` Nicholas A. Bellinger
2013-01-17 22:31   ` Andy Grover
2013-01-17 22:51     ` Linus Torvalds
2013-01-17 23:00     ` Nicholas A. Bellinger [this message]
2013-01-19  8:42     ` Ritesh Raj Sarraf
2013-01-18  1:53 ` Vladislav Bolkhovitin
     [not found] <fa.9LtpVDEImZxRAaqPOyWMlGOK4Ow@ifi.uio.no>
     [not found] ` <fa.xKOV9tOmjA6NPYEPagvZixrd/4w@ifi.uio.no>
2013-01-18 20:21   ` promo
2013-01-19 15:36     ` Fubo Chen

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=1358463656.18551.158.camel@haakon2.linux-iscsi.org \
    --to=nab@linux-iscsi.org \
    --cc=agrover@redhat.com \
    --cc=ast@domdv.de \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rrs@debian.org \
    --cc=target-devel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®