#Sudo cat tee update#

When I do the former I get this output (I've only taken the last three lines): Saving to: ‘STDOUT’Īnd when I do the latter I get the same output just without the 'Cannot write to ‘-’ (Success). Or this: wget -O - | sudo cat /usr/local/bin/youtube-dl One more question when on the subject of using tee like this:Ĭan one not theoretically also replace tee with cat? Like this: wget -O - | sudo cat >/usr/local/bin/youtube-dl Isn't the former string of code superfluous and overly complicated when the latter two completely suffice? And the > operator doesn't work as the files are not writable by my current user. If I've understood correctly the former simply downloads the files and outputs the files being downloaded to standard output which is then piped through tee into the designated file as well as standard output with any additional standard output being redirected to /dev/null. 1,432 4 18 20 2 If you replace the tee with cat >filename, do you get the results that you want sawdust at 23:12 6 cat does not write to files by itself. Is there something particular about using wget with tee that I'm missing here?

Or even for that matter: sudo wget -O /usr/local/bin/youtube-dl What is the difference when comparing with the following?: sudo wget -P /usr/local/bin/ The code being: wget -O - | sudo tee /usr/local/bin/youtube-dl >/dev/null With sudo wget, wget vulnerabilities can be exploited with the elevated privileges. sudo tee command executes wget with regular privileges and uses elevated privileges only to write data into a selected file. It allows you to decrease the attack surface.

#Sudo cat tee update#

So I came across this code for downloading youtube-dl using wget which pipes into tee here: How can I update youtube-dl? The difference is that you don't execute wget with elevated privileges.