Date: Sat, 22 Apr 1995 14:25:32 -0500 From: Mail Delivery Subsystem <MAILER-DAEMON@uuneo.neosoft.com> To: <dbaker@Concorde-Mail.NeoSoft.COM> Subject: Returned mail: Host unknown (Name server: freebsd.com: host not found) Message-ID: <199504221925.OAA11441@uuneo.neosoft.com> Resent-Message-ID: <Pine.BSF.3.91.950422151453.259C@concorde.neosoft.com>
next in thread | raw e-mail | index | archive | help
This is a MIME-encapsulated message
--OAA11441.798578732/uuneo.neosoft.com
The original message was received at Sat, 22 Apr 1995 14:25:26 -0500
from mailman@localhost
----- The following addresses had delivery problems -----
<hackers@FreeBSD.com> (unrecoverable error)
----- Transcript of session follows -----
550 <hackers@FreeBSD.com>... Host unknown (Name server: freebsd.com: host not found)
----- Original message follows -----
--OAA11441.798578732/uuneo.neosoft.com
Content-Type: message/rfc822
Return-Path: dbaker@Concorde-Mail.NeoSoft.COM
Received: (from mailman@localhost) by uuneo.neosoft.com (8.6.10/8.6.10) id OAA11439; Sat, 22 Apr 1995 14:25:26 -0500
Received: from concorde.neosoft.com(198.65.161.214) by uuneo.neosoft.com via smap (V1.3)
id sma011391; Sat Apr 22 14:25:00 1995
Date: Sat, 22 Apr 1995 14:24:56 -0500 (CDT)
From: Daniel Baker <dbaker@Concorde-Mail.NeoSoft.COM>
X-Sender: dbaker@concorde.neosoft.com
To: "Clay D. Hopperdietzel" <hoppy@appsmiths.com>
cc: hackers@FreeBSD.com
Subject: Re: Colorado Tape Drive (floppy tape)
In-Reply-To: <199504221720.MAA14445@anvil.appsmiths.com>
Message-ID: <Pine.BSF.3.91.950422140007.259A-100000@concorde.neosoft.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
On Sat, 22 Apr 1995, Clay D. Hopperdietzel wrote:
> ::
> :: I still can't get my floppy tape to work..
> ::
> :: I tried the -c option with
> :: flags fdc0 1x0
> :: flags fdc0 0x1
> :: flags fdc0 1
> ::
> :: (All at differnt times, not in one boot...)
> ::
> :: I also did the same thing by adding them to my kernel and re-compiling,
> :: it gives me a screen full of errors whenver it tries to probe my tape
> :: drive. Same error over and over again. It says something like reading
> :: writing error or something.
Okay, here are my errors:
r output in input: fdc0: ready for output in input: fdc0: ready for output in input: fdc0: ready for output in input: fdc0: ready for output in input: fdc0: ready for output in input: fdc0: ready for output in input: fdc0: ready for output in input: fdc0:
ready for output in input: fdc0: ready for output in input: fdc0: ready for output in input: fdc0: ready for output in input: fdc0: ready for output in input: fdc0: ready for output in input: fdc0: ready for output in input: fdc0: ready for output in inp
ut: fdc0: ready for output in input: fdc0: ready for output in input: fdc0: ready for output in input: fdc0: ready for output in input: fdc0: ready for output in input: fdc0: ready for output in input: fdc0: ready for output in input: fdc0: ready for outp
ut in input: fdc0: ready for output in input: fdc0: ready for output in input: fdc0: ready for output in input: fdc0: ready for output in input: fdc0: ready for output in input: fdc0: ready for output in input: fdc0: ready for output in input: fdc0: ready
for output in input: fdc0: ready for output in input: fdc0: ready for output in input: fdc0: ready for output in input: fdc0: ready for output in input: fdc0: ready for output in input: fdc0: ready for output in input: fdc0: ready for output in input: fd
c0: ready for output in input: fdc0: ready for output in input: fdc0: ready for output in input: fdc0: ready for output in input: fdc0: ready for output in input: fdc0: ready for output in input: fdc0: ready for output in input: fdc0: ready for output in
input: fdc0: ready for output in input: fdc0: ready for output in input: fdc0: ready for output in input: fdc0: ready for output in input: fdc0: ready for output in input: fdc0: ready for output in input: fdc0: ready for output in input: fdc0: ready for o
utput in input: fdc0: ready for output in input: fdc0: ready for output in input: fdc0: ready for output in input: fdc0: ready for output in input: fdc0: ready for output in input: fdc0: ready for output in input: fdc0: ready for output in input: fdc0: re
ady for output in input: fdc0: ready for output in input: fdc0: ready for output in input: fdc0: ready for output in input: fdc0: ready for output in input: fdc0: ready for output in input: fdc0: ready for output in input: fdc0: ready for output in input:
fdc0: ready for output in input: fdc0: ready for output in input: fdc0: ready for output in input: fdc0: ready for output in input: fdc0: ready for output in input: fdc0: ready for output in input: fdc0: ready for output in input: fdc0: ready for output
in input: fdc0: ready for output in input: fdc0: ready for output in input: fdc0: ready for output in input: fdc0: ready for output in input: fdc0: ready for output in input: fdc0: ready for output in input: fdc0: ready for output in input: fdc0: ready fo
r output in input: fdc0: ready for output in input: fdc0: ready for output in input: fdc0: ready for output in input: fdc0: ready for output in input: fdc0: ready for output in input: fdc0: ready for output in input: fdc0: ready for output in input: fdc0:
ready for output in input: fdc0: ready for output in input: fdc0: ready for output in input: fdc0: ready for output in input: fdc0: too many errors, not logging any more
fd0: Operation timeout
fd0c: hard error reading fsbn 0 (No status)
>
> The errors are "normal", and would indicate that you successfully
> set the flags. (mode 2 and 3 should have worked, 1 is nonsense).
Maybe those aren't the errors you are talking about..
>
> When you get the errors, try using the tape and see if it works now.
> Remember to use 'ft' to do I/O to it:
>
> tar cvf - f1 f2 ... | ft
concorde % tar cvf - f1 / /usr | ft
tar: can't add file f1 : No such file or directory
tar: Removing leading / from absolute path names in the archive.
usr/
usr/tmp/
usr/tmp/src/
usr/tmp/src/cksums
usr/tmp/src/srcsys.au
/dev/rft0: Device not configured
concorde %
/dev/ft0: Device not configured
tar: can't add file f1 : No such file or directory
tar: Removing leading / from absolute path names in the archive.
usr/
usr/tmp/
usr/tmp/src/
usr/tmp/src/cksums
usr/tmp/src/srcsys.au
concorde %
concorde % tar cvf - f1 / /usr | ft -f /dev/ft1
tar: can't add file f1 : No such file or directory
tar: Removing leading / from absolute path names in the archive.
usr/
usr/tmp/
usr/tmp/src/
usr/tmp/src/cksums
usr/tmp/src/srcsys.au
/dev/ft1: Device not configured
concorde %
I tried all the devices that my tape drive should be on..
>
> I also recall from my previous dealings with you that you only had a single
> floppy and one tape connected to the controller. Is that still the
> case?
Yes.. Actually, my tape drive dosen't go directly to the controller, it
shares the jumper with the a:\ or /dev/fd0. So, in MS-Dos, when I backup
my hard drive, it won't let me use the a:\..
> ===============================================================================
> Clay D. Hopperdietzel hoppy@appsmiths.com
> AppSmiths, Inc. Voice (713) 578-0154 Fax (713) 578-6182
> 15915 Katy Fwy, Suite 470 Where do *I* Want to Go Today?
> Houston, Texas 77094 FreeBSD!
..Daniel
Daniel Baker -- NeoSoft Student Assistant (UseNet, FTP & FreeNet Admin.)
DBaker@NeoSoft.COM
DBaker@Concorde-Mail.NeoSoft.COM
** http://www.neosoft.com/neosoft/staff/dbaker/default.html **
--OAA11441.798578732/uuneo.neosoft.com--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199504221925.OAA11441>