Path: utzoo!mnetor!uunet!seismo!sundc!pitstop!sun!gorodish!guy
From: guy@gorodish.Sun.COM (Guy Harris)
Newsgroups: comp.unix.wizards
Subject: Re: filenames with the high bit set.
Message-ID: <49108@sun.uucp>
Date: 11 Apr 88 22:08:24 GMT
References: <8120010@eecs.nwu.edu> <48993@sun.uucp> <4540@bloom-beacon.MIT.EDU>
Sender: news@sun.uucp
Lines: 18

> >(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.)
> 
> Yes, but...
> 
> 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.
> 
> To get it to do this, you have to write a user-level program which
> sends RPC requests directly to the NFS server.
> 
> Of course, you then have to write another one to get rid of it, or
> resort to using clri.

That's obviously a bug, not a feature.  You can't create files containing "/"
by using the official UNIX mechanisms for creating files.