Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!uunet!seismo!sundc!pitstop!sun!decwrl!ucbvax!DDATHD21.BITNET!XBR2D96D From: XBR2D96D@DDATHD21.BITNET (Knobi der Rechnerschrat) Newsgroups: comp.sys.sgi Subject: NFS problems and RE:RE:VT100/Keyboard Message-ID: <8711042328.aa12082@SMOKE.BRL.ARPA> Date: Thu, 5-Nov-87 01:30:00 EST Article-I.D.: SMOKE.8711042328.aa12082 Posted: Thu Nov 5 01:30:00 1987 Date-Received: Sat, 7-Nov-87 18:58:39 EST Sender: daemon@ucbvax.BERKELEY.EDU Organization: The ARPA Internet Lines: 51 Hallo, First in my posting, I have a serious problem. We are running three IRIS 31xx on an ethernet with TCP/IP and NFS. We have Rev. 3.5r1 of the software (Rev. 1.00 of NFS). On one machine we have a Fujitsu Eagle which is local (EFS) to that machine and a NFS-disk to the remaining two stations. Beside a few/lot problems we have encountered with NFS (dbx, graphics, priority, etc., all posted month ago) I yesterday traced another bug (as I assume): Some programs (e.g. good old Kermit) do wild card expansions in their code. Due to the lack of existing routines the do it by their own (see the "expand" modules in Kermit). They use (due to the lack of BSD like opendir/closedir routines) open and read statement to access the directory files (which are told to be "normal" files with the exeption that you cannot write them). Now the problem: with the EFS directories everything works fine, with the NFS directories everything I get from read seems to be junk. Result: I cannot use Kermit to do wildcard get/send's on the NFS disks. Is this a problem/bug or feature? Is this known? Will this be fixed in the next (3.6) release? (Sorry for the DEC slang) Second: I would like to thank Michael Toy for his reply to my posting from last week. I'm unfortunately unable to reply directly. Michael: I didn't know that a 24x80 wsh window is a vt100 emulator (what about the (* flame again *) keyboard?). I had that machine only for four days and couldn't discover all new features. And again: Is there a PD VT100 emulator for the 31xx console? Concerning the keyboard, I dont't complain that much about the physical layout. I can live with 17 keys on they keypad instead of the "standard" 18. But what I hate are the (* flame *) ESC sequences that are generated by that child of IBM compatibility (* general flame: Is having a three letter abrevation for the companies name not compatible enough ??? *). Is there a easy way to remap that sequences to a more handy set? If the ad's say: "Just recompile the 31xx code and enjoy" this should not only be (almost) true for the graphics, but also for the lower classes of applications. And the 4D keyboard is INCOMPATIBLE to the 31xx. Regards Martin Knoblauch TH-Darmstadt Dept. Physical Chemistry 1 Petersenstrasse 20 D-6100 Darmstadt West-Germany BITNET: