Slashdot Mirror


Android and the Linux Kernel Community

An anonymous reader links to Greg Kroah-Hartman's explanation of a rift (hopefully mendable) in the development culture of Google's Linux-based Android OS and the Linux kernel itself. "As the Android kernel code is now gone from the Linux kernel, as of the 2.6.33 kernel release, I'm starting to get a lot of questions about what happened, and what to do next with regards to Android. So here's my opinion on the whole matter ..."

354 comments

  1. Google by sopssa · · Score: 4, Interesting

    Because Google doesn't have their code merged into the mainline, these companies creating drivers and platform code are locked out from ever contributing it back to the kernel community.

    Google shows no sign of working to get their code upstream anymore.

    Oh come on, was it really a surprise to anyone that Google does only care about OSS when it suits them and drops out instantly when it doesn't. All of their own sites, business and back-end technology is just as closed as Microsoft's.

    I see someone coming along and saying "but they contribute to open source!". Sure, they do, they release little snippets of code and open source those products they base on OSS code because they have to by GPL. One could seriously argue if their open sourcing efforts are making better open source community in general, or not. Like TFA states, their ignorance has caused more turmoil than ever before in Linux land. Companies are obviously going to create support and drivers for Android-branch of Linux kernel, but cant contribute the same code back to real Linux kernel. And possibly never will because it costs them too much work, money and time. Even those companies that previously did develop linux drivers. That's not harming Linux and OSS community?

    Get off your lazy ass and see what's really happening.

    1. Re:Google by Colin+Smith · · Score: 1

      That's not harming Linux and OSS community?

      No, it isn't, because there is open competition from other vendors. The only group it's harming is Google and those companies dumb enough to buy into Android for their future.

       

      --
      Deleted
    2. Re:Google by sopssa · · Score: 2, Interesting

      The only group it's harming is Google and those companies dumb enough to buy into Android for their future.

      Google has a major advantage here as one of the largest companies in the world, and those companies "dumb enough" are going to jump on Google's side because they have the market share.

    3. Re:Google by killmenow · · Score: 5, Funny

      Apparently Google employees have mod points today.

    4. Re:Google by CSHARP123 · · Score: 3, Insightful

      It is called Embrace, Extend and Extinguish. I thought it only applies to MS. Well I think, Do no Evil is gone through the window :)

    5. Re:Google by 0100010001010011 · · Score: 1

      "If". "If linux was under"

      No more happy hour for me.

    6. Re:Google by Colin+Smith · · Score: 5, Interesting

      Google has a major advantage here as one of the largest companies in the world

      Nokia has the major advantage that they are *the* largest phone producer on the face of the planet and have *the* largest world market share by a large percentage. Google and particularly, Android are small fry in comparison, despite their size in other markets. Those companies jumping on Android are dumb because their horizon is limited to the US market and a single platform.

      For irony, Google "Maemo" and "Nokia N900".

      As I said, the only groups being hurt by this are Google and those dumb enough to rely on Android for their future, anyone else with a brain will take a look at the competition and more open platforms.
       

      --
      Deleted
    7. Re:Google by sopssa · · Score: 0, Troll

      As I said, the only groups being hurt by this are Google and those dumb enough to rely on Android for their future, anyone else with a brain will take a look at the competition and more open platforms.

      Is that why we already succeeded at Year Of Linux On Desktop back in 2003?

    8. Re:Google by Score+Whore · · Score: 3, Insightful

      This is some seriously poor logic. Consider for a moment GM. In 2008 they were the 4th largest company in the United States. By your logic it would be ideal to attach your company's future well being to GM. Now consider how well that worked out for over 1000 GM dealers, hundreds of parts suppliers, etc. See how that turned out. For the record, Google was #117 in 2008.

    9. Re:Google by gyrogeerloose · · Score: 5, Informative

      It is called Embrace, Extend and Extinguish. I thought it only applies to MS. Well I think, Do no Evil is gone through the window :)

      Well, we know what Steve Jobs said about Google's "Don't Be Evil" mantra--"It's bullshit." Or, "a load of crap," depending on your source.

      --
      This ain't rocket surgery.
    10. Re:Google by Colin+Smith · · Score: 5, Insightful

      Is that why we already succeeded at Year Of Linux On Desktop back in 2003?

      Haven't you noticed? The desktop is irrelevant. It's been abstracted to an Internet access platform. It's the phone in the pocket which is the current battleground, and Linux has won that already.

       

      --
      Deleted
    11. Re:Google by Anonymous Coward · · Score: 0

      Maemo FTW!

    12. Re:Google by h4rr4r · · Score: 4, Informative

      If linux was under the BSD license it would be in the same shape FreeBSD is in, nearly no one using it in the server room.

      So sure we have to wait for btrfs instead of using ZFS, but only because SUN decided to make sure they chose an incompatible license.

    13. Re:Google by GenP · · Score: 5, Funny

      I want ZFS for my home server, zfs is not the answer

      Very Zen.

    14. Re:Google by ClosedSource · · Score: 2, Insightful

      The problem is the idea of a single code base that will satisfy all needs is a pipe dream and always will be. Developers may have to do some extra work to write appropriate drivers for both trees. Welcome to the real world.

    15. Re:Google by nietsch · · Score: 0, Flamebait

      Well good on ya! Drop it if you like, or make it into a balmerbot and let it throw chairs at your Linus idol, I don;t really care (but I do want to see the vids though:). Linux is available in a LOT of different flavours. The free BSD's however have much less mind and market-share. Yes you may argue OSX is a BSD variant, but there you have a company that is more evil then google IMHO.
      Nobody forced them to built on a linux kernel, they choose that one partially because it was Open and Free. On top of that they built an operating system that they could have kept very closed. (The GPL kernel does not imply anything about the licence of the software that runs on top of it), but they chose not to.

      --
      This space is intentionally staring blankly at you
    16. Re:Google by Anonymous Coward · · Score: 0

      Well, so do I, so I give your post and the parent's a bump up.

      Fuck 'em, that's what I say.

    17. Re:Google by 0100010001010011 · · Score: 1, Funny

      zfs-fuse. Bah. I quit.

    18. Re:Google by Lunix+Nutcase · · Score: 1

      It's the phone in the pocket which is the current battleground, and Linux has won that already.

      That's funny cause Symbian owns 50% of the smart phone market.

    19. Re:Google by Anonymous Coward · · Score: 0

      While I dont generally agree with Apple's saying it is great people are starting to see this.

    20. Re:Google by shutdown+-p+now · · Score: 3, Insightful

      Sure, they do, they release little snippets of code and open source those products they base on OSS code because they have to by GPL.

      Erm, no. While I don't consider Google to be a particularly charitable organization, they do regularly open source their products (though mostly minor ones, as you rightly pointed out) when there is no legal obligation on them to do so.

      The reason for that is perfectly clear, too: it strengthens the image of Google as both "geeky" and "open" tech company, which are both important parts of Google's public image.

    21. Re:Google by diegocg · · Score: 1

      Hey, Google doesn't need to contribute back their code to the Linux main tree. It's perfectly fine not try to merge it. But because it makes sense for everyone (end users, Google, Android developers, hardware manufacturers), people is trying to fix the situation. Maybe you don't care about working together, but Linux people do.

    22. Re:Google by Sinning · · Score: 2, Interesting

      Down from over 63% in 2007. Symbian is losing ground quickly.

    23. Re:Google by exomondo · · Score: 2, Insightful

      Well, we know what Steve Jobs said about Google's "Don't Be Evil" mantra--"It's bullshit." Or, "a load of crap," depending on your source.

      Is that actually based on anything though? You have to remember that 'evil' is a point of view and when a company gets that large and that diversified obviously they are eventually going to step on the toes of someone who has a different interpretation of what is 'evil'.

    24. Re:Google by Anonymous Coward · · Score: 0, Insightful

      Sorry, I haven't noticed.

      Please elucidate. Please give me a list of the top three Linux devices and their sales volumes compared to, say, symbian, rim and iPhone.

      Or perhaps you can explain some of these http://w3counter.com/globalstats.php stats and how Linux, Android and WAP come in at less than 2% with regard to your "irrelevant" statement.

      Dammit, you're trolling, aren't you? Well... Fool me once, strike one, fool me twice, strike, uh three.

    25. Re:Google by Anonymous Coward · · Score: 0

      I also had mod points, but I bumped you down to encourage the Google conspiracy theorists. It's nice to have some of the attention off of me for a change.

      -Steve B.

    26. Re:Google by MichaelSmith · · Score: 1

      Google has a major advantage here as one of the largest companies in the world

      Nokia has the major advantage that they are *the* largest phone producer on the face of the planet and have *the* largest world market share by a large percentage.

      Yeah but that is mainly because of their hold on the market for cheap, dumb phones. The smartphone market is really a different beast now.

    27. Re:Google by gyrogeerloose · · Score: 1

      Is that actually based on anything though? You have to remember that 'evil' is a point of view and when a company gets that large and that diversified obviously they are eventually going to step on the toes of someone who has a different interpretation of what is 'evil'.

      Just so we understand each other, I'm not necessarily advocating Jobs's position, just quoting him. But I think that what you're saying is pretty much in line with what Jobs said, which is not that Google is evil, only that "Don't Be Evil" isn't really applicable.

      --
      This ain't rocket surgery.
    28. Re:Google by Anonymous Coward · · Score: 0

      "and Linux has won that already."

      You mean Android (Linux+dVM).

      From a business standpoint, it makes sense for Google to fork Android since the kernel is more focused on the desktop--which is yesterday's news, and of course LKF/Linus would want to strip out the Android stuff from the Kernel since it has no F/OSS maintenance purpose.

      Look at the business world, it appears it's gonna be a Linux(IBM), OpenSolaris(Oracle), and Microsoft world, and we know IBM will muck things up with too much complexity that linux will not be 'linux' when you get it. Unless Mameo takes off, Linux is becoming irrevelant, since yes, the desktop is going away, well, maybe except for games.

    29. Re:Google by sopssa · · Score: 0, Flamebait

      Eh, trolling much? If you look outside US, Nokia is dominating. iPhone is nowhere as successful as it is in US. In top of that, Nokia holds patents (that they really deserve) over many technologies used with GSM, 3G and so on.

      And Nokia offers a real Linux phone, not just Android or locked-down iPhone shit.

    30. Re:Google by DangerFace · · Score: 4, Interesting

      Well, we know what Steve Jobs said about Google's "Don't Be Evil" mantra--"It's bullshit." Or, "a load of crap," depending on your source.

      Is that actually based on anything though?

      Yes - it's based on one rich guy being annoyed that another rich guy threatened to take some of his richness. From the linked article:

      On Google: We did not enter the search business, Jobs said. They entered the phone business. Make no mistake they want to kill the iPhone. We won’t let them, he says. Someone else asks something on a different topic, but there’s no getting Jobs off this rant. I want to go back to that other question first and say one more thing, he says. This don’t be evil mantra: “It’s bullshit.” Audience roars.

      Steve Jobs wasn't making some deep point about Google's manipulation of FOSS, he was just ranting about unfair competition (for 'unfair competition to Apple in the eyes of Steve Jobs' read 'Giant, friendly, happy-go-lucky Silicon Valley company treating design and user experience as important'). He may as well have just complained that Google won't share their toys.

    31. Re:Google by jeffmeden · · Score: 1

      So sponsoring the "Summer of Code" doesn't count as contributing? Seeing as how they have paid for development time on hundreds (if not thousands) of good projects? What have you done for Open Source lately?

      Yes, their behavior with regard to the code going into their products does not really embrace the open source model, but given the constraints they are under to protect their core business IP, can you blame them?

      It seems like the best thing that can happen is for Google to maintain the Android changes on their own. It sacrifices the portability of drivers written for the android flavor, but are you really planning on hacking the mainstream kernel to run on your smartphone? As long as the software stays public, lets avoid reinventing the wheel and let Google do what they need to do to make a competitive product.

    32. Re:Google by t0p · · Score: 1

      You naive fool. The desktop isn't dead. "Cloud computing" isn't anywhere near ready. And the mobile phone isn't as important as you seem believe... yet. Google is a major force in computing, and either you're pretending you don't get it, or you're an idiot.

      --
      http://ihatehate.wordpress.com
    33. Re:Google by Enderandrew · · Score: 4, Interesting

      They don't support OSS when it doesn't suit them?

      They pay the salaries of guys like Andrew Morton and then cut him free to work on Linux as he sees fit, basically just answering to Linus.

      They pay for projects like the Summer of Code, paying for the development of projects they don't use internally.

      They released patches for projects like Wine well before they were using Wine in any releases of their projects.

      You claim they only release code when they have to. They were never required to create an OS. Are you aware the Chromium browser code is BSD released, right? It wasn't like they just wanted to build upon some GPL project and then were required to stick with GPL. They build a whole new browser, and opened it up BSD so anyone can use the code however they want. How is that closed?

      Look what they're doing with Wave. They developed an entire protocol from the ground up. The protocol and all the server code is open. They could have tried to patent the protocol and charge for licensing. They're just releasing the whole thing and telling people to do whatever they want with it completely for free.

      What about protocols like SPDY they wrote from scratch and released for free? What about their various hardware designs for power supplies they've released for free? These are things that give them a competetive edge. If anything, most people would argue it hurts them to give them away for free, but still they do it. They rarely get credit for how many things they open up. And yet the very communities Google helps finance and take care of turn around and slam Google. Do you realize who your allies are in the FOSS world?

      You claim they're just as closed as Microsoft?

      Pure lies and trolling. Seriously, shut the hell up.

      --
      http://blindscribblings.com - Tasty pop-culture in conceptual fashion.
    34. Re:Google by ajs · · Score: 4, Insightful

      Oh come on, was it really a surprise to anyone that Google does only care about OSS when it suits them and drops out instantly when it doesn't. All of their own sites, business and back-end technology is just as closed as Microsoft's.

      Point 1) how is not pushing to mainline code "dropping out" of open source development exactly?

      Point 2) The Common Android Kernel tree is browsable, and looks to be fairly easy for anyone to take advantage of. The complaint here seems to be that Google isn't putting in enough work to merge their Linux kernel changes into the mainline, not that they have failed to release anything in a usable way. I find it somewhat disingenuous to slap down an open source contributor for failing to do our work for us.

      Point 3) Microsoft's services are just as open?! Great, where is Microsoft's instructions on how I can export all of my data from all of their services in open formats? Google provides that so I'm certain you're aware of where Microsoft publishes such information as well... Oh and while you're at it, how many open source projects do Microsoft projects contribute to? Python, Linux, and dozens of other existing projects get updates from Google and they've released more open source software of their own making than anyone else.

      So, what company have you been watching that confused you so badly that you thought Google wasn't the single largest benefactor open source has?

    35. Re:Google by Enderandrew · · Score: 4, Interesting

      What people seem to overlook is that Google wrote Android on their dime, opened it up, and then handed it over to the Open Handset Alliance, which has companies like Nokia on the board. Google does not own and control Android. The Alliance does.

      And how is Android not open? The entire thing is FOSS.

      --
      http://blindscribblings.com - Tasty pop-culture in conceptual fashion.
    36. Re:Google by Temporal · · Score: 5, Informative

      Erm, no. While I don't consider Google to be a particularly charitable organization, they do regularly open source their products (though mostly minor ones, as you rightly pointed out) when there is no legal obligation on them to do so.

      The reason for that is perfectly clear, too: it strengthens the image of Google as both "geeky" and "open" tech company, which are both important parts of Google's public image.

      It's not just public image. There's also the fact that Google is a company full of geeks, many of whom are open source fans in their own right.

      I was primarily responsible for Google releasing Protocol Buffers. I did it not for the sake of improving my employer's public image, but because I thought it was a useful tool that should be shared, and those around me agreed. Because of the bottom-up nature of decision making at Google -- and given that I was willing to do the work -- I had no trouble pushing this through.

      So yeah, it's pretty upsetting to me to see people say things like "Google does only care about OSS when it suits them and drops out instantly when it doesn't.". This kind of statement completely misunderstands how Google even works. This just isn't the kind of company where orders comes down from executives on high with the only motive being profit -- anyone who thinks otherwise obviously doesn't work here.

      Honestly, I think the main reason we haven't released more stuff is because it's kind of a lot of work (as I have learned). Dumping code over a wall does not please the open source community -- you have to maintain it; document it; test it on a zillion platforms; answer e-mail from people who think they are not just entitled to your code, but are doing *you* a favor by using it; review patches from college kids who don't really know what they're doing; etc.

      (Oblig. disclaimer: These are my own personal opinions; I am not authorized to speak for my employer.)

    37. Re:Google by Anonymous Coward · · Score: 1, Insightful

      Yeah but that is mainly because of their hold on the market for cheap, dumb phones.

      What, you mean by far the most popular phone choice across the world? Not everyone wants a smart-phone or to be held ransom with exorbitant data plans to use the expensive device. The vast majority of the world uses phones to talk, how strange.

    38. Re:Google by twistah · · Score: 1

      Did you forget about the Google Summer of Code and multiple other projects where they basically fund the development of OSS tools?

    39. Re:Google by oztiks · · Score: 1, Offtopic

      I started a comment with the sentence "The good thing about the iPhone ..." in a prior Google / Android article and what did i get for my troubles? an instant ... Troll

      Make no mistake, Googles hidden geek mafia run this here town.

    40. Re:Google by Enderandrew · · Score: 2, Insightful

      Please spend two minutes looking at Google.org.

      --
      http://blindscribblings.com - Tasty pop-culture in conceptual fashion.
    41. Re:Google by ajs · · Score: 4, Insightful

      Google's "Don't Be Evil" mantra--"It's bullshit."

      What's sad is that, here on Slashdot, we run with the worst possible interpretation of everything.

      So, what started as one non-Google developer deleting some Android-specific drivers from Linux (mind you, leaving in massive amounts of upstreamed work from Google, this is just the small Android-specific bits) becomes "Google is abusing the open source community and is now evil."

      Sad, just sad.

    42. Re:Google by ajs · · Score: 1

      they do regularly open source their products (though mostly minor ones, as you rightly pointed out)

      And if we look at reality:

      Conservatively, we've released about 14 million lines of code. Android tops 10 million lines of code, and then you have Chrome (2 million lines of code), GWT (300,000 lines of code), and about a project released every week over the last five years. Then you have a couple hundred Googlers patching on a weekly or monthly basis.

      Source: http://news.cnet.com/8301-13505_3-10354530-16.html

      It's hard to imagine that doing a quick Google search (or Yahoo or Bing or whatever if you feel that there's a conflict of interest) would have hurt, here.

    43. Re:Google by Lunix+Nutcase · · Score: 2, Insightful

      But which hardly translate to Linux having "won that already" when their combined percentage is around 10%.

    44. Re:Google by Thantik · · Score: 1, Informative

      Care to explain why I don't see symbian or rim browsers on that list at all? It's because those are WEB BROWSER STATISTICS...Oh, yeah, that's why you posted as AC.

      The mobile phone market in regards to *web page statistics* is a horribly inaccurate way to measure penetration of said devices. Sure, I can pull up any damn statistic I want and say that it means what I want it to mean, but it doesn't mean that it holds water.

      I'd guess there is some very close competition in terms of sales of *NEW* devices, between iPhone and Android. The benefit android has is that you can chose ANY carrier you wish. iPhone your just stuck with AT&T (in the USA) and my own anecdotal evidence amongst friends shows that they're ditching iPhone in droves. But that's just anecdotal evidence. Linux is indeed a contender.

    45. Re:Google by MichaelSmith · · Score: 1

      Yeah but that is mainly because of their hold on the market for cheap, dumb phones.

      What, you mean by far the most popular phone choice across the world? Not everyone wants a smart-phone or to be held ransom with exorbitant data plans to use the expensive device. The vast majority of the world uses phones to talk, how strange.

      True but not relevant to this discussion.

    46. Re:Google by MichaelSmith · · Score: 3, Informative

      Eh, trolling much? If you look outside US, Nokia is dominating. iPhone is nowhere as successful as it is in US. In top of that, Nokia holds patents (that they really deserve) over many technologies used with GSM, 3G and so on.

      And Nokia offers a real Linux phone, not just Android or locked-down iPhone shit.

      Well I live in Australia and the iPhone is very popular. Most people who want a smart phone will have an iPhone. Many older people who just want to make calls will have a $50 nokia. I use an openmoko, which is also a real Linux phone.

    47. Re:Google by shutdown+-p+now · · Score: 1

      I can dig you similar links for most large companies in the field. For example, here's one for Microsoft (it's not the only thing, just the first one that popped up on Google; you can find more in the same way if you're interested).

      Yet, do you consider Microsoft a charity?

    48. Re:Google by shutdown+-p+now · · Score: 0, Troll

      I was specifically talking of products for which Google released the source when they were not obligated to do so (since so was GGP). In case of Android and Chrome, they build on existing [L]GPL'ed codebases (Linux and WebKit, correspondingly), so Google didn't have a choice of not releasing the source there. Well, I guess they could try to separate their code changes as much as possible, so that they wouldn't have to release them under GPL, but it's probably a lot of effort for little worth.

      Nah, I'm speaking of Google products that are developed entirely in-house. Where is the source for the search engine itself? GMail? even for desktop applications only, where's the source for Picasa or Google Toolbar?

    49. Re:Google by unix1 · · Score: 1

      So, what are you saying - that Motorola should reach out to Nokia and hope that Nokia, out of goodness of their heart, will throw their competitors a bone? Nokia has no interest in having their competitors succeed.

      Google, on the other hand, has an interest in making their platform succeed for all phone manufacturers because the more phones those manufacturers sell the more they stuff Google's pockets with online services revenue.

      Don't get me wrong, I like Maemo and I love Qt (it's one of the best and easiest programming toolkit I've used); but I'd love to hear how Nokia's platform(s) are any "more open" than Android. Because Symbian definitely is NOT.

    50. Re:Google by kwerle · · Score: 1

      Oh come on, was it really a surprise to anyone that Google does only care about OSS when it suits them and drops out instantly when it doesn't. All of their own sites, business and back-end technology is just as closed as Microsoft's.

      http://golang.org/

      Where's the open source c# compiler from MS?

      Though it certainly isn't clear how much (if any) they are depending on go.

      I'm just picking one example, here.

    51. Re:Google by bonch · · Score: 1, Insightful

      Linux won? Citation, please.

    52. Re:Google by Microlith · · Score: 5, Insightful

      And how is Android not open? The entire thing is FOSS.

      I wondered that myself when looking into the N900, and the explanation as to why Android is not open is because while it is Open Source, it does not have an open community.

      If you look at the OHA FAQ, they explain why an open platform is good for everyone EXCEPT the end-user. Unless you mistake who your customer is, you'd realize that the end-user's input is just as important as those who apply your OS to their device. Both the OHA and the cell vendors make that mistake, as the OHA thinks the user of Android is the handset maker, who themselves think their customer is the carrier. The only true customer is the person who pays for and uses the device in the end, and they should be able to have input into their device and its OS should they care.

    53. Re:Google by sopssa · · Score: 0

      While I did a little bit exaggerate there (Google has seriously opened up some cool techs), the fact that they're sometimes only partly opened them (which I understand, they need to hold to their main business), the fact that Google is financially mostly supported by advertising and the fact they're wanting to be everywhere makes it a little bit worrying. And how the press releases always state how everything should be open sourced, but never mention that Google itself doesn't like to open source the parts that are within their business.

      That imo is also the reason why Google can support open sourcing a lot in general. It doesn't interfere with their main business and helps to fight with their (mostly closed source) competitors.

      But what comes to TFA, the guy was ready to work with Google to put those patches in the main Linux kernel, and I think it would be reasonable to do so. I agree that theres a lot of overhead in publishing code to open source, but there are people who are willing to help doing it for free.

    54. Re:Google by Anonymous Coward · · Score: 0, Troll

      It is called Embrace, Extend and Extinguish. I thought it only applies to MS. Well I think, Do no Evil is gone through the window :)

      Well, we know what Steve Jobs said about Google's "Don't Be Evil" mantra--"It's bullshit." Or, "a load of crap," depending on your source.

      Considering it's coming from the CEO of one of the single most evil US companies, I think by "bullshit" he means, "it's bullshit that a business would try to operate based on anything other than trying to increase profit. It's their problem, and that's why we're going to win," not "bullshit" as in "they're not trying to not do evil."

    55. Re:Google by Microlith · · Score: 1

      The complaint here seems to be that Google isn't putting in enough work to merge their Linux kernel changes into the mainline

      Then they won't be merged.

      I find it somewhat disingenuous to slap down an open source contributor for failing to do our work for us.

      Whoever picks it up and puts it into the kernel becomes the maintainer. And no one is responsible for the code but the author or whomever he delegates. It is not "our work," if Google wants it in the kernel they (or someone they designate) has to put in the effort to get it in and keep it up to date. Every other company that contributes code does this, why is Google special?

    56. Re:Google by the_enigma_1983 · · Score: 1

      I dunno, maybe I'm misreading TFA, but it seems to say that the "entire thing" is not open, that Google is not disclosing full source which is "part" of the reason for not including android code in the linux kernel. Another part seems to relate to no one being willing to "clean up" the code which has been released, and there are possibly other parts to it.

    57. Re:Google by Anonymous Coward · · Score: 0

      Second paragraph says "Linux is not relevant in unit sales." This means *NEW* devices.

      Third paragraph says "Linux is not relevant as a reported browser platform" irrespective of sales.

      Your "guess" is not of interest without supporting evidence.

    58. Re:Google by ckaminski · · Score: 1

      Hence the whole hulla-bulloo over BTRFS. If Linux had a license compatible with ZFS, then this wouldn't be an issue. But it's not, so they have to do a clean-room implementation of the whole thing. Nevermind the wars about VFS layering, and whether a filesystem should be doing snapshotting and volume management or not.

      I so wanted to run OpenFiler for my NAS. But their lack of support for CF media drove me to EON (OpenSolaris) with my 6TB RAIDZ2 array. FreeNAS still has ZFS as experimental, and I'm just not ready to trust experimental to my data.

    59. Re:Google by bonch · · Score: 1

      No one is using FreeBSD in the server room? What are you smoking?

    60. Re:Google by ckaminski · · Score: 1

      That has nothing to do with the Kernel, and everything to do with the myriad of packaging issues.

    61. Re:Google by Anonymous Coward · · Score: 1, Interesting

      Actually if Linux was under the BSD license Google could have taken what they wanted, changed what they wanted, and never have released the code at all. In that case there would be no open source Android project to contribute to. Would that be better? Ask 20 people who know something about the internals of BSD and Linux which has a better code base and better technology and probably 60%+ would say BSD. Why is it not as popular as Linux? Because a lot of companies would never release code under the BSD license and take the chance that a competitor would take that code, improve it, and release a proprietary app with it. The GPL keeps companies in a share and share alike truce.

    62. Re:Google by Anonymous Coward · · Score: 0

      I see, you didn't actually look at the whole web page, did you. Go back and look at the panel that gives OS stats.

    63. Re:Google by ducomputergeek · · Score: 3, Interesting

      Server room, depends. Desktop, BSD is still beating Linux (Thanks to Apple.) Where BSD has found a niche is in Network appliances such as routers and firewalls. FBSD still has a superior networking stack from what I've seen. I know we use pfSense around here and Monowall before that. We also deploy Juniper networking equipment and JunOS is based on FreeBSD.

      We actually deploy all our production servers on FreeBSD including our PostgreSQL and MySQL database servers. And they do so with rock solid realiability. The only time I can think of boxes crashing had to do with hardware failures. Including a couple boxes that were still running FBSD 6.x. We didn't bother taking them offline to upgrade until we replaced the hardware.

      --
      "The problem with socialism is eventually you run out of other people's money" - Thatcher.
    64. Re:Google by Anonymous Coward · · Score: 0

      Nokia is not part of the Open Handset Alliance, Nokia has there own linux mobile os that they are using in Maemo

    65. Re:Google by adamofgreyskull · · Score: 4, Funny

      Because of the bottom-up nature of decision making at Google

      (Oblig. disclaimer: These are my own personal opinions; I am not authorized to speak for my employer.)

      So just authorise yourself, right? ;)

    66. Re:Google by Enderandrew · · Score: 1

      Anyone can submit patches upstream to Android's code base. You can compile your own fork, and then flash your phone with it. The SDK is free. People are already distributing modified versions of it.

      It doesn't have a huge community of OSS developers, but that doesn't mean that Google or the OHA failed to do anything.

      --
      http://blindscribblings.com - Tasty pop-culture in conceptual fashion.
    67. Re:Google by dangitman · · Score: 2, Funny

      Apparently Google employees have mod points today.

      Well, duh. Google employees always have mod-points. Where do you think slashdot gets them from in the first place?

      --
      ... and then they built the supercollider.
    68. Re:Google by Weezul · · Score: 1

      iPhone isn't exactly dominating inside the U.S. either, except amongst the hipsters, try blackberry.

      I know fairly few techie people abroad, well my foreign friends are mostly women that I was trying to sleep with while living in their countries, but the few I know all own Nokia's, true. Btw, I know more iPod Touch owners abroad than iPhone owners, mostly people who wanted the games mp3 player combo, without killing their phone's battery.

      --
      The Christian religion has been and still is the principal enemy of moral progress in the world. -- Bertrand Russell
    69. Re:Google by Enderandrew · · Score: 1

      Google.org is legally recognized as a charity. They've given away over 100 million already. In addition to handing out money, they also utilize Google's resources to help research.

      The OP stated that Google isn't a particular charitable organization.

      Have they open sourced hardware designs to try and reduce power usage around the world?

      Have they released open protocols like SPDY and Wave without any patents hanging off them?

      Do they sponsor Summer of Code?

      Have they offered up major projects like Chromium Browser under a BSD license for anyone to use however they want?

      These all seem like charitable contributions.

      --
      http://blindscribblings.com - Tasty pop-culture in conceptual fashion.
    70. Re:Google by Anonymous Coward · · Score: 0

      Shhh! The NetBSD guys might hear you.

    71. Re:Google by dangitman · · Score: 1

      Are you aware the Chromium browser code is BSD released, right? It wasn't like they just wanted to build upon some GPL project and then were required to stick with GPL. They build a whole new browser, and opened it up BSD so anyone can use the code however they want.

      Uh, Chromium is based on WebKit, so no, they didn't build a whole new browser.

      --
      ... and then they built the supercollider.
    72. Re:Google by Anonymous Coward · · Score: 3, Interesting

      Steve Jobs wasn't making some deep point about Google's manipulation of FOSS, he was just ranting about unfair competition (for 'unfair competition to Apple in the eyes of Steve Jobs' read 'Giant, friendly, happy-go-lucky Silicon Valley company treating design and user experience as important'). He may as well have just complained that Google won't share their toys.

      To be fair, there's a little more to it than that. Eric Schmidt, the CEO of said "giant, friendly, happy-go-lucky Silicon Valley company," was serving on Apple's Board of Directors while they were developing the iPhone. It's not hard to see why Steve Jobs might have taken it personally when he found out Schmidt's company also happened to be developing a touchscreen-based smartphone platform. The non-evil thing to do would have been for him to resign for the board as soon as it became clear Google would be competing with Apple, yet he stuck around until the secret was out.

    73. Re:Google by lien_meat · · Score: 1

      Also, lets not forget that (at least a year ago) something like 80% of Firefox's funding was from google. You could argue that it's only because firefox defaults to google for search...but funding 80% of their expenses is a pretty large stake in a company (firefox/mozilla) that doesn't really have to exist for google to still turn a huge profit. Especially now that chrome exists and is doing pretty well for itself. Yeah, they might stop funding firefox now that they have a competing product...but who cares...chrome is open too...and recently I'm actually really starting to like it more anyway.

    74. Re:Google by Temporal · · Score: 4, Informative

      But what comes to TFA, the guy was ready to work with Google to put those patches in the main Linux kernel

      I don't think the Android team would describe it that way. TFA doesn't really cover their side of the story. As is usually the case when two sides don't agree, the details are complicated. I'm not on Android so I'm not going to attempt to get into it, but they aren't particularly happy with the situation either.

    75. Re:Google by gyrogeerloose · · Score: 0, Flamebait

      Gee, Mr. Ballmer, I would have thought you had more important uses for your time than posting here on Slashdot. We here are flattered, however.

      --
      This ain't rocket surgery.
    76. Re:Google by adiposity · · Score: 1

      Hmm, do you think you could convince whoever works in the phone dept. to please enable bluetooth hands free dialing? Don't even have to implement it, just allow it.

      http://code.google.com/p/android/issues/detail?id=1181

      Thanks.

    77. Re:Google by hannson · · Score: 4, Insightful

      Yeah Steve's totally right there, Google definitely should have asked Apple for permission before developing the Nexus One or Android... just like Apple asked all the other phone companies for permission when developing the iPhone or the MP3 player manufacturers when developing the iPod..... oh wait... what a dick!

    78. Re:Google by Miamicanes · · Score: 3, Interesting

      > since yes, the desktop is going away,

      Oh pleaze. For all the buzz about "the desktop going away", the number of desktop computers seems to just keep growing. Homes that had one PC now have two. Or three. Individuals who had their own now have their own desktop PC and a laptop (or at least a netbook, which contrary to its name seems to end up spending at least as much "on" time doing stuff a few thousand feet above sea level, inside flying aluminum cylinders that are one of the last frontiers where internet access is still rare and expensive). Most of the people "making do" with a laptop as their only computer are people who formerly had no computer at all. The people who owned computers 15+ years ago won't give up their desktop until laptops routinely come with dual 24" displays and quad+core CPUs.

      Cloud computing is the new paperless office. As more than a few have observed over the years, the paperless office was officially welcomed 15 years ago, yet 21st-century offices still seem to somehow generate at least twice as much printed output per employee as they ever did in the dark ages. The main difference is that back then, the paper copies were carefully stored in file folders for future reference. Now, they're stored in the SAN, and four dozen copies get casually printed on demand so everyone can pretend to read them at the weekly status meeting & use them to scribble notes on before tossing them all in the big blue bin after lunch. I'm quite confident that when the day arrives that I have a hundred terrabytes of data stored "in the cloud", I'll have at least ten times as much physically present within my home.

      Desktops aren't going away anytime soon, any more than TVs with eight-foot screens are going to be displaced by personal media tablets. They might end up mutating into our own personal faux-clouds, perpetually connected to our PadPCs and phones, but at the end of the day, when you need to edit video (from the 25 years of videotapes you're still trying to digitize before they rot into grey digital goo), sort out 400,000 family photos digitized and captured over the years, do your taxes, and write cool software for your new phone to sell online for enough profit to buy a stale gumball from a vending machine, you're going to have one hell of a home PC that will make the most high-end PC available today look like a Commodore 64. With liquid nitrogen cooling to keep it from causing a mini fireball (it only throws off 10 watts of heat thanks to miniaturization & efficiency, but those 10 watts are concentrated in an area the size of a poppy seed).

    79. Re:Google by unfunk · · Score: 2, Informative

      As I said, the only groups being hurt by this are Google and those dumb enough to rely on Android for their future, anyone else with a brain will take a look at the competition and more open platforms.

      Newsflash: Consumers don't care about whether Google's playing nice with the Linux community or not.

    80. Re:Google by turbidostato · · Score: 1

      "If Linux had a license compatible with ZFS"

      You do know that ZFS became *after* Linux, don't you?

      It is ZFS the one with a license non compatible with that of Linux, not the other way around.

      And ZFS is non-compatible with Linux, license-wise, because that's exactly what Sun wanted so, again, don't blame Linux for that.

    81. Re:Google by Eil · · Score: 1

      I have mod points, but your score is topped out at 5. I just wanted to say thank you for the refreshing dose of reality. Google has its dark side, sure, but it's about a million times better at contributing to the open source community than any other company, period. (Red Hat comes in second only because they're a much smaller outfit. They too open source a large number of projects when they don't really have to.)

    82. Re:Google by Anonymous Coward · · Score: 0

      Qualcomm sucks too

    83. Re:Google by Anonymous Coward · · Score: 0

      Protocol Buffers is such a wonderful thing. I thank thee for open sourcing it and freeing it from the bowels of the Googleplex.

    84. Re:Google by LingNoi · · Score: 0

      WebKit isn't a web browser. It is just a rendering engine so yes they did build a whole new browser.

    85. Re:Google by Ifni · · Score: 1

      The point he was making is that WebKit (a rendering engine, NOT a browser) is BSD licensed, they used it to create their Chromium browser (including extensive JavaScript optimizations - V8 - which they DID do from scratch) and released that under BSD. Unlike Apple (for example), who took the BSD licensed WebKit, did significantly less with it when they built Safari, and kept the result locked up.

      --

      Oh, was that my outside voice?

    86. Re:Google by dangitman · · Score: 1

      What is the most significant component of a web browser? The rendering engine. Chromium wouldn't work very well without it.

      --
      ... and then they built the supercollider.
    87. Re:Google by dangitman · · Score: 2, Interesting

      The point he was making is that WebKit (a rendering engine, NOT a browser)

      How can you have a browser without a rendering engine? What would be the point?

      Unlike Apple (for example), who took the BSD licensed WebKit, did significantly less with it when they built Safari, and kept the result locked up.

      What? WebKit is LGPL licensed, not BSD licensed. And it wasn't called WebKit when Apple started using it, it was called KHTML. WebKit is Apple's name for their fork of the KHTML project. And Apple didn't "do significantly less with it" - they basically made the whole thing over, and turned a rendering engine that was going nowhere and not used very widely into a modern, high performance and widely adopted engine.

      WebKit is far more significant than Chromium, which is little more than a GUI wrapper round WebKit.

      --
      ... and then they built the supercollider.
    88. Re:Google by gcerullo · · Score: 1

      Anyone can submit patches upstream to Android's code base. You can compile your own fork, and then flash your phone with it. The SDK is free. People are already distributing modified versions of it.

      It doesn't have a huge community of OSS developers, but that doesn't mean that Google or the OHA failed to do anything.

      This is exactly why Android may fail in the long term. It will fragment into so many different flavours, just like Linux on the desktop, that it will be too hard for developers to know which one to target.

    89. Re:Google by LingNoi · · Score: 0

      It also wouldn't work without a GUI, the javascript engine, image loading/rendering libraries and c++ compiler.

      The fact is they still made a web browser and licensed it under BSD. If you think it is so simple then why don't YOU make your own damn browser using WebKit.

    90. Re:Google by dangitman · · Score: 1

      I never said it was simple. Just that it's disingenuous to claim that it's a "whole new browser" since obviously a significant part of the browser was already developed by others. So it's a partially new browser, not a wholly new one.

      --
      ... and then they built the supercollider.
    91. Re:Google by Anonymous Coward · · Score: 0

      Let me look that up for you on my BlackBerry/iPhone/Symbian/Windows Mobile device...

      Oh...

    92. Re:Google by westlake · · Score: 1

      Haven't you noticed? The desktop is irrelevant. It's been abstracted to an Internet access platform. It's the phone in the pocket which is the current battleground, and Linux has won that already.

      Net Applications tracks pretty much every device with Internet access.

      The iPhone - as an Internet platform - has a 0.48% share. Symbian 0.24%. The iPod Touch 0.11%. Win Mobile 0.07% Android 0.06%. Operating System Market Share

      It is far too early to declare a winner here.

      The cell phone remains primarily a personal messaging platform. Its the everyday telephone call, supplemented by text and still or motion video. The subscriber is interested in coverage, he is interested in the service plan - his monthly bill.

    93. Re:Google by Foredecker · · Score: 1

      Great post.

      --
      Jibe!
    94. Re:Google by Deliveranc3 · · Score: 1

      I agree, by embracing open standards Google has ensured that they won't be a flash in the pan.

      Seems like every 2 bit tech venture hits 60% market share, tries to set standards and fizzles in 5 years.

      I'm just trying to imagine Google standing up to the teleco lobby and not seeing it happening. The teleco's don't need to partner with Google at all and Google is going to make the phone and their service commodity products.

      Google seems to be giving up ring0 control by supporting a protected area for the radio controller and a channel to the SIM card for l/p,eid, whatever.

    95. Re:Google by Anonymous Coward · · Score: 0

      Haven't you noticed? The desktop is irrelevant. It's been abstracted to an Internet access platform. It's the phone in the pocket which is the current battleground, and Linux has won that already.

      What?

    96. Re:Google by Anonymous Coward · · Score: 2, Interesting

      Point 2) The Common Android Kernel tree [kernel.org] is browsable, and looks to be fairly easy for anyone to take advantage of. The complaint here seems to be that Google isn't putting in enough work to merge their Linux kernel changes into the mainline, not that they have failed to release anything in a usable way. I find it somewhat disingenuous to slap down an open source contributor for failing to do our work for us.

      If you read TFA (sacrilege I know), you learn that the problem is that the changes need to be made both in the Android kernel code and correspondingly in the Android userland, and only Google can change the latter.

    97. Re:Google by cowtamer · · Score: 0, Offtopic

      mod parent up, as it brings up a valid point, despite being an AC

    98. Re:Google by Anonymous Coward · · Score: 0

      My god, what a whiny fucking bug.

    99. Re:Google by soupd · · Score: 1

      Yeah, particularly as Apple also had representatives on the Board of fellow manufacturers of such devices so were well aware of long term product strategies before they recused themselves from Board meetings. Oh wait...

    100. Re:Google by Meumeu · · Score: 1

      The GPL has actually caused me to drop Linux. I want ZFS for my home server, zfs is not the answer (maxing out 2 cores to copy files?!). Because of the whole "GPL or the highway" approach, even though ZFS IS opensource, it's not 'compatible'.

      Except ZFS being not compatible with the GPL is not an accident, it was done on purpose by Sun to avoid giving ZFS to Linux. If Linux had been under a BSD license and as successful as it is, you can bet Sun would have managed to make it incompatible with BSD...

    101. Re:Google by gyrogeerloose · · Score: 1

      Apple also had representatives on the Board of fellow manufacturers of such devices so were well aware of long term product strategies

      I'm not disputing your claim--I don't know if it's true or not--but can you please cite some proof? I'd like to see it. Google, of course, had a rep on Apple's board until very recently but I don't know who's boards Apple officers have sat on.

      --
      This ain't rocket surgery.
    102. Re:Google by oztiks · · Score: 2, Interesting

      You know, this might explain the giant hole between the original release of iPhone and the release of Android.

      Apple created the SmartPhone market place and can carry the "I was here first badge". Of course we had other SmartPhones prior to this but the market was fairly restricted to business use not really domestic (everyone one from 16yr old kids to 70+ year old retirees use iPhone).

      And I'll say it again, hoping i wont get marked a troll for stating a true but negative POV, but Google I believe missed the SmartPhone rush. Just like Apple missed the Personal Computer rush way back when.

      A phrase from the movie Pirates of Silicon Valley -

      Jobs: "Mines Better!"
      Gates: "It doesn't matter."

      And i think this is the case again, maybe too early to tell but i just see so much development being done for iPhone specific apps and websites these days i find it difficult to believe Google will get the same attention so easily.

      VHS vs Beta, MS vs Mac, Guitar Hero vs Rock Band, iPhone vs Andriod

    103. Re:Google by symbolset · · Score: 1

      ASUS and Acer have bailed on the ARM slate thing, and those are big wins for the evangelism team.

      The thing is, if HP and Dell bail out also too soon, Google will go to market with their own-branded slate and win. You need to get those two to vaporware some products that never see market, and that's +1 difficulty level. It's easy to get them to bail early, it's entirely different to get them to lead us on with products they won't deliver. If Google has a first tier partner that's still pretenting to try to go to market then they'll hold off own-branded product until it's too late.

      Can it be done? I doubt it.

      If you can get them to fake products long enough to prevent a Google direct product for Christmas, then you have some hope of selling WiMo7 next year. Miss the window and WiMo7 is sunk. Miss the delivery date for WiMo7 and they'll roll with what they have. The risks are high, but those are the stakes.

      We live in interesting times.

      --
      Help stamp out iliturcy.
    104. Re:Google by Anonymous Coward · · Score: 0

      OHA has companies *like* Nokia on board: http://www.openhandsetalliance.com/oha_members.html

      but it does not *have* Nokia on board.

      Sadly, while your statement is technically correct English, it's almost certainly misleading to your Slashdot audience.

    105. Re:Google by Anonymous Coward · · Score: 0

      I'm not disputing your claim--I don't know if it's true or not--but can you please cite some proof? I'd like to see it. Google, of course, had a rep on Apple's board until very recently but I don't know who's boards Apple officers have sat on.

      Among other things, one sat on Google's board.

    106. Re:Google by StripedCow · · Score: 1

      All of their own sites, business and back-end technology is just as closed as Microsoft's

      Google's stuff is even more closed because not even their binaries are viewable.

      --
      If Pandora's box is destined to be opened, *I* want to be the one to open it.
    107. Re:Google by Anonymous Coward · · Score: 0

      That Schmidt guy is such an asshole I'm glad he was kicked out of Sun.

    108. Re:Google by richlv · · Score: 1

      working with kernel devs is rumoured to be suited for people with masochistic desires anyway ;)

      more seriously, i hope both sides can come to an agreement and get good code upstream.

      --
      Rich
    109. Re:Google by Xest · · Score: 1

      "Sad, just sad."

      It's also ironic, when the conclusion was reached via a quote (and used completely out of context I might add) from Steve Jobs. I mean, it's not like Apple ever "borrowed" from the open source community without giving back is it?

    110. Re:Google by Xest · · Score: 1

      Yeah, except Jobs was referring to the fact that Google was now competing with them in the mobile handset market, which is somehow an evil thing to do.

      All whilst his own company was still using child labour in Asia to product iPhones and iPods and half his products still had planned obsolescence by having batteries that can't easily be replaced which inevitably increases the amount of toxic waste from these products when they have to be disposed of by Joe Average. Then of course there's the monopolistic practice of pushing DRM as hard as possible so as to ensure that a lot of content bought from iTunes wont work unless people replace their failed Apple products with more Apple products or must face losing their entire library of content if they go to a competitor.

      Really, the fact Jobs calls greater competition an evil thing, whilst continuing to run a business guilty of things like the above says far more about Jobs and Apple than it does about Google.

    111. Re:Google by TheRaven64 · · Score: 1

      I'd take FreeBSD on the desktop over Linux for one simple reason: Sound works properly. No need to mess about with userspace sound daemons, just open /dev/dsp and write audio there. Full OSS 4 API support, so each app gets its own, private, volume control and if your hardware doesn't support mixing then there's a low latency software path in the kernel.

      --
      I am TheRaven on Soylent News
    112. Re:Google by TheRaven64 · · Score: 2, Insightful

      Chromium didn't have to be open sourced, only their changes to WebKit did. Apple keeps Safari proprietary while using WebKit quite easily. It's also worth noting that Chromium is released under a more permissive license than WebKit.

      --
      I am TheRaven on Soylent News
    113. Re:Google by RichM · · Score: 1

      Apple: creating computers for idiots since 1976.

    114. Re:Google by RichM · · Score: 1

      Where BSD has found a niche is in Network appliances such as routers and firewalls.

      Incorrect.

    115. Re:Google by silanea · · Score: 1

      Haven't you noticed? The desktop is irrelevant. It's been abstracted to an Internet access platform. [...]

      Absolutely! Which is why I have two operating systems with about 30 applications (not counting games) each installed on a quad-core machine with 4GB of RAM, two video cards and a RAID0 array.

      Oh, wait...

      --
      Rudolf Hess edited Mein Kampf. He was the very first grammar nazi.
    116. Re:Google by gtall · · Score: 1

      I hear China is cornering the market by buying mod point mines. Most them are in China anyhow. The mod point shortage is coming, too bad you cannot save them for a rainy day.

    117. Re:Google by gtall · · Score: 1

      Jobs wasn't whining about competition, he was whining about Google having a mole on Apple's board and an unwritten agreement that Apple wouldn't do search and Google wouldn't do phones. He felt double crossed and whine about it. Morons like you attached the "Apple doesn't like competition" to it.

    118. Re:Google by hey! · · Score: 1

      If he'd deliberately participated in the Apple board meetings in a way that was not in the interests of Apple stockholders he could be in legal trouble. If he'd taken Apple's product plans and used that knowledge directly in Google's plans, for example. But you can't go after somebody for general expertise in the market or product development the've gained from working for a company or serving on the board, unless you have a contract that forbids them from doing so.

      This is a situation that certainly skirts the edge of impropriety at the very least, but Apple is a big time player that ought to know how to protect itself. It's not like putting one over on some poor, information overloaded consumer.

      --
      Post may contain irony: discontinue use if experiencing mood swings, nausea or elevated blood pressure.
    119. Re:Google by salesgeek · · Score: 2, Informative

      Wrong. Let's not act like a product category that had been around for 10 years prior to iPhone was suddenly created by Apple. Apple did not create the smart phone. They did not even define the product:

      Palm, Blackberry and Microsoft (to a lesser extent) defined the product. Apple came out with the best model in the 2008 model year. That is the extent of the achievement, and to give Apple more credit is simply an insult to the people that created iconic products like the Blackberry, Treo and to a lesser degree WinMo smartphones that defined the platform that Apple added incremental improvements to.

      It is telling that even my lowly G-1 has more features than the same generation iPhone (keyboard, removable battery, 3G, removable memory, metal detector, etc...).

      Finally, Android has *already won the war* with Apple. It's pretty much exactly like Mac vs. PC in the early 90s. Developers who pass on Android for iPhone will be seen as shortsighted by the end of this year as marketshare expands.

      --
      -- $G
    120. Re:Google by Xest · · Score: 1

      Well, that's certainly the view taken by those behind Apple's reality distortion field yes.

      But those of us living in the real world recognise one fundamental flaw with it- the idea that Google would see Apple as a threat in search is fucking comical. As such, the idea that Google would need such an agreement is clearly stupid. This is why, at worst, Apple will have to jump into bed with Microsoft for search now that Yahoo search is tied up with Microsoft anyway.

      The closest they had was the no poaching agreement for staff.

      It's also worth pointing out that the idea that Schmidt was a mole when he was sat on the board, and hence, sat in on board meetings, is quite amusing. Apple were the ones who wanted him there in the first place.

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

      Symbian is now open source, and Maemo, being Linux, has always been.

    122. Re:Google by Miamicanes · · Score: 2, Interesting

      > And how is Android not open? The entire thing is FOSS

      (cringes, wrings hands for a while, coughs a bit, then sighs)

      "Android" might be "open", but people fighting on the Android front lines and trying to run open builds without the blessing of HTC and their carrier might politely beg to differ. To date, nobody has been able to independently build a fully working 2.6.29 kernel for ANY CDMA Hero phone that shipped with Android 1.5 (Sprint Hero, Sprint Samsung Moment, Verizon Droid Eris). Without a 2.6.29 kernel, major parts of Android 2.x won't work properly. Work is underway, but the fact is, right now... today... my Sprint Hero is running a hacked-up build that can be described as a liquefied Cupcake injected into the clay mock-up of an Eclair facade. And I'm "lucky" -- my other CDMA Android 1.5-shackled brethren can't even do *that*.

      Right now, the cruel reality is that people who buy many Android phones are kind of like consumers who bought a very, very proprietary Packard Bell or HP computer in the mid/late-90s. If the manufacturer didn't feel like supporting Windows NT or Linux, you were basically screwed. You couldn't just download OEM drivers, because they didn't exist -- the company who sold the computer WAS the OEM. Open-source drivers didn't exist, because the hardware itself was built around proprietary ASICs designed for that specific manufacturer.

      OK, let me make the analogy a little better: it's 2000, and you need to buy a new laptop. Your ISP allows you to choose between exactly two laptops, both sold only by the ISP itself with a 2-year contract that has a substantial penalty for early termination. Your ISP personally knows the MAC address of the network interface for every computer it sells, and refuses to accept network traffic from any network interface whose MAC address isn't in its holy database. It's not necessarily *impossible* to spoof an official MAC address with an unapproved laptop, but it happens to be a major federal offense that can be prosecuted as an act of terrorism, narcotics distribution, or organized crime. The laptops are only available with an old, obsolete distro of Linux that's proprietary to the laptop's manufacturer, and the hardware drivers are all compiled straight into the kernel (which happens to be 2.2, even though 2.4 has been considered mature enough to use for at least the past 6 months). Oh, the source? You won't see it until 4-6 months after you buy the laptop -- if you're lucky -- and the code for the proprietary hardware will be obfuscated & devoid of comments.

      Welcome to the brave new world of Americans who buy Android phones in 2010, where "open" phones have to be hacked & rooted to allow upgrades, and it's easier to upgrade an old phone to a newer version of Windows Mobile than it is to upgrade a 4 month old Android phone to a newer version of Android.

    123. Re:Google by lwsimon · · Score: 1

      That's part of what makes Open Source what it is, though. By making your code available to be used by those who share you goals, you also open it up to be used by those who don't. That's not a problem, that's the nature of the beast.

      All they've done is forked the project and turned it into something else. If that something else gains support and becomes the leader in that area, it will have done so because it is better - not necessarily technically better, mind you, but better supported, better marketed, or better funded.

      If you don't like the product, you're free to fork it. That's the part of the GPL that sets it apart - it prevents one company from monopolizing a codebase by allowing *anyone* to give it a shot -- even people you don't like.

      --
      Learn about Photography Basics.
    124. Re:Google by Anonymous Coward · · Score: 0

      apple II and its array of expansion cards: graphic cards, sound cards, DA and AD converters, first to have a midi sequencer. The mac, a toy computer which soon turned into the first DTP and pro-audio platform. Things for idiots, sure. The smarties were using serious productivity tools on commodore or dealing with the stability of windows, sure, mr. troll du jour.

       

    125. Re:Google by Wdomburg · · Score: 1

      s/Apple created the SmartPhone market place/Apple created the consumer SmartPhone market place/

      Fixed that for you. Apple still hasn't even caught up with the leader (Blackberry) in the overall smart phone market.

    126. Re:Google by gtall · · Score: 1

      Of course Google thinks of Apple as competition, Google would like to control access to information and Apple makes the iPhone and iPad. I guess living in the real world isn't all its cracked up to be. Google thinks of MS as competition also and thought that long before Ballmer got the hots for Yahoo. Maybe you missed Google Docs and other Google software...real world, you should see it sometime.

      I never said it was a sensible feeling for Jobs to feel double-crossed, merely that he felt double-crossed. It still had nothing to do with Apple not accepting competition.

    127. Re:Google by MarkvW · · Score: 0

      Mod points, schmod points. Let it go.

      Mod points do nothing to elevate the level of discourse. Fuggedaboutit.

    128. Re:Google by MarkvW · · Score: 1

      But is a common api too much to hope for?

    129. Re:Google by Xest · · Score: 0, Troll

      No, that's just it, he felt double crossed about Google entering the phone market precisely because he did not want competition from them. Perhaps he didn't expect it either, but clearly the two go hand in hand else he wouldn't have been pissed off about it. It still clearly demonstrates Jobs does not appreciate competition however you cut it.

    130. Re:Google by Anonymous Coward · · Score: 0

      He never said anything about lack of fairness. It's just competition. And he wants to crush it. That is, as it turns out, his job.

    131. Re:Google by Anonymous Coward · · Score: 0

      Lets see what it is in two years.

    132. Re:Google by nurd68 · · Score: 1

      In my (admittedly geek) household, every adult has:
        - a desktop
        - a fullsize laptop
        - a portable computing device (netbook, iPhone, etc.)

      The desktop is for the things that the laptop can't do. The portable device is more portable than the laptop. As laptops get better, so do desktops, so they tend to leapfrog each other.

    133. Re:Google by soupd · · Score: 1

      It's not true and that's the difference between Apple launching iPod/iPhone and Google launching their phone. Only the naive would believe Google didn't benefit from Schmidt being on Apple's board during much of the iPhones planning and development.

    134. Re:Google by gyrogeerloose · · Score: 1

      Yeah, not enough coffee, I guess, was feeling a little slow yesterday. Right after I posted that, I realized you were being ironic.

      --
      This ain't rocket surgery.
    135. Re:Google by exomondo · · Score: 1

      VHS vs Beta, MS vs Mac, Guitar Hero vs Rock Band, iPhone vs Andriod

      But pick the ones out of your list that can both co-exist in healthy competition. Obviously MS and Apple can, as can the iPhone and Android handsets.

    136. Re:Google by atheistmonk · · Score: 1

      Anti-Apple != pro-Microsoft

    137. Re:Google by gyrogeerloose · · Score: 1

      It was supposed to be a joke, you know. I guess the Microsoft fanbois didn't get it.

      --
      This ain't rocket surgery.
    138. Re:Google by atheistmonk · · Score: 1

      In my defense, this is Slashdot.

    139. Re:Google by gyrogeerloose · · Score: 1

      Don't feel too bad, apparently no one else got it either. But it did lead to an interesting first for me: a +5, Informative comment and a -1, Flamebait comment in the same thread. I should get a Slashdot Achievement for that, I think.

      --
      This ain't rocket surgery.
    140. Re:Google by oztiks · · Score: 1

      It was a joke implied from what was said in the parent. So far I haven't lost any sleep over it.

    141. Re:Google by bonch · · Score: 1

      You actually think the iPhone runs Linux? Why are you even posting?

    142. Re:Google by Anonymous Coward · · Score: 0

      Maybe pick an example you know something about, then.

      http://www.microsoft.com/downloads/details.aspx?FamilyId=3A1C93FA-7462-47D0-8E56-8DD34C6292F0&displaylang=en

      There it is. This is well-known.

      Unlike go, this is a language that Microsoft has made a large bet on, and has supported in their products and uses internally. They also updated the Rotor release over time, instead of dropping it on the floor.

      Plus, it is a language that is viable for a large range of production projects, not a toy that is more similar to a language created for a school assignment.

    143. Re:Google by notrandomly · · Score: 1

      It seems that what you are saying is that Google as a company doesn't really care about OSS except when it's good for the bottom line, but individual employees may care. Just like Microsoft. As a company, Microsoft is evil (not saying that Google is), but there are still a lot of good, decent, clever people working there.

    144. Re:Google by Foredecker · · Score: 1

      We shall see :)

      --
      Jibe!
    145. Re:Google by Anonymous Coward · · Score: 0

      Well, they don't do GSoC because they have to...

    146. Re:Google by Anonymous Coward · · Score: 0

      FBSD still has a superior networking stack from what I've seen. We also deploy Juniper networking equipment and JunOS is based on FreeBSD.

      Don't for even a second think that the network stack in *BSD is what is used for the data plane of Juniper devices. As a matter of fact, only a very, very small fraction of it is even used in the control plane. The CLI runs on *BSD which then communicates with the actual hardware which runs specialized ASICs and FPGAs. When you execute a show command, the CLI queries the hardware. When you issue a set command, the CLI writes to the hardware. The protocol processes themselves do run under *BSD and that is where the selective RIBs are calculated but the FIB is all in hardware.

      Again, don't be confused.

      --tvo

    147. Re:Google by Anonymous Coward · · Score: 0

      thank you. I agree on some google criticism, but there is a lot of bullshit out there, especially coming from iSteve's face.

  2. One sentence to say it all... by Jorl17 · · Score: 5, Insightful

    "Because of this, Google has now prevented a large chunk of hardware drivers and platform code from ever getting merged into the main kernel tree. Effectively creating a kernel branch that a number of different vendors are now relying on."

    That's all. It's obvious that Google doesn't care about it that much. And yet nobody demanded them to do so -- if Google wants it its own way, why shouldn't it be able to?
    I may be a crazy open-source lunatic, but I am tired of all of this "It's a world conspiracy against Linux"-thing. Let's get a grip, talk less and code more.

    --
    Have you heard about SoylentNews?
    1. Re:One sentence to say it all... by godrik · · Score: 2, Insightful

      I don't think he is seeing this as a conspiracy against linux. He is just saying that some work may have to be done twice (because merging is not feasible) which is really bad for everybody. no one wants to maintain 2 code base.

    2. Re:One sentence to say it all... by Anonymous Coward · · Score: 2, Insightful

      So then maybe they shouldn't have kicked the android code out of mainline in the first place?

    3. Re:One sentence to say it all... by Jorl17 · · Score: 2, Interesting

      Well, I didn't say he meant that either. I'm talking about the great fuzz around these issues. Everywhere I go there's someone trying to give his/her side of the "conspiracy against Linux", whereas I think that there is no such thing. So what if it can't be merged back? If it can't, it can't -- get something better and don't stay up all night banging the ceiling and complaining (if you get what I mean).
      I would like to see people looking at what Google did and say: "Oh well, it's their choice and I can't do anything about it. However, I can help the Linux kernel with something better and more useful than that will ever be."

      Unfortunately, few people think like me...am I just nuts?

      --
      Have you heard about SoylentNews?
    4. Re:One sentence to say it all... by Lumpy · · Score: 4, Interesting

      Nothing is stopping people from porting android to use a standard Linux kernel.

      Honestly It's a two way street, and I doubt that google looked at the Linux guys and told them to go fornicate with themselves.

      Google does releases on their own schedule. Being someone that is deep into Android guts on the x86 level for a project of my own (android based car stereo) I am frustrated at them not releasing the latest version, but I can either sit and while like a baby, or take what I got and build on it.

      --
      Do not look at laser with remaining good eye.
    5. Re:One sentence to say it all... by gstoddart · · Score: 3, Insightful

      So then maybe they shouldn't have kicked the android code out of mainline in the first place?

      If it created code dependencies that nobody buy Google could compile against, it's got no business in the mainline -- it effectively breaks the kernel for everyone else.

      This isn't a matter of getting voted off the island because they don't like your features -- it's about making something which was incompatible and people deciding that it had to go.

      --
      Lost at C:>. Found at C.
    6. Re:One sentence to say it all... by advocate_one · · Score: 3, Informative

      So then maybe they shouldn't have kicked the android code out of mainline in the first place?

      it never made it out of staging into mainline... it wouldn't build as there were items Google never released that it was dependent upon.

      --
      Donald 'Duck' Dunn: We had a band powerful enough to turn goat piss into gasoline.
    7. Re:One sentence to say it all... by tixxit · · Score: 1

      Huh? I think the point he was driving at was that these companies will now have to support their own drivers, with no chance of letting the community take over. If they could merge their drivers into the main linux kernel, then other developers can take on the task of migrating it to new linux versions, improving it, and creating security fixes. Since they can't do this, they (or Google) will now be responsible for maintaining the driver, always.

    8. Re:One sentence to say it all... by h4rr4r · · Score: 1

      Or you could just use a regular linux kernel for your project, would save you a ton of hassle.

    9. Re:One sentence to say it all... by Lumpy · · Score: 3, Informative

      And what for the interface? Android is at least 9000 years ahead of anything else for a limited attention easy to use touchscreen interface. Plus I get a pile of apps ready to go including navigation.

      --
      Do not look at laser with remaining good eye.
    10. Re:One sentence to say it all... by minsk · · Score: 5, Informative

      it wouldn't build as there were items Google never released that it was dependent upon.

      Are you sure that statement is true? It seems inconsistent with other information posted here, and in the LWN discussion.

    11. Re:One sentence to say it all... by grishnav · · Score: 1

      You could look into Maemo...

    12. Re:One sentence to say it all... by h4rr4r · · Score: 1

      I would have suggested using a voice interface, touch screen in a car seems like asking for an accident.

    13. Re:One sentence to say it all... by ajs · · Score: 1

      Remember we're talking about the android-specific driver code (not code for Android devices, but the android-specific drivers like their user-space configurable oom-killer) that clocks in around 2kloc.

      It's tiny and Slashdot is misleading. Film at 11.

    14. Re:One sentence to say it all... by iamwahoo2 · · Score: 1

      While I see the appeal of being able to run Android Java apps, I would not declare Android to be ahead of many of the other options for Linux touchscreens. While it is certainly a decent system for phones, it has not demonstrated the flexibility to be successful in a wide variety of touch screen use cases. It probably would work great at the hobbyist level for getting a quick and powerful interface on a general purpose touchscreen device, but if you were planning to market the car stereo on a large scale it would probably come out looking like you tried to make software designed for a phone work on a car stereo. On the other hand, that may be a good trade-off because saying that your car stereo runs Android would probably convince a lot of Android fans to buy it.

    15. Re:One sentence to say it all... by godrik · · Score: 1

      I understand what you mean. I think it is more that it would be such a waste not to make both project compatible at least from the driver point of view that it drives some people crazy (let's forget the but-it-is-not-fair-not-to-backport-THATS-SO-UNFAIR kind of guys) since it would pool a lot of (tedious) work.

      Unfortunately, few people think like me...am I just nuts?

      Since you are posting on /. I would say taht you must be to a certain degree. :)

    16. Re:One sentence to say it all... by cynyr · · Score: 1

      The code was never in "Mainline" it was in "staging" which is in part of the mainline, but a part with different rules about what stays and what goes. Google steps up and fixes things then the code should be bale to go back into mainline or staging. Please read GHK's posts about what staging is.

      --
      All of the above was encrypted with a Quad ROT-13 method. Unauthorized decryption is in violation of the DMCA.
    17. Re:One sentence to say it all... by Anonymous Coward · · Score: 0

      Maemo. Standard Linux (which Android is anything but) with a mostly open source stack, including touch screen optimized gui. Being standard Linux, this means you also have access to the tens of thousands of existing Linux applications, rather than just the fart app of the week coming out for Android.

    18. Re:One sentence to say it all... by jeremyp · · Score: 2, Informative

      How is this +5 informative? It's completely false.

      The reason it didn't make it to mainline is because the Google code was reviewed and found to have problems that stopped it being accepted into mainline. Because there are user space items in Android that would be affected, only Google could make the changes without breaking Android.

      Think about it, if you were unable to build the Android kernel because Google were withholding stuff, it would be in direct violation of GPL v2. Do you see Greg KH complaining that Android violates the Linux licence? No.

      --
      All I want is a secure system where it's easy to do anything I want. Is that too much to ask ~~ Randall Munroe
    19. Re:One sentence to say it all... by TheRaven64 · · Score: 2, Interesting

      Does that mean Android handles OOM conditions gracefully? I've only seen one OS that does it well[1], but the Linux behaviour in these conditions is the absolute worst (pick a process at random, typically the one with the most unsaved data, kill it). This is one of the biggest problems I saw with Maemo. Run low on memory, and suddenly apps die. Make sure you save regularly, because there's only a small chance it will be the web browser that is killed and not the editor that you were writing in...

      [1] Recent OS X suspends processes that try to allocate when memory is full, reserves a small amount of memory for root, and lets you quit apps to free up memory or delete some files to make some space available for swap. Processes can also set a flag indicating that they have no unsaved data. When this is set, the system can kill them at any point to reclaim their resources and restart them later.

      --
      I am TheRaven on Soylent News
    20. Re:One sentence to say it all... by Lumpy · · Score: 1

      Have you even seen what current double din touchscreen car stereos have for an interface?

      just slapping Android on it will create a product that is tons better. JVC, Kenwood and others all have a horribly crappy interface that is borderline unusable. JVC has the most cryptic control interface on the planet, and they are one of the biggest companies in the mobile entertainment sector.

      --
      Do not look at laser with remaining good eye.
    21. Re:One sentence to say it all... by Lumpy · · Score: 1

      Maemo is great, I have maemo on my N900. it's certianly not useable for a car stereo. The sliding menu at a single touch as well as a lot of other features already built into Android cuts my dev time by 3/4. With maemo I'll have to take almost 5 steps backwards because a lot of the functions I already have in android by default, I'll have to create for android.

      Maemo is awesome for a General purpose touchscreen device. Android is turning out to save me a ton of time. the built in dialer screen rocks for bluetooth dialing, and I already have passthrough to the phone with voice dialing working.

      --
      Do not look at laser with remaining good eye.
    22. Re:One sentence to say it all... by Zebedeu · · Score: 1

      Being someone that is deep into Android guts on the x86 level for a project of my own (android based car stereo)

      Can you share more details on your project? This is something I'm interested in as well.

      I've kind of been waiting on the sidelines for a commercial product (I guess it's inevitable, there are even microwaves running Android now), but I wouldn't mind building one myself.

      Alternatively I was thinking of simply repurposing one of those Android tablets coming out.

  3. up merge justification has to be Android-agnostic by Rene+S.+Hollan · · Score: 4, Interesting

    You don't merge new features into a robust low-level code base.

    You merge support for abstractions the new features rely upon into the low-level code base, and build on them.

    Make a case for kernel support of the "new lock" and "security model" independent of Android's reliance on it, and remove as many of the Android drivers using these facilities OUT of the main tree. IMHO, drivers really don't belong there, but should be available in "driver package sets" aggregated by distro providers.

    --
    In Liberty, Rene
  4. not quite... by RingDev · · Score: 4, Insightful

    This isn't about some anti-Linux conspiracy, it's about conflicting business interests.

    Google has made modifications to make their software work. Those modifications can not be integrated as is with the kernel. Cleaning up their open source code can be done, but their internal closed code would likely also need modifications to account for that cleanup. So for Google, merging their code would likely be expensive and require extensive testing and a large download and upgrade system for all of the live phones.

    On the other hand, companies that are developing drivers and software that depend on the new kernel are now hosed because the kernel is no longer exposed as part of the Linux kernel. So they have to deal directly with Google for any changes to their kernel, and if they also want to release their products for other Linux platforms, they have to re-engineer much of the os-interaction functionality. Obviously a pricey situation for them.

    If Google updates their code to get it into the kernel, it makes it cheaper and easier for other developers to work it, but it costs them money. If they don't then it costs the developers more money.

    -Rick

    --
    "Most people in the U.S. wouldn't know they live in a tyrannical state if it walked up and grabbed their junk." - MyFirs
    1. Re:not quite... by SanityInAnarchy · · Score: 2, Insightful

      Nice summary.

      I'd like to add: Developers, developers, developers, developers. Google should spend that money. Consider it an investment in your platform -- it makes it that much more attractive to other developers.

      --
      Don't thank God, thank a doctor!
    2. Re:not quite... by Anonymous Coward · · Score: 0

      Or the guys maintaining the Linux kernel can spend their money merging the Google code themselves, because that is an investment in their platform (Linux mainline kernel) to attract the phone hardware developers.

      It isn't always downstream's responsibility to push code upstream, especially when upstream doesn't have stable APIs and like to change things randomly because they can. Work isn't free, and if you make the other party's life harder than it needs to be, sometimes you have to pay the price for that.

    3. Re:not quite... by Yvanhoe · · Score: 1

      closed code ? Maybe Google will finally provide a good argument for people wanting to switch the license to GPL v3

      --
      The Wise adapts himself to the world. The Fool adapts the world to himself. Therefore, all progress depends on the Fool.
    4. Re:not quite... by SanityInAnarchy · · Score: 1

      Or the guys maintaining the Linux kernel can spend their money merging the Google code themselves,

      Not realistically. Some of the affected areas include the kernel-userspace boundary -- basically, fixing that to the point where the Google code would make any sense upstream necessarily entails changing the userspace code that it connects to. In this case, that userspace code is also Google's code -- I'm not entirely sure it's open.

      Realistically, this will take cooperation from both sides, and at the moment, Google is the only one who seems to have stopped cooperating.

      --
      Don't thank God, thank a doctor!
  5. Google has just TIVO-ized the kernel by tomhudson · · Score: 2, Interesting

    You can use Android, but you're now dependent on Google for maintenance, bug-fixes, and trusting that they don't include any evil bits.

    1. Re:Google has just TIVO-ized the kernel by AndrewNeo · · Score: 2, Informative

      Hardly. Nobody's forcing you to run their binaries on your phone. You can still compile the kernel and other applications from code, forked or not.

    2. Re:Google has just TIVO-ized the kernel by tomhudson · · Score: 0

      Please RTFA, Only against google's forked codebase. You can't use a generic kernel in your phone.

    3. Re:Google has just TIVO-ized the kernel by AndrewNeo · · Score: 1

      I wasn't talking about a generic kernel. You can still compile from Google's copy of the source just fine, it's no less visible.

    4. Re:Google has just TIVO-ized the kernel by Enderandrew · · Score: 2, Interesting

      You do realize that Google does not own nor control Android, right?

      Google handed Android over to the Open Handset Alliance the moment they unveiled it. There are several large companies (like Nokia and Motorolla) who take part in that alliance.

      --
      http://blindscribblings.com - Tasty pop-culture in conceptual fashion.
    5. Re:Google has just TIVO-ized the kernel by cr_nucleus · · Score: 1

      ...and trusting that they don't include any evil bits.

      Man, i wish i could distinguish the evil bits from the good ones...

    6. Re:Google has just TIVO-ized the kernel by Anonymous Coward · · Score: 0

      No you're not. Since you have the source code, you can maintain it yourself, or pay a third party to do so for you. That's the whole point of open source, right?

    7. Re:Google has just TIVO-ized the kernel by tomhudson · · Score: 1

      So you're going to pay someone to maintain a fork of the kernel, when the only reason it's forked is that google doesn't want to maintain compatibility, because THEY have enough people to maintain a fork, but most businesses don't - and would rather put the resources elsewhere?

    8. Re:Google has just TIVO-ized the kernel by Anonymous Coward · · Score: 0

      Man, i wish i could distinguish the evil bits from the good ones...

      Maybe if you spent less time searching for naughty bits and more time studying code for evil bits you could!

    9. Re:Google has just TIVO-ized the kernel by Miamicanes · · Score: 1

      > Hardly. Nobody's forcing you to run their binaries on your phone.

      Verizon customers with a Droid Eris might beg to differ. http://forum.xda-developers.com/showthread.php?t=617203

  6. Re:Anonymous Coward by gstoddart · · Score: 2, Funny

    Y'a quelqu'un qui comprends ce que Anonymous Coward a écrit? Moi je n'y comprends rien.

    Courtesy of the google translator ...

    As they say in Tuscany, as the gay guy UnitedStatesOfNorthAmerica.

    There was to be expected.
    Good night America.

    Still no idea what it meant. :-P

    --
    Lost at C:>. Found at C.
  7. Lots of comments on LWN.net's coverage by chrisd · · Score: 5, Informative

    If you head over to LWN, we've already gone back and forth on this a bit. http://lwn.net/Articles/372419/. The short form is that if they don't like how we use the kernel, we're unlikely to be accepted upstream. It's all still released as source code to the world, but the mainline is not interested in most of what we've with to the kernel.

    --
    Co-Editor, Open Sources
    Open Source Program Manager, Google, Inc.
    1. Re:Lots of comments on LWN.net's coverage by h4rr4r · · Score: 0, Flamebait

      Surprise, Surprise, reinventing the wheel is not gonna earn you a lot of friends. And no making the wheel less round is not helpful either.

    2. Re:Lots of comments on LWN.net's coverage by VON-MAN · · Score: 1

      Ok. But as far as I know, all new code has to be made fit for the kernel before merging, and not the other way around. So I wonder: can somebody else -outside of Google- cleanup and merge your stuff?

    3. Re:Lots of comments on LWN.net's coverage by Anonymous Coward · · Score: 4, Interesting

      That's completely disingenuous. Everyone agrees that the problems Android needs to solve should be solved. The kernel community simply disagrees with *how* Google solved the problems. Long ago Google could have asked "we need to optimize power usage by doing agressive suspend" and then worked with the kernel community to get a solution that everyone was happy with.

      But instead, Google went off into a corner, created their own solution behind closed doors that nobody in the kernel community likes and now it can't go upstream.

      It's not about "how we use the kernel", it's about how you coded things in isolation then expect everyone to be ecstatic with the result despite the fact that the gatekeepers never had any input into the design.

    4. Re:Lots of comments on LWN.net's coverage by Anonymous Coward · · Score: 0

      I think there was a call for this and no one wanted to do it. Why would they? Google should be doing it.

      If I had an open source project and someone showed up with a big blob of code that they then expected me to fix to merge into my code I would ignore it too. I have my own itches to scratch.

    5. Re:Lots of comments on LWN.net's coverage by Hurricane78 · · Score: 2, Interesting

      Even if the floor is less round? (Not saying this is the case here. Just pointing out, that ideals can change. Einstein said it best: “Leaving research exclusively in the hands of engineers, we would have perfectly functioning oil lamps, but no electricity.”)

      --
      Any sufficiently advanced intelligence is indistinguishable from stupidity.
    6. Re:Lots of comments on LWN.net's coverage by Flavio · · Score: 4, Insightful

      But instead, Google went off into a corner, created their own solution behind closed doors that nobody in the kernel community likes and now it can't go upstream.

      No one in their right mind is going to start a lengthy debate with kernel developers when they have a deadline to meet and a product to ship.

      In the industry, getting things done on time is priority #1. Google's implementation may not have been ideal, but it was delivered.

    7. Re:Lots of comments on LWN.net's coverage by VON-MAN · · Score: 1

      That is not what I asked.

    8. Re:Lots of comments on LWN.net's coverage by diegocg · · Score: 2, Insightful

      Which is perfectly fine, but it shows the autism in the google culture when it comes to working with people from outside. There're many companies working on Linux (doing more serious hacking than Android does), and they have learnt to interact with the Linux community when they want to add a feature. They ask maintainers what design they should follow to implement some feature. They listen, they write code, they get reviews, they make changes, they repost the patches. In other words, they interact with the community, they are a part of the community. SGI, for example, has done a tremendous amount of work in the past years to get the kernel in shape for their beasts with thousands of CPUs, they have touched a lot of complex core code, yet they did all contributing with the community, targetting the main kernel in first place.

      Google, in the other hand, is not a "part" of the community. It hacks the kernel for months without any contact outside of Google, some day it announces a future product using the code and only after that, it drops a shitload of code to the community which does very weird things that many Linux hackers don't like. Then it does nothing to improve the design (because there's already production code depending on it), and it makes zero efforts to fix it or get it merged. Then it claims that everything is fine, because the code is GPL which means you can reuse it. In other words: Google doesn't care about what the rest of the community thinks before modifying the code, and it doesn't care when it releases either.

      Given that Android is supposed to be not just a Google project but a community, and Google is a opensource oriented company, one would expect that Google would have done it better. Sadly, Android has become one of the best examples of how not to work in a opensource community,

    9. Re:Lots of comments on LWN.net's coverage by Anonymous Coward · · Score: 0

      That is not what I asked.
      can somebody else -outside of Google- cleanup and merge your stuff?,

      Uh that is exactly what you asked? Can someone else do it? The call was put out, it was even put into staging for this very thing. NO ONE not even Google stepped up to the plate.

      The rules of staging is it can get yanked out of if no one is going to bother fixing it. It is not where code goes to die.

      The answer is clear no one wanted to do it. That answer may be different today. But yesterday it wasnt. Judging from the reactions here and all over the place everyone is looking to Google to fix their own mess...

    10. Re:Lots of comments on LWN.net's coverage by thetoadwarrior · · Score: 1

      isn't that what they should be allowed to do if open source is striving for the freedom to use the code as you wish?

    11. Re:Lots of comments on LWN.net's coverage by WarlockD · · Score: 3, Interesting

      I think thats the whole issue here. Why does Goggle have to do any work to get "accepted" into the main kernel anyway?

      The android is an embedded device that works with a small subset of chips sets and devices. Why does it have to be in the main kernel to begin with? Is somone going to be shoving a PCI card in that thing? Heck, why does Google have to spend the weeks/months talking back and forth with the developers when they can get their own solution, that works just as well for them, in half the time?

      Talking about "giving back to the community" is all well and good, but I don't expect Google to sacrifice their profitability or deadlines just to make some members of the community happy.

      Lets be honest here though, all the code is in GPL so whats stopping someone else from doing the work?

    12. Re:Lots of comments on LWN.net's coverage by Anonymous Coward · · Score: 0

      I tried finding a reference for that quote, but couldn't find one.

    13. Re:Lots of comments on LWN.net's coverage by Anonymous Coward · · Score: 2, Insightful

      No one except Red Hat, IBM, Oracle, Sun, and thousands of embedded hardware manufacturers the world over. Other than that, though, NO ONE!

    14. Re:Lots of comments on LWN.net's coverage by Anonymous Coward · · Score: 2, Interesting

      The kernel community simply disagrees with *how* Google solved the problems. Long ago Google could have asked "we need to optimize power usage by doing agressive suspend" and then worked with the kernel community to get a solution that everyone was happy with.

      Unfortunately, this is Google's standard operating procedure. Don't get me wrong, I like Google and enjoy tinkering with Android, but its far from perfect. And don't make suggestions to the core developers as some are more than happy to give you the middle finger for simply not bowing to their brilliance. Some of them are pretty good, but some are brilliant at being assholes. I mean, look at some of their widgets. Eeek! Its as if the people who wrote some of the widgets had never actually used UI widgets before. Saw someone politely make suggestion and the Google engineer rudely ignored them after telling them they were wrong.

      Should double clicking of a button, which opens a new window, result in two new windows being opened? No. Shouldn't widgets maintain state? Yes. According to Google's they do yet cancel doesn't actually cancel despite the fact they've already notified the user of the change. Its up to applications to actually track state and cancel it. So on and so on. If a widget's cancel doesn't actually cancel, I don't believe that qualifies as stateful.

      Despite Google's assurances everything they do is better than anything you could ever do, sadly the truth is nowhere near. Google very much has a problem with not invented here and in some cases, a complete lack of consultation with people who actually know what the hell is going on. As a result, some things Google does are just truly horrific, lacking any clue, forcing developers to add lots of code to work around their huge ego and seemingly lack of real world experience.

      I'm posting anonymously because some of the Google engineers also hold petty grudges.

    15. Re:Lots of comments on LWN.net's coverage by Anonymous Coward · · Score: 1, Interesting

      So maybe they need to ship the fork in the short term, meanwhile get engaged in that lengthy debate on something everybody agrees with, and get that working for the next release. Problem solved?

    16. Re:Lots of comments on LWN.net's coverage by Rene+S.+Hollan · · Score: 5, Informative

      Okay. I got off my ass and actually looked at waitlock. It isn't, as I thought, a lock with a restoration of execution context when held, so that one can temporarily surrender other locks, and reacquire them. It is a lock on keeping the system out of various low-power states.

      Mainline has an (arguably, according to Google-folk, inefficient), lock on guaranteed service latency (low, medium, high?). and Google wants a lock on specific activity level abstractions (idle, suspend, etc.). Did I get that right?

      Well, if the present implementation is inefficient (a linear search...), fix that: use an AA-tree or heap, or something.

      I suspect the latency time guarantees are coarse at best and probably map to specific power states (idle, suspend, etc.) anyway. I think BOTH models should be supported (heck, you could always map levels to latencies in some tunable fashion, if you had to fake it: "responsiveness SUSPEND" vs. "hardware SUSPEND") but only because there are already standard abstract notions of what IDLE, SUSPEND, and POWEROFF are.

      What may have happened is that the existing implementation was inefficient, not quite fitting the expected model, and Google-folk found it faster to roll their own driven by time-pressure, instead of reworking the existing inefficiencies, thinking "heck, we can layer our API over the existing implementation later" and finding the models are more different than thought.

      Reconciling that is called "refactoring" and sometimes it breaks APIs as much as one does not want it to.

      Now, who has a vested interest in doing that?

      Google? Not really. They figure they can handle the overhead of a kernel fork, at least for a while.

      Mainline kernel devs? No. The existing model "works".

      I'll tell you who: Google's downstream customers. One of them will do it.

      --
      In Liberty, Rene
    17. Re:Lots of comments on LWN.net's coverage by The+End+Of+Days · · Score: 2, Insightful

      It's like Einstein said, "I didn't say half the shit people think I did."

    18. Re:Lots of comments on LWN.net's coverage by tyrione · · Score: 1

      But instead, Google went off into a corner, created their own solution behind closed doors that nobody in the kernel community likes and now it can't go upstream.

      No one in their right mind is going to start a lengthy debate with kernel developers when they have a deadline to meet and a product to ship.

      In the industry, getting things done on time is priority #1. Google's implementation may not have been ideal, but it was delivered.

      It seems to me you have a choice. Deal with the policy seeing as you aren't in charge or write your own damn operating system. Fork Linux and see just how that works out for you. Come one Google. Can't write your own OS?

    19. Re:Lots of comments on LWN.net's coverage by swillden · · Score: 4, Insightful

      I think thats the whole issue here. Why does Goggle have to do any work to get "accepted" into the main kernel anyway?

      They don't have to. If they don't, however, their codebase and the mainline codebase are going to grow further and further apart, which means that (a) the Android kernel will not be able to easily gain the bugfixes and enhancements that go into mainline and (b) the mainline kernel will not be able to easily take advantage of the drivers written for the Android kernel. Both will lose.

      I strongly suspect that what will ultimately happen, as has happened before, is that the Android devs will eventually realize that maintaining their own fork of the Linux kernel is just too much effort and that it is actually less work to do what's required to get their changes integrated into mainline. Many other companies have been through this same process and come to the same conclusion.

      --
      Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
    20. Re:Lots of comments on LWN.net's coverage by Obsequious · · Score: 1

      Why do you even bother, man? :)

    21. Re:Lots of comments on LWN.net's coverage by Anonymous Coward · · Score: 0

      AC commenting pussy, show some respect.

    22. Re:Lots of comments on LWN.net's coverage by Foredecker · · Score: 1

      Nice post

      --
      Jibe!
    23. Re:Lots of comments on LWN.net's coverage by Pastis · · Score: 1

      One thing I don't understand is that chosing Linux is to implicitly acknowledge that the Linux development model works.

      And the Linux development model is about working with the community and getting things accepted upstream. Sure you can maintain a fork, but that's typically not done and considered not optimum.

      And when you see now that your downstream clients are asking help from the Linux community to get their things accepted, there's clearly a problem.

      So now, I really hope that if one day Google finds that their approach wasn't the best one, that they do a retrospective / 5 why's / whatever session and find out that maybe they should have had a different interaction with the community.

      Getting things to market is important. Getting it with too much code clutter may not be the best thing in the long run.

    24. Re:Lots of comments on LWN.net's coverage by Pastis · · Score: 1

      Because drivers become tied to the new model and can't be accepted upstream ?

      Because Google's clients are asking for help to get their code included (they don't want to maintain it all the time, yet can't get it past the door the first time).

      > Lets be honest here though, all the code is in GPL so whats stopping someone else from doing the work?

      time ? cost ?

      If your brother destroys the family jigsaw puzzle, are you just going to step and do it again, or are you going to ask him to fix it ?

    25. Re:Lots of comments on LWN.net's coverage by Yvanhoe · · Score: 1

      I still have some faith the Google has now too much OSS developers on its staff for this to happen without serious efforts made at mending the gap.

      --
      The Wise adapts himself to the world. The Fool adapts the world to himself. Therefore, all progress depends on the Fool.
    26. Re:Lots of comments on LWN.net's coverage by TheRaven64 · · Score: 1

      For a company that wants to stay around for more than the next quarter, getting things done on time and getting things done in a way that doesn't generate long-term overheads are both high priorities. Using open source code can save you money because you get other people contributing - fixing bugs and so on - but a lot of these benefits evaporate if you have to maintain a fork. If getting it done right will delay the launch by a week but save thousands of hours of developer time over the next year, it may well be the right solution.

      --
      I am TheRaven on Soylent News
    27. Re:Lots of comments on LWN.net's coverage by Eunuchswear · · Score: 2, Informative

      Might be rather hard to "clean up". Back in 2008 Mathew Garret wrote:

      Google was going to be an interesting case of a large company hiring people both from the embedded world and also the existing Linux development community and then producing an embedded device that was intended to compete with the very best existing platforms. I had high hopes that this combination of factors would result in the Linux community as a whole having a better idea what the constraints and requirements for high-quality power management in the embedded world were, rather than us ending up with another pile of vendor code sitting on an FTP site somewhere in Taiwan that implements its power management by passing tokenised dead mice through a wormhole.

      To a certain extent, my hopes were fulfilled. We got a git server in California.

      --
      Watch this Heartland Institute video
    28. Re:Lots of comments on LWN.net's coverage by Anonymous Coward · · Score: 0

      Yes, those guys can be a pain in the ass. Their arrogance is the reason why I no longer contribute to Android and will get a Nokia N900 very soon.

    29. Re:Lots of comments on LWN.net's coverage by bill_mcgonigle · · Score: 1

      if they don't like how we use the kernel, we're unlikely to be accepted upstream

      I think we all know how this story ends - it's only a matter of how long it takes and how much it costs to get sync'ed back up with mainline.

      Given that, the longer it takes the more it's going to cost everybody, so better to just get on with it now, and it's done when it's done (assuming you can offset future budget with current budget).

      --
      My God, it's Full of Source!
      OUTSIDE_IP=$(dig +short my.ip @outsideip.net)
    30. Re:Lots of comments on LWN.net's coverage by Anonymous Coward · · Score: 0

      > If they don't, however, their codebase and the mainline codebase are going to grow further and further apart
      Not necessarily. There's another possibility - someone else can do the work to adapt Googles code to mainline. It can happen, if other Googles fixes, otherwise unaccessible, will be attractive enough for mainline devs/users.

    31. Re:Lots of comments on LWN.net's coverage by VON-MAN · · Score: 1

      "passing tokenised dead mice through a wormhole"
      Ah yes, somehow I remember that quote.

    32. Re:Lots of comments on LWN.net's coverage by swillden · · Score: 1

      Not necessarily. There's another possibility - someone else can do the work to adapt Googles code to mainline. It can happen, if other Googles fixes, otherwise unaccessible, will be attractive enough for mainline devs/users.

      Adapting Google's code to make it acceptable to the Linux developers will mean redesigning it, changing the API from something that very narrowly serves Google's needs to something that is general and flexible enough to serve not only Google's requirements but many others as well. The result will be something that will require Google to change their non-kernel code to make use of the improved kernel API.

      So, if someone else did do the work and got it into the mainline kernel, but Google didn't buy in and do the work to use the new API, then we'd be exactly where we are, with Google managing its own kernel. Other people might make use of the new API, which would be a good thing, but it wouldn't address the issue of the Google fork.

      --
      Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
  8. Android phones.. by Anonymous Coward · · Score: 0

    So does this mean I should or should not have hacked my android phone?
    The rain shrunk my brain up too much to think.

  9. No, I don't think so by Concern · · Score: 5, Interesting

    Google has frankly set a new standard as far as how companies can become very successful by embracing the open and free software communities. I honestly don't think you can point to many other companies that are doing better, nor could you realistically expect to. In the mobile space, pretty much the next nearest competitor in terms of openness is Apple (Darwin, et al) - in other words, a joke. Meanwhile Google not only has a wonderfully organized system for playing with all the Android code, but a broad commitment across products. Look at Wave, for instance - wide, wide open, and very deliberately (because they know it cannot succeed any other way). Google has probably done more for Linux and its credibility than most other companies in the world.

    I think this is something totally different - a disagreement about direction between the mainline maintainers and Google's Android team. Corporate developers, even well-intentioned ones, have a conceptual hurdle to get over when someone Not Their Manager is telling them "you must spend x man-months refactoring your code thusly."

    Many, many companies have run into this issue with Linux (and other projects) before, and many will again. It usually goes something like this:

    Step 1: Whatever. We're Google. Am I going to rearrange my whole development roadmap to follow the directions of some whiny nerd in his mom's basement? LOL.
    Step 2: Oh. Crap. Wow it is kind of a lot work maintaining my own entire fork of the Linux kernel/KHTML/etc. all by myself.
    Step 3: Either A) capitulation - the last guy is fired or smacked with the clue stick, and the cooperation restarts, or B) a true fork. These usually stagnate and die, and are also riddled with bugs and security holes btw... unless, the fork is really more interesting than what it forked from, in which case, the community switches to the fork and justice is served.

    Often between Step 1 and 2, the maintainer will attempt to play a little corporate politics by embarrassing said middle manager in the media. By the way, this is pretty smart and it often works - especially with companies as large but otherwise savvy as Google, a slashdot story can jumpstart efforts to mend the rift by bringing more senior eyes on the problem. Cooperating is in everyone's interest, and they will realize it.

    --
    Tired of Political Trolls? Opt Out!
    1. Re:No, I don't think so by bonch · · Score: 1

      Google has frankly set a new standard as far as how companies can become very successful by embracing the open and free software communities.

      Google can afford to do that because their core, the search and ad engines, are closed source web technologies. They only use free software to get people onto their indexing and advertising platform while the stuff that matters is as closed as Windows.

      That's one of the reasons all the good will Slashdot gave Google over the years was bullshit.

    2. Re:No, I don't think so by Anonymous Coward · · Score: 0

      In the mobile space, pretty much the next nearest competitor in terms of openness is Apple (Darwin, et al) - in other words, a joke.

      I'm not quite sure what you mean by "next nearest competitor", but this isn't true for the mobile smartphone market. Nokia has Symbian (now open source), Maemo, and Qt. I know both companies (Nokia and Google) have even more open source contributions, but to say that Apple is next nearness in openness is inaccurate.

    3. Re:No, I don't think so by Anonymous Coward · · Score: 0

      Windows Mobile is pretty open. No silly limitations about where your apps go and how much space they can take and the APis are all published online. It's one of the reasons Fennec developers are targeting Windows Mobile as the other platform they'll support from the start besides Linux.

  10. Wait, I take it back by Concern · · Score: 2, Insightful

    Somehow I managed to forget Nokia for being more open than Apple - and arguably - Google. I guess because so few people use, or will likely ever use, their smartphones. :)

    --
    Tired of Political Trolls? Opt Out!
    1. Re:Wait, I take it back by marsu_k · · Score: 1

      Yes, only 21 million of them were sold in the last quarter. (hint: USA != world)

    2. Re:Wait, I take it back by Concern · · Score: 3, Insightful

      I can't find anything yet that actually gives N900 or Maemo sales figures. Your link does not - I am all ears if you have something. Something tells me that Nokia isn't anywhere remotely near selling 21 million devices truly comparable to iphone or android in Q4. "Converged mobile device volumes" is very carefully worded and my guess, careful weasel wording is the only way the can come up with a number so impressive-sounding.

      Apple has only shipped 75 million iphone and ipod touch devices combined worldwide, and something like 8.7 million iphones in Q4. So if Nokia "true" smartphones were outselling Apple smartphones by such a margin, in any way shape or form, I think that would be bigger news, no?

      I think this confusion comes from Nokia labelling any $50 gadet of theirs with a dime-store web browser and a music player as a "converged mobile device." But even in this case I should have qualified my remarks as referring to smartphones, rather than just "mobile."

      --
      Tired of Political Trolls? Opt Out!
    3. Re:Wait, I take it back by sopssa · · Score: 1, Insightful

      Uh patent trolling? Nokia is one of the companies that actually deserve any patent they hold. They have spent millions in generating the mobile technology we all use today.

      Btw, your signature having a link to your money making "iPhone app reviews" website kind of makes you biased.

    4. Re:Wait, I take it back by marsu_k · · Score: 1

      A quick googling didn't turn up any sales figures for N900 (which is the only device at the moment running Maemo that is also a phone), but I doubt they're significant - the device went on sale in December in most places, and supplies have been scarce. I don't know the metric Nokia uses for defining a smartphone, but I recon it's based on whether a phone runs S40 (low-end, cheap models) or Symbian/S60 (aka smartphones). Given that they sold ~50 million phones in the previous quarter, and given how common S60 in various versions is in Nokia phones currenlty, I find this reasonable.

      Now you may argue that S60 phones are not smartphones, and I'll admit the platform certainly shows it's age and should probably be replaced with Maemo on all high-end devices. The latest version (S60v5, aka the touchscreen version) really has a "lipstick-on-a-pig"-feel to it. But from very early on it has offered many features associated with smartphones (and not found on iPhone), like multitasking and installing applications from anywhere. Hell, it even had a Webkit-based browser before iPhone was released. As to why this is not being reported more, Apple is the media darling, and Nokia has been really boring as of late. N900 has sparked some media interest though.

    5. Re:Wait, I take it back by Enderandrew · · Score: 1

      I don't make a cent off the site. I help write reviews from time to time for free. I have a love/hate relationship with the iPhone. It is the only Apple product I own.

      And I only own an iPhone because I couldn't get service for a G1 in Omaha when I purchased my last phone.

      --
      http://blindscribblings.com - Tasty pop-culture in conceptual fashion.
    6. Re:Wait, I take it back by Anonymous Coward · · Score: 0

      Rumor has it that Nokia recently increased the number of N900 devices manufactured from 30k to 100k per month. This gives a vague idea of the sales figures.

    7. Re:Wait, I take it back by Anonymous Coward · · Score: 0

      I have not seen sales numbers for Maemo devices, but Nokia's "Converged mobile devices" are not intended to suggest only Maemo devices. I am pretty sure the designation is intended to include powerful S60 devices such as the Nseries and the Eseries. Whether you like Symbian or not, those devices are certainly sufficiently powerful, flexible and programmable to be considered smart phones.

      According to the Nokia press release, they sold 20.8 million converged devices in the fourth quarter of 2009. If you add in the cheap phones, they sold 126.9 million devices(!) in the fourth quarter of 2009.

      The fact that Nokia continues to out sell Apple is not news. Nokia smart phones have always out sold Apple. The real news is how fast Apple has taken market share from Nokia and other mobile phone players. It would also be big news if Nokia starts to lose smart phone market share to Apple in Europe or India. (As far as I know, this has not happened...yet.)

    8. Re:Wait, I take it back by Anonymous Coward · · Score: 0

      Since you don't seem to like the definition of smart phone that puts Nokia clearly in the lead, maybe you could re-define the term? I'm serious, please put up some actual details about your definition and not "comparable to iphone".

      You may not like S60 but it is quite featureful... I'm sure you can find a definition that somehow excludes most S60 phones but I doubt it will seem like a natural definition.

    9. Re:Wait, I take it back by TheRaven64 · · Score: 1

      This is the same Nokia who fought open standards for HTML5

      I can't exactly contradict this, but Apple also opposed Theora in HTML5 and Google, which owns the largest video sharing site, decided to go with H.264 as a content provider and support both Theora and H.264 as a browser maker.

      has been guilty of patent-trolling

      References? Hint: Investing a lot in R&D, making products based on the results, and then suing people who violate these patents does not count as patent trolling.

      and tried to kick OSS projects around in the past

      Really? The open sourced Symbian, they bought Trolltech and kept Qt open source, they contribute code to WebKit, but I can't think of any open source projects that they tried to kick around.

      --
      I am TheRaven on Soylent News
    10. Re:Wait, I take it back by Nursie · · Score: 1

      Ummm, what the HELL are youy smoking?

      Nokia has around 50% of the global smartphone market sewn up, with RIM coming in second and apple behind them. If they aren't big in the US that doesn't mean they aren't huge absolutely everywhere else, and beating the crap out of both google and apple in every market bar one.

    11. Re:Wait, I take it back by Anonymous Coward · · Score: 0

      It's not from Nokia, but almost:

      Thus, a new category of devices has been born. They’re not smartphones, they’re something else. And we love them.

      http://blogs.sonyericsson.com/troedsangberg/its-not-about-smartphones/

    12. Re:Wait, I take it back by jfanning · · Score: 1

      I think it is very funny how every time it is proved beyond any doubt that Nokia is the absolute king of smart phones that some whiney geek gets upset and thinks that they somehow redefined smartphone just to prove them wrong. Although I thought I had to be on AppleInsider to see comments like this.

      Nokia produces 40% of all smartphones on the planet. Get over it.

      Symbian is a smartphone OS, Maemo is a smartphone OS. It doesn't matter one fetid dingo's kidney if they can manage to put it in a phone that costs USD 100. Just because it conflicts with your world view that a smartphone must cost USD600 and be limited to white rich people doesn't make it so.

    13. Re:Wait, I take it back by Anonymous Coward · · Score: 0

      Olli-Pekka Kallasvuo - is that you??

      Seriously, Symbian is great. I don't know why they even made Maemo. After all there is no difference between Symbian smartphones and Maemo smartph... [sorry - my phone crashed, jk]

      They made Maemo for a reason. It's not my fault if it's not catching on.

      “When it comes to the myth of Symbian being a modern and robust OS, I have several objections. Symbian is severely limited by design decisions made in the beginning of '90. The design decisions were maybe okay at that point in time, when the target was Psion's EPOC and EPOC32-based Series 3 & 5 with extreme memory and resource constraints compared with today's devices.

      Look if you want I can modify my definition of smartphone so that Nokia loses just by including even less sophisticated phones too...

    14. Re:Wait, I take it back by Anonymous Coward · · Score: 0

      They made Maemo for a reason. [slashdot.org] It's not my fault if it's not catching on.

      What's that supposed to mean? Why should anyone be surprised that Maemo hasn't caught on yet when only 1 phone has been released with Maemo, and even that phone has only been out for 2 months. My impression from other peoples comments on the n900, is that it is not quite ready for mainstream, though I'm sure some would disagree. The n900 seems to be targeted at geeks so that Nokia can get some real-world feedback on it and Maemo before putting Maemo on their more mainstream smartphones.

    15. Re:Wait, I take it back by Anonymous Coward · · Score: 0

      It means Nokia is late to the party. They may find it difficult to gain mindshare for their "modern" smartphone platform now. Ultimately, because of this, Nokia may find themselves as irrelevant in the smartphone space as RIM and Palm. Just one prediction among many, but there it is.

    16. Re:Wait, I take it back by Anonymous Coward · · Score: 0

      I guess we'll just have to wait and see on that one, but I do think Nokia is big enough to pull it off even if they are relatively late bringing their modern offering to market.

  11. Re:up merge justification has to be Android-agnost by exomondo · · Score: 1

    Make a case for kernel support of the "new lock" and "security model" independent of Android's reliance on it, and remove as many of the Android drivers using these facilities OUT of the main tree.

    That's exactly right, we can't just be having code merged into the kernel mainline because a 'big business' depends on it. The answer to the question on it's presence there should be determined on the merit of the code itself, not the weight of the company proposing it.

  12. Technical aspects by shutdown+-p+now · · Score: 5, Informative

    "OMG fork!" and other political issues aside, I think it's interesting to look at the technical side of the problem. What is the exact nature of Google's changes to the kernel, why did they feel they need them, and are they actually a good idea or not? Can someone with kernel hacking experience enlighten us?

    I'm particularly curious after reading the comments on LWN, and specifically this:

    Kernel developers (including other embedded developers who have achieved good power savings modes) don't believe that the Android way of doing things is good.

    and this:

    The code could be mainlined if Google were willing to consider that their wakelock approach was suboptimal and adapt to a more reasonable one. ...

    The wakelock patches were first posted to the linux-pm list on the 13th of January 2009, which is just over a year ago. http://lwn.net/Articles/318611/ gives a good overview of how they were received - there's basically no buy in, even from other developers in the embedded Linux field. ...

    the major sticking point (ie, wakelocks) were posted for public review a year ago and most of the substantive issues people had with them weren't addressed at all in the four months of intermittent discussion that followed. If the entire world suggests that you do something in some other way and you refuse to, that doesn't constitute a genuine effort to work with them. Nokia have managed to obtain the same level of power management without such invasive changes, so any assertion that wakelocks are required for Android to achieve its goals seem pretty baseless.

    So apparently the issue at the heart of this is a questionable design decision by Google.

    1. Re:Technical aspects by Aladrin · · Score: 1, Insightful

      I love how they blast Google for not being willing to meet halfway, but they're doing exactly the same thing.

      Not that there's actually anything wrong with -either- side, but if you're going to redress someone for something, you should make sure you're not guilty of it yourself first.

      --
      "If you make people think they're thinking, they'll love you; But if you really make them think, they'll hate you." - DM
    2. Re:Technical aspects by Lunix+Nutcase · · Score: 1

      Yeah cause it's not like the kernel devs have ever turned down ideas that later they would implement themselves after years of denial that there's even a problem with their original design. *cough* Complete Fair Scheduler *cough*

    3. Re:Technical aspects by mjg59 · · Score: 5, Informative

      Some background on this:

      Android is written to automatically attempt to enter a sleep state whenever possible. So, for instance, when your phone is in your pocket the hardware is suspended. You get an incoming call. You pick up a phone and press a button. The button press fully wakes up the phone. What stops the phone from suspending again?
      Wakelocks are Google's solution to this. Pressing the button takes a named wakelock. While any wakelocks are held, the phone will not go back to sleep. Once the call is complete, userspace can release the wakelock and the phone will suspend again.

      The problem here is that your wakelocks are tied to your userspace. Userspace needs to know which wakelocks the kernel takes in order to be able to release them. Which wakelocks you want will depend on how your platform is designed. Google have implemented the wakelocks they need to solve the problems they face - other vendors may wish to use different wakelocks. The end result is that you end up with a kernel that can only usefully run with a specific userland, and userland modifications require kernel modifications. It's broadly like saying that it'd be fine for some kernel drivers to require gnome and some others to require KDE.

      What's depressing about this is that it's an entirely unnecessary approach. You don't need the system to fully suspend. Modern ARM hardware supports something generally referred to as retention mode, which is where the hardware enters a power state equivalent to suspend without actually performing a full state transition. Rather than explicitly suspending, if there are no tasks to run then the kernel idle routine will put the CPU into this state. When a task is scheduled to run (either because of a timer or in response to an event), it runs.

      The stated objection to this is that applications can't be trusted to behave themselves. If I write an Android application that repaints itself by sleeping for a frame and then drawing, that'll keep waking up the CPU. In the wakelock scenario, the system isn't running and so this isn't a problem. In the retention scenario, it'll keep getting scheduled and battery life will suffer.

      There's two easy solutions to this. The first is to use the range timer functionality in the kernel. This allows applications to say "I want to sleep for about a second, and can afford this much inaccuracy". The kernel uses this to attempt to merge wakeups - if an application sleeps for a second and a millisecond later another application does the same, they can both be woken up at once rather than causing two wakeups. But we can also take this to more extreme lengths, for instance by changing the accuracy value to a millennium when the screen is turned off. The application won't get scheduled again until we receive a "wakeup" event and set the timers back. The second approach is even simpler - just SIGSTOP all non-system tasks when we'd otherwise release the wakelocks.

      So I wouldn't frame this as refusing to meet Google halfway. People have tried to come up with solutions that would meet the usecases that Google want to deal with and which don't end up forcing people to tie their kernel to their userland. Nokia achieve comparable power consumption without any of the wakelock infrastructure, so it's clearly not a requirement in order to hit these targets. What would you expect a meeting halfway solution to look like?

    4. Re:Technical aspects by Anonymous Coward · · Score: 0

      Now, if that discussion could translate into a working ACPI subsystem on laptops would be novel! (here's an LWN discussion about what Google is doing wrong, yet we (the mainline) can't get laptops to come out of suspend mode right)...

    5. Re:Technical aspects by GooberToo · · Score: 5, Informative

      I love how they blast Google for not being willing to meet halfway, but they're doing exactly the same thing.

      It doesn't appear that's the case. It seems Google coded a bunch stuff without consulting other, more knowledgeable kernel developers. Google then announces what they've done and throw it over the wall. The feedback is the design stinks and is very fragile. They also ask why Google didn't leverage the existing infrastructure which is already working, and which seems to have been in place long before Google started, which addresses their very issue. Nokia via their Linux/OMAP ARM efforts don't seem to have trouble using the existing infrastructure.

      Google responds by saying the existing infrastructure isn't a complete solution for their needs. The kernel guys ask why Google didn't simply update the existing code to address their specific needs rather than add poorly conceived new code/interfaces. Even the Linux/Nokia guys step forward and state the existing infrastructure is plenty useful and powerful and is easily able to address Google's need with only minor changes. Furthermore, the general consensus is that the required changes can be made such that its fully compatible with their userspace applications.

      Google response? Who gives a shit?!?!? We don't need it upstream. Let everyone else fend for themselves. We don't care if it ads bloat and is unusable for anyone else.

      Now the kernel guys are left with unmaintained code, which nobody wants, which exists only to add bloat to the kernel, which benefits nobody but Google. Seems to me, Google doesn't care to meet in the middle and they've made it very clear its Google's way or no way. And as result, Android's kernel is more bloated because of it. Seems like a lose-lose for everybody while highlighting just how huge Google's ego can be.

    6. Re:Technical aspects by Anonymous Coward · · Score: 0

      What's depressing about this is that it's an entirely unnecessary approach. You don't need the system to fully suspend. Modern ARM hardware supports something generally referred to as retention mode, which is where the hardware enters a power state equivalent to suspend without actually performing a full state transition. Rather than explicitly suspending, if there are no tasks to run then the kernel idle routine will put the CPU into this state. When a task is scheduled to run (either because of a timer or in response to an event), it runs.

      When I was first learning about Android I asked some of the core developers how they handled sleep and suspension and what kept the device awake, etc. After asking questions along the lines of what you're stating, I was openly ridiculed by some. Granted, I do not believe these were Google's kernel developers but but just the same, it goes a long way to show just how out of touch and egotistical they can be.

    7. Re:Technical aspects by godrik · · Score: 1

      thank you very much for those explanations.

    8. Re:Technical aspects by nightfire-unique · · Score: 1

      All of this complexity makes me appreciate the beauty and simplicity of my n900. It doesn't suspend at all. It simply slows the processor clock to reduce battery usage while the screen is off. A heavy load task will encourage the CPU to upclock again if it needs it.

      Sure, battery life isn't as good as Android's. But really... how often are you without a USB charge port for longer than 48 hours?

      --
      A government is a body of people notably ungoverned - AC
    9. Re:Technical aspects by Anonymous Coward · · Score: 5, Interesting

      I'm commenting anonymously because I'm closely involved with Android. I'm not going to comment on whether wakelocks are good or bad.

      But mjg59's comment about ARM retention state being as good as suspend is blatantly wrong at a SoC level. There are several good reasons why a suspend details is better than retention but I can't go into the details due to NDAs. But I can vouch that I have personally seen power usage shoot up on well known Android phones when suspend is disabled and only retention is done.

      So, mjg59, I would kindly request that you stop making such claims. I doubt you have worked on embedded devices -- I believe you work on server level stuff -- but you most certainly haven't worked extensively on the SoCs being used on Android phones.

      Just to make my stance clear, I'm all for having the Android kernel merged into mainline.

    10. Re:Technical aspects by Aladrin · · Score: 1

      From what I've read on this, Google devs are under NDA and can't just willy-nilly discuss the issues with the public. But they -do- have good reason for what they've done and they aren't just covering their ears and ignoring everyone.

      --
      "If you make people think they're thinking, they'll love you; But if you really make them think, they'll hate you." - DM
    11. Re:Technical aspects by mjg59 · · Score: 3, Interesting

      Firstly, thanks for posting this. It's the kind of thing that we never really got out of previous discussion on the topic, which makes it much harder to make reasonable technical decisions.

      Secondly, your results are interesting. I'd be fascinated to know whether they're due to the implicit differences between retention and suspend (ie, transitioning to full suspend stops processes that would otherwise be generating wakeups while retention doesn't, or cuts power planes that should otherwise be powered down manually) or because of fundamental silicon level issues. On the other hand, I don't think it fundamentally matters. We have an rtc that's capable of generating wakeup events, so it's acceptable for the lowest level runtime idle state to be system suspend with the rtc set for the next scheduler tick. Just make sure that the latency values are set correctly and it ought to work fine with the existing cpuidle code.

    12. Re:Technical aspects by GooberToo · · Score: 1

      From what I've read on this, Google devs are under NDA and can't just willy-nilly discuss the issues with the public. But they -do- have good reason for what they've done and they aren't just covering their ears and ignoring everyone.

      There are many ways around that. Often companies approach this in one of three ways. One, make someone unknown to the outside world use a non-company email address and explore the issue with those more knowledgeable without fully letting the cat out of the bag. Or two, privately email one or more of the knowledgeable developers, politely state the sensitivity of the issue due to an NDA and ask for general guidance based on general details. Or three, hire one or more of these guys for a short consulting gig and officially extend the NDA.

      Google chose a forth option which appears to make no one happy. I think the fact that Google chose the path least traveled speaks loudly about Google in general. Others seem to agree.

    13. Re:Technical aspects by pslam · · Score: 5, Interesting

      So, mjg59, I would kindly request that you stop making such claims. I doubt you have worked on embedded devices -- I believe you work on server level stuff -- but you most certainly haven't worked extensively on the SoCs being used on Android phones.

      I have worked on embedded devices - Linux based and others - for over a decade, and mjg59 is right. If you need something as brutal as hard suspend mode, you're doing it wrong. Any serious low power optimized ARM SoC can run down to very low current when idle, and has peripherals which can be individually clocked down and/or gated. I did work in a periphery way on the G1 at Google, and was very surprised at the way power gating was done. Put simply: the only other embedded OS in the same class as Android which does power gating like this is Windows Mobile. Everyone else learned it was unnecessary a long time ago. I was fairly shocked how few engineers had ever done serious embedded work before, and the result shows.

      I know the Qualcomm parts have horrendously stupid design decisions in them which prevent decent idle current, but it's a wash compared to the other sources of battery drain. It's also a wash compared to the damage it does to your code design to support full suspend as part of normal per-second operation.

      The Linux maintainers are right: Android is just doing it the wrong way. If there's any one feature I think Android could have done without, it's wake-locks. Learn how to use fine-grained clock switching and gating, not brutally-coarse-grained suspend. This isn't a bloody laptop. And no, I'm not saying this as a back seat driver: I really have done this kind of crap for a decade.

    14. Re:Technical aspects by Anonymous Coward · · Score: 0

      No, you are wrong. I'm involved in ARM development, and I also have signed an NDA, so I can't state why you are wrong, but you are.

  13. An oldie but a goodie: by Ossifer · · Score: 1

    "Embrace & extend"!

    1. Re:An oldie but a goodie: by Sir_Lewk · · Score: 1

      Since when is forking considered "embracing"?

      --
      "linux is just DOS with a UNIX like syntax" -- Galactic Dominator (944134)
    2. Re:An oldie but a goodie: by Virtucon · · Score: 1

      Embrace, Extend and Eradicate is more like it.

      This is what I love about FOSS, these little tiffs can now be on public display to just show how petty organizations or individuals can be.

      I don't pretend to understand why this rift exists however I do know that market forces can move mountains.

      --
      Harrison's Postulate - "For every action there is an equal and opposite criticism"
    3. Re:An oldie but a goodie: by Sir_Lewk · · Score: 1

      I'm well aware of how embrace, extend and extinguish works, but I'd say they prematurely ended phase 1. It's not like android has enough weight right now to make them forking (extending) really matter. Not to mention, this is all pretty much over some shitty poorly thought out modification what isn't useful for anything except android. Not exactly an effective extend...

      --
      "linux is just DOS with a UNIX like syntax" -- Galactic Dominator (944134)
  14. Whoa there Cowboy by mpapet · · Score: 0, Troll

    Your representation of the facts is suspect on a number of fronts.

    The short form is that if they don't like how we use the kernel, we're unlikely to be accepted upstream.
    You casually forget to mention your introduction of a completely new lock method. This is a case of Google throwing code over the wall. That's not going to fly. When some suggestions are made regarding the method, they are ignored.

    Then, there are proprietary dependencies that can't be released that breaks the build process. No effort is made on Google's part to make this play nice with a kernel build. More code throwing.

    Then there are implications to other ARM builds that Google won't touch.

    It's all still released as source code to the world
    Which creates problems for practically every ARM platform developer BUT Google.

    Outside of the Google Reality Distortion Field, the code just doesn't work. At all.

    --
    http://www.maxineudall.com/2010/02/should-economists-be-sued-for-malpractice.html
  15. Option B by zogger · · Score: 2, Interesting

    Has there ever really been a serious option B effort to just pick a time and do a major kernel fork and maintain it forever by any company as large as google, with their level of developers and resources/cash behind them? Any precedent there?

    1. Re:Option B by Enderandrew · · Score: 1

      They would only really be responsible for maintaining a set of patches, not a full-on fork.

      Plenty of projects exist outside the mainline kernel that will likely never be merged upstream.

      --
      http://blindscribblings.com - Tasty pop-culture in conceptual fashion.
    2. Re:Option B by Kjella · · Score: 1

      Has there ever really been a serious option B effort to just pick a time and do a major kernel fork and maintain it forever by any company as large as google, with their level of developers and resources/cash behind them? Any precedent there?

      Not to my knowledge, but from the grandparent you'd think this would be resolved quickly one way or the other. Google could just keep a patchset and rebase from the vanilla kernel from time to time like pretty much every distro does and which will work just fine unless it's an area where the kernel devs are also rewriting a lot. Then their kernel and their drivers would have it and the vanilla kernel wouldn't.

      --
      Live today, because you never know what tomorrow brings
  16. Android is open source so does it really matter? by thetoadwarrior · · Score: 2, Insightful

    I suspect this isn't clear cut and there is more than a little "Google is too big we must hate them now" attitude. The fact is Android is open source and anyone can take their code do what they want with it just as Google can take any other open source code and do what they want with it.

    That's the point of open source code. Claiming something is open and all about freedom and then trying force everyone into doing what you think should be done is neither really free or open.

  17. Re:Anonymous Coward by Anonymous Coward · · Score: 0

    do you know blowjob? so, the tuscan verb "puppare" is litterally "to make a blowjob"; in my way, is in a methaphoric sense.

  18. Re:Anonymous Coward by Anonymous Coward · · Score: 0

    Y'a quelqu'un qui comprends ce que Anonymous Coward a écrit? Moi je n'y comprends rien.

    Courtesy of the google translator ...

    As they say in Tuscany, as the gay guy UnitedStatesOfNorthAmerica.

    There was to be expected.
    Good night America.

    Still no idea what it meant. :-P

    I know this is a time waster, but my knowledge of spanish somewhat helps with both languages. The italian one probably means "Like we say in Tuscani, 'There's a lot of gay guys in the United States... just as expected.'" to mean that the poster finds nothing unpredictable with the kernel change.

    The french reply i'm guessing more "Wasn't I the only one who [always] understands what Anonymous Coward writes? But I [notice they are both anons] didn't understand this at all."

  19. Yes, Redhat by Concern · · Score: 4, Interesting

    "Redhat Enterprise Linux 5" is essentially a massive kernel fork at 2.6.18. Redhat is the most plausible contender for doing this, since they employ a really significant number of the world's kernel devs, including Alan Cox (until last year). That split was even acrimonious at times IIRC. But then again, you can just call it similar to Canonical's LTS - people choose whether to go with a version of something that's more or less mature - and most distros going with the "more mature" option frequently cheat and backport all kinds of things in the meantime (with greater and lesser success).

    Depending on who you ask, RHEL can be more risky than mainline. I've definitely had RHEL panics take down production, only to later discover linux kernel bugs that had been fixed in mainline for a while, but that redhat hadn't backported to their ancient linux fork. But then again, people get burned going the other way all the time too. I don't know if anyone's really independently studied what's ultimately safest. My guess is that you are usually safest inside the biggest crowd - i.e. closer to mainline - but not too near the very latest version.

    --
    Tired of Political Trolls? Opt Out!
    1. Re:Yes, Redhat by TheRaven64 · · Score: 1

      RHEL also had the fun distinction of not being quite ABI-compatible with the main kernel. They used an unused flag in one system call, then the main branch used the same flag to mean something different in a later version.

      --
      I am TheRaven on Soylent News
    2. Re:Yes, Redhat by shallot · · Score: 1

      "Redhat Enterprise Linux 5" is essentially a massive kernel fork at 2.6.18.

      Yes. When I last checked a few weeks ago, they had over 4000 individual patch files in that source RPM. Nevertheless much of that code must simply come from newer mainline. So it's a fork of the mainline 2.6.18 release, which is dead upstream anyway since 2007-02-24.

    3. Re:Yes, Redhat by Nevyn · · Score: 1

      "Redhat Enterprise Linux 5" is essentially a massive kernel fork at 2.6.18.

      Backporting a lot of patches is not the definition of fork, for any sane person. Esp. when that same group of people are actively working upstream on the latest releases.

      Depending on who you ask, RHEL can be more risky than mainline.

      Sure, if you ask stupid people questions they can often give you stupid answers. But I've yet to see anyone intelligent run a vanilla upstream kernel in a production environment. Google are probably the closest, and they basically have a mini-RHEL kernel team that they employ ... I guess wasting huge amounts of money to do that isn't a big deal when you are Google.

      I've definitely had RHEL panics take down production, only to later discover linux kernel bugs that had been fixed in mainline for a while, but that redhat hadn't backported to their ancient linux fork

      Shocker, software having bugs. But here's a hint, if we play chess 30 times and you win 1 match ... that doesn't mean we are both winners, "depending on who you ask". Maybe you really are trying to say that RHEL vs. vanilla are going to have roughly the same number of bugs (and the same time to get them fixed) ... but you'd be a pretty small minority at that point.

      --
      ustr: Managed string API with ave. 44% overhead over strdup(), for 0-20B
    4. Re:Yes, Redhat by Concern · · Score: 1

      Wow, work for Redhat? Stockholder? :)

      Other distros are closer to mainline and this is really all I'm saying. Redhat may claim their code is more appropriate for the enterprise - and maybe it is. But any guise of maturity is an illusion. They run 2.6.18 with almost 4000 patches consisting of almost 4 million lines, that they've been developing in parallel with mainline for almost 4 years. If their patches are pulled from mainline, or are similar, or different, or one day get merged, or not, the bottom line is this is a monumental effort, their kernel is different and diverging, and it is not more "mature" than mainline - it's just coming from a different team with different processes, priorities, and people.

      By comaprison Ubuntu 9.10 has divergence too, from 2.6.31. Their patch - in a single file - is about 308k lines - or less than 10% of Redhat's effort in terms of volume. Their 8.04 LTS release (which is more like RHEL in conservative approach) is based on 2.6.24, and that patch runs ~551k lines since Spring 2008, as it nears the end of its support life in a couple of months.

      If you want to argue semantics, it is pretty fun, I won't stop you. Just don't fool yourself that you're doing anything more, or that you really sound more convincing giving a definition than, say...

      "As Linus Torvalds has pointed out, in the Open Source world, there always are forks; whenever someone creates a patch and submits it for inclusion, a fork is temporarily created." -tytso

      Does Redhat get a lot of its patches merged, ultimately? Why yes they do. So it's an amicable fork not so different from the old AC kernels - in fact, that has its roots in them.

      "And certainly "code forks" in the form of the Alan Cox, David Jones, Andrea VM trees, et. al, have certainly not hurt the Linux kernel development community; in fact, they are an important and invaluable part of the Linux development process." --ibid

      Look, you are better off arguing that Redhat is a fork and it is more relevant than mainline, since more people use it. Or maybe you are actually arguing that, I'm not sure.

      But you can read what I wrote - I don't make any claims about reliability. I only tell my story and raise the question. It's about mindshare, and often when companies try to go it alone on this stuff, they get in over their heads. In a way, every old unix variant tells this story...

      --
      Tired of Political Trolls? Opt Out!
  20. In summary... by rickb928 · · Score: 2, Informative

    Google has silently forked the kernel. There is an 'Android' kernel, and the mainline kernel

    Is this the first time this has happened?

    Will it matter?

    Apparently, this is reasonably well understood.

    I, for one, welcome our Android kernel overlords. My phone doesn't need server optimizations.

    --
    deleting the extra space after periods so i can stay relevant, yeah.
    1. Re:In summary... by cynyr · · Score: 1

      but it seems to need Android bloat, see the part with the linux/Nokia devs saying that the current systems in place would almos work, but would require a bit of minor tweaking to work for google. Google goes out and makes changes all over the place.

      --
      All of the above was encrypted with a Quad ROT-13 method. Unauthorized decryption is in violation of the DMCA.
    2. Re:In summary... by rickb928 · · Score: 1

      I'm more interested in how anyone expected to see the mainline kernel on Android phones. Kernel bloat is not what you want on a phone, and if Google is driving a leaner or better kernel for Android, I'm all for it.

      Of course, Android is its own project. Perhaps there needs to be a Google-less Android? Which would require some work on several apps.

      --
      deleting the extra space after periods so i can stay relevant, yeah.
    3. Re:In summary... by Anonymous Coward · · Score: 0

      You realise you can, at compile-time, remove almost all (if not absolutely all) of the 'kernel bloat' you speak of, correct?

    4. Re:In summary... by rickb928 · · Score: 1

      I have more to do than compile my phone kernel. I'll get a ROM.

      There is more to life than compiling your rig.

      --
      deleting the extra space after periods so i can stay relevant, yeah.
    5. Re:In summary... by Eunuchswear · · Score: 1

      Where do you get the idea that Google's kernel is "leaner" or "better"? It has extra stuff the mainline doesn't - "wakelocks", "binder". Google haven't removed stuff, they've added extra stuff that makes it hard to port drivers from Android to mainline.

      Of course, Android is its own project. Perhaps there needs to be a Google-less Android? Which would require some work on several apps

      Apparently this may be the way forward. Leaves everyone with hardware that's only supported by Android in the shit though.

      --
      Watch this Heartland Institute video
    6. Re:In summary... by rickb928 · · Score: 1

      "Leaves everyone with hardware that's only supported by Android in the shit though"

      I'm confused. What hardware running Android now needs any other support?

      This is interesting to say the least. I get the impression that the community thinks Android should be more like Linux than Android. But it's intended to be a phone OS. If the future of Android is to include portable/mobile devices, then it is now to decide if the Android community wants to accept Google's influence and control. If not, fork and get on with it. There are several good distros (ROMs in fonspeek) that are almost independent of Google, and it must be possible. If not, well, then Google *owes* Android and all this is moot.

      --
      deleting the extra space after periods so i can stay relevant, yeah.
    7. Re:In summary... by rickb928 · · Score: 1

      Oh, and while we're at it, a phone has different needs than a desktop PC or a server. So forking the kernel makes sense.

      Google 'adding stuff'? The two-step they pulled off to let Dalvik bypass Java ME and avoid licensing adds complexity but solves a problem. It's necessary to make an open-source platform for phones, and it works. Along the lines of 'why a VM?', I think 'why a fork?' fits in the same slot. But yes, I suspect Google likes this to maintain control of Android.

      So much for 'do no evil', but we've known this for quite a while.

      --
      deleting the extra space after periods so i can stay relevant, yeah.
    8. Re:In summary... by Eunuchswear · · Score: 1

      I'm confused. What hardware running Android now needs any other support?

      Because we know that the current kernel is perfect and no improvements or new features will ever be implemented.

      --
      Watch this Heartland Institute video
    9. Re:In summary... by Eunuchswear · · Score: 1

      Oh, and while we're at it, a phone has different needs than a desktop PC or a server. So forking the kernel makes sense.

      Really? Apparently Nokia (among others) disagree.

      --
      Watch this Heartland Institute video
    10. Re:In summary... by rickb928 · · Score: 2, Interesting

      Example?

      N900? Heavily marketed as something a lot like the G1. Usually as a 'Mobile Internet Device and Smartphone'. I interpret that as an even more general-purpose mobile platform. They chose (probably because they started before Android was) to not use Android, the alternative was, um, Linux. And I see them not going to Android, I think they mistrust Google even more.

      This is an area where there is disagreement. But phones DO have different needs. Obviously. Nokia accomodated those within the mainline (?) kernel. Google drove Android in a very different direction.

      Let's not get into the Maemo thing. It's just a little different, not quite as much as Android.

      --
      deleting the extra space after periods so i can stay relevant, yeah.
    11. Re:In summary... by T.E.D. · · Score: 1

      Google has silently forked the kernel. There is an 'Android' kernel, and the mainline kernel Is this the first time this has happened?

      Hardly. It happens every time anybody makes a kernel mod. First they pull down the kernel, then they make their custom mod (technically a fork), then they wrangle with the gatekeepers over how/if their mod can be put into the baseline.

      I understand it is fairly typical for new mods from first-time submitters to get extra-skeptical treatment. Once the developer has been around a while, learns how to work with the other interested parties, and shows a willingness to do so, things get much easier.

      The only thing that makes this news is that an employee of Google is getting the same treatment as you or I would get. Some may find that appalling, but I think it is the way things should be.

    12. Re:In summary... by Eunuchswear · · Score: 1

      N900? Heavily marketed as something a lot like the G1.

      Really? You've seen an N900 ad that mentions the G1?

      They chose (probably because they started before Android was) to not use Android, the alternative was, um, Linux.

      Yes Nokia chose not to use Android because Android didn't exist.

      This is an area where there is disagreement. But phones DO have different needs.

      Mere repetition isn't proof. What do you think the specialised needs of phones are? Tokenized dead mice? Hardcoded user Id's?

      Obviously. Nokia accomodated those within the mainline (?) kernel.

      what's with the question mark?

      Google drove Android in a very different direction.

      which was chucking a mess of unmaintainable hacks in the kernel?

      Let's not get into the Maemo thing. It's just a little different, not quite as much as Android.

      A little different, how exactly?

      --
      Watch this Heartland Institute video
  21. Re:up merge justification has to be Android-agnost by SchroedingersCat · · Score: 3, Insightful

    Kernel development isn't driven by the product needs but by egos people maintaining it. In that sense it is no different to any closed source kernel. The only option to get things done quickly is to fork it and then hope to get it merged later. Linus isn't exactly known as "accommodating" and "reaching out" individual and merging code upstream isn't exactly a priority on Google product schedule so there.

  22. Apple and BSD by EEPROMS · · Score: 1

    I can't see what the issue is, if Google wants to make their own fork of Linux go for it, that is what FOSS is about, "CHOICE!!". Apple have done this with their own version of BSD (Darwin) and added lots of things not in the mainstream flavours of BSD and they are doing fine thank you.

  23. Re:Anonymous Coward by Anonymous Coward · · Score: 0

    do you know blowjob? so, the tuscan verb "puppare" is litterally "to make a blowjob"; in my way, is in a methaphoric sense.

    Ooooh, Slashdot. Now with more Italian lessons. =)

  24. Re:Android is open source so does it really matter by Paradigm_Complex · · Score: 1

    Android is open source so does it really matter?

    It's not black-and-white. It's better then Android being closed source, but it's not as good as it could be. It'd have been better (for the public, not necessarily Google) if Google got the android-specific changes to the Linux kernel in the mainline kernel. This would require quite a bit of back-and-forth with the kernel devs, though, and a lot more time and money then Google would truly have to spend to get Android on the market.

    --
    "A witty saying proves nothing." - Voltaire
  25. Re:up merge justification has to be Android-agnost by Chousuke · · Score: 0

    No. Drivers need to be merged to mainline. The kernel devs have been trying to hammer this point through for ages.

    The reason of course is that there is no stable kernel API, and the developers are completely uninterested in maintaining one... And it's not necessary if all drivers are part of the mainline.

    I know it sounds like circular logic, but the documentation at http://www.kernel.org/doc/Documentation/stable_api_nonsense.txt clarifies the reasoning.

  26. Re:Anonymous Coward by godrik · · Score: 1

    the french reply means "Does anybody understand what AC said ? I am really clueless"

  27. OT Re:Technical aspects by ckaminski · · Score: 1

    What that looked like to me was someone who was furious that a person who self-taught himself C in less than a few years implemented a kernel scheduler that kicked the crap out of anything the community came up with to date.

    No way that dude could be better than me...

    Ego's abound everywhere, my friend...

  28. Lazy by CrypticSpawn · · Score: 1

    GPL says contribute your changes. Doesn't say one thing about contribute your changes, and make sure they work in the main tree. He himself said they were doing it, until people started complaining about how things were written or what not. So they stopped. I don't blame them one bit. It is kind of like writing a library to be in PEAR, you have a piece of code that works. And and you see people asking for a library and you submit it for a vote, they first don't like that you used the PHP license, they want you to use the BSD license, then they don't like your naming of the methods. Hell, has the people running PEAR, looked at the naming conventions of PHP (addslashes, mysql_connect) I basically said flip that and put it on google code. There are forks all the time in the linux kernel, they usually die out, but wouldn't it be fun if googles kernel was the only one to survive?

  29. anyone see the Feb. Linux Journal? by Anonymous Coward · · Score: 0

    I was wondering why the editorial in the February edition of Linux Journal was saying so much bad stuff about Google! I was like why all the google-hate from Linux users? Well, if Google forked the kernel, that would explain it....

  30. Btrfs vs ZFS by Anonymous Coward · · Score: 1, Interesting

    http://www.codestrom.com/wandering/2009/03/zfs-vs-btrfs-comparison.html

  31. Couple of things to say... apk by Anonymous Coward · · Score: 0

    "So yeah, it's pretty upsetting to me to see people say things like "Google does only care about OSS when it suits them and drops out instantly when it doesn't.". This kind of statement completely misunderstands how Google even works. This just isn't the kind of company where orders comes down from executives on high with the only motive being profit -- anyone who thinks otherwise obviously doesn't work here." - by Temporal (96070) on Wednesday February 03, @04:57PM (#31015460)

    You've got to understand how this place is @ times: There are a LOT of "trolls" around here, first of all. Secondly, most of them haven't even BEGUN to even "scratch" your level of accomplishment (& certainly NOT that of GOOGLE itself). If you can take this place in that context? You understand better as to some of the "commentary" around here - need I say more?

    Secondly? I absolutely LOVED hearing this part (I didn't think companies like this existed anymore):

    "Because of the bottom-up nature of decision making at Google -- and given that I was willing to do the work -- I had no trouble pushing this through." - by Temporal (96070) on Wednesday February 03, @04:57PM (#31015460)

    Man, again: I love the sound of THAT! Especially considering that's generally not "how it goes" elsewhere (at least not in my experiences in the professional working world as a coder)... makes me wish I worked @ GOOGLE in fact!

    (Why? I say that simply because in a tech field, a tech company should be run by "TECHIE TYPES"... which makes for perfectly good sense, considering that nobody knows another "geek" as you put it, like geeks!)

    Keep up the good work man, & ignore the "trollish" comments (plenty of that goes on here, trust me, I know (6 yrs. of it almost in dealing with it many times here, which is the "WHY" of why I post as "A/C" here on THIS site - to make it harder for the trolls to track & troll me is all - pretty simple actually!)).

    APK

    P.S.=> I have to admit something though: I have recently made the acquaintance of a mgt. person @ MICROSOFT who posts here under the "pseudonym/nick/handle" of Foredecker, & upon my finding out more of his background in this "art & science" of computing? Well... I was pretty impressed, & especially from a mgt. person @ MS of all places. Upon speaking to he here (which didn't start out on the "best note")? It turns out he is EXACTLY that kind of guy, Comp. Sci. B.S. & all as well as having worked for AMD before his time @ MS (since 2003 to now)... it's good to see that the "ERA OF THE MBA ONLY TYPE" is passing, especially in "tech-oriented" companies... "The Times they are a changin'"...apk

    1. Re:Couple of things to say... apk by Anonymous Coward · · Score: 1, Insightful

      Man, if you have posted here 6 years, just please try to learn to type like a normal person. No one would be trolling you if you didn't post like this. Your text is really, really hard to read. It itself comes out as trollish. Replace the @'s with at and &'s with "and" and don't use so many unnecessary ". Your points might be good but no one bothers to read them like this.

    2. Re:Couple of things to say... apk by Anonymous Coward · · Score: 0

      "Man, if you have posted here 6 years, just please try to learn to type like a normal person. No one would be trolling you if you didn't post like this. Your text is really, really hard to read. It itself comes out as trollish. Replace the @'s with at and &'s with "and" and don't use so many unnecessary ". Your points might be good but no one bothers to read them like this." - by Anonymous Coward on Wednesday February 03, @11:07PM (#31018754)

      Man, if you have posted here 6 years, just please try to learn to STAY ON TOPIC like a normal person. No one would be trolling you if you didn't GO OFF TOPIC like this. Your OFF TOPIC B.S. is really, really OFF TOPIC and OPINION ONLY. It itself comes out as trollish. Replace the OFF TOPIC TROLLING with ON TOPIC MATERIAL and YOUR PERSONAL OPINIONS with NO PHD TO YOUR NAME TO SHOW YOU ARE SOME EXPERT IN ENGLISH OR WRITING and YOUR RUN-ON SENTENCES (Note the bolded part in what I quoted from you above? That's a run on sentence, bigtime. So, so much for your OTT TOPIC critique of others's writing, eh?). Your points are not good and no one bothers to read them like this BECAUSE THEY ARE OFF TOPIC.

  32. google should open all their code!! by frvfilmslashdot · · Score: 1

    help humanity get knowledge inovation

  33. Re:up merge justification has to be Android-agnost by Anonymous Coward · · Score: 0

    The reason of course is that there is no stable kernel API, and the developers are completely uninterested in maintaining one... And it's not necessary if all drivers are part of the mainline.

    And that is why developing anything near the Linux kernel sucks goats. The fact that you push your changes upstream doesn't mean they'll keep maintaining your code; old hardware drivers still get broken and ignored. For the most part things are kept compilable, but that doesn't mean anyone pays any attention to not introducing bugs for things they don't test. Until they remove your code anyway because they got bored with it.

  34. Um, if there's a problem with this, I don't see it by melted · · Score: 1

    Cell phones need a different kernel than servers, with different drivers, graphics and security requirements. Maybe this fork is justified? Maybe this doesn't need to be in the mainline?

  35. Actually... by symbolset · · Score: 1

    We've had no improvements in real productivity on the desktop in 15 years. It's long past time it was replaced with something else. Since we've tried WinTel, and that gave no progress, it's time we tried another path.

    If it turns out that these new platforms deliver the same productivity or better on 1% of the watts and 10% of the capital cost, they'll drive a revolution in IT that shifts influence from the people who have unlimited watts (the US) to more fairly share influence with people who are Watt and capital challenged (India, Pakistan and others). That's an advantage to the new markets actually, since they leverage the volume production of innovations they haven't paid for. And then there's the side-effect that power efficient computing reduces the need for hydrocarbon fuels and carbon emissions, which is a good thing even if you don't believe in AGW because if you use it up, then it's gone.

    The US can win this one by innovating, rather than milking the market they inherited. It's not that hard, and we have the experience advantage until we forfeit it.

    --
    Help stamp out iliturcy.
  36. Re:Android is open source so does it really matter by thetoadwarrior · · Score: 1

    Without a doubt it's no the best outcome and I would hope that eventually something changes for the better but freedom does give people the choice to do what they want even if Google didn't make the best decision.

    For that reason I would support their move. I think giving people the impression that open source only has freedom for those who think a certain way will stop businesses from taking on open source code because they'll be labeled as bad.

    It is wise to discuss it with Google and try to get the best outcome but if it doesn't happen then as long as they're not violating that particular licence, it's all fine imo.

  37. The simple solution by symbolset · · Score: 4, Interesting

    I'm hiding the easy answer here deep in the thread under your question.

    Google has Android slates (tablet format ARM-powered machines). If Google took 1000 of them ($400K worth) and just gave them to select Kernel developers (several each) to do with what they would, the problem would solve itself. The Kernel developers would adapt their preferred distro to work on the first slate they had, and they'd keep the rest to work as they were intended until it limited them - and then they'd want to break the limit by improving the Android code, which they would then want back in the Kernel tree because they would want their improvements to persist. It's all about motivation, and you motivate a Kernel geek with cool tech he wants to continue to use.

    HP did this. Why do you think Kernel.org runs on HP servers and has for many years? It's because HP donates servers strategically, and yields huge benefits therefrom.

    --
    Help stamp out iliturcy.
  38. Re:up merge justification has to be Android-agnost by kscguru · · Score: 2, Insightful

    And to a lot of people outside the Linux kernel development community, that "stable API nonsense" document is such a blindingly wrong example of software design that advocating it would get you shown the door in a job interview.

    The "nonsense" docuemnt assumes that the purpose of all drivers is to converge to a single less-buggy ideal; this is true for a hardware driver where the hardware is frozen when it goes out the door. This is blatantly untrue for software drivers (e.g. 3d graphics, virtualization) where the interface between the driver and other (non-kernel) software changes far more rapidly than the interface between the driver and the kernel (and especially for 3d graphics, where the driver contains an entire thread stack, JIT compiler, etc.).

    Good programmers will tell you that the driver belongs next to the component to which it is more tightly bound by a rapidly-changing API. Linux programmers will tell you the driver belongs in the Linux kernel so LKML can keep it up-to-date with changes to the mostly-unchanging kernel/driver API (and you can only make changes to the more-rapidly-changing driver/userlevel API during the merge window every three months). And to an extent Linux programmers are right - in an ideal world, the driver should be refactored until the driver/userlevel API is not so rapidly changing, at which point the driver should indeed live in the kernel. It's very easy for a Linux programmer to demand such ideal code as the cost of merging it into the kernel; it's much harder to take a "good enough" system and achieve such a high level of perfection, especially when merely achieving "good enough" is a target that moves fast enough to consume almost all of a programmer's time.

    The two camps will never see eye-to-eye; both are completely convinced that they are correct.

    --

    A witty [sig] proves nothing. --Voltaire

  39. So what you're saying is... by jonaskoelker · · Score: 1

    Yo mama's company so fat it's too big to fail?

  40. You forgot Palm by MobyTurbo · · Score: 1

    Somehow I managed to forget Nokia for being more open than Apple - and arguably - Google. I guess because so few people use, or will likely ever use, their smartphones. :)

    You also forgot Palm, who have WebOS, which is more "Linux like" than Android (No forking here!) Palm's WebOS is often thought of by Android fans as being so Apple-like that they immitated the closed source nature of Apple. Nothing is further from the truth.

    By the way, Nokia's market is limited to Europe (and the third world, but they don't buy smartphones in India, Africa, and the Far East), but there, they are the Blackberry of Europe with regards to smartphones. In other words, there are arguably more N and E series Nokia owners in Europe than any other smartphone. (Those *are* smartphones, albeit some of the older Symbian ones are more on the Palm Treo type of Smartphone technology than iPhone, very capable devices but very old-fashioned interface. Though it should be noted that they had a mobile WebKit browser before Apple did on the iPhone for Symbian's "Nokia browser"!)

  41. Re:up merge justification has to be Android-agnost by TheRaven64 · · Score: 1

    I think describing anything that Greg Kroah-Hartman says as 'reasoning' is stretching the definition of the term somewhat...

    --
    I am TheRaven on Soylent News
  42. Shipping an embedded Linux product by Anonymous Coward · · Score: 0

    When you're shipping an embedded Linux product you can only debate the relative goodness of an approach for so long. You're on product time, not community time. They shipped their product, people made phone calls, Linux got used in the process.

    Wakelocks are quick and dirty, so they were rejected, but they work for Google's embedded Linux product. The giant VM hack that separates user process space from kernel space was also quick and dirty, but it got in, and now the entire VM is affected by it. 4 KB page size assumption is also a giant problem now, but it got in. There are a million hacks in the Linux kernel, people just bring up Wakelocks because other people have explained them and said "these are bad." Well the emperor has no clothes. Read the code.

  43. Re:up merge justification has to be Android-agnost by Chousuke · · Score: 1, Informative

    I'm not sure what you mean by "rapidly changing driver/userlevel API". The kernel userspace backwards compatibility may not be broken, so it's quite stable compared to in-kernel interfaces.

    If you mean that the interfaces *need* to change, then perhaps those parts of the drivers should not be in the kernel (as is the case for 3d drivers)

    I'm not at all qualified to talk about virtualisation, but regarding 3d drivers, my understanding is that a significant portion of the stack actually lives in MESA, not the kernel.

    The kernel side's responsibility (assuming a "modern" one instead of the traditional "X does everything" kind of driver) is to handle details the kernel cares about such as initialisation, mode-setting, power and memory management, while providing a mostly static interface to the userspace component of the driver, which contains most of the messy 3d stuff.

    I think malleable in-kernel APIs allow your driver *not* to be perfect when you merge it. Perfection is required only for any user-space interfaces.

    Furthermore, if your driver suffers from bad design in some kernel subsystem, it is possible go and fix things. Or conversely, if some driver depends on an interface that you wrote, but you need to change it, that is also feasible.

    Now, one might argue that it's possible to preserve the old kernel APIs, but while that is possible, it greatly increases the maintenance burden. You will need to test code that only outdated drivers use. That's a waste of resources.

  44. Couple more things to say in response to a troll by Anonymous Coward · · Score: 0

    1.) Is there a 'writing style' forums on this website? Answer = No.

    2.) Are you on topic?? Again, no.

    3.) Do you have a PHD in English???

    If not, and I strongly doubt that you do???? Then, who are you to criticize anyone's writing style, period?????

    ----

    After all - Without that PHD to your name/credit, & in English, what exactly makes you the "expert" on how to write???? Answer = NOTHING.

    (Not that it'd matter even IF you had a PHD in English, as this is just a forums (with no section on 'writing style critique' no less), and writing "style" is pretty much moot because it's like resumes - one reviewer will love your resume, another will not (and you cannot please everyone))

    Thus, Your off topic b.s. is mere opinion & that's it...

    Now, I see you are the SAME "Anonymous Coward 'writing critique slinging troll'" that lurks around here... well, seeing as you started a sentence with a CONJUNCTION in the word "AND" here -> http://tech.slashdot.org/comments.pl?sid=1505462&cid=30729986 who screws up on writing himself no less?????

    LOL, who are you to tell others how to write then??????

    (You clearly cannot write correctly yourself, and you certainly cannot read!)

    Please - Do consider getting remedial reading courses & of course, "hooked on phonics" too on your end... because, after all, "READING IS FUNDAMENTAL"... lmao!

    APK

    P.S.=> Of course lastly, in regards to your "mod up"? Well, I see you used an alternate registered account to "mod yourself up" as well, hilarious... especially considering I have caught others here admitting to using alternate & multiple registered accounts here to do that very thing as well, per this evidence thereof -> http://slashdot.org/comments.pl?sid=1147437&cid=27056793 so it's no "big trick" to pull that little trick off either.

    So, as anyone can see? You are clearly off topic, & "busted" either way... not even a "nice try", because you don't possess the intellect to "get the better of me", period... apk

  45. Re:Um, if there's a problem with this, I don't see by Eunuchswear · · Score: 1

    Cell phones need a different kernel than servers, with different drivers, graphics and security requirements.

    Sez who? My phone runs a pretty much standard kernel. Nokia have worked with the Kernel developers getting it all in to mainline.

    This is great for me - if (when) Nokia abandon it some time in the future I (or "the community") can carry on supporting it forever.

    Which is the whole point about the GPL (see RMS vs the printer driver).

    --
    Watch this Heartland Institute video
  46. Re:Um, if there's a problem with this, I don't see by melted · · Score: 1

    Sez common sense.

    Android beats the crap out of whatever Nokia is capable of producing. And it's 100% open source, so you (or "the community") can just as well "carry on supporting it forever".

  47. Re:Um, if there's a problem with this, I don't see by Eunuchswear · · Score: 1

    Sez common sense.

    More details. What features of mainline Linux make it incompatible with portable phones?

    Android beats the crap out of whatever Nokia is capable of producing.

    How, exactly?

    --
    Watch this Heartland Institute video
  48. Re:Anonymous Coward by Anonymous Coward · · Score: 0

    You need a better Google translator:

    There's someone who understands what Anonymous Coward wrote? I do not understand.

  49. Re:up merge justification has to be Android-agnost by kscguru · · Score: 1

    If you mean that the interfaces *need* to change, then perhaps those parts of the drivers should not be in the kernel (as is the case for 3d drivers)

    That's the ideal. Now step out of the ivory tower and look around. Drivers that are simple enough to conform to that ideal are already in the tree (or will always be out of the tree because of reasons that have nothing to do with "stable API nonsense"); Greg K-H has a neat program to work with such drivers so long as enough documentation is present. Drivers that are too complex to easily evolve to that design are universally OUT of the tree - the complexity coming from the driver being cross-platform or having code maturity behind it that rivals the Linux kernel itself. (And, bluntly, Linux has never had to deal with a codebase comparably mature to Linux - Linux has never learned how). No one disagrees that the ivory-tower ideal is better; the disagreement is in whether the effort to achieve it is worthwhile (or even feasible).

    To make an analogy: the design improvements necessary to make a graphics / virtualization / smartphone codebase totally acceptable to LKML are (very roughly) equivalent in scope to the design improvements that would be necessary to make Linux *natively* run Windows drivers (ignoring the wisdom of doing so). This isn't obvious to LKML because most of the redesign would be in non-kernel code, but the scope of work really is that large. Google is not rejecting a better design simply out of spite; Google is rejecting the better design because the amount of effort to implement it is something that LKML would balk at doing to their own codebase.

    --

    A witty [sig] proves nothing. --Voltaire

  50. Re:Couple more things to say in response to a trol by Anonymous Coward · · Score: 0

    No, I did not use an alternate account to moderate myself up. People have been telling you this for ages. I do not hold PHD in English (we don't even have PHD's, and I don't even live in US but I still manage to write better English than you).

    And no, I'm not the other AC that commented about your writing style in the link.

    I know I'm not on topic, that's why I posted as anon. But it needs to be told to you somewhere somehow, since you post as AC and you don't have an email to contact you.

    I'm not forcing you to change your writing style, but I'm just telling you it's insanely hard to read and others here agree. It doesn't matter if I hold a PHD in English or not.

    You can ignore mine (and everyone else) advice, but this is the reason why you are trolled and ignored here. If we all wrote like this or everyone in our ways, this and every other discussion section and forum would be a total mess. This is why we have common writing etiquette - so we can understand each other.

    I'm not trying to "get the better of you", I'm just trying to tell you that no one here will take you seriously if you write like this. But you will probably just think I'm either a troll, off there to get you or some other AC that has told you the same thing, so maybe it's pointless.

    Laters.

  51. Re:up merge justification has to be Android-agnost by Chousuke · · Score: 1

    This isn't obvious to LKML because most of the redesign would be in non-kernel code, but the scope of work really is that large. Google is not rejecting a better design simply out of spite; Google is rejecting the better design because the amount of effort to implement it is something that LKML would balk at doing to their own codebase.

    Citation needed. Kernel people are not oblivious to userland needs. I can't say how much work it would be for Google to fix Android, but at least according to one LWN comment, Android could be made mainline-palatable without breaking userland interfaces: http://lwn.net/Articles/372631/

    Some drivers would need to be modified as well, of course, but I think it's better to do the work early than late when you realise you really should've listened to the mainline developers.

    Here's an interesting report from one of the realtime tree developers: http://lwn.net/Articles/372877/

  52. That's BSD by emj · · Score: 1

    it's not like Apple ever "borrowed" from the open source community without giving back is it?

    The BSD crowd shouldn't care about that, Apple can do almost what they want with the code. But for Linux not getting the drivers for 3D accelerators, SOC models or other kind of hardware, just because Google have to reinvent the wheel, is really sad.

    1. Re:That's BSD by ajs · · Score: 1

      The BSD crowd shouldn't care about that, Apple can do almost what they want with the code. But for Linux not getting the drivers for 3D accelerators, SOC models or other kind of hardware, just because Google have to reinvent the wheel, is really sad.

      You're confused.

      This isn't a licensing issue. Google has released the code. What's being said here is that it can't be mainlined because it a) hasn't been updated with fixes requested by the Linux mainline developers and b) it relies on userland components that will cause it to fail to build without them and needs to be stubbed out appropriately so that that isn't a concern. Both the former and latter could be resolved by anyone who wants to resolve them. There is no licensing angle here.

      Now, I should be clear. I believe that it's actually not Google but the Open Handset Alliance that controls Android, and that includes developers from Google and 64 other companies. So technically, this isn't something that Google alone could address.

  53. You're wrong again troll, see inside (bigtime)... by Anonymous Coward · · Score: 0

    "I do not hold PHD in English (we don't even have PHD's, and I don't even live in US but I still manage to write better English than you)." - by Anonymous Coward on Thursday February 04, @02:31PM (#31025686)

    Then you are nobody of authority or known expertise in English, period... and, as to your writing better English than I do? I do not begin my sentences with "AND" (a conjunction) as you did here "AC writing critic troll" -> http://tech.slashdot.org/comments.pl?sid=1505462&cid=30729986

    (That's a HUGE mistake in this language (English) on YOUR part)...

    So that evidence of your "expertise in English" aside?

    So much for this next statement of yours I quote next below:

    ----

    "but I still manage to write better English than you)." - by Anonymous Coward on Thursday February 04, @02:31PM (#31025686)

    Your opinion only, & since you have no PHD in English? Well... lol, to you. Especially after your screwup above, lmao...

    ----

    "I know I'm not on topic, that's why I posted as anon." - by Anonymous Coward on Thursday February 04, @02:31PM (#31025686)

    Well, well: The "AC writing critic troll" with no PHD in English answers the question I asked in my subject-line above. That makes YOU the candidate for a "mod down" for being nothing more than the low-life troll you are.

    (Gee, I guess now I "wonder" how you got "modded up" as "insightful" then? Your alternate registered accounts?? After all, it does happen here and I have caught "The End of Days" admitting to it here no less, per this evidence thereof -> http://slashdot.org/comments.pl?sid=1147437&cid=27056793 ...)

    Who do you think you are fooling, other than yourself?

    ----

    "No, I did not use an alternate account to moderate myself up" - by Anonymous Coward on Thursday February 04, @02:31PM (#31025686)

    Oh, yea: "Sure, sure" (sarcasm) - that doesn't go on here, right? See the last URL just above what I quoted from you.

    Once more - who do you think you are fooling, other than yourself??

    ----

    "People have been telling you this for ages." - by Anonymous Coward on Thursday February 04, @02:31PM (#31025686)

    No, only you have, actually!

    LOL, and you did before in this URL -> http://tech.slashdot.org/comments.pl?sid=1505462&cid=30729986

    (It is hilarious to see you 'critique my writing' & then only to see YOU fall FLAT ON YOUR FACE in the doing of it no less, and to have yourself screwup on English grammar, especially after trying to tell ME how to write (especially on a forums where it really doesn't matter, & you cannot please everyone, but most especially because you are off topic to the max and that this forums has no "English Grammar/English Writing Style Critique" section either)).

    You're nothing but a TROLL... and, we all know it.

    ----

    "And no, I'm not the other AC that commented about your writing style in the link." - by Anonymous Coward on Thursday February 04, @02:31PM (#31025686)

    "Sure, sure" (sarcasm again): Hmmm, looks that way to me! I see an AC in yourself once more trying to "tell me what good writing style is".

    ----

    But it needs to be told to you somewhere somehow, since you post as AC and you don't have an email to contact you.

    ----

    "I'm not forcing you to change your writing style" - by Anonymous Coward on Thursday February 04, @02:31PM (#31025686)

    On your BEST DAY, you couldn't force me to do a thing.

    ----

    "but I'm just telling you it's insanely hard

  54. Android is not Google's by DragonWriter · · Score: 1

    From TFS:

    [...] Google's Linux-based Android OS [...]

    Android, while Google popularized it (after purchasing Android, Inc.) and provides its own apps that are used on most Android phones, is the Open Handset Alliance's Linux-based OS now, not Google's.

  55. Oh, as to your writing better English than I do? by Anonymous Coward · · Score: 0

    "I do not hold PHD in English" - by Anonymous Coward on Thursday February 04, @02:31PM (#31025686)

    Dearest "AC writing critique slinging troll":

    The correct phrase above would be "I do not hold a PHD in English" (note the "a")?

    LMAO!

    APK

    P.S.=> You sure you want to keep telling ME how to write correctly, troll? You did a horrible job of that here too -> http://tech.slashdot.org/comments.pl?sid=1505462&cid=30729986 where you tried to tell me "how to write" and "what good writing style is" (inclusive of stating you were a professional writer no less too, lol (NOT)), and what did you do there?

    YOU DID THE SAME THING HERE, LOL, as you did there, only once more here, again:

    "And no, I'm not the other AC that commented about your writing style in the link." - by Anonymous Coward on Thursday February 04, @02:31PM (#31025686)

    CORRECT ENGLISH SENTENCES DO NOT BEGIN WITH A CONJUNCTION LIKE THE WORD "AND"... get it?

    ----

    "Novice writers should be especially careful not to begin sentence fragments with conjunctions." - http://www.cliffsnotes.com/WileyCDA/Section/Is-it-okay-to-begin-a-sentence-with-and-.id-305408,articleId-27216.html

    "Formal alternatives to 'and', include words such as 'furthermore', 'moreover' and 'additionally" - http://languagestyle.suite101.com/article.cfm/grammar_starting_a_sentence_with_or_and_or_but

    "The rule against starting sentences with and, but or because is a hypercorrection teachers insist on in elementary school so that kids don't stay in the habit of writing fragments" - http://www.english-test.net/forum/ftopic7888.html

    "I remember learning in grade school that this was absolutely out of the question" - http://www.english-test.net/forum/ftopic7888.html

    ----

    Want more, Mr. "Truly Anonymous Coward",

    ROTFLMAO! Ah... you're just "too, Too, TOO EASY" to get the better of in debate intellectually, and moreso based on your blatant lack of a mastery of proper written english (and, yet you have the NERVE to try to tell others like myself, college graduates (770 on my SAT in English by the by), how to write? Please, you're making my stomach hurt I am laughing so hard by this point)... apk

  56. Re:up merge justification has to be Android-agnost by kscguru · · Score: 1

    If you go off and read in more depth, one of the features of the Android waitlock is how waitlocks can be acquired or released by writing a waitlock name to a magic device (/proc/wait/lock and /proc/wait/unlock or something); this means userlevel can release a lock the kernel acquired, which is a feature Android uses but kernel developers reject as bad design. (And I happen to agree isn't ideal design, but taking a shortcut like that which only root can exploit does make a lot of sense.) Still think no userlevel code needs to be rewritten?

    Greg K-H may be technically right in that Android could use a different mechanism without changing the kernel-user ABI. But that's only because his definition of stable ABI/API only covers syscalls and conveniently ignores special device nodes (/proc, /sys, /dev) where power management interfaces live. The Linux kernel ABI/API is really 10x larger than he realizes; those special device node interfaces are quite wide.

    Linux kernel developers really are smart people, and their statements tend to be true - from a certain point of view. That point of view often has little to do with bringing in useful functionality and more to do with protecting that developer's personal interest - in Greg K-H's case, promoting the kernel as the one true repository of all code.

    --

    A witty [sig] proves nothing. --Voltaire

  57. Re:Oh, as to your writing better English than I do by Anonymous Coward · · Score: 0

    Like I said, English isn't my main language, and forgetting things like "a" is quite an easy thing to do because we do not have such in our language.

    However the point here is that your text is really hard to read. I do not need to hold any English master to say it.

    I'm not debating, fighting on the internet is retarted. I'm just stating the fact that countless of other people have told you too. I'm still not the same person you keep linking to, in fact I haven't even responded to you before. Do you see conspiracies against you everywhere all the time? You should probably do something about that.

  58. You started another sentence w/ AND, lol! by Anonymous Coward · · Score: 0

    "Like I said, English isn't my main language, and forgetting things like "a" is quite an easy thing to do because we do not have such in our language." - by Anonymous Coward on Friday February 05, @01:27PM (#31037222)

    NO, you actually said you write better English than I do, right here ->

    "but I still manage to write better English than you)." - by Anonymous Coward on Thursday February 04, @02:31PM (#31025686)

    No, you clearly do not, as you begin sentences with a conjunction which is a huge mistake grammatically no less...

    It is also QUITE FUNNY HOW YOU NOW ALSO SEEM TO UNDERSTAND EVERYTHING I WRITE AS WELL TOO ("funny that", eh? NOT!)

    And, you said you were NOT the "AC writing critique slinging troll" who bothered me before here on the EXACT SAME THING (telling me "what good writing style is" etc. et al) here -> http://tech.slashdot.org/comments.pl?sid=1505462&cid=30729986

    He's the same one who STARTED A SENTENCE WITH A CONJUCTION NO LESS - whom YOU said you were not HE. Funniest part is, you did the SAME MISTAKE HE DID, right here in this very exchange as well:

    "And no, I'm not the other AC that commented about your writing style in the link." - by Anonymous Coward on Thursday February 04, @02:31PM (#31025686)

    CORRECT ENGLISH SENTENCES DO NOT BEGIN WITH A CONJUNCTION LIKE THE WORD "AND"... get it?

    ----

    "Novice writers should be especially careful not to begin sentence fragments with conjunctions." - http://www.cliffsnotes.com/WileyCDA/Section/Is-it-okay-to-begin-a-sentence-with-and-.id-305408,articleId-27216.html

    "Formal alternatives to 'and', include words such as 'furthermore', 'moreover' and 'additionally" - http://languagestyle.suite101.com/article.cfm/grammar_starting_a_sentence_with_or_and_or_but

    "The rule against starting sentences with and, but or because is a hypercorrection teachers insist on in elementary school so that kids don't stay in the habit of writing fragments" - http://www.english-test.net/forum/ftopic7888.html

    "I remember learning in grade school that this was absolutely out of the question" - http://www.english-test.net/forum/ftopic7888.html

    ----

    Do you think I believe you at this point? Do you think ANYONE READING HERE BELIEVES YOU OR ANYTHING YOU SAY BY THIS POINT??

    (Once more: Who do you think you are fooling, other than yourself???)

    All in all, I must actually THANK you... why? For proving that your admittedly OFF TOPIC TROLLING has gotten the better of you, in your attempting to tell me "how t write" you only show how poorly your write this language yourself, and that's you're nobody to take seriously in your 'writing critiques' you sling here is all.

    APK

    P.S.=>

    "However the point here is that your text is really hard to read. I do not need to hold any English master to say it." - - by Anonymous Coward on Friday February 05, @01:27PM (#31037222)

    Again - it's rather "odd" (not) how you can read everything I write and respond to it well enough (grammatical mistakes & all on your part nonetheless), isn't it? Not. So... Here's a piece of advice, for you:

    LEARN TO READ THIS LANGUAGE THEN, AND BEFORE TELLING ANYONE HOW TO WRITE WELL IN IT - you don't do a good job of it anyhow, on writing it yourself, per the examples thereof above, and TRY TO STAY "ON TOPIC", please. I say that, because as you can see?? Your off topic trolling only ended up making you w

    1. Re:You started another sentence w/ AND, lol! by Anonymous Coward · · Score: 0

      Did you even read the link you pasted me?

      http://languagestyle.suite101.com/article.cfm/grammar_starting_a_sentence_with_or_and_or_but

      In the 1700s it was perfectly acceptable to start sentences with a conjunction. And it is becoming increasingly prevalent again now. But why use a conjunction to start a sentence? There are many advantages:
      It maintains an easy, conversational style.
      It preserves a link between sentences, whilst still delivering in a short, punchy vein. (Great for on-line writing).
      It reduces the need for long, wordy compound sentences.

      It is not grammatically incorrect to start a sentence with 'or', 'and' or 'but', and never has been

      My ability to still carefully go over your text and try to understand what you're trying to say doesn't make the text any easier to read. And like I suggested, you did actually stop using & and @ which alone makes your text a lot easier to read than in the initial post.

      Others have suggested me even here on slashdot if I make an obvious grammatical mistake or misspell some word, and I've learned from it. The point here isn't about knowing all the times you should use a/an/the or if you write flawless English with no typos. It is that the general style of writing is hard to read. It applies to every language, not just English. Misspellings or minor grammatical errors don't affect that as anyone can easily go over them.

      This is an old topic so I don't think many will even read this conversation, expect maybe with a small grin on their face.

  59. "Ebonics" is correct english too then, right? by Anonymous Coward · · Score: 0

    See my subject-line above, & realize that this:

    "In the 1700s it was perfectly acceptable to start sentences with a conjunction. And it is becoming increasingly prevalent again now" - by Anonymous Coward on Friday February 05, @05:13PM (#31040280)

    This is not the 1700's, and the literacy rates, ESPECIALLY TODAY? Not good, see here:

    Why is the literacy rate going down in the United States?

    http://www.literacynews.com/2010/01/why-is-the-literacy-rate-going-down-in-the-united-states/

    ----

    Perhaps because a foreign born person is at the wheel in academia now, like yourself, using incorrect grammar as you have?

    Bottom-line here, is this: CORRECT ENGLISH SENTENCES DO NOT BEGIN WITH A CONJUNCTION LIKE THE WORD "AND"... get it?

    (or doesn't the bulk of this information below tend to back me on that much??)

    ----

    "Novice writers should be especially careful not to begin sentence fragments with conjunctions." - http://www.cliffsnotes.com/WileyCDA/Section/Is-it-okay-to-begin-a-sentence-with-and-.id-305408,articleId-27216.html

    "Formal alternatives to 'and', include words such as 'furthermore', 'moreover' and 'additionally" - http://languagestyle.suite101.com/article.cfm/grammar_starting_a_sentence_with_or_and_or_but

    "The rule against starting sentences with and, but or because is a hypercorrection teachers insist on in elementary school so that kids don't stay in the habit of writing fragments" - http://www.english-test.net/forum/ftopic7888.html

    "I remember learning in grade school that this was absolutely out of the question" - http://www.english-test.net/forum/ftopic7888.html

    ----

    Yes, the majority of that does tend to back me, & I actually got a 770 on my SAT to get into college (which I graduated from no less, & working on yet another degree to my name now as we speak no less).

    Much more seems to gravitate my direction, and it illustrates that what you wrote is NOT CORRECT ENGLISH, period.

    APK

    P.S.=> So, what did you do here, and here earlier also in attempting to troll me (which you admit you are off topic on to begin with here no less)? Ok:

    http://tech.slashdot.org/comments.pl?sid=1505462&cid=30729986

    Yes, it's obvious that you're the same "AC 'writing critique' slinging troll" who STARTED A SENTENCE WITH A CONJUCTION NO LESS there in the URL above - whom YOU said you were not HE, & that's clearly b.s. period.

    Funniest part is, you did the SAME MISTAKE HE DID, right here in this very exchange as well:

    "And no, I'm not the other AC that commented about your writing style in the link."

    Please - don't attempt to tell others how to write, and don't try to tell us that "ebonics style english" is correct, when the bulk of the evidence I produce above states QUITE CLEARLY OTHERWISE.

    Especially when you don't write well yourself, per your mistakes above in starting sentences with a conjunction, using "And" on your part!

    (All that, & despite your stating you cannot read my posts? Well, you do an AWFUL GOOD JOB RESPONDING TO EACH POINT I MAKE, "isn't that odd" (sarcasm/NOT)... so who do you think you are kidding? Not I, or anyone else reading, you "AC writing critique slining troll", rotflmao)... apk

    1. Re:"Ebonics" is correct english too then, right? by Anonymous Coward · · Score: 0

      Yes, it's obvious that you're the same "AC 'writing critique' slinging troll" who STARTED A SENTENCE WITH A CONJUCTION NO LESS there in the URL above - whom YOU said you were not HE, & that's clearly b.s. period.

      That's because starting a sentence with an "and" is not grammatically incorrect . His writing style is even completely different than mine, and I don't even want to know what's going inside your head if you think everyone who tells you this is the same person.

      You also conveniently left off this part:

      But why use a conjunction to start a sentence? There are many advantages:
      It maintains an easy, conversational style.
      It preserves a link between sentences, whilst still delivering in a short, punchy vein. (Great for on-line writing).
      It reduces the need for long, wordy compound sentences.

      It is not grammatically incorrect to start a sentence with 'or', 'and' or 'but', and never has been

    2. Re:"Ebonics" is correct english too then, right? by Anonymous Coward · · Score: 0

      And I never said your posts were impossible to read, I just said it was hard and frustrating to read them because of the formatting and use of & , @ and unnecessary " . This is why I usually tend to jump past your posts, but wanted to point it out this time.

  60. 3:1 seems to prove you wrong easily enough... apk by Anonymous Coward · · Score: 0

    "That's because starting a sentence with an "and" is not grammatically incorrect " - by Anonymous Coward on Friday February 05, @06:45PM (#31041218)

    Oh, really? All of this tends to prove QUITE otherwise:

    ----

    "Novice writers should be especially careful not to begin sentence fragments with conjunctions." - http://www.cliffsnotes.com/WileyCDA/Section/Is-it-okay-to-begin-a-sentence-with-and-.id-305408,articleId-27216.html

    "The rule against starting sentences with and, but or because is a hypercorrection teachers insist on in elementary school so that kids don't stay in the habit of writing fragments" - http://www.english-test.net/forum/ftopic7888.html

    "I remember learning in grade school that this was absolutely out of the question" - http://www.english-test.net/forum/ftopic7888.html

    ----

    APK

    P.S.=>

    "You also conveniently left off this part:" - by Anonymous Coward on Friday February 05, @06:45PM (#31041218)

    Sure, kind of like how you left out the OVERWHELMING BODY OF EVIDENCE ABOVE I USED? Sure, because you made that very same mistake here 2 times now:

    ----

    http://tech.slashdot.org/comments.pl?sid=1505462&cid=30729986

    "And no, I don't have a PhD, but I do know spelling, grammar, and usage much better than you do, apparently." - by Anonymous Coward on Monday January 11, @08:42AM (#30722214)

    ----

    HILARIOUS - YOU DO NOT START SENTENCES WITH THE CONJUNCTION "AND" IN PROPER ENGLISH!

    (So, on that erroneous note of yours? Well - what did you do yet again later? Read on):

    ----

    http://linux.slashdot.org/comments.pl?sid=1535998&cid=31025686

    "And no, I'm not the other AC that commented about your writing style in the link." - by Anonymous Coward on Thursday February 04, @02:31PM (#31025686)

    ----

    Yea, ok (b.s.)... "Sure, sure" (sarcasm). You just made the exact same mistakes 2 times here as the "AC 'writing critique slinging troll'", and I am not supposed to think you are he? Beg to differ!

    (Who do you think you are fooling here, other than yourself?)

    All in YOU trying to tell others "how to write", & failing to do it correctly yourself (as you clearly do not write English well yourself per the examples above which are quotes of YOUR OWN WORDS no less. Additionally you possess no PHD in English either to your name establishing you as an expert in English either (while you are admittedly "off topic" the entire time here too, lol)...

    Give us a break! apk

  61. I wanted to point YOUR grammatical errors out too by Anonymous Coward · · Score: 0

    "And I never said your posts were impossible to read, I just said it was hard and frustrating to read them because of the formatting and use of & , @ and unnecessary" - by Anonymous Coward on Friday February 05, @07:06PM (#31041386)

    I have a simple solution for you then: Don't read my posts then (pretty simple). Nobody's "twisting your arm" to do so, after all!

    ----

    "This is why I usually tend to jump past your posts, but wanted to point it out this time." - by Anonymous Coward on Friday February 05, @07:06PM (#31041386)

    Per my subject-line above? Well, I have to point out YOUR blatant errors then, despite your arrogance in attempting to tell others "how to write" or "what good writing style is", when you cannot manage it yourself (per this evidence thereof):

    ----

    "Novice writers should be especially careful not to begin sentence fragments with conjunctions." - http://www.cliffsnotes.com/WileyCDA/Section/Is-it-okay-to-begin-a-sentence-with-and-.id-305408,articleId-27216.html

    "The rule against starting sentences with and, but or because is a hypercorrection teachers insist on in elementary school so that kids don't stay in the habit of writing fragments" - http://www.english-test.net/forum/ftopic7888.html

    "I remember learning in grade school that this was absolutely out of the question" - http://www.english-test.net/forum/ftopic7888.html

    ----

    That's what? 3 or 4:1 as a the ratio in favor of my pointing out to you that starting sentences with a conjunction is indeed, BAD ENGLISH... & yet you have the nerve to tell others how to write?? Please...

    APK

    P.S.=>

    "You also conveniently left off this part:" - by Anonymous Coward on Friday February 05, @06:45PM (#31041218)

    Sure, kind of like how you left out the OVERWHELMING BODY OF EVIDENCE ABOVE I USED? Sure, because you made that very same mistake here 2 times now:

    ----

    http://tech.slashdot.org/comments.pl?sid=1505462&cid=30729986

    "And no, I don't have a PhD, but I do know spelling, grammar, and usage much better than you do, apparently." - by Anonymous Coward on Monday January 11, @08:42AM (#30722214)

    ----

    HILARIOUS - YOU DO NOT START SENTENCES WITH THE CONJUNCTION "AND" IN PROPER ENGLISH!

    (So, on that erroneous note of yours? Well - what did you do yet again later? Read on):

    ----

    http://linux.slashdot.org/comments.pl?sid=1535998&cid=31025686

    "And no, I'm not the other AC that commented about your writing style in the link." - by Anonymous Coward on Thursday February 04, @02:31PM (#31025686)

    ----

    Yea, ok (b.s.)... "Sure, sure" (sarcasm). You just made the exact same mistakes 2 times here as the "AC 'writing critique slinging troll'", and I am not supposed to think you are he? Beg to differ!

    (Who do you think you are fooling here, other than yourself?)

    All in YOU trying to tell others "how to write", & failing to do it correctly yourself (as you clearly do not write English well yourself per the examples above which are quotes of YOUR OWN WORDS no less. Additionally you possess no PHD in English either to your name establishing you as an expert in English either (while you are admittedly "off topic" the entire time here too, lol)...

    Give us a break! apk

  62. Re:3:1 seems to prove you wrong easily enough... a by Anonymous Coward · · Score: 0

    "The rule against starting sentences with and, but or because is a hypercorrection teachers insist on in elementary school so that kids don't stay in the habit of writing fragments"

    You may be in elementary school, but I don't recall myself being.

    Like the above quote states, it is used in elementary school so that kids learn to write complete sentences and don't generate a habit of using conjunction in beginning of sentence. It doesn't mean there wouldn't be places where the correct use of it is appropriate.

    The other link (which you now conveniently removed from your "body of evidence") also states that it is perfectly appropriate to start a sentence with conjunction to link the sentences together and keep conversation style, especially on online forums or chat. And guess what, we are here discussing on slashdot comments on the internet. perfectly acceptable use of conjunction in a beginning of sentence.

    What makes you think I am him? Just because I commented about the formatting of your text and use of & and @ ? There are countless of people here on slashdot who think the same and you've seen it yourself too. And do not bring your list of modded up posts, I probably have countless more than you. It just tells that they might be informative posts, not that they wouldn't be hard to read!

  63. Re:3:1 seems to prove you wrong easily enough... a by Anonymous Coward · · Score: 0

    "You may be in elementary school, but I don't recall myself being." - by Anonymous Coward on Friday February 05, @07:31PM (#31041588)

    The CORRECT PHRASE FOR THE BOLDED PART ABOVE would be "but I don't recall myself being in elementary school"...

    You clearly have a problem with writing sentence FRAGMENTS... and your grammar has problems too (more evidences of that are below, quoted in YOUR OWN WORDS no less). Read on:

    Oh - By the by, I am not in elementary school. I have actually completed collegiate degrees and am further doing so again on yet more (2 courses away now/less than a full semester).

    Additionally, in order for myself to even get there in the first place, I scored an almost PERFECT "english section" of the SAT (at 770/800 mind you).

    So please - get over yourself already, as you have screwed up too many times here in English writing period!

    More evidences of those errors on your part?

    Ok, here goes:

    ----

    http://tech.slashdot.org/comments.pl?sid=1505462&cid=30729986

    "And no, I don't have a PhD, but I do know spelling, grammar, and usage much better than you do, apparently." - by Anonymous Coward on Monday January 11, @08:42AM (#30722214)

    ----

    HILARIOUS - YOU DO NOT START SENTENCES WITH THE CONJUNCTION "AND" IN PROPER ENGLISH!

    (So, on that erroneous note of yours? Well - what did you do yet again later? Read on):

    ----

    http://linux.slashdot.org/comments.pl?sid=1535998&cid=31025686

    "And no, I'm not the other AC that commented about your writing style in the link." - by Anonymous Coward on Thursday February 04, @02:31PM (#31025686)

    ----

    Yea, ok (b.s.)... "Sure, sure" (sarcasm). You just made the exact same mistakes 2 times here as the "AC 'writing critique slinging troll'", and I am not supposed to think you are he? Beg to differ!

    ----

    "I do not hold PHD in English" - by Anonymous Coward on Thursday February 04, @02:31PM (#31025686)

    Dearest "AC writing critique slinging troll":

    The correct phrase above would be "I do not hold a PHD in English" (note the "a")?

    LMAO!

    ----

    (Who do you think you are fooling here, other than yourself?)

    APK

    P.S.=> Learn these facts below, on PROPER ENGLISH (not "ebonics" english), & on how to write properly + especially before you go and try to tell others how to write well (especially a college grad like myself who also scored a 770 SAT verbal score (near perfect)):

    "Like the above quote states, it is used in elementary school so that kids learn to write complete sentences and don't generate a habit of using conjunction in beginning of sentence. It doesn't mean there wouldn't be places where the correct use of it is appropriate." - by Anonymous Coward on Friday February 05, @07:31PM (#31041588)

    Oh, really? These evidences clearly tend to state QUITE otherwise:

    ----

    "Novice writers should be especially careful not to begin sentence fragments with conjunctions." - http://www.cliffsnotes.com/WileyCDA/Section/Is-it-okay-to-begin-a-sentence-with-and-.id-305408,articleId-27216.html

    "The rule against starting sentences with and, but or because is a hypercorrection teachers insist on in elementary school so that kids don't stay in the habit of writing fragments" - http://www.english-test.net/forum/ftopic7888.html

    "I remember learning in grade school that this was absolutely out of the question" -

  64. Re:3:1 seems to prove you wrong easily enough... a by Anonymous Coward · · Score: 0

    "The rule against starting sentences with and, but or because is a hypercorrection teachers insist on in elementary school so that kids don't stay in the habit of writing fragments" - http://www.english-test.net/forum/ftopic7888.html [english-test.net]

    In addition to your writing skills, your eyes seem to need some fixing too.

    You go on and on pasting some other posts and avoid answering to the real questions, because apparently, it's some kind of competition to you and you feel like you are losing now.

    But why use a conjunction to start a sentence? There are many advantages:
    It maintains an easy, conversational style.
    It preserves a link between sentences, whilst still delivering in a short, punchy vein. (Great for on-line writing).
    It reduces the need for long, wordy compound sentences.

    It is not grammatically incorrect to start a sentence with 'or', 'and' or 'but', and never has been

    No, I don't need those three links again. It just shows that you cannot think yourself but feel the need to quote other people or that having a PhD and the relevant "knowledge" (told by other people) is the only way people can think and are justified to make their mind or opinions. And guess what, some people can think with their own brain too.

  65. You're making grammatical errors & losing by Anonymous Coward · · Score: 0

    "You go on and on pasting some other posts and avoid answering to the real questions" - by Anonymous Coward on Friday February 05, @08:10PM (#31041906)

    What "questions" are those? You have come here, trying to tell me "how to write" (not the first time for you, evidence of that much is clear below), & you also admitted you are off topic in doing so... that's in addition to your blatant grammatical errors evidenced below (via my quotes of YOUR OWN ERRORS no less).

    because apparently, it's some kind of competition to you and you feel like you are losing now." - by Anonymous Coward on Friday February 05, @08:10PM (#31041906)

    Competition is amongst equals, & you clearly are NOT mine (nor my superior in English based on your list of errors below). I think that anyone with any sense would read this and realize you have come here, off topic, trolling me on "how to write" and yet you make HUGE grammatical blunders here left & right? Please... "Gee, I wonder 'who is losing' here"? NOT I...

    ----

    More evidences of those grammatical errors in English, on your part (hilarious - all while you tried to tell ME "how to write")?

    Ok, here goes:

    ----

    http://tech.slashdot.org/comments.pl?sid=1505462&cid=30729986

    "And no, I don't have a PhD, but I do know spelling, grammar, and usage much better than you do, apparently." - by Anonymous Coward on Monday January 11, @08:42AM (#30722214)

    ----

    HILARIOUS - YOU DO NOT START SENTENCES WITH THE CONJUNCTION "AND" IN PROPER ENGLISH!

    (So, on that erroneous note of yours? Well - what did you do yet again later? Read on):

    ----

    http://linux.slashdot.org/comments.pl?sid=1535998&cid=31025686

    "And no, I'm not the other AC that commented about your writing style in the link." - by Anonymous Coward on Thursday February 04, @02:31PM (#31025686)

    ----

    Yea, ok (b.s.)... "Sure, sure" (sarcasm). You just made the exact same mistakes 2 times here as the "AC 'writing critique slinging troll'", and I am not supposed to think you are he? Beg to differ!

    ----

    "I do not hold PHD in English" - by Anonymous Coward on Thursday February 04, @02:31PM (#31025686)

    Dearest "AC writing critique slinging troll":

    The correct phrase above would be "I do not hold a PHD in English" (note the "a")?

    LMAO!

    ----

    "You may be in elementary school, but I don't recall myself being." - by Anonymous Coward on Friday February 05, @07:31PM (#31041588)

    The CORRECT PHRASE FOR THE BOLDED PART ABOVE would be "but I don't recall myself being in elementary school"...

    You clearly have a problem with writing sentence FRAGMENTS... and your grammar has problems too (more evidences of that are below, quoted in YOUR OWN WORDS no less).

    ----

    (Who do you think you are fooling here, other than yourself?)

    APK

    P.S.=> Learn these facts below, on PROPER ENGLISH (not "ebonics" english), & on how to write properly + especially before you go and try to tell others how to write well (especially a college grad like myself who also scored a 770 SAT verbal score (near perfect)):

    "Like the above quote states, it is used in elementary school so that kids learn to write complete sentences and don't generate a habit of using conjunction in beginning of sentence. It doesn't mean there wouldn't be places where the correct use of it is appropriate." - by Anonymous Coward on Friday February 05, @07:31PM (#31041588)

    Oh, really? These evidences clearly tend to state QUITE otherwise:

    ----

    "Novice writers should be especially careful not to

    1. Re:You're making grammatical errors & losing by Anonymous Coward · · Score: 0

      Again you paste irrelevant links and comment pieces we have read ton of times already.

      But why use a conjunction to start a sentence? There are many advantages:
      It maintains an easy, conversational style.
      It preserves a link between sentences, whilst still delivering in a short, punchy vein. (Great for on-line writing).
      It reduces the need for long, wordy compound sentences.

      It is not grammatically incorrect to start a sentence with 'or', 'and' or 'but', and never has been

      The use of conjunction to begin a sentence is all fine in some cases. Counter the above points, if you can (I doubt it; and don't just paste those 3 links again, think for yourself)

  66. Nothing irrelevant in YOUR grammar errors by Anonymous Coward · · Score: 0

    "Again you paste irrelevant links" - by Anonymous Coward on Friday February 05, @09:12PM (#31042406)

    These look pretty relevant here, & especially vs. your errors here quoted directly beneath them:

    ----

    http://linux.slashdot.org/comments.pl?sid=1535998&cid=31025686

    "And no, I'm not the other AC that commented about your writing style in the link." - by Anonymous Coward on Thursday February 04, @02:31PM (#31025686)

    ----

    HILARIOUS - Per what's in my 'P.S.' below? Well - IT IS INCORRECT/BAD GRAMMAR TO START SENTENCES WITH THE CONJUNCTION "AND" IN PROPER ENGLISH!

    So, get over it. You messed up, laughingly trying to tell me "how to write" and yet messing up hugely yourself on that very account!

    And, to what you said? Yea, ok (b.s.)... "Sure, sure" (sarcasm). You just made the exact same mistakes 2 times here as the "AC 'writing critique slinging troll'" -> http://tech.slashdot.org/comments.pl?sid=1505462&cid=30729986 , and I am not supposed to think you are he? Beg to differ!

    (Who do you think you are fooling here, other than yourself?)

    APK

    P.S.=> Learn these facts below, on PROPER ENGLISH (not "ebonics" english), & on how to write properly + especially before you go and try to tell others how to write well (especially a college grad like myself who also scored a 770 SAT verbal score (near perfect)):

    ----

    "Novice writers should be especially careful not to begin sentence fragments with conjunctions." - http://www.cliffsnotes.com/WileyCDA/Section/Is-it-okay-to-begin-a-sentence-with-and-.id-305408,articleId-27216.html

    "The rule against starting sentences with and, but or because is a hypercorrection teachers insist on in elementary school so that kids don't stay in the habit of writing fragments" - http://www.english-test.net/forum/ftopic7888.html

    "I remember learning in grade school that this was absolutely out of the question" - http://www.english-test.net/forum/ftopic7888.html

    ----

    apk