Slashdot Mirror


OSDL Denies Rewriting Kernel

yootje writes "Although there were rumours saying that OSDL writes a version of the Linux kernel that doesn't infringe patents (an argument that was used by Microsoft), OSDL denies this: 'OSDL officials have said that the report was not accurate, and that while Beaverton is putting $1.2m into economic development around open source software, this is not connected to rewriting the Linux kernel.'"

237 comments

  1. SCO by wpiman · · Score: 0, Redundant
    So will the rewrite scare of people that SCO is persuing as well?

    1. Re:SCO by Anonymous Coward · · Score: 0

      The mods did not get the joke...

    2. Re:SCO by Anonymous Coward · · Score: 0

      The mods did not get the joke...

      Me neither. I think you may have imagined it.

  2. That's a shame by stratjakt · · Score: 0, Troll

    They should rewrite the kernel.

    IP issues aside, it's > 10 years old, when code gets that old, it's due for a good overhaul, if nothing else.

    Don't kid yourself into thinking the kernel is without it's flaws.

    --
    I don't need no instructions to know how to rock!!!!
    1. Re:That's a shame by drivinghighway61 · · Score: 5, Insightful

      Yes, it's 10 years old. Rewrite it and get rid of 10 years worth of testing, 10 years worth of bug fixes, 10 years worth of great security. This is exactly what Microsoft is running into with Longhorn. Buggy as Windows may be sometimes, rewriting the Linux kernel would put it behind Windows.

    2. Re:That's a shame by danheskett · · Score: 5, Insightful

      10 years isn't old. It's mature.

      The Linux kernel is just getting to the point where it doesn't completely suck ass.

      This isn't to disparage where things are at, going, or have been. But you dont just scrap something like the kernel just because its a decade or more old.

      That's how you get versions that are "newer" with half the features.

      Kernels are time expensive and iterative. You just can't go from nothing to a working production kernel in one or a few releases. It's a big job to do it right.

      The linux kernel is finally to a place where you have a good mix of micro and monolithic design principles (not a lot of bloated message passing, loadable modules). It's finally got some really decent SMP, and the VM issues are finally being addressed.

    3. Re:That's a shame by avarus · · Score: 1, Funny

      Indeed - code rot is a well known phenomenon.

      If the kernel is not re-written soon, it will start slowing down and maybe break altogether!

      TIM

    4. Re:That's a shame by Anonymous Coward · · Score: 1, Funny

      Zoidberg: Give it to me straight, Professor.
      Is it fin rot? It's fin rot, isn't it? Tell me it's not fin rot! ...

    5. Re:That's a shame by A+beautiful+mind · · Score: 5, Informative

      That's something made me laugh this week. NO, the code isn't 10 years old. One of the core developers said this week that the kernel is getting 4mb of patches every week. Now, lets compute a bit:

      # du -hs /usr/src/linux-2.6.7
      290M linux-2.6.7
      # bc
      (...snip...)
      290/4
      72


      This would assume that in a little bit over 1 year, the kernel is totally replaced. I know its logically flawed, but it means in my interpretation that there is no obsolete code in the kernel that would be >10 years old, or maybe with a few exceptions. I think it's safe to assume that most parts of the kernel aren't older than 2-3 years. Your logic is flawed.

      Personally i think the kernel is perfectly good without a rewrite.

      Legal issues shouldn't be a consideration neither, since SCO-code in the linux kernel is something in one class with Santa Claus. Linus stated on multiple occasions that he doesn't believe sco code could be in the kernel. I don't have evidence who generates those rumours, but i got a hunch it's from the SCO,Microsoft side of the barricade.

      --
      It takes a man to suffer ignorance and smile
      Be yourself no matter what they say
    6. Re:That's a shame by stratjakt · · Score: 4, Interesting

      There are large sections of code that havent been touched since 1.x releases. Linux frankly runs for shit on anything other than x86, despite all the claims of all the different systems it runs on. Too much PC specific cruft.

      "Rewrite", to a programmer, doesn't mean to throw everything out and start from scratch, either. It means rethink some the design. Reevaluate why feature X was done the way it was, and if that's stillt he best way to do it. Make sure it's still relevant for modern hardware, and make sure it will still be relevant for tomorrows hardware.

      MSFT is doing this with Longhorn. The hardware evolves, why shouldn't the software that runs on it?

      --
      I don't need no instructions to know how to rock!!!!
    7. Re:That's a shame by Anonymous Coward · · Score: 0
      MSFT is doing this with Longhorn. The hardware evolves, why shouldn't the software that runs on it?

      Duh, GUIs are teh sux0r in l33t world!

    8. Re:That's a shame by robertjw · · Score: 0, Troll

      Why does it NEED to run on anything other than x86? Sure, it's cool to run it on a Mac, but for practicality why not run OSX? It's tweaked for the platform, and from what I've heard doesn't run like shit.

      If IBM, SUN, etc.. wants their platform supported let them donate the time/money/resources to fix where the failures are.

    9. Re:That's a shame by A+beautiful+mind · · Score: 3, Informative

      "Rewrite", to a programmer, doesn't mean to throw everything out and start from scratch, either. It means rethink some the design. Reevaluate why feature X was done the way it was, and if that's stillt he best way to do it. Make sure it's still relevant for modern hardware, and make sure it will still be relevant for tomorrows hardware.
      MSFT is doing this with Longhorn. The hardware evolves, why shouldn't the software that runs on it?


      ...And linux is doing this with odd releases(2.1, 2.3, 2.5) and now with -mm while keeping 2.6 around. Did you ever look at LKML? You could see tons of discussions about what and how should be done.

      --
      It takes a man to suffer ignorance and smile
      Be yourself no matter what they say
    10. Re:That's a shame by Anonymous Coward · · Score: 0

      Shut up. You've just shown yourself to have no fucking clue about linux.

      Ever heard of a little thing called embedded linux? It happens to be linux' commercial future. From TiVo's to Zaurus' and beyond.

    11. Re:That's a shame by ignorant_newbie · · Score: 1, Interesting
      Linux frankly runs for shit on anything other
      than x86, despite all the claims of all the
      different systems it runs on



      really? got any numbers to support that, oh great fudmeister?

      I dont' have any numbers to support my rebuttal either, but I do have 4 non intel systems ( 2 ppc and 2 ultrasparc ) running perceptably faster than equivalently clocked intel machines

    12. Re:That's a shame by LWATCDR · · Score: 1

      Rewrites are so 1990's..
      Really it would be wasteful to rewrite from scratch far better to keep fixing and improving what is there.
      If you want a more modern OS may I suggest Hurd?

      --
      See my blog http://ilovecookes.blogspot.com/ for light hearted technical information.
    13. Re:That's a shame by Lord+Kano · · Score: 1

      Kind of like if you shake hands with someone today, and then again in 6 months. You'll still be you, he'll still be him, but none of the cells in your hands will be the same. From one perspective, four different hands would have been involved.

      LK

      --
      "Hi. This is my friend, Jack Shit, and you don't know him." - Lord Kano
    14. Re:That's a shame by northcat · · Score: 1

      No, your logic is flawed. The patches aren't uniformly applied to all parts. Some parts get patched repetitively while others dont get patched at all. And it is a fact that there are things from many years ago in Linux.

    15. Re:That's a shame by Lisandro · · Score: 4, Insightful

      Seriously. There was a great article posted some months ago here about this very issue (the rewrite-everything vs. don't-fix-if-it-ain't-broken argument), and i agreed with it's conclusions: rewrites should be done when they're needed and no when they can be done.

      The Linux kernel is very good as it is, why rewrite it from scratch? It's been evolving these past 10 years, it's not like no one touched the code ever since.

    16. Re:That's a shame by Anonymous Coward · · Score: 0

      Try to put together some embedded devices with the stock kernel, then reply. Kthx byebye

    17. Re:That's a shame by Anonymous Coward · · Score: 0
      1. Embeded devices are not the only non-x86 systems
      2. The 2.6 series allows you to disable all kinds of features (floating point, MMU, etc) and define sub-architectures.
      Kthx byebye
    18. Re:That's a shame by Anonymous Coward · · Score: 0
      I assume by 'they' you mean They==Microsoft.


      Microsoft should rewrite their kernel around Linux to get some decent security. Even if they infringe on Linux patents (IBM patents released to linux), they'd be OK with IBM's new policies if they open source it.

    19. Re:That's a shame by pqdave · · Score: 2, Interesting

      Because there are situations where X86 is irrelevant, but Linux is a top OS contender. In these cases, someone has (probably correctly) decided that resources are better spent customizing Linux to run on their hardware than it would be to start from scratch.

    20. Re:That's a shame by Anonymous Coward · · Score: 0
      Don't kid yourself into thinking the kernel is without it's flaws.

      Likewise you're grammar. But your too smart to bother with that.

    21. Re:That's a shame by Tribbin · · Score: 1

      Amsterdam (Netherlands) is getting old.

      The infrastructure could be much more efficient if they blow up and then re-build everything from scratch.

      Would the trouble outweight the gains?

      And I'm not talkin about lost nostalgia here.

      OK - the analogy sucks, but it shows that something being old should not be the only aspect for deciding what should be rebuilt.

      --
      If you mod this up, your slashdot background will turn into a beautiful sunset!
    22. Re:That's a shame by linuxcoder · · Score: 0

      That can be said about any OS not specifically written for embedded systems. It is not a Linux problem.

    23. Re:That's a shame by Anonymous Coward · · Score: 0

      If linux sucks for embedded systems, don't use it. *shrug*

    24. Re:That's a shame by MuMart · · Score: 1
      There are large sections of code that havent been touched since 1.x releases. Linux frankly runs for shit on anything other than x86, despite all the claims of all the different systems it runs on. Too much PC specific cruft.
      Would you like to provide some evidence to back up this little "fact" of yours?
    25. Re:That's a shame by Blarfy_Snarflepoop · · Score: 1

      Along these lines, does anyone know the 'if' and 'when' with respect to a 3.0 kernel? I imagine that would be a rather major overhaul, as compared to a 2.4 -> 2.6 jump, for instance (not to say that those aren't large undertakings, of course).

      Not that I really need to know, I'm just interested as to whether or not it's been discussed.

      --
      No sig for you.
    26. Re:That's a shame by Anonymous Coward · · Score: 1, Funny

      10 years isn't old. It's mature.


      Thats what I tried to tell the cops but they still put me in jail!

    27. Re:That's a shame by A+beautiful+mind · · Score: 1

      There are large sections of code that havent been touched since 1.x releases. Linux frankly runs for shit on anything other than x86, despite all the claims of all the different systems it runs on. Too much PC specific cruft.

      Actually i'm not totally convinced. I didn't see LKML full of complaints neither developers saying "we should do something about it now". PC specific "cruft" can be disabled or is disabled by default on non-x86. It would be interesting to do a diffstat from 1.x up until today's kernel, with statistics. If i cannot find any source that has done it before i might do it even. THEN we can talk about the age of code. The last change to 1.3 has been made on 20-Mar-2003 15:02 according to kernel.org. I wouldn't call that 10 years old neither.

      --
      It takes a man to suffer ignorance and smile
      Be yourself no matter what they say
    28. Re:That's a shame by Omniscientist · · Score: 1, Insightful

      If Linux is proven to infringe on IP's, than it is really essential that those are taken out. But the infringements must be proven with hard facts. But anyways, when I first heard of the rumors I dismissed them myself due to their nonsensical nature. That being, if there was a plan to rewrite the code that was infringing on IP's, it would be done through www.kernel.org since Linus Torvald is employed at OSDL and heads that website. You would have definitely heard something from Linus on the kernel development mailing list also. I would highly doubt that OSDL along with Linus would rewrite the kernel code outside of www.kernel.org and its contributors.

    29. Re:That's a shame by Anonymous Coward · · Score: 1, Interesting

      Linux frankly runs for shit on anything other than x86, despite all the claims of all the different systems it runs on. Too much PC specific cruft.

      Examples, please! I find this kind of FUD exactly on the same par as SCO's bullshit! Aside from the memory management stuff (which, I admit, I have not examined in much detail) I do not see lotsa x86 specific stuff. I have worked on scaled-down versions of Linux kernel on other architectures besides x86 (my forte is embedded code) and I take direct exception to this.

      Defend yourself with facts, sir!

    30. Re:That's a shame by Anonymous Coward · · Score: 0

      Let's do a better job with the math.

      We assume that the patches are equally likely to occur at any point in the code. Therefore, the amount of the code remaining unchanged at any given time is ((total code - code patched per week)/total code)^(number of weeks)
      == ((290 - 4)/290)^N ~= 0.9862^N (apologies to sig.figs.)

      Therefore, log0.9862(0.9862^N) == log0.9862(0.5) is true when N is the number of weeks in the kernel's half-life. Solving for N gives about 50 weeks.

      The half-life of the linux kernel is therefore 50 weeks. Slightly more often than every year, the Linux kernel is half new.

    31. Re:That's a shame by Tim+C · · Score: 1

      I do have 4 non intel systems ( 2 ppc and 2 ultrasparc ) running perceptably faster than equivalently clocked intel machines

      Which proves what about the Linux kernel, exactly? Perhaps with a BSD the differences would be even more noticable; perhaps they'd be less noticable.

      The point is, you can't draw any conclusions at all from that setup, except that for those exact conditions, the non-x86 machines are "perceptably faster". Maybe he's right, and if the kernel was fixed, the other machines would beat the x86 ones into the ground - you just can't tell.

    32. Re:That's a shame by A+beautiful+mind · · Score: 1

      Not really. There was a discussion about 2.7 lately (revisiting the issue which occured at last summer) but people seemed to have a consensus to stick with 2.6.x and -mm for a while still before starting 2.7. About 2.8+, i don't think there was any time(line|frame). I guess 2.7+ is heavily dependant on developers wanting to incorporate new stuff in the kernel which would break things. That situation just didn't occur yet.

      --
      It takes a man to suffer ignorance and smile
      Be yourself no matter what they say
    33. Re:That's a shame by Anonymous Coward · · Score: 0

      Sorry, but how stupid you have to be to say this is insightful? What are you, smoking crack?

    34. Re:That's a shame by ThousandStars · · Score: 1

      This is particularly true (or so I've been told) for embedded PPC applications and for servers (there are lots of old and not-so-old PPC servers out there).

    35. Re:That's a shame by hunterx11 · · Score: 3, Funny
      Obviously this won't be an issue since HURD is coming out soon.

      Unix already did this; everyone uses Plan 9 now.

      --
      English is easier said than done.
    36. Re:That's a shame by cirisme · · Score: 1

      >>IP issues aside, it's > 10 years old, when code gets that old, it's due for a good overhaul, if nothing else. Why? Does code rust?

    37. Re:That's a shame by GoCoGi · · Score: 1

      I don't see why everything has to be patched.

    38. Re:That's a shame by Anonymous Coward · · Score: 0
      If IBM, SUN, etc.. wants their platform supported let them donate the time/money/resources to fix where the failures are.

      They and any interested coder already does do that. An interested group built Linux for the mainframe and then IBM wrote their own version. Likewise, a group ported Linux to Sparc and then individuals from Sun got somewhat interested and modded it. Linux is exactly what you suggest.

    39. Re:That's a shame by c0p0n · · Score: 0, Troll

      LOL

      --

      Your head a splode
    40. Re:That's a shame by stratjakt · · Score: 1

      No, it rots.

      Google for "code rot". It's a real phenomenon.

      --
      I don't need no instructions to know how to rock!!!!
    41. Re:That's a shame by Matt+Perry · · Score: 1
      "Rewrite", to a programmer, doesn't mean to throw everything out and start from scratch, either. It means rethink some the design. Reevaluate why feature X was done the way it was, and if that's stillt he best way to do it. Make sure it's still relevant for modern hardware, and make sure it will still be relevant for tomorrows hardware.
      That's called refactoring in programmer newspeak.
      --
      Slashdot: Failed Car Analogies. Amateur Lawyering. Anecdote Battles.
    42. Re:That's a shame by Narishma · · Score: 4, Interesting
      http://www.joelonsoftware.com/articles/fog00000000 69.html

      I think this is the article you're referring to.

      --
      Mada mada dane.
    43. Re:That's a shame by Anonymous Coward · · Score: 1, Interesting

      On the other hand, I think the developement of HURD, lethargic though it may be is a good thing.

      And the fact that 99% of the sw that I write will run on Linux or any BSD.

      I like options.

    44. Re:That's a shame by Lisandro · · Score: 1

      Indeed, thank you!

    45. Re:That's a shame by TCM · · Score: 1

      Why does it NEED to run on anything other than x86? Sure, it's cool to run it on a Mac, but for practicality why not run OSX? It's tweaked for the platform

      Your thinking is a bit flawed. Running on only one platform optimally is not a sign of good "tweaking". Running on as many platforms as possible _using the same codebase_ shows that your developers can code cleanly and architecture-independant. And of course this doesn't mean that the result is far from optimized.

      --
      Of course it runs NetBSD. BTC: 1NT7QvbetmANwaMzhpVL6
    46. Re:That's a shame by greatmazinger · · Score: 2, Interesting
      I agree with most of what you said. 10 years of testing is invaluable.

      But a rewrite of the kernel doesn't mean that the old kernel will be junked. It could be forked and we all could have both kernels to run on. :) Maybe I'm just being naive though.

    47. Re:That's a shame by Anonymous Coward · · Score: 0

      Fine. Help starting out by pointing out a section of code in the Linux kernel which has not been changed in ten years.

      I don't think you can.

    48. Re:That's a shame by Handpaper · · Score: 2, Insightful
      Thank you, thank you, thank you.
      For what?
      du

      I've been looking for years for an app to do that. The functionality is in Konqueror, but only one directory at a time, through the 'Properties' dialog. I thought Konq accomplished it by recursively doing 'ls -l' and adding everything up, something I wasn't prepared to duplicate.

      This keeps happening to me.
      The last time was with 'screen'. Before that it was 'df'.

      The pattern seems to be:

      1) Need something done
      2) Google furiously, scour sourceforge, (in desperation) man -K "$function"
      3) Give up, do it the hard way or not at all
      4) Months to years later, discover that a programmer scratched that itch back in 196?, the function was duplicated by the GNU project twenty years later, but retained its original, short, cryptic, UNIX name
      5) do: locate, man $short_cryptic_UNIX_name, discover that it's been installed on this box since I installed Mandrake 8.1
      6) kick self, vow to read more early UNIX history, get on with things

    49. Re:That's a shame by andreyw · · Score: 1

      The "concept" may be 10 years old, but if you seriously think today's sources bear anything but the slightest semblance at say.... 0.01, then please pass around whatever it is you're smoking.

      Heck... even the **printf functions have been rewritten, jeez. The VM has long been rewritten. Drivers drivers? Yup. Module support? Didn't exist in 0.01 days. I could go on for pages describing the sheer volume of changes - and I won't even mention the fact that Linux isn't tied to the IBM PC AT anymore. Please actually LOOK at the linux source code before spouting off. The stuff that is > 10 years old is minimal and/or completely insignificant. They don't increment version numbers for nothing.

      Out of sheer curiousity, go grab some random binaries of off an SLS disk and try running then on your latest Linux install. Oh, you can't. Likely cause your kernel wasn't compiled ith supporting the obsolete a.out format, eh? You don't need to be an amature OS developer (I am) to figure out that you're wrong.

    50. Re:That's a shame by andreyw · · Score: 1

      Really? Hmmm, my Linux/PPC install says otherwise. Nice troll. It doesn't take a MENSA genius to figure out that you a) never even looked at the linux kernel source code, b) have no clue how it works c) don't even know "which" PC specific cruft you're talking about (PC-specific, or x86-specific? These are different things)

    51. Re:That's a shame by Slur · · Score: 1

      Shouldn't this be modded "funny"?

      --
      -- thinkyhead software and media
    52. Re:That's a shame by Azh+Nazg · · Score: 1

      Yes, but these are things like panic.c, which have proven themselves to do quite well without any modification. panic.c was last modified, in the main kernel branch, in 1993. There are many pieces of code like that which do not need updating in the kernel.

      --
      Azh nazg durbataluk, azh nazg gimbatul, Azh nazg thrakataluk agh burzum ishi krimpatul! This sig blocked by Slashdot.
    53. Re:That's a shame by ckaminski · · Score: 1

      I never had issues getting 2.0 running and working well on Alpha and Solaris machines. You suffer some for device support, in my case my video cards were worthless (that's an X issue more than Linux), and some of the SCSI cards I had were not supported, but the kernel was robust and served me just as well as it's Intel x86 counterpart.

      The applications, on the other hand, were a different story. Most software out there isn't 64bit clean, and compatibility modes proved a little troublesome. Bootstrapping the systems also wasn't nearly as easy as loading on Intels...

    54. Re:That's a shame by agraupe · · Score: 1
      There are large sections of code that havent been touched since 1.x releases. Linux frankly runs for shit on anything other than x86, despite all the claims of all the different systems it runs on. Too much PC specific cruft.

      As much as I support having a universal system that can be used on many architectures, Linux was designed for x86, hence its best performance will be on x86. If you need it, or want it, on other systems, you can, but don't expect the same level of performance. If, for example, Mac OS X (a good OS, IMO) were ported to x86, it would not run half as well as on Apple (until a lot of small bugs got worked out). Besides, except in the server market (not to discount its importance), there is very little other than x86. If you run PPC, there is a Unix-like OS with a pretty interface and a lot of ports from Linux, and if you need linux, it's there. And may I remind you that Linux is still the only desktop OS to have 64-bit support :)

    55. Re:That's a shame by vadim_t · · Score: 1

      I'd recommend simply buying/getting a Linux/Unix manual.

      Those can contain lots of useful stuff. A distro manual is probably a bad idea though, you'd want something that properly explains the administration of an Unix system in the generic way - with the command line.

      Whatever the distro, some things remain constant, such as /etc/hosts, /etc/nsswitch.conf and commands like 'du'. A generic manual can contain lots of useful info about things like that.

    56. Re:That's a shame by EddWo · · Score: 1

      So what are the current security problems with the NT Kernel?

      Theres not really a lot that needs improving in that respect, there are undoubtedly many problems with Windows, but they mostly stem from high priveleged services being exploitable and the default configuration not taking full advantage of the security features that are present. These are issues of configuration and implementation rather than fundamental problems with the design.

      --
      "Taligent is still pure vapor. Maybe they'll be the last who jumps up on Openstep... "
    57. Re:That's a shame by koko775 · · Score: 1

      Longhorn is based on Windows XP, which is based on Windows 2000, which is based on Windows NT, which is based off of OS/2. Microsoft's track record isn't the best, but I'd say you're full of it and too sure of your own opinion about Windows.

    58. Re:That's a shame by FxChiP · · Score: 1
      MSFT is doing this with Longhorn. The hardware evolves, why shouldn't the software that runs on it?
      Longhorn will probably have a lot of PC-specific cruft, too, though.
    59. Re:That's a shame by bob+beta · · Score: 1

      And may I remind you that Linux is still the only desktop OS to have 64-bit support :)

      That's a hell of a reach. There are other OSes that people run happily on the desktop that have good 64 bit support. Linux is frankly a latecomer to 64 bits, when compared to what a lot of people were running on 64 bit boxes on their desktop as long as half a decade ago. SGI and Sun have made plenty of desktop-oriented hardware in that past that ran 64 bits.

      Or maybe you only meant the low-budget 'crummy PeeCee desktop' market segment.

      Anyways, it's weasel-words to make a 'desktop' distinction, since the Linux 'install base' withers away to a tiny minority of the hardware out there when only desktop-Linux is counted.

    60. Re:That's a shame by Anonymous Coward · · Score: 0

      Obviously you've never tried to write drivers or perhaps you've never actually gone into the kernel source and studied/changed it.

    61. Re:That's a shame by Anonymous Coward · · Score: 0

      Just because Linux runs on other hardware doesn't mean it doesn't include a lot of x86 bloat/work-around within it. I think YOU'RE the one who hasn't WORKED with the kernel. Simply looking at it won't point out the obvious things that OP was talking about. It's this narrow minded thinking that keeps these portions of the kernel around release after release after release.

    62. Re:That's a shame by robertjw · · Score: 1

      Fair enough. My original thought was that linux originally was intended as a Unix that ran on 'cheap' PC hardware. If it works for embedded apps and other things, great, but I'm not sure I'm behind rewriting the whole kernel for embedded platforms, or IBM's big iron, Sun sparcs, etc...

      If better optimization for different platforms is needed, maybe the code should be forked for these platforms, or maybe someone that needs it should start over from scratch.

    63. Re:That's a shame by andreyw · · Score: 0, Troll

      Examples, dipshit?

    64. Re:That's a shame by pqdave · · Score: 1

      To some extent, that's what happens--I'm nowhere nere an expert (but if I get it wrong, I'm sure an expert or 70 will show up to correct me) but there is platform-specific code in the source that only gets used when compiling for that platform. That means in most cases you can optimize for one platform without harming another. Keeping the base code platform-neutral as much as possible is more difficult, but long term benefits all platforms, even X86. And difficult is less of a problem with a popular open-source program.

    65. Re:That's a shame by northcat · · Score: 1

      OK, I wasn't saying old == bad. I was only saying grandparent's logic was flawed.

    66. Re:That's a shame by Sri+Lumpa · · Score: 1


      "We assume that the patches are equally likely to occur at any point in the code."

      But your assumption is wrong, a part of the kernel that is actively being developed is more likely to have patches applied to it at frequent intervals.

      A LRM assumption is more likely to be correct. That is code that was recently modified is most likely to be modified (because it is actively developed) while a Least Recently Modified part is less likely to be modified because it is stable code. Of course once in a while an LRM portion will get heavily modified because it needs modernising... but it should increase the half life of the kernel significantly.

      --
      "The obvious mathematical breakthrough would be development of an easy way to factor large prime numbers." Bill Gates,
    67. Re:That's a shame by XnR'rn · · Score: 0

      IIRC Linux was originally intended as a terminal emulator.

  3. Monkey on your back. by Anonymous Coward · · Score: 2, Interesting

    "Although there were rumours saying that OSDL writes a version of the Linux kernel that doesn't infringe patents (an argument that was used by Microsoft), OSDL denies this: "OSDL officials have said that the report was not accurate, and that while Beaverton is putting $1.2m into economic development around open source software this is not connected to rewriting the Linux kernel.""

    OK. So why exactly is rewriting the kernel a problem?

    1. Re:Monkey on your back. by GrAfFiT · · Score: 4, Interesting

      It can be explained by SCO&co. as an implicit recognition of IP infringments.

    2. Re:Monkey on your back. by eno2001 · · Score: 3, Interesting

      My thoughts exactly. It's a free kernel. Anyone is damned well welcome to rewrite it. Now, the technical issues are many. All this talk of "complete rewrite from the ground up" tend to be bad ideas. The reason is that the original code may have some very good bits to it that you may bollocks if you write a completely new implementation. What is more needed from a technical point of view is a re-architecture. You keep the good stuff, replace the bad stuff and you're done. Keep in mind that it will take a long time to do, but it may be worth it in the end.

      --
      -"...bad old ideas look confusingly fresh when they are packaged as technology" - Jaron Lanier (Digital Maoism on Edge.o
    3. Re:Monkey on your back. by Wier · · Score: 2, Insightful

      ...
      "OK. So why exactly is rewriting the kernel a problem?"

      Because it's not needed. The kernel is being constantly rewritten via incremental (hopefully better) changes.

      I would imagine that there is very little code in the kernel that has never been changed.

    4. Re:Monkey on your back. by pclminion · · Score: 5, Insightful
      OK. So why exactly is rewriting the kernel a problem?

      Because "rewriting the kernel to avoid patent infringement" implies that you knew about the infringements before, which makes you legally liable.

      It would be admitting that kernel developers knowingly used patented methods in the kernel, which would open them to willful infringement lawsuits.

    5. Re:Monkey on your back. by macklin01 · · Score: 1

      Mod the parent up. This is precisely why they're denying it: they don't want to provide legal fuel to SCO's arguments! -- Paul

      --
      OpenSource.MathCancer.org: open source comp bio
    6. Re:Monkey on your back. by m50d · · Score: 1

      If OSDL are rewriting it, it shows they know there's a big problem with it.

      --
      I am trolling
    7. Re:Monkey on your back. by chromatic · · Score: 1

      You'd be liable even if you didn't know about it. The terrible part is that if you knew about the infringements, you'd be liable for triple damages. See my article Linux and Patent Risks, for example.

    8. Re:Monkey on your back. by drwho · · Score: 2, Informative
      Mod the parent up. This is precisely why they're denying it: they don't want to provide legal fuel to SCO's arguments! -- Paul



      No, I was reading somewhere (groklaw, perhaps) that actions to ameliorate a controversy can't be used as evidence of knowledgeable wrongdoing. So you can rewrite code to sidestep a patent infingement complaint, but that doesn't mean you are acknoledging the legitimacy of the patent or the claims of infringement. And this makes sense.

    9. Re:Monkey on your back. by Omniscientist · · Score: 1
      There is always the chance however that the various contributors to the kernel-dev used methods not exactly like the alleged-IP's, but similiar enough to possibly legally warrant an infringement. I think rewriting those parts does not necessarily tell people that you knew about the infringements, but you only overlooked them perhaps. Due to the mass amount of people that can contribute to the kernel, its not the kernel-dev leaders fault if someone contributes IP property that was previously closed source to the public...how would Linus or them know if they are putting in that if they have no published code to compare it to?

      If you factor in all these elements, and if the kernel is indeed infringing on certain IP's, I believe that would not make them legally liable, as the inclusion of IP material may have well been implemented without the awareness of the fact that the material was intellectual property. Nonetheless, I have not studied all of the IP's alleged to have been infringed in the kernel code, but so far I see no reason for changing it. It would be wise only to do so if absolutely necessary, as that would really throw Linux development down a hole.

    10. Re:Monkey on your back. by Tim+C · · Score: 1

      It would be admitting that kernel developers knowingly used patented methods in the kernel

      I don't follow your logic there at all. You can equally well argue that they knew no such thing, but are rewriting any bit that is even vaguely suspicious to remove any possibility of infringement, now that such possibility has been brought to their attention.

    11. Re:Monkey on your back. by Spolster · · Score: 1

      No, I was reading somewhere (groklaw, perhaps) that actions to ameliorate a controversy can't be used as evidence of knowledgeable wrongdoing.

      In a court of law yes, but in the court of public opinion it could be spun by SCO et al. that way.

    12. Re:Monkey on your back. by macklin01 · · Score: 1

      That's very interesting, and I appreciate your having posted that. (I hope that I can learn at least something new every day. :-) )

      I wonder if timing makes a difference. For instance, if the suit were against XYZ and it turned out that XYZ was rewriting the code to exclude the alleged SCO source code before the suit was filed, could that then be used to argue that XYZ knew of the infringements?

      At any rate, I suppose that it's good that this false rumor is being denied by SCO so as to not buoy SCO's arguments in the so-called court of public appeal. (Since this show is just as much for SCO's investors as for anybody else.)

      Again, thanks for the very interesting post! -- Paul

      --
      OpenSource.MathCancer.org: open source comp bio
    13. Re:Monkey on your back. by Anonymous Coward · · Score: 0

      Big fat "IF."

      You did read the article.... and the story summary right?

      Seems that the gist of both is that the rumor is false, so what's your point?

    14. Re:Monkey on your back. by midav · · Score: 1
      A (very) superficial answer (you might want to read at least GrokLaw to find out more) is:

      Of course, it can be used as an argument, and judging by SCO vs. IBM case you would be amazed what else can be used as arguments (including, for example, such as some statement in the contract actually was meant to mean its opposite and the current statement is a "scrivener's error.") However, being a very circumstantial argument akin to 'the reason we can not find Iraq's WMDs is because they are hidden very well,' it can hardly stay on its own.

    15. Re:Monkey on your back. by m50d · · Score: 1

      My point is that if it was true then it would matter. Which the OP didn't seem to think was the case.

      --
      I am trolling
  4. What, they're changing the recipie? by mveloso · · Score: 1

    Oops, never mind. /dumb, but had to be done

  5. Look at the source of the rumor by Vengeance · · Score: 5, Informative

    It was Maureen O'Gara, a writer without an ounce of credibility or ethics. She's been a huge part of the MicroSCOft campaign against Linux all along, this is just another bow shot.

    --
    It was a joke! When you give me that look it was a joke.
    1. Re:Look at the source of the rumor by Anonymous Coward · · Score: 0

      how do you know she isn't just a transsexual? I mean , according to Harvard's president, women aren't good at math and science. Of course that's JUST his opinion based on statistics.

    2. Re:Look at the source of the rumor by A+beautiful+mind · · Score: 2, Interesting

      Ah, this explains. Her latest reports i can remember of were heavily criticised by Groklaw and with that she lost all credibility. She did such poor job on even lieing that it was painful even to read.

      --
      It takes a man to suffer ignorance and smile
      Be yourself no matter what they say
    3. Re:Look at the source of the rumor by rewt66 · · Score: 3, Informative

      "Just another bow shot"? To me, a bow shot is a shot to inform your (naval) opponent that you can hit them, and to imply that you will hit them if they don't stop.

      This article, however, is nothing of the sort. It's more like "just another shot at a random set of coordinates, hoping that it comes close enough to someone to scare them".

    4. Re:Look at the source of the rumor by Anonymous Coward · · Score: 0

      lol and groklaw of course is not biased at all and is the single source of the truth..

    5. Re:Look at the source of the rumor by Anonymous Coward · · Score: 0

      Wasn't she on SCTV?

      What's the McKenzie bothers' take on this?

    6. Re:Look at the source of the rumor by ilikecaffeine · · Score: 1

      "just another shot at a random set of coordinates, hoping that it comes close enough to someone to scare them".

      You sunk my battleship!

    7. Re:Look at the source of the rumor by drew · · Score: 1

      careful you idiot, i said across her nose, not up it!

      --
      If I don't put anything here, will anyone recognize me anymore?
    8. Re:Look at the source of the rumor by Anonymous Coward · · Score: 0

      Cyberarmy is dead. Groklaw was born.

    9. Re:Look at the source of the rumor by Linuxathome · · Score: 2, Informative

      I agree. This is not the first time she's caught flak for putting out false claims. I'm actually surprised she still has a job.

    10. Re:Look at the source of the rumor by Anonymous Coward · · Score: 0

      Maureen? What are you doing here.

    11. Re:Look at the source of the rumor by Anonymous Coward · · Score: 0

      The media are a fickle bunch. When there is no more money to be made singing the praises of a person or thing, many journalists switch over to tearing them or it down instead.

    12. Re:Look at the source of the rumor by Anonymous Coward · · Score: 0

      I guess her work just isn't up to the high standards of the National Enquirer so she has to peddle her work to less reputable news organizations....

    13. Re:Look at the source of the rumor by dipipanone · · Score: 1

      It always helps when you own the company that employs you...

    14. Re:Look at the source of the rumor by Thing+1 · · Score: 1

      She's a hoser.

      --
      I feel fantastic, and I'm still alive.
  6. Sorry to state the obvious by k98sven · · Score: 4, Funny

    But given the current state of things, I'm pretty unsure that you can write any computer program of complexity beyond 'hello world' without infringing on at least one software patent.

    1. Re:Sorry to state the obvious by Klivian · · Score: 3, Funny

      Not to mention if you compile it, or run it with an interpreter.

    2. Re:Sorry to state the obvious by color · · Score: 1

      "Hello world" is already patented!

      --
      -- EOF
    3. Re:Sorry to state the obvious by AceCaseOR · · Score: 1

      I'm sorry, "Hello World" is patented.

      --
      Zagreus sits inside your head, Zagreus lives among the dead, Zagreus sees you in your bed and eats you in your sleep.
    4. Re:Sorry to state the obvious by speed-sf · · Score: 1

      Can anyone point to a resource regarding 'software' patents in North America? I'm terribly confused about it. IP is becoming more muddled and quagmire-ish, I'm afraid to write code because IBM mave have already patented it. More importantly, who owns the FIFO Queue patent?

      --
      All your database are belong to us
    5. Re:Sorry to state the obvious by mr_z_beeblebrox · · Score: 1

      I'm pretty unsure that you can write any computer program of complexity beyond 'hello world' without infringing on at least one software patent.

      Patent number (some absurdly high number) a method for grouping a collection of code in any computer language which will cause the computer to output the string "Hello, world!"

    6. Re:Sorry to state the obvious by mstefanus · · Score: 1

      ThankS for giving me an idea...

      I'm going to patent "Displaying a greeting using a computer program".

      I'll be filthy rich... HAHAHA...

    7. Re:Sorry to state the obvious by ch-chuck · · Score: 1

      Let's see, here it is: Claim #2 "A test program comprised of a toplevel delineated procedure containing a console output means, said output means containing a universal greeting message and an exit means, which, when compiled and executed, indicates that a basic, fundamental operational level of the program development system exists."

      They couldn't find any prior art, so patent that sucker!!

      --
      try { do() || do_not(); } catch (JediException err) { yoda(err); }
    8. Re:Sorry to state the obvious by LWATCDR · · Score: 1

      That is one of the benifits of having IBM in your corner.
      In case you have not read when SCO tried to sue IBM for patent infringment IBM wacked them with several patents that the owned. Right down to tree based menus.
      You can not beat IBM in a patent battle.

      --
      See my blog http://ilovecookes.blogspot.com/ for light hearted technical information.
    9. Re:Sorry to state the obvious by DrCode · · Score: 1

      Hah! They may have patented "Hello, world!", but they forgot to do "hello world".

    10. Re:Sorry to state the obvious by mr_z_beeblebrox · · Score: 1

      Our lawyers will be speaking to you about your "derived" work.

    11. Re:Sorry to state the obvious by hunterx11 · · Score: 2, Funny

      I'm sure all those "Just another Perl hacker," programs infringe on some of Rube Goldberg's patents.

      --
      English is easier said than done.
    12. Re:Sorry to state the obvious by DrCode · · Score: 1

      Sorry, but I've patented the "process of hiring legal experts to represent a given party in court".

    13. Re:Sorry to state the obvious by Anonymous Coward · · Score: 0

      Oh come on, hello world is the oldest program around, someone must have had the bright idea to patent it years ago and is probably just waiting until the whole world has writen cloned copies before pouncing on us all and demanding stupid amounts of royalty

    14. Re:Sorry to state the obvious by Anonymous Coward · · Score: 0

      HEY! 'hello world' is MY TRADEMARK! Pony up my royalties now thanks...

  7. In other news.. (Patents) by Antonymous+Flower · · Score: 1, Interesting

    In other news, FIPFS (Fictitious Initiative for Patent-Free Software) has incredible difficulty writing an operating system due to all practical functionality of operating systems being patented...

    1. Re:In other news.. (Patents) by youngerpants · · Score: 1

      Erm, no

      All "current" practical functionality has been patented, how about ideas and design that hasn't yet been thought of.

      When Charles Babbage came up with his Difference Engine, did he think "Wow, all this needs is a mouse and a graphical UI", nope, that came later.

      Although I cant believe I'm saying it (just playing devils advocate I suppose) but perhaps all this patenting may lead to some designers thinking out-of-the-box with their next UI/ Human Interface

    2. Re:In other news.. (Patents) by cybergrue · · Score: 1
      but perhaps all this patenting may lead to some designers thinking out-of-the-box with their next UI/ Human Interface

      doubtful. creating a better UI/HI has been researched for quite a while. The guy who came up with the design for the mouse at PARC (for the life of me, I can't remember his name, Keys or something) also created a piano type keybord that could be used one handed, and was considered vastly superior to the normal keybord by everyone who learned to use it. It just didn't catch on. If I recall correctly, PARC also experimented with trying to design the absolute worst pointing HI device that was usable (It consisted of a 10 pound weight attached to a light pen that you held in mid air!) A whole series of 3d UI have been developed over the years as well, again, none of them caught on.

      However, the major problem is with the patent system itself in the US, which allows applications based on work done by others, and concepts that are far to vague (even approaching ideas). The US legal system is also at fault for allowing enforcement of these bogus patents (I consider a lawyer showing up at my door with a notice saying 'you are infringing on my patented obvious_idea, pay me X millions or I sue' to be part of the legal system. By the time this gets to court, I would probably have already spent X millions on legal fees determining the patent was bogus)

    3. Re:In other news.. (Patents) by Antonymous+Flower · · Score: 1

      For my own benefit I'd request someone explain why this would be modded Flamebait? Thanks in advance.

    4. Re:In other news.. (Patents) by Anonymous Coward · · Score: 0
      for the life of me, I can't remember his name

      Douglas Engelbart.

    5. Re:In other news.. (Patents) by youngerpants · · Score: 1

      Yes, but you're still thinking about using monitors and handheld devices for your UI/ HI

      To quote Back to the Future II "You use your hands, thats a kids toy"

      Sorry about the source of the reference, but oh so apt

    6. Re:In other news.. (Patents) by youngerpants · · Score: 1

      I agree, more OT :)

    7. Re:In other news.. (Patents) by Antonymous+Flower · · Score: 1

      I am absolutely a supporter of innovation, don't get me wrong. Those innovations too will be patented. How about a little freedom of invention? I'd like to be able to use ideas that came before me, I mean, they have to be useful for people to guard them so closely, right?

      By the way, a database of inventions is a database of ideas. When you submit all your ideas to your government, that leaves little to their imagination. Y'know, Einstein was a patent clerk..

  8. MOD PARENT DOWN by Anonymous Coward · · Score: 3, Funny

    Comment is too sensible for slashdot.

  9. Infringe away by kad77 · · Score: 1

    Umm, why not maintain an alternate kernel that uses all the best technologies, copyrighted, patented, or not, and let people compile it themselves? Store it on a server in one of the many countries that doesn't give a rip... b

    1. Re:Infringe away by jimicus · · Score: 1

      I'm not sure any US-based maintainers could easily maintain it (legally) then.

      Disclaimer: IANAL

  10. More FUD from O'Gara by Foofoobar · · Score: 5, Insightful

    PJ over at Groklaw has a nice write up on this. Is it just me or is Maureen O'Gara just part of the FUD-machine funded by SCO?

    Hmmm... I wonder how much reporter integrity goes for on the open market?

    --
    This is my sig. There are many like it but this one is mine.
    1. Re:More FUD from O'Gara by stratjakt · · Score: 3, Funny

      SCO doesn't have enough cash to fund a junior high school newsletter.

      --
      I don't need no instructions to know how to rock!!!!
    2. Re:More FUD from O'Gara by Anonymous Coward · · Score: 0

      I wonder how much reporter integrity goes for on the open market?

      That's a good question. How much does it cost Roland Piquepialle to advertise his blog here a dozen times a month?

    3. Re:More FUD from O'Gara by arkanes · · Score: 1

      I dunno. Sure, they have a lot less cash than they did last year. But I bet you could get a high schooler to do almost anything for 37 million dollars.

    4. Re:More FUD from O'Gara by Anonymous Coward · · Score: 0

      Trust me, you wouldn't believe what some of those high schoolers will do just for a couple grand.

    5. Re:More FUD from O'Gara by MrWa · · Score: 2, Interesting

      $240,000 - or atleast that is how much Armstrong Williams's integrity costs.

    6. Re:More FUD from O'Gara by doublem · · Score: 1

      Depends on the journalist's profile, market and existing salary. It also depends on if it's a one time story, a series of articles or an ongoing bias.

      They gave us the price chart in one of my College Journalism classes, but I it's languishing in the basement. There's a theoretical "ethical surcharge" for advocating something you find morally abhorrent, but it's rarely charged. Most journalists don't have enough ethics to justify charging the extra fee.

      --
      "Live Free or Die." Don't like it? Then keep out of the USA
    7. Re:More FUD from O'Gara by Anonymous Coward · · Score: 0

      Ask Armstrong Williams and the Bush White House.

    8. Re:More FUD from O'Gara by mopslik · · Score: 1

      SCO doesn't have enough cash to fund a junior high school newsletter.

      Looks like they might want to read this thread then.

    9. Re:More FUD from O'Gara by Tim+C · · Score: 1

      Redundant my arse. The OP is countering one person's article with another person's article. Apart from the fact that we like and agree with what's said on groklaw, what reason do I have to take PJ's word over O'Gara's?

      Let me put it this way - the OP said "O'Gara's an SCO-funded shill!", to which the parent replied "PJ's an IBM-funded shill!". Flamebait or troll perhaps, but *redundant*? Go look it up moderator, because you don't know what means.

    10. Re:More FUD from O'Gara by Anonymous Coward · · Score: 0

      Hmmm... I wonder how much reporter integrity goes for on the open market?

      About $50!

      And did I ever tell you you're grea... wait, this money's fake, ok, £25?

    11. Re:More FUD from O'Gara by bhsx · · Score: 1

      FTA: However, a source close to Open Source Risk Management (OSRM), which commissioned Ravicher's review, claimed to know what the Jan. 25 announcement was and told NewsForge that it had nothing to do with Ravicher's study.
      So, come on Bruce... what's the announcement. We know they meant you! Spill it baby.

      --
      put the what in the where?
    12. Re:More FUD from O'Gara by quarkscat · · Score: 1

      The last confirmed payout for "reporter
      integrity" is $240K USD. Considering:
      (1) the general state of the USA economy,
      (2) there are holiday bills to be paid,
      and (3) Dubya's push to lower wages,
      that $240K may represent a high point.

      BTW: The fee is a really a private
      negotiation between the "John"
      and the "Hooker", so YMMV.

  11. Done. by hummassa · · Score: 1

    It was really overhauled. From 1.2 to 2.0, from 2.0 to 2.2, from 2.2 to 2.4 and from 2.4 to 2.6. That's the odd/even thing.

    --
    It's better to be the foot on the boot than the face on the pavement. ~~ tkx Kadin2048
  12. No 2.6.11 by Anonymous Coward · · Score: 0

    There you go folks, Linux is dead...

  13. Look at the LinuxWorld article author by Nevita · · Score: 1

    All you have to do is look at the author of the original LinuxWorld story. Yes, that's right. It's everyone's favorite journalist/paid SCO shill Maureen O'Gara. That should have been enough to convince anyone with half a brain cell that this wasn't legit.

    --
    Wise men learn more from fools than fools learn from the wise.
  14. Maureen O'Gara strikes again by avidday · · Score: 2, Informative

    The article at the centre of this particular storm-in-a-teacup was written by the infamous Maureen O'Gara, who regularly gets dumped on over at groklaw for the quality and balance of her linux reportage and whose company (G2 computer intelligence) is behind a motion in Utah connected to the SCO IBM case to unseal submissions to the Court by both parties. Summary: Nothing to see here.

    1. Re:Maureen O'Gara strikes again by Anonymous Coward · · Score: 0

      In what way is her credibility lessened by the fact that her company is trying to have the court proceedings opened to the public? Isn't that what a good journalist is supposed to do? (I'm not saying she is a good journalist--I don't know anything about her.)

  15. Maybe... by deafpluckin · · Score: 3, Interesting
    ...this sounds like complete bs. For the sake of argument, instead of rewriting the kernel maybe they (ibm, redhat, novelle, whoever) should be working on developing material that would help them in any court cases against Microsoft, i.e. prior art and whatever else can help to combat any of those 27 patents.

    Then, if there's a patent that they think MS might try to stick them with, re-write/change only that part of the kernel that's affected.

    Am I the only one that thinks an entire re-write for operating system technologies that have been around long before MS is a little silly?
    1. Re:Maybe... by Anonymous Coward · · Score: 0

      MS doesnt use patents to fuck competition... Thats Apple and IBM jobs.

  16. Re:That's a shame (huhwhat?) by Anonymous Coward · · Score: 1, Insightful

    The Linux kernel is a living codebase. It's constantly scrutinized and updated. The nature of it being open source guarantees this. To say it should be rewritten simply because it is 10 years old is a hollow statement. If you know of a module that's needs updating, point it out.

  17. re-writing Kernel by doodlelogic · · Score: 1

    Sounds like an awful lot of work to achieve the same aim. And if what is being done here is effectively reverse-engineering, isn't there the risk of falling into the same trap again, i.e. inadvertently writing into the kernel patent-infringing code?

  18. Re:That's a shame (huhwhat?) by Anonymous Coward · · Score: 3, Insightful

    Meh, the whole kernel is stuffed with x86 specific cruft. Despite people constantly cheering all the platforms it "runs" on (IMO there's more to running than just bootstrapping), the focus has been on x86 from day one. Much of it is just too ingrained, and entire subsystems could do with a brand new design.

    There's no point on discussing stuff like this on slashdot, hardly anyone here knows shit about linux, or computers in general.

    Bunch of know-nothing know-it-alls.

  19. An infringement-free kernel... by russotto · · Score: 1

    Step 1: cp -R kernel.orig kernel.infringement-free
    Step 2: There is no step 2. Alas, there is also no Step 3: Profit.

    1. Re:An infringement-free kernel... by Tribbin · · Score: 1

      Thanks for the tip, I just made myself an infringement-free photoshop version.

      --
      If you mod this up, your slashdot background will turn into a beautiful sunset!
  20. Fud-meisters at work by Ashe+Tyrael · · Score: 4, Insightful

    I can just see the fud-meisters now.

    "They aren't going to rewrite the kernel to take out our patented stuff. So it must be in there!"

    While not the gist of any of the statements, that viewpoint can be made to fit.

    Ah, the power of spin.

    --
    "How fine you look when dressed in rage."
  21. OSDL dispatches Iraqi Minister of Information by PocketPick · · Score: 3, Funny

    OSDL, god praise it's name, wishes to send out noice that there is no re-writing of Linux kernel, nor has there ever been any attempt to re-write it. These are the truths! Even if there were attempts to re-write it, which ther are not, it would only be by word of our great master, IBM.

    Only the infidels at Microsoft could create such lies, and surely would admit it if they were not such cowards, hiding in thier cubes like the unholy nerds that they are. God willing, capitalist proprietary software will fail under the great crush of thier devil-like closed-source policies. Indeed, I do not doubt this. Praise OSDL.

    1. Re:OSDL dispatches Iraqi Minister of Information by Ashe+Tyrael · · Score: 1

      I now inform you that you are too far from Utah!

      --
      "How fine you look when dressed in rage."
  22. Not accurate? Uh, oh. Here we go again... by AtariDatacenter · · Score: 3, Insightful

    "OSDL officials have said that the report was not accurate..."

    I always hate in when PR types use this phrase. Mind you, I like the OSDL, I just hate the "was not accurate" thing. For example...

    "The report that Mr. Jones embezzled $10.5 million was not accurate." REASON: Mr. Jones actually embezzled $10,548,984. Its the classic non-denial denial where you deny something in super-general or super-specific terms, while not adding anything meaningful at the same time. It is more about perception than truth.

    I don't know if the OSDL is playing perceptions vs. truth here, but I don't like things that are phrased in that particular manner for those reasons.

    1. Re:Not accurate? Uh, oh. Here we go again... by Anonymous Coward · · Score: 0

      It's logically the same as saying it was wrong.

      In this case, they specifically said they were not rewriting the kernel; e.g. they gave the reason why it was wrong, not just that it was wrong, which would seem to be the source of your complaint.

      Basically, I can't see any better way of saying it than just what they said: no, we aren't doing that.

    2. Re:Not accurate? Uh, oh. Here we go again... by temojen · · Score: 1

      Well, if they made the statement "The Linux kernel is not being re-written" they would be incorrect. The kernel is constantly re-written, but not for intellectual property reasons.

    3. Re:Not accurate? Uh, oh. Here we go again... by poofyhairguy82 · · Score: 1
      It is more about perception than truth.

      As a natural born PR type, let me warn you- perception is truth. Or at least it matters more.

    4. Re:Not accurate? Uh, oh. Here we go again... by Anonymous Coward · · Score: 0
      For example... "The report that Mr. Jones embezzled $10.5 million was not accurate." REASON: Mr. Jones actually embezzled $10,548,984.

      Bad example. That statement is not just misleading; it's factually wrong. If Mr. Jones embezzled $20 million, he embezzled $10 million. And if even if he embezzled only $10,450.01, it is accurate (but imprecise) to say that he embezzled $10.5 million).

    5. Re:Not accurate? Uh, oh. Here we go again... by jimicus · · Score: 1

      I don't know if the OSDL is playing perceptions vs. truth here, but I don't like things that are phrased in that particular manner for those reasons.

      I hear what you're saying, but I can't see anyone rewriting anything for patent reasons, at least not until the first reasonably sensible (ie. not SCO) lawsuit shows up. (This assumes that there is a single not-easily-dismissable patent infringed; for the purposes of this argument let's pretend there is)

      Largely because the implications are huge. I'm thinking along the lines of: all of a sudden, everyone who doesn't contribute to the development of, and ultimately move to the new Patent-Free (TM) kernel could arguably be seen as having infringed the offending patent wilfully. Hence triple damages (particularly big problem if your vendor offers limited indemnity). Hands up all those who want to give every IT manager with a Linux box in the US palpitations!

      IANAL, so I could be way out here...

    6. Re:Not accurate? Uh, oh. Here we go again... by LuSiDe · · Score: 1

      A very broad, wide and wildly interpretable detail of the statement indeed. AKA lawyer-speak or marketing-speak -- both not adored by techies.

      However if you look at who wrote the article to which OSDL replies (the troll / FUDster / fisher known as `Maureen O'Gara') i'd say any detail in reply to her is unnecessary for that'd give credit to her fishing expeditions and related noise.

      A broad statement as backfire is much more effective, although both HER as well as OSDLs statement are not news for any credible news organisation. Ie. don't feed the trolls, report real news, etcetera. The problem lies with those who reported about HER 'news' though because that started the misinformation problem in the first place.

      --
      WE DON'T NEED NO BLOG CONTROL.
    7. Re:Not accurate? Uh, oh. Here we go again... by Anonymous Coward · · Score: 0
      I always hate in when PR types use this phrase. Mind you, I like the OSDL, I just hate the "was not accurate" thing.

      Just like the other day,

      The New Yorker article was "so riddled with errors of fundamental fact that the credibility of his entire piece is destroyed," Pentagon spokesperson Lawrence DiRita told reporters on Monday.
      Of course they haven't denied sending troops into Iran.
    8. Re:Not accurate? Uh, oh. Here we go again... by Error27 · · Score: 1

      The problem is that MOG is really smart. She deliberately writes her stories so that all the facts are true or attributed to an anonymous source so you end up with the wrong conclusion.

      Look at this story on Groklaw.

      PJ refutes one of MOGs stories but what PJ didn't notice is that every sentence in the article was true when taken by itself. The fact that they combined to give you a false impression that was the opposite of what happenned is a problem for the reader to deal with.

  23. Coincidentally by Anonymous Coward · · Score: 0

    Beaverton

    I used to live in Beaverton. It wasn't as much fun as you'd think.

  24. wow.. by essreenim · · Score: 3, Insightful
    thats gotta be the cleverest thing I ever heard...idiot or maybe you were being funny!, the kernel is 10 years worth of research.

    And: OSDL writes a version of the Linux kernel that doesn't infringe patents

    So its the same as the official kernel then!!

    1. Re:wow.. by Anonymous Coward · · Score: 0
      Research? Hahaha.

      The kernel is 99.9% ad-hoc.

    2. Re:wow.. by joeljkp · · Score: 2, Informative

      So its the same as the official kernel then!!

      OSRM estimated last August that Linux may infringe on 283 patents.

      Personally, I believe that if specific instances of actual infringement are known, those parts of the code should be rewritten. Unless the kernel writers are part of a civil disobedience campaign I'm not aware of?

      --
      WeRelate.org - wiki-based genealogy
    3. Re:wow.. by Anonymous Coward · · Score: 0

      Such as not being American?

  25. Re:That's a shame (huhwhat?) by Anonymous Coward · · Score: 0

    Well, instead of trolling, do something about it. If you belong on the pedestal you put yourself on, then please do the world some charity and assist in this unworthy cause we "know-nothing know-it-alls" absent mindedly toil with.

    Otherwise, you are just another troll among "know-nothing know-it-alls".

  26. TTL? Nah, TTF by chucken · · Score: 1

    Instead of Time To Live, packets should be given TTF - Time To Float....

    1. Re:TTL? Nah, TTF by Tribbin · · Score: 1

      For you, it s TTSU.

      --
      If you mod this up, your slashdot background will turn into a beautiful sunset!
  27. I stand corrected by Vengeance · · Score: 1

    Or to be more accurate, I sit corrected. :-D

    I was attempting to convey the meaning of a warning shot, but never stated the caliber or airspeed of the projectile! Think of it as a kid with a pellet gun firing across the bow of an AEGIS destroyer.

    --
    It was a joke! When you give me that look it was a joke.
    1. Re:I stand corrected by Progman3K · · Score: 1

      I think the term "saber rattling" is what you were looking for.

      --
      I don't know the meaning of the word 'don't' - J
  28. I wonder... by Anonymous Coward · · Score: 1, Funny

    ...if the Linux kernel could be rewritten to compile in Microsoft C? Could it then be interfaced under the Windows GUI to provide the best of both worlds? A rock solid kernel with a rock solid UI? Dump all that ugly Bash, sh, ksh, Bourne Shell, csh crap and put the much nicer CMD or COMMAND on top of it for CLI freaks. Maybe drop IE and replace it with the Linux program Firefox. The same with Outlook. Replace it with Linux Evolution. A lot of stuff from the Linux project (GIMP, Xine, Ogg Vorbis and Theora) could be added to this new frankenWindows. Since Macintosh is now Linux as well, you could probably get the code for some of the projects from the Darwin project. I think that iCal, iTunes and the new iWork projects are all part of the Darwin kernel. To be honest, I think you'd wind up with the most usable, stable and secure OS ever. But you know why it wil never happen? Because none of these businesses want to work together. Linus is only interested in his own company's profits. The same with Bill Gate and Steve Jobs. They won't work together because they are trying to smash each other so they can own the world.

    1. Re:I wonder... by Anonymous Coward · · Score: 0

      Microsoft C ... rock solid UI

      +1: Funny.

      Linux program Firefox, Linux Evolution

      Clearly you're new/unexposed to Linux.

    2. Re:I wonder... by Anonymous Coward · · Score: 0

      very nice... :-)

    3. Re:I wonder... by temojen · · Score: 1

      That is just so ignorant, I don't know where to start. All in all, it's a lame troll.

    4. Re:I wonder... by dahl_ag · · Score: 0

      Check out http://www.colinux.org/. "Cooperative Linux is the first working free and open source method for optimally running Linux on Microsoft Windows natively". It is still in early beta dev, but quite impressive.

    5. Re:I wonder... by sloanster · · Score: 0, Offtopic

      "Cooperative Linux is the first working free and open source method for optimally running Linux on Microsoft Windows natively".

      okely dokely, I don't really have much interest in "running Linux on microsoft windows natively"... What would be cool though, is something that would work the other way around...

      It would be very handy at present if I could, in my linux desktop environment, say, fire up a microsoft windows environment strictly as a handler for whatever odd legacy windows program I might want to run.

      I'd want to be able to shut it down completely when the microsoft application has finished, such that the microsoft environment is neither using any resources, nor resident in memory, but could be started again if I needed to run some other legacy ms windows application.

    6. Re:I wonder... by allanc · · Score: 1

      Then you want Wine.

      (Or, rather, you want a version of Wine from far in the future when it works a lot better)

      --AC

    7. Re:I wonder... by Richard_J_N · · Score: 1

      Qemu is pretty good for this. It's free, amd (relatively) fast. http://fabrice.bellard.free.fr/qemu/

    8. Re:I wonder... by Anonymous Coward · · Score: 0

      Hey shutup! I wasn't trolling. I was making a serious suggestion. That's the problem with computer types. They fly off the handle whenever a user suggests something he or she thinks might be a good idea. I've been reading about this Linux stuff for a little bit and I've seen some Linux programs working on my friend's computer. He run Linux Gimp, Linux Mozilla and Linux GAIM on his Windows 2000 PC. They seem to work OK, but need some help. I was just thinking that the area they most need help in is the GUI. So why not use the superior Windows GUI and the superior Linux Kernel compiled in MS C? That seems like a reasonable approach. The best of the best so to speak. So I don't know what's your problem, but you obviously don't care at all about what users think. Typical computer guy. You're just like that IT guy skit on Saturday Night Live. I made a simple suggestion and you called me ignorant and a troll. Nice netiqette there loser.

    9. Re:I wonder... by gnuLNX · · Score: 0

      I am not sure if you are the bigges idiot ever....or the funniest person alive.

      --
      what?
    10. Re:I wonder... by sloanster · · Score: 1

      (Or, rather, you want a version of Wine from far in the future when it works a lot better)

      Yes, what you said...

    11. Re:I wonder... by sloanster · · Score: 1

      Qemu is pretty good for this. It's free, amd (relatively) fast. http://fabrice.bellard.free.fr/qemu/

      Thanks for the link, I'll check this out -

      Hmm, Fabrice Bellard... that name rings a bell, way back from my msdos days... (peruses the bellard.org website) AHA! That's the very same Fabrice Bellard who wrote that gem of a program called lzexe - That just made my day, finding that Mr Bellard has come over to the light side of the force :)

    12. Re:I wonder... by Anonymous Coward · · Score: 0

      Harrrr!!!! I've been found out. I was the original poster, and yes this was intended to be humorous. Thanks to gnuLNX for "getting it".

  29. What do they mean, "doesn't infringe patents"? by Anonymous Coward · · Score: 5, Insightful

    The whole concept of a kernel which doesn't infringe patents is ridiculous. You don't decide what is and is not infringement by reading through source code in some magical process. You decide it when some patent holder says "this piece of code here infringes on my patent!" and then both parties either agree or go to court and then the court comes up with some resolution. There are millions of patents out there and there are millions of lines of code in the kernel. There's no such thing as a magical search engine that you can plug a piece of code into and see which patents apply to it. Even things that are heavily promoted as "patent-free" such as PNG, Ogg, and others, might be infringing some patent. There is just no way to say with certainty in this. The patent office grants so many crappy patents all the time that it's hard to say that any very large body of code (like the kernel) doesn't possibly infringe on something.

    This is all why big companies tend to enter into cross-licensing agreements with eachother. They know that it's almost inevitable that if you write enough code, you will write something that could reasonably be argued to infringe on some patent that no one has ever heard of. In fact even the companies that hold enormous numbers of patents don't have the ability to check all the code that is out there.

    This area of law is only defined and made certain in practice involving specific patents and specific code. For someone to make claims about some code not infringing is completely bogus.

    I remember all the arguments about PGP vs. the RSA patent and how much time was wasted arguing about that patent and worrying about it, when a) it was never clear that it was a valid patent and b) RSA never enforced it up until the time it expired.

    The right thing to do is to be fearless about these things. If there is an infringement, let the patent holder notify the kernel developers about what the patent is and which regions of code are infringing. The ODSL should then get a lawyer to talk with the developers, look over the patent and the code in question, and see if the patent holder's claim makes sense. If it does, then it is time to think about coding around the patent, but until that set of things has happened, trying to code around patents that may or may not be enforceable is just a waste of time.

    Patents are not at all like copyrights. Copyright is usually pretty clear: there's a piece of work authored by someone and that work is or is not similar to some other work. If it is too similar there is infringement and it's pretty easy to see usually. Patents just aren't like that at all.

    1. Re:What do they mean, "doesn't infringe patents"? by bob+beta · · Score: 1

      If there is an infringement, let the patent holder notify the kernel developers about what the patent is and which regions of code are infringing. The ODSL should then get a lawyer to talk with the developers, look over the patent and the code in question, and see if the patent holder's claim makes sense.

      Do the kernel developers have a legal department?

      I suspect not.

    2. Re:What do they mean, "doesn't infringe patents"? by xixax · · Score: 1
      Even things that are heavily promoted as "patent-free" such as PNG, Ogg, and others, might be infringing some patent.

      Specifically, PNG was written to side-step specific GIF patents, whilst Ogg was written to avoid specific MP3 patents. There is no guarantee that the authors avoided these patents completely, or that there aren't *other* patents that may be infringed by these projects.

      Xix.
      --
      "Everything is adjustable, provided you have the right tools"
    3. Re:What do they mean, "doesn't infringe patents"? by hta · · Score: 1

      I remember all the arguments about PGP vs. the RSA patent and how much time was wasted arguing about that patent and worrying about it, when a) it was never clear that it was a valid patent and b) RSA never enforced it up until the time it expired.


      This is the first time I've heard someone claim that RSA "never enforced its patents"!
      RSA, when it owned the patents, was the poster boy for the "I own this patent and I'm going to get your money" movement - insisting that nobody, but nobody, could use RSA without a license agreement that either involved hefty payments to RSA or significant equity stakes in the company.
      I'm RATHER happy the patents have expired!
  30. what patents? by Anonymous Coward · · Score: 0

    To my knowledge the current 2.6 Linux kernel does not infringe on any patents. I have done alot of reading while the SCO case was going on but so far I haven't come across one single patent that the Linux kernel would infringe on.

  31. Same Principle. Different Day by opposume · · Score: 1, Informative

    Like Ann Coulter is to Democrats and Michael Moore is to Republicans Maureen O'Gara is to Open Source Only the weak minded, lazy, and easily led will beleave a word she says. But, unfortunately, the majority of the populace is one of the above...

    --
    I haven't lost my mind. It's backed up on disk somewhere.
  32. MOD PARENT UP by Anonymous Coward · · Score: 0

    Good point, except Coulter is clearly completely insane while the other two are just hucksters.

    PS: I'm a registered Republican. But Coulter is a nutbag, even we know it.

    1. Re:MOD PARENT UP by opposume · · Score: 1

      I agree fully... I read 2 of her three books and it scares me to think people actually listen to her...

      --
      I haven't lost my mind. It's backed up on disk somewhere.
  33. How would you begin such a project anyway? by MrLint · · Score: 2, Insightful

    Given the nature of the USTPO, where any obvious or ancient idea (like swinging on a swing sideways) gets a patent, how can you possibly rewrite something that you can guarantee wont infringe on some over broad chicken scratch filed in the 70's when they had wire wrapped electronics and nixie tubes in cash registers.

    By the time you are done whats to stop someone from patenting the code you are working on. Even if its invalid, you get tied up in court either way.

    The problem is the system, and the system alone.

    1. Re:How would you begin such a project anyway? by Anita+Coney · · Score: 1

      I agree. The astonishing growth of the PC market was due partially because there were very little patent hinderance. The sole purpose of the current patent system is to keep the status quo in place. "Little" companies like Microsoft who have grown up, do not want to be replaced by smaller companies with better ideas.

      --
      If someone says he and his monkey have nothing to hide, they almost certainly do.
  34. Where did 288 come from? by erroneus · · Score: 0

    That's an interesting question that I'm surprised no one has answered yet.

    The number 8 is considered lucky. 88 is very lucky and 8888 even moreso. 288 might be read as 2 88s or 8888. Was that coincidence or fairly artful? Dunno!

    1. Re:Where did 288 come from? by erroneus · · Score: 0

      OOOPS!!! I explained that wrong!!! Crap! Got it backwards.

      Here, just read this and that will explain it. 8888 is wishing them death... horrible omen.

  35. Re:Same Principle. Different Day by Anonymous Coward · · Score: 0

    You need to do a bit more research. Michael Moore does not lie. He spins the truth to support his views, but he does not lie. Maureen O'Gara lies though her teeth.

  36. Actually, not the same thing... by AtariDatacenter · · Score: 1

    It's logically the same as saying it was wrong. In this case, they specifically said they were not rewriting the kernel; e.g. they gave the reason why it was wrong, not just that it was wrong, which would seem to be the source of your complaint.

    You're not thinking like a PR drone. You're thinking like a logical human being who talks in specifics.

    From the article: "Open Source Development Labs (OSDL) [....] has denied that it plans to rewrite the Linux kernel to combat claims that it infringes some software patents." And "But the OSDL has denied that it is planning to rewrite parts of the kernel."

    Lots out outs here. Perhaps OSDL themselves aren't doing the rewrite. Perhaps it IS doing the rewrite, but isn't doing it to combat _claims_. Perhaps they aren't planning it, but they have already planned it.

    Compare/Contrast: CEO Speak. The way that CEOs get away with telling lies because, technically, they're not actually lies, even though they totally lead you to a wrong conclusion.

  37. Which patents? by Anonymous Coward · · Score: 0

    First of all, the Linux kernel has not been proven to violate any patents yet!

    Secondly, if proven to violate patents, will the patents so violated really hold up in court?

    Frankly, I think that any knee-jerk reaction to the vast FUD machine that is Microsoft by rewriting a kernel that has stood the test of time is way too drastic.

  38. Sorry, but the legal threats have no credibility by SunFan · · Score: 1


    IANAL, but it doesn't take one to read what other companies are doing. Are IBM, HP, Red Hat, and Sun slowing down due to SCO....nope. They are actually speeding up! Anyone who has any inkling of fear over SCO needs to get a hug and some hot cocoa and go worry about things that matter.

    --
    -- Microsoft is the most expensive commodity operating system and office suite vendor in the marketplace.
  39. infringement tournament? by newr00tic · · Score: 1

    [...] Although there were rumours saying that OSDL writes a version of the Linux kernel that doesn't infringe patents (an argument that was used by Microsoft), OSDL denies this: 'OSDL officials have said that the report was not accurate, [...]

    OSDL themselves are unhappy that they don't infringe the kernel? Are they striving to infringe patents now??? ..I hope this is a typo..

    --
    A horse can't be sick, you know, even if he wants to.
  40. It is, that's why so many are screaming by jd · · Score: 2, Informative
    People are screaming blue murder over the magnitude of code rewrites and updates in the current 2.6 kernel. They're not just talking about new features, as you can always choose not to compile those in. They're talking major editing of sections that are considered stable.


    Personally, I don't care about the edits - the difference between a "stable" release and an "unstable" one is the number of characters you choose to represent it with. It's just a label, it doesn't confer any magical properties.


    Some of the networking code is getting a little old - there are sections of the IPv4 code which haven't been touched in 2-3 years. You can have a lot of new ideas on how to improve something, in that kind of timeframe.


    A complete rewrite is unlikely at present. The kernel is still evolving too rapidly. Nobody would be able to keep up with the changes. Now, once we reach Linux 3.0 or 4.0, things might settle down some. Then, a rewrite might be smart. Code that evolves is inherently going to have inefficiencies and redundancies, because nobody can track every possible interaction between every possible combination of blocks of code.


    In consequence, yes, I think it would be smart to stop at Linux 4.0, deconstruct the kernel and then reassemble. That would be a good time to do a thorough security audit, too. Then we've got a stable base to start the rapid evolution all over again.


    The problem with evolving code is that the number of potential interactions rises with the factorial of the number of blocks of code. This means that, beyond a certain point, it's impossible to maintain. By "resetting" the code to a stable state, you can get round that problem to some degree. You still can't increase complexity forever, but you can raise the upper limit.


    The problem with a purely designed piece of software is that it's very hard to change the design midway. This means that it's great for producing static results, or a stable starting point, but it is useless for dynamically updating the code.


    Finally, OSDL doesn't have the money or the manpower to do a rewrite of the Linux kernel. Do you realise how large the kernel is, these days? Linux 2.6.11-pre1-mm1 is 22,892,878 lines long. Every block of code in that would need to be cross-referenced with every patented algorithm, to be sure Linux was IP-violation-free. I don't know how many patents there are for algorithms, software and "business methods", but it's probably in the hundreds of thousands, maybe the millions.


    Let's say that there's an average of a thousand lines per block, and ten thousand business methods. Then you'd need to perform almost 229 million comparisons. By hand, as a computer can't compare two abstract concepts for similarity.


    If OSDL employed 10% of the entire population of America, they could probably manage it within a year and keep in step with all the patches that are being submitted. If OSDL could afford to hire 10% of the entire population, they could afford to buy SCO. And IBM. And Microsoft. And every other damn computer software and/or hardware manufacturer in the US. At which point, why would they care about patents? They'd own them all.

    --
    It's a small world and it smells funny; I'd buy another if it wasn't for the money; Take back what I paid (SoM)
    1. Re:It is, that's why so many are screaming by Donny+Smith · · Score: 1

      > a little old - there are sections of the IPv4 code which haven't been touched in 2-3 years.

      Personally I would barely _consider_ using* anything that's newer than 2-3 years.
      Shiiit, I bet they've barely debugged it properly for production use!

      * Talking about servers here (I haven't considered using Linux on desktop yet..)

      > This means that, beyond a certain point, it's impossible to maintain... If OSDL employed 10% of the entire population of America, they could probably manage it within a year and keep in step with all the patches that are being submitted.

      I entertained myself with such idea a while ago; I think there's my comment somewhere on this site where I mentioned "Slave to The Kernel" as a SF scenario where the humanity becomes enslaved by the huge (random huge number here) Linux OS (or kernel if you will).
      It's been a while since I read about long-term computing trends but the whole concept of the operating system seems really outdated. I mean, just imagine how little OS have changed since first UNIX. We still have to work with (edit and such) configuration files - how backward is that!
      I will be surprised if OS as we know them survive beyond 2020.

  41. In EU we don't care by pioppo · · Score: 1

    yet...

  42. You bet... by Wooky_linuxer · · Score: 1

    Cause I've just patented ALL "hello world" programs... let me se... 1.Patent trivial program 2.??? 3.Profit!

    --
    Where is that guy who'd die defending what I had to say when I need him?
  43. OSDL Official by Magickcat · · Score: 1

    What the hell is an"OSDL official"?

    --

    Si tacuisses philosophus mansisses. If you had kept quiet, you would have remained a philosopher.

  44. 88 - hh - terrible by Velmont · · Score: 1

    I wouldn't call 88 really unlucky :] It is often used my new nazis in their nicks; e.g. Velmont88, 88 -> HH, -> Heil Hitler. Well. That's just a use. But it is to signify something secretly..... Or maybe it's just a bunch of guys born i 88' who tend to be very nazi :p

  45. Should I worry? by sharkey · · Score: 1
    run it with an interpreter

    "Hola mundo"

    --

    --
    "Outlook not so good." That magic 8-ball knows everything! I'll ask about Exchange Server next.
  46. Re:That's a shame (huhwhat?) by ultranova · · Score: 0, Flamebait

    Meh, the whole kernel is stuffed with x86 specific cruft. Despite people constantly cheering all the platforms it "runs" on (IMO there's more to running than just bootstrapping),

    Really ? So what are the specific issues on non-x86 systems that prevent anything besides bootstrapping on those systems ?

    the focus has been on x86 from day one.

    And this is bad because ?... x86 family of processors do run most desktops in the world, you know. And before someone starts trolling about Linux not being ready for desktop, I'd like to point out that I'm writing this very message on a GNU/Linux system, so it's ready for my desktop, at least...

    I, for one, welcome development focus and optimizations for my specific platform.

    There's no point on discussing stuff like this on slashdot, hardly anyone here knows shit about linux, or computers in general.

    Witness the difference between words and deeds of the Anonymous Coward.

    Bunch of know-nothing know-it-alls.

    Watch it with the flamebait, you trolls are vulnerable to fire.

    --

    Forget magic. Any technology distinguishable from divine power is insufficiently advanced.

  47. Re:From the does-it-run-linux dept. by Anonymous Coward · · Score: 0

    Chauvinist pig!

  48. rebutted by anonymous sources by Anonymous Coward · · Score: 0

    Um, did you actually RTFA? There's no actual denial from anyone from OSDL, despite what the misleading headline says. It's all he-said she-said they-said junior-high crap.

  49. Re:Same Principle. Different Day by LittleLebowskiUrbanA · · Score: 0, Flamebait

    He lies non-stop and spins the truth. Plus he's a fat douche bag.

  50. Linux has gone mainstream by Anonymous Coward · · Score: 0

    I remember win98 when everybody said dump netscape and use IE it's so much better "loads so much faster", (now it sucks) most of you did change browers and thought IE was awesome. Fast forward to 2005 now it's firefox, same story different browser(or os, 95-98 was cool the whole world should change to what you use).

    "You just don't get it do you Earl"

    You think you're so cool because you post to slashdot. You're just so techy(tacky).

    By the way the story was bull, but don't you think it's awsesome that if oss is infringing on anyone's patents it can be changed to take that company out of the oss equation. (free and open "not as in beer" software)

    I for one welcome our new linux overlords

    Just my 2 senses
    Gunillablue

    1. Re:Linux has gone mainstream by Anonymous Coward · · Score: 0

      I have no idea what you just said.

  51. Re:That's a shame (huhwhat?) by aichpvee · · Score: 0
    Really ? So what are the specific issues on non-x86 systems that prevent anything besides bootstrapping on those systems ?

    It won't even bootstrap on my TI-99/4a. So I'd say that's a pretty big issue...

    --
    The Farewell Tour II
  52. In other news. by twitter · · Score: 1
    I'm pretty unsure that you can write any computer program of complexity beyond 'hello world' without infringing on at least one software patent.

    Several honest lawyers are trying to make a patent that does not infringe on any known computer program.

    --

    Friends don't help friends install M$ junk.

  53. Are you illiterate? by A+nonymous+Coward · · Score: 1

    what reason do I have to take PJ's word over O'Gara's?

    Any literate person can read articles written by both of them, see which ones have references and are internally self-consistent, and pretty easily decide who is lying thru her teeth.

    Anyone who considers O'Gara reasonable probably also thinks Fox is fair and balanced.

  54. Hello World is probably out too - its an ad slogan by Dr.Knackerator · · Score: 1

    http://www.travelocity.co.uk/ are using "hello world" as their ad slogan.

    they are probably going to start suing programming books soon....

  55. Last name: Munch by Anonymous Coward · · Score: 0

    By the time discovery is finished in the lawsuit, the code
    will have been changed/replaced anyway. You can't
    sue a boson, it doesn't live long enough.

  56. mod this fucker up! by Anonymous Coward · · Score: 0

    - who gives a fuck about patents, etc.?

  57. Re:That's a shame (huhwhat?) by jr87 · · Score: 1

    what arch are you talking about? some patch sets don't do well on other archs... but I have gotten linux to work well on x86, amd64, ppc, and sparc...that's pretty damn good if you ask me (preemptive kernel sometimes will make things more unstable though)

  58. Re:It's called VMWare by sloanster · · Score: 1

    It's called VMWare

    I've used vmware, but find it to be just a bit on the pricey side, and not a perfect solution. I've also run win4lin, and while it was pretty nice, it was dependent on a kernel patch, and IIRC was limited to win98...

  59. Re:From the does-it-run-linux dept. by Anonymous Coward · · Score: 0

    OK. This HAS to be said. How many guys here on Slashdot are into female domination? It's obvious that someone here is posting what they believe to be female domination troll fantasies. So, thinking about what geeks tend to like, I have to guess that a lot of them like femdom? I was hoping this wasn't true because frankly I find it frightening that so many men would want to have a woman treat them in such a denigrating manner. Especially when a lot of geeks tend to be the "nice guys". On the other hand, I'll bet a lot of dommes would easily let a jerk of a guy treat them like shit. It doesn't make sense. Not one bit. I will go first. I'm not into femdom at all. I think it's a sick and degenrate practice that is the revenge for the way jerky men have treated women for years. So now, the nice geeky guys have to pay the bill for the assholes? Not me. I'm perfectly happy to keep things as traditional as possible. Femdom is just for sickos in my book.