Lecturing linux guru slapped into place
-
I figured as much with the ;) lol
-
you've done this before i see.
Yes, he has, and mentioned it here, too.
That will take a long time to eat up gigs of memory, though. I think my computer ran for half an hour to an hour before I got down to 25% free and decided to reboot to get rid of it. A month later I found the file it created in a directory somewhere, thought "what was this?" and then remembered.
-
@ben_lubar is using MilwaukeePC. I don't think speed is his biggest concern.
He did get an upgrade. To mediocre.
-
What's wrong with
#!/bin/sh $0 | $0
? Aside from it burning PIDs so much faster than memory.. if you have control over the /bin/sh alias that could be fixed too.
-
? Aside from it burning PIDs so much faster than memory.
no, that's basically that.
my version works even if per-user PIDs are restricted, you can still consume gigabytes of memory!
-
Win95 had domain-connected accounts? Since when?
...I know this is 95 because NT4 and 98 both had gradients in the title bars.
-
Win95 had domain-connected accounts? Since when?
Since... ever?
Way back when I was at school we had Windows 95 machines with domain logon.
-
To give another example, I just read another article about a Hungarian high school cutting almost 1/2 of costs by buying half as many computers and using them as multi-user workstations. (They could not afford buying a computer for each student in the PC room.)
Some details:
- Thin clients would not be sufficient as the exam students take at the end of high school features basic database management tasks, and the state mandates that the students can choose between MS Access or LibreOffice Base acting as a frontend for a local MySQL server. (this one is a minor because I'm sure Base can also connect to a database server and that can serve many users... but it's probably easier this way for everyone)
- 3 GHz CPU, 8 GB ram in each machine. They put 2-3 video cards in each one.
- OS: A SUSE Linux distribution provided by Novell in cooperation with our national Office of Education
-
Thin clients would not be sufficient as the exam students take at the end of high school features basic database management tasks, and the state mandates that the students can choose between MS Access or LibreOffice Base acting as a frontend for a local MySQL server.
I don't understand why that rules out thin clients. Our customers design skyscrapers with AutoCAD and Revit on thin clients. It's easier to give 60 engineers in different cities thin clients that go to the same back-end than it is to sync a 100MB drawing to 60 locations.
-
It's easier to give 60 engineers in different cities thin clients that go to the same back-end than it is to sync a 100MB drawing to 60 locations.
Yet with software development, it's easier to sync a 100MB repository to 60 locations than it is to give all the developers thin clients that go to the same back-end. Isn't that curious?
-
I don't understand why that rules out thin clients. Our customers design skyscrapers with AutoCAD and Revit on thin clients. It's easier to give 60 engineers in different cities thin clients that go to the same back-end than it is to sync a 100MB drawing to 60 locations.
My guess is that the know-how of installing a multi-user MySQL server and ensuring its security in a state regulated exam situation is much rarer and more expensive than the know-how to install a few Linux machines with local MySQL servers. (Read: you cannot find a school sysadmin that knows how do that, cause the pay is not too damn high.) If it is even allowed by the state rules on the exam. State rules on IT are infamously uninformed, and cutting costs is the last of the priorities. ("We're gonna go all open source in schools and save a truckload of money... oh wait, we just got a call from Microsoft, forget that last one" - true story)
-
Yet with software development, it's easier to sync a 100MB repository to 60 locations than it is to give all the developers thin clients that go to the same back-end. Isn't that curious?
The data is very different. This is one big file that needs its content synced, and it's a nightmare to do.
Imagine 60 remote developers working on one big MS Access mdb file in source control. It would be like that.
-
Imagine 60 remote developers working on one big MS Access mdb file in source control.
I'd rather not.
-
-
Touché
-
This is one big file that needs its content synced, and it's a nightmare to do.
It's hard enough to believe that that's reasonable even on the one system.