| 1 |
On 2021-04-25, Grant Taylor <gtaylor@×××××××××××××××××××××.net> wrote: |
| 2 |
|
| 3 |
>> It is usually simple to setup and use a serial null-modem cable and |
| 4 |
>> run kermit or somthing on the MS-Win side and add a getty (I've used |
| 5 |
>> mgetty) handling the serial port on the linux side. |
| 6 |
> |
| 7 |
> Is it wrong that the first thing that came to mind when reading the OP's |
| 8 |
> post is UUCP with as high speed serial as possible? |
| 9 |
|
| 10 |
Nope. Many years ago I used UUCP a number of times for "production" |
| 11 |
projects involving data gathering from remote systems via |
| 12 |
dial-up. 25+ years ago, I wrote an article about one of those projects |
| 13 |
for Linux Journal. |
| 14 |
|
| 15 |
UUCP would work a treat for the problem I initially posed. Back in |
| 16 |
the day, I always used Taylor-UUCP, and I'm pretty sure I could get it |
| 17 |
working again on Linux, but I have little confidence I could get it |
| 18 |
working on Win10. I'd probably have better luck with Kermit. |
| 19 |
|
| 20 |
> I wonder if the USB LapLink (type) cable or USB On The Go gadget cables |
| 21 |
> could present as a multi-megabit serial interface. |
| 22 |
|
| 23 |
It turns out the initial requirements that I was given were wrong, and |
| 24 |
the Windows machine does have some limited Internet access via a VPN |
| 25 |
and proxy, and I can get files to/from the Windows machine that way. |
| 26 |
|
| 27 |
So my initial question is moot. |
| 28 |
|
| 29 |
-- |
| 30 |
Grant |
Archives