Lurker_2k - Slashdot User

Microsoft Trying To Appeal to the Unix Crowd? 468

Posted by CmdrTaco on Wednesday February 27, 2008 @11:00AM from the well-we-are-very-sexy dept.

DigDuality writes "With the news that Windows 2008 (recently discussed on Slashdot) will have GUI-less installs and be fully scriptable, that they've opened up their communication protocols for non-commercial usage and are providing a patent covenant (Redhat Responds), and now finally an interesting rumor floating around that Microsoft will be taking on GNU directly. Has Microsoft totally switched gears in how it is approaching the Unix and FOSS sector for direct competition? According to an anonymous email leaked from a Microsoft employee, it seems Microsoft will be developing a framework that will be completely GNU compatible. Microsoft CEO, Steve Ballmer, said on Friday (23 February) that they are aiming to restore a Unix-like environment to its former proprietary glory, at the same time proving that Microsoft is committed to interoperability. Ballmer emphasized that Microsoft's new strategy is to provide users with a complete package, and this includes users who like Unix environments. According to the supposedly leaked email, UNG, which stands for UNG's not GNU, is set to be released late 2009."

Comment Re:Uhm, right... (Score 2, Informative) 819

by Lurker_2k on Wednesday August 13, 2003 @01:10PM (#6687441) Attached to: Microsoft Code at Fault for Half of all Windows Crashes

Sorry if I misunderstand something here but doesn't that indicate a memory/resource leak somewhere?
Its still a bug even if it doesn't bring the system to it's knees for days.

Actually, it's a stress test. This is generally an automated tst where we would run scripts to open and close various applications and whatnot for days. One script I ran when I was contracting at MS was something that opened up every single image in a certain directory (100+ jpgs) and at the same time, the machine would be also opening up several dozen excel spreadsheets, doing calculations on them, and exporting them to word files.

The system would be pegged at 100% CPU usage and the memory usage would max out as well, hence it was unusable from an ordinary standpoint. The scripts generally can be set to autoterminate after a certain amount of hours. Over the weekends I'd sed them to terminate after 72 hours and would arrive back on mondays to check out what ran and what didn't. For the systems that crashed, I'd have to send out reports to the various developers regarding how it crashed, what module actually crashed, and when it crashed.

Slashdot Top Deals