Slashdot Mirror


ReactOS Runs On The XBox

KJK::Hyperion writes "ReactOS (the open-source Windows clone) has been ported and successfully runs on the Microsoft XBox (screenshot), thanks to the interest and knowledge base of the XBox Linux project and the work of Gé van Geldorp (HAL and boot loader) and Hervé Poussineau (FATX driver)." (Read on for more.)

KJK::Hyperion continues "This port definitely establishes two facts: the XBox is nothing but a broken PC, and the kernel + HAL design that ReactOS inherited from Windows is sound - all of the changes to the core system necessary for the XBox port (namely, the blacklisting of a buggy PCI device and handling the fixed partition table on the built-in hard disk) were limited to the HAL. This is a first, important step towards better portability, as it has already underlined some shortcomings in our build system.

What the port is lacking is hardware support: especially, ReactOS has no USB support at the moment, so it basically just sits there being pretty, because mouse and keyboard won't work. The network and video cards should be mostly identical to their "real" counterparts, so the Windows drivers for them should work (except the video card, a modified GeForce - it's been established we need some HAL trickery to make the Windows driver load). We wouldn't mind some help :-)

To run ReactOS on the XBox you need our custom version of the Cromwell boot loader (not released yet) and the XBox HAL for for ReactOS."

50 of 289 comments (clear)

  1. Hmm Running a.. by 2mcm · · Score: 4, Funny

    MS windows emulator on a peice of MS hardware .... nice

    1. Re:Hmm Running a.. by thryllkill · · Score: 3, Informative

      -1 Idiot!

      ReactOS is not an emulator. It doesn't even resemble one. Not even a little bit. Its not like Wine which is so darn close to being an emulator it might as well be. It is a totally different piece of software.

      ReactOS is a F/OSS operating system, and here's the catcher, designed to look and run like Windows NT 4.0.

      --

      Note to self: No more arguing with the faithful.

    2. Re:Hmm Running a.. by ottothecow · · Score: 4, Interesting
      See the problem with this news article is that I dont know what it it is really for.

      I mean I know it appears to me that its about ReactOS running on the xbox...but then I realized that the existance of ReactOS is the real news. Something running on the xbox is amazing but...where is the slashdot article for reactos?

      --
      Bottles.
    3. Re:Hmm Running a.. by thryllkill · · Score: 3, Informative
      Well, it works like this.

      I obviously know that Wine is not an emulator since the sentance you cited states that Wine is not an emulator (slightly roundabout yes, but not so terse as to be easily mistaken to mean something else).

      The difference is Wine intercepts Win32 calls and translates them to something the Linux system can understand. However ReactOS doesn't have to intercept these calls to the Win32 API since it is _duplicating_ them directly.

      --

      Note to self: No more arguing with the faithful.

    4. Re:Hmm Running a.. by WJMoore · · Score: 5, Informative
      ...where is the slashdot article for reactos?

      That would be here:
      ReactOS 0.2.3 Released
      Steven Edwards On The Future Of ReactOS And Wine

    5. Re:Hmm Running a.. by AstroDrabb · · Score: 5, Informative
      No. Wine doesn't "intercept" anything. It is not like WINE has some _HUGE_ switch statement where it just "intercepts" Win32 calls and translates those to Linux calls. WINE has _rewritten_ the WIN32 API (well, a lot of it so far). For example, I write a program with an API to control it with functions like:
      sendMessage(int, int)
      beep(int)
      sleep(int)
      phoneHome(int)
      Now, you come along and rewrite those some functions for your program with the same "function signatures" (which just means the same function names, parameters and return types). Your not emulating/intercepting me, you have _totally_ rewritten what I did on your own. Granted, what I did above was very samll and the Win32 API is HUGE. That is why it has taken the WINE team (the core group is pretty small) a long time to get a large part of the WIN32 API rewritten to the Linux platform. For example there is a Win32 API called CreateWindow. That _same_ function had to be recreated under WINE in Linux. Under Win32, it creates a window with the Win32 API. Under Linux, it takse the same parameters and creates a window using the methods that the Wine team created.

      You are correct in the sense that the WINE team has tried to "emulate" the look and feel of the Win32 API. That is why a Win app under WINE often looks the same. They (WINE) have tried to make the windows looks just like a window in Win32. However, at the end of the day, WINE is still not emulating or "intercepting" anyting. They are recreating API's and copying a look-n-feel.

      --
      If Tyranny and Oppression come to this land,
      it will be in the guise of fighting a foreign enemy. -James Madison
    6. Re:Hmm Running a.. by xeno314 · · Score: 4, Insightful
      Aren't we being a slightly anal about what is and is not an emulator? Go look at The American Heritage Dictionary of the English Language, Fourth Edition.

      emulate
      To imitate the function of (another system), as by modifications to hardware or software that allow the imitating system to accept the same data, execute the same programs, and achieve the same results as the imitated system. Isn't this what ReactOS does?

  2. Yeah... by bccomm · · Score: 5, Funny

    but will it run Linux?

    Oh wait...

  3. ReactOS? by IO+ERROR · · Score: 3, Interesting
    ReactOS is intended to be a clean, open source reimplementation of Microsoft Windows NT 4.0.

    I'd never heard of ReactOS before this posting, and so I checked it out. I'm impressed by what they've done so far, but not the seven years it took them to do it. It's still VERY early pre-alpha software. Maybe now that all the basic pieces are in place it will pick up speed, but I suspect it will have the same trouble WINE runs into: it's chasing a moving target, and it's way behind. WINE, at least, decided to implement newer APIs found in Windows 2000 and XP. ReactOS has not. So even when they hit a 1.0 or stable release, they're going to be so far behind that not that much Windows software will run on it.

    --
    How am I supposed to fit a pithy, relevant quote into 120 characters?
    1. Re:ReactOS? by IO+ERROR · · Score: 4, Insightful
      how is NT 4.0 a "moving target?

      The passage of time makes it a moving target. It's moving further and further into the software tarpits of the past, as more and more new software simply doesn't work on NT 4.0.

      --
      How am I supposed to fit a pithy, relevant quote into 120 characters?
    2. Re:ReactOS? by runderwo · · Score: 4, Interesting

      Yes, they will face many of the same challenges the WINE project does, which is why WINE and ReactOS liberally share patches. Why does everyone think they are just some peripheral group reinventing the wheel for no particular reason? The ReactOS project enjoys a symbiotic reliationship with WINE in which both projects benefit from each other's advances.

    3. Re:ReactOS? by KJKHyperion · · Score: 5, Informative

      ReactOS is Wine - everything Wine has, ReactOS has too, except the Linux-specific parts (that, in ReactOS, will be handled by drivers). And ReactOS does implement recent APIs, we're no way stuck with Windows NT 4 compatibility, in fact our current baseline is more like Windows 2000 (especially true for the kernel). Finally, we won't just get up one day and declare 1.0: it will be 1.0 when compatibility reaches the intended milestone for 1.0 (namely, good enough to replace somewhere between Windows NT 4 Workstation and Windows 2000 Professional)

      --

      Make a difference - use Windows! (open source clone of Windows NT)

    4. Re:ReactOS? by k98sven · · Score: 5, Insightful

      I'm impressed by what they've done so far, but not the seven years it took them to do it.

      Well, this is a bit symptomatic of a lot of OSS projects, they start out with a grand vision and end up planning and then re-planning and throwing out code and never really get off the ground. Some die and stay dead, some get picked up by a group of enthusiasts with a more down-to-earth approach of 'Getting something working now, improvements later.' and the project takes off.
      (Case study: See Linux vs. GNU Hurd)

      I believe this is pretty much what happened with ReactOS (I'm not a ReactOS developer), so I wouldn't hold it against the current crowd too much.

      I suspect it will have the same trouble WINE runs into: it's chasing a moving target, and it's way behind.

      Ah, the old catch-up argument. It's a valid argument, but it's not as important for API:s as it is for, say, file formats.
      With the MS Word file format, Microsoft can tweak and alter that all they want, because it's not publicly documented, and they're not that interested in having compatibility with anything other than MS own products. Backwards compatibility isn't important. Heck, they're happy to break it and create incentive for people to buy the new versions. That's a hard act to follow.

      With API:s, things are quite different though. Firstly, the '80-20 rule of features' pretty much applies. Most programs don't use the entire API, but a rather small subset.

      Secondly, API:s rarely break backwards compatibility. That would break all existing third-party apps and make it difficult for people to migrate. The exact opposite situation to the previous one. So MS bends over backwards to make stuff backwards compatible. Windows 3.0 apps still run on XP.

      The APIs are also (relatively) well documented. Sure, there's a lot of undocumented functionality, but most of that is also unused. The implementer has access to the same information as most application-developers.

      Another point of difference is that you don't have to be super-fast in implementing new API:s.
      The day a new Word version hits the street, people will be asking 'Why doesn't this work with OpenOffice?'.

      Not as true for APIs. While we all like the latest and greatest, professional developers don't rewrite their programs to use the latest APIs 'just for the heck of it'. There has to be good reason. In fact, you want to avoid using the latest APIs as far as practical and economical, because otherwise, you're going to be shutting-out potential customers running the old OS version.
      (There are plenty of brand-new apps released today which run on Win98, or Win95 even.)

    5. Re:ReactOS? by AstroDrabb · · Score: 5, Insightful
      I'm impressed by what they've done so far, but not the seven years it took them to do it
      Your kidding right? How many OS's have you developed yourself? None? I thought so. MS spent millions and took _many_ years to develop the NT OS, and _many_ more years to get it stable (NT 4 sucked for stability, 2k and 2003 still crash, though not as much as NT 4)

      Here is a group of OSS developers working in their _spare_ time and you say your not impressed? Dude, your an idiot. This small group has done what MS did in _half_ the time. I am _very_ impressed.

      I guess your expecting a small group of developers to duplicate what a bunch of developers and tons of cash did over _years_ funded by the _largest_ software company in the world?

      --
      If Tyranny and Oppression come to this land,
      it will be in the guise of fighting a foreign enemy. -James Madison
    6. Re:ReactOS? by k98sven · · Score: 5, Informative

      Oh please. I didn't say "Windows is backwards compatible with every single app".

      I said that Microsoft tries hard to keep backwards-compatibility.

      But don't take my word for it, I don't work for them. Read Raymond Chen's various blog articles on the subject. He is one of the poor souls at MS who worked his butt off to try and keep backwards-compatibility.

    7. Re:ReactOS? by evilviper · · Score: 4, Interesting
      it's chasing a moving target, and it's way behind.

      I must disagree there. NT4, despite lacking support for a few things, is still a modern OS, and highly usable. With the hundreds and hundreds of programs I use, the only one that I can recall not working on NT4 is MPC, and that's not a big problem.

      Namely, NT4 is lacking in USB support (oddly enough, I find NT4's lack of USB support better than Windows 98's USB support), only has DirectX6, and doesn't support FAT32 without a 3rd-party add-on. Those limitations can all be fixed easily, making an NT4 clone every bit as useful as, say, XP.

      In addition, they are in a very different place than WINE. If programming for ReactOS is vagely similar to recent Windows, and it has just a few thousand users, it would become a supported platform. There are probably less Windows 95 users out there than that, yet just about all modern Windows programs still run on 95. A small bit of extra effort to reach a few thousand more people is a great trade-off for most.

      Personally, I'd love to see it improve, as Windows is a constant headache for me. Having an Open Source version would make it far easier to solve problems (like why those dammed ATI drivers won't work).
      --
      Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
    8. Re:ReactOS? by KJKHyperion · · Score: 5, Informative
      I believe this is pretty much what happened with ReactOS (I'm not a ReactOS developer), so I wouldn't hold it against the current crowd too much.

      ReactOS was born in dark, barbaric times. In 1997, your most realistic option to build PE executables with GCC on Windows was DJGPP, the port of GCC to a DOS extender, because MinGW didn't exist yet. I have had the dubious privilege of trying that - when I joined the project, DJGPP was no longer required for the main tree, but the boot loader still had to be built with it.

      Also, the "don't design, code!" attitude worked in the beginning, to get anything done and avoid the mistake of the ReactOS father, FreeWin95, forever stuck in the design phase, but it backfired when real stuff began to run. It just doesn't work when cloning a system as firmly established as Windows - you can't always attack the problems by implementing function after function, many times you need a good overhead view. The short of it is that we have some embarassingly bad code in the kernel.

      --

      Make a difference - use Windows! (open source clone of Windows NT)

    9. Re:ReactOS? by gnarlin · · Score: 5, Funny

      The short of it is that we have some embarassingly bad code in the kernel.

      So that means you are really making some headway in duplicating windows properly ;-)

      --
      A bad analogy is like a leaky screwdriver.
    10. Re:ReactOS? by laughingcoyote · · Score: 3, Insightful

      Pardon me for rudeness...but are you stupid?

      I would say that seven years worth of people duplicating a massive, multimillion dollar development project in their SPARE TIME is VERY impressive. If it works, more power to them, and even if it does not, I will certainly say it was an excellent attempt. Don't you remember when Linux was thought of as a "silly" OS?

      I'm also not sure how NT4 is a "moving target", MS stopped development on that years ago. Please don't knock other people's work until you do something more worthwhile yourself. If you have, feel free to submit your own articles...

      And finally, even if this particular project doesn't pan out, the project is opensource, and the implementations of the "base" API's and similar could easily be used to jumpstart an opensource reimplementation of a newer Windows version. So all in all...these people are doing something quite worthwhile, and I for one think they're due credit, not bullshit.

      --
      To fight the war on terror, stop being afraid.
    11. Re:ReactOS? by lav-chan · · Score: 3, Insightful

      Very mature. If you lose an argument, just call names. I love it! Nothing like an immature baby trying to make a _poor_ point on /. and then calling names!

      OK, um....

      (a) If you're newfangled enough to figure out the bold tags, you should be able to figure out the italic ones too. <i> isn't so much harder to do than <b>.

      (b) You called him an idiot first, what the Hell.

  4. Soooo..... by dnaboy · · Score: 4, Funny
    They got an embedded windows box to run a windows clone...

    This is all getting a little silly.

  5. Cool, but... by sH4RD · · Score: 4, Insightful

    I see this more as a proof of the power of ReactOS than the XBox. If it is a crippled PC it should be easy to port to (note: I have not tried, so I don't really know, but it should not be *that* hard), however porting an OS (specifically a similar-to-Windows one) so easily is a great sign for ReactOS. Makes me even more interested in what this could become (stable, embedded, Windows x86 EXE compatable, OSes anyone?).

    --
    WASTE - The Secure P2P
  6. Next question: by Anonymous Coward · · Score: 5, Funny

    When will they get ReactOS working on a PC?

  7. Reaction? by methangel · · Score: 3, Interesting

    Yeah, I think ReactOS will make Microsoft "react" since it's a Windows clone. You are the weakest link, goodbye.

    I love it how the geeks will uproar about MS taking measures to prevent their console from doing things that it shouldn't ... Of course if Apple circumvents (Real) ... it's their RIGHT!

    1. Re:Reaction? by jerw134 · · Score: 4, Insightful

      Microsoft sells the Xbox at a loss, and expects to make up for that by selling games. If people aren't using their Xbox for games, or are pirating games instead of buying them, then Microsoft doesn't make back their money. That's why they care.

  8. Minesweeper by believekevin · · Score: 5, Funny

    Does Minesweeper support Xbox Live?

    1. Re:Minesweeper by Ingolfke · · Score: 3, Funny

      We could rid the world of mines in meer minutes. Ee-gads Batman!

  9. Yeah... by Anonymous Coward · · Score: 5, Funny

    My ISP won't talk to me after lodging a support call for helping gettting ADSL hooked up to a WinXP install running under VMWare under Linux on my XBox.

  10. How about porting Windows? by enosys · · Score: 3, Interesting

    So could you theoretically build a new HAL for XP and get it to work on an XBox? Or for that matter any weird x86 architecture? I suppose it may be hard to do this without using the source, but it's not impossible. It'd be an interesting project.

  11. Re:Cheap by dnaboy · · Score: 4, Funny
    Actually, with a $100 AOL rebate* and a $100 MSN rebate**, this thing's free...

    * Requires 8 year subscription to AOL at $23.95 per month

    ** Requires 12 year subscription to MSN at 21.95 per month

  12. You're missing the point by Gilesx · · Score: 3, Insightful

    The point with ReactOS isn't to keep up with the latest and greatest. ReactOS with full NT4 compatibility will have a function in many offfices, that still have a huge NT4 presence, but are find that they are coming to the end of their support life cycle with Microsoft. ReactOS would squeeze a little more life out of their systems, and would also provide an easier upgrade path to a straight Linux system than simply going Windows --> Linux.

    Home users are a different breed to corporate users, and tend to want the latest version of an OS. Of course, ReactOS is in no position to compete with XP, but wouldn't we be hoping that rather than chosing Windows XP, home users will eventually be installing one of the multitude of distros available?

    --
    Sunday you're Thinking Different, Monday you're a huge tool, paying too much and waiting to think like everyone else.
  13. RTF...-- hey wait, you just quoted the F'nA!!! by xtermin8 · · Score: 3, Insightful

    NT 4.0 is not a "moving target." The project has no plans to implement the features of 2k and XP. I've seen a lot of "RTFA" cases, but this post is the first I've seen where the writer has neglected to read the quote he's included in his own post.

  14. Waiting for the XBOX to run Longhorn by Ingolfke · · Score: 4, Funny

    When XBOX runs Longhorn, then I'll think about switching.

  15. running? by focitrixilous+P · · Score: 4, Funny
    What the port is lacking is hardware support: especially, ReactOS has no USB support at the moment, so it basically just sits there being pretty, because mouse and keyboard won't work.

    This must be some new meaning of 'running' an OS I was unaware of.

    Anyone want a 'running' Mac SE 30 with ethernet card? Drop me an email.

    --
    SAILING MISHAP
  16. Re:Uh huh. by Erwos · · Score: 5, Insightful

    That's like saying an AthlonXP emulates a Pentium4. It's reimplementing something, not emulating it.

    -Erwos

    --
    Plausible conjecture should not be misrepresented as proof positive.
  17. Re:React OS is... by Markos · · Score: 4, Insightful

    The same could be said for Linux when it was in its infancy.

    I commend the group working on ReactOS for the job they've done so far. Unlike others, they seem to be progessing nicely and arent stuck in the limbo between design and coding which so many projects seem to suffer from these days.

    Theres a growing amount of users who have older hardware that struggles on 2k, XP and will struggle even more so with Longhorn. If ReactOS can provide a relatively stable Windows compatable environment, IMO they will make serious inroads.

  18. Re:Uh huh. by Piquan · · Score: 4, Informative

    So what you're saying is it emulates an API. Right?

    No more than my car emulates a mode of transportation employing paved streets, or Mentat's MPS emulates SVR4 STREAMS (or even BSD sockets).

    Wine implements the API.

  19. Re:USB Driver? by hattig · · Score: 3, Informative

    USB controller is in the nVidia southbridge, then there is a 4 port USB hub chip connecting to the USB ports that are gameports.

  20. What a horrible idea by theantix · · Score: 3, Interesting

    Why would people spend their free time on a project to re-implement Windows? Their answer from their FAQ:

    "Reliability, subsystems, filesystem drivers, services and the registry
    are all good concepts which are implemented well in the NT kernel.
    Not everything is perfect, but without access to the source code, we can't fix it, so we're choose to clone it."

    WTF? I can understand WINE, if you have a legacy binary application that is windows-only. But poorly re-implementing windows? They will probably *never* get full compatibility with windows, so it will always be an inferior solution -- some "fix". I'm tempted to think these ReactOS people are clinically insane.

    If a ReactOS dev is listening here, explain this to me: why don't you just create drop-in replacement .dlls for mswindows in cases where you think it's broken? This is something you'd have to write in the first place if you're going to reimplement the whole goddamn system, and seems a lot more productive. Alternatively, why not work productively to improve Linux or a BSD variant so it has the supposed "advantages" that you find in mswindows?

    --
    501 Not Implemented
    1. Re:What a horrible idea by absurdist · · Score: 4, Insightful

      If you can't see the value of a free, open source OS that will run the abundance of Windows executables, then I guess there's nothing more that needs to be said.

    2. Re:What a horrible idea by mmusson · · Score: 4, Insightful

      So by that logic you are also against Linux since there were free Unix implementations already available?

      --
      SYS 49152
    3. Re:What a horrible idea by KJKHyperion · · Score: 5, Informative

      Windows applications are not legacy. Linux is not a Windows replacement. BSD neither. We are totally, absolutely, positively sure: it's a Windows clone we want. We don't all secretly dream running Linux, and in fact several of us must fight the puke back when forced to deal with it (except KDE. I like KDE. I'd like it even more if it ran under Windows). Some have had their weird ideas phase, but you get over it soon.

      We're tired of hearing about this every damn time, and I'm not speaking personally here. Even the Linux users among the developers are fed up with that argument. It doesn't make sense, ReactOS is real, is here, today: deal with it already, because at the point it is now, it's not just going to go away.

      Your technical argument doesn't make sense, either. One of such DLLs you talk of is called "the Windows kernel", and it's a pretty big piece of software (a 2+ MB binary, for the record). And it has a private API to talk to the HAL. And one to the authentication service. And another to the event logging service. And yet another to the PNP service. Each of these services can be queried by applications with an undocumented RPC protocol. It's a recurring theme in Windows: most APIs have two sides with unknown grounds in the middle, and many DLLs expose multiple client sides. Picture the graph in your mind. No, more arcs. No, way more than that. Yes, you're getting closer, and yes, that arc does go twice the same way. Etc.

      One has to wonder why couldn't Wine just provide a loader for Windows executables and let the (air quotes) D-L-L-s (air quotes) do the rest, if your statement had even the slightest trace of truth in it.

      Please don't trivialize our work, which is something you apparently don't fathom in the slightest

      --

      Make a difference - use Windows! (open source clone of Windows NT)

    4. Re:What a horrible idea by ebooher · · Score: 4, Insightful

      theantix wrote:

      but that doesn't change the fact that your work is perhaps the very essence of trivial. **You are building something that has already been built.** To me it seems like you are doing the equivilent of building a new version of the leaning tower of Pisa that isn't leaning

      Well, I have to step in here and fire up my rant machine. Everyone else is having a row, I want one too. So here goes: It's time for my Bullshit Theory of the Day!

      You say that the team is building something that has already been built. You claim that they are attempting to reinvent a wheel that is no longer useful. I must call bullshit on this whole diatribe. This isn't the wheel. I know how to build a wheel. More importantly I'm pretty sure you know how to build a wheel. My little brother knows how to build a wheel. With so many people building wheels we have to stop using this analogy for open source implementation.

      I say this is building a Pyramid. Do you know how to build a Pyramid? I know I sure don't, and they are one of the wonders of the world. The Great Pyramid was built within the lifetime of one man. But the secrets that allowed them to build the Pyramid died with the master builder. (Oh, and let's nip this before it starts. The workers were not slaves. They were freemen as evidenced by "signatures" around the pyramid structure.)

      The secrets of the source of the Win32 API are held by one man. He (and his team) know exactly how to push this block on that level and move it hundreds of feet into the air to start the next level of the Pyramid being built. I don't know how to move that block, and the ReactOS guys don't know how to move that block either. But they are trying to learn.

      For hundreds of years man has attempted to relearn knowledge that was lost through the sands of time. Hundreds have tried to decode exactly how this block moved to be placed on top of that one after being rough cut by hand from a quarry at the base. Is this worthless? Is the knowledge of how a structure was designed, fabricated, built, and weathered as such that it has lasted hundreds of years useless information?

      Rome had aquaducts, plumbing, roads. All structures designed in the minds of men and built on the backs of men. But which required decades, if not centuries, to recreate elsewhere in the world after the fall of the Roman Empire. Those structures too are still standing today.

      My house, however, built only a year and a half ago, is not. Creaky boards, swaying walls, truly horrifing things happening. I, Sir, want an aquaduct. I want a Pyramid, a Castle. I want a home I know is going to stand for centuries. Not a measely couple of decades.

      This is no different than what is happening here. There is no amount of information which is not knowledge. There is no knowledge that is not power. Power is what mankind strives to achieve. The very fact that the secrets of how to move those blocks into the air to get Word to run belong to so few is why so many are working so hard to recreate the information needed to perform these tasks.

      It's the *why*. Why does x+y=z? Why does yellow + blue = green? Why is the sky blue? This isn't about recreating an OS that is dying if not dead just so they can have a perfectly dead OS. This is not about wanting to run an old copy of Word 2.0 they happen to have lying around. This is about the why of the power.

      It's also the exact same why that created Linux.

      Why is it that whenever someone with so little resources accomplishes so much there are always millions waiting to tear them down and tell them to go to hell? You don't want to install ReactOS to run Word 2.0 because you've already pirated XP SP2? Fine! Don't download it, don't install it, don't run it. But as a member of mankind at least understand that we will always rebuild what has already been built. Always.

      Cars, Trains, Buildings, Waterways, Boats, Spaceships, and yes even the leaning t

      --
      "Genius may shine aloof and alone, like a star, but goodness is social, and it takes two men and God to make a Brother."
  21. Comment removed by account_deleted · · Score: 5, Informative

    Comment removed based on user account deletion

  22. Re:React OS is... by Planesdragon · · Score: 4, Informative

    You're kidding, right?

    A usable, workable microkernal that snuggly runds Win32 by design, and you're suggesting they give up and poke and Linux some more?

    And let's not forget that they have essentially "joined WINE" -- both projects apparantly share rather liberally between each other.

  23. Oh Great... by durtbag · · Score: 3, Funny
    Once again the mod community pulls through in their quest to make a Microsoft product less stable.

    Just kidding, good work all.

    --
    itadakimasu
  24. New joypad soon by zenst · · Score: 3, Informative

    I look forward to the modded controllers with CTRL/ALT/DEL. Kick, block shoot and reboot.

    I'd like to see Plan-9 for XBOX, now that would be some funky fun to be had.

  25. ReactOS rules! by 808140 · · Score: 5, Insightful

    Ok, first off: I hate Windows. I hate its stupid UI, its ugly fonts, and the company that produces it. I jumped ship and switched to Linux before Windows 95 came out. I mean, I hate it, and I would never run an OS that even superficially resembles it. That includes ReactOS.

    But.

    ReactOS is a perfect example of the OSS spirit. Lots of folks here have been making comments along the lines of "You ought to be working on Linux" or "You ought to be working on WINE" or the like. It surprises me that a site as devoted to the OSS concept would parrot such ridiculous drivel.

    It's possible that Linux-based OSS has gotten so popular that we now have lusers of our own. You know what makes a hacker? Someone who codes because he (or she) loves to code. Loves, you know? Not to be productive. Not because they want to change the world. These things may be true of some hackers, but these things alone do not a hacker make.

    There was a time when people here respected this. When the majority of Slashdotters were active hackers themselves. Don't be fooled by my high UID -- I remember those times. We wrote software because we loved to. I rather suspect that lots of folks would have told Tim Berners Lee that the web was a dead end idea, or that at the very least it would never be useful. Lots of people have belittled Linux over the years using the same flaccid arguments.

    You know GNU? The group that started it all? What was their goal? To produce a free UNIX. Yes, a clone. You understand this? In those days, there was no Windows (1984). A hacker at MIT decided that he wasn't going to put up with this proprietary software bullshit and he said, "I'm going to make a free UNIX clone." And people laughed at him. They said it would never happen. But it did, didn't it? I'm typing this from my Debian GNU/Linux workstation. People like Stallman and Torvalds made that happen. All they wanted was a free OS to replace the one they used at school/work and loved.

    Now, most of us (myself included) dislike Windows. We dislike Microsoft (but then, I'm sure RMS disliked IBM, Sun and HP, too). But aren't you missing the point? Some guys like Windows. They like its interface. But like RMS, they demand freedom. Freedom, you know? In this world of the business-friendly "Open Source" movement, people seem to have forgotten this concept, the concept that motivated hackers to create a free UNIX in the first place. It's easy to forget about uncomfortable, uncomprimising ideals like Freedom. But people like Richard Stallman and Theo De Raadt -- and even Linus -- for all their failings -- are motivated by this ideal.

    ReactOS is simply another GNU project. But this time, the hackers that have undertaken it aren't fond of the UNIX way. So what? They like an OS I don't like, but so the fuck what? Look at what they're doing. They're creating a free replacement. Free. As in Freedom, you know. So people everywhere that like Windows can use Free Software.

    As difficult as it is for me, a unix-geek, to believe, some people don't like UNIX. Some people prefer VMS (I actually quite like VMS and wouldn't mind a FreeVMS). Some people prefer Windows. BeOS. Whatever.

    People seem to think that if these guys weren't working on ReactOS, they'd be working on Linux, or BSD, or the HURD, or whatever pet project you have. But that's not how it works. Developers scratch and itch, you know? Because they're coding for love, because they like to code. Not for you. Not so that you can sit on your fat ass and benefit from their work. They do it for themselves, in an ultimately selfish way, to scratch their personal itches. And if you benefit, that's great.

    Lusers are people that think FS devs are out to serve them. But guess what: just because you discovered Linux last week and found out that you can run on your machine and get work done doesn't mean that its a "product" that is being "produced" for you to consume. It's a labour of love, made by

  26. The idiot comment by jesterzog · · Score: 3, Insightful

    -1 Idiot!

    Woah, control yourself. I actually found it amusing (albeit misleading), despite your comment.

    Why is it so accepted to call someone an idiot just because they make a mistake? There's such a thing as constructive criticism, and it's possible to comment on something without acting like a jerk while doing it.

    If the earlier poster was deliberately provoking it or if you were a regular troll then I could understand it and ignore it, but you've gone out of your way to also correct what was said. Slashdot's great for conversation with tech-minded people and that's what keeps me here, but all that fostering this attitude does is to make potentially interesting slashdot conversation appear even more childish and immature to anyone who reads it.

    Yeah I know. This is slashdot. Whatever.

  27. Yes, but by RAMMS+EIN · · Score: 3, Insightful

    Will it run XLiveCD?

    Seriously, ReactOS has been making some amazing progress lately. I don't know why anyone would want to use it (other than geek factor), but it shows that even Microsoft's crown jewels aren't safe from assimilation.

    --
    Please correct me if I got my facts wrong.