Right click increase the temp of the touchpad, which the user has macroed as an "Enter"input, letting him press enter with all fingers on home row and just resting the palm on the touch pad
That's not how randomness works. You would want to randomize once, saving the number of steps remaining until the bullet is the next shot, decrementing the number of steps for each try.
Fun fact there was a guy a little over a decade ago who got drunk and traded 7m barrels of oil futures. Not dollars, barrels. He made the price of oil jump up for a short while.
But I do remember a story (on daily wtf) where a lady bought coal futures and somehow forgot or didn't manage to sell, and a coal barge turned up in the river behind her office!
A future means that they will be created at some point in the future. Basically its an agreement to buy for a certain price in the future regardless of what the markets are doing.
Yes you said exactly that in the comment I replied to, I never argued against it I was just adding onto it. We both were talking about how unrealistic the comment further above yours was.
On ye olde hpux this would work, especially when you did rm-fr /$var and $var was unset and nobody unit tested their shell back then. That db server ran for 2 days though with open file handles before it finally died.
Scene : 1998, Fort Bragg 18th Support Something-or-other, IT department
Date: 11th day of the month sometime before summer. Let's assume May.
Young Specialist looks at wall clock. Looks at time on the system. "I can fix that!"
Should I man date first? Fuck that, let's just do it!
Proceeds to set the time in the HP Unix minicomputer that handled all supply orders for the non Special Operations side of Fort Bragg.
Oops, set date to November 5th but with the correct time. No problem, we'll just run that date command again and flip the 5 and the 11 around. All fixed! Back to May 11th.
Comes into work the next day wondering why everyone is running around like crazy. All the processes have kicked off and are waiting for November to run again.
Ut-oh. Comes clean to NCOIC.
Aftermath: root was taken from all junior enlisted (good move) and only Staff Sergeants and above had it l. Oh, also the outside IT professional/Army civilian I assume.
Young Specialist gets written counseling (which was bullshit BTW- I made an honest mistake) and not UCMJ supposedly because I was going off to Kuwait for PCS (Permanent Change of Station) soon. Not allowed back on system.
Disclaimer: might have happened in June but either way I'm pretty sure I set the date to November and I know I got the date command order wrong at least once.
Are you sure it doesn't work on zsh? It's valid POSIX shell code, and like bash, zsh is a superset of POSIX, at least if I remember correctly.
This is not to goad you into destroying your filesystem. Replace the rm with something relatively harmless like echo "BANG! You're dead!" if you decide to test it.
Key here is the outer [] and interaction of $[], test doesn't have == by default in standard posix, so no this isn't posix shell or bourne compatible. Tis but another bashism. I could probably force zsh into a more bourne mode to try it but its definitely not portable bourne shell its bash.
$ [ $[ $RANDOM % 6 ] == 0 ] && echo rm || echo ok
zsh: = not found
$ zsh --version
zsh 5.9 (x86_64-pc-linux-gnu)
== should be -eq for this to be posix/bourne portable, you could use = but -eq is for numeric comparisons so not quite right.
Depends on the terminal I think. Pretty sure KDE's Konsole warns you that commands may be run when pasting something with newlines, but still allows it.
There is an exploit which addresses copy pasting things in terminal. Where you'd copy one thing, but when pasting you get more than you bargained for. Any decent terminal would ignore \n for this reason or at least not treat it as pressing enter.
Well they did have the type the command, and to do that they would first have to navigate to the terminal (assuming the machine isn't running just a plain tty) first.
