Відео

Related: If your terminal doesn't have a setting to prompt for confirm on multiline paste, change terminals

I often like to put a # before the command so it’s a comment and won’t do anything unless I remove that # again. Also sometimes I use this as a temporary clipboard: When I already typed a long command and remember that I need to execute another command before, put # in front of the long command, execute (now it’s in history and didn’t do anything) write the other command, arrow up twice, remove # and execute that command second.

is there like a way ti make unkiklable binary with maybe forking mecanism on sig kill or somehow ignore sigkill

echo does not always save the day. It does not prevent you from overwriting a file via redirect (>file.na) or execute a second (or later) command in a pipeline. Better use '#', as suggested by @danydanger

I thought you would write all of that without peeking at the other screen…! (Remember you told about that in a reel) But still great content . Really appreciate.

Nice one! When I'm about to reboot or shutdown a server, I do "sleep 5; sudo reboot". This way I have 5 seconds to change my mind. Also I often do "arrow up; enter" immediately after I login to a remote host. Most of the time it's "sudo -u myuser -i", but sometimes it's the reboot command :)

We can write our virus then💀

Hey bro I got a question. Btw love your content. The question: why would I ever whip up a program in C++, as opposed so just using bash to orchestrate a bunch of C binaries that are tried and true? I understand implementing in C++ could be more portable and secure, but let's say I don't care about that. I only care about performance. For example say I have three binaries foo bar and baz that I can compose together. I could 1) implement foo bar and baz in C++ 2) use bash to orchestrate foo bar and baz 3) use c++ and call out to foo bar and baz and orchestrate with c++ for more control Keen for your thoughts on this. Rate the content dude

Else way we do is to put # in front of the command

Gotta admit, the ability to remove duplicated output is pretty clever. It just so happens that I'm also filtering duplicate data with parallel workers. :P Duplicate file finder. I'm porting my Python implementation from a few years ago to C++, which I just started learning earlier this year. Just this month, I finally wrote something faster than my Python implementation. Now I struggle to write it slower. lol You might have given me an idea for a new feature, though, so double thanks!

I did something similar, when I use dd for example I add one char to dd, like dda if=/dev/sdX of=/dev/sdY status=.... And when I review the command many times I remove the a char

He gradually gets cooler

Pure bash TUI isn't actually too bad, dylanaraps has a GitHub page about it and I've personally written a fair few terminal guis in bash

you can also do Ctrl-x Ctrl-e, which will only run the command on exit of the file.

This already existed for literally decades. PDSH it also has a parallel scp for copying files to multiple machines, pdcp. Oh also cexec does it too

Or just start the line with a "#" while you are editing it. And use an alias for things like reboot, poweroff and shutdown alias poweroff='echo "You are on the main \"$HOSTNAME\" server!"' '

This looks useful for big distributed ai training runs

I just type it a notepad

So much better than for item in ${array[@]}

i thought to myself, "why is this guy not getting views man", then i found out this was posted just 18 minutes ago. great work, best wishes, yousuckatprogramming dude.

This is a perfect example of taking all necessary precautions

The Fabric Python package works in a similar fashion

I feel like this is a really early version of Ansible :P

Cool! But it seems that you've just reinvented Ansible, but in C )

This is really cool.

Nice!

Use xargs, n00b

This tool is really neat!

I tend to use nushell for parallel tasks, it handles it like a champ. Since it works with real data that you can pipe and not strings like in bash, you can do really cool things. The key word here is par-each. If I do parallel ssh connections I mostly do the following: open hosts.txt | lines | par-each {|h| let out = (ssh $h dostuff | from json); return {"host": $h, "ret": $out}}

Good content. Anyone notice "parallel" misspelled in the video's thumbnail?

This is a fabulous tool. Thanks for this, Eddy. Sure going to be a standard part of my toolkit going forward :-)

Excellent stuff...would you use this to replace Ansible or something like that to install apps/updates, make config updates etc?

ugo and rwx are WAY easier and usable than octal. add *read* perm for *others* ? chmod o+r. done.

Home depot is fascist, absolute dipshits

I subscribed because I do suck at programming

That comment was way more relatable than it should be considering only recently I gained a random interest in making a desk.

I'd appreciate a full video on this

Yes, the only proper answer is yes

Plot twist: Alice is schizophrenic

Source: trust me! :v

What you explained is TCP, a transport protocol. Not a socket. Both are not the same

The golden man and his golden land preform a song so cool the pixels go away

Where's the song

The guy forgot -R

why not just take 2 mins to actually test it instead of rambling

fr