[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- To: neves at MIT-VAX
- From: Mike McMahon <MMCM at MIT-AI>
- Date: Thu ,7 Jan 82 16:14:00 EDT
- Cc: BUG-LISPM at MIT-AI, jekulp at MIT-MC
Date: 5 Jan 1982 16:47:03-EST
From: neves at mit-vax
1. When I tried to ^x^f a file on the Vax while logged into
MC the Lispm asked me to log will name and password or just
password. Because my ITS name is the same as my Unix name I
just typed in my password (carriage return) but the Lispm just
prompted me for my name/password again. Typing both worked.
Are you sure they are the same? Remember that case matters to unix,
so NEVES wouldn't do for neves.
2. When I finally got logged in I tried finding my login file
to test things out. I ^x^fed /usr/neves/.login . The lispm
for some reason wanted to put some file name in front of the
".login" and produced buffer.login I believe. Periods can be
part of Unix file names and don't have the special significance
that they do in Tops-20 (i.e. seperating name and extention).
Well, the lisp machine wants to know about foo.lisp as two separate
components. Leading dots could be part of the filename.
3. I assumed that when I logged in I could access my files by
just typing in their name (i.e. foo) and not the whole pathname
/usr/name/foo. This was not always the case. If had a Vax
file in the buffer then the new file I wanted to find would
have the right default (i.e. if I was editting /usr/neves/bar and
wanted to read in foo I would just ^x^f vx:foo. However if I
had an ITS file in my buffer and tried to read vx:foo I would
get part of the ITS file name in the file I wanted read (i.e.
/neves/foo where neves was the directory of the ITS file I was
looking at. (Perhaps this problem had something to do with
the ".login" case above? I remember trying to read in the .login
file when I was in ITS buffer mode.)
Perhaps you want to change FS:*DEFAULTS-ARE-PER-HOST*?
Defaulting does not work the same way on unix on the lisp machine.