Path: utzoo!utgpu!attcan!uunet!husc6!mailrus!cornell!uw-beaver!microsoft!ricom
From: ricom@microsoft.UUCP (Rico Mariani)
Newsgroups: comp.sys.amiga
Subject: Re: PATH:
Message-ID: <1081@microsoft.UUCP>
Date: 20 Oct 88 19:54:05 GMT
References: <2867@sugar.uu.net>
Reply-To: ricom@microsoft.UUCP (Rico Mariani)
Organization: Microsoft Corp., Redmond WA
Lines: 38

In article <2867@sugar.uu.net> peter@sugar.uu.net (Peter da Silva) writes:
>Alas, but Rico Mariani's PATH: device doesn't work for me as a replacement for
>the PATH kludge in AmigaDOS.
>
>(edit mountlist, install path-handler)
>1> mount PATH:
>(system still up, a good sign!)
>
>I note that I can create normal subdirectories in PATH: as well as create
>files. It's still a fully functional RAM disk... a nice feature.
>
>(after creating path:s containing sys:s and sys:devs)

Do you have the trailing / on the names in the path: device?  You must have 

sys:s/
sys:devs/

In the file.  Yes I know I could have tested to make sure that the path
ended in a / and put one there if it didn't but then what about

df0

should it become df0: or df0/.  Or what if it's a virtual volume like
My_fair_volume

Then what?  Do I add a : or a / ???

Well, I punted on the whole issue by insisting that there be a '/' at
the end.

Matt seems to have uncovered a possible startup problem in the path:
device.  So in order for things to work (until I fix it).  Do a
mount path: followed by cd path: and the startup will go well.  Everything
is fine from there, it's only a startup problem.  Sorry but this is
a use at your own risk release after all...

	-Rico