Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!wuarchive!decwrl!shlump.nac.dec.com!shodha.dec.com!elvira!ridder
From: ridder@elvira.enet.dec.com (Hans Ridder)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Determining disk devices
Message-ID: <570@shodha.dec.com>
Date: 6 Jan 90 06:22:32 GMT
References: <331@sed170.HAC.COM> <9223@cbmvax.commodore.com> <129936@sun.Eng.Sun.COM>
Sender: news@shodha.dec.com
Organization: Digital Equipment Corporation, Customer Support Center
Lines: 28

In article <129936@sun.Eng.Sun.COM> cmcmanis@sun.UUCP (Chuck McManis) writes:
>In article <9223@cbmvax.commodore.com> (Andy Finkel) writes:
>>For now (and, if you always want to be safe) run through the list
>>twice, and only report the devices that have matching volume nodes.
>
>Uh Andy, there is this problem that if there isn't a disk in the
>floppy drive you would never put it's button up on the screen using
>your method no? So people running DPAINT from the ram disk without
>having any floppies in drives would just get RAM: ?

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....

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.

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.

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

-hans
========================================================================
  Hans-Gabriel Ridder			Digital Equipment Corporation
  ridder@elvira.enet.dec.com		Customer Support Center
  ...decwrl!elvira.enet!ridder		Colorado Springs, CO