anything that wasn't possible to revert in a hurry open MS Paint and draw something (those pranks weren't necessarily small, we got three huge monitors side by side on those workstations) change Spotify playlist from rock to childrens songs or rickroll or something innocent videos (annoying videos for toddlers etc) I'd almost recommend that policy for some places. I'm sure there's pent-up demand just waiting for one!Īt some place I worked there was a policy that a small prank was allowed if the workstation was not locked when someone left. However, I've been toying around with the idea of eventually writing a minimal 'vi' clone that you cannot exit. It has been an incredibly handy skill: I never use vi for anything larger but these days I actually do 'vi /etc/fstab' myself instead of calling for emacsclient. So instead of just learning :q and figuring out how to make the particular program or script relaunch another editor I thought it's the path of least resistance to just edit with vi directly. Every once in a while another application brought up 'vi' for some reason (maybe I lost VISUAL or EDITOR while sudoing or the app was looking for another variable) and I could never exit the damn thing. Stretching your fingers between ctrl and b (the default prefix key) merely made me wonder who the heck thought of something like this?Īs for vi, I made a point of learning to use it enough to do useful work editing config files and small texts. It's in a handy location next to ctrl and I very rarely use suspend anyway (which is still available as easily as C-z z). And I probably use a few hundred execute-extended-command calls for each kill-emacs (which I now have to type manually as 'C-x C-c kill-emacs' - no problemo).Ī similar optimisation was with tmux to bind the prefix to C-z. It was way too easy to (even accidentally!) kill emacs with a sweep of a finger. In the opposing vein, as an Emacs user the best configuration I ever made was to rebind C-x C-c to execute-extended-command instead of kill-emacs. Much to our surprise, several of them actually worked, and later ended up racked in our datacenter. So we ran a long extension cord out to the parking lot, plugged them in and stepped back. Clearly they had been submerged by hurricane flooding for some period of time. These servers had green and brown smears on them. Of course each of AOS/VS and VMS had their own, non-UNIX operating systems.įunny story: we put word out to AETC (Air Education and Training Command) that we needed more 3B2s, and a few months later, some pallets arrived from Homestead Air Force Base, which had been destroyed by hurricane Andrew a couple of years prior. We also had, among others, DGUX, SCO, AOS/VS, Sun and Vax/VMS servers. If memory serves, they ran AT&T System V release 3 UNIX. They were, in fact, the only machines we had that were rated for classified data. So, six years later, in 1994, I found myself as the UNIX system administrator for a large (at the time) datacenter at Keesler Regional Medical Center, Keesler AFB, Biloxi Mississippi, where we had quite a number of 3B2s. Holy shit, ATT 3B2, I haven't heard any mention of those in a long time.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |