Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!ames!oliveb!amiga!cbmvax!andy
From: andy@cbmvax.UUCP (Andy Finkel)
Newsgroups: comp.sys.amiga
Subject: Re: Request to Commodore (Fast File System)
Message-ID: <4612@cbmvax.UUCP>
Date: 31 Aug 88 16:14:54 GMT
References: <8808291950.AA12753@cory.Berkeley.EDU> <4604@cbmvax.UUCP>
Reply-To: andy@cbmvax.UUCP (Andy Finkel)
Organization: Commodore Technology, West Chester, PA
Lines: 29

In article <4604@cbmvax.UUCP> daveh@cbmvax.UUCP (Dave Haynie) writes:
>in article <8808291950.AA12753@cory.Berkeley.EDU>, dillon@CORY.BERKELEY.EDU (Matt Dillon) says:
>> 	What I would like to see is an unmount command.... to unmount a 

>You mean like 1.3's "Assign UNMOUNT DF0:" 

Well, actually, no.  That particular option of the assign command
(which was renamed REMOVE to avoid just this kind of confusion)
just lets you remove handlers and filesystems from the assign list
(you can do the same thing with AssignDev) as a developer tool.
(otherwise developing handlers and filesystems takes a lot of rebooting).
The device being removed doesn't give up any of its resources.

If I were using it to play dismount type of games, I'd inhibit the
drive first, then remove it.

A real dismount has to be implemented through a new packet; since
one of the reasons that you want to dismount a handler or filesystem
is so it gives up its resources.

		andy
-- 
andy finkel		{uunet|rutgers|amiga}!cbmvax!andy
Commodore-Amiga, Inc.

"If we can't fix it, it ain't broke."

Any expressed opinions are mine; but feel free to share.
I disclaim all responsibilities, all shapes, all sizes, all colors.