{"id":5073,"date":"2006-10-05T10:14:00","date_gmt":"2006-10-05T10:14:00","guid":{"rendered":""},"modified":"2021-09-20T12:16:22","modified_gmt":"2021-09-20T19:16:22","slug":"linux-watch-get-the-facts","status":"publish","type":"post","link":"https:\/\/www.microsoft.com\/en-us\/windows-server\/blog\/2006\/10\/05\/linux-watch-get-the-facts\/","title":{"rendered":"Linux-Watch: get the facts"},"content":{"rendered":"
Every now and again\u00a0we use this blog to correct inaccuracies<\/a> in the public domain. Mostly innocent errors at media outlets. And usually I wouldn’t comment on opinion pieces\u00a0at Linux-Watch because the rhetorical debate would be fruitless. You know, “taste great” versus “less filling” sort of thing. But one of our pals at Linux-Watch botched some facts while he was predicting doom and gloom<\/a> for Windows Server, and the article was picked up by reputable media site eWeek<\/a>. I’m not asking reporters (with editors) to spare the rod. Your critical eye\u00a0helps us identify areas of improvement. But how about getting the facts right?<\/p>\n In this case, we’re talking about virtualization licensing. It’s not a simple topic, and virtualization is certainly causing Microsoft and the industry as a whole\u00a0to review its current licensing policies<\/a>. When you combine\u00a0the onset of virtualization\u00a0with the introduction of multi-core processors and mainstream x64 computing, there’s a tremendous amount of new capabilities available to you. But also new licensing models<\/a>\u00a0to understand that aren’t uniform<\/a> across the industry.<\/p>\n So if eWeek editors want to get the facts straight on the timing and details of Microsoft’s virtualization licensing policies, they\u00a0should start with Ward’s posting<\/a> last October. Then they can read the announcement<\/a>. And if there’s more column inches left in the revised balanced article, then you can give a shout out to IDC’s reports<\/a>, the updated licensing for Datacenter Edition<\/a>\u00a0– in addition to Peter Galli’s article<\/a>.<\/p>\n Patrick<\/p>\n","protected":false},"excerpt":{"rendered":" Every now and again\u00a0we use this blog to correct inaccuracies in the public domain. Mostly innocent errors at media outlets. And usually I wouldn’t comment on opinion pieces\u00a0at Linux-Watch because the rhetorical debate would be fruitless. You know, “taste great” versus “less filling” sort of thing.<\/p>\n","protected":false},"author":685,"featured_media":20685,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"msxcm_post_with_no_image":false,"ep_exclude_from_search":false,"_classifai_error":"","_classifai_text_to_speech_error":"","footnotes":""},"post_tag":[14],"product":[],"content-type":[],"solution":[],"coauthors":[926],"class_list":["post-5073","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","tag-virtualization","review-flag-new-1593580246-692"],"yoast_head":"\n