Path: utzoo!attcan!uunet!mailrus!cs.utexas.edu!rutgers!mit-eddie!snorkelwacker!ira.uka.de!smurf!nadia!ncc1701!space
From: space@ncc1701.stgt.sub.org (Lars Soltau)
Newsgroups: comp.sys.amiga
Subject: Re: One big assign
Summary: BindNames has one Caveat!
Message-ID: <614@ncc1701.stgt.sub.org>
Date: 27 Jun 90 10:55:23 GMT
References: <sam.646020836@s.ms.uky.edu> <4795@minyos.xx.rmit.oz> <5624@jhunix.HCF.JHU.EDU> <8534@canterbury.ac.nz> <5657@jhunix.HCF.JHU.EDU>
Reply-To: space@ncc1701.stgt.sub.org (Lars Soltau)
Organization: United Federation of Planets
Lines: 28

In article <5657@jhunix.HCF.JHU.EDU> barrett@jhunix.HCF.JHU.EDU (Dan Barrett) writes:
>BindNames looks at a set of configuration files (tables, really), that
>look like "volume directory" pairs.  Here's an example:
>
>               T:              ram:T
>               ENV:            ram:ENV
>               CLIPS:          ram:CLIPS
>               games:          home:games
>               home:           dh0:

While I use BindNames all the time, and really enjoy to have all the assigns
out of the Startup-Sequence, there is one major caveat for you A2090(A) people:

If your boot disk misses one of the "standard" directories, i.e. C, LIBS, DEVS,
FONTS, L (did I miss one?), AmigaDOS creates a shadow volume. Try it out, if
you type "Assign LIST", you get for example "FONTS", listed with no directory.

Since I tend you have my boot disk (or partition) as small as possible, there
is no FONTS directory on it. When BindNames tries to assign FONTS: to a
directory on the FFS partition, the system is halted. No guru, no nothing,
everything just freezes.

Moral: If you use BindNames (which I can only recommend, even with ARP), you
*HAVE* to have all the default directories on your boot disk or boot partition.

--
Lars Soltau     bang: <insert ridiculously long path>   Bix: -- no bucks --
                smart: space@ncc1701.stgt.sub.org