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

109 of 468 comments (clear)

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

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

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

    5. 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.
    6. Re:Wow by AKAImBatman · · Score: 5, Insightful

      Long story short: "Embrace, extend, extinguish"

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

    8. 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.
    9. 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....

    10. 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...
    11. 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);
    12. 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.

    13. 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.
    14. 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.

    15. 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
    16. 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.
    17. 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

    18. 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.
    19. 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.
    20. 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
    21. 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.

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

    23. 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
    24. 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.
    25. Re:Wow by melikamp · · Score: 3, Funny

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

    26. 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
    27. 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
    28. 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
    29. 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 ...

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

    31. 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. "
    32. 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
    33. 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.
    34. 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.........
    35. 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.

    36. 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!
    37. 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?

    38. 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.
    39. 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.
    40. 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
    41. 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[...]

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

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

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

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

      ...and of course salty lemonade!

      Gatesorade.

    46. 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
    47. Re:Wow by Anonymous Coward · · Score: 5, Funny

      [n+5] Ubuntu: ???

    48. Re:Wow by debatem1 · · Score: 4, Funny

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

    49. Re:Wow by Dracophile · · Score: 2, Funny
      [n+6] ...

      [n+7] Profit !!!

      --
      Athy, athier, athiest.
    50. Re:Wow by Tsagadai · · Score: 2, Funny

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

    51. 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!
  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 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.

    2. 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.
    3. 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.
    4. 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
    5. 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.

    6. 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.
    7. 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
  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 Abreu · · Score: 2, Funny

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

      --
      No sig for the moment.
    5. 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.
    6. Re:Microsoft: UNG's not GNU by AJWM · · Score: 4, Funny

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

      Figures.

      --
      -- Alastair
  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 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
  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!

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

  8. 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
  9. itsatrap by BoberFett · · Score: 4, Funny

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

  10. 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
  11. 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.

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

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

  15. 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
  16. 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
  17. 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
  18. 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.

  19. 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.
  20. 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.

  21. 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
  22. 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.
  23. 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.
  24. 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.

  25. 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).
  26. 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'.

  27. 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?!
  28. 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.
  29. 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
  30. 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.

  31. 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.
  32. Okay, who told Microsoft... by rHBa · · Score: 2, Funny

    ...that GNU stands for Generally No User interface? Come on, own up, who was it?

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

  34. 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
  35. 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.
  36. Xenix by flyingfsck · · Score: 2, Funny

    MS should buy Xenix back from SCO.

    --
    Excuse me, but please get off my Pennisetum Clandestinum, eh!
  37. 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
  38. 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
  39. 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