Interesting. I've not gotten it working yet but I thought it was possible.
I've gotten the kernel ready on parallel/serial support.
The terminal is set towards vt100 emulation & the getty lines are set.
I'm glad those inittab lines were mentioned because that was a big part of my confusion;
etc/inittab
# /sbin/getty invocations for the runlevels.
# The "id" field MUST be the same as the last
# characters of the device (after "tty").
# Format:
### I'll try with 2 & 5.
# <id>:<runlevels>:<action>:<process>
#1:12345:respawn:/sbin/getty 38400 tty1
2:2345:respawn:/sbin/getty 38400 tty2
#3:2345:respawn:/sbin/getty 38400 tty3
#4:2345:respawn:/sbin/getty 38400 tty4
5:2345:respawn:/sbin/getty 38400 tty5
#6:2345:respawn:/sbin/getty 38400 tty6
# Example how to put a getty on a serial line (for a terminal)
### I'll try both.
T0:23:respawn:/sbin/getty -L ttyS0 9600 vt100
T1:23:respawn:/sbin/getty -L ttyS1 9600 vt100
I've read that >setserial can be a deciding factor with this style networking
but for now I'll experiment with inittab.
Concerning the crossover cable, these ModTaps look like this male side;
0, no pin: 1, pin
1-13= 0111111100000
14-25= 000000101000
I'm alsmost certain this qualifies as a null modem/cross over cable, but I might be way off about it. The vt420 and vt320 are close, this also has the tab off center.
There are multiple slots with the tab like this, one for the printer, keyboard,
one for this adapter connection, and one for something else. That one has an icon with
two arrows going in opposite directions, maybe if the adapter doesn't allow from the term's Comm port I could try this other port without the adapter(the Linux end still connected by modtap).
This is an interesting project. I appreciate the input
.