Comment by rightbyte
Comment by rightbyte 2 months ago
You'd probably need to put the HD in the other machine.
What is the "scrappy" way to do it?
Comment by rightbyte 2 months ago
You'd probably need to put the HD in the other machine.
What is the "scrappy" way to do it?
Windows has had OpenSSH's ssh/sftp/scp client binaries built in by default for ~7 years now. You can also do this in reverse by enabling OpenSSH Server on Windows (included feature but not installed or enabled on boot by default) and having the sftp client be the Linux box, which can be easier depending which you have more control of.
Or just... put in a usb thumb drive, move the 50gb on it and call it a day?
If you don't have a thumb drive handy you could probably transfer it to your phone and use that instead
I think many (most?) modern phones have that much storage
That is the scrappy way :)
I think sometimes we forget there are plenty of engineers out there whose experience interfacing with a computer begins and ends at the KBM. "Put the HD in the other machine" isn't super obvious to every junior, though I wish it was!
I have been nerd-sniped into conjuring up a less-traveled-path technique:
Portable Python on the Windows computer. `python -m http.server`. On the Linux computer, something like `wget -mkp` followed by `find … -delete` to get rid of the index files.
(Lots of disks are soldered in nowadays, or the procedure might require multiple M2 slots that the destination mobo might not have. Is your company IT department happy to know their hardware is being disassembled?)
I have not benchmarked to see if this would sustain the 120 Mbps the original scenario would require.