Jeff mentions:
> >
> > Could I ask for one exception to this rule? I'd like to have a rule that says
> > that no HFS syntax name on MPE can begin with a $....
>
> I am interested in feedback on this exception.  Do we need to restrict $
>from the beginning of all filenames, or can we say that we have certain
> reserved filenames, like: $NULL, $OLDPASS, $NEWPASS, $STDLIST, $STDIN, $STDINX,
> $STDERR, and $<some directory names>?

ok...bad idea!


Remember the purpose of this change: we have users on Win95/WinNT machines (and others),
who don't care *what* characters are in their filenames...and in some cases, have
absolutely no control over the filenames.  (On our RS6000, for example, one file
starts with a "$".)

On my local WinNT machine, 5 files start with "$":

   $$
   $OEM$
   $LDR$
   $winnt$.inf
   $WIN_NT$.~BT

I'd hate to have to tell a user that if they'd done a "cd" to a directory on their
PC, and then tried to backup the files in that directory into a similarly named
directory on the 3000 (via samba), that they'd lose some of the file names
(absent some renaming-mechanism, of course).

--
Stan Sieler                                          [log in to unmask]
                                     http://www.allegro.com/sieler.html