something from 1978 using an 8080A. It shows how
The LA120 was the de facto console terminal for the VAX-11/78*s. One reason
why I have three; albeit, one has been cannibalized for parts.
--
VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)ORG
Well I speak to machines with the voice of humanity.
I'm fairly certain (though have not verified) that the ONLY interface
available on the LA120 family is serial. The LA180 uses a much more
system-friendly LP[v]11 or LS11 interface. That may be the
difference...target market, etc.
RS-232 and 20mA current loop. I saw nothing about parallel in the docs.
-Dave
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
to run OpenVMS X11 apps on my 17" MacBookPro OS X 10.5.8 after launching X
server on the Mac and setting security preferences to allow network clients.
$ SET DISPLAY/CREATE/NODE=192.168.2.100/TRANSPORT=TCPIP
$ MCR DECW$PUZZLE
You *may* need to set your X server security preference to NOT authenticate
the connection. Restart X11 on your Mac if you disable authentication.
Doing an xhost + basically disables any authentication. But he is
tunneling X over SSH, which in itself might cause interesting effects
here. Not sure why he wants to do that, but anyway.
In that case, the questions I asked about architecture, VMS version and
TCPIP are even more import.
--
VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)ORG
Well I speak to machines with the voice of humanity.
After running X -ac from a terminal window (X was closed before) I was able to use SET DISPLAY/CREATE/... and then RUN without problems. I did not connect with ssh -X or ssh -Y (in fact, being on a "secure" LAN, I used telnet)
I am aware that it is not the best policy to simply run an X server without any authentication on any network; but I think it would at least be useful for some diagnostics.
to run OpenVMS X11 apps on my 17" MacBookPro OS X 10.5.8 after launching X
server on the Mac and setting security preferences to allow network clients.
$ SET DISPLAY/CREATE/NODE=192.168.2.100/TRANSPORT=TCPIP
$ MCR DECW$PUZZLE
You *may* need to set your X server security preference to NOT authenticate
the connection. Restart X11 on your Mac if you disable authentication.
Doing an xhost + basically disables any authentication. But he is
tunneling X over SSH, which in itself might cause interesting effects
here. Not sure why he wants to do that, but anyway.
In that case, the questions I asked about architecture, VMS version and
TCPIP are even more import.
--
VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)ORG
Well I speak to machines with the voice of humanity.
to run OpenVMS X11 apps on my 17" MacBookPro OS X 10.5.8 after launching X
server on the Mac and setting security preferences to allow network clients.
$ SET DISPLAY/CREATE/NODE=192.168.2.100/TRANSPORT=TCPIP
$ MCR DECW$PUZZLE
You *may* need to set your X server security preference to NOT authenticate
the connection. Restart X11 on your Mac if you disable authentication.
Doing an xhost + basically disables any authentication. But he is tunneling X over SSH, which in itself might cause interesting effects here. Not sure why he wants to do that, but anyway.
Sampsa, try what Brian suggested, in actually talking X directly over TCP/IP instead, and see if that don't work better perhaps?
Also, could you report what your display is actually set to when you ssh in?
Johnny
to run OpenVMS X11 apps on my 17" MacBookPro OS X 10.5.8 after launching X
server on the Mac and setting security preferences to allow network clients.
$ SET DISPLAY/CREATE/NODE=192.168.2.100/TRANSPORT=TCPIP
$ MCR DECW$PUZZLE
You *may* need to set your X server security preference to NOT authenticate
the connection. Restart X11 on your Mac if you disable authentication.
--
VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)ORG
Well I speak to machines with the voice of humanity.
s there any way to make the NTY session show up as REMOTE instead of LOCAL?
Yes, a kernel variable needs to be set by the following command:
$ MULTINET SET/KERNEL NETWORK_PTY_IS_REMOTE 1
This command has to be executed each time MultiNet is started. If it
exists, MultiNet executes the file MULTINET:LOCAL_INITIALIZATION.COM
after starting. You can add the SET/KERNEL command to the file if it
already exists, or create the file and add the SET/KERNEL command if
the file does not already exist.
--
VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)ORG
Well I speak to machines with the voice of humanity.
So, for noone to be able to delete a file, you need to not have the D set in the protection mask, and also, the owner of the file needs to be someone else, or else people can always change the protection to allow the deletion.
All that said, the same applies for modifying a file. For that you need write access.
Now, there is no way for you to allow people to create files remotely on your machine without them also having write access to the files. And besides, naturally they will be the owners of the files if they create them.
The best I can think of here is to just set a default protection so that newly created files at least by default have a protection that don't include D (and possibly exclude both E and W as well).
The second part of this is actually making the files visible in the specific library. For this users need write access to the directory (and possibly extend access). In order to find the files, you need read access. For removing files from a directory, you need write access to the directory.
So obviously, you either allow both entering and removing, or neither.
Johnny
