On Sat, 27 Oct 2012, Tom Sparks wrote:
From: Tothwolf <tothwolf at concentric.net>
Ok, having re-read the entire thread, I have a
better idea of what you
are after.
For printing, I used a multi-port parallel autoswitch with its inputs
connected to the different computers I wanted to print from.
<snip>
I hoping to use ethernet hardware, so I can use power over ethernet, ATA
over ethernet, KVM over ip, Audio over ethernet etc
IMO, you are getting way ahead of yourself. AFAIK, the Lantronix UDS10
doesn't support PoE anyway. In fact, I don't think /any/ of their older
(read: halfway affordable) devices support PoE. As far as KVM over IP
goes, that's a whole 'nother ball of wax...
As for serial
connections, if you just wanted to use the machines as
terminals, a basic terminal server would do the job,
so a shell account is doable :)
but since you also want to be able to transfer
files, you'd need
something more flexible.
what about Zmodem for basic file transfer?
Software for many classic machines may not have support for Zmodem since
it was one of the later protocols. Some may support protocols such as
Xmodem or Kermit, but may or may not support proper CRC checking. On the
Linux machine, lrzsz and ckermit will support these.
Standalone
serial device servers such as the Lantronix UDS10 probably
aren't going to do what you want (or at least not easily) if you want
to transfer files and data between the classic system and the Linux
computer. For inbound telnet connections /to/ a system, devices such as
the UDS10 can work pretty well though.
when I am in serial mode I can only talk to CUPS/lpd
when I am in modem mode I can "dail-into" a shell account, BBS , PPP etc
i've contacted lantronix, to see if the could add auto-switch mode to
the firmware
Good luck. Unless you have a support contract, Lantronix is highly
unlikely to add a feature to unsupported / "legacy" devices. They are
trying to target wireless stuff these days. Keep in mind that Lantronix
also only provides Windows drivers for port redirection with their serial
devices. Again, for inbound connections, something like the UDS10 can work
well, but for outbound, you'll probably be rather disappointed.
Based on my own experience I'd recommend using parallel where you can for
sending print jobs out to the Linux machine and save serial for outgoing
connections from and data transfers to/from the classic hardware. If you
need to remotely locate your printers, have the Linux machine talk to
print server devices near your printers. If the Linux machine is close to
the printers and you don't have very many printers, skip the ethernet
print servers entirely and save yourself the trouble and headaches they
absolutely /will/ cause.