Path: utzoo!mnetor!uunet!lll-winken!lll-lcc!ames!elroy!david
From: david@elroy.Jpl.Nasa.Gov (David Robinson)
Newsgroups: comp.unix.wizards
Subject: Re: filenames with the high bit set.
Message-ID: <6173@elroy.Jpl.Nasa.Gov>
Date: 12 Apr 88 08:49:06 GMT
References: <8120010@eecs.nwu.edu> <48993@sun.uucp> <4540@bloom-beacon.MIT.EDU> <49108@sun.uucp>
Organization: Image Analysis Systems Grp, JPL
Lines: 23
Summary: Non Unix?

In article <49108@sun.uucp>, guy@gorodish.Sun.COM (Guy Harris) writes:
< > >(BTW, you *can't* create files that have names with truly arbitrary bytes in
< > >them; '/' and '\0' are not valid in UNIX file names - '/' separates *file*
< > >names in a *path* name, and '\0' terminates a path name.)
< > 
< > If you're running NFS, the NFS _server_ (at least the one we're
< > running here) will let you put `/' in filenames, since it works at the
< > inode & filename level, not the pathname level.
< > 
< That's obviously a bug, not a feature.  You can't create files containing "/"
< by using the official UNIX mechanisms for creating files.

What if the NFS server is not a *Unix* machine?  What if the client
is not a Unix machine?  There is no NFS error to indicate an illegal
file name character!




-- 
	David Robinson		elroy!david@csvax.caltech.edu     ARPA
				david@elroy.jpl.nasa.gov	  ARPA
				{cit-vax,ames}!elroy!david	  UUCP
Disclaimer: No one listens to me anyway!