From: Finn Thain <fthain@telegraphics.com.au>
To: "Martin K. Petersen" <martin.petersen@oracle.com>
Cc: Chris Boot <bootc@bootc.net>,
linuxppc-dev@lists.ozlabs.org, target-devel@vger.kernel.org,
linux-scsi@vger.kernel.org,
linux1394-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org,
Bart Van Assche <bvanassche@acm.org>,
Chuhong Yuan <hslester96@gmail.com>,
Nicholas Bellinger <nab@linux-iscsi.org>,
Stefan Richter <stefanr@s5r6.in-berlin.de>
Subject: Re: [PATCH] scsi: target/sbp: remove firewire SBP target driver
Date: Wed, 17 Jun 2020 14:21:39 +1000 (AEST) [thread overview]
Message-ID: <alpine.LNX.2.22.394.2006171310520.11@nippy.intranet> (raw)
In-Reply-To: <yq18sgml9ds.fsf@ca-mkp.ca.oracle.com>
On Tue, 16 Jun 2020, Martin K. Petersen wrote:
> > I haven't used this driver for a long time, but I still own PowerMacs
> > with firewire, and I know I'm not the only one.
>
I need to correct what I wrote above. I recall that years ago, when I
needed to share storage from my Linux box to my PowerBook pismo, I used
ethernet and the globalSAN iSCSI initiator for Mac OS X (which is no
longer freely available AFAICS). When I said that I had used the SBP
target driver before, I misremembered that iSCSI target setup. I've
actually never used the SBP target driver.
> I also have old 1394 hardware kicking around in the basement. But having
> worked with FireWire shared storage targets in the past, I have zero
> desire to ever touch any of that again.
>
> I could understand an objection if we were to entertain removing sbp2.
> But really, how many people are setting up FireWire targets?
>
It's a good question. I don't know the answer.
I have successfully used the Linux sbp2 host driver in the past, and will
probably need to use it again. Likewise, I can see myself using the sbp
target driver in the future because that might interoperate with MacOS 9,
and might provide a bootable device to the PowerMac ROM. iSCSI cannot do
those things.
WARNING: multiple messages have this Message-ID (diff)
From: Finn Thain <fthain@telegraphics.com.au>
To: "Martin K. Petersen" <martin.petersen@oracle.com>
Cc: Chris Boot <bootc@bootc.net>,
linuxppc-dev@lists.ozlabs.org, target-devel@vger.kernel.org,
linux-scsi@vger.kernel.org,
linux1394-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org,
Bart Van Assche <bvanassche@acm.org>,
Chuhong Yuan <hslester96@gmail.com>,
Nicholas Bellinger <nab@linux-iscsi.org>,
Stefan Richter <stefanr@s5r6.in-berlin.de>
Subject: Re: [PATCH] scsi: target/sbp: remove firewire SBP target driver
Date: Wed, 17 Jun 2020 04:21:39 +0000 [thread overview]
Message-ID: <alpine.LNX.2.22.394.2006171310520.11@nippy.intranet> (raw)
In-Reply-To: <yq18sgml9ds.fsf@ca-mkp.ca.oracle.com>
On Tue, 16 Jun 2020, Martin K. Petersen wrote:
> > I haven't used this driver for a long time, but I still own PowerMacs
> > with firewire, and I know I'm not the only one.
>
I need to correct what I wrote above. I recall that years ago, when I
needed to share storage from my Linux box to my PowerBook pismo, I used
ethernet and the globalSAN iSCSI initiator for Mac OS X (which is no
longer freely available AFAICS). When I said that I had used the SBP
target driver before, I misremembered that iSCSI target setup. I've
actually never used the SBP target driver.
> I also have old 1394 hardware kicking around in the basement. But having
> worked with FireWire shared storage targets in the past, I have zero
> desire to ever touch any of that again.
>
> I could understand an objection if we were to entertain removing sbp2.
> But really, how many people are setting up FireWire targets?
>
It's a good question. I don't know the answer.
I have successfully used the Linux sbp2 host driver in the past, and will
probably need to use it again. Likewise, I can see myself using the sbp
target driver in the future because that might interoperate with MacOS 9,
and might provide a bootable device to the PowerMac ROM. iSCSI cannot do
those things.
WARNING: multiple messages have this Message-ID (diff)
From: Finn Thain <fthain@telegraphics.com.au>
To: "Martin K. Petersen" <martin.petersen@oracle.com>
Cc: Chris Boot <bootc@bootc.net>,
Bart Van Assche <bvanassche@acm.org>,
linux-scsi@vger.kernel.org, Chuhong Yuan <hslester96@gmail.com>,
linux-kernel@vger.kernel.org,
Nicholas Bellinger <nab@linux-iscsi.org>,
target-devel@vger.kernel.org,
linux1394-devel@lists.sourceforge.net,
linuxppc-dev@lists.ozlabs.org,
Stefan Richter <stefanr@s5r6.in-berlin.de>
Subject: Re: [PATCH] scsi: target/sbp: remove firewire SBP target driver
Date: Wed, 17 Jun 2020 14:21:39 +1000 (AEST) [thread overview]
Message-ID: <alpine.LNX.2.22.394.2006171310520.11@nippy.intranet> (raw)
In-Reply-To: <yq18sgml9ds.fsf@ca-mkp.ca.oracle.com>
On Tue, 16 Jun 2020, Martin K. Petersen wrote:
> > I haven't used this driver for a long time, but I still own PowerMacs
> > with firewire, and I know I'm not the only one.
>
I need to correct what I wrote above. I recall that years ago, when I
needed to share storage from my Linux box to my PowerBook pismo, I used
ethernet and the globalSAN iSCSI initiator for Mac OS X (which is no
longer freely available AFAICS). When I said that I had used the SBP
target driver before, I misremembered that iSCSI target setup. I've
actually never used the SBP target driver.
> I also have old 1394 hardware kicking around in the basement. But having
> worked with FireWire shared storage targets in the past, I have zero
> desire to ever touch any of that again.
>
> I could understand an objection if we were to entertain removing sbp2.
> But really, how many people are setting up FireWire targets?
>
It's a good question. I don't know the answer.
I have successfully used the Linux sbp2 host driver in the past, and will
probably need to use it again. Likewise, I can see myself using the sbp
target driver in the future because that might interoperate with MacOS 9,
and might provide a bootable device to the PowerMac ROM. iSCSI cannot do
those things.
next prev parent reply other threads:[~2020-06-17 4:21 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-13 8:37 [PATCH] scsi: target/sbp: remove SBP target driver Chris Boot
2020-06-13 8:37 ` Chris Boot
2020-06-14 0:03 ` [PATCH] scsi: target/sbp: remove firewire " Finn Thain
2020-06-14 0:03 ` Finn Thain
2020-06-14 0:03 ` Finn Thain
2020-06-14 10:34 ` Chris Boot
2020-06-14 10:34 ` Chris Boot
2020-06-14 10:34 ` Chris Boot
2020-06-14 23:28 ` Finn Thain
2020-06-14 23:28 ` Finn Thain
2020-06-14 23:28 ` Finn Thain
2020-06-15 15:00 ` Chris Boot
2020-06-15 15:00 ` Chris Boot
2020-06-15 15:00 ` Chris Boot
2020-06-16 9:42 ` Finn Thain
2020-06-16 9:42 ` Finn Thain
2020-06-16 9:42 ` Finn Thain
2020-06-16 14:08 ` Bart Van Assche
2020-06-16 14:08 ` Bart Van Assche
2020-06-16 14:08 ` Bart Van Assche
2020-06-16 14:13 ` Johannes Thumshirn
2020-06-16 14:13 ` Johannes Thumshirn
2020-06-16 14:13 ` Johannes Thumshirn
2020-06-16 15:34 ` James Bottomley
2020-06-16 15:34 ` James Bottomley
2020-06-16 15:34 ` James Bottomley
2020-06-16 17:59 ` Chris Boot
2020-06-16 17:59 ` Chris Boot
2020-06-16 17:59 ` Chris Boot
2020-06-17 3:09 ` Martin K. Petersen
2020-06-17 3:09 ` Martin K. Petersen
2020-06-17 3:09 ` Martin K. Petersen
2020-06-18 0:40 ` Finn Thain
2020-06-18 0:40 ` Finn Thain
2020-06-18 0:40 ` Finn Thain
2020-06-17 2:07 ` Finn Thain
2020-06-17 2:07 ` Finn Thain
2020-06-17 2:07 ` Finn Thain
2021-01-04 17:43 ` Bart Van Assche
2021-01-04 17:43 ` Bart Van Assche
2021-01-04 22:50 ` Finn Thain
2021-01-04 22:50 ` Finn Thain
2021-01-05 1:48 ` Bart Van Assche
2021-01-05 1:48 ` Bart Van Assche
2020-06-17 2:35 ` Martin K. Petersen
2020-06-17 2:35 ` Martin K. Petersen
2020-06-17 2:35 ` Martin K. Petersen
2020-06-17 4:21 ` Finn Thain [this message]
2020-06-17 4:21 ` Finn Thain
2020-06-17 4:21 ` Finn Thain
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=alpine.LNX.2.22.394.2006171310520.11@nippy.intranet \
--to=fthain@telegraphics.com.au \
--cc=bootc@bootc.net \
--cc=bvanassche@acm.org \
--cc=hslester96@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=martin.petersen@oracle.com \
--cc=nab@linux-iscsi.org \
--cc=stefanr@s5r6.in-berlin.de \
--cc=target-devel@vger.kernel.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 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.