mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Kurt Garloff <garloff@suse.de>
To: Rogier Wolff <R.E.Wolff@BitWizard.nl>
Cc: Andre Hedrick <andre@linux-ide.org>,
	e.ckhard@u-code.de, marcel@mesa.nl, linux-kernel@vger.kernel.org
Subject: Re: IDE_TAPE problem wiht ONSTREAM DI30
Date: Mon, 4 Dec 2000 16:05:54 +0100	[thread overview]
Message-ID: <20001204160554.L6281@garloff.etpnet.phys.tue.nl> (raw)
In-Reply-To: <Pine.LNX.4.10.10012032315100.13699-100000@master.linux-ide.org> <200012040825.JAA08264@cave.bitwizard.nl>
In-Reply-To: <200012040825.JAA08264@cave.bitwizard.nl>; from R.E.Wolff@BitWizard.nl on Mon, Dec 04, 2000 at 09:25:33AM +0100

[-- Attachment #1: Type: text/plain, Size: 1995 bytes --]

Hi,

On Mon, Dec 04, 2000 at 09:25:33AM +0100, Rogier Wolff wrote:
> Stay away from onstream is my advice nowadays. 

I've been using the USB and the SCSI versions of OnStream tapes with 
good success!

> We've been trying to get the stupid thing to work since july 8th, and
> onstream technical support has been very helpful by telling us what to
> do and such. 

If you want a really helpful advice:
Use the osst driver and the use it with ide-scsi.
Report problems to the osst mailing list. 
So far, I'm not aware of anybody we failed to help.
http://linux1.onstream.nl/test/

> Like downgrading to a kernel version that has known remote attacks.

Who did give such a stupid advice?

> However doing that does not solve the problems we
> report. After much ado, they promise to "escalate" the problem to 
> people in the states, and then this does not lead to results in 
> the month we've given them. 

I'm afraid I do not know too much about the ide-tape support for DI-30.
Gadi Oxman is the author of it (has been paid by OnStream to write it, BTW),
but he may be short on time at the moment to help you with the problem.

> If you start using a backup program that needs to seek back and forth
> a few times, the drive loses track where it is, and doesn't recover
> from this situation.

I don't know whether this is a hard- or a software problem in your case.

> I've returned mine to my vendor, and I hope that Onstream gets the
> message in the end: They do NOT support Linux. 

I have a completely different impression. Otherwise neither the DI-30 would
be supported by ide-tape, nor would there be the osst driver, supporting
SC-x0, DI-30 (over ide-scsi) and USB30 (usb-storage in 2.4 w/ Freecom
support).

Regards,
-- 
Kurt Garloff  <garloff@suse.de>                          Eindhoven, NL
GPG key: See mail header, key servers         Linux kernel development
SuSE GmbH, Nuernberg, FRG                               SCSI, Security

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

  reply	other threads:[~2000-12-04 15:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-30 16:26 Eckhard Jokisch
2000-11-30 16:05 ` Marcel J.E. Mol
2000-12-03 21:07   ` Eckhard Jokisch
2000-12-04  7:16     ` Andre Hedrick
2000-12-04  8:25       ` Rogier Wolff
2000-12-04 15:05         ` Kurt Garloff [this message]
2000-12-13 21:05           ` [Solved]IDE_TAPE problem with " Eckhard Jokisch

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=20001204160554.L6281@garloff.etpnet.phys.tue.nl \
    --to=garloff@suse.de \
    --cc=R.E.Wolff@BitWizard.nl \
    --cc=andre@linux-ide.org \
    --cc=e.ckhard@u-code.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcel@mesa.nl \
    /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®