From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <4a2565de133d5ef363789b5fa2ff4bca@centurytel.net> To: 9fans@cse.psu.edu Subject: Re: [9fans] cpu vs ocpu and talking to 9p1 clients. From: "Skip Tavakkolian" MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Date: Mon, 13 Jan 2003 20:52:17 -0800 Topicbox-Message-UUID: 40b62a92-eacb-11e9-9e20-41e7f4b1d025 >> fixed the problem, though I find that I still can't get to /mnt/term, >> (this is from FreeBSD, by the way) which is a major, serious, bummer. > > > see if you can cd to /mnt/term/home/$user directly, or try > cd-ing to /mnt/term/stand for example... > > i had the same problem just yesterday and found that 'du -a' was able > to read /mnt/term while 'ls' was not... If this is the "bad character in file name #/", there is a work-around for it. A variation of one that was suggested a while back, that I use is: cpu% mkdir termdrive # assuming you don't have one already cpu% bind -ac /mnt/term termdrive cpu% lnfs termdrive # optional A message a while back from Russ said that this was a known bug.