On and off for the last month or so I have been trying to get a bunch of
old NCD X terminals to function with Linux. I have now reached the point of
concluding that this is a little beyond me, and I would dearly love a
little help from someone with a bit more experience in this area.
        The X terminals are all using the NCD boot Monitor v2.1.1 or v2.3 and
while they support TFTP, they do not appear to speak/understand BOOTP or
DHCP. My impression is that it there are three solutions to this, one
should be able to:
(1) Update the boot PROM in the X terminals to a more recent version which
speaks DHCP.

(2) Manually configure the IP information for the X terminals and boot them
through TFTP.

(3) Let the terminals configure themselves based on a working MOP server on
the network.

I ran into a brick wall on (1) because NCD will (apparently) not admit to
ever having made something that didn't speak BOOTP and will not support
these terminals, and (2) is a problem due to a lack of documentation (there
is NO documentation with them) and no clear way of configuring addresses
from the Boot Monitor prompt, which left me with (3). I managed to locate a
version of the mopd-linux package which would actually run on my systems
(the RPM version from Powertools 6.2 installs on Redhat 6.1), but it's (2
pages) of documentation seems to indicate that it is able to work as a
substitute for TFTP, and gives no indication of how MOP can be used (as
these X terminals appear to want to use it) as a substitute for BOOTP.
        Is anyone out there running old NCD X terminals without BOOTP from an x86
machine? If so, what software are you using and how?
--

Who is this General Failure, and why is he reading my hard disk?


-- 
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.

Reply via email to