From: Pete Zaitcev <zaitcev@redhat.com>
To: Mikael Pettersson <mikpe@csd.uu.se>
Cc: Pete Zaitcev <zaitcev@redhat.com>,
linux-kernel@vger.kernel.org, linux-tape@vger.kernel.org
Subject: Re: idetape broke in 2.4.x-2.4.9-ac5 (write OK but not read) ide-scsi works in 2.4.4
Date: Fri, 28 Sep 2001 22:35:02 -0400 [thread overview]
Message-ID: <20010928223502.D13766@devserv.devel.redhat.com> (raw)
In-Reply-To: <200109042234.AAA28635@harpo.it.uu.se> <20010927234023.A16753@devserv.devel.redhat.com> <15284.16283.111942.13934@harpo.it.uu.se>
In-Reply-To: <15284.16283.111942.13934@harpo.it.uu.se>; from mikpe@csd.uu.se on Fri, Sep 28, 2001 at 11:15:07AM +0200
> From: Mikael Pettersson <mikpe@csd.uu.se>
> Date: Fri, 28 Sep 2001 11:15:07 +0200
> Cc: linux-kernel@vger.kernel.org, linux-tape@vger.kernel.org
> > By the way, why does everyone insist on using ide-tape?
> > It seems to be broken beyond any repair by injection of
> > lethal poison marked "OnStream Support" (not that it was brilliant
> > before, but that was the last nail in the coffin). Just use ide-scsi
> > and be done with it. I really do not enjoy reading ide-tape.c.
>
> I agree that ide-tape.c looks like a buggy piece of cr*p, but apart
> from that, what would I gain from using scsi tape on top of ide-scsi?
> Would it magically work on broken Colorados?
Umm... I hope someone else would fix ide-scsi when it breaks :)
I fixed Colorado, but it's certainly not the last bug.
Frist, DMA must be off, and it is often on by default.
Second, Dell QA already filed a new tapemark related bug...
-- Pete
next prev parent reply other threads:[~2001-09-29 2:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-04 22:34 idetape broke in 2.4.x-2.4.9-ac5 (write OK but not read) ide-scsi works in 2.4.4 Mikael Pettersson
2001-09-28 3:40 ` Pete Zaitcev
2001-09-28 9:15 ` Mikael Pettersson
2001-09-29 2:35 ` Pete Zaitcev [this message]
[not found] <mailman.999367801.660.linux-kernel2news@redhat.com>
2001-09-04 0:14 ` Pete Zaitcev
-- strict thread matches above, loose matches on Subject: below --
2001-09-01 18:08 Mikael Pettersson
2001-09-01 15:03 Floydsmith
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=20010928223502.D13766@devserv.devel.redhat.com \
--to=zaitcev@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tape@vger.kernel.org \
--cc=mikpe@csd.uu.se \
/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