Forgot your password?
typodupeerror

Comment: Virtualization may be your answer (Score 2) 98

We had a similar issue with our engineers. We had login servers which worked great as they were poorly advertised and woefully underused, but once we had a system in place for them to make efficient use of them, they started to randomly crash. Most times it was due to them trying to submit a job to our compute farm and end up running it on the login servers, but sometimes it was malicious and a deliberate attempt to get a few extra CPU cycles at the expense of others. For us, the solution was rolling our own virtual desktop farm. We used KVM for the hypervisor, python for the back end control, and php for the front end web interface. We used Active Directory for authentication and rights management. That way we could control precisely how much resources each engineer had rights to.

As you are working at a school, it is not without reason to believe that you can use the students to help develop a system to manage the virtual instances. With a bit of forethought and a limit to the specifications, you can have a simple VDI broker developed and tested in a month. And if you avoid my mistake and use the libvirt API, you will even have the ability to easily expand the system to using linux containers.

Comment: Re:Haven't cared in 5 years, don't care now (Score 1) 108

by Jailbrekr (#47469491) Attached to: KDE Releases Plasma 5

We officially rolled out centOS6 earlier this year, and we were hit hard by the transition from KDE3 to KDE4. In the end all we could do was either recommend that users either go to gnome, or switch to Trinity (KDE3 fork). I expect that we'll have similar challenges when transitioning to CentOS7 in 2 years unless KDE4 was fixed in CentOS7, except then we'll have challenges with both KDE4 and Gnome3.

Comment: BYOD means I/T loses some control over it (Score 5, Insightful) 377

by Jailbrekr (#43855429) Attached to: Why Everyone Gets It Wrong About BYOD

BYOD means you can no longer trust your own network because you no longer have the same level of control over the devices on it. And if you do not trust your own network, you need to increase your security costs substantially and provide other resources that you would otherwise not need to offer. So while you're saving around $1000 per year per user on hardware, you're spending more on licensing for NAC and VDI/RDP/ICA. You also need to amp up the local tier1/2 support because now without standards they're going to be spending more time dealing with more types of machines. Any gains made by standardization will be utterly destroyed.

BYOD is a short sighted, stupid idea thought up by someone who sure as hell has no experience with I/T support.

Comment: NEWSFLASH (Score 2) 369

by Jailbrekr (#43048269) Attached to: Cliff Bleszinski: Vote With Your Dollars

We already do you pompus twit. We rail against companies like EA for many reasons, and the games they produce is only part of it. We also rail against them because they are a HORRIBLE COMPANY TO WORK FOR. I've been approached twice for a job with EA in the last year, and twice I've politely declined despite the numbers looking good. Why? Because they suck.

Comment: It is official; Netcraft confirms: *BSD is dying (Score 1, Troll) 84

Honestly, how can we have a BSD post and NOT have the "BSD is Dying" meme?

One more crippling bombshell hit the already beleaguered *BSD community when IDC confirmed that *BSD market share has dropped yet again, now down to less than a fraction of 1 percent of all servers. Coming on the heels of a recent Netcraft survey which plainly states that *BSD has lost more market share, this news serves to reinforce what we've known all along. *BSD is collapsing in complete disarray, as fittingly exemplified by failing dead last
http://www.samag.com/documents/s=1148/sam0107a/0107a.htm
in the recent Sys Admin comprehensive networking test.

You don't need to be a Kreskin
http://www.amdest.com/stars/Kreskin.html
to predict *BSD's future. The hand writing is on the wall: *BSD faces a bleak future. In fact there won't be any future at all for *BSD because *BSD is dying. Things are looking very bad for *BSD. As many of us are already aware, *BSD continues to lose market share. Red ink flows like a river of blood.

FreeBSD is the most endangered of them all, having lost 93% of its core developers. The sudden and unpleasant departures of long time FreeBSD developers Jordan Hubbard and Mike Smith only serve to underscore the point more clearly. There can no longer be any doubt: FreeBSD is dying.

Let's keep to the facts and look at the numbers.

OpenBSD leader Theo states that there are 7000 users of OpenBSD. How many users of NetBSD are there? Let's see. The number of OpenBSD versus NetBSD posts on Usenet is roughly in ratio of 5 to 1. Therefore there are about 7000/5 = 1400 NetBSD users. BSD/OS posts on Usenet are about half of the volume of NetBSD posts. Therefore there are about 700 users of BSD/OS. A recent article put FreeBSD at about 80 percent of the *BSD market. Therefore there are (7000+1400+700)*4 = 36400 FreeBSD users. This is consistent with the number of FreeBSD Usenet posts.

Due to the troubles of Walnut Creek, abysmal sales and so on, FreeBSD went out of business and was taken over by BSDI who sell another troubled OS. Now BSDI is also dead, its corpse turned over to yet another charnel house.

All major surveys show that *BSD has steadily declined in market share. *BSD is very sick and
its long term survival prospects are very dim. If *BSD is to survive at all it will be among OS dilettante dbblers. *BSD continues to decay. Nothing short of a miracle could save it at this point in time. For all practical purposes, *BSD is dead.

Fact: *BSD is dying

"When it comes to humility, I'm the greatest." -- Bullwinkle Moose

Working...