1 Aug
2006
1 Aug
'06
12:12 p.m.
Kevin Handy wrote:
Sellam Ismail wrote:
Can't you build a tarball and cat it to the printer port
(there are tools that will let you configure another machine
to *capture* data from the printer port). No, not PLIP, etc.
This would be an open-loop process... you just push the data
and *expect* the other device to capture it all correctly.
Serial port has the adantage of being unattended -- but slow.
I suspect you won't find support for anything above 19.2K (?)
depending on the vintage of the OS.
Another option would be to dd(1) a tarball to a *second*
RAW disk (and hope it numbers blocks the same as the "other"
machine that you later move the drive to). This is quick
and relatively painless to try (1MB at 19.2K will take you
~10 minutes depending on protocol overhead; 60MB will
obviously take even longer :> ). Swapping a drive in and
out should take less than an hour start to finish
(been there -- too often! -- done that...)
Sorry for the OT posting, but I figure I'd
find some qualified Unix
techs here. I have a client in the Springfield, Missouri area that
needs to get some data off of a very old SCO unix box. The box is not
interconnected with anything else, and the only means to get data
off--an old Irwin 60MB tape drive, went bad. I figure there would be
a simple way to get the data off the hard disk, by either mounting it
into a Linux box or adding an external drive to the SCO box via SCSI
(though I'm not sure if it has a SCSI interface...in fact I know next
to nothing about the box currently).
You could always try 'kermit' through a serial line.
Slow, but it should work. Might be faster and safer than mucking
about with assorted hardware.
Another serial option might be 'uucp', or related programs.