It's an Associated Press article, transmitted on MSNBC.
I can't help but think that's a good thing -- no matter what I think of the article itself.
Which, by the way, as a long-time supporter of EFF, is this: it's a good survey, accurate in its description and not excessively focused on repoting criticisms.
Mott is originally from Dell, actually. What he was brought in to address is the fact that HP's "innovative" IT solutions cost 10x what Dell's do per dollar of revenue earned, but generate dramatically less business efficiency.
Even under AOL's current whitelist policy, it's not as "fine" as it used to be.
It used to be true that, once they filtered viruses, whitelisting meant your message would get delivered.
Today, there are about a half dozen circumstances that cause your mail to be rejected even if you're on the whitelist.
For example, if your message "contains a URL that is the subject of a number of complaints" your mail will be rejected even if you're whitelisted.
Unfortunately, AOL has a habit of deciding that some of their hosting competitors's domains are "the subject of a number of complaints" and blocking all sites in the domain.
One of our lists' mail was blocked because the list-owner's informational site was mentioned in the footer, and was hosted by Yahoo Geocities.
(And, of course, they don't tell you which particular AOL in your message they object to.)
Compared to Microsoft these days, Google is proving impossible to partner with, impossible to leverage development with, and most tragic, totally dominant in the startup-funding arena, chilling investment when VCs ask the simple quesiton: "But isn't Google going to get around to this some day and flood you under?"
The license price, free or not, is the most trivial part of the real cost of upgrading a business server. downtime and labor cost far more then the licenses... unless of course you use slave volunteer or student labor.
...said strategy making your entire operation one-off and unleverageable. The point of non-OSS software -- for both the benefits and faults with this -- is that the software itself, as written, productes income multiple times. The better the software, the more efficient you are as a consultant, so the less you make off each consulting engagement, the more time you need to spend actually lining up work instead of doing it, etc.
Will AIM Mail be subjected to the same arbitrary, unexplained and untested filtering that AOL mail currently is?
As administrator for a mailing list service that has had cooperative whitelisted status with AOL for the better part of a decade, I must report that recent changes to AOL mail have made it impossible for us to offer consistent delivery to AOL customers -- even despite our whitelisted status.
AOL will now block mail due to "malformed URLs" and "URLS with complaints" -- but they won't explain which URL in the message they're blocking, won't exempt whitelisted services, and won't test the validity of complaints before blocking mail.
When you combine this with the fact that many users today can't be bothered to unsubscribe, so they just report mail from a list they're bored with as spam, we end up with cases like these two that occurred this past week alone.
- On one list, the list-owner's events page was rejected as a "complaint URL" - On another list, a list-owner's off-site searchable archive of their own list was rejected as a "complaint URL"
And the only way we know those were the URLs in question was by sending test messages, one URL at a time of the 5 to 10 appearing in the messages, to our own AOL account and seeing what din't get through.
For the first time in the over 14 years I have managed this service, I am actively suggesting subscribers not receive their list messages at AOL or Compuserve, because we can't guarantee they'll get through no matter how well we behave and how much time and energy we put into it.
So I ask you: any reason not to warn hem away from AIM Mail too?
And that's why you need a product manager: to coalesce and prioritize the differing requirements of users witohut getting bogged down in the implementation.
Too often -- especially in open-source land -- developers design functionality, then slap a user interface veneer on it.
What they really need to do is to design a user experience, then architect a solution that can serve it and potential similar uses, then develop the implementation to support the user experience.
Yeah, it actually does matter. Proper British usage is that a noun representing a body of people takes plural forms. "The Liberal Party *have*," not "has."
Slashdot Mirror
Why do you think on an ongoing basis VMware will continue to outpace more generalized system management software companies at this? Just curious.
The term we seem to be converging on is "hardware-assisted virtualization."
It's an Associated Press article, transmitted on MSNBC.
I can't help but think that's a good thing -- no matter what I think of the article itself.
Which, by the way, as a long-time supporter of EFF, is this: it's a good survey, accurate in its description and not excessively focused on repoting criticisms.
Mott is originally from Dell, actually. What he was brought in to address is the fact that HP's "innovative" IT solutions cost 10x what Dell's do per dollar of revenue earned, but generate dramatically less business efficiency.
Even under AOL's current whitelist policy, it's not as "fine" as it used to be.
It used to be true that, once they filtered viruses, whitelisting meant your message would get delivered.
Today, there are about a half dozen circumstances that cause your mail to be rejected even if you're on the whitelist.
For example, if your message "contains a URL that is the subject of a number of complaints" your mail will be rejected even if you're whitelisted.
Unfortunately, AOL has a habit of deciding that some of their hosting competitors's domains are "the subject of a number of complaints" and blocking all sites in the domain.
One of our lists' mail was blocked because the list-owner's informational site was mentioned in the footer, and was hosted by Yahoo Geocities.
(And, of course, they don't tell you which particular AOL in your message they object to.)
Why, exactly?
Compared to Microsoft these days, Google is proving impossible to partner with, impossible to leverage development with, and most tragic, totally dominant in the startup-funding arena, chilling investment when VCs ask the simple quesiton: "But isn't Google going to get around to this some day and flood you under?"
Wow, and I thought the distinguishing characteristic of humor is that it's funny.
The license price, free or not, is the most trivial part of the real cost of upgrading a business server. downtime and labor cost far more then the licenses... unless of course you use slave volunteer or student labor.
...said strategy making your entire operation one-off and unleverageable. The point of non-OSS software -- for both the benefits and faults with this -- is that the software itself, as written, productes income multiple times. The better the software, the more efficient you are as a consultant, so the less you make off each consulting engagement, the more time you need to spend actually lining up work instead of doing it, etc.
Will AIM Mail be subjected to the same arbitrary, unexplained and untested filtering that AOL mail currently is?
As administrator for a mailing list service that has had cooperative whitelisted status with AOL for the better part of a decade, I must report that recent changes to AOL mail have made it impossible for us to offer consistent delivery to AOL customers -- even despite our whitelisted status.
AOL will now block mail due to "malformed URLs" and "URLS with complaints" -- but they won't explain which URL in the message they're blocking, won't exempt whitelisted services, and won't test the validity of complaints before blocking mail.
When you combine this with the fact that many users today can't be bothered to unsubscribe, so they just report mail from a list they're bored with as spam, we end up with cases like these two that occurred this past week alone.
- On one list, the list-owner's events page was rejected as a "complaint URL"
- On another list, a list-owner's off-site searchable archive of their own list was rejected as a "complaint URL"
And the only way we know those were the URLs in question was by sending test messages, one URL at a time of the 5 to 10 appearing in the messages, to our own AOL account and seeing what din't get through.
For the first time in the over 14 years I have managed this service, I am actively suggesting subscribers not receive their list messages at AOL or Compuserve, because we can't guarantee they'll get through no matter how well we behave and how much time and energy we put into it.
So I ask you: any reason not to warn hem away from AIM Mail too?
And that's why you need a product manager: to coalesce and prioritize the differing requirements of users witohut getting bogged down in the implementation.
Too often -- especially in open-source land -- developers design functionality, then slap a user interface veneer on it.
What they really need to do is to design a user experience, then architect a solution that can serve it and potential similar uses, then develop the implementation to support the user experience.
All three NDMP users? You mean, like the majority of NetApp and EMC Celerra filer sites?
"why are the chapters about configuring Webmin at the end, for example"...
Simple. (And as an ex-trainer, laudable.)
You should learn how to use the B-flat vanilla version of anything before tailoring it -- follow the rules before you break the rules.
Additionally, it helps keep the printed examples consistent with the user's own screen during the essential first-use period.
Yeah, it actually does matter. Proper British usage is that a noun representing a body of people takes plural forms. "The Liberal Party *have*," not "has."
How? How about the fact that the unclassified VM has access to the virtualized MMU, not the real one?
Sorry, wrong thread...
By giving it direct access only to the virtualized MMU?
Actually, VMware GSX Server, which you saw, does use a host OS. VMware ESX Server, which is still in beta, doesn't.