cottrell@nbs-vms.ARPA (02/12/85)
/* > Why do you enclose your postings in /* */? Just curious. > > Peace > > Josh Knight, IBM T.J. Watson Research > josh at YKTVMX on BITNET, josh.yktvmx.ibm on CSnet, > ...!philabs!v1!josh Most people include a little snack for the line eater and a cute little signoff line. Since what I write are `comments', it seems appropriate to include them in /**/. You will know I have switched to Pascal when you see my messages enclosed in (* *) (and when hell freezes over) (oops, better check with my censor at Princeton). Also, if the `/*' is missing, you can assume my entire message didn't make it. */
cottrell@nbs-vms.ARPA (03/05/85)
/* > P.S. I've asked about this before, without any response: Does anyone have > a simple (repeat simple) file-transfer method across RS-232 lines? The > ideal would be a pair of programs, a writer and a reader, which have the > property that the reader can easily be typed in to the target system and > then a few files (including the source for the writer) can be transferred > across the line in a highly-reliable manner. I have been using two `tee' processes to xfer files between V6 & 4.2BSD. Logon to the destination machine, pick a non-login port & stty it to the proper baud rate, raw, tabs, no echo, & tandem if you have it. Connect a cross-cable (null modem) from this port to the source machine. Type `tee file < /dev/ttyxx & tee > /dev/ttyxx'. You are now running a poor man's `cu'. Sounds gross, but it works (only on ascii files). You might want to write a program that cuts up the output of something like `more *.c'. Good luck! jim cottrell@nbs */