Bug 7461 - older ftape in kernel
older ftape in kernel
Product: Red Hat Linux
Classification: Retired
Component: kernel (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Michael K. Johnson
Depends On:
  Show dependency treegraph
Reported: 1999-11-30 19:43 EST by rgiusti.cart
Modified: 2008-05-01 11:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2000-01-04 17:20:20 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description rgiusti.cart 1999-11-30 19:43:23 EST
It doesn't appear that the latest version of ftape was included with 6.1.
The included version is 3.04d, and I thought would be 4.02.

Also, the Makefile included /usr/src/linux/drivers/char/ftape is for
"personal development only" of Claus Heine, and doesn't accept the
"uninstall" parameter.  This makes ftape hard to remove, or upgrade.

Also, why isn't ftape in the Component drop down box of bugzilla?

I would appreciate any insight in upgrading my ftape to a different
version.  I have tried downloading 4.02 and 4.03prerelease2, reading the
documentation, and compiling the code.  However, I continue to get errors
with "structure has no member named 'timeout'" in several components (fdc-
io.c ftape.c ftape-buffer.c ftape-ro.c)

While I use ftape to access many different devices, today's goal was to
read a tape using my Ditto Max parallel port device.  I was unsuccessful,
though documentation lead me to believe it can be done with 4.02 or

Thank you for your time.
Comment 1 rgiusti.cart 1999-11-30 22:31:59 EST
I was able to find a web site that touts a fix:

I am trying it now...
Comment 2 Cristian Gafton 2000-01-04 17:20:59 EST
Assigned to dledford
Comment 3 Alan Cox 2000-09-15 14:16:49 EDT
Right now the status for ftape4 is a bit of a mystery. Nobody has submitted it
for the 2.2 kernel and I cant find a clear maintainer answer for it either

Note You need to log in before you can comment on or make changes to this bug.