When people mention how this is implemented in Eve (my game) - they often forget to mention that it allows the isk grinders to play for free. So - for two players, CCP gets both subscriptions, one player gets to 'pay with isk to play' and one player essentially pays for two subs. Everybody is happy.
I work hard I'm not going to work in-game. I'm most certainly not going to try and compete with unemployed guys who play 18 hours a day. If I can help them by paying for their game time in return for their in game money I think it's a fair deal.
Dynamic LPAR, add 5 fiber adapters and 20G of RAM without bringing the OS down. Maybe add 4 virtual processors and only entitle the system to 1, allowing it to donate unused cycles back to the sharepool.
When I want to apply a service pack I don't get some silly Python error. It just works. Oh, also I can apply the service pack to a copy of the disk while the system is up and just reboot when I please. (alt_disk_copy.)
Feel like adding a virtual ethernet adapter to the system mentioned above? No Problem? While it's up? No problem!
If you want to move a completely virtualized system to a different machine, while it's running, no problem!
AIX LVM simply blows everything else away.
The briefing center in Texas has great breakfast burritos.
Anyway, you get the idea. You don't simply buy a processor, you buy a enterprise Unix OS that can do everything. Linux is almost there...
Take your time - you're lucky - you have no real reason to rush. What you have works. Ask around (you're doing this now) - try it out. Run parallel for a while in test. Then make a nice easy switch when you have no more questions...
I'm with ya - don't really need to mess around with games at home. However, my approach is different. My computer only has a PCI slot, so I'm stuck with a low end ATI card. I just play games that are a few years old. I buy the 20 dollar version that has all the expansions and bug fixes built in. Right now I'm playing Neverwinter Nights and Baldur's Gate.
Perhaps they want to be able to dynamically toss their app couple of CPU's without downtime. Perhaps they want to dynamically toss it any number of i/o adapters dynamically without downtime. Same goes for memory. Mabye they like the virtualization features, like micro partitioning and Virtual I/O servers.
I know the article talks about stability, but there really are a lot of features on the power5 platform that simply don't exist in Linux land. Cmon, with linux we are talking about PC hardware, PC realiability, PC availability, and PC service. I don't care what high end equipment you put in it, if it can still boot DOS 6.22, it's a freaking PC.
Why does support always mean telephone support to Slashdotters?
- They will probably distribute white papers on making debian work. - They may distribute driver packages for the hardware in the different models. - They may issue a proliant support pack that will install easily on debian that works with HP Systems Insight Manager (SIM) (an snmp trap destination for server monitoring.) ETC ETC ETC - Online firmware updates via SIM are possible - They may distribute new 'jobs' with HP Rapid Deployment (It's really Altiris) that install debian on the different models for - just a drag a job to a server.
ETC ETC ETC.
You see SUPPORT means having software (Proliant packages) that works without calling for help. It means having the tools available for deployment (Rapid Deploy), and having the tools to know when something goes wrong (Insight Mangager).
Geezus - innovation in office? I could get by with office 95 - and probably with something older than that.
Everybody always shouts about innovation in office, but then when we get something new we shout about how bloated it is.
Everybody using the same thing is good for business. Business is what counts, not choice in office products. When will the slashdot crowd get that through there friggin ms hating heads?
I'm a Citrix admin. I install office. It works. Everybody knows how to use it. I move on the to the hard clinical apps. Thank you very much.
Has anybody seen Wyse's front page lately? There is a penguin there I believe. They are pushing the linux based thin clients hard in every roadmap meeting we've had. In healthcare, wireless thin clients are pretty much required - I wonder what their wireless support is like in linux products?
I didn't take the time to read the comments, so I'm sorry if a million people have already made this argument. It's also a no brainer, not sure why we have to point this out.
I think the intent of the GPL is to protect the user's, and the authors, rights, not the software:)
A better head line would have been " GPL Hurts Linux, but continues to protects Users"
You said you don't care about or understand the certification.
Makes sense.
You don't care about it because you run 3 different distro's on desktop class hardware in a non mission critical enterprise shop.
You don't understand what is being offered because the problems (and solutions) you face in your 3-PC world are different than the person who does understand (and care about) this certificaiton.
I make close to 40 dollars an hour. If I spend 10 hours learning OpenOffice, any savings are washed out. Will it take me 10 hours to leran? No... but what if I have to spend 15 minutes working around a difference? How about 2 minutes fixing some document that didn't translate well? Add em all up, and the savings is gone. Now perform these calculations, but use Doctor salaries. Use attorney salaries. Or executive assistant salaries. Do the math. The cost of software is really insignificant in comparison to people-time.
Most slashdotters advocating open source on the desktop think they are battling a monopoly or vendor lock-in. From a business's perspective, the best software is ALWAYS the software you know, the software with which you are most productive.
Yes, thin clients 'have their uses.' I'll give you a pretty common one.
The hospital I work for has around 2000 of them, plugged into batteries and wireless client bridges. Along with an LCD display, they are rolled around on carts.
The last place I worked had another use. Again, pretty common. Very distributed company, hard to support PC's. Data wasn't being backed up at all the remote locations, people just wouldn't change tapes. Needed to move the data to central data center, and to do that, we needed to move the apps there as well.
Citrix rocks.
Slashdot users still think PC's are 'way cool man' - naturally server based computing makes no sense to most slashdotters.
I work at one of those big shops where the unix guys to the unix stuff and the NT guys do the Windows stuff.
I guess DNS, Email, Web, DHCP, File, Print, Etc is all 'windows' stuff. Note that any of these COULD be done by the 'UNIX' guys.
I am personally skilled in both Unix and Windows. Our shop recently had the need to setup a stand alone mail server, we couldn't use Exchange for the thousands of mailboxes we needed for a project because of the expense. Because the mail would eventually end up on a very large AIX box, our UNIX admins should have picked up the project. But they only know how to configure sendmail enough to use a smart host.
So, I, a member of the 'windows' team, setup a linux/postfix/vmpop3d solution for them. I needed my Unix skills. (Setup Linux.) I need my Mail skills (Setup postfix. Configure for virutal mailboxes. Configure pop server to use virtual mailboxes. ) I needed my DNS skills (setup internal domain, mx record, etc.) I need my x86 skills (will eventually live on hp hardware) I needed my web skills (Setup apache, write simple python cgi script to manage the virtual mailboxes)
Our Unix team uses host files.
Anyway, being an 'admin' nowadays requires, or should require, more knowledge than vi. Deal with it.
You are either a solutions-oriented admin, and will use whatever tools you need for the solution, or you're just an operator.
Using the command line and using the GUI really are the same thing.
However -
Anybody ever run across a guy who just likes to click every fucking button in sight? Hell, I've even clicked through a few thing myself too quickly and regretted it.
In a nutshell, the gui does sometimes make things easier TO DO. But there it little difference when it comes to figuring out WHAT TO DO. And it's been my experience that figuring WHAT TO DO is usually the hard part.
I've met too many windows admins who like to use the GUI to figure out WHAT TO DO. They just try every option, every button, etc. This is just plain bad. They think this is normal:)
Here is a list of the new features in XP. Notice the use of words like "Enhanced, Improved, Greater, Easier" -
For the life of me, I can't figure out why anybody would consider moving thousands of workstations to XP. The only thing I can come up with is the built in firewall which can be controlled via group policy.
User interface improvements? Big deal, so now it looks like nintendo. Better help? Users call the help desk. 64 bit? Big deal...
-Intelligent User Interface -Comprehensive Digital Media Support -Greater Application and Device Compatibility -Enhanced File and Print Services -Improved Networking and Communications -Integrated Help and Support Services -Improved Mobile Computing -Reliability Improvements -Stronger Security Protections -Easier Manageability -64-Bit Support -Looking Forward: The Microsoft.NET Platform
XP (even 2000) does not come to a half slowly. I'm and admin. I run a 150 server Citrix farm at a hospital. I am part of the team that manages the 400+ wintel boxes. These boxes are busy. They run clinical applications for thousands of users. Our servers stay up. Period. Forget BSOD's - they really don't happen. It's too hard even to get permission to reboot them on purpose. I don't reboot my workstation regularly either, maybe once a month or so.
2k/2003/xp - they really are stable for most of the stuff we ask them to do.
Geez, I'm a unix/linux guy, working with windows professionally - at a freaking hospital. Take my word for it, windows is stable.
Now, for some things that DO suck: -Patches that require reboots -THE FUCKING REGISTRY. just go back to ini files like the rest of the world -When I say end task, I'm not joking. -Drive Letters (but this is getting better) -Lack of included utils like grep etc...
Anyway, Windows is pretty stable if you're not stupid. Put it on good hardware from a good vendor, follow best practices, and you'll have a box that stays up.
Slashdot Mirror
1998 called, they want their drama back.
I'll start worrying when the users can figure out how to automate a file copy on their own.
When people mention how this is implemented in Eve (my game) - they often forget to mention that it allows the isk grinders to play for free. So - for two players, CCP gets both subscriptions, one player gets to 'pay with isk to play' and one player essentially pays for two subs. Everybody is happy.
I work hard I'm not going to work in-game. I'm most certainly not going to try and compete with unemployed guys who play 18 hours a day. If I can help them by paying for their game time in return for their in game money I think it's a fair deal.
IF you bought an RS/6000 there is your answer about why your dual Xeon is faster. I don't think they have made RS/6000's for like ten years man.
A couple of reasons -
Dynamic LPAR, add 5 fiber adapters and 20G of RAM without bringing the OS down. Maybe add 4 virtual processors and only entitle the system to 1, allowing it to donate unused cycles back to the sharepool.
When I want to apply a service pack I don't get some silly Python error. It just works. Oh, also I can apply the service pack to a copy of the disk while the system is up and just reboot when I please. (alt_disk_copy.)
Feel like adding a virtual ethernet adapter to the system mentioned above? No Problem? While it's up? No problem!
If you want to move a completely virtualized system to a different machine, while it's running, no problem!
AIX LVM simply blows everything else away.
The briefing center in Texas has great breakfast burritos.
Anyway, you get the idea. You don't simply buy a processor, you buy a enterprise Unix OS that can do everything. Linux is almost there...
Ummmm...
If it aint broke...don't fix it.
Take your time - you're lucky - you have no real reason to rush. What you have works. Ask around (you're doing this now) - try it out. Run parallel for a while in test. Then make a nice easy switch when you have no more questions...
The Atari Portfolio Palmtop! Basically runs Dos 2.11. Couple of AA batteries. Open Lid, on. One keystroke and you are in an editor.
But seriously, just use a pen and paper.
I'm with ya - don't really need to mess around with games at home. However, my approach is different. My computer only has a PCI slot, so I'm stuck with a low end ATI card. I just play games that are a few years old. I buy the 20 dollar version that has all the expansions and bug fixes built in. Right now I'm playing Neverwinter Nights and Baldur's Gate.
Perhaps they want to be able to dynamically toss their app couple of CPU's without downtime. Perhaps they want to dynamically toss it any number of i/o adapters dynamically without downtime. Same goes for memory. Mabye they like the virtualization features, like micro partitioning and Virtual I/O servers.
I know the article talks about stability, but there really are a lot of features on the power5 platform that simply don't exist in Linux land. Cmon, with linux we are talking about PC hardware, PC realiability, PC availability, and PC service. I don't care what high end equipment you put in it, if it can still boot DOS 6.22, it's a freaking PC.
Why does support always mean telephone support to Slashdotters?
- They will probably distribute white papers on making debian work.
- They may distribute driver packages for the hardware in the different models.
- They may issue a proliant support pack that will install easily on debian that works with HP Systems Insight Manager (SIM) (an snmp trap destination for server monitoring.) ETC ETC ETC
- Online firmware updates via SIM are possible
- They may distribute new 'jobs' with HP Rapid Deployment (It's really Altiris) that install debian on the different models for - just a drag a job to a server.
ETC ETC ETC.
You see SUPPORT means having software (Proliant packages) that works without calling for help. It means having the tools available for deployment (Rapid Deploy), and having the tools to know when something goes wrong (Insight Mangager).
Geezus - innovation in office? I could get by with office 95 - and probably with something older than that.
Everybody always shouts about innovation in office, but then when we get something new we shout about how bloated it is.
Everybody using the same thing is good for business. Business is what counts, not choice in office products. When will the slashdot crowd get that through there friggin ms hating heads?
I'm a Citrix admin. I install office. It works. Everybody knows how to use it. I move on the to the hard clinical apps. Thank you very much.
Has anybody seen Wyse's front page lately? There is a penguin there I believe. They are pushing the linux based thin clients hard in every roadmap meeting we've had. In healthcare, wireless thin clients are pretty much required - I wonder what their wireless support is like in linux products?
"This Guy"
Is a TEACHER
Is an AUTHOR
Ia a HACKER
Now shut the $^#( up before I hunt you down and stuff that minix formatted floppy up your A$$.
I didn't take the time to read the comments, so I'm sorry if a million people have already made this argument. It's also a no brainer, not sure why we have to point this out.
:)
I think the intent of the GPL is to protect the user's, and the authors, rights, not the software
A better head line would have been " GPL Hurts Linux, but continues to protects Users"
This was great post...the first time I read it...
/ 2026242&from=rss
http://books.slashdot.org/article.pl?sid=05/07/26
The 400 Wintel servers we run at 3 hospitals beg to differ.
You said you don't care about or understand the certification.
Makes sense.
You don't care about it because you run 3 different distro's on desktop class hardware in a non mission critical enterprise shop.
You don't understand what is being offered because the problems (and solutions) you face in your 3-PC world are different than the person who does understand (and care about) this certificaiton.
I make close to 40 dollars an hour. If I spend 10 hours learning OpenOffice, any savings are washed out. Will it take me 10 hours to leran? No... but what if I have to spend 15 minutes working around a difference? How about 2 minutes fixing some document that didn't translate well? Add em all up, and the savings is gone. Now perform these calculations, but use Doctor salaries. Use attorney salaries. Or executive assistant salaries. Do the math. The cost of software is really insignificant in comparison to people-time.
Most slashdotters advocating open source on the desktop think they are battling a monopoly or vendor lock-in. From a business's perspective, the best software is ALWAYS the software you know, the software with which you are most productive.
Yes, thin clients 'have their uses.' I'll give you a pretty common one.
The hospital I work for has around 2000 of them, plugged into batteries and wireless client bridges. Along with an LCD display, they are rolled around on carts.
The last place I worked had another use. Again, pretty common. Very distributed company, hard to support PC's. Data wasn't being backed up at all the remote locations, people just wouldn't change tapes. Needed to move the data to central data center, and to do that, we needed to move the apps there as well.
Citrix rocks.
Slashdot users still think PC's are 'way cool man' - naturally server based computing makes no sense to most slashdotters.
Shouldn't this be titled
JBoss Founder Hard-Nosed About -COMMERCIAL- Open Source
???
So one fucking guy has a problem with commercial open source, big fucking deal. Okay everybody, just stop writing software. RMS, you too. Pack it up.
It's amazing to me how much people will pay just to be able to press some buttons.
I did buy a dreamcast for 50 bucks to be able to smash some buttons. But I can't bring myself to spend this kind of money to do it.
I work at one of those big shops where the unix guys to the unix stuff and the NT guys do the Windows stuff.
I guess DNS, Email, Web, DHCP, File, Print, Etc is all 'windows' stuff. Note that any of these COULD be done by the 'UNIX' guys.
I am personally skilled in both Unix and Windows. Our shop recently had the need to setup a stand alone mail server, we couldn't use Exchange for the thousands of mailboxes we needed for a project because of the expense. Because the mail would eventually end up on a very large AIX box, our UNIX admins should have picked up the project. But they only know how to configure sendmail enough to use a smart host.
So, I, a member of the 'windows' team, setup a linux/postfix/vmpop3d solution for them. I needed my Unix skills. (Setup Linux.) I need my Mail skills (Setup postfix. Configure for virutal mailboxes. Configure pop server to use virtual mailboxes. ) I needed my DNS skills (setup internal domain, mx record, etc.) I need my x86 skills (will eventually live on hp hardware) I needed my web skills (Setup apache, write simple python cgi script to manage the virtual mailboxes)
Our Unix team uses host files.
Anyway, being an 'admin' nowadays requires, or should require, more knowledge than vi. Deal with it.
You are either a solutions-oriented admin, and will use whatever tools you need for the solution, or you're just an operator.
Heres a thought.
:)
Using the command line and using the GUI really are the same thing.
However -
Anybody ever run across a guy who just likes to click every fucking button in sight? Hell, I've even clicked through a few thing myself too quickly and regretted it.
In a nutshell, the gui does sometimes make things easier TO DO. But there it little difference when it comes to figuring out WHAT TO DO. And it's been my experience that figuring WHAT TO DO is usually the hard part.
I've met too many windows admins who like to use the GUI to figure out WHAT TO DO. They just try every option, every button, etc. This is just plain bad. They think this is normal
Here is a list of the new features in XP. Notice the use of words like "Enhanced, Improved, Greater, Easier" -
.NET Platform
For the life of me, I can't figure out why anybody would consider moving thousands of workstations to XP. The only thing I can come up with is the built in firewall which can be controlled via group policy.
User interface improvements? Big deal, so now it looks like nintendo. Better help? Users call the help desk. 64 bit? Big deal...
-Intelligent User Interface
-Comprehensive Digital Media Support
-Greater Application and Device Compatibility
-Enhanced File and Print Services
-Improved Networking and Communications
-Integrated Help and Support Services
-Improved Mobile Computing
-Reliability Improvements
-Stronger Security Protections
-Easier Manageability
-64-Bit Support
-Looking Forward: The Microsoft
XP (even 2000) does not come to a half slowly. I'm and admin. I run a 150 server Citrix farm at a hospital. I am part of the team that manages the 400+ wintel boxes. These boxes are busy. They run clinical applications for thousands of users. Our servers stay up. Period. Forget BSOD's - they really don't happen. It's too hard even to get permission to reboot them on purpose. I don't reboot my workstation regularly either, maybe once a month or so.
2k/2003/xp - they really are stable for most of the stuff we ask them to do.
Geez, I'm a unix/linux guy, working with windows professionally - at a freaking hospital. Take my word for it, windows is stable.
Now, for some things that DO suck:
-Patches that require reboots
-THE FUCKING REGISTRY. just go back to ini files like the rest of the world
-When I say end task, I'm not joking.
-Drive Letters (but this is getting better)
-Lack of included utils like grep etc...
Anyway, Windows is pretty stable if you're not stupid. Put it on good hardware from a good vendor, follow best practices, and you'll have a box that stays up.