No subject

1). UUCP launches dialer

Sort of - there's a script language that looks kinda like a bunch of 'expect' commands

2). Remote system answers

Inshallah.

3). Remote system gives login prompt and UUCP logs in as UUCP (is this what happens?)

Usually if you have multiple users you each has a login name starting with U (this is convention only)
,
4). UUCP on initiating system talks with UUCP's "shell" given after login on remote system.

If you're connecting over port 540 (i.e. uucico is invoked by inetd directly), the receiving system sends an Shere <system name> message to which the sending system sends it's own UUCP name.


Am I missing any (major) steps?

Not that I am aware of.


(Also, UUCP would want to dial would it not?   Would it be easier to implement a custom "dialer" that just opens the device in /dev and doesn't send any AT commands, or do some UUCP implementations implement this feature already? The initial test would likely occur between two 4.3BSD instances.)


The "dialling" part is done with scripts - if you just hack it together so the uucico\s just talk to each other, no "dialling" or authentication need to take place.