Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
At my first job, a lot of the "normal office people" just got a tiny computer that was siting behind the monitor, if I remember correctly, it had a striped down version of windows xp plus additional 4gb hd, that you had to flash to persist the storage. We set them up to automatically open RDP once they booted and those user used to work directly on the server. Worked actually pretty well.
-
We had this too at my old school. You had like 40 thin clients all connecting to some Windows 2003 Server. It had just 8GB (8!!!!!) of RAM and a single gigabit Ethernet connection. This thing was slow af and we needed to launch some basic java ide which took about 5 mins to load. We had this until 3 years before. Also rocking Firefox 32.
-
@Jop- I'm not sure myself. Probably because it was be best structure they could think of for their network at the time. But it os kinda convenient since you only need a weak hardware with a modified bios to add a new terminal with dualboot.
It's a windows server, with a virtual environment for linux. The virtual environment also shares it's ram with the whole server (36gb).
And too answer a possible next question: Yes, they also think they pulled of a miracle there -
@xsacha replace "must" with "should". And yeah there are, kind of.
TL;DR
I accidentally surpassed(?) my user permissions and closed some of my classmates browsers and locked up a terminal for me
In school we have 2 primary operating systems: Windows and Ubuntu. Windows is hell in general and but not as hell as the firefox installation on Ubuntu.
"Just loaded this page. Now wait half a minute so that I can render it"
"Woah, woah, woah. Slow there. You just made an input event. Give me those 5 seconds to compute what you just did"
Executing "top" or "htop" shows you a long list of firefox processes with a cpu usage of 99.9%, since the whole school shares that linux environment.
Anyway, one day it was way more servere than normally and I way forced to kill my firefox instances. So I pressed CTRL+ALT+T for that terminal, waited 5 minutes until it accepted input typed "killall firefox" with a delay of half a minute per character and smahed that enter key.
At this very point in time I could hear confusion from every corner of the room. "What happened to firefox?"
Around 30% of the opened browsers where abruptly stopped. I looked back to my screen noticed I was logged out. I couldn't login from that terminal for the rest of that day.
Our network admin, which happened to be there, since the server is just next door, said that this was just convenience, but the timing was too perfect so I heighly doubt that.
I felt like a real hackerman even if it was by accident :)
undefined
wk65