Yes, the file server on EDDIE is broken

[David A. Moon <Moon@SCRC-TENEX>]

    Date: Monday, 1 August 1983, 01:35-EDT
    From: David Vinayak Wallace <Gumby at MIT-EDDIE>
    In ZWEI, Release 4.0, Experimental Macsyma 6.13, site configuration 12, on Zarniwoop:
    (patches are way behind on this machine, so if this has been fixed, sorry).

    I typed C-X C-F .new<end> and it bombed.

    >>Error: Unknown OPEN option.
    (METHOD FS:HOST-UNIT COMMAND): (P.C. = 363)
     (SELF = #<HOST-UNIT 26474402>)
     Arg 0 (OPERATION): COMMAND
     Arg 1 (MARK-P): NIL
     Arg 2 (STREAM-OR-HANDLE): NIL
     Arg 3 (SIMPLE-P): NIL
     Arg 4 (WHOSTATE): "Complete"
     Rest arg (COMMANDS): ("COMPLETE" "" "" " NEW-OK" 215 "//usr//gumby//foo.l" 215 ".news" 215)
     Local 5 (STRING): " ERROR UOO C Unknown OPEN option."

    FS:COMPLETE-CHAOS:  (P.C. = 237)
       Arg 0 (HOST): #<UNIX-CHAOS-HOST MIT-EDDIE>
       Arg 1 (PATHNAME): #<UNIX-PATHNAME "EDDIE: //usr//gumby//foo.l">
       Arg 2 (STRING): ".news"
       Arg 3 (OPTIONS): (NEW-OK)

This is an illegal reply from the file server to a perfectly legitimate
command.  Note that the "unknown OPEN option" message is somewhat bogus
since the command was COMPLETE, not OPEN.

You really should talk to whoever is in charge of software on that VAX
and get them to install a file server that works.  Probably EDDIE is
running some ancient file server that dates back to the days when
completion wasn't implemented on Unix.