From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: mdresser@windsormachine.com (Mike Dresser)
Cc: camm@enhanced.com (Camm Maguire), khalid@fc.hp.com (Khalid Aziz),
linux-kernel@vger.kernel.org
Subject: Re: 2.2.18 IDE tape problem, with ide-scsi
Date: Tue, 27 Feb 2001 22:21:58 +0000 (GMT) [thread overview]
Message-ID: <E14XsVO-0004M1-00@the-village.bc.nu> (raw)
In-Reply-To: <3A9BF340.B8DD9F56@windsormachine.com> from "Mike Dresser" at Feb 27, 2001 01:34:40 PM
> Wish i knew, I'm praying that 2.2.19 hasn't/doesn't implement the ide patches like 2.4.x did. If so, and a major problem is found in
> 2.2.18, then I have to maintain another machine running 2.2.18 to restore tapes. Also means i'd have to stop using taper or dump,
> and stick to tar only, as both want to read the tape back in at some point.
2.2 isnt likely to ever see the IDE patches as standard.
next prev parent reply other threads:[~2001-02-27 22:20 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-27 16:06 Camm Maguire
2001-02-27 15:07 ` Khalid Aziz
2001-02-27 17:19 ` Camm Maguire
2001-02-27 15:34 ` Khalid Aziz
2001-02-27 19:52 ` Camm Maguire
2001-02-27 18:18 ` Khalid Aziz
2001-02-27 20:26 ` Andre Hedrick
2001-02-27 21:26 ` Khalid Aziz
2001-02-28 15:23 ` Camm Maguire
2001-02-28 15:34 ` Mike Dresser
2001-03-07 22:54 ` Camm Maguire
2001-03-12 16:52 ` Khalid Aziz
2001-03-13 14:14 ` Camm Maguire
2001-02-27 17:32 ` Mike Dresser
2001-02-27 18:31 ` Camm Maguire
2001-02-27 18:34 ` Mike Dresser
2001-02-27 19:05 ` Andre Hedrick
2001-02-27 19:40 ` Camm Maguire
2001-03-01 17:02 ` Khalid Aziz
2001-02-27 22:21 ` Alan Cox [this message]
2001-02-27 19:01 ` Andre Hedrick
2001-02-27 19:04 ` Mike Dresser
2001-03-07 0:34 ` [PATCH] " Chip Salzenberg
2001-03-07 1:09 ` Andre Hedrick
[not found] <Pine.LNX.4.10.10102271153560.29323-100000@coffee.psychology.mcmaster.ca>
2001-02-27 17:16 ` Camm Maguire
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=E14XsVO-0004M1-00@the-village.bc.nu \
--to=alan@lxorguk.ukuu.org.uk \
--cc=camm@enhanced.com \
--cc=khalid@fc.hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mdresser@windsormachine.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 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®