Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!iuvax!cica!gatech!udel!mmdf
From: Ata@multics.radc.af.mil (John G. Ata)
Newsgroups: comp.sys.amiga
Subject: Re: Re-assigning DF0: to DF1:
Message-ID: <19494@louie.udel.EDU>
Date: 11 Jul 89 20:29:50 GMT
Sender: mmdf@udel.EDU
Lines: 29


    Date:  10 July 1989 17:36 edt
    From:  "Chris (The Home of the Killer Smiley" <crs at CPSC6B.CPSC6A.ATT.COM>
    Subject:  Re: Re-assigning DF0: to DF1:


    Why would AssignDev be necessary?  Wouldn't it work to add a Mountlist
    entry for 'DF1:' that references the same device as DF0:?  This could
    then be mounted, and used as an independent device, much as the example
    from the 1.3 Mountlist for mounting DF2: as DF1:.  If I am missing something,
    then I deserve some serious flaming :-), but it seems to be a simple
    solution.

Have you tried mounting df2:  as df1:  as in the example mentioned?  I
did a while ago and noticed that the system had a hard time tracking
df1:  as the identical device as df2:  Particularly, after mounting
df1:, if you referenced df2:  again, the system would become extermely
confused and would end up in a guru...  Additionally, the info command
would print some very interesting numbers.

    --
    Chris (Insert phrase here) Seaman |    ___-/^\-___      bIyIn nI' je chep.
    crs@cpsc6a.att.com <or>           |  //__--\O/--__\\       (Look it up
    ...!att!cpsc6a!crs                | //             \\        in your
    The Home of the Killer Smiley     | `\             /'   Klingon Dictionary)



                                        John G. Ata