tape support
Corinna Vinschen
corinna@vinschen.de
Mon May 8 13:18:00 GMT 2000
JUAN LUIS GARCIA BUENDIA wrote:
> [...]
> -----------------------------------------------------------
> the command issued for mounting the tape device
>
> bash-2.03$ mount -f -s -b //./tape0 /dev/ct
> [...]
> bash-2.03$ mt -f /dev/ct status
> tape capacity : 0 KB remaining : 0 KB
> current block : 0 write protected : no
The output is strange. Was a media in the drive? Why does NT
report a capacity of 0 and remaining 0?
Please insert a media into the drive and send me the output
of
mt -f /dev/ct status 3
> bash-2.03$ tar cvf /dev/ct b20
> b20/
> b20/cori/
> b20/cori/cpio-2.4.2.README
> b20/cori/cpio-2.4.2.README.nfo
> b20/cori/cpio-2.4.2.tar.gz
> tar: Cannot write to /dev/ct: Permission denied
> tar: Error is not recoverable: exiting now
You get this `permission denied' when you try to read a tape,
that is written with another blocking factor than the Windows
tape driver is set to. Currently cygwin has no automatical
recognition for this. You must(!) know the blocking (U*Xes
typically uses 5K blocking on tape devices) and you can set
it with my `mt' command.
> i tried to use the command you wrote in your message
>
> bash-2.03$ mount -f -s -b //./tape0 /dev/ct
> [...]
> bash-2.03$ mount -f -s -b '//./tape0' /dev/ct
> [...]
> bash-2.03$ mount -f -s -b "//./tape0" /dev/ct
What's that? Above you mentioned that you have successfully
mounted???
--
Corinna Vinschen
Cygwin Developer
Cygnus Solutions, a Red Hat company
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
More information about the Cygwin
mailing list