TIL
TIL
38 comments
-
I assume most of those students weren't "officially" given admin priveleges, which makes it extra funny
-
They may have been, things were far more trusting back then.
X servers, for example, would accept any connections. So we would often "export DISPLAY=friendscomputer:0.0" in the computer lab and then open windows of embarrassing content. Which at the time would likely be ASCII art....
-
One of my favourite wars was to open audio files on other people's SPARCs, somebody had the loudest bag pipe music that usually ended things.
Access to the SPARCs was normally restricted to third year but if you knew the right person you could get an account created pretty easily. Had the fastest access to the internet at the time within the uni as well.
-
Still can. Only a few years ago, I would cat random things to classmates' tty devices.
-
-
-
Little known fact: A Stanford mainframe kept logs of the activities of the 'wheels' in a journal -- the 'journal of the wheels'. Young George Lucas, who briefly attended the university, found that journal, and became fascinated with the 'Wheel Wars'. He later drafted a document that he called 'Journal of the Whills', based largely on what he read on those logs; this is the draft that later became 'Whill Wars', and ultimately, of course, 'Star Wars'.
-
The best part of working in a meat grinder startup were the Linux masters teaching you stuff like
cat /dev/random > /dev/pty23
or
su _otheruser_ chsh -s /bin/false
-
In my freshman year of computer science our main computer lab was filled with Sage IV machines. Basically a Motorola 68k series with 4 or 5 serial terminals. Most people were writing Pascal code or using a simple word processor. But god forbid you were on there with someone taking assembly language. Because they could write really stupid code with super tight loops that never allowed any other code to run, and the only thing you could do was reboot. So if you hadn’t saved your code you were fucked.
So I never purposely wrote really bad code that would overwrite unprotected shared memory with random quotes from Marvin from HHGTG to mess with other people. I would never do that. That would have been unethical and shit… 🤔
I did learn a lot of basic hardware and operating systems though so there’s that.
-
-
We had similar issues and they disabled kicking participants. However, they didn’t disable muting teachers for another week.
-
-
I remember back in college we would abuse the wall command on our shared Linux server so much that IT had to disable it
-
I've always wondered why the admin group is called wheel
-
It's from the phrase "big wheel", meaning a person with a lot of power/influence. Similar to "big cheese"... It would have been better to use "cheese" instead of "wheel" IMO.
-
What if wheel referred to a wheel of cheese? Best of both worlds that way!
-
I always think of it as 'being behind the wheel', which gives control of whatever direction you want to steer into.
-
Pretty sure it's not. I saw something on this topic a few weeks ago but can't quite remember. Iirc, it was a term in an early early OS, where a bit in memory was the privilege but and could be set or unset by turning a real wheel on the computer. This Stück with some people developing UNIX, so they called the wheel group wheel, but none of them are sure who came up with this.
Of course, this is just hearsay.
-
-
-
Brodie Robertson made a video on that recently.
-
Here is an alternative Piped link(s):
https://www.piped.video/watch?v=5vmp6Pg8rWc
Piped is a privacy-respecting open-source alternative frontend to YouTube.
I'm open-source; check me out at GitHub.
-
-
-
Reminds me of the "Op" wars on IRC. All users would be given @ status and the point was to kick everyone before you got kicked. Writing scripts for this was my first "taste" at programming.
-
Reminds me of the test server shenanigans I had at an old job versus a colleague. All in fun. Nothing in production.
One was the faux Bash shell that kind of worked OK until you pushed it or tried to do anything fancy. It was the default shell for the user called "root", but that wasn't the UID 0 user. It had been, but I renamed it. Then created a new "root" with a different UID. Of course, the faux shell would tell "root" that it was UID 0.
The other was the simple background loop that would detect any rival admin sessions and SIGHUP their shell process. First user on the box to run that pretty much had free reign, and everyone else was logged off instantly.
-
Why declare a war over it? Just
sudo sed -i 's/%wheel/$(whoami)/' /etc/sudoersor smth like that
-
got a similar situation in MUDs, someone finds a way to
frobeveryone else up towizardlevel and the whole round of the game just becomes a mess ofshouts
-
$ usermod -G wheel lntli think that's right
-
Need to throw a
-ain there otherwise wheel will be your only extra group.
-
38 comments