Slashdot Mirror


Microsoft Trying To Appeal to the Unix Crowd?

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."

468 comments

  1. Wow by Renegade+Lisp · · Score: 5, Funny

    A rumour that sounds about as trustworthy as an e-mail from Nigeria.

    1. Re:Wow by ZeroFactorial · · Score: 5, Insightful

      Does Balmer actually understand the holy war he's getting the company into?

      This is like Satan trying to appeal to Christians.

      *nix users have already eaten the apple and realized they were duped.
      If the Nigerian princes are right, I'd say it's time to sell your Microsoft stock.

    2. Re:Wow by sundarvenkata · · Score: 1

      I completely agree. Slow news day?? CmdrTaco, I think you can also link to the letter that reveals your newly found wealth in Cambodia.

    3. Re:Wow by AKAImBatman · · Score: 4, Insightful

      I dunno, seems plausible enough to me. I was always of fan of the idea of extracting the NT kernel and doing a GNU distribution on top of it. (Something which is theoretically possible even without Microsoft's help, though rather difficult.) Microsoft would never have been happy about it because it would further erode their lock-in.

      Of course, these days Microsoft's lock-in is slipping away fast. More and more programs are showing up on the Mac, the web is going standards-compliant, and Java has ensured that Windows no longer locks customers in on the server side.

      The way I see it, Microsoft is fighting. Which is step 3 of 4 in Ghandi's formula for success: "First they ignore you, then they laugh at you, then they fight you, then you win."

    4. Re:Wow by jayhawk88 · · Score: 4, Insightful

      Perhaps, but there's no denying that products like Server 2008 and Powershell definitely have a very *nix flavor to them and are at least partially meant to appeal to the Linux crowd. I'm sure MS would love to make the MySQL/MSSQL or IIS/Apache decision a little more difficult for a lot of admins out there.

    5. Re:Wow by diegocgteleline.es · · Score: 5, Informative

      I don't agree. Microsoft IS trying to make Windows the best FOSS platform. The goal is not to be nice to FOSS, but to try to damage Linux. It's not me who says it, but Mary Jo Foley (who got it from a Microsoft), one of the most journalists experts in microsoft, if not the best. Quote:

      "Microsoft is looking at open-source software (OSS) as just another flavor of independent software vendors (ISV) software. Microsoft's goal is to convince OSS vendors to port their software to Windows. But Microsoft doesn't want OSS software to just sit on top of Windows; the company wants this software to be tied into the Windows ecosystem by integrating with Active Directory, Microsoft Office, Expression designer tools, System Center systems-management wares and SQL Server database.

      In cases where customers and software vendors want/need Linux to still be part of the picture for some reason, Microsoft will suggest they use Hyper-V, its forthcoming virtualization hypervisor, to run Linux and Linux-dependent applications.

      Microsoft's OSS strategy makes a lot of sense for Microsoft. It's another way for Microsoft to try to make Linux obsolete, and not look as obviously ruthless doing so. And for OSS vendors who are selling a lot of their software on Windows -- Ramji repeated a couple of times that more than 50 percent of JBoss' business these days is from software running on Windows -- Microsoft's OSS push isn't a bad deal, either.

    6. Re:Wow by AKAImBatman · · Score: 5, Funny

      This is like Satan trying to appeal to Christians.
      Is that really that great of a description? I mean, Satan is depicted as putting money, power, wealth, women, and other temptations in front of Christians to tempt them from their path. He's also depicted as regularly succeeding.

      I think the analogy you're looking for is something more along the lines of selling sno-cones to Eskimos.
    7. Re:Wow by Anonymous Coward · · Score: 0

      Still, any time you see the beginning of an "Embrace", watch out.

    8. Re:Wow by AKAImBatman · · Score: 5, Insightful

      Long story short: "Embrace, extend, extinguish"

    9. Re:Wow by Andrzej+Sawicki · · Score: 5, Insightful

      If anything it's a step on the way from Embrace to Extend. Later to be followed by Extingiush. I wonder, though, if the target isn't a tad too big this time. We'll see, I guess.

    10. Re:Wow by MightyMartian · · Score: 4, Funny

      When I can recompile the Windows kernel to my liking, then we'll talk about how Windows will be a better FOSS platform.

      --
      The world's burning. Moped Jesus spotted on I50. Details at 11.
    11. Re:Wow by Anonymous Coward · · Score: 1, Informative

      If only Microsoft would release a cute little action figure related to this, I would be interested. Until then, I'm not.

    12. Re:Wow by ZeroFactorial · · Score: 3, Interesting

      You insensitive clod! I'm an Eskimo and I love the sweet tasty goodness of a cool, sugary sno-cone.

      Also, you left one other difference out:
      Satan engages in questionable business practices.
      Oh wait....

    13. Re:Wow by Bill_the_Engineer · · Score: 5, Funny

      More like Yellow sno cones, being sold as lemon-aide.

      Eskimo: Hey! This doesn't smell right!

      Microsoft: Trust us, it's an improved lemon flavor.

      --
      These comments are my own and do not necessarily reflect the views or opinions of my employer or colleagues...
    14. Re:Wow by kestasjk · · Score: 2, Interesting

      MS also has existing software available for making Windows UNIX compatible, "UNIX Services for Windows", if memory serves. It's not a long distance from that to GNU compatibility.

      With Cygwin already around, and UNIX being open and readily able to be integrated into Windows, it would be a smart way to envelop potential UNIX users. Personally I'd like a Microsoft supported Cygwin, which isn't as buggy and doesn't feel as detached from Windows.

      --
      // MD_Update(&m,buf,j);
    15. Re:Wow by BotnetZombie · · Score: 4, Funny

      We use car analogies around here. This is like a car-dealer trying to sell Trabants to a Formula 1 team.

    16. Re:Wow by Archangel+Michael · · Score: 2, Funny

      Wine on top of NT Kernel? Now we're talking!

      --
      Agent K: A *person* is smart. People are dumb, stupid, panicky animals, and you know it.
    17. Re:Wow by Llanfairpwllgwyngyll · · Score: 3, Informative

      ...and I remember when some "microsoft partners" were told (very hush hush) that a GUI-less version of windows2000 would be released.

      We're still waiting.

      It's not like a Unix system, where a GUI is built on top of a CLI. Windows is GUI by design from the start. It's a whole different kettle of meat.

    18. Re:Wow by Nimey · · Score: 4, Insightful

      What'd be the benefit of the NT kernel instead of Linux or *BSD? Surely the kernel doesn't directly host Win32 or .NET APIs, since so much of them has to do with the GUI.

      --
      Hail Eris, full of mischief...

      E pluribus sanguinem
    19. Re:Wow by boris111 · · Score: 1
    20. Re:Wow by Provocateur · · Score: 3, Funny

      I think he's right, Satan with the upside down cross, MS with UNG instead of GNU...

      --
      WARNING: Smartphones have side effects--most of them undocumented.
    21. Re:Wow by iminplaya · · Score: 1

      A marriage analogy works just as well. A Microsoft "covenant" is about as good as a prenuptial agreement.

      --
      What?
    22. Re:Wow by gnu-user · · Score: 3, Informative

      Colinux is exactly that: http://www.colinux.org/

      Its a linux distro that runs on top of the NT kernel

      Runs pretty fast, for what it's worth

    23. Re:Wow by ArikTheRed · · Score: 3, Insightful

      But Microsoft doesn't want OSS software to just sit on top of Windows; the company wants this software to be tied into the Windows ecosystem by integrating with Active Directory, Microsoft Office, Expression designer tools, System Center systems-management wares and SQL Server database. If this is indeed their strategy, then it's not a good one. If GNU tools are available on Windows, then it would only be a matter of time acceptable OSS alternatives appear that interwork with Active Directory or SQL Server clones. Hell, clone the interface, and use LDAP and Postgres behind the scenes.
    24. Re:Wow by malevolentjelly · · Score: 3, Informative

      When I can recompile the Windows kernel to my liking, then we'll talk about how Windows will be a better FOSS platform. Of course, you don't need to because it's not monolithic. The benefits of recompiling the linux kernel stem from the fact that everything in linux-land is jammed into the kernel.

      You can simply load different drivers in pseudo-userland and run a separate set of services to completely rework your windows system. As far as enterprises and business customers are concerned, there's little to no benefit for them to be able to compile their own kernel unless it is completely monolithic- it's just a waste of time and a leak of talent for microsoft.

      FOSS is mostly GNU userland, not the linux kernel. If you don't believe me, try BSD or OpenSolaris.
    25. Re:Wow by CarpetShark · · Score: 1

      Embrace, extend, extinguish


      Everyone misquotes this. The full microsoft behaviour pattern goes as follows:

      Embrace, extend, extinguish, embarrasment, extricate head from ass


      Granted, they rarely reach step 5.
    26. Re:Wow by ZeroFactorial · · Score: 1, Troll

      Modded as flamebait? Who the hell is the jackass Microsoft employee that modded it so?

      It's a legitimate point. Microsoft is engaging themselves further (because they've pretty much already been engaged) in a holy war with *nix OSes. This is just a MUCH larger step in that direction.

      Perhaps you modded it as flamebait because of my suggestion to sell Microsoft stock?

      My mistake, you're not an employee, you must be a concerned shareholder.

      Disagreeing or having a financially vested interest in something doesn't qualify as grounds to mod as flamebait.

      Go ahead Mod THIS as flamebait, jackass, er, I mean Steve.

    27. Re:Wow by Ed+Avis · · Score: 0

      She got it from a Microsoft? This certainly lends credibility to the suggestion that they will make the Vista compatible with the Linux.
      </jerrylee>

      --
      -- Ed Avis ed@membled.com
    28. Re:Wow by ColdWetDog · · Score: 1

      What'd be the benefit of the NT kernel instead of Linux or *BSD?

      Here, have a nice cup of hot cocoa. Read this.

      --
      Faster! Faster! Faster would be better!
    29. Re:Wow by calebt3 · · Score: 1

      I think someone disapproved of the religious reference.

    30. Re:Wow by The+One+and+Only · · Score: 5, Insightful

      The way I see it, Microsoft is fighting. Which is step 3 of 4 in Ghandi's formula for success: "First they ignore you, then they laugh at you, then they fight you, then you win."

      What Gandhi left out is that, nine times out of ten, the fourth step is "then you're never heard from again".

      --
      In Repressive Burma, it's not just your connection that dies. slashdot.org/comments.pl?sid=314547&cid=20819199
    31. Re:Wow by incripshin · · Score: 5, Informative

      I think Cygwin's full of too many hacks to be a good starting point. For instance, Windows programs have no ability to fork, and yet cygwin has a fork() implementation. Personally, I don't want GNU compatibility but POSIX compatibility. There are POSIX makefiles and there are GNU makefiles. The difference is that POSIX makefiles run everywhere, while GNU makefiles don't. Just the same, I try never use GNU-specific language features in gcc (I use -std=c89 or -std=c99 with -pedantic). GNU hinders interoperability, themselves. It would be good if a Microsoft-developed make (there is nmake, but I don't know how it works at all) had a POSIX mode and a GNU+POSIX mode, in the same way that GCC allows by use of -std=XXX -pedantic flags to disable GNU extensions.

      Also, Microsoft's library model is positively nutty. Static libraries are stored as a big .lib file, while shared libraries are stored as a small .lib file together with a .dll file. Unix has .a and .so files, respectively. Inter-operable makefiles need simpler compilation systems than having three kinds of library files.

    32. Re:Wow by EvilRyry · · Score: 2, Informative

      You might not have heard this, but Linux does have support for these things called kernel modules. Also BSD and OpenSolaris don't use the GNU userland for the most part.

    33. Re:Wow by clang_jangle · · Score: 4, Funny

      Where the heck have you been? We've come a long way since those days -- now we have classic poop, diet poop, cherry poop, new poop, and of course salty lemonade!

      --
      Caveat Utilitor
    34. Re:Wow by Nimey · · Score: 1

      Data: "Perhaps the joke was not funny."

      And it looked like GP was serious, FWIW.

      --
      Hail Eris, full of mischief...

      E pluribus sanguinem
    35. Re:Wow by Wowsers · · Score: 2, Insightful

      A marriage analogy works just as well. A Microsoft "covenant" is about as good as a prenuptial agreement. Don't you normally get to see the prenup before marriage, what do you see of a shrink wrapped EULA?
      --
      Take Nobody's Word For It.
    36. Re:Wow by amliebsch · · Score: 1

      The difference, I guess, would be that Server 2008 already exists and is available for download. Just select "Core Installation" in the install options to get the GUI=less server.

      --
      If you don't know where you are going, you will wind up somewhere else.
    37. Re:Wow by xeoron · · Score: 1

      It might also be better for people whom will only run Window server stuff within a hypervisor controlled by a FOSS stack.

    38. Re:Wow by melikamp · · Score: 3, Funny

      Wine is great, but will it run Linux? Oh, wait...

    39. Re:Wow by bhtooefr · · Score: 1

      Ah, but that's only because the GUI is tied in at the kernel. Untie it, like IBM did with OS/2 1.3 (Microsoft wrote OS/2 1.1 and 1.2, and the GUI being part of the kernel was exactly the same as it was in NT,) and it's fine.

      And, even on NT5-6, you can get just console, no GUI. Try a chkdsk /f C:. ;)

    40. Re:Wow by Anonymous Coward · · Score: 0

      The original NT kernel was pretty cool. It had a built in security manager and provided POSIX, WoW (16 bit Windows API), Win32 and OS2 interfaces. I am pretty sure that all but WoW and Win32 was killed off w/ Win2K. The death of the security manager is particularly grieved.

    41. Re:Wow by huckamania · · Score: 1

      I don't think MS is trying to make Windows a better FOSS platform. Their stated goal is fluff. Does anyone really believe there is a demand for FOSS apps on Vista? Let me put on my tin foil hat.

      I think it is much more likely that undermining GNU (linux) is the real goal. GNU seems like it is in an unassailable position being free and open, but there will be companies whose business model or ethics preclude using GNU (GPL) and they will jump at a proprietary (pirated) alternative. Additionally, UNG could weaken some claims of GPL violation that are based on using GNU tools and libraries, if UNG provides an alternative (big IF). A fully functioning UNG would make GPL updates more difficult, which I didn't think was possible.

      I always thought Novel would be the ones to try to develop a UNG. Maybe MS got tired of waiting or maybe Novel is more useful as an 'early adopter'.

      Or maybe this is just a fake. MS sure has announced a lot of stuff for 2009.

    42. Re:Wow by DaedalusHKX · · Score: 2, Interesting

      I don't recall what is wrong with a prenup.

      Marriage was supposed to be a contract, it became a government and religious institution. Prenups became an attempt to bring the contract part of things back into it.

      Technically, if a woman cannot enter into a prenup (unwilling) it means she's likely to be taking you only for your money and goods and will fleece you dry. If she loves you, she wouldn't give a damn, so long as the prenup wasn't some ridiculous shitty deal. Marriage as it stands in its institutionalized format, already IS a shitty deal.

      Pick a different analogy.

      --
      " What luck for rulers that men do not think" - Adolf Hitler
    43. Re:Wow by mikael · · Score: 5, Informative

      Microsoft did try this before when they first brought out Windows NT. They provided a very minimal shell environment along with some unix emulation commands (make, ls, df, du, vi) as well as being able to get OpenGL drivers ported over. The idea was to provide these commands to get the applications ported over, and then to silently withdraw the suppport once the applications were ported.

      There are still emulation libraries by Cygwin and MKS

      Shell scripts are Microsofts weakness. Microsoft held off from including Monad into Vista for security fears. This was in a previous Slashdot discussion

      --
      Vintage computer adverts: http://www.vintageadbrowser.com/computers-and-software-ads
    44. Re:Wow by PitaBred · · Score: 1

      I think you just made up step 5, since I've never seen anything like that. You're probably some sort of Microsoft shill ;) </joke>

    45. Re:Wow by jollyreaper · · Score: 3, Insightful

      Microsoft's OSS strategy makes a lot of sense for Microsoft. It's another way for Microsoft to try to make Linux obsolete, and not look as obviously ruthless doing so. And for OSS vendors who are selling a lot of their software on Windows -- Ramji repeated a couple of times that more than 50 percent of JBoss' business these days is from software running on Windows -- Microsoft's OSS push isn't a bad deal, either. This appears risky for Microsoft. In times past, you ran Windows because that's all anybody wrote for. Those weird apps that are industry-specific, they're always defaulting to Windows. Microsoft's biggest fear is that the client can become platform-agnostic. If your app is now running via browser, you can run anything you want on the desktop. If you aren't coding to IE proprietary extensions, there's no lock-in.

      Previously, Microsoft's fear was apps moving from Windows to OSS platforms. The fear was that if you could run your precious app on Linux, why keep Windows? Well, now they're talking about apps that started in the OSS world and trying to get people using them on Windows. That to me seems to be accurately fitting the hoary old gateway drug scare story! You dip your toe into OSS while still having all your comfy Windows apps on the box. You get to like the functionality, pretty soon the jump to Linux isn't all that abrupt, the desktop looks a little different but lookie here, all your apps are just fine.

      By breaking down the barrier between Windows and OSS, Microsoft thinks Linux will lose the attractiveness and people will just run the OSS apps they like on Windows. I think it could accelerate the move the other direction. Well, wait five years and we'll see if I'm right.
      --
      Kwisatz Haderach
      Sell the spice to CHOAM
      This Mahdi took Shaddam's Throne
    46. Re:Wow by emilper · · Score: 2, Insightful

      I'll consider believing this sort of rumors when Microsoft will have usable auto completion in cmd.exe.

      Until their command tool gets closer in usability to xterm, and their GUI gets close to GNOME, I'll stick to Solaris if I want proprietary Unix.

      I suppose they could hijack one of the BSDs ...

    47. Re:Wow by marafa · · Score: 0

      thats nothing!
      my htc phone thinks i m in namibia!

      --
      _ In Egypt Networks: Network Solutions with a Twist
    48. Re:Wow by realthing02 · · Score: 2, Insightful

      Why do you care that you were moderated flamebait?

      This is the problem with slashdot, you can't stand the fact that your opinion was refuted by someone. Oh heaven's no! someone disagrees with what I said? How dare they take offense when I use broad stereotypes and overreaching generalizations! Here is a hint, if someone thinks you're flamebait, then you're flamebait to them. I don't think anyone goes around randomly using their mod points- I may be mistaken on that though.

      You have a +2 insightful as it currently stands, and I see more insightful thought in the "Microsoft sucks" bullshit that gets posted around here all the time. It's one thing to point out that mods missed a joke or something, but another to complain that someone took your polarizing comments the wrong way. THEY ARE POLARIZING, what the hell did you expect?

      The point is, why read slashdot comments if everyone thinks like you? I'd hate to have opposing viewpoints here! I mean, it's discussion of why you're so right, not about the facts and merits of the article that no one reads. I post once and a while, and sometimes people like what I say, sometimes they don't, and sometimes people just don't give a rip (I've got a lot of 1 point posts with no replies). Do you think I'm constantly hitting refresh or checking my profile to see if someone replied? You must have more smugness than a prius forum* to write a comment, and then wait for the +1 funny/insightful modifiers to roll in that you actually took offense to someone disagreeing with you.

      I'm not posting anonymously, because I could care less about the -1 I'll be getting in about 10 minutes.

      *heard this from someone else, didn't want to take credit for it.

    49. Re:Wow by rs79 · · Score: 1, Interesting

      It makes sense.

      Windows is the only non-unix OS of any mention any more and we've always seen PC ports to unix apps - that what you get paid to do, vry few pc programs or worth porting to unix. So, the closer Windows is to being some form of unix compatible the better.

      And there'e precedent for it. The architecture of dos/win is derived from CP/M which was a was written while looking at unix but only doing what could be done with an 8 bit processor and 16K or very expensive RAM. Keep in mind too Microsoft had Xenix - the first commercial unix ever sold.

      I can almost see how this happened. A few of the biggest MS investors corner Ballmer in a bar: "Unless your company does something like sell Linux, we think you have no long term future. Apple has switched, Sun hasn't died. Look like unix is everywhere not Windows like you guys said" to which Ballmer replied "bah, we can do everything Linux can"

      "Run Linux programs?"

      "We'll have it on two years" (Note to self: remind Bill I did this)

      --
      Need Mercedes parts ?
    50. Re:Wow by stox · · Score: 3, Funny

      And if you like the Lemon, just wait until you try our new chocolate flavor!

      --
      "To those who are overly cautious, everything is impossible. "
    51. Re:Wow by Aurisor · · Score: 1

      I don't agree. Microsoft IS trying to make Windows the best FOSS platform.


      That's inaccurate. I think you meant to say "the best platform for FOSS." Your statement implies that windows would somehow become FOSS, hence the confused / hostile replies to your post.
    52. Re:Wow by nxtw · · Score: 4, Informative

      MS also has existing software available for making Windows UNIX compatible, "UNIX Services for Windows", if memory serves. It's not a long distance from that to GNU compatibility.

      With Cygwin already around, and UNIX being open and readily able to be integrated into Windows, it would be a smart way to envelop potential UNIX users. Personally I'd like a Microsoft supported Cygwin, which isn't as buggy and doesn't feel as detached from Windows.


      As of Windows 2003 R2 and later, it's now called Subsystem for UNIX-Based Applications.

      SFU/SUA applications are not Win32 applications; they operate on the POSIX layer. The apps are still Windows PE formatted binaries. Libraries are also PE and do not have a .dll extension.

      The Unix environment is more Unix-like than Cygwin. Executables have no file extension; their names are all lowercase and appear that way in the Task Manager. SUA is aware of NT ACLs and permissions and appears to work with ACLs. It's possible to suspend and kill processes like any unix system.

      SUA borrows a lot of stuff from BSD and includes some GNU code. Much of the userland is based on BSD; the SUA FTP application supports HTTP downloads as well, like NetBSD's IIRC. SUA applications can be compiled with the Microsoft Visual C++ compiler or the included gcc (version 3.3). SUA provides a /proc filesystem.

      The userland is not as "complete" as a GNU system; commands like top and killall are missing, but ps and kill are functional.

      Ports of some GNU software are available here.

      I haven't found much of a need for SFU/SUA, mainly because I typically have some sort of Linux system accessible and because PowerShell makes it possible to do many of the same things. But it doesn't feel too different than any other Unix

      Here's the output of a few commands on my Windows Vista box:

      bash-3.00$ uname -a
      Interix bobspc 6.0 10.0.6000.0 x86 Intel_x86_Family6_Model15_Stepping10
      bash-3.00$ gcc -v
      Reading specs from /opt/gcc.3.3/lib/gcc-lib/i586-pc-interix3/3.3/specs
      Configured with: : (reconfigured) : (reconfigured) /dev/fs/D/gnu2.intel/egcs.s
      ource//configure --verbose --prefix=/opt/gcc.3.3 --disable-shared --with-stabs -
      -enable-nls --with-local-prefix=/opt/gcc.3.3 --with-gnu-as --with-gnu-ld --enabl
      e-targets=i586-pc-interix3 --enable-threads=posix
      Thread model: posix
      gcc version 3.3
      bash-3.00$ pwd
      /dev/fs/C/Users/bob
    53. Re:Wow by nxtw · · Score: 1

      POSIX is still around in the form of the Subsystem for Unix Applications. It's downloadable at no cost for users of certain XP and Vista SKUs and for Windows 2003/2008.

    54. Re:Wow by Anonymous Coward · · Score: 0, Offtopic

      Because you're not supposed to mod someone troll or flamebait because you disagree with them. You're just burying their potentially valid point that may not be either of those two. If you disagree, respond back and refute his point. Don't hide behind the moderation system.

    55. Re:Wow by lysse · · Score: 2, Insightful

      You can simply load different drivers in pseudo-userland and run a separate set of services to completely rework your windows system.

      You mean, kind of like Linux's modules...? There's no reason to recompile a kernel just to get a system working these days, nor has there been since about 2001; indeed, vendors tend to recommend against doing so. But you do at least get the chance to say "no, I know what I'm doing" and choose.
    56. Re:Wow by Anonymous Coward · · Score: 1, Insightful

      This actually sounds like MS is acknowledging that the open source community have developed quit a lot of good applications, and MS would like them to be able to run on their machines. The implication that MS is making is that the open source model of development is actually a good one, though they probably will not admit it.

    57. Re:Wow by cayenne8 · · Score: 3, Funny
      I wonder if there will be 'religious' wars between users of MS Vi, and MS emacs?

      :-)

      --
      Light travels faster than sound. This is why some people appear bright until you hear them speak.........
    58. Re:Wow by EvanED · · Score: 2, Informative

      MS has kept it up to date too. (I think there was some time when it was neglected, but it was then restored a bit ago.)

      They've got several programs (though not that many) including Bash, SSH, and GCC.

      The integration with the rest of Windows isn't great.

    59. Re:Wow by Anonymous Coward · · Score: 0

      Long story short: "Embrace, extend, extinguish"

      Lets try:

      Embrace, emulate, extend, extinguish, extort, exacerbation, extinction.

      M$ is entering exacerbation phase. People have had it with MS telling us what OS we want to run. And why emulate FOSS apps in MS-Windows when you can have the real thing in X-Windows? And in the end, just like Coke, MS has made a big strategic error with Vista and people hate it. If MS had any sense, they would bring back XP. But Balmer's and corporate ego could not take that I guess.

      I will predict Q2 MS sales will be down dramatically, if for nothing else the XP media sales are no longer there to prop this dinosaur up any longer.
       

    60. Re:Wow by PPH · · Score: 0, Redundant

      More like Yellow sno cones, being sold as lemon-aide. Watch out where the huskies go.
      --
      Have gnu, will travel.
    61. Re:Wow by Brother+Phil · · Score: 1

      I'd prefer a Microsoft supported Wine.

      Phil.
      --
      READ CAREFULLY. By reading this email, you agree, on behalf of your employer, to release me from all obligations and waivers arising from any and all NON-NEGOTIATED agreements, licenses, terms-of-service, shrinkwrap, clickwrap, browsewrap, confidentiality, non-disclosure, non-compete and acceptable use policies ("BOGUS AGREEMENTS") that I have entered into with your employer, its partners, licensors, agents and assigns, in perpetuity, without prejudice to my ongoing rights and privileges. You further represent that you have the authority to release me from any BOGUS AGREEMENTS on behalf of your employer.
      (http://smallprint.netzoo.net/reag/)

    62. Re:Wow by Java+Pimp · · Score: 2, Informative

      Of course, you don't need to because it's not monolithic.

      Windows is absolutely monolithic. Even though you can dynamically extend it with drivers/kernel modules, it is still monolithic. As is Linux. When the module is inserted, it essentially becomes part of the operating system.

      You are likely thinking of a Microkernel architecture which separates services into completely independent components. However, the difference being if one component goes down, it does not take the entire system with it.
      --
      Ascalante: Your bride is over 3,000 years old.
      Kull: She told me she was 19!
    63. Re:Wow by Anonymous Coward · · Score: 2, Informative

      > The architecture of dos/win is derived from CP/M

      Yeah, because you see, Windows NT is built on DOS, right?

      Would it kill you people to just not speak when you don't know what you're talking about?

    64. Re:Wow by nuzak · · Score: 2, Informative

      CoLinux runs User Mode Linux on NT. It's really quite a far cry from "running on top of the NT kernel", and more like a paravirtualized guest.

      --
      Done with slashdot, done with nerds, getting a life.
    65. Re:Wow by QRDeNameland · · Score: 3, Funny

      ...or else you'll find yourself trudging across the tundra, mile after mile, until you reach the parish of St. Alfonzo...

      --
      Momentarily, the need for the construction of new light will no longer exist.
    66. Re:Wow by SmellTheCoffee · · Score: 1

      Sorry to point out but it spelled Gandhi. I am an Indian and I am a bit annoyed when his name is misspelled, which it often does on /.

    67. Re:Wow by malevolentjelly · · Score: 1

      I disagree. Windows is not monolithic in the same way that Linux is- it's more of a hybird microkernel. It's like a microkernel with a monolithic structure, whereas BSD or Linux are true monolithic kernels.

      I think wikipedia does a good job of describing it.

      http://en.wikipedia.org/wiki/Architecture_of_Windows_NT

      Although Windows is not a true microkernel, I still believe that there's little to be gained in recompiling it.

    68. Re:Wow by burnin1965 · · Score: 1

      then we'll talk about how Windows will be a better FOSS platform

      Not so fast. Once Windows becomes a viable solution for a computer operating system and not simply a toy then the next step is to haggle over licensing.

      I don't care how good they claim Windows is, I'm not signing over my freedom of speech or right to privacy on my own property just so I can use their goofy software.

      If I use there software and it sucks, I'm going to tell others it sucks. And there is no way I'm going to agree to allowing a bunch of BSA goons to rifle through all my files if I don't pay some extortion fee.

      Nope, Microsoft has a long way to go before they have a viable platform. :P
    69. Re:Wow by malevolentjelly · · Score: 1

      You might not have heard this, but Linux does have support for these things called kernel modules. Also BSD and OpenSolaris don't use the GNU userland for the most part. It certainly does. These modules must be compiled for the specific kernel they support or can be compiled into the kernel. Windows' driver interface is a little more separated from the kernel, thus allowing IHV's to compile drivers without the source code of the kernel.

      BSD uses a bit of its own userland, true, but beyond the basic text mode legacy unix junk, it's running X.org, Gnome (or KDE), and other modern unix applications- which I consider to be part of the Gnu environment.

      OpenSolaris is truly a GNU environment- It's not like Solaris 10, which had Sun versions of BSD tools-- they are stripping as much sun out of the system as they can now-a-days. OpenSolaris is becoming very much like Red Hat Linux. I think the system is even compiled in GCC as opposed to Sun CC.
    70. Re:Wow by einhverfr · · Score: 2, Interesting

      Well, the other thing is that the desired development model is entirely different. Linux tends to support cheap process creation and optimize for that. The NT kernel is really optimized for single process, multithreaded applications which use things like async I/O. So yes, you can get the software to run from one to the other, but the performance overhead of running on the wrong platform could be substantial under load.

      --

      LedgerSMB: Open source Accounting/ERP
    71. Re:Wow by malevolentjelly · · Score: 1

      There's no reason to recompile a kernel just to get a system working these days, nor has there been since about 2001; indeed, vendors tend to recommend against doing so. But you do at least get the chance to say "no, I know what I'm doing" and choose. Well, I don't think this detracts from my point in any way. All I am saying is this: people just don't need to recompile their NT kernels. I agree with you with the restriction that recompiling NT would only be interesting or useful for either enthusiasts (a fringe market) or people trying to exploit the system (for better or worse).
    72. Re:Wow by evil_neanderthal · · Score: 5, Funny


      [0] Unix
      [1] GNU: Gnu's Not Unix
      [2] UNG: Ung's Not Gnu
      [3] UNU: Unu's Not Ung
      [4] UNU: Unu's Not Unu
      [...]
      [n+0] UNU: Ununix's Not Unu
      [n+1] UNU: Ugnu's gnot Ununix
      [n+2] UNU: Unugnu's tong Ugnu
      [n+3] UNU: Gnugnuung's gnongt Unugnu
      [n+4] UNU: Ungnungnungnu[...]

    73. Re:Wow by EvanED · · Score: 5, Interesting

      [Whew, long post. If your reaction is 'TL;DR' I don't feel bad.]

      The NT kernel... is an interesting beast. There are a lot of things I really like about the architecture it presents. In many ways it has a lot of things that are more modern and better-designed than Unix-descendents (including Linux). At the same time MS seems to have made it more complicated than it "needs" to be, in part to satisfy backwards compatibility and in part because they just seemed to make some decisions I don't agree with.

      Some of the good points:

      1. Security. Yes, security. This is often brought up as a Windows problem, but that is largely because of policy decisions such as running as admin. (There are also a number of bugs caused by just plain bad coding that lead to buffer overflows. The biggest problem here in some sense is some of the abilities such as sending messages to other processes, which are probably too ingrained to pull out without some very clever modifications.) The security manager in NT provides a lot of very fine-grained control. Related, you don't need explicit file system support and a separate mechanism to do more than RWX on files. (ACLs are absolutely vital in some environments, and things like an "append only" or "create files but no delete" are useful for some applications.) In Unix, sometimes you use chmod, sometimes you use fsacl or whatever it is; the framework isn't unified.

      2. Flexibility, in some sense. MS (in theory) can change the system calls that the NT kernel accepts on a whim. This is because all programs are dynamically linked to the Windows subsystem DLLs. These DLLs translate Windows API calls into whatever actual system calls they need. (One API call may generate zero, one, or more syscalls.) It's only the rare, "misbehaving" program that uses the syscall interface directly, and MS doesn't mind breaking them too much. (There are some mostly-legitimate reasons why you need to do this.) By contrast, statically linking code is a bigger tradition in Unix. (Then again, so is having source, so you can recompile if you change your syscall interface.) The idea of having various subsystems that provide different API views is pretty neat, though it's not a fundamental idea. (It's hard to say how it differs from just dynamically linking against just some shared lib.)

      3. Not really a good advantage, but interesting and one of the rare examples of where Windows is actually simpler is in the read/write interface. In Unix, my impression is that if you are writing a driver, you "have" to implement to entry points for each: synchronous and asynchronous read, and synchronous and asynchronous write. In Windows, you only implement the asynchronous interface. If a synchronous request is issued, it is handled at a higher level and translated to an async call. (Upside: simpler driver code. Downside: inability to implement just the synchronous version.)

      4. It's actually possible to use extended attributes on Windows, though admittedly only because of a huge hack introduced for a related but not-quite-the-same reason. (In Unix, opening a file with an extended attribute in Vi or Emacs, modifying it, and saving it is enough to kill the extended attributes. This makes them next to useless, when I at least can imagine a TON of very useful and neat things you could do with them if you could use them reliably.)

      5. The registry gets a lot of hate, but I think a modified version could be better. There are a lot of very nice things it provides over config files. (Transactional access, fine-grained access controls (often nice for a corporate environment, at least in some sense),

      6. Diversity. Yes, diversity. People often talk about the "Windows monoculture" on /. and other places. And yes, this is a big problem. But there is another kind of diversity, which is that Windows is the only major OS that isn't Unixy. Solaris is Unix. BSD is Unix. Linux is Unixy. It's only when you start talking about either research OSes (Mach, L4, Singularity) and old Oses (OS/2, BeOS

    74. Re:Wow by SL+Baur · · Score: 4, Informative

      Proprietary emacsen have died on the vine. The Gosling split (which was really the driving force behind RMS inventing the GPL) - Unipress Emacs never did well. When DEC tried to reinvent Emacs with EDIT/TPU they did a passable job (it was a fantastic editing environment for VMS), but it was so tied to the system that it could never make itself free.

      I am certainly not wedded to the command line in and of itself (though zsh is a tool I cannot live without), but I wouldn't be tempted even if they duplicate the Unix open architecture of interchangeable parts. I'm a Linux developer and user because I got extremely pissed off by having my system (the AT&T PC7300 aka the Unix PC) end-of-lifed on me and I never want that to happen again. Never. Those of you who love Microsoft Windows XP, take note. Maybe instead of complaining to Microsoft, you should join up with the ReactOS guys and keep the environment you love so much.

      It worked for us ...

    75. Re:Wow by Darinbob · · Score: 2, Insightful

      Windows NT did have a POSIX environment that sat above the NT kernel. The big snag though is that most of the useful services you needed were in the WIN32 environment. WIN32 is the real OS, which isn't just a GUI layer, even NT command line utilities and services sit on top of WIN32. You can't even do networking without WIN32. The kernel itself doesn't do much of anything outside of process and memory management. So given the POSIX implementation you really couldn't do more than write simple console apps that communicated to the outside world using files.

      In short, it was just enough POSIX for Microsoft to claim it was POSIX.1 compliant, which was just enough to satisfy some Department of Defense contracting requirements. A sort of wink and a nod in a way; allowing contractors to make bids for POSIX systems and end up getting the Windows they wanted.

    76. Re:Wow by Anonymous Coward · · Score: 0

      Didn't apple hijack a BSD?

    77. Re:Wow by ozbird · · Score: 2, Funny

      ...and of course salty lemonade!

      Gatesorade.

    78. Re:Wow by iminplaya · · Score: 1

      I don't recall what is wrong with a prenup.

      The comment had to do with how easy they are to wiggle out out of than anything else. I suspect a Microsoft covenant would be even easier.

      --
      What?
    79. Re:Wow by Paracelcus · · Score: 3, Funny

      Just think of the incredible added value M$ will be including with Windows! A GNU (Unix) work alike, now we won't have to get Linux and FreeBSD anymore! Now we can pay through the nose for it, oh wow, I'm hyperventilating, in fact my breath is coming in short pants!

      --
      I killed da wabbit -Elmer Fudd
    80. Re:Wow by EvanED · · Score: 1

      Windows NT did have a POSIX environment that sat above the NT kernel. ...and it still does, and it's been kept up to date. It's not included and has changed names a couple times (it's now called SUA -- Subsystem for Unix-based Applications), but it's a free download.

      You can't even do networking without WIN32.

      This hasn't been true for a while... You can get an implementation of SSH for instance. It also provides an NFS server and client (IIRC).

      In short, it was just enough POSIX for Microsoft to claim it was POSIX.1 compliant...

      It's now just enough for MS to claim it is POSIX.2 compliant.

      It's not great -- you can still not do GUIs and stuff from a program running in SUA, the compatibility isn't great, and I think that one way or the other (running SUA programs from cmd.exe or Win32 programs from SUA Bash) requires that you invoke the program through another command, but it is still rather better than it used to be.

      My impression is that the POSIX subsystem was neglected for a few years and then MS brought it back and updated it to POSIX.2. Between that and the release of PowerShell, I'm not terribly surprised to see something like this story. Could it be a hoax? Maybe. And concerns about "embrace, extend, extinguish" are probably worth having. But for my take, don't be surprised to see increased interoperability attempts at least in the short term, whatever MS's longer term goals are.

    81. Re:Wow by Anonymous Coward · · Score: 5, Funny

      [n+5] Ubuntu: ???

    82. Re:Wow by EvanED · · Score: 1

      Out of all of the objections you could take of CMD, you choose autocompletion?

      I have about one real complaint... it won't complete through / used as a directory separator. (Even though they usually actually work for commands... cd foo/bar works fine for instance.)

      It definitely works differently than the Unix approach, but I would say it's a 50/50 chance as to which works better in any given situation. (Though admittedly the CMD model sometimes falls on its face when it doesn't do as well, while the Unix method never is actively destructive.)

    83. Re:Wow by Kalriath · · Score: 1

      Hey hey! GNU is not Unix! Is that Stallman with a stick running at you?

      --
      For a site about things like basic rights, Slashdot users sure do like to censor "dissent".
    84. Re:Wow by lordofwhee · · Score: 0

      tl;dr

    85. Re:Wow by suckmysav · · Score: 1

      "But Balmer's and corporate ego could not take that I guess."

      More to the point, were Ballmer to Wall St and MS stockholders that they have spent 5 years and however many billions on Vista only to discover that it is a market total flop and that people prefer to keep using a Circa 2002 product then utter chaos would erupt.

      --
      "You can't fight in here, this is the war room!"
    86. Re:Wow by Curtman · · Score: 1

      I mean, Satan is depicted as putting money, power, wealth, women, and other temptations in front of Christians to tempt them from their path. He's also depicted as regularly succeeding.

      I never understood that. Satan is supposed to be the bad guy, but in the bible he doesn't really do all that much. God is the one inflicting all the wrath. The locusts and whatnot. The killing of everything except the fish and the lucky ones on the boat..

      You're right, it's a shitty analogy. Microsoft really is evil.
    87. Re:Wow by Anonymous Coward · · Score: 0

      [n+m] UBUNTU

    88. Re:Wow by Anonymous Coward · · Score: 0

      Try telling that to 1 billion Indians...

    89. Re:Wow by 2muchcoffeeman · · Score: 1
      "A rumour that sounds about as trustworthy as an e-mail from Nigeria."

      This is the first statement on the page that has the ring of truth. Mod him up, please.

      Newspapers have a better chance of long-term survival than this "rumor" does of being true.

      --
      Prevent Windows piracy. Use Linux instead.
    90. Re:Wow by akita · · Score: 0, Redundant

      Obviously Mods don't like Frank Zappa. Come on, it's funny...

    91. Re:Wow by The+One+and+Only · · Score: 1

      That was the other 1 time out of 10.

      --
      In Repressive Burma, it's not just your connection that dies. slashdot.org/comments.pl?sid=314547&cid=20819199
    92. Re:Wow by macshit · · Score: 1

      It's only when you start talking about either research OSes (Mach, L4, Singularity)

      Even then, it's pretty much a given that any modern research OS has as a design-goal that it be at least able to support an efficient unix-like layer of some sort (even if they prefer some other interface). So in some sense, these systems are much closer to "unix-like" in practice than Windows/NT.

      It's not the minor differences between NT/windows and unix that cause problems, after all, but the fundamental differences that make it very hard to implement a feature of one on top of the other (e.g. the "can't rename/delete a file while its in use" bogosity in windows, or the super heavyweight windows processes).

      --
      We live, as we dream -- alone....
    93. Re:Wow by Dantu · · Score: 1

      I don't recall what is wrong with a prenup.

      They aren't worth the paper they are written on. I write financial software. My clients (financial firms) don't even want to let clients pretend that they have separate financial assets from their spouse, regardless of what paperwork they have signed.

    94. Re:Wow by mjwx · · Score: 1

      What Gandhi left out is that, nine times out of ten, the fourth step is "then you're never heard from again".
      . Nelson Mandela would like to disagree with you.
      --
      Calling someone a "hater" only means you can not rationally rebut their argument.
    95. Re:Wow by shadwstalkr · · Score: 1

      No no, Satan honors his contracts.

    96. Re:Wow by rtb61 · · Score: 1
      Nah, I don't think it is even that. Just vapour ware, another idiotic ballmer marketing campaign. Buy M$, we are going to be more stable, secure and reliable, more Linux, 'er' 'um', Unix like, in the next version, we promise. You see we will be doing all this 'er' stuff and we will 'allow you' to do all this other 'stuff', we will, really we will.

      If they were in any way serious, they would simply use Linux, it free and it is readily available, anything else is just monopoly greed driven stupidity. Ballmer's stuck himself in a hole that he dug with his own mouth and ego and, he just can't get out.

      They have been trotting this stuff out upon a regular basis, we will be more open, we will be more interoperable, and then a month latter it's all your code belongs to us, it's our IP, it's our innovation, "we shall fight on the seas and oceans, we shall fight with growing confidence and growing strength in the air, we shall defend our Island, whatever the cost may be, we shall fight on the beaches, we shall fight on the landing grounds, we shall fight in the fields and in the streets, we shall fight in the hills; we shall never surrender"(Winston Churchill, must be a bald thing).

      They just really don't get it, you don't compete with Linux, it's free, it's open source, you either use it or you don't. How stupid are they really, why pay to develop your own, when it is readily available to use for free. I mean sure, if your some kind of nutter control freak having your customers define how you provide service and support and the nature of product you supply can be offensive but what is it with M$, the whole rest of the company can't stand up to ballmer's delusions.

      --
      Chaos - everything, everywhere, everywhen
    97. Re:Wow by m50d · · Score: 1

      Easy answer: Hardware support. Hard answer: Like it or not, it's actually a very nice kernel; seriously, I'd take it over Linux any day.

      --
      I am trolling
    98. Re:Wow by The+One+and+Only · · Score: 1

      Nelson Mandela is another one time out of ten that it does work. Leonard Peltier, John Brown, thousands of Chinese people at Tiananmen Square, and many others would agree with me.

      --
      In Repressive Burma, it's not just your connection that dies. slashdot.org/comments.pl?sid=314547&cid=20819199
    99. Re:Wow by Nimey · · Score: 1

      In what ways is the NT kernel better?

      --
      Hail Eris, full of mischief...

      E pluribus sanguinem
    100. Re:Wow by debatem1 · · Score: 4, Funny

      I mod randomly.
      The dice have decided- you get 'Insightful'. Congratulations.

    101. Re:Wow by cbhacking · · Score: 1, Troll
      I use Interix (the Unix-like "OS" taht runs in the NT kernel's POSIX subsystem) almost every day. I've got everything from vi (came with it), to ssh and sshd (installed binaries from Interop systems), to programs like sox - I needed it for something a while ago - that I compiled myself, using (a modified, and redistributed with source from Microsoft, version of) the GNU build toolchain.

      To those who ask "Why?" and point out that I could just use Linux/Cygwin, there's a couple of noteworthy points here:
      • I do use Linux, but I don't always want to reboot just to run a bash script or compile a tarball that requires a Unix-like environment.
      • I can, from the shell (bash, though I have a few others as well), run Win32 programs as well, including piping or redirecting their output. This even works with popen() or system() calls.
      • It's native to the system, and probably runs faster that cygwin (no syscall interpretation layer).

      There's probably a few other issues, both good and bad. I've not used Cygwin enough to know, for example, how it works with limited accounts (on XP, or using UAC on Vista); Interix handles it quite nicely including the use of su and sudo (in Vista, su to "root" will require enabling the full Administrator account, however... note that this should be password protected even if disabled since it gets enabled if the computer is booted to Safe Mode). Interix does not come with an X server, but it does come with the X client libraries; I use Xming (a port of the freedesktop.org X server to win32) for an X server when I need it.

      The only real problems are that you can't get block device access to hard drives, etc. and you can't use Linux-specific code or libraries (syscalls or things like the varius Linux-only ioctl tricks). Some programs won't compile because of this. It also uses Windows PE format executables, not ELF binaries (although it does have .so libraries) so it isn't binary-compatible with non-Interix compilations even if it has the needed libraries.
      --
      There's no place I could be, since I've found Serenity...
    102. Re:Wow by Anonymous Coward · · Score: 0

      Micro$haft will appeal to me when they fire every employee, even the ones who don't work there anymore, shut down the company, release all their patents, delete every braindamaged bit of software from every infected computer, and Bill Gates gives back all that money.

      No, I take it back. I'd still hate them.

    103. Re:Wow by spitzak · · Score: 1

      Re #2: this is what Linux does as well (provide a shared library that implements what appears to be the system interface). I'm pretty certain all modern operating systems do this. The actual Linux system api does not exactly match POSIX and does not match exactly between versions.

      On extended attributes, you are going to have the same problem as you have with Emacs with *any* program that tries to copy a file and does not know about the attributes. This happens on Windows, and certainly on the Mac with the "resource fork". I would prefer to see a system where the attributes are embedded into the single stream of text that is in the file, so they are always copied and can be stored on any device. Unix sort of has some trivial examples, such as the "#!" at the start of a file to indicate the program to run. Ideally *everything* about the file, even it's name, could be embedded this way. Gets tricky if protection/acls are embedded but not impossible (it would ignore them excessive permissions).

      Largest problem I see with Linux is a rather rabid requirement for back-compatability with quite-obsolete file system layout requirements. Every reason for the LSB disappeared 20 years ago with the implementation of symbolic links. Would like to see atomic creation of files (no other program sees changes until the file is closed), union mounts, elimination of most/all environment variables and replacement with the existence of files, etc, make FUSE be the primary way to get files and add enormous numbers of named services using it, etc. All of these will break things but need to be done.

      Biggest problem I see with Windows is the use of "wide characters" in the filenames. They need to replace this with utf-8 asap and remove all the triplicated interfaces (old, a, and w) that it has now. And start using forward slash and make "/A/" mean the same as "A:/".

    104. Re:Wow by i.of.the.storm · · Score: 1

      Haha I agree completely, except the general rule of thumb is that predicting your own burial is a guarantee that you will be modded up.

      --
      All your base are belong to Wii.
    105. Re:Wow by Bert64 · · Score: 1

      There was even a "MicroEmacs" made by Commodore to run on the Amiga.... It shipped with AmigaOS by default, I always preferred "ed" that also shipped with the OS tho, and came on the main bootable floppy instead of the "extras" disk (or whatever it was called).

      --
      http://spamdecoy.net - free throwaway anonymous email - avoid spam!
    106. Re:Wow by Dracophile · · Score: 2, Funny
      [n+6] ...

      [n+7] Profit !!!

      --
      Athy, athier, athiest.
    107. Re:Wow by DarkEmpath · · Score: 1

      This is like Satan trying to appeal to Christians.
      It work for George W., didn't it?
    108. Re:Wow by emilper · · Score: 1

      Out of all of the objections you could take of CMD, you choose autocompletion?
      I suppose auto completion is easier to fix. And the brain damaged auto completion of CMD is terribly annoying.
    109. Re:Wow by Tsagadai · · Score: 2, Funny

      I think I saw a video of that. It had two girls and a cup...

    110. Re:Wow by ElderKorean · · Score: 1

      I mod randomly.
      The dice have decided- you get 'Insightful'. Congratulations.


      Pity that you then posted non-anonymously, as now your insightful rating has been removed.

    111. Re:Wow by m50d · · Score: 1

      Microkernel design. Stable ABI. Stable releases of the kernel are actually stable. Kernel "personalities" features. Beautiful unified disk cache/virtual memory system, which is a lot more flexible than the Linux swap business. Cleaner design, e.g. none of the multiple layering of the SCSI/block devices that Linux has (to be fair this is a legacy thing that looks to be going away)

      --
      I am trolling
    112. Re:Wow by Marcos+Eliziario · · Score: 2, Funny

      There's a rumour floating around that Hans Reiser found a solution for that problem for every wife X, where X is not using bullet-proof vests.

      --
      Your ad could be here!
    113. Re:Wow by Anonymous Coward · · Score: 0

      I think you left out the part about Xenix. Microsoft was doing unix in 1979 and selling it to OEM's like Tandy etc.

      http://en.wikipedia.org/wiki/Xenix

      They're doing the same thing with linux only this time they don't have to pay for the license.

      If MS were smart, they'd be thinking about a full blown UNIX OS right now and cutting a deal with SCO to buy their unix kernel back so they can fix it and do what Apple's doing (yet again 8)

      It's scary how things always come full circle in this industry, from thin clients to virtualization to Microsoft UNIX to Microsoft following Apple ROFL.

      Some things will never change :P

      -Viz

    114. Re:Wow by EvanED · · Score: 1

      On extended attributes, you are going to have the same problem as you have with Emacs with *any* program that tries to copy a file and does not know about the attributes.

      Copying a file shouldn't have to know about the attributes... systems should just issue the "copy" system call. It's only if they open the file, read the contents, then write the contents out that you have a problem. And if you copy command is doing that, I would say it's broken. Both because of the attribute thing but also because it deprives the file system the ability to optimize a lot. For instance, the file system may want to implement copy on write. Or maybe you have a networked file system, and it can issue a remote copy command and avoid transferring all that data.

      As for the extended attributes problem, I did indeed get things wrong on the emacs point; it is also broken on Windows. That said, there are other programs that will be broken on Unix but not windows. The problem (which I consider a severe bug) is that when you save "foo.txt" in Emacs, it issues a "rename foo.txt foo.txt~" command, a "open O_CREAT foo.txt" command, and then several writes to the new foo.txt. In other words, foo.txt is a new file.

      Now, Windows has a capability they call file system tunneling, which I thought I had tested and found that it would keep extended attributes, but I guess I'm wrong, because it doesn't.

      Now I'm just even more annoyed at Emacs. ;-)

      I would prefer to see a system where the attributes are embedded into the single stream of text that is in the file, so they are always copied and can be stored on any device.

      But then every program would have to be modified to know about these. Want to add metadata to your photo? Oops, you broke the file format.

      You need either something external to the file (extended attributes), to change a large portion of current code so that it doesn't break, or not use a unified way of storing the information. (Comments for source code, EXIF comments for photos, ...)

      Also, I don't really WANT to see all the metadata when I'm editing, say, a text file, tough I guess this could be added as a editor feature to turn it off.

      Biggest problem I see with Windows is the use of "wide characters" in the filenames. They need to replace this with utf-8 asap and remove all the triplicated interfaces (old, a, and w) that it has now.

      As someone who has only recently been reading about Unicode and text encodings and such, what are the problems with wide characters? The only one I know of is wasted space for western alphabets, but utf-8 wastes space for east Asian alphabets.

      And I don't think it's terribly fair to say that there are three interfaces when the old interface is just a thin layer on top of one of the two others.

      And start using forward slash and make "/A/" mean the same as "A:/".

      I do like this idea. (Actually, I would make /A:/ mean the same thing, which would probably ease porting quite a bit. And people who start deliberately using the new root would probably not use directory names like /A/, /D/, etc. anyway.)

    115. Re:Wow by debatem1 · · Score: 1

      lighten up, francis. Its a joke.

    116. Re:Wow by T.E.D. · · Score: 1

      I think Cygwin's full of too many hacks to be a good starting point. For instance, Windows programs have no ability to fork


      As fate would have it, I just stumbled over this posting from Linus yesterday. Its about the issues around making efficient Win32 ports of Git (the revision control system used for the Linux kernel). In particular, he complains about having to simulate fork+exec with CreateProcess, and with Windows filesystem operations in general.
    117. Re:Wow by spitzak · · Score: 1

      Copying a file shouldn't have to know about the attributes... systems should just issue the "copy" system call...

      Unfortunately it is nowhere near that simple. *something* has to copy the file, for instance the file system that is on the receiving end of your "copy" system call. If it does not know about extended attributes, you lose. The only solution is to get everything into a single stream.

      Emacs, it issues a "rename foo.txt foo.txt~" command, a "open O_CREAT foo.txt" command, and then several writes to the new foo.txt. In other words, foo.txt is a new file.

      That is the only safe way to make a backup. A copy might fail. I suppose you could rename to the ~ file, then copy to the new file (with the copy-file api) and then write over the new file, and the safety would be equal. But it would be rather wasteful as the copy-file api would copy stuff you know is going to be overwritten. You might then say "well the copy file api should take some flags to indicate what to copy" but then you have started down the rats nest of adding options to what should be simple api's.

      In any case *many* people want exactly what Emacs is doing to be the basic behavior of the OS. Writing a file will *always* get you a completely blank one. When you close the written file, it is an atomic operation and at that point anybody opening the file will see the new one, anybody who previously opened the file sees the old one. The old one either disappears from from the directories (so nobody can open it) or it is given a version number (like VMS used to do) or otherwise placed where it can be readable. This is the way it should be done, but it will mean that nothing can possibly be preserved between copies, and this will happen to *all* programs.

      Now, Windows has a capability they call file system tunneling, which I thought I had tested and found that it would keep extended attributes, but I guess I'm wrong, because it doesn't.

      Without a preserved reference to the original file there is nothing the OS can do.

      You need either something external to the file (extended attributes), to change a large portion of current code so that it doesn't break, or not use a unified way of storing the information. (Comments for source code, EXIF comments for photos, ...)

      The second version is what I was proposing. There are obvious problems though, so it could never provide a reliable metadata system. What could work is that there are rules to *attempt* to extract metadata from a file, probably done by user-space programs. Thus if the metadata disappears, in many cases it will magically reappear because it can be extracted from the file.

      Another possibility is to use directories, but change it so that reading a directory produces a data stream that is something like a tar file of all the contents. Writing this to an aware filesystem would produce a matching directory. Writing this to another file system would produce a file that when copied back to the original filesystem would produce the directory. Then all the branches of data is stored in subfiles. Then programs that want to actually use the data rather than copy it would have to open name/data instead of name.

      Also, I don't really WANT to see all the metadata when I'm editing, say, a text file, tough I guess this could be added as a editor feature to turn it off.

      Biggest problem I see with Windows is the use of "wide characters" in the filenames. They need to replace this with utf-8 asap and remove all the triplicated interfaces (old, a, and w) that it has now.

      As someone who has only recently been reading about Unicode and text encodings and such, what are the problems with wide characters? The only one I know of is wasted space for western alphabets, but utf-8 wastes space for east Asian alphabets.

      By far the biggest problem is that wide characters cannot represent an arbitrary stream of bytes, for instance an illegal utf-8 encoding. This means that a program cannot re

    118. Re:Wow by EvanED · · Score: 1

      Unfortunately it is nowhere near that simple. *something* has to copy the file, for instance the file system that is on the receiving end of your "copy" system call. If it does not know about extended attributes, you lose.

      Yes, but this only needs done once per file system, which isn't bad at all. And it should already be done or I'm even more dismayed at the current state of support. (I don't have a Linux box to test it there, but on Windows, extended attributes are indeed copied, assuming you are going NTFS->NTFS.)

      That is the only safe way to make a backup. A copy might fail. I suppose you could rename to the ~ file, then copy to the new file (with the copy-file api) and then write over the new file, and the safety would be equal

      You could also copy to the ~ file. (If that fails you likely wouldn't be able to either rename to ~ or create the new file anyway.)

      Or you could use something like transactional NTFS, which Vista provides, and avoid the whole shuffling files around problem. Of course, then you cease to be portable, even to previous versions of Windows.

      (I also wonder if transactional NTFS was added to help with the case if transactional memory becomes common in a few years, because reversing I/O is one of the major problems with it.)

      Without a preserved reference to the original file there is nothing the OS can do.

      The file name is almost a preserved reference. You didn't read that link, did you? Ever notice how Windows keeps file creation date in addition to the last modified and last accessed dates? That date is preserved, even when something acts like Emacs. The reason Windows needed this feature is because the long file name also acts like metadata to 16-bit programs... you don't want "c:\some file with long name.txt" to suddenly become "c:\somefi~1.txt" because you opened it in a 16-bit, non-LFN aware program which removed the old file and recreated "c:\somefi~1.txt".

      Like I said, it's a huge hack, but it works pretty well. And the same thing could be done with extended attributes.

      The second version is what I was proposing.

      So you propose rewriting a large portion of our current collection of libraries and applications so that they accommodate extra information as we throw out a large portion of our current file formats? Because that's what the second option was...

      Another possibility is to use directories, but change it so that reading a directory produces a data stream that is something like a tar file of all the contents. Writing this to an aware filesystem would produce a matching directory. Writing this to another file system would produce a file that when copied back to the original filesystem would produce the directory. Then all the branches of data is stored in subfiles. Then programs that want to actually use the data rather than copy it would have to open name/data instead of name.

      This is probably the best realistic way of handling metadata that still satisfies most of my desires.

      It's not perfect because I still can't tell most programs to open just name (instead of name/data) and see just the data, which is one of the benefits of using alternate streams instead of directories in the first place. But it wouldn't be too hard to have applications support it (you may even be able to pick up most of them with a change to the standard OS open dialog, so that it returns name/data instead of name as the chosen file), and having Explorer or your equivalent file browser support it would already be a big step even if the open dialog idea didn't pan out well.

      By far the biggest problem is that wide characters cannot represent an arbitrary stream of bytes, for instance an illegal utf-8 encoding. This means that a program cannot rely on uniqueness of a stream of bytes being equivalent to meaning the filename is unique (this is also why case independence is bad and why OS/X decomposed-only utf8 is bad). This leads to nasty security vulnerabilities

    119. Re:Wow by spitzak · · Score: 1

      - What is the value of being able to express illegal utf-8 strings? It seems you would want to reject them anyway before using such a string to store file names.

      This is necessary if your file system has a file on it named by an illegal utf-8 string and you want to open it!

      If you take a case-sensitive view, why can't a stream of wide characters be viewed as a stream of bytes for string comparison purposes?

      Because you can translate more than one utf-8 string into the same utf-16 string (this will happen if the utf-8 string contains an illegal encoding or an encoding of a the surrogate half-characters). This means that comparing the utf-16 strings does not return the same result as comparing the utf-8 strings. OS/X decomposed characters are also a problem

      How does this lead to the problems that you say?

      It basically comes down to a program saying "these two utf-8 strings are not equal, therefore I know that I can write the file named by one and not clobber the file named by the other". When the program gets this wrong you get security vulnerabilities and you lose data and you get weird error messages.

      Whether case-independent file systems is bad is probably another discussion

      They are bad because the filenames are no longer a plain string of bytes. What you are really asking for is a spelling corrector, and it is unclear why you (and so many others) think a spelling corrector should be part of the file system. The system should provide a way to quickly list matching filenames to an arbitrary regexp (this is needed rather than just readdir because some file systems have an infinite number of available names) so that a program or back-compatability library can quickly do case changing and other spelling correction if the filename it got was wrong.

      So the unadorned interface isn't really a third interface, it just lets you switch between the *A and *W versions with the UNICODE symbol.

      I was talking about the a, w, and "mb" interfaces. Though the existence of the the mb interface is due to the poor design of the Asian dual-character encodings. UTF-8 can be used with the old ASCII interface because of the ASCII compatability and the extremely low probability that text in ISO-8859-1 would look like a legal UTF-8 encoding (preserving these, and allowing programs to generate arbitrary streams of bytes, are the reasons I want illegal utf-8 strings to be legal filenames).

    120. Re:Wow by Anonymous Coward · · Score: 0

      Or my example above about some mechanisms that probably shouldn't be there. (Another example of this is ReadProcessMemory and WriteProcessMemory, and the ability to inject threads into other processes unilaterally. Extremely useful for some things, but also a huge malware propagation vector.)

      These are simply mechanisms for debugging, and Unix-type systems have exactly the same capabilities. They are bounded by the security system; by default that's based on user account (for both NT and Unix).

    121. Re:Wow by Anonymous Coward · · Score: 0

      If you take a case-sensitive view, why can't a stream of wide characters be viewed as a stream of bytes for string comparison purposes?

      Because you can translate more than one utf-8 string into the same utf-16 string (this will happen if the utf-8 string contains an illegal encoding or an encoding of a the surrogate half-characters). This means that comparing the utf-16 strings does not return the same result as comparing the utf-8 strings.

      An illegal UTF-8 string is an illegal UTF-8 string, so there is no valid UTF-16 representation of it. If your filesystem is designed to support Unicode, this issue does not come up. If it's not designed for Unicode, then you can't pretend it deals with Unicode and do Unicode processing on your filenames.

      OS/X decomposed characters are also a problem

      You seem set on conflating two entirely separate interfaces into one big mess, which I find baffling. When you design something to support Unicode, you define a set of rules for consistent processing based on Unicode semantics. Both Windows/NTFS and OS X/HFS+ do this just fine.

      Decomposition is a subset of the normalization semantics for Unicode in general. If you're processing Unicode, you need to deal with this, full stop. Trying to process Unicode text as byte streams (or even code unit streams) will get you nowhere, regardless of encoding form.

      How does this lead to the problems that you say?

      It basically comes down to a program saying "these two utf-8 strings are not equal, therefore I know that I can write the file named by one and not clobber the file named by the other". When the program gets this wrong you get security vulnerabilities and you lose data and you get weird error messages.

      That's because that is a fundamentally insecure practice for working with any filesystem. If you want to know precisely what you're operating on, you ask the filesystem! That means doing things like opening a file to test whether it exists and is the file you intended it to be, or creating a file using an interface that will fail if the file already exists. You can't work around this by trying to exactly duplicate every behavior of every filesystem you will ever work with at an application level. Attempting to do so is a security bug in your application, not a design fault of the filesystem. (The same holds true for pretty much any modern and potentially complex platform, filesystem or otherwise. You simply don't duplicate the work or make naive assumptions; you use the interface you've been given to get authoritative answers.)

      Whether case-independent file systems is bad is probably another discussion

      They are bad because the filenames are no longer a plain string of bytes.

      Filenames are a human interface element, and haven't ever been a plain string of bytes. There have always been special rules for them.

      Some of your other comments lead me to think you believe modern Unicode-based case-insensitive filesystems do all their processing at the OS level. (It's a common theme with application-based processing of filenames.) However, both NTFS and HFS+ operate like self-consistent databases, which means they store information on case mappings in the filesystem itself, to avoid software versioning issues. NTFS in particular is actually a case-sensitive filesystem; there is a casetable in the filsystem metadata that is used by the driver to solve case-insensitive requests as appropriate.

      It's not just some crackpot design someone came up with in 10 minutes and implemented for the hell of it.

      So the unadorned interface isn't really a third interface, it just lets you switch between the *A and *W versions with the UNICODE symbol.

      I was talking about the a, w, and "mb" interfaces. Though the existence of the the mb interface is due to the poor design of the Asian dual

    122. Re:Wow by kesuki · · Score: 1

      the trabant is the first car to use recycled materials (wool and the plastic) but has the worst vehicle emissions... but it's fuel economy wasn't half bad, and people kept them running an average of 28 years. what car enthusiast wouldn't want a trabant?

    123. Re:Wow by Gearrion · · Score: 1

      um.. No. Marriage is a covenant between God and man. It is not a business contract and by the covenant with god you state that you're wife and you are one body and flesh and all property and assets are between the both are considered as one. God implemented divorce if the woman was the guilty party and she would most often be stoned to death and if not left with no assets at all.

                With the new covenant with Jesus he discouraged divorce all together saying the father only gave the option cause men where hard at heart towards each other and it was to appease man and was not apart of marriages original design by God.

      If you consider that marriage is to combine two as one flesh, you would understand that a prenuptial agreement tries to undermine God design. It is a attempt to make it more like a contract to protect ones assets from their poor decisions they make in choosing a partner as a direct result of the inability to hear Gods will in thier lives.

      You can say all you want about it, but marriage was created in the garden of Eden, so unless you have written text that is dated beyond that time you don't really have a argument otherwise.

    124. Re:Wow by cornjones · · Score: 1

      as the GP mentioned, marriage was both a legal and a religious concept. The legal/state part is a contract between two people. The religious part is responsible for what ever combining of flesh or omnipotent fantastical friend's intention you may want it to be.

      A prenup is part of the state part.

      i know, i know... don't feed the trolls...

      PS...
      God implemented divorce if the woman was the guilty party and she would most often be stoned to death and if not left with no assets at all.
      religions like the one in the parent post always make me wonder why any woman would believe in that religion.

    125. Re:Wow by DaedalusHKX · · Score: 1

      Yeah, because we all see, that according to God, spineless wimps like Adam damned us all to hell, right? Why? Because if the garden was so good, and man in the image of God, then why was man so weak as to get "tricked" into gaining knowledge?

      It seems to me your precious marriage is why we ARE NOT in the garden anymore. Perhaps you should reevaluate what you exchanged to be married to someone that got you damned for eternity (by your loving God) because of the foolishness of the wife and the gullibility and weakness of the husband.

      If you ask me, marriage was a way of saying "you broke it you bought it, sucker!"

      And those of us married sure did.

      PS - marriage dates to before the Torah and Talmud... thus before your vaunted "old testament".

      --
      " What luck for rulers that men do not think" - Adolf Hitler
  2. MS is a business by Shados · · Score: 4, Insightful

    A business tries to appeal to its market. The market changed. MS will change too. Its just long to shift gears of such a behemoth.

    1. Re:MS is a business by morgan_greywolf · · Score: 1

      Oh, c'mon. You're not really buying this crap are you? If this were remotely true, it would mean that Microsoft is pretty much scrapping it's entire codebase for Windows and replacing it with a Unix or Unix-like architecture. And, they're gonna ship it by late next year.

      Do you also believe in Santa Claus? The Easter Bunny?

    2. Re:MS is a business by Shados · · Score: 2, Informative

      Err? Nothing even remotely hint at that.

      All it means is that Windows (which btw, already has a partial, optional, Unix-like stack btw!) is going to offer more open source tools, more command-line utilities, more GUI-less fonctions, more open protocols.

      Thats it. And thats been in the process for like ever (The latest version of Exchange for example, is fully administrated from Windows Powershell. The GUI works Unix-style, with a front end calling the CLI commands.).

      Nothing more, nothing less.

    3. Re:MS is a business by AKAImBatman · · Score: 4, Informative

      it would mean that Microsoft is pretty much scrapping it's entire codebase for Windows and replacing it with a Unix or Unix-like architecture.
      Says who? The NT kernel was designed to be able to project different "personalities", much in the same way that Mac OS X does. The POSIX system necessary has been available in Windows for just shy of forever in an effort to win government contracts and companies that require POSIX as a checkbox on their requisition forms.

      Of course, their support hasn't been very good, but that has more to do with an unwillingness on Microsoft's part rather than any real technical reason. Typically Microsoft implements sub-standard support, then claims that their support is top notch. A few examples of this are the David Korn debacle:

      http://slashdot.org/article.pl?sid=01/02/06/2030205

      Just as bad was the Kerberos debacle where Microsoft extended Kerberos for Windows such that Unix machines could subscribe to a Windows domain, but a Windows machine could not subscribe to a Unix domain. I called a rep on it in one of their presentations on Win2K, and he assured me that I was mistaken.
    4. Re:MS is a business by MightyMartian · · Score: 4, Informative

      Windows NT has had a POSIX layer since the beginning. At any point Microsoft could have extended this and ported over GNU tools if they had wanted. The whole thing smells of bullshit, and Powershell is not bash. It may have its advantages, but you sure can't bring over a library of thousands of shell scripts.

      Cygwin is a solution, but of course, that has nothing to do with Microsoft.

      --
      The world's burning. Moped Jesus spotted on I50. Details at 11.
    5. Re:MS is a business by smcdow · · Score: 1

      That POSIX layer isn't.

      It's POSIX only in name, but function.

      --
      In the course of every project, it will become necessary to shoot the scientists and begin production.
    6. Re:MS is a business by Shados · · Score: 1

      You're missing my point too. I'm not saying MS is going to make Windows another Unix. I'm saying it will give Windows some of the advantages of Unix environments. That does not mean GNU tools. That just means the ability to natively admin a server with a command line (instead of having to use remote desktop or install SSH)), a way to make minimal installs, a way to do most tasks with a shell and automate them along with better scripting, more protocol compatibility, etc.

      Who talked about using existing scripts? We're talking about giving it equivalent abilities. Not to make it a clone. Again, if this strategy from Microsoft is new to you people, you know even less about MS than I thought so far. What the article describes has been going on for a -while-, and its not new. People in this discussion (like you) are just reading too much into it.

    7. Re:MS is a business by TheRaven64 · · Score: 4, Informative

      Unfortunately, POSIX allows a large number of functions to return ENOTIMPLEMENTED, instead of actually working. The original POSIX subsystem did this everywhere it was permitted. It also couldn't be used in conjunction with the Win32 subsystem, so you could only use it for command-line apps. Cygwin filled the gap a bit by providing an implementation of the POSIX APIs that wrapped Win32 calls. More recently, Services For UNIX have provided an updated POSIX subsystem and userland that is more-or-less useable.

      --
      I am TheRaven on Soylent News
    8. Re:MS is a business by Anonymous Coward · · Score: 0

      As I recall the original posix layer wasn't worth a pinch of racoon shyte to begin with. A fix/rewrite would be a massive relief for me.

      Cygwin is flakey. Don't get me wrong, I install Cygwin all over the place in order to maintain my sanity. It's just that unix win32 does not translate all that well. Unix permissions to ACLs is hardly a 1:1 map and the windows authentication system is just fundamentally damaged. Signals are out to lunch as well.

      I would *love* to be able to install windows and run make, sh and cc (such that they function) from the command-line, right out of the box. Inclusion of ssh would be bliss as well, as would a headless installer. I'm sure MS will get all of that working just as soon as they finish up with WinFS.

    9. Re:MS is a business by nine-times · · Score: 2, Insightful

      Yeah, I actually think that, in abstract, this sort of thing is very appropriate. Microsoft *should* be trying to appeal to the Unix/Linux crowd. They should be trying to make there stuff more interoperable, opening their protocols, giving headless servers, supporting GNU tools, etc. There's a case to be made for doing those sorts of things because of business interests, economic benefit, and technological need.

      The only problem I see is that Microsoft has not earned people's trust that they'll do these things properly. They've earned a reputation for being willing to hobble their own products in order to maintain vendor lock-in and damage their competition.

    10. Re:MS is a business by Shados · · Score: 1

      Indeed. Except MS has been failing to keep its lock-ins more and more lately. If this time isn't it, next time will be. They'll have to change strategy or go bankrupt in the long run... And once they lost all of their locks it will be too late to start working on things like this.

    11. Re:MS is a business by node+3 · · Score: 1

      A business tries to appeal to its market. The market changed. MS will change too. Its just long to shift gears of such a behemoth. That's only true for non-monopolies. Monopolies, on the other hand, have the ability to alter the market when the market's desires and the monopolist's desires are in conflict. This is what makes monopolies so problematic and generally either outlawed or strongly regulated.

      While Microsoft is no longer as strong a monopoly as it was before, it's still acting like one. Perhaps Microsoft really is trying to change (as you've implied), but given their past behavior, it's insane to believe they are until they can demonstrate that they really have turned a new leaf.

      This distrust of MS is fully deserved. It's them reaping what they've sown.
    12. Re:MS is a business by jc42 · · Score: 5, Interesting

      That POSIX layer isn't. It's POSIX only in name, ...

      Actually, the proper term is WEIRDNIX.

      For those not familiar with the term, WEIRDNIX was the POSIX crew's term for a hypothetical implementation that was technically compliant with all the POSIX standard, but implemented everything in the worst possible way. The idea was to find bugs in the POSIX standard that would allow implementers to claim compliance while violating the intent of the standard.

      Mostly, people just sent in specs for a component that followed the standard but would in some way sabotage software that expected the obvious behavior. When NT came out, there were a number of discussions of its POSIX implementation, and a lot of people explained it by saying that Microsoft had done a full implementation of WEIRDNIX. Hardly anyone's POSIX software would run sanely on NT, and that was a simple, elegant explanation of why.

      Is there any reason to expect things to be different this time around?

      --
      Those who do study history are doomed to stand helplessly by while everyone else repeats it.
    13. Re:MS is a business by value_added · · Score: 1

      I'm saying it will give Windows some of the advantages of Unix environments. That does not mean GNU tools. That just means the ability to natively admin a server with a command line (instead of having to use remote desktop or install SSH)), a way to make minimal installs, a way to do most tasks with a shell and automate them along with better scripting, more protocol compatibility, etc.

      I'm confused here. What I regard as functional starts with a terminal, a fully-featured shell, a way to connect securely to remote systems, and a basketful of standardised tools to do anything and everything needed, along with standardised documentation for each. And that's an uncomfortable minimum.

      What you're suggesting is what Microsoft has already been doing. Introducing a series of ad hoc command-line utilities (an embarssingly limited subset of what's needed to get anything done) that may or not be included as part of the default installation and may or may not work with the next go around, all to be run using shortcuts (due to the lack of a sane path) from cmd.exe, the Notepad of command-line environments. You think incremental improvements are the solution to goofiness?

      Sorry, but this whole thing reminds of the absurd statement everyone made that Windows 2000 could be managed entirely using command-line tools only. The fact of the matter is Microsoft doesn't get it, and quite frankly, I don't expect them to any time soon.

      The OP put it best when he said Powershell ain't bash.

    14. Re:MS is a business by AJWM · · Score: 1

      Do you also believe in Santa Claus? The Easter Bunny?

      Hey, where did you think Microsoft is going to get that Unix-like architecture, the Tooth Fairy? Sorry, but she's helping out Torvalds with Linux. (Santa Claus, generous guy that he is, seems willing to help both.)

      --
      -- Alastair
    15. Re:MS is a business by TemporalBeing · · Score: 1

      Windows NT has had a POSIX layer since the beginning. At any point Microsoft could have extended this and ported over GNU tools if they had wanted. The whole thing smells of bullshit, and Powershell is not bash. It may have its advantages, but you sure can't bring over a library of thousands of shell scripts.

      Cygwin is a solution, but of course, that has nothing to do with Microsoft. They did - it's called Service for Unix and it mostly utilizes GNU tools. It's otherwise primarily based on Interix. At one point you could get the SFU Source code - I thought it was for 3.5 but might have been for an earlier version, which was all GNU tools. Some quick searches aren't finding it. Possible it's with the installer. (Downloading now to find out.)

      The POSIX sub-system works quite well, and is quite functional. However, they didn't give it the performance they gave Win32 - the plan being, tell them it can run on Windows under the POSIX sub-system, then get them to port to Win32 when they realize that they can't get the performance under POSIX they can under Win32.

      Someone could probably figure out how to write a sub-system for the NT Kernel that could provide better performance to replace the POSIX one. But good luck figuring out the detailed interaction to deal directly with the NT Kernel as an API sub-system.
      --
      Truth is like the sun. You can shut it out for a time, but it ain't goin' away. - Elvis Presley (source: imdb.com)
    16. Re:MS is a business by TemporalBeing · · Score: 1

      The NT kernel was designed to be able to project different "personalities", much in the same way that Mac OS X does. The POSIX system necessary has been available in Windows for just shy of forever in an effort to win government contracts and companies that require POSIX as a checkbox on their requisition forms.
      Odd you mention gov't contracts since the Windows Gold Disk (put out by Microsoft!) disables the POSIX sub-system, and removing all the supporting DLLs for it.
      --
      Truth is like the sun. You can shut it out for a time, but it ain't goin' away. - Elvis Presley (source: imdb.com)
    17. Re:MS is a business by MightyMartian · · Score: 1

      Alternatively, I can install Linux or one of the BSD variants, and then I don't have to worry about it at all.

      --
      The world's burning. Moped Jesus spotted on I50. Details at 11.
    18. Re:MS is a business by Locutus · · Score: 2, Interesting
      oh pleaz, there is nothing to show that Microsoft is appealing to its market and that is not how Microsoft has worked over the last 20 something years. They are adjusting to the competition and those adjustments are designed to eliminate the competition. THAT is how Microsoft works.

      Microsoft is profitable because of Windows and without Windows they would be just another software company. Because they know Windows must continue to exist in its dominant and monopoly position, they must stop threats from diminishing the position Windows has. That's it, Microsoft in a nutshell. Protect Windows market position and continue making billions in profits per quarter. People will take what is handed to them by Microsoft and like it because most see there being no other option.

      I'll say it again here, Microsoft has been in the business of anti-competition for over 20 years. Why do people not see this and think that this is Microsoft adjusting to the market? I hate to quote John C. Dvorak but here's a bit of insight as to how this company is managed:

      As to how and why the OS failed to become a huge success--I'm leaving the debate open this week. Steve Ballmer comes to mind. He started the ball rolling by proclaiming OS/2 to be the next great operating system, and within a few years he was walking around the floor of a computer show putting disks into computers running OS/2 to crash the systems and prove that OS/2 wasn't crash-proof! http://www.pcmag.com/article2/0,4149,768242,00.asp

      There are hundreds of examples of Microsoft's anti-competitive behavior and nothing has changed or has ever changed. It is in their DNA and no press release changes that. IMO.

      LoB
      --
      "Anyone who stands out in the middle of a road looks like roadkill to me." --Linus
    19. Re:MS is a business by KidSock · · Score: 1

      it would mean that Microsoft is pretty much scrapping it's entire codebase for Windows and replacing it with a Unix or Unix-like architecture. Says who? The NT kernel was designed to be able to project different "personalities", much in the same way that Mac OS X does. The POSIX system necessary has been available in Windows for just shy of forever in an effort to win government contracts and companies that require POSIX as a checkbox on their requisition forms. No. The POSIX subsystem is for trivial little commandline utilities. It doesn't even have sockets. It's basically worthless. Personally I think they did it just so that they could claim POSIX compatibility, split hairs and trick people into thinking Windows was compatible with UNIX.

      Just as bad was the Kerberos debacle where Microsoft extended Kerberos for Windows such that Unix machines could subscribe to a Windows domain, but a Windows machine could not subscribe to a Unix domain. I called a rep on it in one of their presentations on Win2K, and he assured me that I was mistaken. Yes, you were mistaken. Windows client accounts can be hosted by MIT and Heimdal KDCs. The KDCs just don't generate a PAC (which was not a "debacle" or even controvesial since an MIT or Heimdal KDC does not have the necessary group information to put into the PAC). The "debacle" you speak of was probably when MS claimed that the PAC information was a "trade secret". MIT sued them over it but MS quickly recinded the claim and published documentation about the PAC (which has since been used in Samba 4 incedentally). MIT and MS get along just fine. It's only people who actually believe what they read on Slashdot that think otherwise.

      The OP is right. A GNU compatible system on Windows is a diffcult project. There are syscalls that are almost impossible to emulate efficiently on Windows. For one, the Windows' process model is fundamentally different which makes implementing something like fork(2) a problem.
    20. Re:MS is a business by nuzak · · Score: 1

      WEIRDNIX wouldn't happen to be the native OS of the DeathStation 9000, would it?

      --
      Done with slashdot, done with nerds, getting a life.
    21. Re:MS is a business by nuzak · · Score: 1

      > The NT kernel was designed to be able to project different "personalities", much in the same way that Mac OS X does.

      From everything I've heard, Darwin does not run BSD as a personality, but it's instead quite integrated into the kernel. Which makes me suspect it doesn't quite support personalities to the degree of Mach.

      --
      Done with slashdot, done with nerds, getting a life.
    22. Re:MS is a business by spectecjr · · Score: 1

      For those not familiar with the term, WEIRDNIX was the POSIX crew's term for a hypothetical implementation that was technically compliant with all the POSIX standard, but implemented everything in the worst possible way. The idea was to find bugs in the POSIX standard that would allow implementers to claim compliance while violating the intent of the standard.

      So you're saying that the POSIX standard was badly written?

      Reminds me of the original Java 1.0 days. They didn't specify what direction Z-order was in the UI, so Netscape had one way of doing it, and everyone else including Sun did the opposite. Lovely.

      --
      Coming soon - pyrogyra
    23. Re:MS is a business by HiThere · · Score: 1

      Well, they *did* say UNIX, not Linux.

      Perhaps they'll find some suckers. (You can easily guess my take on their offer.)

      --

      I think we've pushed this "anyone can grow up to be president" thing too far.
    24. Re:MS is a business by EvanED · · Score: 1

      Windows NT has had a POSIX layer since the beginning. At any point Microsoft could have extended this and ported over GNU tools if they had wanted. The whole thing smells of bullshit, and Powershell is not bash.

      And actually they've done that. The POSIX subsystem has been extended to POSIX.2, and you can get a small library of pre-compiled programs for it. Including, yes, a port of Bash.

    25. Re:MS is a business by spitzak · · Score: 1

      No you are mistaken. At the time a Windows client would not work without that "PAC" information. Thus Windows clients could not use non-Windows hosts.

      Also Microsoft did not "publish" the documentation. They specifically threatened Slashdot and told them to remove links to a leaked version of the documentation. Eventually they gave up and thus the leaked information is the "published" information you seem to think exists.

    26. Re:MS is a business by Anonymous Coward · · Score: 0

      You obviously haven't had the full force of 1,000 developers work full time on anything you tell them to.

    27. Re:MS is a business by jc42 · · Score: 1

      So you're saying that the POSIX standard was badly written?

      No; you don't understand - the POSIX committee put out the request for WEIRDNIX implementations. They understood that it's difficult to get such things right, so they invited the crowd of unix hackers to examine their standard and find the things that hadn't been phrased quite right. They used the WEIRDNIX things that people sent them, to improve the standard.

      Of course, like most standards, they still didn't manage to describe it all in a completely unambiguous manner. That's hardly possible in as messy a language as English. Microsoft found lots more little ambiguities that they missed, and took advantage of them to make the NT POSIX library as awful as they could (while still technically following the standard).

      It did lead to a fair amount of abstruse, tongue-in-cheek geek humor.

      --
      Those who do study history are doomed to stand helplessly by while everyone else repeats it.
    28. Re:MS is a business by cbhacking · · Score: 1

      I only discovered the POSIX subsystem in NT when I started running Vista betas, but if it's "implemented in the worst possible way"
        then POSIX must be a very well-designed spec indeed. There are quite a few programs that run just flawlessly on Interix (the Unix-like environment that runs in the POSIX subsystem, you can think of it as the OS and indeed uname identifies it as such). Bash is one such program - I have powershell installed, and quite like it, but I know bash better and often end up using it instead. ssh/sshd, svn, GNU make, and quite a bit more runs easily and essentially flawlessly. It may just be that MS has patched up a lot of the initial issues, but overall I'm very happy with bash in Interix - it even deals nicely with Win32 programs, which makes it suitable for replacing cmd.exe as long as I don't need Win16 (it won't do those).

      --
      There's no place I could be, since I've found Serenity...
    29. Re:MS is a business by jc42 · · Score: 1

      As computer standard go, POSIX is actually pretty well written. Much of this is due to them actually responding to criticisms such as the WEIRDNIX ideas by revising the standard appropriately. They got a lot of points with developers for their inviting criticism and then actually listening when criticism flooded in. Who'd'a thunk a standards body would actually do such a thing?

      It's also true that MS has improved their POSIX library over the years. Rather than viewing their initial release from the common "MS is evil" theory, it really looked more like the result of the usual corporate pressure on developers to get a minimally acceptable release out the door as quickly as possible. This phenomenon is hardly unique to Microsoft; I've seen it on every project I've ever worked on. But MS's stuff is often more visible than other companies', so it gets attention when it causes problems.

      Also, MS does have a bit of a history of sticking with an initial release and not funding improvements until sufficiently many customers were complaining sufficiently loudly. Consider IE as just one well-known example. Again, this is hardly anything unique to that one company. But we programmers do tend to notice when a company with the clout of MS is touting their support of a standard, while in our labs we see a product that requires an inordinate number of #ifdefs in our code.

      --
      Those who do study history are doomed to stand helplessly by while everyone else repeats it.
    30. Re:MS is a business by cbhacking · · Score: 1

      Interesting... I hadn't looked into the history of POSIX much (and it was before my time, so it's all history to me). No disagreement with your characterization of MS in general, but the comment about #ifdef s surprised me a little... I just finished a rather complicated multi-threaded server/client networked app that required interprocess communication in C. It had to compile and run on a Nokia N800 (uses a variant of Debian Linux on a ARM processor) but I used (among other things) my Windows box via Interix for building and testing... and there were only two places I had to check for Interix: the one to get/change the IP address (there's surely a better way to do this than
      system("/sbin/ifconfig wlan0 ...");
      but I didn't know of one that would allow us to change the IP to a static value - and it's what we were told to use for this particular school project - except on Interix I needed to use the Win32 program netsh instead) and reading the MAC address (there's GOT to be a getter way to do this on Windows/Interix, but I ended up just using
      popen("ipconfig /all | grep ...");
      which, since it only had to run once at server startup was sufficient). Note that the Linux alternative to this used an ioctl #define not present in anything EXCEPT Linux, as best I can tell. Named pipes (FIFOs) were used for the interprocess communication and worked fine. I couldn't compile the GUI client in Interix - it relied on a number of libs specific to the N800 - but the server worked without a hitch. Some of the development was done on Linux (Fedora Core 7) as well, but I actually found the manpages often more useful in Interix.

      --
      There's no place I could be, since I've found Serenity...
  3. Microsoft: UNG's not GNU by FlameWise · · Score: 5, Funny

    > UNG, which stands for UNG's not GNU

    Wait is it april's fool's already?

    1. Re:Microsoft: UNG's not GNU by morgan_greywolf · · Score: 5, Funny

      In related news, Microsoft announced today that it has hired Richard M. Stallman and Linus Torvalds, who will be working together as partners on their new UNG project. Torvalds and Stallman hugged following a speech given by Steve Ballmer, and promised to put their differences in the past.

    2. Re:Microsoft: UNG's not GNU by arclyte · · Score: 3, Funny

      Oh, and here I was thinking the name "UNG" was just them foreshadowing their user's responses, as in... "This new M$ OS is supposed to be like Unix, but UNG! it's worse than DOS!"

    3. Re:Microsoft: UNG's not GNU by the_B0fh · · Score: 2, Funny

      No wonder Stallman's stepping down as the maintainer of EMACS. He's too busy GPLing Windows.

    4. Re:Microsoft: UNG's not GNU by mhall119 · · Score: 1

      You left out Theo de Raadt. Shame on you.

      --
      http://www.mhall119.com
    5. Re:Microsoft: UNG's not GNU by Anonymous Coward · · Score: 1, Funny

      ... before RMS ceremonially shaved off his beard, Linus crushed a live penguin underfoot and they all then chanted, "We're gonna fucking KILL Google!!" together.

      Man, it was a beautiful press conference.

      Me, I'm just glad this whole FOSS thing is finally over... it's been going on quite long enough, thank you.

    6. Re:Microsoft: UNG's not GNU by Abreu · · Score: 2, Funny

      Don't forget Andy Tanenbaum's emotional toast blessing the union during the celebratory dinner!

      --
      No sig for the moment.
    7. Re:Microsoft: UNG's not GNU by jc42 · · Score: 1

      Oh, and here I was thinking the name "UNG" was just them foreshadowing their user's responses, ...

      Me, too, but my immediate thought was that where I'd seen "UNG" before was in porn comics, where it was used for the sounds from the female participants.

      --
      Those who do study history are doomed to stand helplessly by while everyone else repeats it.
    8. Re:Microsoft: UNG's not GNU by Anonymous Coward · · Score: 0

      This story can't be true. I know RMS wouldn't join in unless the product is called GNU/UNG!

    9. Re:Microsoft: UNG's not GNU by ElectricRook · · Score: 2, Insightful

      So if UNG stands for "UNG is not GNU"... And GNU stands for "GNU is not UNIX"...

      Then it seems to me, that perhaps, there is a very slight possibility that "UNG _is_ UNIX" ???

      I guess that when the going gets weird, the weird go pro... (yes, that's a stolen sig)

      --
      - High Tech workers, please say NO to Union Carpenters, their Union sees fit to control our compensation.
    10. Re:Microsoft: UNG's not GNU by AJWM · · Score: 4, Funny

      Of course, that would be Microsoft UNG, or MUNG.

      Figures.

      --
      -- Alastair
    11. Re:Microsoft: UNG's not GNU by Count+Fenring · · Score: 1

      Holy sh*t! They're just dusting off Xenix, renaming it, and porting Winelib to it to run MFC applications! We've solved the mystery, guys.

    12. Re:Microsoft: UNG's not GNU by jimmypw · · Score: 1

      I hate self referencing acronyms, i cant stop thinking about them.

    13. Re:Microsoft: UNG's not GNU by Anonymous Coward · · Score: 0

      - I am not ElectricRook
      - I am not Linus

      => (slight possibility) EletricRook is Linus???

    14. Re:Microsoft: UNG's not GNU by morgan_greywolf · · Score: 1

      You left out Theo de Raadt. Shame on you. It's UNG, not UNB (UNB's Not BSD?!)
    15. Re:Microsoft: UNG's not GNU by mhall119 · · Score: 1

      True, it would have been better in reply to the AC who brought Tenenbaum into it, but what's the point in replying to an AC?

      --
      http://www.mhall119.com
    16. Re:Microsoft: UNG's not GNU by ElectricRook · · Score: 1

      In another life, I was a hardware tech (60's military simuilator), and our digitized audio installed in the 80's, ran on a Xenix system. The goof-ball Sysadmin found a bunch of files he thought were "Sexy Porn", and deleted them... Fortunately we had this marvelous thing call backup tapes, because he was deleting files that matched $EXECPROF.

      --
      - High Tech workers, please say NO to Union Carpenters, their Union sees fit to control our compensation.
    17. Re:Microsoft: UNG's not GNU by Richthofen80 · · Score: 1

      You'd think so, but there are parts of MS that appreciate humor. MS's game library SDK (essentially a framework of managed code [.NET] libs on top of DirectX) is called XNA. The XNA stands for XNA's not Acronymed. DirectX itself wasn't even the original name for the product that we know today as DirectX. It was originally Windows Game something-or-other, but since all the function calls were called like 'Direct'y, such as DirectShow, DirectPlay, DirectInput, etc, a journalist referred to it as DirectX. MS liked the name and ran with it.

      --
      Reason, free market capitalism, and individualism
    18. Re:Microsoft: UNG's not GNU by Jon_E · · Score: 1

      SRAs are fine .. personally i hate SRTs ..
      (Self Referencing TLAs (three letter acronyms))

    19. Re:Microsoft: UNG's not GNU by ncohafmuta · · Score: 1


      nope, it's the cave-men operating system.

  4. this has to be fake by kevgaxxana · · Score: 2, Interesting

    microsoft is way to, what's the word, oh yeah, proud to let their os be subject to community modification.

    --
    In Soviet Halo, the game kills you (socially anyway)
    1. Re:this has to be fake by stoolpigeon · · Score: 1

      you are so right - quite obviously Orochimaru is the original character. I don't think evil had ever been associated with a snake before that - so Rowling must have stolen it! What a hack.

      --
      It's hard to believe that's how Micronians are made. Why don't we see it right now by having you both kiss one another?
    2. Re:this has to be fake by betterunixthanunix · · Score: 4, Informative
      Competing with GNU does not mean that they are releasing open source software. What it means is that they would be release tools that are compatible with GNU, so that companies that are running GNU right now would have an easy time switching to Microsoft. It should be interesting to see Microsoft pull this off without violating the GPL.

      Also, this idea reeks of embrace/extend/extinguish.

      --
      Palm trees and 8
    3. Re:this has to be fake by jedidiah · · Score: 1

      What's a Dementor?

      A Nazgul that's gotten thrown off his horse.

      Get off it. Rowling recycles like Lucas.

      --
      A Pirate and a Puritan look the same on a balance sheet.
    4. Re:this has to be fake by stoolpigeon · · Score: 1

      Yes - disembodied soul sucking entities were the original creation of Tolkien. I don't need to get off anything. Rowling recycled like all author's recycle. But to get to the original from the gp's sig - the idea of Rowling ripping off Naruto is pretty humorous.
       
      If you want egregious theft go slog through Eragon - Rowling used themes and imagery common back to the early days of civilization. Of course there will be similarities to other works created before and after what she wrote.

      --
      It's hard to believe that's how Micronians are made. Why don't we see it right now by having you both kiss one another?
    5. Re:this has to be fake by failedlogic · · Score: 1

      I see it as a way for MS to avoid more trouble with the EU and lower the price tag of existing lawsuits. I don't think its a sudden 'embrace' of openness or transparency.

    6. Re:this has to be fake by m50d · · Score: 1

      Given that GNU managed to release a compatible version of unix without violating copyright, I think MS can probably manage it.

      --
      I am trolling
  5. Obligatory Jokes by SendBot · · Score: 4, Funny

    Microsoft: Bringing new meaning to "Gnu's not unix"

    Didya hear that there's this operating system that gives you the best of windows and linux? It's called linux!

    1. Re:Obligatory Jokes by Seraphim_72 · · Score: 1

      Yea gads! Gives new meaning to the old joke UNGa Bunga! Please God, not this way either, not with a thrown chair!

      --
      Slashdot, where armchair scientists get shouted down and armchair theologians get modded up.
  6. book about UNG by stoolpigeon · · Score: 5, Funny

    There is already a book out on UNG. How do publishers knock this stuff out so quickly?

    --
    It's hard to believe that's how Micronians are made. Why don't we see it right now by having you both kiss one another?
    1. Re:book about UNG by Silver+Sloth · · Score: 1

      Err... that site is a parody. It doesn't take that long to knock out a parody.

      BTW, I love the author's name E.X.Tend who presumably co-writes with E.M.Brace

      --
      init 11 - for when you need that edge.
    2. Re:book about UNG by tenco · · Score: 1
    3. Re:book about UNG by Otter · · Score: 1

      This whole thing seems like an April Fools joke that was accidentally distributed a month early.

    4. Re:book about UNG by stoolpigeon · · Score: 1

      Err... I made it. So yeah - I get the parody part. I originally did E.M. Brace as the author - but then I wanted emrbrace & extend fully spelled out so I made "Embrace &" the publisher. A little odd, but I'll call it comedic license.

      --
      It's hard to believe that's how Micronians are made. Why don't we see it right now by having you both kiss one another?
    5. Re:book about UNG by Anonymous Coward · · Score: 0

      Adlibs.

      ds

    6. Re:book about UNG by Anonymous Coward · · Score: 0

      Microsoft Unix Not Good

  7. UNG's not GNU? by Anonymous Coward · · Score: 0

    That's taking recursive acronyms to a whole new level.

    1. Re:UNG's not GNU? by FlameWise · · Score: 1

      Well yeah, you know: GNU could now officially stand for "GNU's not UNG", too.

    2. Re:UNG's not GNU? by steelfood · · Score: 1

      That's there's someone working in Microsoft who's geeky and dorky enough to come up with this recursive acronym makes me wonder if there's hope yet for the company.

      --
      "If a nation expects to be ignorant and free in a state of civilization, it expects what never was and never will be."
  8. Fake by ledow · · Score: 0, Flamebait

    Fake. 'Nuff said.

    1. Re:Fake by J3rryken · · Score: 1

      it looks like a fish, it smells like a fish, what is it ? :)

    2. Re:Fake by Anonymous Coward · · Score: 1, Funny

      Your mother.

      Wait, is this supposed to be a joke?

    3. Re:Fake by iperkins · · Score: 1

      It's a constipated duck that swallowed a fish

  9. Race to the bottom by dsginter · · Score: 1

    The water will seek its own level. I've written a high-level overview of what could happen if tech workers leveraged Free Software to "Embrace and Extend" the tech industry down to the employment level. Unless Microsoft (and many, many others) go the Free Software route, then this plan does not include them.

    --
    More
    1. Re:Race to the bottom by Anonymous Coward · · Score: 0

      Nobody is going to read your stupid article. Get a job.

    2. Re:Race to the bottom by FudRucker · · Score: 3, Insightful

      since UNG is for non-commercial use only that mean business wont be able to use it... just jane & joe sixpack on his home PC...

      --
      Politics is Treachery, Religion is Brainwashing
    3. Re:Race to the bottom by fizzbin · · Score: 2, Insightful

      Then its not Free Software.

      Both Free Software and Open Source advocates agree that if you can't use the software for whatever you want, including a for-profit business, then its not Free/Open Source.

      So Microsoft is up to its old tricks, trying to kill Free software since they can't Embrace and Extend (and Extinguish) it. The only difference is that now it's trying to make a faux-Free clone to kill it with.

      --
      Fizz
    4. Re:Race to the bottom by Anonymous Coward · · Score: 0

      Your article is completely senseless. Do you work in tech support or something?

  10. Windows Services for Unix by TheRealMindChild · · Score: 3, Interesting

    And what is the difference between this and Windows Services for Unix? Sounds like rebranding to me.

    --

    "When life gives you lemons, don't make lemonade. Make life take the lemons back!" -- Cave Johnson
    1. Re:Windows Services for Unix by zappepcs · · Score: 1

      Personally, I think this is a big step. Linux fanbois missed it. Microsoft is imploding. 2 years ago chairs would fly at even the suggestion that Windows should cater to Linux users in any form. Now MS seems to have a 'we do GNU too' attitude.

      From bully on the playground to 'why can't we all play nice' ??

      Don't believe it for a second, but take heart, GNU/Linux has made an impression in Redmond big enough to affect the marketing machine.

    2. Re:Windows Services for Unix by Alioth · · Score: 4, Insightful

      I hope SFU has had some improvement since I last tried it a couple of years ago. Running as an NT subsystem, and owned by MS, it should just be miles better than Cygwin. However, it feels like ISC Unix in 1991, and has poor source compatibility with other Unixes and Unixlikes such as Solaris, *BSD and Linux. Cygwin was blowing it away two years ago and probably still is.

    3. Re:Windows Services for Unix by lysse · · Score: 1

      SFU

      *blink*
    4. Re:Windows Services for Unix by The+Moof · · Score: 1

      The last Services for Unix release was in 2004, and it's out of production. EOL is still a ways off (2014 for extended support).

    5. Re:Windows Services for Unix by Anonymous Coward · · Score: 0

      SFU

      *blink*


      i know .. i always instinctively put a "T" in there (ie: Microsoft STFU ..)

    6. Re:Windows Services for Unix by cbhacking · · Score: 1

      I've only used SFU (properly speaking) a little, on an XP box I had to use for work, but was pleasantly surprised. However, it has in fact been updated - it just had the name changed. SUA, or Subsystem for Unix Applications, is present in Server 2003 (v5.2, like the s2003 kernel version) and in Vista (6.0). I've used 6.0 extensively, both with third-party tools (pre-compiled or from source) and for my own development projects. Many 3.5 (last official SFU version) programs run fine on 6.0, but many have also been updated or modified to use new features or fix old issues. It's not without issues, but it does the job and does it pretty well.

      On source compatibility, it's actually quite good. Sure, there's a lot of individual things in Linux/BSD/Solaris that aren't supported, but almost anything that will compile across them will compile on Interix as well. The biggest issues are often with the configuration scripts; newer versions of config.guess and config.sub handle Interix but a couple years ago they tended not to.

      --
      There's no place I could be, since I've found Serenity...
  11. Will believe it when I see it by pembo13 · · Score: 2, Insightful

    And I think this is fair enough to be applied to any company, not just Microsoft.

    --
    "Thanks for all the money you paid to us. We've used it to buy off ISO among other things" -Microsoft
  12. This one's a whopper. by morgan_greywolf · · Score: 1

    Next thing you're gonna say is that a black man and a white woman are both viable contenders for the U.S. presidency in 2008....oh, wait...

  13. Makes some sense by sayfawa · · Score: 1

    What's that line?

    Something like "Those who forget Unix are doomed to recode it". So the last big OS vendor is finally coming around. Good.

    As for involving GNU as part of their plans, of course it's a trap :)

    --
    Free the Quark 3 from asymptotic confinement! Bring your charm! Don't get down! All colours and flavours welcome!
    1. Re:Makes some sense by Constantine+XVI · · Score: 2, Informative

      IIRC, it's "Those who fail to understand Unix are doomed to reinvent it, poorly" Can't recall the source ATM

      --
      "I think an etch-a-sketch with an ethernet port would beat IE7 in web standards compliance."
    2. Re:Makes some sense by genik76 · · Score: 5, Funny

      >Something like "Those who forget Unix are doomed to recode it".

      And those who forget important quotes are condemned to reinvent them, poorly.

    3. Re:Makes some sense by Tibor+the+Hun · · Score: 0, Redundant

      Wow. That was fantastic sir. (or Ma'm as it may be the case.)

      --
      If you don't know what AltaVista is (was), get off my lawn.
    4. Re:Makes some sense by DarkEmpath · · Score: 1

      Something like "Those who forget Unix are doomed to recode it".
      Umm... Isn't that what Linus Torvalds did?
  14. This could be a trap for OSS by Chrisq · · Score: 1

    In future they will be able to say "they must have copied our code" SCO wise.

    1. Re:This could be a trap for OSS by garett_spencley · · Score: 1

      You're right. We need to watch out. Novell's demise should have taught the FOSS world a very valuable lesson.

      Wait, what ?

    2. Re:This could be a trap for OSS by Chrisq · · Score: 1

      But look at the FUD it gained against OSS. Microsoft won't bring a case themselves, they'll transfer rights to some small company and "license" it back at a rate large enough to fund legal shenanigans.

  15. my opinion by theMerovingian · · Score: 1


    they are aiming to restore a Unix-like environment to its former propriety glory

    The most glorious thing that I can remember about proprietary unix was the awesome pizza box cases. I seriously have no idea why the PC "tower" caught on instead of that.

    --
    "If you think you have things under control, you're not going fast enough." --Mario Andretti
    1. Re:my opinion by plague3106 · · Score: 1

      Because no one wants to waste desk space with that? My monitor takes up less space.

    2. Re:my opinion by garett_spencley · · Score: 1

      I had one of those sitting on my desk for a while, it was an UltraSparc actually, so a little newer. Solaris (7 I think) + UFS + IDE = agonizing pain.

      Simply because of the slow read/writes it took about 30 minutes to do a compile that would take 3 - 5 minutes on an equivalently clocked x86 box.

      I loved SUN's servers but their low-end workstations put new meaning to the word 'low end'.

    3. Re:my opinion by tuffy · · Score: 1

      The Sparcstation typically went directly under the monitor. That added little to the amount of desk space used while increasing the monitor height slightly.

      These days, the prevalence of LCDs makes the design less practical.

      --

      Ita erat quando hic adveni.

    4. Re:my opinion by Firehed · · Score: 1

      Have you never seen a rackmount server? Something in a pretty similar enclosure continues to exist - though as another responder points out, it's an unnecessarily large footprint for desktop use (probably the single largest reason I don't have a nice rackmount for my home server).

      --
      How are sites slashdotted when nobody reads TFAs?
    5. Re:my opinion by plague3106 · · Score: 1

      Yes, I should have added that I only have LCDs now.

    6. Re:my opinion by kimvette · · Score: 1

      I seriously have no idea why the PC "tower" caught on instead of that.


      How expandable were those sparcstations? Oh right, they weren't - unless, like early Macintoshes, you want external cases connected to the SCSI port. Second internal hard drive? Right. Internal optical drive upgrades? In your dreams. Third-party sound cards? Additional graphic cards? Good luck.

      Those style cases are available for PCs, but they aren't practical if you want to expand them later on -- unless you want to go with the slow (compared to PCI/PCIe/PCI-X) firewire or usb peripheral route.
      --
      The Christian Right is Neither (Christian nor right). See: Matthew 23, Matthew 25, Ezekiel 16:48-50
    7. Re:my opinion by Culture20 · · Score: 1

      This is made getting into the box for cleaning or repair a pain. I always turned them sideways next to the monitor if I could. I did kind of like the Sparc IPX mini boxes though; very stackable.

    8. Re:my opinion by TheLink · · Score: 1

      Probably cheaper to do a tower with the same amount of power, cooling, expansion space.

      I think it was easier to stick new graphics/sound/network cards into a PC tower than it was into a flat pizza box case.

      --
    9. Re:my opinion by Anonymous Coward · · Score: 0

      How expandable were those sparcstations?

      You're thinking of something other than the pizza box stations. Some had 2-3 SBUS slots, supported multiple graphics cards, dual internal hard drives, and had internal optical drives (before that they had floppies). No, I wasn't dreaming and a quick search confirms that other people used the same things.

  16. Open protocols and MSFT not compatible by Anonymous Coward · · Score: 0

    I am with Bjarne on this one.
    Bjarne Stroustrup, creator of the C++ programming language, claims that C++ is experiencing a revival and
    that there is a backlash against newer programming languages such as Java and C#. "C++ is bigger than ever.
    There are more than three million C++ programmers. Everywhere I look there has been an uprising
    - more and more projects are using C++. A lot of teaching was going to Java, but more are teaching C++ again.
    There has been a backlash.", said Stroustrup.

    1. Re:Open protocols and MSFT not compatible by ThirdPrize · · Score: 2, Insightful

      Heaven help us if thats true.

      --
      I have excellent Karma and I am not afraid to Troll it.
  17. Full circle by sm62704 · · Score: 1

    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

    Sounds like DOS 3.1 to me! Will it run KDE or Gnome?

    --
    mcgrew's razor: Never attribute to stupidity that which can be explained by greedy self-interest
  18. doubting the veracity by czmax · · Score: 1

    This would move developers away from Microsoft's proprietary APIs and functionalities, aka their lock-in. The end result would be developers writing 'GNU' type code and expecting it to run on either Vista or any 'Unix' environment. Suddenly Vista has to compete on its own merits and can't depend on "killer applications" to pull people in.

    Although I think this a good thing, and Apple thinks this a good thing, and Linux thinks this is a good thing I'll be a bit surprised if somebody at Microsoft has convinced enough leads that they now think it is a good thing.

  19. itsatrap by BoberFett · · Score: 4, Funny

    If ever there were an appropriate story for the itsatrap tag, this is it.

  20. If money can be made from free software... by TwoQuestions · · Score: 1

    then why wouldn't Microsoft give it a whirl? If it makes money, great. If it doesn't, then sue the pants off of anyone who extended or modified their stuff. It doesn't seem too irrational to try to make money the free software way, and worst comes to worst, they can make money spreading FUD and litigation!

  21. Too good to be true by Reality+Master+101 · · Score: 1

    I've begged for YEARS to the non-existent God for Microsoft to get a clue and make their operating system Unix-like (if not completely replace their kernel with a Unix kernel). It would literally be the perfect operating system: Unix compatibility and mainstream Application compatibility. It would ROCK SO HARD.

    Unfortunately, I just can't see it happening. It would be far too smart for Microsoft. --weeps--

    --
    Sometimes it's best to just let stupid people be stupid.
    1. Re:Too good to be true by red+star+hardkore · · Score: 1

      There's already enough crying over Vista's incompatibiliy problems. If they completely replaced the Kernel, nothing would work. Sure MS could include an emulator/virtual machine of Vista, but then what would be the incentive for app developers to port their code to the new kernel when people can still use it on the old?

    2. Re:Too good to be true by plague3106 · · Score: 1

      My god, the Unix kernel isn't the be all end all of OSes. What is with this attitude that Unix was the best? Unix didn't get computers infront of just about everyone, it just about rotted and died in universities and research companies.

    3. Re:Too good to be true by pyite · · Score: 0

      Unix compatibility and mainstream Application compatibility. It would ROCK SO HARD.

      If only this existed already... Ah, one can dream.

      --

      "Nature doesn't care how smart you are. You can still be wrong." - Richard Feynman

    4. Re:Too good to be true by betterunixthanunix · · Score: 1

      How many years and which operating system? Microsoft did sell a Unix at one time (Xenix) and they did release "Windows services for Unix," which is the Unix tools.

      --
      Palm trees and 8
    5. Re:Too good to be true by jedidiah · · Score: 1

      ...and companies.

      Unix has been chugging along doing "real work" since
      before the first version of MS-DOS was _bought_ from
      it's original author.

      The fact that you are too much of a rube to know it
      was around is not relevant. It still allowed you to
      make completely baseless claims in public forums.

      This is a discussion about CORPORATE COMPUTING not
      some stupid desktop toys.

      --
      A Pirate and a Puritan look the same on a balance sheet.
    6. Re:Too good to be true by bombshelter13 · · Score: 1

      'If they completely replaced the Kernel, nothing would work.'

      I think you just guessed the killer feature of Windows 7.

    7. Re:Too good to be true by betterunixthanunix · · Score: 1
      Unix (especially BSD) made the Internet. You say that Unix never brought computers into the home? I say that without a bunch of Unix servers hosting websites on the Internet, and a standardized and mostly compatible protocol and API in use on those systems, there would have been virtually no market for home computer systems. Windows was the OS that became dominant in the home, because most PC vendors were shipping Windows. Nobody would haven't spent the money on a computer, however, if there was no Internet for them to connect to. Windows NT Server had a much, much smaller presence on the Internet in the mid 90s than Unix and Unix-like systems did.

      Sure, there would have been global networks without Unix. There was FidoNET. There were various mainframe systems that could be used to create global networks. But it would be a complete mess. Microsoft might have created its own network standard (and therefore its own network), Apple might have created a different one, and so on, and those networks would only be loosely coupled by a bunch of gateways. It would be an order of magnitude worse than what we see in the cell phone market.

      So I would say that Unix did bring computers into the home, but nobody noticed it.

      --
      Palm trees and 8
    8. Re:Too good to be true by Reality+Master+101 · · Score: 1

      How many years and which operating system? Microsoft did sell a Unix at one time (Xenix) and they did release "Windows services for Unix," which is the Unix tools.

      Xenix was a full attempt at Unix, but the hardware wasn't ready. It was much too slow and too limited. Then Microsoft made the huge mistake of putting Dave Cutler, a VMS guy, in charge of NT. That gave us the steaming pile of unmanageable crap called the NT kernel, and Unix was abandoned. The irony is that Bill Gates was Unix guy! He's the one who tried Xenix.

      If Microsoft had put a Unix guy in charge of NT, the world would be very, very different, and Windows probably wouldn't suck nearly as much.

      Windows services for Unix was a crappy attempt at being able to check off the "POSIX Compatibility" checkbox on government requirements forms. In practice, it's totally worthless.

      --
      Sometimes it's best to just let stupid people be stupid.
    9. Re:Too good to be true by plague3106 · · Score: 1

      Unix has been chugging along doing "real work" since
      before the first version of MS-DOS was _bought_ from
      it's original author.


      Sorry, did I say otherwise? No I didn't. It's also irrelevent to the point I was making.

      The fact that you are too much of a rube to know it
      was around is not relevant. It still allowed you to
      make completely baseless claims in public forums.


      Linux isn't Unix, it's a "Unix-like" OS. And other kernels can do just as well serving "public forums." Again, what's your point here?

      This is a discussion about CORPORATE COMPUTING not some stupid desktop toys.

      No, it's a discussion about why the OP thinks that the Unix kernel is perfect and seems to think that no others should exist. FWIW, COPPORATE COMPUTING didn't start becoming popular until DOS came along and MS marketed it.

      MS also had a Unix kernel that it tried to sell too, but nobody wanted it.

    10. Re:Too good to be true by Reality+Master+101 · · Score: 2, Insightful

      My god, the Unix kernel isn't the be all end all of OSes. What is with this attitude that Unix was the best?

      To paraphrase a quote, "Unix is the worst operating system, except for all the others."

      There's a reason that Unix dominates so many different areas, from the smallest embedded systems to the largest supercomputers: it's very, very flexible, and gets out of your way. It doesn't straight-arm you into "my way or the highway" like most operating systems.

      --
      Sometimes it's best to just let stupid people be stupid.
    11. Re:Too good to be true by Reality+Master+101 · · Score: 1

      Unix compatibility and mainstream Application compatibility. It would ROCK SO HARD. [...] If only this existed already... Ah, one can dream.

      Actually, I half agree with you, but 1) it only has a small (though, important) subset of mainstream applications, and 2) it doesn't (officially) run on mainstream, commodity hardware, which I should've added to my dream operating system list.

      --
      Sometimes it's best to just let stupid people be stupid.
    12. Re:Too good to be true by Xtravar · · Score: 1

      I'd be happy with just being able to install "Documents and Settings", "Program Files", and *all temp/cache folders* on different partitions than "Windows".

      I can do it, but it's damn near impossible. Lots of dicking around.

      --
      Buckle your ROFL belt, we're in for some LOLs.
    13. Re:Too good to be true by plague3106 · · Score: 1

      First, no one would care about the internet if DOS didn't bring computers into companies and more importantly, homes. No one was buying Unix on PCs when DOS was around.

      Nobody would haven't spent the money on a computer, however, if there was no Internet for them to connect to.

      What nonsense. People starting buying computers in the last 80s. The internet played an important part by creating a "must have" which boosted sales later, but to say no one was spending money on home computers is just stupidity. Quite a few people had 286s in their houses. And that was after companies like Commadore and Amiga were selling home computers as well.

      At any rate, you completely missed my point, which was my questioning of this assumption that we shouldn't try building other kernels, that all kernels must function like the Unix kernel. Go read the post to which I replied and then see that your comments were irrelevent.

    14. Re:Too good to be true by plague3106 · · Score: 1

      So, when MS' OS dominate a market, it's because they have a monopoly or "got lucky" at the right time. When Unix does, its because its superior and we shouldn't bother developing other kernels?

    15. Re:Too good to be true by Reality+Master+101 · · Score: 1

      So, when MS' OS dominate a market, it's because they have a monopoly or "got lucky" at the right time. When Unix does, its because its superior and we shouldn't bother developing other kernels?

      Microsoft dominated the desktop market because 1) they had the best upward compatibility from DOS, 2) went out and wooed developers to develop for Windows, and 3) went out and wooed hardware developers. With the compatibility path in their pocket, they then leveraged that to "encourage" hardware manufacturers to only sell Windows.

      Unix dominated the server market primarily because it was the first operating system written in a high-level language (C). That allowed it to be ported to a wide variety of hardware, giving it broad-based support. Over the years, it got continually upgraded with new features and standards.

      No one it out there forcing people to adopt Unix -- when it comes to embedded systems or supercomputers, the operating system is of second concern. Yet, Unix is consistently chosen because of its flexibility.

      --
      Sometimes it's best to just let stupid people be stupid.
    16. Re:Too good to be true by Reality+Master+101 · · Score: 1

      which was my questioning of this assumption that we shouldn't try building other kernels, that all kernels must function like the Unix kernel.

      Sheesh, if that's your point, then you're arguing from false premises. I never said we "shouldn't try" building other kernels, I said that Unix-style operating systems are the best reasonable option we have right now, and they are certainly better than the rat's nest NT represents.

      --
      Sometimes it's best to just let stupid people be stupid.
    17. Re:Too good to be true by Anonymous Coward · · Score: 0

      FWIW, COPPORATE COMPUTING didn't start becoming popular until DOS came along and MS marketed it.

      I was with you up to there. Corporate computing was huge when DOS came out (back office/IBM) and Microsoft still only has a tiny corner of that today. Word processors and spread sheets are toys.

    18. Re:Too good to be true by plague3106 · · Score: 1

      Well, if people are doomed to "recode" unix because they don't know it, that certainly implies that every OS "evolves" into Unix. From wha I understand, the NT kernel is fairly small and modular as well. Why do you call it a rats nest?

    19. Re:Too good to be true by plague3106 · · Score: 1

      Microsoft dominated the desktop market because 1) they had the best upward compatibility from DOS, 2) went out and wooed developers to develop for Windows, and 3) went out and wooed hardware developers. With the compatibility path in their pocket, they then leveraged that to "encourage" hardware manufacturers to only sell Windows.

      MS also sold a unix OS for PCs too, but people choose DOS over that OS. Personally, I'd rather sell two products instead of betting the cow on one, but I suspect that unix for PCs wasn't viable at that time.

      Unix dominated the server market primarily because it was the first operating system written in a high-level language (C). That allowed it to be ported to a wide variety of hardware, giving it broad-based support. Over the years, it got continually upgraded with new features and standards.

      Being developed in C may be why one of the compaints of MS' PC unix being slow. At any rate, that was then, and today NT is also written in C and could probably be run on a wide varity of hardware as well. Windows Embedded exists for this, and from I've read its slowly catching on.

      No one it out there forcing people to adopt Unix -- when it comes to embedded systems or supercomputers, the operating system is of second concern. Yet, Unix is consistently chosen because of its flexibility.

      No one is forcing people to adopt Windows, and certainly not outside the desktop market. Yet it does seem to be gaining traction, just as IIS is gaining traction as a web server.

    20. Re:Too good to be true by VGPowerlord · · Score: 1

      No one it out there forcing people to adopt Unix -- when it comes to embedded systems or supercomputers, the operating system is of second concern. Yet, Unix is consistently chosen because of its flexibility.

      Really? I was under the impression that they were choosing things like AIX, Solaris, and Linux.

      In fact, I'm pretty sure that Xenix... er... SCO OpenServer's kernel isn't used all that much any more.
      --
      GLaDOS for President 2016! "Well here we are again. It's always such a pleasure." -- GLaDOS, 2011
    21. Re:Too good to be true by colinrichardday · · Score: 1

      First, no one would care about the internet if DOS didn't bring computers into companies and more importantly, homes. No one was buying Unix on PCs when DOS was around.

      True, Unix was too large (or PC's were too small). But it wasn't DOS that brought PC's into companies, it was IBM's imprimatur.

    22. Re:Too good to be true by DeVilla · · Score: 1

      I've always felt that UNIX's slogan ought to be "UNIX, it's more flexible than you are..." And based on that, the open source variants could effectively add "... and we're more flexible than that."

  22. I heard about this several years ago... by emil10001 · · Score: 1

    I had heard about this several years ago (2005?). My understanding was that Blackcomb was supposed to be built on a different paradigm that previous MS Windows, with a more Unix-like architecture. I heard that they were developing their own shell, and separating the GUI as a separate piece. As I understood it, they were going to try to make windows more modular, and give admins some better shell tools. ... not that I'll ever use it.

    I don't have a link handy, but I remember reading this on the Microsoft website, probably in their development section or something.

    1. Re:I heard about this several years ago... by emil10001 · · Score: 1

      Please ignore the above post, I think I misunderstood what was being discussed.

      On another note, it probably wouldn't be too technically difficult to accomplish what they're talking about doing. It'd be like having an MS branded cygwin, but some other default shell besides bash.

      *If* that's what their intention is.

  23. Embrace, Extend and Extinguish by davecb · · Score: 4, Insightful
    his is exactly what MS tried to do with Java, and did do with C#.

    First, build a language or system that runs existing programs.

    Then change the compilers so they use MS-only, intel-only features by default

    Then add attractive features at the source level.

    Pretty soon, you can port *to* the new platform, but can't port away from it.

    --dave
    [PS: If you're already in that situation and want to port, send me private email]

    --
    davecb@spamcop.net
    1. Re:Embrace, Extend and Extinguish by Anonymous Coward · · Score: 0

      Pretty soon, you can port *to* the new platform, but can't port away from it.

      And after that, file a patent and extort some more.

  24. MSFT used to be a UNIX vendor by peter303 · · Score: 3, Informative

    In the late 1970s and early 1980s MicroSoft sold a version of PC-UNIX called Xenix (they didnt write it). Until the mid-1990s PCs were too-weak to effectively run UNIX, so it was not a popular product. In the early 1980s MicroSoft decided to concentrate on MS-DOS and other products, so it sold Xenix to a company which eventually became SCO.

    1. Re:MSFT used to be a UNIX vendor by Anonymous Coward · · Score: 5, Informative

      Um, you're a little confused on the facts there.

      Around the mid eighties, Xenix was the most widely installed unix, due primarily to the cheapness of the hardware on which it ran. To say it wasn't popular just isn't true.

      Also, MS never sold Xenix directly to customers, quoth Wikipedia:

      "Microsoft did not sell Xenix directly to end users; instead, they licensed it to software OEMs such as Intel, Tandy, Altos and SCO, who then ported it to their own proprietary computer architectures. Microsoft Xenix originally ran on the PDP-11; the first port was for the Zilog Z8001 16-bit processor. Altos shipped a version for their Intel 8086 based computers early in 1982, Tandy Corporation shipped TRS-XENIX for their 68000-based systems in January 1983, and SCO released their port to the IBM PC in September 1983."

    2. Re:MSFT used to be a UNIX vendor by yorugua · · Score: 3, Informative

      In the late 1970s and early 1980s MicroSoft sold a version of PC-UNIX called Xenix (they didnt write it).

      Great old times..!! I remember I had a 80266 machine back then, 10 MHz (way faster than the original IBM PC-AT, but you could always press CTRL-ALT-minus to set it back to normal speed in case of incompatibilities).

      Until the mid-1990s PCs were too-weak to effectively run UNIX


      Well, on my 80266 10MHz/640kb RAM I used to do the college work (Turbo Pascal, Turbo C, documentation) on PC-DOS. When I "discovered" Xenix-286, the same machine could run 4 virtual terminals on the console, I was able to edit, compile, run/test on three different terminals. If I made a mistake on C, I'd get a coredump, but the machine kept running. Also, I was able to enable my modem, so a classmate could also work on what I was doing.

      Great times, 80266 machine, 640 KB ram, 40 MB Hard drive.

      Then I met a lot of people that were using SCO Xenix/UNIX on 80386 class machines, doing all kind of things from running a BBS with 20+modems, or running the billing system of local companies from multiple RS-232 terminals in the late 80's, early 90's.

    3. Re:MSFT used to be a UNIX vendor by yorugua · · Score: 1

      80266 = 80286, sorry about

    4. Re:MSFT used to be a UNIX vendor by Anonymous Coward · · Score: 0

      > Xenix (they didnt write it).

      Xenix was a licenced implementation of AT&T Unix edition 7. The main contractors who developed it for MS were from a small consultancy called SCO and they later bought the product. Part of the deal, alledgedly, was that MS promised to not release another Unix that would compete with them.

    5. Re:MSFT used to be a UNIX vendor by samrolken · · Score: 1

      Aah yes, the good ol' Intel 80266.

      Wait. What?

      --
      samrolken
  25. Is this the conference call by esocid · · Score: 1

    they are referring to? I don't see anything in there about GNU or UGN or UNIX. All it is, is a tele-press-conference about interoperability.

    --
    Absolute power corrupts absolutely. indymedia
  26. Microsoft's Linux replacement by angryfirelord · · Score: 1

    The aim of UNG is to write complete GNU-like tools and frameworks that will be completely compatible with existing GNU software and standards. These tools will run natively on Vista. This means that software written for the GNU environment will be able to compile and run on Vista with little or no modifications. Major software currently running on GNU/Linux will be able to run natively on Vista. Sounds like Microsoft still wants to take out Linux, but instead of trying to force their own tools upon its users, they'll allow GNU tools and other programs to be substituted instead.

    Of course, this sounds too good to be true. What will be used to compile said programs? When they say "little" modification, what is being implied? Will the GPL linking be forbidden in some way when you compile it on Vista?
  27. MS already has unattended scripted installs by breagerey · · Score: 3, Informative

    and has for a very long time.

    1. Re:MS already has unattended scripted installs by obender · · Score: 2, Funny

      Not any more, now you have to double click on those email attachments.

    2. Re:MS already has unattended scripted installs by dotancohen · · Score: 1

      You are referring to all those scripts that timecop installs, right?

      --
      It is dangerous to be right when the government is wrong.
  28. Okay, fess up by Panaqqa · · Score: 1

    Who sold Ballmer the good BC buds?

  29. tags: fake, vaporware by Anonymous Coward · · Score: 0

    I'm still tagging it fake and vaporware. This has been promised before and dropped out. Add it to the list with WinFS and other crap. Besides, even if it does ship, it's still on Windows. You can't do anything serious with that, at least not if you're planning on connecting it to the net.

    With the easy to maintain first rate tools out there, (Solaris, NetBSD, OpenBSD, OS X, FreeBSD, Linux), why go with a hard to use, hard to maintain, insecure second rater? The productivity hit you take by bringing MS into the subnet will stress and drive away your skilled staff. Then the real problems kick in when all you have left are the trained monkeys you hire by the dozen from want-ads. Then just when you think the services can perform any worse or any less reliably, then the swarm of trained monkeys start replacing good systems with MS cruft, eventually pushing the whole house into crisis mode, stressing and driving away your skilled non-technical staff.

    No thanks. Stick to stuff you are good at Steve, like that monkey dance of yours.

  30. Appeal? by Anonymous Coward · · Score: 0

    " Microsoft Trying to Appeal to the Unix Crowd?"

    I thought Microsoft was trying to 'IMPALE' the unix crowd....

  31. non-commercial uses by FooAtWFU · · Score: 3, Insightful

    opened up their communication protocols for non-commercial usage Get back to me when it's for general-purpose uses.
    --
    The World Wide Web is dying. Soon, we shall have only the Internet.
    1. Re:non-commercial uses by MrNemesis · · Score: 2, Informative

      Really, this comment should be +5 insightful by now. By having a caveat that basically says "if you're a corporation making money off Linux (hello Redhat!) and your distro happens to contain a nifty utility that some dude made based on stuff in our patents, we'll sue the hell out of you unless you pay us this protect... er, technology licensing fee", this is just yet another version of embrace, extend, extinguish.

      When commercial distros (and community distros used commercially, like Debian) can't implement the tools needed to interoperate with Microsoft on a solid legal basis, distros will fail and Linux will once again be relgated to a) businesses outside of software patent control and b) yo' mommas basement. Like the Samba team say, stay away if you value using FOSS in the commercial world without being held to account by MS. It's a poisoned chalice.

      Disclaimer: I'm in the EU and, since most of the patents don't apply over here (yet) we're hopefully in the clear for now. Until MS "lobbies" WIPO to "encourage" the EU to adopt a US software patent policy, or something similar. Yes, I wear my tinfoil hat shiny side out.

      --
      Moderation Total: -1 Troll, +3 Goat
  32. Unrelated re your sig: by ZeroFactorial · · Score: 0, Offtopic

    I have blind faith in gravity - I'm pretty sure that's safe.
    Unless of course you're one of those people who stays tethered down "just in case"...
    Also I have blind faith in "The Boss". He's never led me wrong... er... wait a minute...

    1. Re:Unrelated re your sig: by doti · · Score: 1

      No, your faith in gravity is far for blind. It's actually the opposite.
      You know gravity is here, you feel it, you see it's effect every day.

      "Blind faith" does not mean you can't optically see the subject.

      --
      factor 966971: 966971
    2. Re:Unrelated re your sig: by JesseMcDonald · · Score: 1

      By definition, it's not blind faith if there's evidence and a consistent model to support your predictions. Lots of observations indicating that things tend to stay on the ground, plus a model consistent with these observations that predicts things will continue to tend towards staying on the ground, leads to rational faith that one isn't going to just float away without a tether.

      Blind faith is when your model goes beyond the minimum necessary to explain the observations, such that you are selecting an unnecessarily complex (i.e. over-constrained) model out of a range of possibilities.

      --
      "The state is that great fiction by which everyone tries to live at the expense of everyone else." - Bastiat
    3. Re:Unrelated re your sig: by Anonymous Coward · · Score: 0

      I have blind faith in gravity Not me. I believe in gravity because repeated experiments have validated a model of the effect that I find useful in my daily life.
    4. Re:Unrelated re your sig: by ZeroFactorial · · Score: 1

      Actually according to the definition of faith in the Bible that's exactly what it is...

      "Now faith is the substance of things hoped for, the evidence of things not seen."
      -Heb. 11: 1

      By that definition (which I'd say is a reliable source for the religious definition of faith), the EFFECTS of gravity are the evidence of an unseen force.

      You can't see gravity; you can only see its effects.

      Q.E.D.

    5. Re:Unrelated re your sig: by node+3 · · Score: 1

      Actually according to the definition of faith in the Bible that's exactly what it is...

      "Now faith is the substance of things hoped for, the evidence of things not seen."
      -Heb. 11: 1

      By that definition (which I'd say is a reliable source for the religious definition of faith), the EFFECTS of gravity are the evidence of an unseen force.

      You can't see gravity; you can only see its effects.

      Q.E.D. By that definition (even acceding to the silliness of using the Bible instead of the Dictionary to define a term, not to mention you switching from "blind faith" to merely "faith"), "faith is the substance of things hoped for". Faith (trust) in gravity has nothing to do with whether or not it's "hoped for", and thus is different from "blind faith" (or even just "faith", as defined by that specific Bible quote).

      Q.E.D.
    6. Re:Unrelated re your sig: by ZeroFactorial · · Score: 1

      1) Faith is a religious term, and merits a religious definition - not one provided by a secular source, such as the dictionary.

      2) "Blind Faith" is a subset of "Faith".

      3) Faith is "Substance of things hoped for" or "Evidence of things not seen"

      4) Thus we can safely say Faith is "Evidence of things not seen"

      5) Since "Blind Faith" is a subset of "Faith", then "Blind Faith" also has the property of being "Evidence of things not seen"

      Q.E.D.

      You focused on "substance of things hoped for" and ignored the more pertinent "evidence of things not seen".

    7. Re:Unrelated re your sig: by node+3 · · Score: 0, Offtopic

      1) Faith is a religious term, and merits a religious definition - not one provided by a secular source, such as the dictionary. No, it's a word. Words are best defined in the Dictionary.

      2) "Blind Faith" is a subset of "Faith". Sure.

      3) Faith is "Substance of things hoped for" or "Evidence of things not seen" I didn't see the word "or" in that quote. I saw a comma, which is usually interpreted as an "and" or "also".

      4) Thus we can safely say Faith is "Evidence of things not seen" No, we cannot. I can close my eyes and be just as sure there's a planet beneath my feet as I can with my eyes open and looking right at it.

      5) Since "Blind Faith" is a subset of "Faith", then "Blind Faith" also has the property of being "Evidence of things not seen" Not necessarily, but even if we take it to mean that, being a subset means it has additional characteristics, the most important being that "blind faith" means having no direct, rational reason to believe in something. There is no blind faith involved in accepting the existence of gravity.

      Q.E.D. Not even close.

      You focused on "substance of things hoped for" and ignored the more pertinent "evidence of things not seen". A. Why is it more important? B. I can see the effects of gravity. In fact, one can actually *see* gravity itself. Gravitational Lensing is seeing gravity itself, just as much as seeing light reflected from a statue is seeing the statue.
    8. Re:Unrelated re your sig: by morgan_greywolf · · Score: 1

      Heh. Hilarious exchange between the two of you. I didn't respond to his troll 'cause I assumed he wasn't worth my time. I was right.

      Yeah, basically his whole argument is pointless and lacks logic. Of course gravity can be seen -- indeed, as you point out, it has been seen. Newton didn't have 'faith' in gravity. He saw that things that went up also came down. Newton proved gravity is real. Einstein didn't have 'faith' in gravity -- he proved it fit in with his theory of general relativity. Gravity is essentially a scientifically proven fact that requires no faith on the part of anyone who's had a high school physics course.

      Blind faith requires that you simply accept what someone else has told you as you truth -- either through writing or through speech. The fact fundamentalist Christian whackos can't get around is that they believe what they believe because someone else told them it was true.

    9. Re:Unrelated re your sig: by samjam · · Score: 1

      Now may be a good time to remind everyone that not all Christians are blind christian wackos.

      Group-think clubs exist in all sorts of guises.

      Faith, though, helps all kinds of people see, live by and act on that which they could not know, and is to many people very useful in that respect; and also naturally closely tied to hope.

      I have faith that by acting I will get what I hope for, and therefore I act.

      Sam

  33. A rooted filesystem would help by Trailer+Trash · · Score: 1

    A rooted filesystem would help, too, along with a reasonable "fork", but at some point you just have a crappy, Microsoft version of Unix. Why bother?

    1. Re:A rooted filesystem would help by TheRaven64 · · Score: 1

      Windows has had a single-rooted (networked) filesystem hierarchy for ages. If you use a DOS-style path, it is internally translated to something like \\localhost\c\foo (not used Windows for a few years, so I can't remember the exact syntax). NTFS has also supported arbitrary numbers of forks since its inception. You can copy things into forks using the copy command on the command line. Services for Macintosh used this in its AFP server for compatibility with HFS+, but it's not commonly used by Windows software since there is no fork emulation for FAT filesystems.

      --
      I am TheRaven on Soylent News
    2. Re:A rooted filesystem would help by Trailer+Trash · · Score: 1

      Perhaps I should have clarified. "A single rooted filesystem with the ability to mount drives arbitrarily within that system". "\\localhost\c\foo" isn't terribly more useful than "C:\foo".

    3. Re:A rooted filesystem would help by TheRaven64 · · Score: 1

      Once again, this has been around for about a decade. You can configure the mappings however you want, and you can mount things in multiple places using NTFS junctions.

      --
      I am TheRaven on Soylent News
    4. Re:A rooted filesystem would help by amliebsch · · Score: 1

      Uh...you can already do this? Use the Disk Managment tool to mount volumes to any empty directory in your filesystem.

      --
      If you don't know where you are going, you will wind up somewhere else.
    5. Re:A rooted filesystem would help by jameskojiro · · Score: 1

      You can take multiple drives and mount them to directories, making them more unix like, you still have C:\ but you can mount hd0 to c:\, hd1 to C:\Program Files, hd2 to C:\Documents and Settings, C:\windows is kinda like /bin, it is always mounted on root.

      --
      Tsukasa: All I really want, is to be left alone...
    6. Re:A rooted filesystem would help by afidel · · Score: 1

      You can use reparse points to use a single root point for all local resources and DFS for a single root point for all network resources (across all computers in the forest). IE \\localhost\c\DDriveFolder is a reparse to a second volume which could have alternately been named D:\ also with DFS I can present any number of fileshares as a common rooted namespace with the ability to provide arbitrary distribution and failover. In fact I do exactly that to collapse a number of file servers into two at DR without changing the way people work of access their data.

      --
      There are 4 boxes to use in the defense of liberty: soap, ballot, jury, ammo. Use in that order. Starting now.
    7. Re:A rooted filesystem would help by EvanED · · Score: 1

      I think the fork the OP is talking about is for forking processes, not alternate data streams.

      (The latter is actually starting to see use BTW. For instance, if you download a file with IE, it will add a stream that states that it came from the internet, and if you run it, it will display a confirmation dialog that the program came from an untrusted source. (This is starting with XP SP2; I don't know how it interacts with UAC in Vista.) I think it's actually a reasonably spiffy technique, at least if it works, which I don't know if it does.)

    8. Re:A rooted filesystem would help by TheRaven64 · · Score: 1

      Forking is a really strange thing to want. It's a relic from '60s machines which wrote their entire memory contents out on a context switch and was used by Unics as a substitute for supporting shared libraries. The fact that it's the standard way of creating processes in UNIX is a historical accident and nothing to do with good design.

      --
      I am TheRaven on Soylent News
    9. Re:A rooted filesystem would help by EvanED · · Score: 1
      I disagree, and elaborated in another post in this story. It suffers from a bit of a false dichotomy fallacy (i.e. it may be possible to do better process creation than either the Windows method or fork/exec), and there are good arguments for why the Windows-way of doing things is right (fork, especially not the vfork variant, is expensive), but of those that I have heard and those I can think of, I think a well-implemented fork-exec API would be better to have than a CreateProcess API. (Of course, you /could/ have both, but I don't know if that's worth the complexity.) To wit:

      Windows seems to have complexity a lot of places Linux doesn't, and for no good reason. Other places, it is for backwards compatibility, which is a good reason in spite of the fact that maintaining it at almost any cost is already starting to bite MS a bit. As an example of the first case, I trot out my example of process creation.

      The API on Unix seems really weird when you first see it. (Or at least it did to me.) Why do I have two calls -- fork then exec? Why not just have one that creates a new process? (And doesn't block like system(3) does.) Then you learn that there are uses of fork alone -- e.g. the Apache model. But then the big one hits: you can do things between the fork and exec. Want to remap your standard input and output so they go to a pipe? Do fork, dup2 or whatever (I'm too lazy to look it up), then exec. Running as root and want to drop privileges? Do fork, setuid, then exec. Want to run the child process in another directory? Do fork, chdir or whatever, exec. fork has zero parameters. Depending on the version of exec you use, it may have as few as two.

      On Windows, you get CreateProcess. (This isn't a wrapper over a better syscall API either, from what I know; see NtCreateProcess [ntinternals.net].) Any of those things that I said above you have to do in the call to CreateProcess, which means that is a horridly complicated function. Look at the API docs; it takes 10 parameters. (Though for comparison purposes it's better to assume it takes 9. One of them is an out parameter used for the PID and other information.) Not only that, but one of the parameters takes a STARTUPINFO struct, which has 18 fields (three of which must be zero (?!)). Want to redirect standard input and output? You fill in fields in the STARTUPINFO, then set a flag. Want to drop permissions? You create a new SECURITY_ATTRIBUTES struct and pass it to CreateProcess. Want to start it in another working dir? That's a parameter to CreateProcess.
    10. Re:A rooted filesystem would help by EvanED · · Score: 1

      I guess I didn't do a good job of wrapping up my argument in my original post, and then never finished it in this one. My point is that, because everything that you might want to do to affect the execution environment of the child process you have to be able to do at the CreateProcess call, the complexity is there whether you need it or not. Even though probably most of the time you're not going to redirect standard input or output, change security permissions, or change the working directory, you have to deal with those options whenever you make a call to CreateProcess, whether you care or not.

    11. Re:A rooted filesystem would help by spitzak · · Score: 1

      No, you cannot make "/xyz" point at an arbitrary place. As far as I can tell the highest up in the hierarchy you can go is "//localhost/?/a/xyz", the "xyz" can be made to point somewhere.

      Since you cannot make arbitrary changes I agree with the gp that NT is not providing a "single rooted file system".

      Another HUGE problem is that not all the Win32 calls accept unc filenames, meaning you cannot type them into many programs.

      Conversely, I would like Unix to accept a zero-length filename so that the "//" leading syntax is legit. Apparently this is not allowed by the POSIX standard but I think that should be changed. This and FUSE would allow 100% compatability with the Windows unc filenames. And they should get rid of that "prefix:" syntax being used by wrapper libraries to access things, and go with mounted links.

  34. Bristol vs Microsoft - nothing to trust in MS by Locutus · · Score: 1

    A long time ago in a sector far far away, the Imperial Microsoft Death Star
    set its sights on UNIX application vendors. The Death Star weapon was a
    big success. See the Bristol vs Microsoft history. So, is there really
    enough ignorance in the market to let them do it again?

    http://www.google.com/search?q=bristol+vs+Microsoft

    "The Truth Is Out There," just look for all the evidence.
    "Trust No One," at Microsoft.
    "I Want to Believe" but they are still out to destroy Linux.

    LoB

    --
    "Anyone who stands out in the middle of a road looks like roadkill to me." --Linus
  35. UNG?? by LecheryJesus · · Score: 0

    Isn't that the noise you make if you get kicked in the nuts?

    --
    Jesus was an invention of the Romans - watch "The Pharmacractic Inquisition" for something more credible...
  36. You cracked it! by Anonymous Coward · · Score: 0

    > "A business tries to appeal to its market"

    Therefore Microsoft is not a business?

    1. Re:You cracked it! by Anonymous Coward · · Score: 0

      > "A business tries to appeal to its market"

      Therefore Microsoft is not a business? No. It's a cult, to be sure.
  37. In other words, someone at the top said: by ProteusQ · · Score: 1

    So, we can legally rebrand every BSD codebase as MS products? No kidding...!

  38. Microborg Collective by mk_is_here · · Score: 1

    Now they are going to assimilate the GNU!

  39. They have to by law by esocid · · Score: 4, Informative
    This is just a conference to make it look like this interoperability was all their idea. From this quote:

    This covenant will use the exact same terms created in October for the protocols covered by the CFI decision. This means that open source developers will be able to use the documentation to develop implementations of these protocols without paying for a patent license. Companies that subsequently engage in commercial distribution of these protocol implementations will be able to obtain a patent license from Microsoft, as will enterprises that obtain these implementations from a distributor that does not have such a patent license. So that's how we're addressing the intellectual property rights
    you can see that all they are doing is simply complying with the CFI's decision about how the

    Commission found that Microsoft had abused its monopoly in the market for client PC operating systems by (i) refusing to supply its competitors in the market for work group server operating systems with "interoperability information," i.e., documentation allowing server products of Microsoft's competitors to freely interoperate with the Windows environment, and (ii) tying the Windows client PC operating system and Windows Media Player.
    --
    Absolute power corrupts absolutely. indymedia
  40. Unix crowd? by DBCubix · · Score: 1

    If 3's a crowd.

    --
    I called it a mighty Sperm Whale, she called it Finding Nemo.
  41. it was destined to be so... by AceJohnny · · Score: 1

    "Those who do not understand UNIX are condemned to reinvent it, poorly." - Henry Spencer

    --
    Misleading titles? Inflammatory blurbs? Keep in mind that Slashdot is a tabloid.
  42. Non commercial use by pembo13 · · Score: 1

    Is, I worry, an attempt to divide OSS from it's commercial funding. The RedHat's and Sun's, etc that put dollars into OSS which the users in turn benefit from.

    --
    "Thanks for all the money you paid to us. We've used it to buy off ISO among other things" -Microsoft
  43. Yeah..... Except by mpapet · · Score: 1

    They'll do with Windows Server Core what they did with that home server garbage. You can't upgrade, migrate or otherwise get out of it. A quick and dirty search for an eula for Windows Server Core came up empty. Please, post one!

    As is always the case with Microsoft, the first few features are free. It's the rest they'll screw you on.

    --
    http://www.maxineudall.com/2010/02/should-economists-be-sued-for-malpractice.html
  44. Where is the news? by WhyMeWorry · · Score: 1

    The article about microsoft taking on GNU sounds like microsoft is going to duplicate cygwin. Is this the great breakthrough? The only surprise is that they plan on doing this internally.

  45. Trying to appeal or trying not to? by Anonymous Coward · · Score: 0

    How would MS be trying to appeal to the "Unix crowd" if all the things that it has supposedly done towards these ends (making available communication protocols) were things they were forced to do?

  46. The real Microsoft UNG by kabloom · · Score: 1
    Microsoft UNG

    Microsoft C#UNG (pronounced "chung" and short for C# Universal Network/Graph System) is a desktop application that displays graphs, which are collections of vertices connected by edges. C#UNG can read graphs in several file formats, lay them out using one of several layout algorithms, and display them with a variety of display options. An Excel add-in enables graph data entered in an Excel worksheet to be displayed easily in C#UNG. The components used to develop the application are available as an API for developers who want to create and display graphs in their own applications.
  47. Strange date by fcarolo · · Score: 1

    Microsoft CEO, Steve Ballmer, said on Friday(23 February)
    Yeah, he said this directly from his alternative universe, since in this universe Friday was February 22.
    1. Re:Strange date by popmaker · · Score: 1

      Already we are seeing some signs of difficulties with the UNG calendar programs.

      Either that or they are actually offering an extra day of the year with this thing.

    2. Re:Strange date by allenw · · Score: 1

      An alternate universe where not only is the date weird (maybe the leap day happens in January?) but Microsoft employees apparently don't know their CEO is Steve Ballmer and need to have this explained in internal documents on a regular basis.

  48. Comment removed by account_deleted · · Score: 0, Troll

    Comment removed based on user account deletion

  49. Dying desktop by jhines · · Score: 1

    In this day of racks of headless servers, blades, virtual machines, the desktop metaphor that Microsoft has owned for so long is not as relevant as it once was. An increasing amount of their revenue is now coming from the backend that doesn't give a hoot about 3d transparency on a display.

  50. Cultural Differences by Anonymous Coward · · Score: 0

    1. Prank day is APRIL 1, not MARCH 1. Glad to see someone trying to learn the culture, though.
    2. UNG -- nice touch. No matter how many times I've seen the acronym GNU explained in print, it has never been either clever or funny. Putting the same lack of cleverness and humor in your parody is an achievement.

  51. Who's the target? by Phantom+of+the+Opera · · Score: 4, Insightful

    Let's see, the target audience could be :
        * people who hate M$'s guts all ready
        * Windows users who want to see what the fuss is all about
        * Manager who read this and think "my tech people like Unix, I can buy this and they will be happy".

    Would anyone reading this want to touch it with a 10' pole? Anyone curious enough to find out what 'faster and easier' features they've added?

    This is gonna be a dog, a distorted bizarro unix.

    1. Re:Who's the target? by nickyj · · Score: 1

      If it's not free (as in beer), it's not for me.

      --
      Causing Chaos Everywhere,
      Nik J.
      The strange world of a loner, in a populous city, drowning in society
  52. The sound of a thousand toliets flushing by Anonymous Coward · · Score: 0

    [T]hey are aiming to restore a Unix-like environment to its former proprietary glory
    Let's see. So, I can "buy" OpenSolaris from Sun, hire support services from Sun on contract as I need, and I can also hire in-house talent to do small custom modifications as necessary. Microsoft plans to enter this market with a proprietary (read: closed source) but interoperable product?

    Well, Microsoft knows what it's doing. I'm sure this will go over as well as Vista has.
  53. Jackson? by splutty · · Score: 1

    That reminds me of Michael Jackson. Born a black man, will die a white woman.

    --
    Coz eternity my friend, is a long *ing time.
  54. Who would rely on Microsoft support for this? by cptnapalm · · Score: 1, Interesting

    Considering how routinely Microsoft drops support for something they offer, telling their users to switch over to their newest latest, greatest and best, who would actually rely on this thing for the long haul? This isn't even a "Microsoft is evil" post; I'm just not sure who would believe they could depend on Microsoft to continue support this over a long period of time.

  55. Its all part of a new FUD campaign by JustNiz · · Score: 1

    MS will implement this GNUish wrapper in the same way they implemnented POSIX and STL under windows.... very badly.

    Then their marketing dept. will use it to demonstrate how crap GNU is compared to native windows functionality to the executive managers of large traditionally MS-only IT depts looking to migrate to Linux.

    The sad reality is that most managers will believe the MS droids that they're looking at a truly representative GNU environment so will agree GNU is bad, without ever having seen a real GNU environment.

  56. Looks like a trap... by mdeslaur · · Score: 1

    Now that Microsoft has released all the documentation, won't it be easier for them to sue commercial open-source projects? Is there a legal difference between reverse-engineering protocols to make a clean-room implementation and using the documentation provided by Microsoft, but that comes with a license?

  57. Re:Wow - may already be possible to do by dyfet · · Score: 1

    I dunno, seems plausible enough to me. I was always of fan of the idea of extracting the NT kernel and doing a GNU distribution on top of it. (Something which is theoretically possible even without Microsoft's help, though rather difficult.) Microsoft would never have been happy about it because it would further erode their lock-in.


    I imagine this could be achieved using ReactOS, which is a project to create a GNU GPL licensed NT-like/binary call compatible kernel. I am not suggesting whether doing so is good or bad, but rather simply pointing out the possibility may already exist to do this without requiring the involvement of or help from Microsoft.



  58. Copyright violations? by hippo · · Score: 1

    Let's hope that SCOX are still around when this gets released so they can sue Microsoft for stealing their IP.

  59. Unix is better than Windows by n6kuy · · Score: 1

    Microsoft already knows it.

    --
    If you disagree with me on social issues, then it's pretty clear that you are a narrow-minded bigot.
  60. You forgot someone, I think by Anonymous Coward · · Score: 0

    I believe that Andy Tenenbaum was also there, hugging and shaking hands with Torvalds, Stallman, and Ballmer. Then Torvalds and Tenenbaum announced that they are developing a hybrid kernel monolithic kernel on top of a microkernel, based on both Linux and Minix, to run UNG.

    When they were done, Ballmer actually *sat down* in a chair instead of throwing it, while each of them (Torvalds, Tenembaum, and Stallman) describe this bright new future for the IT world. (It's rumored that Ballmer was not actually listening to them, however, but instead doing transcendental meditation during the speeches. . . developers, developers, developers, developers, developers. . .)

  61. Did I miss a massive management turn over? by HangingChad · · Score: 1

    Has Microsoft totally switched gears in how it is approaching the Unix and FOSS sector for direct competition?

    In the absence of a massive turn over in management, this is MS changing gears and competing with FOSS the same way they competed with Netscape. The same way they competed in the SCO fiasco, file formats, DRM, and all the other ways MS "competes" in the IT world. The kind of competition that just earned them a $1.3 billion dollar fine from the EU.

    A leopard can't change its spots and MSFT can't change their character with the same people calling the shots. If they really want to change direction a re-establish trust then that change has start and spring from the top.

    --
    That's our life, the big wheel of shit. - The Fat Man, Blue Tango Salvage
  62. They're NOT opening up to "open source" by argent · · Score: 4, Insightful

    They're opening up to "non-commercial use".

    This isn't "Microsoft's answer to Open Source", it's "Microsoft's answer to shareware".

    Releasing these documents is meaningless to the open source community so long as they require money for "commercial use". It's not meaningless, but it's not the open source community that will benefit.

  63. the last war by LEBMan · · Score: 1

    Funny. We always fight the last war. The VMWare and other products make this approach irrelevant. Why would anybody want to run x86 Unix/Linux code under a fake OS "framework," when they can just boot it in a VM? If what they're saying is that I can download & run x86 Linux-compiled binaries that will interoperate with Windows at the X11 and OS Kernel level, then yee-hah, more power to them, but they're expending an awful lot of effort for virtually zero payback. Mabye it's a stop-loss strategy: prevent further erosion of the Windows desktop. If anything, this goes to show (me) that MS still doesn't "get" "open." The idea that's driving Linux to the desktop isn't the superiority of its "tools." Tools in both environments are competitive. It's the idea that you don't have to pay a licensing tax to use the software. Putting an "honest" UNIX personality under-the-covers of Vista makes it look an AWFUL LOT MORE like OS/X, rather than a Linux "killer." Yee-hah. A war on two fronts!

  64. Recursive acronyms by popmaker · · Score: 1

    So, UNG stands for "UNG's not GNU" and GNU stands for "GNU's not unix".
    Unwinding the definitions, one gets "UNG is not GNU is not Unix".
    I just thank god that GNU is not UNG.

    1. Re:Recursive acronyms by Pitr · · Score: 1

      I think there's a haiku in there somewhere... but my brain hurts too much to try and find it.

      --

      --Not to be worried, Pitr fix.
  65. Spot on by bogie · · Score: 1

    Exactly what I heard from people in the know like the Samba project. This is a big FU to the OSS community and anyone who wants better interoperability with Microsoft's products. For pete's sake, split the freaking company into pieces already. The individuals companies would be thrilled to not have MS's entertainment divisions dragging them all over the place.

    --
    If you wanna get rich, you know that payback is a bitch
  66. while they are at it by EdelFactor19 · · Score: 1

    gnu is going to have to release GNW: gnu's not windows, that way MS can follow by releasing MSNW: MicroSoft's not Windows

    keeping the holy war joke from another poster, they will obv include emacs and vii... but they are clearly going to have to introduce their own entry into that holy war too so that it can be a complete trio.

    On a more serious note does this mean that the previously scrapped "longhorn power console update" dealie that got the axe is going to finally get put back in?

    as a linux user and fan who's ditched windows; i hate to say it but I think that is a very wise move on their part. there are many times in the workplace where as much as I prefer linux, windows on the whole would provide me w/ an easier solution if not for the lack of a decent command line interface. Yes i could install cygwin, but there is ugliness to it and i have yet to see a good ultra easy way to launch the term. that and when i installed cygwin's X component (and registered it into my env so that it would work) it broke my windows emacs install. and vm's just arent the same thing for this purpose. What are the problems that it can resolve that I'm having in linux?

    work machine is a laptop
    1. display switching (take with a grain of salt because I'm running under compizfusion w/xgl which presents a problem for this issue)
    i have a widescreen panel attatched to the laptop that i use for display expansion. problem is that if x/xgl is started when im not connected to the display, even when i plug it in i cant change my resolution live (using xrandr/resapplet) to the 'right' resolution. i could go from 1400x1050 to 2800x1050 instead of 3360x1050 (which sadly is not 3050 as it should be for a 1400x1050 + a 1680x1050). when i have started docked and was at the higher resolution i seem to have to switch from compiz to metacity to do the res change and then restart compiz (not restart x) to go back up to full res if i have to undock ( i seem to be able to safely reduce the res down from 3360->1400). if i dont its a lop sided coin toss and more times than not it crashes X and i end up having to reboot. also i have yet to get the vga out to work to connect to a projector if i dont boot connected to it... again these issues are probably because of xgl more than anything else.. (this is on a thinkpad t60p with firegl mv5250... if you have a fix i'd love the hear it :-)

    2. mice
    so i bought a wireless usb mouse to plugin to the laptop; problem is its moving "way too fast" on the screen.. if i lower the speed it doesnt affect that mouse only, it seems to slow down both the touchpad/stick as well; which becomes a problem when i undock. lately the speed change doesnt seem to do anything.. the other problem ive run into is getting all of the buttons recognized; i've got everything working except for the horizontal tilt on the tilt wheel. dunno why, but it isn't even getting reported down to xev. dunno why, i think it has to do with the the synaptics touchpad/stick and the wireless mouse (logitech vxrevo) all getting dumped onto the same 'device' from /dev.... and yes ive googled around for this i speculate id have better luck on a desktop.

    --
    "Jazz isn't dead, it just smells funny" ~Frank Zappa
    EdelFactor
  67. Cross platform development by SpinyNorman · · Score: 1

    If it makes sense for Microsoft commercially then bully for them, but for anyone wanting to develop for Windows (or Linux+Windows) using free software there's already plently of choices:

    MinGW -- minimal GNU toolchain for Windows (incl g++/gcc)
    Qt (not just GUI, but also threads, networking, ...)
    Cygwin -- Linux API DLL for porting Linux apps to Windows (I prefer to just use cross-platform libraries)
    Cygwin/X -- X windows libs, server, utilities for Windows (presumably can be used with GTK, although I havn't tried it)
    pthreads_win32
    Boost.Theads - portable threads library (if pthreads, or QThread doesn't fit your needs)

    Using MinGW and Qt it's easy to develop apps that can just be recompiled across Linus/Solaris/Windows/Mac.

    What's currently missing is a strong cross-platform multimedia toolkit, but that will be changing with KDE's Phonon framework which will be supported by Qt 4.4. Phonon will support Linux, Windows and Mac via (respectively) GStreamer, DirectShow and Quicktime backends.

    I'm not sure if GNOME has any equivalent in the works, or to what degree Phonon is tied to Qt. Having alternate desktops and even GUI libraries is not a bad thing, but it'd be helpful if Linux could standardize on core stuff like multimedia support rather than having competing camps there too.

  68. It's the channel partnering, stupid. by tjstork · · Score: 4, Interesting

    My whole point of investing my time into Linux is because FOSS is a cultural phenomon that is completely new. Nobody, at least, not a single entity, owns Linux, and for that reason, it belongs to everyone. If you make some sort of a contribution to it, free of charge, it is almost like making a contribution directly to humanity.

    I can't possibly see how Microsoft could pull off a similar thing.

    No amount of being nice or slick marketing posters could make me think that writing for free on platform with a track record of sickening self interest could even remotely equate to the grand social experiment that is Linux.

    But that's really not the worst of it. If anything, the slick marketing posters that come with Windows are a part of the problem. To a large extent, I view the drive for Linux as a push for a newer set of ethics for consulting firms.

    We need to at some examine the relationship consulting firms have with large concerns like Microsoft. I always though that in the ideal case, a consultant was somewhat akin to a doctor, supposedly free of any sort of taint from any particular vendor's solution. But that's not what we have today. We have consulting firms that are "Junior, Gold", and more with Microsoft. It's an unholy alliance, where, consultants invest in MCSD's and other certifications, pay through the nose to get a product logo'd as compatible. In exchange, Microsoft gives those companies preferred listings and free development tools and operating systems. So basically, Microsoft is using artificial prices for copying to induce consultants to support their platform for free, and those consultants, in turn, are going to always be biased towards push their clients to Microsoft products. Indeed, higher levels of Microsoft partnership require sales of Microsoft products to achieve Gold or some other channel status.

    If doctors did that, they would be barred from practice, and I think this comingling of a vendor with a solution provider is flat out wrong. In other lines of business, if you were paid by a vendor to advocate a particular product, selling everything from nuts and bolts to window frames, you would wind up in jail. But this practice of "partnering" is mysteriously ok in IT.

    Adopting Linux removes this disgust. Because the software is free, there's no incentive to copy it, and ultimately, the customer is going to wind up with a solution that is genuinely more right sized for their needs. With Microsoft, you'll always have consultants pushing Biztalk and Enterprise this or Enterprise that, because, well, they are getting paid to do it.

    The bottom line is this. If Microsoft genuinely wants to promote an open source environment, then yes, it has to make open source software, but it also has to work to promote the idea of a consultant as an independent advocate for his or her clients. We are not some salesman on the cheap motivated by free licensing for products similar to what Linux gives you for free.

    --
    This is my sig.
    1. Re:It's the channel partnering, stupid. by Cjstone · · Score: 1

      If doctors did that, they would be barred from practice, and I think this comingling of a vendor with a solution provider is flat out wrong. Doctors do just that. Prescription drug companies give doctors a lot of perks and, in exchange, the doctors will often sell brand-name drugs over the generic variants. Sad but true.
    2. Re:It's the channel partnering, stupid. by maxume · · Score: 1

      HMOs and PPOs are pretty much exactly what you are describing, with doctors instead of consultants.

      --
      Nerd rage is the funniest rage.
    3. Re:It's the channel partnering, stupid. by Jynx77 · · Score: 1
      Consultants are consultants. Every big company has them pulling the same type of stunts. Even the consultants pushing FOSS are self-serving, except maybe for you and those other people

      making a contribution directly to humanity.
      You are the good guys of course. Alot of this FOSS rhetoric reminds me of Animal Farm http://en.wikipedia.org/wiki/Animal_Farm with MS as the humans.
      --
      It's turtles all the way down!
    4. Re:It's the channel partnering, stupid. by Anonymous Coward · · Score: 0

      Amusingly, this post plays right into the idea that Linux is communist.

    5. Re:It's the channel partnering, stupid. by clang_jangle · · Score: 1

      Indeed they do. Furthermore, a doctor's education in an AMA-approved med school is almost completely controlled by Big Pharma, so between the profit motive and the brainwash your odds of finding a truly good doctor are roughly equivalent to the odds that MS is sincere about interoperability.

      --
      Caveat Utilitor
    6. Re:It's the channel partnering, stupid. by tjstork · · Score: 1

      You are the good guys of course. Alot of this FOSS rhetoric reminds me of Animal Farm http://en.wikipedia.org/wiki/Animal_Farm with MS as the humans.

      Well, yeah... the thing though, is that separates FOSS from socialism is that there is no scarcity for duplicating software, and, as a consequence, there is a complete lack of central control.

      Animal Farm, warns us, quite rightly, that, once you decide to have a government doling out resources "fairly", then, the government is going to abuse the privilege and the result will be a huge, inefficient mess. However, no one in Linux can be the Orwell's Napolean Pig because no one owns it. There's no central control, no authority. If anyone is like animal farm, it is in fact, Microsoft, because it is a single, centrally planned system.

      That's not to say that there's some nauseatingly liberal folks working on Linux. There are. Richard Stallman is all but a bleeding heart socialist, but I think in his case it is forgivable because he spent all that time writing emacs when he could have been improving vi
      And true, some Linux people will argue in favor of standards and a single approach to something, but, for an operating system that has more desktops GUIs, more languages, more file systems, and more databases out of the box, I'd have to say that a lot less people buy into that central argument on the Linux side than do the MS side, which has one desktop, maybe two programming languages, a single file system and a single database server.

      --
      This is my sig.
  69. what took so long? by billmil · · Score: 1

    I don't understand why MSFT has treated the "command line crowd" with such a crappy product for the last 20 years.

    They clearly did not want people to use the dos window: thus it's pretty much the same as in 1985 and lacks bash' niceties.

    Only recently have they added auto-complete.

    They clearly should have added an easier-to-use command line and made windows less of pain to administer from the command line.

    1. Re:what took so long? by thethibs · · Score: 1

      command.com and cmd.exe were never meant to be heavy-duty shells. They do what they are supposed to do--run simple scripts that call applications to do the heavy lifting. Use wsh and VBScript or JScript for interesting scripts if you are too cheap to buy something stronger. Anyone who wants a big interactive shell can run one of the many third-party shells, including ports of ksh, csh, and bash.

      Oh, yeah. command.com wasn't DOS and cmd.exe isn't.

      --
      I'm a Programmer. That's one level above Software Engineer and one level below Engineer.
  70. Screenshots? by RavenChild · · Score: 0

    Are there any screenshots of this GUI-less version?

  71. This looks fake by Animats · · Score: 1

    First, Microsoft would never call it "UNG". Second, Ballmer would not talk about a "UNIX-like environment". Microsoft doesn't need a UNIX-like offering. Ballmer might order Microsoft to develop an easy migration path from Linux servers to Windows servers, but the Linux desktop share is too small to matter.

    1. Re:This looks fake by booch · · Score: 1

      I like the way that the "internal" memo has to explain who Steve Balmer is. Also, the way "proprietary" is misspelled.

      --
      Software sucks. Open Source sucks less.
    2. Re:This looks fake by EvanED · · Score: 1

      And the way 2/23/08 was a Friday.

  72. I think its great news! by Anonymous Coward · · Score: 0, Flamebait

    I love programming in unix, shell scripting, pipes, the entire unix philosophy about building tools for a specific purpose and putting them together, but I HATE THE FSF because of their idiot dogmatic refusal to support ordinary programs. Look RMS has money thrown at him for basically doing nothing at all, he is a complete antisocial bum, and he doesn't understand what it means to hold an ordinary job and pay bills. You FSF freaks take note, theres no such thing as GPL'd food or shelter.

    It would be an extraordinarily good day for programmers if Microsoft could simply sideline the GNU project completely and then we could all tell RMS to just go fuck off. All of the unixy goodness, none of the stupid dogma.

    1. Re:I think its great news! by jsiren · · Score: 2, Interesting

      Then get a job working with Solaris, HP-UX, AIX, etc. These still exist, you know.

      While on the subject, I'm sure many people have told RMS to fsck off. Then again, thanks to his "stupid dogma" I've always been able to count on some excellent tools (such as bash, apache, perl...), which are nearly always much better than the vendor-supplied equivalent. The latter tend to be somewhat quirky and/or limited.

      Oh yes, I've always been paid real money.

      --
      Usage: km/h for speed (kilometers per hour); kph for very slow impulses (kilopond hours).
    2. Re:I think its great news! by Anonymous Coward · · Score: 0

      You FSF freaks take note, theres no such thing as GPL'd food or shelter.

      Something close to it, here. :)

    3. Re:I think its great news! by Anonymous Coward · · Score: 0

      Why don't you just move to North Korea; I hear they worship MS there...

    4. Re:I think its great news! by zippthorne · · Score: 2, Interesting

      Woah, woah, RMS is a worthless commie, but he's not a lazy worthless commie.

      He did write the Emacs Operating System, after all.

      IMO, that gets negative points, but it's certainly quite a bit far from nothing, you'll have to concede.

      And you still have plenty of Unix options that don't involve free software. You just have to buy actual Unix.

      --
      Can you be Even More Awesome?!
    5. Re:I think its great news! by MindKata · · Score: 5, Insightful

      "able to count on some excellent tools" and from one of the parent posts "Microsoft would never have been happy about it because it would further erode their lock-in."

      also from the article link http://www.royalidea.com/site/?q=node/12 we get this section...
      "The aim of UNG is to write complete GNU-like tools and frameworks that will be completely compatible with existing GNU software and standards. These tools will run natively on Vista. This means that software written for the GNU environment will be able to compile and run on Vista with little or no modifications. Major software currently running on GNU/Linux will be able to run natively on Vista."

      Microsoft's strategy revolves around the idea of lock in. Looking at this from the point of view of lock in, it then sounds like Microsoft is trying to find a way to get GNU code over onto Vista. If you can't beat them, then assimilate anything useful they have ... like some excellent tools. That way, you get some good and free applications, sitting on top of your proprietary OS. Plus maybe even help remove, some of the reasons some corporate (non-technical) bosses of companies would think their staff would want Linux. "Why both, its got the same apps on Vista?".

      While Microsoft controls the OS, they hold the foundations upon which all their competitors try to build a living. They are not going to give that up, but any company switching to Linux is a problem for them. So this is another chess move to try to reduce corporate customers moving towards Linux. Loosing corporate customers is what Microsoft really fears. Big customers moving away from Windows sends out a message to other big customers to act in a similar way. Microsoft wants to prevent this slide, especially as more cheaper embedded systems are very likely in the near future and a lot of them are likely to be using Linux.
      e.g. News such as 10 billion ARM CPU sales isn't going to help Microsoft as much as its going to help grow Linux support, as a lot of ARM CPUs are using embedded Linux. Add to this the number of other CPUs using embedded forms of Linux, then industry support for Linux is growing faster than just on desktop machines. Microsoft needs to move to either block or reduce this, to help maintain their OS lock-in.
      e.g. http://www.vnunet.com/vnunet/news/2207797/arm-hits-billion-processor

      --
      There are 10 kinds of people in the world... those who understand binary and those who don't.
    6. Re:I think its great news! by Anonymous Coward · · Score: 1, Informative

      Apache doesn't have a copylefted license. Its just like you people, I bet you almost posted GNU-Apache didn't you? Why don't you lay off taking credit for other peoples work, thats the whole point, work has value, and you guys just never get that part.

    7. Re:I think its great news! by AmaDaden · · Score: 3, Insightful

      I agree but I feel that in the long run it's going to totally destroy their lock-in. Let's say your a developer out to make some new software. Since *nix code can now run on Windows, OS X, Linux and Unix with a doable effort you might as well aim for that. Given a few years most software will be multi-platform and the idea of anything else will seem silly.

    8. Re:I think its great news! by ardor · · Score: 4, Insightful

      Note though that the GPL is specifically designed to prevent Embrace&Extend. They cannot take, say, gcc, and develop propietary closed-source extensions on top.Their only way of applying lock-in is by using propietary formats and protocols - which require apps to be written from scratch. So, nothing new on the assimilation front.

      --
      This sig does not contain any SCO code.
    9. Re:I think its great news! by Anonymous Coward · · Score: 0

      I wonder about that. Stallman has made software unusable for production in business with GPL v3 because any and all trade secrets must come with bundled stuff, so if you use GPL v3 software in a car's ECM, you have to also give every single timing value and part blueprint with materials and allow specs of everything hardware to be given to the customer and anyone he or she chooses, or else its a copyright violation, and can be criminally and civilly punished.

      This is why every business I know of who was doing embedded work in Linux has dumped it for Windows CE. Not because WinCE is better, but because should some GPL v3 software be added somehow, it would kill the company with lawsuits, from shareholders stating the company failed to use due diligence, to GPL enforcers, to corporate regulators swooping in because of a Sarbanes Oxley violation, to customers who by the v3 license can demand any and all corporate trade secrets for their widget. The $3 per hardware item that Windows CE has for a licensing fee is cheap when compared to the damage should a GPL v3 module be accidentally incorporated.

      Stallman has effectively killed Linux for use in embedded apps with the GPL v3. Even more ironic, it doesn't stop DRM at all. Look at the PS3 and the hypervisor used.

    10. Re:I think its great news! by BlueStraggler · · Score: 4, Interesting

      And say you're a company maintaining existing cross-platform software. Why pay the costs of maintaining Windows and Unix versions; just drop support for the Windows version, and let UNG pick up the slack. But once a few companies start doing that, the negative marketing consequences (not a real technical issue, just the *appearance* of loss of Windows support) will probably cause Microsoft to scuttle the whole idea and screw over everyone who had banked on it.

      A better strategic approach would be the inverse - a Windows-compatible subsystem that runs on *nix. Then companies could drop support for their *nix versions, and let this subsystem pick up the cross-platform slack. This gives superior marketing optics - the major packages only appear to run on Windows. In reality, of course, it would mean that everything runs on *nix, but marketing trumps reality, so it would be a pyrrhic victory for the *nixers.

    11. Re:I think its great news! by Anonymous Coward · · Score: 1, Informative

      Apache doesn't have a copylefted license. Nor does perl.
    12. Re:I think its great news! by darien · · Score: 1

      work has value

      So who's going to pay me for the six hours I spent today moving rocks from one side of the beach to the other? A lot of effort went into that!

    13. Re:I think its great news! by DannyO152 · · Score: 1

      Isn't this the server side of the Linux Desktop conundrum. How do you get people to switch when what they have is okay?

    14. Re:I think its great news! by swiftcoder · · Score: 2, Insightful

      Lock-in doesn't require closed source. Look at what Apple does with GCC, they extend the compiler willy-nilly (fully open-source, all of it), and now every Mac ships with a custom GCC that understands lots of additional options, changes the meaning of others, doesn't support some standard options, and produces completely incompatible binaries...

      Sure you can apply the Apple patches to mainline GCC, and get the same thing, but that doesn't change the fact the this is lock-in: Mac developers have different expectations about GCC's operation than do linux users.

      --
      http://swiftcoder.wordpress.com
    15. Re:I think its great news! by AmaDaden · · Score: 1

      Why pay the costs of maintaining Windows and Unix versions; just drop support for the Windows version, and let UNG pick up the slack.
      That's almost what I'm saying. Maintain a Windows version that ONLY uses UNG. Do it from day one. You can say it runs on Windows AND Unix. If you plan on doing this from the start you can minimize the cross platform issues and therefore adding Windows to the list of *nix systems you support will be trivial. The only issue this would have is if UNG is just a bunch of GNU app clones that are too underpowered to do anything. If this is the case it's a joke anyway and Windows will continue it's slow but steady death march.
    16. Re:I think its great news! by ardor · · Score: 1

      This is just a customized GCC. Lock-in means you cannot get out by any means except expensive reverse-engineering (not required here, since Apple's GCC code is fully available). Also, no patents apply (otherwise the GPL could not be used), so there is no IP blocker either. It is by all means just a customized version of some opensource software. ARM does this all the time, for example.

      --
      This sig does not contain any SCO code.
    17. Re:I think its great news! by Doctor+Memory · · Score: 1

      He did write the Emacs Operating System, after all. Yep, and MS is going to provide that too...
      --
      Just junk food for thought...
    18. Re:I think its great news! by Anne+Thwacks · · Score: 1
      The aim of UNG is to write complete GNU-like tools and frameworks that will be completely compatible with existing GNU software and standards.

      This stands to demonstrate beyond all reasonable doubt that the reason most of us use OpenSource is the process not the product. I really look forward to Bash rewritten by MS 'MASH' - I confidently predict a more bug infested product will never see the light of day. In fact, that is the point - the bug infested 'MASH' will not see the light of day, while bash code is open for all to see.

      "Free as in roaming the jungle wild and uncontrollable" - yay that the kind of software we all need ???

      --
      Sent from my ASR33 using ASCII
    19. Re:I think its great news! by Schraegstrichpunkt · · Score: 1

      All of the unixy goodness, none of the stupid dogma

      Cut the man some slack. He is the reason why Unix is still relevant today.

    20. Re:I think its great news! by Anonymous Coward · · Score: 0

      a Windows-compatible subsystem that runs on *nix.
      ---------
      It's called WINE www.wine-hq.com

      It's not perfect but it works a lot of the time and is getting better every day. My favorite games are running on my 64 bit Gentoo system...

      Sound support is pretty weak, and you need some libraries from a real windows image for some things, but it's pretty stable. It's a little slower but not by much. Often it requires a patch here and there but it's FOSS so you can apply all the patches you like, and chances are there's a patch out there you can find.

      -AC

  73. The question becomes... by Junta · · Score: 1

    Why the hell would you want to do that? The kernel is not interesting, and doesn't give you the vast majority of compatibility features, you need the various libraries, GUI, everything else. If you think magically excel will work without MS libraries and will run under X, you are deluded.

    --
    XML is like violence. If it doesn't solve the problem, use more.
  74. Back to the beginning..... by naglep · · Score: 1

    A GUI-less Windows.. Isn't that called DOS?? Or have I missed something..

    1. Re:Back to the beginning..... by EvanED · · Score: 1

      A GUI-less Windows.. Isn't that called DOS?? Or have I missed something..

      Um, maybe Windows NT?

      Hell, the connections between Windows 9x and DOS are often overstated:
      "Among other things those drivers did [during the loading of Win95] was 'suck the brains out of MS-DOS,' transfer all that state to the 32-bit file system manager, and then shut off MS-DOS."

  75. UNIX on Windows is like.... by JetScootr · · Score: 1

    A landfill on a toxic waste dumpsite.
    Really, if they did it, they'd get the disadvantages of both, and the advantages of neither.
    And, as a Unix programmer myself, I'll say it right out: No way in *%$&# would I find that an desirable programming environment.

    --
    Pavlov wouldn't be so famous if he'd used a can opener instead of a bell.
  76. Try to buy just a copy of Excell, just try by crovira · · Score: 1, Troll

    I keep being led around to buy a copy of Office even though don't WANT a fuckin' copy of fuckin' Office.

    All I fuckin' well want is a fuckin' copy of fuckin' Excel.

    And they keep asking all these fuckin' questions.

    ALL I WANT IS A FUCKIN' COPY OF EXCELL.

    I DON'T WANT A FUCKIN' INQUISITION!

    THE CLIENT CAN GO AND FUCK HIMSELF.

    --
    MSBPodcast.com The opinions expressed here are my own. If you don't like 'em... Think up your own stuff.
    1. Re:Try to buy just a copy of Excell, just try by Frank+T.+Lofaro+Jr. · · Score: 1

      Get Gnumeric.

      Works just like Excel mostly, except when I tried to print it came out all corrupted, but that is likely fixed by now.

      --
      Just because it CAN be done, doesn't mean it should!
  77. I don't buy it and it wouldn't work anyway by erroneus · · Score: 3, Interesting

    Microsoft would have to do a complete make-over on BSD the way Apple did with OSX. It's not that they couldn't do it, it's that they wouldn't. It would upset all of their development users to no end. There are so many developers making their products and living based on the Windows API that to move to something GNU "compatible" would simply be catastrophic in so many ways that I'd prefer not to put brain power into imagining the details. It would be ugly though... very ugly.

    And in the end, it's not only that the Windows platform isn't and will never be efficient and reliable, it's that people who aren't using Microsoft as their basis for development or operations aren't doing so because they haven't heard or or tried Microsoft's stuff, it's because they have! Microsoft's reputation remains fresh in the minds of those who have rejected them.

    To pull this off would require a lot. The first thing they would need to do is assure their developers that all the work, the time and resources devoted to Microsoft's platforms will not be wasted. To keep those developers would be no easy task. A large portion of them are 'worshipers' but many more are simply very invested in the current API and only take changes in small increments.

    So such a move would take a long time -- even more than 5 years, possibly more than 10 -- to accomplish and even then, people are already burned on Microsoft's name, brand, style and attitude that it would take a long time to 'heal.' But 10 years is a long time to heal those memories, but why should the industry wait 10 years for what it has available to it now just so it could get something from a company that has a general strangle-hold on the IT market? People will figure it out eventually.

    And since so much of today's business mentality is short-term anyway what with having to give in to short-term investors' demands or fear being sued, any planning more than 2 or 3 years out is just unimaginable.

    Can they do it? Should they do it? Yes and yes! I have been saying it all along that if Microsoft wants to restore its former glory, it will have to dump the Windows API and either create a new, more stable and secure basis or adopt BSD and tweak it the way Apple did and hen create a WindowsAPI compatibility layer that actually works. Apple did it with their "Classic" mode (it's not perfect, but it worked well enough for many, and from what I hear Vista is a 'resounding success' even with its declining level of backward compatibility). Microsoft can do it too.

    But will they? Not while present management is currently in control of things. If Microsoft wants another shot at being fresh, new and what's hip the way they were quite a few years ago, they'll have to dump their 80's-mentality leadership and fast! Only then will spurned anti-Microsoft people give a second look at Microsoft now or in the future.

    1. Re:I don't buy it and it wouldn't work anyway by EvanED · · Score: 1

      There are so many developers making their products and living based on the Windows API that to move to something GNU "compatible" would simply be catastrophic in so many ways that I'd prefer not to put brain power into imagining the details. It would be ugly though... very ugly.

      You are making a critical error, which is to assume that they would have to abandon the Windows API. There are two possible approaches:
      1. Do something like Cygwin, and build this hypothetical UNG on top of Win32.
      2. Expand SUA a bit.

      The second approach is the more interesting one. See, the Windows NT system call interface is NOT the Windows API. Translation from the Windows API to the (half-undocumented) system call interface is done by a set of DLLs that together comprise the Windows Subsystem. Other subsystems could provide different translations. For a while there was an OS/2 subsystem, which provided an OS/2 API. SUA is a subsystem that provides a POSIX.2 API. In fact, if you run a 16-bit program, that is running in a different subsystem than 32-bit programs. (Likewise if you run 32-bit programs on 64-bit Windows.)

      One of the very nice things about NT is that it is extremely amenable to putting a new API on top, because it was designed that way from the beginning.

    2. Re:I don't buy it and it wouldn't work anyway by hayriye · · Score: 1

      Microsoft would have to do a complete make-over on BSD the way Apple did with OSX. It's not that they couldn't do it, it's that they wouldn't. It would upset all of their development users to no end. There are so many developers making their products and living based on the Windows API that to move to something GNU "compatible" would simply be catastrophic in so many ways that I'd prefer not to put brain power into imagining the details. It would be ugly though... very ugly.

      You're so right. Just look at the "software component" market which depends on the things that Microsoft didn't solve. For example, if you examine componentsource.com, most components are ActiveX and .NET based; Java and Unix based components have only a marginal share there.

  78. Unbundle, then we'll talk. by Bob9113 · · Score: 1

    Tell ya what Microsoft, I've got a deal for you. You unbundle your products; sell your OS, windowing system, window manager, and applications separately (or give them away, without restrictions on their use, if one or more components are considered not commercially viable alone). And don't use any non-published features, rapidly changing software interfaces under your control, or other anti-competitive advantages to glue them together. The price of the bundle (if you do sell a complete kit) should be within maybe 20% of the sum of the unbundled prices (a reasonable package discount is OK, but anything more than 10% starts to sound like bundling to me). You do that, then we'll talk.

    A big part of *nix's advantage is that it is componentized. You can use the best tool for your particular needs. I don't want to be tied to a particular window manager when I choose a kernel. And if I don't like or need your windowing system, I don't want to pay for it. The nice thing about that approach is that each product has to stand on its own merit. It leads to this cornerstone of free market economics thing called "competition."

    Oh - and stop calling your entire software stack an "OS". You're confusing the end users.

  79. Microsoft X by Digital_Mercenary · · Score: 1

    Its MSX you fools. Bill finally woke up and is after Apple/UNIX. Bill is going to take advantage of the BSD licensing terms and roll out a MS Windows WM. Can't you see??? The rumors are just a way to fake out the market. Bill Gates will copy Apple ther take over the world.

    "MS ZENIX The Return"

    -The End is Near!!!

  80. Some supporting info by Tomy · · Score: 2, Interesting

    I live in Seattle and the last three months I have been receiving a lot of calls from head hunters staffing for MS looking for people with a strong Unix background. When I first received the job descriptions, my guess was that they were working on something that would allow you to manage Linux/Unix systems from a Windows machine. Reflecting back on the job description, it could have been something like this.

    I didn't accept the offers, but here is some free advice:

    - Get rid of single letter drive names (you know, the eighties called, ...)

    - The directory separator is '/', As Seen On Unix and URLs.

    - Reorganize the file system more like Unix/Linux, and maybe rename 'Program Files' to 'Applications', have a /usr directory tree, etc.

    - Ship every copy of the OS with an X server.

    - And I still need a compliant shell and C compiler to support the holy invocation './configure && make && sudo make install'.

    1. Re:Some supporting info by formal_entity · · Score: 1

      Microsoft has distributed SFU for a long time to aid unix-to-win32 migrations. Because the old make, cc etc just plain sucks, what they have actually shipped is gmake, gcc (most of GNU really). A while back GNU switched to GPLv3 which has new wording relating to patents. This basically means that MS can no longer ship any GNU products. However, MS still needs a unix-to-win32 migration story. Basically, the GPLv3 could be the reason why MS created UNG. If UNG is not a hoax that is.

    2. Re:Some supporting info by jeberle · · Score: 1

      If you follow this exercise to its logical conclusion, you end up with, port the Win32 API to BSD.

      Definitely _drop_ the X Server requirement. That's the best thing Windows ever has had going for it! A sane, preconfigured, fast, native, decent-looking, consistent GUI.

      The rest of it. Let's see:

      - Forward-slash (for the love of god)
      - Dump the registration database ( " )
      - Add proper signal handling
      - Add process groups
      - Add psuedo-terminals

      Microsoft threw the baby out with the bathwater when they designed Win16 -- which Win32 just extends. They abandoned any notion of process control from the command-line. That's essentially why cygwin can never work correctly. Without psuedo-terminals, process groups, decent signals, and a process hierarchy, how are you going to control a set of related processes?

    3. Re:Some supporting info by EvanED · · Score: 1

      Get rid of single letter drive names (you know, the eighties called, ...)

      The current situation isn't perfect, but it's not horrible. You can mount drives at paths, just like in Unix. (You do have to do it on NTFS; the functionality is provided by the file system itself rather than at a higher level. This is probably a mistake.) Things work a little funky if you mount removable drives, but it can be done.

      The directory separator is '/', As Seen On Unix and URLs.

      You already can use '/' in many places, including directly in calls to fopen. Again not perfect support; for instance CMD (very annoyingly) won't tab-complete through them.

      Reorganize the file system more like Unix/Linux, and maybe rename 'Program Files' to 'Applications', have a /usr directory tree, etc

      I like the Program Files -> Applications rename idea. Vista renames Documents and Settings to Users, which is sometimes nice for programs that don't like spaces in paths.

      (Speaking of which, here's a suggestion: make your command line parsing like Unix. Passing the command line, uninterpreted, has some occasional nice benefits, but the drawbacks that parsing is not always done consistently or very predictably.)

    4. Re:Some supporting info by spitzak · · Score: 1

      Actually on Vista they did make "/Users/name" as a "home" directory with all personal stuff under it. This happens to be the same name used by OS/X. They go through some contortions to avoid using the word "home" or put a picture of a house anywhere, which is pretty funny, but otherwise it works.

      I would also like to see:

      - Make \n be the newline seperator by changing their file system so all written files are binary mode at all times. Reading files can continue to strip the \r when in text mode, but they will all quickly disappear and then text mode can be eradicated. Fix notepad (the only program I can find that does not like bare newlines in the file). Programs should also be written to treat \r as whitespace and ignore it at the ends of lines (Linux programs should do this as well). And finally we will be rid of this disgusting mess.

      - Make UTF-8 be the character set to name all files, and have the system treat filenames as strings of arbitrary bytes. Thus the 'a' interface becomes the native one and the current encoding is forced to utf-8. Remove case independence. This will allow identification of files to be done by "the string of bytes is equal" and thus eliminate a lot of bugs in filesystem implementations. For back-compatabilty add whatever is needed so the win32 api can search for possible matches if the first name it tries does not open because it has the wrong case (adding this is also proposed for Linux, apparently).

      - Stop writing "bom" to the start of UTF-8 files. No big deal but it will help with the removal of "text mode" just like the newlines.

      And on the Linux end:

      - Allow a blank directory name, or some other arrangement, so that "//blah" is a legal filename and different from "/blah". This will allow the much nicer Windows unc remote host names to be used.

      - Make FUSE work and be always supported, and have it do the rest of the "//computername" naming. And put all that crap that is in KDE/Gnome libraries into FUSE so that we can do "/http/..." and similar things and access everything.

      - Put the damn fonts into /Library/Fonts/NAMEOFFONT.ttf where the filename is actually something user-friendly.

  81. too early by 93+Escort+Wagon · · Score: 1

    You should've held onto this one for another month or so - it wasn't due to be published until 4/1.

    --
    #DeleteChrome
  82. I dont think it will work... by keirre23hu · · Score: 1

    unless the GUI-less scriptable version of Server 2008 is offered as a free download with the source code released. I believe that when I get hit in the face with a snowball thrown by Bill Gates on July 4th in Miami.

  83. Microsoft already has UNG by Per+Abrahamsen · · Score: 1

    They just spell it Windows Services for UNIX. It includes GCC and many other GNU utilities, no reason to reverse engineer them when you can already redistribute them for free.

    The UNG name is way to cure at too many levels for Microsoft, but congratulation to the author of the fake leak for making it /..

  84. They almost apeal to me by houghi · · Score: 1

    All they need to do is throw in some hookers! And blackjack! In fact, forget obout the OS.

    --
    Don't fight for your country, if your country does not fight for you.
  85. MS and it's SCO source license by Anonymous Coward · · Score: 0

    Let's suppose for a moment that everything pointed out by the article is correct. Now recall that MS has (supposedly) a license to Unix V (for what it's worth) from SCO themselves (thatselves? :-). Now where the fun begins is that this license has a high chance to be declared invalid by the judge next April which could leave MS in a odd position...

    But not that it matters since they now have Novell in their pock^H^H^H^H address book...

    AC

  86. Assimilate by mouko · · Score: 0

    And Steve Jobs just loves his new Zune!

  87. unix switch could actually happen by CranberryKing · · Score: 1

    It would seem a smart move for MS to go the way apple did w/ OSX. Tailor a unix kernel the way they want it and then dress it up to have the olde familiar windows look. Desktop users wouldn't know the difference and admins and power users would rejoice. There would be a bit of grumbling initially since so many admins would have to go out and learn something new, plus get new certs, &c., but ms can make changes of that size and people just put up with it. The only reason I can think of them not doing it, is out of fear that admins who normally only learn useless windows crap would now have 'some' inherent understanding of competing operating systems and 'some' actually useful cross-platform skills instead of just being exclusively invested in ms stuff. Do they still talk about posix in school?

  88. Microsoft Trying To Appeal To Unix Crowd? by MagickalMyst · · Score: 1

    They're officially closing the doors? I guess global warming won't be an issue anymore. Hell just froze over.

    --
    Political correctness is really just herd psychology pushed by insecure people who desperately seek social conformity.
  89. Do you really want that? by Anonymous Coward · · Score: 0

    Ghandi's formula for success, step 5: "They have you assassinated."

    Do you really want to give Microsoft that option?

  90. Great acronym by captainbajoo · · Score: 1

    And the gaming packages will be Direct UNG's Not GNU?

  91. Microsoft appeases the Unix crowd until... by CFBMoo1 · · Score: 1

    ...they step on an age old land mine in a very bad way.

    ANNOUNCING NEW MICROSOFT VeMACS! Thats right! We combined VI and Emacs! ...

    And I heard a sound as if millions of geeks world wide cried out in unison.

    "Nooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo!"

    --
    ~~ Behold the flying cow with a rail gun! ~~
  92. I think this is a good idea by Anonymous Coward · · Score: 0

    One thing that's never been fixed in Linux is that it can't run exe files. I need my exe files and so does everyone else. Hopefully Microsoft Linux will address that.

    I, for one, welcome our new Microsoft overlords.

    1. Re:I think this is a good idea by mozkill · · Score: 1

      lol... thats funny. this is a good way to start a day.

      --

      -- Betting on the survival of the media industry is a serious risk. I advise investing elsewhere.
  93. GNU compatibility? by BPPG · · Score: 1

    it seems Microsoft will be developing a framework that will be completely GNU compatible Richard Stallman might disagree. It's not GNU compatible until it's GPL compatible.
    --
    What's the value of information that you don't know?
  94. Actualy: Satan only appeals to Christians. by krischik · · Score: 1, Offtopic

    Note that Satan is not part of pagan believe, budism, hindusm or the old roman or greek belive - to name a few. He only appeals to monothesis religions as only monothesis religions need an anti-god.

    Martin

    1. Re:Actualy: Satan only appeals to Christians. by chromatic · · Score: 1

      He only appeals to monothesis religions as only monothesis religions need an anti-god.

      Yeah, like Zoroast... oh wait.

  95. Re:Wow: Developers Developers Developers by snakecoder · · Score: 2, Interesting

    You don't really gain anything with the NT kernel. The problem is developers. They want to learn technologies that don't lock them down to one vendor or a "licensed" solution. Because of that chosen career paths follow toolkits that are portable. Java, python,ruby, mysql, apache, etc.. . Automation and installation of these type of tools are best handled through the GNU or GNU like products.

    Even though the developer doesn't have the purchasing power, they do influence. If someone says, I need you to implement XYZ for my business. If the developer says, I need 3 linux boxes, it's done (because it's cheaper too). The purchaser has no power. MS needs to get rid of this factor. Non-techy people who do the buying would feel much more comfortable with windows machines. They need to empower the purchaser to say, look, I'll buy what I want, since you can develop on either.

    Personally, I think it's still a failed strategy. If they see the writing on the wall, they should just port windows GUI part to linux or BSD and move on.

    --
    -Nuke the moon
  96. Re:Wow - Jujitsu by SlowMovingTarget · · Score: 1

    Apparently someone informed Ballmer that Stallman has ninja training (or is at the very least, able to defeat them... maybe he's a pirate?), so Ballmer decided to learn jujitsu...

  97. Focus on freedom by wikinerd · · Score: 1

    That's why we have to focus on freedom as RMS teaches. If the only reason we use GNU is for the technology or nerdiness, at some point someone working against the community will release a product which will encompass the various technical advantages of it, and at that point many of those who use GNU merely for the technology will find themselves enslaved to proprietary software again. We should use GNU because we want to be free, not only for its superior technology. By focusing on freedom, we make sure that no one will ever be able to attack our community.

  98. SFU by Anonymous Coward · · Score: 0

    MS has had services for unix for years. It is evil & rude, but one way to get the Unix tools on win32:

    http://technet.microsoft.com/en-us/interopmigration/bb380242.aspx

  99. It's about developers by thethibs · · Score: 1

    Folk here tend to forget that MS' greatest asset is the millions of third-party developers producing software for Windows. GNU compatibility can only expand that community; more than a few are likely to be attracted by the prospect of tapping into the vast Windows market. MS has nothing to lose.

    Of course, if anyone does anything really good that's useful to more than a handful of people, MS is likely to try to buy them out. But not to worry; FOSS developers abhor the idea of being independently wealthy.

    --
    I'm a Programmer. That's one level above Software Engineer and one level below Engineer.
  100. well by Anonymous Coward · · Score: 0

    theres bsd of course, and then theres any number of unixy stuff that already runs on windows. Open source to the rescue. GNU hates for open source to be available for windows, even when that in itself helps the GNU's cause, thats just how stupid the GNU people are. It took Eric Raymond to finally cut to the heart of the matter and sit RMS on the sidelines once and for all, and when RMS finally got his smelly ass booted from the GCC toolchain project, the world could finally get some work done using open source.

    Even Emacs had to fork to get something useful. Everyone eventually forks away from RMS. Even Linus avoids the GPL 3 and rightfully so.

  101. Slashdot now used for Microsoft PR by Anonymous Coward · · Score: 0

    This entire post is just part of the current Microsoft PR drive which is going full throttle during Feb and March until the final vote on the adoption of OOXML as an ISO standard is complete.

  102. Way faster? by LWATCDR · · Score: 1

    The orginal AT ran at 6Mhz and then was upgraded to 8Mhz soon after it was found that you could just put in a new crystal and get 8Mhz. Your way faster PC was only two to four Mhz faster. Gee that isn't even enough difference to spit at...
    Just something like 25 to 50 percent.
    The good old day.
    I remember swaping out my 8088 for a Nec V20.

    --
    See my blog http://ilovecookes.blogspot.com/ for light hearted technical information.
    1. Re:Way faster? by Delkster · · Score: 1

      The orginal AT ran at 6Mhz and then was upgraded to 8Mhz soon after it was found that you could just put in a new crystal and get 8Mhz. Your way faster PC was only two to four Mhz faster. Gee that isn't even enough difference to spit at... Just something like 25 to 50 percent.

      Well, I'm not an expert, but with more advanced CPU generations you often also get more work done per clock cycle. The clock rate isn't the whole thing.

      Thus says Wikipedia:

      The 80286's performance was more than twice that of its predecessors (the Intel 8086 and Intel 8088) per clock cycle. In fact, the performance increase per clock cycle may be the largest among the generations of x86 processors. Calculation of the more complex addressing modes (such as base+index) had less clock penalty because it was performed by a special circuit in the 286; the 8086, its predecessor, had to perform effective address calculation in the general ALU, taking many cycles. Also, complex mathematical operations (such as MUL/DIV) took fewer clock cycles compared to the 8086.

      Of course it may be that some of the improvements will only give a good performance boost with something bigger than the average real-mode DOS application, but it's still not quite right to look at just the clock rate.

    2. Re:Way faster? by LWATCDR · · Score: 1

      "Well, I'm not an expert, but with more advanced CPU generations you often also get more work done per clock cycle. The clock rate isn't the whole thing."
      Actually it was the difference between a 6Mhz 286 and a 12 Mhz 286 so they where the same cpu generation so all the difference is in clock speed in this case.

      --
      See my blog http://ilovecookes.blogspot.com/ for light hearted technical information.
    3. Re:Way faster? by Delkster · · Score: 1

      Actually it was the difference between a 6Mhz 286 and a 12 Mhz 286

      Ah, that's correct -- it was the "original PC-AT" that was mentioned. My bad.

  103. They can't do this Until SCOUnix is DEAD! by gabrieltss · · Score: 1

    As part of the contract to sell Xenix to SCO Micorsoft had to agree NOT to sell a cometing Unix like operating system as logn as Xenix/SCOUnix was around. So until SCO 's unix (Xenix/SCOUnix) is dead MS cannot compete in the Unix market or SCO could sue Microsoft for Breach of Contract - And you know SCO - they love to sue!

    --
    The Truth is a Virus!!!
  104. Ballmer is a secret Linux fan? by boombasticman · · Score: 1

    Or does he just the necessary things to comply with european law, to no get sued again with 800 million Dollars and to cover it up as new,progressive ways of microsoft?

  105. Microsoft Exchange 2007 by artgeeq · · Score: 1

    I did not find this entirely surprising. Microsoft's new e-mail platform, Exchange 2007, has made all its management operations available in its "Power Shell". It has it's own scripting language and some useful variations on pipes and the ability to incorporate CSV file columns into a script without a whole lot of extra work. It is more like UNIX, but really, I see it as something that they should have done a long time ago, when it would have saved me a lot of C++ programming.

  106. here's how mac owners can profit from this by bliz1985 · · Score: 1
  107. Henry Spencer said it - (and he was right) by toby · · Score: 1
    --
    you had me at #!
  108. Okay, who told Microsoft... by rHBa · · Score: 2, Funny

    ...that GNU stands for Generally No User interface? Come on, own up, who was it?

  109. the GNU by Anonymous Coward · · Score: 0

    refuses to value information and work. Thats essentially their biggest unsolved problem, reconciling their philosophy with the mechanics of a market economy. Copyright as a legal framework allowing careers in the intellectual realm is dismissed by Richard Stallman as according to him, the mere existance of copyright causes "homosexual rape." At some point, more reasonable minds have to prevail. After all, unlike Richard Stallman, some of us have to purchase soap, water, laundry detergent and even the occasional haircut and a shave.

    1. Re:the GNU by James+McGuigan · · Score: 1

      Stallman's ideas do form a system of economics, just like money. Our current money based economics, attempts to optimize the allocation of scarce resources. If there is greater demand than supply, money is a proxy medium that restricts demand and attempts to optimize the distribution of the supply (ie who gets what).

      Turn the question around, if we can find a way to increase the supply to meet and exceed demand, then wealth is maximized by increasing supply and decreasing costs to the point it stimulates extra demand. This is the economics of abundance.

      The market economy should always work to maximize real wealth, and in the case of software, instead of trying to create an artificial scarcity, target the natural scarcities that arise from it.

      Which is more valuable diamonds or air, which would you prefer to live without.

  110. ...M$ XENIX even ran on Apple Lisa. by toby · · Score: 1

    n/t

    --
    you had me at #!
  111. Some interesting benchmarks from back then by Anonymous Coward · · Score: 0

    To put things in perspective, Neil Nelson (of the commercial benchmark fame) did some benchmarks from back then on the original ATT UNIX published by Microport. It put the 286 and 386 as faster than a PDP 11/70, and a little slower than a VAX, on non disk IO related benchmarks.

    That was pretty sweet, considering the price difference, and that an individual could afford the PC. So, yes, the OP's statement that PC's were too weak to run UNIX is completely bogus. Heck, that's one of the reasons why RMS was so eager to first develop gcc on the 386 UNIX systems.

  112. This would be *good* for Linux by foobarbaz · · Score: 1

    This means when developers ask themselves what platform to target, POSIX will be the only option that is well supported on Windows, Mac & *nix.
    Which means many more people will target it.
    Which means it will be easier for users to swap out the POSIX implementation.
    Which means many users will choose the cheapest, stablest one with the best hardware support.
    Which is Linux.

  113. Not interested by PPH · · Score: 1

    Ballmer emphasized that Microsoft's new strategy is to provide users with a complete package I'm not interested in seeing your package, Steve.
    --
    Have gnu, will travel.
  114. Re:Wow - Jujitsu by Anonymous Coward · · Score: 0

    Why, does Stallman also have an anti-chair shield?

  115. Why would I bother by Colin+Smith · · Score: 2, Insightful

    When I can install VMware, and then run a full Linux system to get real work done.

    --
    Deleted
  116. ...then the next morning Steve Jobs calls (again) by toby · · Score: 1

    ...asking what you're going to give him in return for ripping off his plan that brought Apple back into technical leadership. :)

    --
    you had me at #!
  117. Sun Solaris by Anonymous Coward · · Score: 0

    Instead of buying Yahoo!, perhaps MS could buy Sun.

  118. April first already? by slashbart · · Score: 1

    Man I didn't realize it was spring already. Time to grab the climbing gear.

  119. Do they have fork() yet? by Sloppy · · Score: 1

    I know this fancy new API has only been out for 3 or 4 decades, but I guess I'm a bit of a bleeding-edge early-adopter, so I've already written some code that uses fork(). Usually with a pipe.

    --
    As copyright owner of this comment, I authorize everyone to defeat any technological measure which limits access to it.
  120. does that mean by Anonymous Coward · · Score: 0

    that I can compile and run GNU ontop of UNG?

  121. Best defence is attack!!! by Anonymous Coward · · Score: 0

    I think Ubuntu must now respond in similar manner: Gnome/KDE should be mandatory in base installation and getty should be thrown out from debian repository!!!

  122. Appealing to the UNIX crowd? by rnturn · · Score: 1

    Not hardly. Not to me anyway.

    While it's nice that they've made it possible to do a GUI-less installation and there's some sort of scripting available, merely stripping the GUI off of Windows will not necessarily make a Windows box look and feel like a UNIX system. Unless Microsoft includes a fully-featured shell with an OS that can actually support multiple simultaneous users, I'll be taking a pass. Somehow, I suspect that any Windows without a GUI is going to feel much, much more like MS-DOS than UNIX. What's that old phrase? Oh yeah: Been there, done that.

    --
    CUR ALLOC 20195.....5804M
  123. This isn't for the Unix crowd by tclark · · Score: 1

    MS knows that there is no point in trying to appeal to the Unix crowd. Nobody is running Unix/Linux today because they are waiting for MS to release a sufficiently Unixy system.

    What this could do however, is keep some Windows shops from bringing in Unix boxes. The scenario could go like this: A Windows shop hires a Unix/Linux person to build some sort of system they need. This person makes a case for bringing in a couple of Linux boxes. Rather than giving in to this, the Windows shop can set up some Windows servers with this crap and get away with it because it's close enough to Linux

    1. Re:This isn't for the Unix crowd by colinrichardday · · Score: 1

      What this could do however, is keep some Windows shops from bringing in Unix boxes. The scenario could go like this: A Windows shop hires a Unix/Linux person to build some sort of system they need. This person makes a case for bringing in a couple of Linux boxes. Rather than giving in to this, the Windows shop can set up some Windows servers with this crap and get away with it because it's close enough to Linux

      But is it close enough to Linux in price?

    2. Re:This isn't for the Unix crowd by tclark · · Score: 1

      It's not close enough for me, but for a place that is already committed to running Windows that won't matter. I know some people at a nearby Windows shop, and to them the thought of admin'ing Linux systems is terrifying.

    3. Re:This isn't for the Unix crowd by colinrichardday · · Score: 1

      But would they be much better at running a unixified version of MS Windows?

    4. Re:This isn't for the Unix crowd by tclark · · Score: 1

      No - but just the fact that it came from MS would make them feel better.

      Look, in these circumstances we're talking about I would say they should just take the plunge and run Linux. My point is that customers who want to run Windows but find themselves in circumstances where they probably should run Unix/Linux might find this sort of thing appealing.

    5. Re:This isn't for the Unix crowd by colinrichardday · · Score: 1

      Then my question is how many such customers are there in relation to Microsoft's market share? Or are they even numerous with respect to Linux's adoption?

  124. Re:...then the next morning Steve Jobs calls (agai by Ilgaz · · Score: 2, Insightful

    ...asking what you're going to give him in return for ripping off his plan that brought Apple back into technical leadership. :) Apple could dare to do it, MS can't. Read the archive.org pages from OS X 10.0 period, people, their core customers (including professionals) _hated_ OS X. Apple could stand to all those flaming, loss of developers, advanced developers having to re-learn things. It really needs courage.

    There are posts from people who are clearly technical saying "What the hell? Ship MacOS 10 already. This junk doesn't work at all!"

    Apple is a company which can actually warn its _own_ core system parts to keep up with times. Like:
    27.02.2008 13:33:07 com.apple.launchctl.System[2] Notice launchctl: Please convert the following to launchd: /etc/mach_init.d/dashboardadvisoryd.plist

    It is a polite warning for now, in a year or so, it will say very harsh things and later, it will say "I am not loading it". :)

    Can MS do such things? As long as they can't do, they will have these issues. Dark tactics like pushing NBC to show Olympics site to SilverLight having people etc. will keep them in business though.
  125. Xenix by flyingfsck · · Score: 2, Funny

    MS should buy Xenix back from SCO.

    --
    Excuse me, but please get off my Pennisetum Clandestinum, eh!
  126. Re:Wow: Developers Developers Developers by protohiro1 · · Score: 2, Interesting

    This is the best option, port the GUI (vista gui sounds pretty portable actually) to SCO unix (ms can buy it), run old apps in a virtual machine. Done and done.

    --
    Sig removed because it was obnoxious
  127. Bad analogy. by Ayanami+Rei · · Score: 1

    I can think of a few people who worked on Formula 1 teams who would be happy to have an odd but iconic little auto to play around with in the shop. :-D

    --
    THIS THING CAN TURN ON A DIME, MACROSSZERO STYLE ALSO FUCK BETA, ~NYORON
  128. You're describing .NET by rubies · · Score: 1

    But I don't think .NET is working out the way they thought it would. It's basically a portable windows implementation that supposedly should run anywhere. In practice, they forgot the "anywhere" part of the equation. In some ways, it's a pity as .NET is quite nifty in later versions.

  129. Still... by TwoToeWilly · · Score: 1

    No matter how much GNU you sprinkle on a turd it's still a turd.

  130. NT and forking by Myria · · Score: 5, Informative

    Win32 does not have a way to fork a process, but NT does. Passing a NULL image handle to NtCreateProcess() is similar to calling fork(), cloning the memory space as a new process. The NT kernel supports a lot of system calls that are not exposed through Win32, and it's a shame. The NT API is much more elegant and self-consistent than the Win32 wrapper, yet it's the officially undocumented one.

    NT is almost a superset of the features of Linux. There are only a few concepts that don't exist in NT, like signals.

    --
    "Screw Sun, cross-platform will never work. Let's move on and steal the Java language." - Visual J++ Product Manager
  131. NOW WITH by davesays · · Score: 0

    Improved *lemonix*security!

  132. Already seen by starfishsystems · · Score: 1
    I agree with how Mary Jo Foley introduces the story, but not perhaps with the conclusion that it necessarily tilts the playing field. In fact, history tells us that it might backfire on Microsoft.

    After all, it was the same strategy which the commercial Unix vendors started to try out on their customers beginning back in the 1980s, and which continues to this day. The idea was that each variant is recognizably Unix, but with lots of cool proprietary features that your applications should really use to advantage.

    In some sense, this arrangement creates a healthy competitive ecosystem. Bear with me here. You have a common framework which benefits everyone, and then you're free to add value on top of that in a modular way. That much is cool. For example, Sun develops NFS on top of the Unix filesystem model, and other platform vendors turn around and develop their own, more or less interoperable, implementations. More interoperable is better, since anything that encourages the entire space to grow will give every participating vendor a small piece of a growing pie. Modularity and interoperability are preserved, which frees users to choose the best solution for their needs. Technology progresses, and everyone wins.

    So what's wrong with this picture? Well, it invites a tragedy of the commons. It's fine to develop technologies which genuinely compete for market share based on merit. In the physical world, we see that all the time, for example innovations in motor sports eventually finding their way into production vehicles. The trouble comes when some greedy vendor gets the bright idea to use a proprietary extension as a means to sabotage the competition instead of competing on merit.

    Extensions which deliberately break interoperability cause damage to the growing digital commons. The exact tipping point arises when there is little or no real value in innovation, while there is a correspondingly significant loss of compatibility. To the relatively minor degree that the commercial Unix vendors engaged in this practice, they visibly slowed the growth of the entire market segment. By not collaborating more openly, each fought to preserve its own piece of a pie that was no longer growing.

    Despite the ensuing damage to the commons, why is it that Microsoft gets away with its much more radical embrace-and-extend strategy? I'd argue that this is the result only in cases where by doing so it can overwhelm the competition. While it's true that there is not much real innovation, and the pie is therefore not growing nearly as fast as it would under conditions of healthy competition, Microsoft gets essentially all of it. At that point, growth due to adoption gives way to growth of the base population.

    But this situation does not so clearly obtain where free software is concerned. The GPL sees to that. Even if an open source application is ported to Windows, there is nothing to stop it being ported back to some other platform. Yes, in principle it could become so heavily integrated with Windows that portability becomes an issue, but this is exactly what hurt commercial Unix vendors in the long run. Given a choice between two similar applications, one which is locked into a proprietary platform, and one which ports easily between multiple platforms, which of the two is most strategically versatile? Which is more capable of being adapted to a broad variety of new capabilities as they become available on diverse platforms?

    --
    Parity: What to do when the weekend comes.
  133. Heh by Xaero_Vincent · · Score: 1

    Microsoft thinks they can build a fully-compatible clone of the GNU tool chain in just a year with small side developer team? This is obviously a fake rumor, especially considering there is SFU, Cygwin, OpenLina, and CoLinux stuff that tries brings most GNU stuff over to Windows already.

    --
    Regards, Vincent
  134. Re:SFU or STFU? by Anonymous Coward · · Score: 0

    I know SFU stands for "Services for Unix", a Microsoft product.
    But everytime I see SFU I can't help but think it's a misspelling of
    STFU -- Shut The F* Up! We're Microsoft and we know best!

  135. trustworthiness by perlchild · · Score: 1

    When I see an annoucement from Microsoft saying they LOST a customer to a competitor because they gpled code, and they admit they have no choice but to grin and bear it, and hope the customer will change their mind... Then I will believe they are serious about NOT hassling GNU.

    Anything less just leaves them too many options, including legal and anticompetitive pressures.

  136. UNG, which stands for UNG's not GNU by Anonymous Coward · · Score: 0

    yup, i'd buy one,
    to funny to pass up :)

  137. Your free advice: by Anonymous Coward · · Score: 0

    It's not run, run as fast as you can?

  138. OMG by kauttapiste · · Score: 1

    According to the supposedly leaked email, UNG, which stands for UNG's not GNU
    Acronym OMG would be more appropriate..
  139. Possible legal response.... by greginnj · · Score: 1

    If they actually use "UNG's Not GNU" as a slogan, Stallman could sue them for trademark infringement ...

    --
    Read the best of all of Slash: seenonslash.com
  140. UNG: UNG's not feasable by Anonymous Coward · · Score: 0

    Hrmmm probably the dead giveaway is that when a
    proprietary vendor speaks of things that would
    be compatible with GNU, they will always talk
    aboot POSIX compatibility.

    I would however like to point out that I am
    Augustus Pinochet JR, and during the upheavals
    in my father's country I was forced to flee
    hastily, leaving my vast inheritance secreted
    in bank accounts that I may not directly access.

    With your assistance I will be able to
    recover this fortune. You will be greatly rewarded
    for your assistance in this matter.

    Also, I am a graduate engineer with a busy
    professional life and would like to find love and
    happiness on-line. I can send you a recent picture
    but my current construction contract does not
    pay up for another month, and I will require
    a small favor of money for surgery on my emailing
    hand.

    I look forward to meeting you and discussing
    your exciting new sales career, and don't
    worry, as soon as you have recruited 4 sales
    people of your own, you will qualify for tier
    2 and the profit will come rolling in!