Been using UNIX since the late 80s; Linux since the mid-90s; virtualization since the early 2000s and spent the past few years working in the cloud space.
Location
Alexandria, VA, USA
Education
B.S. Psychology from Pennsylvania State University
A really effective prank is setting the init-default to 0.
I did that to an annoying co-worker back in the early 2000s. They ended up calling out the hardware vendor to come fix their workstation. Obviously, since it was an OS-level setting, when the FE replaced the "faulty" power module, it didn't fix the problem. It apparently occurred to neither of them that there might be a problem with the OS (in defense of the FE, he was just a hardware-monkey; but the workstation owner was an SA and should have thought to boot off of media so he could mount the boot drive and examine the logs), so, the FE ended up replacing the entire workstation.
On the plus side, because our employer had a platinum service contract, the dispatch of the FE and the replacement of the workstation was essentially "free".
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
A really effective prank is setting the init-default to 0.
I did that to an annoying co-worker back in the early 2000s. They ended up calling out the hardware vendor to come fix their workstation. Obviously, since it was an OS-level setting, when the FE replaced the "faulty" power module, it didn't fix the problem. It apparently occurred to neither of them that there might be a problem with the OS (in defense of the FE, he was just a hardware-monkey; but the workstation owner was an SA and should have thought to boot off of media so he could mount the boot drive and examine the logs), so, the FE ended up replacing the entire workstation.
On the plus side, because our employer had a platinum service contract, the dispatch of the FE and the replacement of the workstation was essentially "free".