From owner-freebsd-scsi Wed Dec 23 20:43:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA06363 for freebsd-scsi-outgoing; Wed, 23 Dec 1998 20:43:10 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from math.berkeley.edu (math.Berkeley.EDU [128.32.183.94]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA06357 for ; Wed, 23 Dec 1998 20:43:07 -0800 (PST) (envelope-from dan@math.berkeley.edu) Received: from rain.berkeley.edu (rain.Berkeley.EDU [128.32.183.196]) by math.berkeley.edu (8.8.7/8.8.7) with ESMTP id UAA10439 for ; Wed, 23 Dec 1998 20:42:47 -0800 (PST) From: dan@math.berkeley.edu (Dan Strick) Received: (dan@localhost) by rain.berkeley.edu (8.8.5/8.6.4) id UAA03018 for freebsd-scsi@FreeBSD.ORG; Wed, 23 Dec 1998 20:42:45 -0800 (PST) Date: Wed, 23 Dec 1998 20:42:45 -0800 (PST) Message-Id: <199812240442.UAA03018@rain.berkeley.edu> To: freebsd-scsi@FreeBSD.ORG Subject: Re: /dev/nrsa0 file mark handling Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > "control open" - Already on my list. > > "mt_fileno/mt_blkno" - I'm mulling that one. Yes, I think I will, but > it'll take a lot of work because there are (now) a large number of > conditions that invalidate and make completely unknown those > relative positions (EOD, hard block locating). > > "current state" - Interesting notion. My motivation for wanting these things is that I have a program (designed for use with a different device driver that provided these facilities) that could repeatedly query the driver for device state and type the result using something like a curses overlay style. The result was something like a continuous drive status control panel that lent confidence to the progress of long tape jobs. It was also cute when used with disks (my disk driver returned the number of the most recently accessed block in the status struct). I liked to watch the heads march down the drive when doing disk-to-disk copies and such. I once considered doing a graphical interface that would draw a rotating disk with a sliding disk head arm over a numerical scale. (Note: pseudo cylinder numbers are useful even when not precisely accurate.) There are all sorts of other interesting possibilities. Bad sectors could be colored red. When disk errors occur, we could show bits falling off the disk and piling up on the floor. Imagine a snow storm of metallic film flakes. Color them dark red in honor of the traditional medium. but I digress ... back to work now Dan Strick dan@math.berkeley.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message