Ultimately it was, but mostly because it's inevitably going to be a political decision when there's a large number of powerful politicians pushing for the other option.
The only reason that there was an oil rig out there in the first place was a matter of politics. Had we pushed for alternative energy in the 70s and not lost focus that oil rig wouldn't have been in such a risky locale.
Sigh, you do realize that you're comparing things which aren't of similar magnitude, right? I mean K street, Iraq, Katrina or the present economic crisis, these are not minor things, but significant instances of corruption and incompetence. But then again, it's not like reality has anything to do with it.
Depending upon the set up he might be able to get his money back for the portion of the license that hasn't been used. But it still requires a bit more than wanting to use Linux to actually justify this.
Probably the best first step would be to establish that all the software that the employees need works on Linux or has a fully compatible clone. If he can't do that then the rest of this is futile and a waste of the employers resources.
printing (maintaining both Windows and Unix print queues is apparently difficult)
Shouldn't be, they should ultimately use the same que. I'm pretty sure that the printer daemon can handle that without too much trouble. Samba just presents the device the way that a Windows server would, it then hands that off to the local print daemon for actual printing. So, it should handle that largely by itself provided that things have been correctly set up.
But it's been a while since I did anything like that, most of the time I'm just connective my *NIX computer to the networked printer. And these days most departments of any size just use a specialty printer that connects to the network, as when dealing with anything more than a small department you need something more heavy duty anyways.
You mean especially in a small woods. The transmission lines between cities tend to be much higher voltage than the ones in a typical city. The electric company tends not to obsess about hot spots on lines in the city the way they do those interstate transmission lines.
You might not care, but the Hague might. Stealing electricity for use in combat ops is almost certainly illegal. It's been criminal for some time to use pillaged resources against the owner. I'd assume that includes intangibles such as electricity.
It's possibly a war crime actually. You're not allowed to pillage, and one would assume that would mean using an occupied nations electrical grid against it as well. Now, if you're in their with the backing of the ruling power, I doubt very much that they'd appreciate you damaging their power lines in that fashion.
One of the very real problems out there is that it's more or less impossible to have strong passwords that are changed on a regular basis for everything. I've personally got nearly 500 log ins that I use from time to time and even just changing them once every few months takes a really long time.
I think it's more likely that they were expecting it to put up Kin numbers. In which case 2 phones would be more than enough. In total MS sold 500 Kin, so having two at this store would be reasonable in that context. Although a bit early to throw in the towel.
Citation necessary. The different versions of Android isn't about locking things down, it's a combination of them not waiting until the entire OS was mature and carriers that seem to need to differentiate themselves from the competition.
The only apps that get excluded from the version of the store on a particular handset are the ones with requirements that the phone can't handle.
Well, what does MS care if you're Winmodem gets repurposed for Linux? I'm sure it's not a perfect analogy, but there is precedence for hardware for MS platforms to be crippled and overpriced.
Even if that were the case, there's nothing they can do about it. Selling at a loss is a stupid strategy for items that have other uses. Once I've plunked down my money for the hardware, I own it and can do damn well whatever I like with it. Legally speaking they don't get a say in what I do with my property. What you're suggesting would be larcenous. They're selling you a product and then saying that you can't use it if you don't agree to their terms.
I'm pretty sure that WA state law doesn't allow for that. It's not really a verbal contract nor is it really any sort of promise. And it definitely isn't a signed contract. Under WA state law, there has to be a meeting of the minds and contracts is signed are presumed to be valid and signed in good faith. However as I just stated, I don't think that MS has a valid basis for claiming that there is a contractual obligation involved here.
Oh, believe me it can. Businesses in the modern era are run by people with MBAs that don't necessarily have the understanding of business to actually run one. Consequently you see all sorts of puerile and otherwise stupid business moves.
Trust me, MS is fully capable of making the same mistakes as everybody else even knowing the consequences. Which is what drives things like the WGA program. Anybody running a pirated copy of Windows doesn't have to put up with that crap, but the rest of us have to pay to run their antipiracy tools.
It's easy for a country that small to come out ranked highly in GDP per capita. All it takes is being willing to do something like offer offshore banking without any prying eyes and deliberately turning a blind eye to foreign tax dodgers.
And don't forget that scam that MS had going with their specially branded crap. Where they allowed manufacturers to make modems that were lacking the ordinary chips in favor of offloading the work to the processor and charge the end user more for the privilege of getting proprietary crap which didn't work as well as the other alternatives.
The thing about gold though is that once it gets into your lungs, it's not going to get out. Since it's not bio-reactive and rarely reacts with other things it tends to stay put. Meaning that if it does clog or otherwise harm something internally it's not coming out.
And yet you misspelled grammar. If you're going to get snippy about the grammar, it might make sense to make sure you're spelling is correct. I mean it's a little bit too ironious for most people's tastes.
Unless of course you're referring to actor Kelsey Grammer, in which case, bravo.
I suspect it's more along the lines of people expecting there to be something significant that they have for writing secure code. I'm willing to bet that the only thing they have that most other organizations don't have is a substantial budget for auditing the code for vulnerabilities. They probably wait longer before deploying code as well until it's been thoroughly vetted.
But cryptographic techniques aren't where most vulnerabilities are found. Most vulnerabilities are ones which could be avoided using secure programming practices.
In fact the FBI failed to break into a set of hard disks encrypted with Truecrypt and another program using 256-bit AES. Which pretty clearly indicates that as long as you choose an appropriate encryption algorithm, the vulnerability is almost always going to be in either the implementation, user error or in access to the machine.
But it's almost certainly true. Just look at OpenBSD's record. They went for a full decade without any vulnerabilities in the base system before one was eventually found. And that's from a group of mostly volunteers. Just imagine what you could get from programmers that are both paid and required to use secure coding practices.
What's really embarrassing is that most of it has been known about for quite some time, but for one reason or another the organization funding the programming doesn't feel like paying for it to be done securely. It's a similar problem to programming style.
Saltwater is tough to build in. The typical building materials, steel, cement, wood and even plastics don't really deal very well with it. You can attach a block of zinc to the hull to keep that to a minimum, but you really do have to pull ships out of the water from time to time to service the hull. And I'm not really sure how they propose to do that on what is essentially a floating man made island.
That was my thought. Why a few floating cities placed strategically where the garbage is collecting to clean it up is probably a good idea, in general this isn't all it's cracked up to be.
Slashdot Mirror
Ultimately it was, but mostly because it's inevitably going to be a political decision when there's a large number of powerful politicians pushing for the other option.
The only reason that there was an oil rig out there in the first place was a matter of politics. Had we pushed for alternative energy in the 70s and not lost focus that oil rig wouldn't have been in such a risky locale.
Sigh, you do realize that you're comparing things which aren't of similar magnitude, right? I mean K street, Iraq, Katrina or the present economic crisis, these are not minor things, but significant instances of corruption and incompetence. But then again, it's not like reality has anything to do with it.
You forgot about:
Want your users to use Windows 7 instead of Windows XP? They'll demand training. And get it, if the company wants to keep them.
Depending upon the set up he might be able to get his money back for the portion of the license that hasn't been used. But it still requires a bit more than wanting to use Linux to actually justify this.
Probably the best first step would be to establish that all the software that the employees need works on Linux or has a fully compatible clone. If he can't do that then the rest of this is futile and a waste of the employers resources.
printing (maintaining both Windows and Unix print queues is apparently difficult)
Shouldn't be, they should ultimately use the same que. I'm pretty sure that the printer daemon can handle that without too much trouble. Samba just presents the device the way that a Windows server would, it then hands that off to the local print daemon for actual printing. So, it should handle that largely by itself provided that things have been correctly set up.
But it's been a while since I did anything like that, most of the time I'm just connective my *NIX computer to the networked printer. And these days most departments of any size just use a specialty printer that connects to the network, as when dealing with anything more than a small department you need something more heavy duty anyways.
You mean especially in a small woods. The transmission lines between cities tend to be much higher voltage than the ones in a typical city. The electric company tends not to obsess about hot spots on lines in the city the way they do those interstate transmission lines.
You might not care, but the Hague might. Stealing electricity for use in combat ops is almost certainly illegal. It's been criminal for some time to use pillaged resources against the owner. I'd assume that includes intangibles such as electricity.
It's possibly a war crime actually. You're not allowed to pillage, and one would assume that would mean using an occupied nations electrical grid against it as well. Now, if you're in their with the backing of the ruling power, I doubt very much that they'd appreciate you damaging their power lines in that fashion.
One of the very real problems out there is that it's more or less impossible to have strong passwords that are changed on a regular basis for everything. I've personally got nearly 500 log ins that I use from time to time and even just changing them once every few months takes a really long time.
I think it's more likely that they were expecting it to put up Kin numbers. In which case 2 phones would be more than enough. In total MS sold 500 Kin, so having two at this store would be reasonable in that context. Although a bit early to throw in the towel.
Citation necessary. The different versions of Android isn't about locking things down, it's a combination of them not waiting until the entire OS was mature and carriers that seem to need to differentiate themselves from the competition.
The only apps that get excluded from the version of the store on a particular handset are the ones with requirements that the phone can't handle.
Well, what does MS care if you're Winmodem gets repurposed for Linux? I'm sure it's not a perfect analogy, but there is precedence for hardware for MS platforms to be crippled and overpriced.
Even if that were the case, there's nothing they can do about it. Selling at a loss is a stupid strategy for items that have other uses. Once I've plunked down my money for the hardware, I own it and can do damn well whatever I like with it. Legally speaking they don't get a say in what I do with my property. What you're suggesting would be larcenous. They're selling you a product and then saying that you can't use it if you don't agree to their terms.
I'm pretty sure that WA state law doesn't allow for that. It's not really a verbal contract nor is it really any sort of promise. And it definitely isn't a signed contract. Under WA state law, there has to be a meeting of the minds and contracts is signed are presumed to be valid and signed in good faith. However as I just stated, I don't think that MS has a valid basis for claiming that there is a contractual obligation involved here.
Oh, believe me it can. Businesses in the modern era are run by people with MBAs that don't necessarily have the understanding of business to actually run one. Consequently you see all sorts of puerile and otherwise stupid business moves.
Trust me, MS is fully capable of making the same mistakes as everybody else even knowing the consequences. Which is what drives things like the WGA program. Anybody running a pirated copy of Windows doesn't have to put up with that crap, but the rest of us have to pay to run their antipiracy tools.
It's easy for a country that small to come out ranked highly in GDP per capita. All it takes is being willing to do something like offer offshore banking without any prying eyes and deliberately turning a blind eye to foreign tax dodgers.
And don't forget that scam that MS had going with their specially branded crap. Where they allowed manufacturers to make modems that were lacking the ordinary chips in favor of offloading the work to the processor and charge the end user more for the privilege of getting proprietary crap which didn't work as well as the other alternatives.
The thing about gold though is that once it gets into your lungs, it's not going to get out. Since it's not bio-reactive and rarely reacts with other things it tends to stay put. Meaning that if it does clog or otherwise harm something internally it's not coming out.
And yet you misspelled grammar. If you're going to get snippy about the grammar, it might make sense to make sure you're spelling is correct. I mean it's a little bit too ironious for most people's tastes.
Unless of course you're referring to actor Kelsey Grammer, in which case, bravo.
Indeed, because the new mind control devices are only blocked by those stupid cheese head hats.
I suspect it's more along the lines of people expecting there to be something significant that they have for writing secure code. I'm willing to bet that the only thing they have that most other organizations don't have is a substantial budget for auditing the code for vulnerabilities. They probably wait longer before deploying code as well until it's been thoroughly vetted.
But cryptographic techniques aren't where most vulnerabilities are found. Most vulnerabilities are ones which could be avoided using secure programming practices.
In fact the FBI failed to break into a set of hard disks encrypted with Truecrypt and another program using 256-bit AES. Which pretty clearly indicates that as long as you choose an appropriate encryption algorithm, the vulnerability is almost always going to be in either the implementation, user error or in access to the machine.
But it's almost certainly true. Just look at OpenBSD's record. They went for a full decade without any vulnerabilities in the base system before one was eventually found. And that's from a group of mostly volunteers. Just imagine what you could get from programmers that are both paid and required to use secure coding practices.
What's really embarrassing is that most of it has been known about for quite some time, but for one reason or another the organization funding the programming doesn't feel like paying for it to be done securely. It's a similar problem to programming style.
Saltwater is tough to build in. The typical building materials, steel, cement, wood and even plastics don't really deal very well with it. You can attach a block of zinc to the hull to keep that to a minimum, but you really do have to pull ships out of the water from time to time to service the hull. And I'm not really sure how they propose to do that on what is essentially a floating man made island.
That was my thought. Why a few floating cities placed strategically where the garbage is collecting to clean it up is probably a good idea, in general this isn't all it's cracked up to be.