Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!iuvax!rutgers!usc!pollux.usc.edu!papa
From: papa@pollux.usc.edu (Marco Papa)
Newsgroups: comp.sys.amiga
Subject: Re: Mount Bug Warning (Was: Re: VD0 help)
Message-ID: <19810@usc.edu>
Date: 10 Sep 89 04:49:57 GMT
References: <935@wsu-cs.uucp> <11102@boulder.Colorado.EDU> <26766@shemp.CS.UCLA.EDU> <20932@sequent.UUCP> <2493@abaa.UUCP> <838@madnix.UUCP>
Reply-To: papa@pollux.usc.edu (Marco Papa)
Organization: Felsina Software, Los Angeles, CA
Lines: 33

In article <838@madnix.UUCP> perry@madnix.UUCP (Perry Kivolowitz) writes:
>In article <2493@abaa.UUCP> esker@abaa.UUCP (Lawrence Esker) writes:
>>The Mount program is case dependent on the "Device=" line.  I had many fits
>>on the RAD: device when I used "Device = RamDrive.device".  Mount would not
>>mount the device AND never gave any error messages.  Only thing that worked
>>was "Device = ramdrive.device".
>
>You are absolutely right, but for the wrong reasons.
>It isn't actually mount's fault. It turns out the the operating system must
>find a match between a device or libraries external and internal names. Un-
>fortunately, the match is case sensitive. 
>Almost nowhere else in the system does case matter. But here. It matters.

Quite true, Perry.  In fact, if one tried to do something like:

Atalk3 DEVICE Serial.Device

the device won't open, BUT a subsequent (correct) call:

Atalk3 DEVICE serial.device

will also fail, for the reasons Perry mentioned. At that point only a reboot
will free the device. 

>This should be considered a bug and fixed.

Yep. (I am sending this to cbm, just in case you haven't done so).

-- Marco Papa 'Doc'
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
uucp:...!pollux!papa       BIX:papa       ARPAnet:pollux!papa@oberon.usc.edu
"There's Alpha, Beta, Gamma, Diga and Caligari!" -- Rick Unland
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=