Path: utzoo!yunexus!geac!syntron!jtsv16!uunet!mcvax!unido!fauern!faui44!mlelstv From: mlelstv@faui44.informatik.uni-erlangen.de (Michael van Elst ) Newsgroups: comp.sys.amiga Subject: Re: Request to Commodore (Fast File System) Message-ID: <623@faui44.informatik.uni-erlangen.de> Date: 6 Sep 88 12:10:16 GMT Article-I.D.: faui44.623 References: <8808291950.AA12753@cory.Berkeley.EDU> Reply-To: mlelstv@faui44.UUCP (Michael van Elst (kdebugger)) Organization: CSD., University of Erlangen, W - Germany Lines: 30 In article <8808291950.AA12753@cory.Berkeley.EDU> dillon@CORY.BERKELEY.EDU (Matt Dillon) writes: > What I would like to see is an unmount command.... to unmount a >device (i.e. DF0:) then remount it under the new filesystem. Even better, >have the OS detect the disk format (easily done) and use the proper filesystem. > > -Matt I think, the last thing is nearly done in current AmigaDOS. The old filesystem and FastFilesystem use the first long word on sector zero to detect their format, i.e. DOS\0 is old file system, DOS\001 is FFS. If you run two filesystems on the disk they recognize only the right format but you get disk icons with the label DF1:DOS (A invers) if you insert an FFS disk. Nevertheless, the main problem is that disk changing is not recognized by FFS and on the other way OldFS uses the TD_REMOVE call from trackdisk to detect disk changes, and those are overridden if another TD_REMOVE call is made. So both filesystemhandlers have to use TD_ADDCHANGEINT (right name ?). BTW, I have seen a gamma version of 1.3 that has an UMOUNT option with the ASSIGN command. That does not stop the handler for you cannot track down who actually is using the handler. But it removes the DosNode from the device list, so noone can find the handler. I think it would be better to terminate the handler and use a dummy handler that rejects all packets. Michael van Elst E-mail: UUCP: ...seismo!unido!fauern!faui44!mlelstv E-mail: UUCP: ...uunet!unido!fauern!faui44!mlelstv <- when seismo ceases operation