From: Matthias Schniedermeyer <ms@citd.de>
To: linux-kernel@vger.kernel.org
Cc: linux1394-devel@lists.sourceforge.net
Subject: Re: eth1394 and sbp2 maintainers
Date: Mon, 12 Sep 2005 12:38:55 +0200 [thread overview]
Message-ID: <43255ABF.8080500@citd.de> (raw)
In-Reply-To: <20050912074758.GB3863@ime.usp.br>
Rogério Brito wrote:
> On Sep 11 2005, Randy.Dunlap wrote:
>
>>Stefan,
>>
>>I want to say that I think that you are doing a very commendable
>>job on sbp2. Much thanks for your efforts.
>
> Let me add my voice to the choir here. I agree with Randy when he says
> that Stefan does a superb job supporting firewire with Linux.
Then let me be the voice telling about the flip-side.
I've used Firewire with SBP2-driver for nearly 4 years and most of the
time there was one problem or another (beginning from not-SMP-safe to
"plainly not working" for nearly a year, where i had to downpatch
Firewire (The nodemanager "desaster") for a very long time)
When the last problem crept up (sbp2-module couldn't be unloaded if only
a none-HDD-device was connected) i was so feed up with the continuous
hassle that i completly replaced my firewire hardware with USB2 Hardware.
With USB pluging/unplugging works flawlessly (couldn't say that for 4
years Firewire). Operating several devices concurrently works flawlessly
(I was lucky when my 2 devices worked concurrently with Firewire. Most
of the time only 1 device couldn't be connected without risking
desaster), in constrast i've had 10 HDDs running concurrently connected
via USB2 without a problem!
I know that i may have skipped the time where USB hasn't been mature to
the time where USB was mature, but it got there. So forgive me when i'm
too negative about firewire and too positive about USB.
To say it short:
- Firewire and especially SBP2 haven't been very mature in my 4 YEARS(!)
using it.
- As far as i see the userbase just isn't big enough to make it mature.
Taking aside some niche usages, i guess firewire WILL DIE because of USB
sooner then later. For me firewire died 6 month ago. Rest in peace.
--
Real Programmers consider "what you see is what you get" to be just as
bad a concept in Text Editors as it is in women. No, the Real Programmer
wants a "you asked for it, you got it" text editor -- complicated,
cryptic, powerful, unforgiving, dangerous.
next prev parent reply other threads:[~2005-09-12 10:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-10 18:39 eth1394 and sbp2 maintainers Stefan Richter
2005-09-12 4:55 ` Randy.Dunlap
2005-09-12 7:47 ` Rogério Brito
2005-09-12 10:38 ` Matthias Schniedermeyer [this message]
2005-09-12 16:41 ` Stefan Richter
2005-09-12 21:58 ` Jody McIntyre
2005-09-13 1:50 ` Ben Collins
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=43255ABF.8080500@citd.de \
--to=ms@citd.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
/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