Compiling FreeBSD's main branch until then
View attachment 20942
Not even wrong - Wikipedia
en.wikipedia.org
Compiling FreeBSD's main branch until then
View attachment 20942
LOL, this actually happened to me!
Moronic stories like that are unfortunately awfully commonplace in the IT industry. I have stories of my own I can tell. This is what you pay an admin for - to protect important equipment from inside stupidity.In my case at the time I ws working as a sysadmin for a company that owned a few shopping centers and grocery stores, of various sizes. In one of them, seemingly randomly, in the morning we would find that no records were processed and trasmitted during the night and thus thay had to be generated manually.
So, one day I decided to take my car, drive about 300Kms from my office and stay overnight to see if there was something strange to report. So, after the closing time I was sitting there with a cup of coffe in my hand, just like the guy in the comic strip. I actually thought I was alone there but it turned up that I wasn't: there was, imagine that, the butcher still in the store. He saw me and he went like "OK, I'm going home, are you going to turn the power off tonight?" I initially thought he was talking about the light but I asked him what did he mean with that.
It turned out that, as there only were a bunch of employees in the store, there was a schedule of who was in charge of the end-of-day activities, something I and my colleagues in the office did not know. And we were very lucky: it also turned out that the butcher at the end of the day used to switch the lights off by cutting off the power of the entire store! (including fridges, air conditioning and... the server and the router).
Of course I told him not to do that anymore and to tell his colleagues to do the same (it turned out that he was the only one to do that, that's why I said that I was very lucky to stay in the store overnight the exact day that the butcher was also there).
Needless to say, we never had that morning problem again.
and you definitely *need* to observe that stupidity in real life to actually believe how deep that rabbit hole goes. there's no amount of 'war stories' that could prepare a novice to what levels of idiocy you will see out in the field...This is what you pay an admin for - to protect important equipment from inside stupidity.
So true, it looks like a Blade Runner thing but in my 30 years of experience I've seen so many things that I wouldn't believe if they hadn't happened just in front of me. I have to say that in the last decade or so really weird things are becoming less common in my experience.and you definitely *need* to observe that stupidity in real life to actually believe how deep that rabbit hole goes. there's no amount of 'war stories' that could prepare a novice to what levels of idiocy you will see out in the field...
The saying "make it idiot proof and the world will make a better idiot" isn't just a joke.
hacked
! I was once accused of hacking for - wait for it...One department on our university had a bad admin. The pseudo terminals were world writable, so you could send bell characters to people working on the same machine. When people got on your nerves, the shutdown message would appear on their screen - and they would log out and leave. Good times.running who(1) during an SSH session on my school's Sun Solaris server! I recognized some people's UNIX login names and sessions on other TTYs, and next day, asked them how their homework went (compiling helloworld.c for a freshman-level C programming class).
Each class at school typically was supported by a different (minicomputer-based) system running software (OS + apps) typically written by grad students working for said professor.One department on our university had a bad admin. The pseudo terminals were world writable, so you could send bell characters to people working on the same machine. When people got on your nerves, the shutdown message would appear on their screen - and they would log out and leave. Good times.
Well, you do know about "blanket party", don't you? This would have made you wear running shoes all year around.Followed by groans. :>
Our "hacks" were always at the intellectual level. Messing with another person's head instead of his body. It's hard to explain-away a physical attack. But, psychological attacks are hard to prove or attribute to a particular individual!Well, you do know about "blanket party", don't you? This would have made you wear running shoes all year around.
Well, crashing the system (requiring an admin to come reboot it) is annoying when the admins are grad students just babysitting the system as a "side job" (they are more interested in pursuing their degrees than baysitting undergrads). Doubly so when you consider the reason for the crash was an exploited BUG in code that the admin (or one of his peers) likely wrote! So, add THAT to their "ToDo List"!And you gotta mess with the admins as well. As one user was asking what that message meant that came every few minutes
"Solaris Kernel : It hurts when you do that. Stop doing that."
My education predated postscript and other PDLs (and PCs, for that matter).Or you put a PCL command into your PDF which changes the translation texts in a printer, so instead of "Waiting for data" it would from then on read "I crave blood".
IBM Fortran H, iirc. My dad once almost went Sgt Hartman when he discovered his "variable" PI.I do recall being able to assign new values to *constants* in the FORTRAN (?) compiler. Interesting bug to chase down!
I once used talk(1) to say hello to someone who I knew to be an admin. The guy was logged in on another TTY on the same school server. Turns out he was at a huge conference doing some kind of demo, and my greeting flashed on a huge screen for everyone in the auditorium to see!And you gotta mess with the admins as well.
That's one of the first rules I learned in the new-fangled way of doing "structured programming": Instead of using the value of pi as 3.14159... all over the code, you declare a constant PI =3.14159... at the top of the program once. Like that, it's easier to update the code when pi changes.IBM Fortran H, iirc. My dad once almost went Sgt Hartman when he discovered his "variable" PI.
You mean that attempt to change it by law?when pi changes.
In my first commercial product, this was essential! The 24b floating point package (that *we* wrote) had no notion of "decimal vloating point values".it's easier to update the code when pi changes.
This made me LOL for realz...That's one of the first rules I learned in the new-fangled way of doing "structured programming": Instead of using the value of pi as 3.14159... all over the code, you declare a constant PI =3.14159... at the top of the program once. Like that, it's easier to update the code when pi changes.