Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!zaphod.mps.ohio-state.edu!uwm.edu!dogie.macc.wisc.edu!vms.macc.wisc.edu
From: gilmore@vms.macc.wisc.edu (Neil Gilmore)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Determining disk devices
Message-ID: <2924@dogie.macc.wisc.edu>
Date: 6 Jan 90 18:24:44 GMT
Sender: news@dogie.macc.wisc.edu
Organization: University of Wisconsin Academic Computing Center
Lines: 35

In article <570@shodha.dec.com>, ridder@elvira.enet.dec.com (Hans Ridder) writes...

>What is the purpose of putting up a button when there is no disk in
>the drive?  There's nothing to read from or write to....

What is the purpose of putting up a volume buttin when that disk isn't 
in the drive. There's nothing to read from or write to....

>I have always thought that file requesters shouldn't be putting up
>*drive* buttons, they should be putting up *volume* buttons.  This
>would make network filesystems more transparent (to applications) too.

How would you then be able to access a volume not currently mounted? 
Having the drives allows you to put a disk in, then call the drive to 
access the volume.

>Also, I'd be inclined to use a *list* of volumes rather than buttons,
>so that you don't have to worry about running out of room for buttons
>in your requester.

A good idea, but there must be a way to access floppy volumes not 
currently known by the system. The drive buttons are quite useful for 
floppys, less so for hard disks and networks, which tend to be always 
mounted and have potenrially several volume names per physical device.

>Not trying to flame...just my point of view.

And mine.

>-hans
+-----------------------------------------------------------------------+
| Kitakaze Tatsu Raito	Neil Gilmore     internet:gilmore@macc.wisc.edu | 
| Jararvellir,          MACC, UW-Madison bitnet: gilmore@wiscmac3       |  
| Middle Kingdom        Madison, Wi                                     |
+-----------------------------------------------------------------------+