This is nonsense. Netflix uses CDNs, and I'll bet the big ISPs have peering agreements with these networks. I think they're all aching to get into the cell phone overage model and the cable companies obviously want to shut out their competition.
The companies that bought these applications because they didn't realize this would mean that the applications would not work in other operating systems, other browsers,...
It's not that they didn't realize it. I'm sure their geek employees were telling them it didn't work in Firefox, Safari, etc. Most of these companies deserve what they got themselves into. And many of them are repeating the mistake, just not with the browser this time.
Since we're quoting the article, don't forget this bit.
But because Acer and Asustek are international vendors of netbook PCs, the actual motivation of Microsoft's royalty charge is to keep Acer and Asustek from using Google Android or Chrome OS instead of Windows Mobile for their netbook or tablet PCs, the sources pointed out
This article could be complete BS, but regardless, what if they just want to sell to countries that don't recognize software patents? Must MS get paid for anything shipped that resembles a PC?
Except that you have to run Windows to run Exchange and everything will "just happen" to work better with other MS products. There's plenty of alternatives so don't chain yourself to MS. I'll bet you can get Zimbra up and running at least as quickly as Exchange Server. After which, your boss can focus more time on actually conducting business and less time trying to fight with Windows and Exchange. See how that works.
That's actually a really good point. I suspect there may be a correlation between age and views about MS. In fact, I'm sure that luring in young developers (counting on them not knowing MS history) is on their agenda.
Over the past 15 years, I've gone from pro-MS to agnostic to "avoid when possible" based largely on their behavior. But young developers don't know about DR-DOS, Netscape, MS JVM, or even the recent OOXML fiasco. So for those that don't understand the reasons for the seemingly automatic negative responses, a single action doesn't eclipse an entire history or even come close to meaning that they've "changed" as the shill put it.
If MS wants to gain respect, they've got to consistently play nice. That means supporting standards instead of trying to own them. That means playing nice instead of trying to lock out competitors with their monopolies. But I really can't see this happening unless they are broken up or they lose enough market share so that they're forced to compete on merit. They're too addicted to their current business of locking in customers and leveraging their monopolies.
This is and will be true for any two different programs using non-native (more so for proprietary) formats. Word Perfect -> Word. Word -> Open Office. Even Word '97 to Word 2007. You've hit on one of the reasons that standard formats are needed.
However, if formatting is that important, consider if you should even be sending word processor documents. Maybe you should be sending PDFs for review. Or maybe you're doing something that requires desktop publishing software.
I'll second that. I've got T-Mobile on my N900 in Houston and I often get 6.5 down and 1.5 up. And it's $10 per month less when you bring your own phone and no contract. Pretty sweet.
Same here. Be it.NET, SQL Server, Windows, Office, or whatever comes from MS, they all serve as lock-in tools. Take SQL Server for instance. The only major database that isn't cross-platform. It's based on Sybase, which originated on UNIX, so they should have been able to offer a UNIX version and may have been very profitable. The reason they don't is because it doesn't fit their larger business plan, which is to force users to use MS for everything. As long as they have desktop and office monopolies, they'll do this. We'll see them start to play nicely as soon as they lose their monopoly (as we're beginning to see with I.E.). This is the biggest reason I avoid MS.
Next is their despicable behavior, like what they did in the OOXML ISO debacle. I'll consider MS when they start completing fairly and introduce some ethics into their business. They could start by offering their software on other platforms in the cases where it would be profitable.
So I setup an account that was easy to hack into. It plays back screaming monkey sounds (included with Asterisk) to the caller and records the conversation. Most of the time, the caller is a machine, but a few times I've had a real person on the line and those were interesting.
You need not be disturbed. Look at mature professions like engineering and medicine. Both encompass learning a fair amount about related fields. I completed a mechanical engineering program which required a good deal of math and physics. Nearly enough to get a minor in them, but I'm neither a mathematician nor a physicist. Also a good deal of chemistry and EE classes too. If you want to be competent engineer, you need to know the fundamentals for the entire field before you specialize. As for medicine, you cover every main area of medicine both in the classroom and in clinic before you specialize.
A professional administrator should be able to do some programming. Programming is what computers are really all about. You give instructions to a machine to carry out a task, and often this must be automated, hence the need for programming (scripting in this case). My opinion: If you can't script, you're an operator, not an administrator, at least speaking professionally. Scripting is not hard and is way too powerful of a tool to brush off.
The only people I see arguing against scripting are people that only use Windows. MS made the mistake of having weak and too often absent scripting capabilities, and for some reason, users want to make excuses for them. Even MS realized their mistake and came out with Monad/PowerShell and Unix Services for Windows (or something similarly named).
Like Linux does? Surely you jest. You keep making these definitive statements that are simply not correct.
I don't mean for things to get heated, but did you not read the UNIX philosophy section of my post? You know, "Make each program do one thing well", "Store data in flat text files" and I think it's missing that everything is a file, which is one of my favorites. So no, I don't "jest". I'm quite serious. And these statements are correct.
'Get-Content' is not recognized as an internal or external command...
You helped make my point. Get-Content is part of Power Shell, which is not part of a default install on Windows Server. Not being included in the default install is a big deal because it means it's not intended to be part of the core system and an admin can't count on it being there when they need it.
Also Power Shell is relatively new compared to other shell languages. That's an important point because it takes time to build a skill set and it's a tremendous help to be able to build on previous knowledge. Who knows if Power Shell skills will be relevant in 5 to 10 years. And the skills are portable only between versions of MS Windows. Someone who learned UNIX fundamentals 10 years ago has a very relevant skill set today applicable to many different systems. Windows admins from 10 years ago when confronted with the Windows today will ask Mondad, I mean Power Shell what? Oh and I have to install it.
The list titled "Mike Gancarz: The UNIX Philosophy" here http://en.wikipedia.org/wiki/Unix_philosophy pretty much outlines what drew me to Linux/UNIX. These were really good ideas to stand the test of time as they have. Windows doesn't have this level of vision and consistency. If it does, please inform me. Because to me it looks like a mish-mash of technologies that change whenever MS needs some more cash flow.
In the same ways Windows generally is lame compared to Linux/Unix. No forking. Spawning processes is slow. CLI is an afterthought because the default CLI sucks and Power Shell doesn't offer much over a Perl install. Remote access is very anemic compared to SSH (no tunneling, it uses SOAP,..) and what's the point of a remote shell if the shell sucks.
I've learned that the ability to script anything and everything on a server and to be able to do it from anywhere should be essential for an administrator. I say should be because after you've done it for a while, the Windows way feels so, what's the word... oh yea, anemic, yet Microsoft has serious "not invented here" syndrome and doesn't include this ability by default and the installable options don't compare to those on a base Linux/UNIX install.
And even if you can point at Unix tools for Windows to enable awk, sed, grep or install perl and bash or ssh whatever, it's not the "Windows Way" and the way that nearly all Windows admins run Windows servers. As I'm writing this, I'm frustrated with a Windows admin because they can't write a script to watch a Tomcat log for errors and email the log entry. You know, something simple like grep ERROR logfile | mail -s "to_address".
I use them as an express checkout. It's nice when there is nobody in line and I can scan a few items a leave quickly. I don't dare go through with a full buggy.
I've gone from land line to Vonage to running Asterisk with several VOIP gateway services, which I've been doing for about 5 years. VOIP quality primarily depends on routing. I've currently got a VOIP gateway provider with ping times 40 ms and the latency and jitter during calls is not a problem and definitely better than a cell phone. I can't control how the gateway routes calls and it seems that some area codes I call have some noticeable latency, but overall it is a good experience. I've had many people comment on how good my phone sounds (probably b/c they have to take so many cell calls), but rarely the opposite. --Randall
"My Documents" is the correct place to store documents on Windows, hence the name. Instead of having "Network Drives", the user's entire home directory should be a network mount. Whether or not that's feasible on Windows, I don't know because I was able to ditch it many years ago, but you can't blame the users for saving to "My Documents". It's either your fault or Microsoft's.
And as to the actual topic, changing passwords frequently will result in them being written down, increasing the chance they'll be more easily accessible by others. When the employee starts work, they should be told that sharing passphrases is against policy and that there are other means to share data. They should then choose or be assigned a very good passphrase, that is not forced to change during their employment or at least changes no more than once per year. If an employee does share their passphrase, it should be dealt with as other breaks in company policy are.
It scares off innovation because people are afraid of being sued.
You could just as well get sued for using h.264. Though h.264 has more exposure, both have been on the market for a while. According to Wikipedia, VP8 was announced in September 2008. Patent trolls could come after the users of either codec. I wouldn't be surprised if (as a previous post mentioned) Google owns a patent or two related to h.264 after buying On2. This situation is a clear example why software patents hinder progress, but make no mistake; h.264 is not immune.
Most of the applications I see that use Oracle would work fine or better with an OSS database such as Postgresql or even SQLite. For some reason managers feel good about themselves when they spend gobs of money to run their app on Oracle. Sure there are apps that need Oracle's 24/7/365 top notch support, but most don't. In most situations, a catastrophe could be handled by importing yesterday's backup after a little downtime, saving bucks and DB management headaches.
Slashdot Mirror
This is nonsense. Netflix uses CDNs, and I'll bet the big ISPs have peering agreements with these networks. I think they're all aching to get into the cell phone overage model and the cable companies obviously want to shut out their competition.
The companies that bought these applications because they didn't realize this would mean that the applications would not work in other operating systems, other browsers, ...
It's not that they didn't realize it. I'm sure their geek employees were telling them it didn't work in Firefox, Safari, etc. Most of these companies deserve what they got themselves into. And many of them are repeating the mistake, just not with the browser this time.
Since we're quoting the article, don't forget this bit.
But because Acer and Asustek are international vendors of netbook PCs, the actual motivation of Microsoft's royalty charge is to keep Acer and Asustek from using Google Android or Chrome OS instead of Windows Mobile for their netbook or tablet PCs, the sources pointed out
This article could be complete BS, but regardless, what if they just want to sell to countries that don't recognize software patents? Must MS get paid for anything shipped that resembles a PC?
As a sysadmin, you first obligation is to your employer, not your principles.
As a medical doctor, you first obligation is to your employer, not your principles.
Just doesn't sound right, does it? This industry has some growing up to do.
Except that you have to run Windows to run Exchange and everything will "just happen" to work better with other MS products. There's plenty of alternatives so don't chain yourself to MS. I'll bet you can get Zimbra up and running at least as quickly as Exchange Server. After which, your boss can focus more time on actually conducting business and less time trying to fight with Windows and Exchange. See how that works.
http://wiki.samba.org/index.php/Exchange_Server_Alternatives
Because it's not how much you spent, it's how much you saved!
That's actually a really good point. I suspect there may be a correlation between age and views about MS. In fact, I'm sure that luring in young developers (counting on them not knowing MS history) is on their agenda.
Over the past 15 years, I've gone from pro-MS to agnostic to "avoid when possible" based largely on their behavior. But young developers don't know about DR-DOS, Netscape, MS JVM, or even the recent OOXML fiasco. So for those that don't understand the reasons for the seemingly automatic negative responses, a single action doesn't eclipse an entire history or even come close to meaning that they've "changed" as the shill put it.
If MS wants to gain respect, they've got to consistently play nice. That means supporting standards instead of trying to own them. That means playing nice instead of trying to lock out competitors with their monopolies. But I really can't see this happening unless they are broken up or they lose enough market share so that they're forced to compete on merit. They're too addicted to their current business of locking in customers and leveraging their monopolies.
Reminds me of the SNL episode with Will Ferrell doing George Bush and the "Axis of Evil".
Don't listen to what the economists say. Why? Because they like math, and math is very much a part of the Axis of Evil.
If you need a good laugh, here's the video: http://vids.myspace.com/index.cfm?fuseaction=vids.individual&videoid=32947614
This is and will be true for any two different programs using non-native (more so for proprietary) formats. Word Perfect -> Word. Word -> Open Office. Even Word '97 to Word 2007. You've hit on one of the reasons that standard formats are needed.
However, if formatting is that important, consider if you should even be sending word processor documents. Maybe you should be sending PDFs for review. Or maybe you're doing something that requires desktop publishing software.
I'll second that. I've got T-Mobile on my N900 in Houston and I often get 6.5 down and 1.5 up. And it's $10 per month less when you bring your own phone and no contract. Pretty sweet.
Same here. Be it .NET, SQL Server, Windows, Office, or whatever comes from MS, they all serve as lock-in tools. Take SQL Server for instance. The only major database that isn't cross-platform. It's based on Sybase, which originated on UNIX, so they should have been able to offer a UNIX version and may have been very profitable. The reason they don't is because it doesn't fit their larger business plan, which is to force users to use MS for everything. As long as they have desktop and office monopolies, they'll do this. We'll see them start to play nicely as soon as they lose their monopoly (as we're beginning to see with I.E.). This is the biggest reason I avoid MS.
Next is their despicable behavior, like what they did in the OOXML ISO debacle. I'll consider MS when they start completing fairly and introduce some ethics into their business. They could start by offering their software on other platforms in the cases where it would be profitable.
So I setup an account that was easy to hack into. It plays back screaming monkey sounds (included with Asterisk) to the caller and records the conversation. Most of the time, the caller is a machine, but a few times I've had a real person on the line and those were interesting.
You need not be disturbed. Look at mature professions like engineering and medicine. Both encompass learning a fair amount about related fields. I completed a mechanical engineering program which required a good deal of math and physics. Nearly enough to get a minor in them, but I'm neither a mathematician nor a physicist. Also a good deal of chemistry and EE classes too. If you want to be competent engineer, you need to know the fundamentals for the entire field before you specialize. As for medicine, you cover every main area of medicine both in the classroom and in clinic before you specialize.
A professional administrator should be able to do some programming. Programming is what computers are really all about. You give instructions to a machine to carry out a task, and often this must be automated, hence the need for programming (scripting in this case). My opinion: If you can't script, you're an operator, not an administrator, at least speaking professionally. Scripting is not hard and is way too powerful of a tool to brush off.
The only people I see arguing against scripting are people that only use Windows. MS made the mistake of having weak and too often absent scripting capabilities, and for some reason, users want to make excuses for them. Even MS realized their mistake and came out with Monad/PowerShell and Unix Services for Windows (or something similarly named).
Like Linux does? Surely you jest. You keep making these definitive statements that are simply not correct.
I don't mean for things to get heated, but did you not read the UNIX philosophy section of my post? You know, "Make each program do one thing well", "Store data in flat text files" and I think it's missing that everything is a file, which is one of my favorites. So no, I don't "jest". I'm quite serious. And these statements are correct.
-Randall
'Get-Content' is not recognized as an internal or external command ...
You helped make my point. Get-Content is part of Power Shell, which is not part of a default install on Windows Server. Not being included in the default install is a big deal because it means it's not intended to be part of the core system and an admin can't count on it being there when they need it.
Also Power Shell is relatively new compared to other shell languages. That's an important point because it takes time to build a skill set and it's a tremendous help to be able to build on previous knowledge. Who knows if Power Shell skills will be relevant in 5 to 10 years. And the skills are portable only between versions of MS Windows. Someone who learned UNIX fundamentals 10 years ago has a very relevant skill set today applicable to many different systems. Windows admins from 10 years ago when confronted with the Windows today will ask Mondad, I mean Power Shell what? Oh and I have to install it.
The list titled "Mike Gancarz: The UNIX Philosophy" here http://en.wikipedia.org/wiki/Unix_philosophy pretty much outlines what drew me to Linux/UNIX. These were really good ideas to stand the test of time as they have. Windows doesn't have this level of vision and consistency. If it does, please inform me. Because to me it looks like a mish-mash of technologies that change whenever MS needs some more cash flow.
-Randall
In the same ways Windows generally is lame compared to Linux/Unix. No forking. Spawning processes is slow. CLI is an afterthought because the default CLI sucks and Power Shell doesn't offer much over a Perl install. Remote access is very anemic compared to SSH (no tunneling, it uses SOAP, ..) and what's the point of a remote shell if the shell sucks.
I've learned that the ability to script anything and everything on a server and to be able to do it from anywhere should be essential for an administrator. I say should be because after you've done it for a while, the Windows way feels so, what's the word ... oh yea, anemic, yet Microsoft has serious "not invented here" syndrome and doesn't include this ability by default and the installable options don't compare to those on a base Linux/UNIX install.
And even if you can point at Unix tools for Windows to enable awk, sed, grep or install perl and bash or ssh whatever, it's not the "Windows Way" and the way that nearly all Windows admins run Windows servers. As I'm writing this, I'm frustrated with a Windows admin because they can't write a script to watch a Tomcat log for errors and email the log entry. You know, something simple like grep ERROR logfile | mail -s "to_address".
So yes, Windows Server is anemic.
--Randall
I think you have that backwards. From wikipedia:
Affirmative action refers to policies that take factors including "race, color, religion, sex or national origin"[1] into consideration
So affirmative actions is discrimination by race, sex, etc.
I use them as an express checkout. It's nice when there is nobody in line and I can scan a few items a leave quickly. I don't dare go through with a full buggy.
Anybody here tried this?
https://paymentnetwork.intuit.com/
I've gone from land line to Vonage to running Asterisk with several VOIP gateway services, which I've been doing for about 5 years. VOIP quality primarily depends on routing. I've currently got a VOIP gateway provider with ping times 40 ms and the latency and jitter during calls is not a problem and definitely better than a cell phone. I can't control how the gateway routes calls and it seems that some area codes I call have some noticeable latency, but overall it is a good experience. I've had many people comment on how good my phone sounds (probably b/c they have to take so many cell calls), but rarely the opposite. --Randall
"My Documents" is the correct place to store documents on Windows, hence the name. Instead of having "Network Drives", the user's entire home directory should be a network mount. Whether or not that's feasible on Windows, I don't know because I was able to ditch it many years ago, but you can't blame the users for saving to "My Documents". It's either your fault or Microsoft's.
And as to the actual topic, changing passwords frequently will result in them being written down, increasing the chance they'll be more easily accessible by others. When the employee starts work, they should be told that sharing passphrases is against policy and that there are other means to share data. They should then choose or be assigned a very good passphrase, that is not forced to change during their employment or at least changes no more than once per year. If an employee does share their passphrase, it should be dealt with as other breaks in company policy are.
Just curious. Is the 80GB after applying lossless compression to the image set? If not, there's no good reason to store it uncompressed.
As for your question, I agree with those that say to skip the filesystem. Just use tar and a block device.
-Randall
It scares off innovation because people are afraid of being sued.
You could just as well get sued for using h.264. Though h.264 has more exposure, both have been on the market for a while. According to Wikipedia, VP8 was announced in September 2008. Patent trolls could come after the users of either codec. I wouldn't be surprised if (as a previous post mentioned) Google owns a patent or two related to h.264 after buying On2. This situation is a clear example why software patents hinder progress, but make no mistake; h.264 is not immune.
if we have some sort of warhol worm, everyone ranting against the kill switch will be begging for the president to cut off the internet
Maybe that's just what we need to finally get rid of the Windows monoculture.
Most of the applications I see that use Oracle would work fine or better with an OSS database such as Postgresql or even SQLite. For some reason managers feel good about themselves when they spend gobs of money to run their app on Oracle. Sure there are apps that need Oracle's 24/7/365 top notch support, but most don't. In most situations, a catastrophe could be handled by importing yesterday's backup after a little downtime, saving bucks and DB management headaches.