←back to thread

Pipe Viewer – A Unix Utility You Should Know About

(catonmat.net)
236 points lnyan | 1 comments | 20 Nov 24 15:09 UTC | HN request time: 0.205s | source
Show context
emptiestplace ◴[20 Nov 24 19:28 UTC] No.42197265[source]▶
> The obvious way to do it is:

> $ gzip -c access.log > access.log.gz

Is it?

replies(1): >>42199308 #
zoky ◴[20 Nov 24 23:36 UTC] No.42199308[source]▶
I mean, if you’re the type of person who considers using tar and nc to be the obvious way to transfer a directory between two computers…
replies(1): >>42200575 #
vbezhenar ◴[21 Nov 24 02:44 UTC] No.42200575[source]▶
I might be weird, but for me the most obvious way to transfer a small directory is to do

    tar -cz dir | base64
Copy output into clipboard

    base64 -d | tar -xz
Paste from clipboard into input

Works flawlessly to move configs and stuff between servers.

I actually love the blend between terminal and GUI. For this example I'm using CLI tools to produce text and I'm using GUI to scroll, select and copy&paste the text between two terminal tabs. I wish developers put more emphasis on empowering terminal with GUI capabilities.

replies(2): >>42201381 #>>42201805 #
1. zoky ◴[21 Nov 24 05:20 UTC] No.42201381[source]▶
Under certain circumstances, like where machines are not directly accessible to each other and you’re only able to connect by Remote Desktop or something, that’s not actually bad way to do that. But for machines that are on the same network, using a weird invocation of tar and nc instead of just using, say, rsync is an odd choice. And for machines connected to each other over the Internet, it’s positively insane.