From owner-freebsd-hackers Tue Mar 21 14:14:56 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id OAA05790 for hackers-outgoing; Tue, 21 Mar 1995 14:14:56 -0800 Received: from LOCALHOST (LOCALHOST [127.0.0.1]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id OAA05781; Tue, 21 Mar 1995 14:14:54 -0800 X-Authentication-Warning: freefall.cdrom.com: Host LOCALHOST didn't use HELO protocol To: jbryant@server.iadfw.net cc: freebsd-hackers@FreeBSD.org Subject: Re: Problems with 2940 and 950210snap In-reply-to: Your message of "Tue, 21 Mar 95 15:46:52 CST." <199503212146.PAA23793@server.iadfw.net> Date: Tue, 21 Mar 1995 14:14:54 -0800 Message-ID: <5780.795824094@freefall.cdrom.com> From: "Jordan K. Hubbard" Sender: hackers-owner@FreeBSD.org Precedence: bulk > > Wrong. mt & st are control commands. ft should vanish into the device > > driver itself. > > Exactly what do you mean by that? I have been hacking a FULLY QIC compat > backup/restore [i.e., QIC-40/80, and 113 style filesets] program for some > time now for FreeBSD. Would such a change in any way effect my work? I mean that having both a device driver (/dev/ft0) and a special user-agent for dealing with it (ft) violates the UNIX principle of least surprise. I should be able to do: tar cvf /dev/ft0 And have it just work. The fact that /dev/rst0 and /dev/rmt0 both do this only leads the new user further down the garden path. Actually, I think if you do a tar cvf /dev/ft0 at this point you will panic your system! Not quite user-friendly enough yet! :-) Jordan