Really? That is how I've always seen the argument presented. The windows codebase is filled with ugly hacks to implement backwards compatibility. These hacks add bloat to the code, create vulnerabilities, and are probably one of the biggest reasons that Windows is often seen as unstable. Yet, even with all of this "backwards compatibility" built in, every time a freaking patch is released companies have to test all of their apps to see if anything was broken.
Yes, this is the way to go. Isn't that pretty much how Rosetta on Intel Macs were able to use PowerPC compiled software? This would be even simpler since it would be the same or similar proc architecture. No need to even base on *nix (though that would be nice), they could go back and create a clean NT kernel with all the cruft stripped from it. IIRC, pretty much all of the funny comments found in the leaked win2k source were caused by hacks to include undocumented system calls that older software was using (like office). A lean, mean, 64-bit only NT kernel would be fantastic. I would bet most of the bloat in the 6.x kernel line (Vista, 2008, Win7) is piling code on top of the old hacks to try and secure them (that and the DRM code, but I doubt MS would ever take that out).
Crunch the numbers and tell him how much it will save the company compared to buying new MS licenses according to your Microsoft agreement (assuming your company is completely legal with MS licensing, i.e. Each server has 1 Server license, each exchange server has 1 server license, each workstation has 1 XP Pro or Vista Business license, each user or workstation has 1 CAL each for Server, exchange, and possibly Office, plus any licenses for other MS services). If your company is like many and is hurting right now, you could be a hero.
If they are worried about support for the servers, include in your numbers the support costs of Red Hat, SUSE, Canonical (Ubuntu), Sun, or whomever else you would want to get support from. If they are worried about obscure software that isn't 100% WINE compatible, leave a Windows server in place, though then you are still stuck with CALs and the server license. Perhaps get once-off licenses for those instead of continued payment agreements.
Maybe they use Nvidia graphics card model numbering as their basis for version numbers.
"I bought a 9400 GT and my games run slower than they did with my 8800 GTX"
"Well thats because its a weaker card."
"But the number is higher, this is false advertising!"
"..."
I used to do phone support for a graphics card manufacturer.
Thanks for the info, my statement was based on having read many times before that generally RaLink wireless cards were recommended for use with linux. Is it just the chipsets used in the eee that have poor linux support, or is it a problem overall with their products?
Did yours come with XP pro? His probably came with XP Home, which I thought was the only version of XP that is still sold through OEMs (not counting Vista "downgrades" for businesses).
Well, XP Pro is usually the OS people pine for when they gripe about Vista. XP Home edition is what is normally supplied by OEMs with netbooks. XP Home is an abomination of an OS. The only good thing about XP Home that I can say is that the drivers for my D-Link wireless card do not crash Home, only Pro. Although the Stop error I get in Pro states that the drive is trying to use a higher IRQ level than the system granted, so I'd assume that means Home is just allowing it by.
Erm, Citrix has pretty much always had products that are add-ons to Microsoft stuff. Look at XenApp (formerly Citrix Presentation Server), it is basically an add-on for Microsoft Terminal Services that adds a bunch of enhancements and management tools, including load-balancing and running apps in a window on the client instead of just inside a terminal window. Adding "Essentials" to their XenServer and Microsoft's Hyper-V is just another way to make money on add-ons for other products. The big news here is that XenServer is now free, and not just the limited "Express" edition.
Yes, they basically just made the new management and HA features part of the "Essentials" package and added more features to the free "Express" edition, that they are calling "Enterprise" now.
And when that big machine goes down, so do all of the services. By virtualizing a datacenter into a pool of machines, if a server goes out any VMs on it can be moved off to other servers on the pool. For one big machine, if it runs virtual hosts for each app, those hosts can be reverted to a previous snapshot if something goes wrong. Or you can backup said snapshots to another server and bring that online very quickly if the main server goes down. Plus, since you can run multiple OSes, if a new app requires a newer or different OS, you can build a VM for it and send it to the server without affecting the other app VMs.
Per-box license instead of per socket. VMware ESX is $5k for up to 2 sockets, then 5k more for each additional 2 sockets rounding up (7 sockets would need 4 licenses). Also, on the subject of support, Citrix XenApp customers now recieve support for XenServer Enterprise.
VMware Server doesn't begin to compare to XenServer or VMware ESX. Might as well compare it to VirtualBox or QEMU. ESXi is more comparable to XenServer Express, which are both free and are "bare metal" hypervisors. However, XenServer Enterprise is now also free, plus if you already have a support contract for Citrix XenApp, you are now supported for XenServer Enterprise.
Xen without VT or AMD-V has the Linux-on-linux-only problem. But with either of those enabled, Windows runs fine. In fact, Microsoft Hyper-V, Citrix XenServer, and Sun xVM Server all are based on Xen, just with different a base OS (NT, Linux, and Solaris, repectively). I'm not sure how well Hyper-V supports Linux, although I believe Microsoft and Red Hat have some sort of agreement to do that. IIRC, VMware ESX and ESXi all use a linux base, though I think they use a proprietary hypervisor kernel not based on Xen.
And in an business environment, you will run into lots of commercial apps that need supporting. Plus, if you want high availability of those services, you will probably want a server for each one in case one needs to go down so you don't have all eggs in one basket. In a good virtualized environment with pooling, if one server goes down you bring the VMs up on another server so you can work on the one that went down while your business is still operational.
And why are "use taxes" fine, but sales taxes are not? Although they put the burden of collection on the purchaser and not the seller, they still are taxing interstate commerce. I understand that many states (including my own) have a "use tax" for purchases made out of state, but I believe they should be abolished.
As far as collection, the only way I believe they could is if they add it to the "use tax" section of the state income tax forms. Any other means that I could think of would either step on the toes of internet retailers(forcing them to collect) or would be far too difficult to implement(monitoring downloads at the ISP level).
Calling software a robot? Why not? Because you have some preconceived notion of what a robot is from watching too much Lost in Space?
Why should it? Because you assume everyone else is a moron that has no idea what they are talking about? The word already has a standardized meaning.
The International Organization for Standardization gives a definition of robot in ISO 8373: "an automatically controlled, reprogrammable, multipurpose, manipulator programmable in three or more axes, which may be either fixed in place or mobile for use in industrial automation applications." This definition is used by the International Federation of Robotics, the European Robotics Research Network (EURON), and many national standards committees.
Well, this tax violates the Interstate Commerce Clause, assuming that they are taxing purchases made with vendors from out of state as well. So they are advocating bypassing an illegal tax over copyright infringement.
Whenever I get frustrated with a piece of electronics, I defenestrate like mad and feel much better afterward. Just don't do it too much or you might go blind.
Of all the things you mentioned, the wiki would likely work best. MediaWiki is pretty easy to setup on a LAMP stack and has the benefit of being identical to Wikipedia as far as editing goes. At my last job (tech support call-center), we eventually implemented a wiki. It started out as an awesome repository of knowledge, protocols, and even some email reply scripts. However, it quickly devolved into only 3 people really making edits (Me and 2 other guys had edits in the thousands, #4 top editor had a couple hundred). Instead of the wiki becoming the #1 spot to look up an issue, instead most of the techs would send one of the top editors a jabber. To which we would usually respond with a link to the wiki page with all of the info. It seems that the people who use it most are those that put effort into making it. Perhaps a push to have all of your users make contributions would alleviate this problem. Just my 2 cents.
And security will do what to stop the guy from waiting nearby for her to leave? The biggest security in women's shleters are that their locations are kept as secret as possible.
Slashdot Mirror
Really? That is how I've always seen the argument presented. The windows codebase is filled with ugly hacks to implement backwards compatibility. These hacks add bloat to the code, create vulnerabilities, and are probably one of the biggest reasons that Windows is often seen as unstable. Yet, even with all of this "backwards compatibility" built in, every time a freaking patch is released companies have to test all of their apps to see if anything was broken.
Yes, this is the way to go. Isn't that pretty much how Rosetta on Intel Macs were able to use PowerPC compiled software? This would be even simpler since it would be the same or similar proc architecture. No need to even base on *nix (though that would be nice), they could go back and create a clean NT kernel with all the cruft stripped from it. IIRC, pretty much all of the funny comments found in the leaked win2k source were caused by hacks to include undocumented system calls that older software was using (like office). A lean, mean, 64-bit only NT kernel would be fantastic. I would bet most of the bloat in the 6.x kernel line (Vista, 2008, Win7) is piling code on top of the old hacks to try and secure them (that and the DRM code, but I doubt MS would ever take that out).
Crunch the numbers and tell him how much it will save the company compared to buying new MS licenses according to your Microsoft agreement (assuming your company is completely legal with MS licensing, i.e. Each server has 1 Server license, each exchange server has 1 server license, each workstation has 1 XP Pro or Vista Business license, each user or workstation has 1 CAL each for Server, exchange, and possibly Office, plus any licenses for other MS services). If your company is like many and is hurting right now, you could be a hero.
If they are worried about support for the servers, include in your numbers the support costs of Red Hat, SUSE, Canonical (Ubuntu), Sun, or whomever else you would want to get support from. If they are worried about obscure software that isn't 100% WINE compatible, leave a Windows server in place, though then you are still stuck with CALs and the server license. Perhaps get once-off licenses for those instead of continued payment agreements.
Maybe they use Nvidia graphics card model numbering as their basis for version numbers.
"I bought a 9400 GT and my games run slower than they did with my 8800 GTX"
"Well thats because its a weaker card."
"But the number is higher, this is false advertising!"
"..."
I used to do phone support for a graphics card manufacturer.
Thanks for the info, my statement was based on having read many times before that generally RaLink wireless cards were recommended for use with linux. Is it just the chipsets used in the eee that have poor linux support, or is it a problem overall with their products?
The fact that this was modded informative is one of the funniest things I've seen all day.
Which with correct provisioning of resources in the virtual environment shouldn't be a problem anymore.
Thats odd, RaLink support in linux has historically been very good. They even open the source for many of their drivers.
Did yours come with XP pro? His probably came with XP Home, which I thought was the only version of XP that is still sold through OEMs (not counting Vista "downgrades" for businesses).
Well, XP Pro is usually the OS people pine for when they gripe about Vista. XP Home edition is what is normally supplied by OEMs with netbooks. XP Home is an abomination of an OS. The only good thing about XP Home that I can say is that the drivers for my D-Link wireless card do not crash Home, only Pro. Although the Stop error I get in Pro states that the drive is trying to use a higher IRQ level than the system granted, so I'd assume that means Home is just allowing it by.
Erm, Citrix has pretty much always had products that are add-ons to Microsoft stuff. Look at XenApp (formerly Citrix Presentation Server), it is basically an add-on for Microsoft Terminal Services that adds a bunch of enhancements and management tools, including load-balancing and running apps in a window on the client instead of just inside a terminal window. Adding "Essentials" to their XenServer and Microsoft's Hyper-V is just another way to make money on add-ons for other products. The big news here is that XenServer is now free, and not just the limited "Express" edition.
Yes, they basically just made the new management and HA features part of the "Essentials" package and added more features to the free "Express" edition, that they are calling "Enterprise" now.
And when that big machine goes down, so do all of the services. By virtualizing a datacenter into a pool of machines, if a server goes out any VMs on it can be moved off to other servers on the pool. For one big machine, if it runs virtual hosts for each app, those hosts can be reverted to a previous snapshot if something goes wrong. Or you can backup said snapshots to another server and bring that online very quickly if the main server goes down. Plus, since you can run multiple OSes, if a new app requires a newer or different OS, you can build a VM for it and send it to the server without affecting the other app VMs.
Per-box license instead of per socket. VMware ESX is $5k for up to 2 sockets, then 5k more for each additional 2 sockets rounding up (7 sockets would need 4 licenses). Also, on the subject of support, Citrix XenApp customers now recieve support for XenServer Enterprise.
VMware Server doesn't begin to compare to XenServer or VMware ESX. Might as well compare it to VirtualBox or QEMU. ESXi is more comparable to XenServer Express, which are both free and are "bare metal" hypervisors. However, XenServer Enterprise is now also free, plus if you already have a support contract for Citrix XenApp, you are now supported for XenServer Enterprise.
Sorry, I was mistaken. Hyper-V is NOT based on Xen. Oracle VM is the other commercial implementation of Xen.
Xen without VT or AMD-V has the Linux-on-linux-only problem. But with either of those enabled, Windows runs fine. In fact, Microsoft Hyper-V, Citrix XenServer, and Sun xVM Server all are based on Xen, just with different a base OS (NT, Linux, and Solaris, repectively). I'm not sure how well Hyper-V supports Linux, although I believe Microsoft and Red Hat have some sort of agreement to do that. IIRC, VMware ESX and ESXi all use a linux base, though I think they use a proprietary hypervisor kernel not based on Xen.
And in an business environment, you will run into lots of commercial apps that need supporting. Plus, if you want high availability of those services, you will probably want a server for each one in case one needs to go down so you don't have all eggs in one basket. In a good virtualized environment with pooling, if one server goes down you bring the VMs up on another server so you can work on the one that went down while your business is still operational.
I get an error that wiki doesn't have an article with that name, maybe it was removed? http://en.wikipedia.org/wiki/C**T
And why are "use taxes" fine, but sales taxes are not? Although they put the burden of collection on the purchaser and not the seller, they still are taxing interstate commerce. I understand that many states (including my own) have a "use tax" for purchases made out of state, but I believe they should be abolished.
As far as collection, the only way I believe they could is if they add it to the "use tax" section of the state income tax forms. Any other means that I could think of would either step on the toes of internet retailers(forcing them to collect) or would be far too difficult to implement(monitoring downloads at the ISP level).
Calling software a robot? Why not? Because you have some preconceived notion of what a robot is from watching too much Lost in Space?
Why should it? Because you assume everyone else is a moron that has no idea what they are talking about? The word already has a standardized meaning.
The International Organization for Standardization gives a definition of robot in ISO 8373: "an automatically controlled, reprogrammable, multipurpose, manipulator programmable in three or more axes, which may be either fixed in place or mobile for use in industrial automation applications." This definition is used by the International Federation of Robotics, the European Robotics Research Network (EURON), and many national standards committees.
From Wikipedia
Even the average layperson knows what a program is. There is no reason to call it a robot.
Well, this tax violates the Interstate Commerce Clause, assuming that they are taxing purchases made with vendors from out of state as well. So they are advocating bypassing an illegal tax over copyright infringement.
Whenever I get frustrated with a piece of electronics, I defenestrate like mad and feel much better afterward. Just don't do it too much or you might go blind.
Of all the things you mentioned, the wiki would likely work best. MediaWiki is pretty easy to setup on a LAMP stack and has the benefit of being identical to Wikipedia as far as editing goes. At my last job (tech support call-center), we eventually implemented a wiki. It started out as an awesome repository of knowledge, protocols, and even some email reply scripts. However, it quickly devolved into only 3 people really making edits (Me and 2 other guys had edits in the thousands, #4 top editor had a couple hundred). Instead of the wiki becoming the #1 spot to look up an issue, instead most of the techs would send one of the top editors a jabber. To which we would usually respond with a link to the wiki page with all of the info. It seems that the people who use it most are those that put effort into making it. Perhaps a push to have all of your users make contributions would alleviate this problem. Just my 2 cents.
And security will do what to stop the guy from waiting nearby for her to leave? The biggest security in women's shleters are that their locations are kept as secret as possible.