From: Willem Riede <wrlk@riede.org>
To: Paul Jackson <pj@sgi.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] remove obsolete onstream support from ide-tape in 2.6.3-rc3
Date: Sun, 15 Feb 2004 18:47:11 -0500 [thread overview]
Message-ID: <20040215234711.GC4957@serve.riede.org> (raw)
In-Reply-To: <20040215153214.002dcc9a.pj@sgi.com> (from pj@sgi.com on Sun, Feb 15, 2004 at 18:32:14 -0500)
On 2004.02.15 18:32, Paul Jackson wrote:
> And another obsolete tape drive goes on my vintage shelf.
>
> Willem - I notice off SourceForge a note:
>
> http://sourceforge.net/forum/forum.php?forum_id=333748
>
> Posted By: wriede
> Date: 2003-12-01 16:24
> Summary: osst, the Linux OnStream Tape driver now avalable on sf.net
>
> Following the unfortunate bankruptcy of OnStream, I have now completed
> the migration of the osst CVS repository, web site and mailing list to
> SourceForge.
>
> Willem Riede,
> osst maintainer.
>
> How does this relate to your removal of onstream from 2.6? I'm guessing
> that you are maintaining onstream in 2.4, but not in 2.6 or beyond. But
> that's just a guess.
I am maintaining osst, which is available in both 2.4 and 2.6. It works very
well, and the DI-30 is supported by it through ide-scsi. In contrast,
onstream code in ide-tape has not been maintained, and is buggy. To ease my
work, I want osst to be the only onstream code in the kernel.
So the "obsolete" refers to ide-tape's implementation only, not the drive.
Regards, Willem Riede.
next prev parent reply other threads:[~2004-02-15 23:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-15 22:11 [PATCH] remove obsolete onstream support from ide-tape in 2.6.3-rc3 Willem Riede
2004-02-15 23:32 ` Paul Jackson
2004-02-15 23:47 ` Willem Riede [this message]
2004-02-16 1:08 ` Paul Jackson
2004-02-17 0:15 ` bill davidsen
2004-02-17 10:13 ` Paul Jackson
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=20040215234711.GC4957@serve.riede.org \
--to=wrlk@riede.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pj@sgi.com \
/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.