Slashdot Mirror


Linus on Subversion, GPL3, Microsoft and More

victor77 writes "Linus has repeatedly slammed Subversion and CVS, questioning their basic architecture. Subversion community has responded...how valid is Linus's statement?" This and many other subjects are covered in this interview with Linus.

350 comments

  1. Can't RTFA... by shish · · Score: 2, Interesting

    [Microsoft][ODBC SQL Server Driver][SQL Server]Transaction (Process ID 128) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction. Indeed :|

    Linus has repeatedly slammed Subversion and CVS, questioning their basic architecture. Did he slam it, or did he say that it's fine, just not appropriate for a project as distributed as the kernel?
    --
    I mod down anyone who says "I will be modded down for this", regardless of the rest of their comment
    1. Re:Can't RTFA... by dknj · · Score: 2, Funny

      It's designed for projects as distributed as the kernel. This is just another one of his inane ramblings.

      Who is this Linus character and what does he have to do with Linux?

    2. Re:Can't RTFA... by andreyvo · · Score: 1

      hosting anything about Linus, Linux and opensource considered "unholy" by microsoft software;)

    3. Re:Can't RTFA... by Nasarius · · Score: 3, Insightful

      Did he slam it, or did he say that it's fine, just not appropriate for a project as distributed as the kernel?
      The former. I was able to load the article, but can't get it back now. He said something like it's "good enough" for many people, but no one's really excited about SVN. To me, that's crap. SVN does what it does very well. What more could you really want from a centrally-managed versioning system?
      --
      LOAD "SIG",8,1
    4. Re:Can't RTFA... by FecesFlingingRhesus · · Score: 1


      No he basically said that it is rehashing old concepts like cvs, but that svn fixes some problems. what he calls "good enough" then he goes on to plug git as revolutionary. I am sorry but, the only thing new and revolutionary I have seen coming out of that space is Accurev.

    5. Re:Can't RTFA... by Oddscurity · · Score: 5, Informative

      He did slam CVS indeed, SVN likewise. In Linux talk at Google about Git[video] he mentions SVN and their credo at on time being something along the line of "CVS done right", commenting that "there is no way to do CVS right."

      The article linked here is light on details concerning SCM, though.

      --
      Indeed!
    6. Re:Can't RTFA... by Anonymous Coward · · Score: 0, Funny

      I think hes a porn star. Have you ever noticed how porn stars use a 'stage' name similar to a big hollywood star's name? I think hes one of those.

    7. Re:Can't RTFA... by Anonymous Coward · · Score: 1, Interesting

      Good thing you're careful to add that caveat centrally managed.
      Since as you must know that makes SVN totally different from the others like git, mercurial and bazaar.

      And if you want to get into things that CVS and Microsoft's crappy VSS can do but SVN can't - how about aliasing files and directories such that X trees share some common files that must be in sync yet managed? The very SVN model prohibits this without some messy client or server side scripting.

    8. Re:Can't RTFA... by nwbvt · · Score: 4, Informative
      Site seems to be back up, here is what he had to say:

      I suspect a lot of people really don't much like CVS, so I didn't really even expect anybody to argue that CVS was really anything but a legacy system. And while I've gotten a few people who argued that I shouldn't have been quite so impolite against SVN (and hey, that's fair -- I'm really not a very polite person!), I don't think anybody actually argued that SVN was 'good'.

      SVN is, I think, a classic case of 'good enough'. It's what people are used to, and it's 'good enough' to be used fairly widely, but it's good enough in exactly the sense DOS and Windows were 'good enough'. Not great technology, just very widely available, and it works well enough for people and looks familiar enough that people use it. But very few people are 'proud' of it, or excited about it.

      And here is the reaction from the subversion team. For those of you who don't want to RTFA, they basically say they agree, its not appropriate for something like Linux.

      BTW, isn't this all old news? His original comment on subversion was dated from 05

      --
      Mathematics is made of 50 percent formulas, 50 percent proofs, and 50 percent imagination.
    9. Re:Can't RTFA... by Anonymous Coward · · Score: 1, Funny

      Who is this Linus character and what does he have to do with Linux?

      Lucy van Pelt's younger brother. According to TFA, Linus was named after him because of the way some geeks cling to their favorite operating system similarly to the way Linus clings to his security blanket. Before that it was called Freeax.
    10. Re:Can't RTFA... by marcosdumay · · Score: 1

      "Did he slam it, or did he say that it's fine, just not appropriate for a project as distributed as the kernel?"

      I can't tell you what he said now. But he repeteadly said that CVS and Subversion didn't fit the Linux development model, not because it is big, or distributed, just because it is different. And it seems people keep asking him that same question :)

    11. Re:Can't RTFA... by Deorus · · Score: 1, Insightful

      > SVN does what it does very well. What more could you really want from a centrally-managed versioning system?

      Proper branching and tagging would help a lot.

    12. Re:Can't RTFA... by Anonymous Coward · · Score: 0

      but is a new interview, isn't it? (don't know for sure, ./ed)

    13. Re:Can't RTFA... by x_MeRLiN_x · · Score: 1

      If you have some time to kill, you could always watch his Google Tech Talk about Git - his alternative to CVS. He can't help himself from insulting CVS/SVN numerous times. If I remember correctly, he thinks SVN is "pointless".

    14. Re:Can't RTFA... by thePsychologist · · Score: 4, Interesting

      Yes this is extremely old news. I thought it would be something new, but then I see the comment from the SVN guys is dated 2006: last year for people who keep track of time.

      For instance, the comment from the Subversion team states that they hope the kernel dev team find some VCS that they like. They already did and it was git (http://git.or.cz/), a program that Linus Torvalds wrote himself.

      As a side comment, I like git over Subversion for a number of reasons. First it has data verification in the form of checking SHA1 (note that this isn't for repository protection from attacks but just for verification from corruption). It's distributed, and doesn't blow up the repository size when the repository gets large. SVN keeps a .svn metadata folder in each normal directory; hence if you have 1000 normal directories you get 2000 directories.

      Even if that's not much of an increase in space, it's ugly and it makes the repository (just files) hard to copy (have no idea why they implemented it this way). Of course there's a backup feature in the program so there's no reason to copy by hand, but still, it's inelegant.

      --
      "What lies behind us, and what lies before us are tiny matters compared to what lies within us." Ralph Waldo Emerson
    15. Re:Can't RTFA... by chthon · · Score: 2, Informative

      Too bad Continuus costs too much to try, I think he would want to return to SVN after using that piece of shit.

    16. Re:Can't RTFA... by coryking · · Score: 2, Informative

      easy

      - Not mess up my working directory with a bunch of .svn hidden directory junk.
      - As somebody else said, proper branching & tagging
      - Related to the .svn directory stuff, it is *way* to easy to ruin a working copy. Why related? You ever try to version a 3rd party tree (say, the ports tree)? It is virtually impossible because when you update the ports tree, it will mess with the filesystem enough to de-sync the .svn directory and ruin the entire working copy.
      - While getting better, it isn't very fast dealing with large working copies (say, 200+ megs)

    17. Re:Can't RTFA... by smenor · · Score: 5, Informative

      I used to use CVS (and still do for some projects). Then I switched over to SVN. It was remarkably unremarkable.

      Then, a few months ago, there was a /. article on git. It sounded interesting so I tried it... and was thoroughly impressed.

      I was up and running in about 20 minutes. You can use cvs/svn like commands, *but* you get local / decentralized repositories with fast forking and merging.

      Start a project. Type "git init" and you've got a repository in place (you don't have to initialize and then check it out). "git add ." and "git commit" and you've got your first revision.

      It took a little bit more effort to figure out how to push/pull from a remote repository, but it's fairly straightforward. A bunch of people can work in a group, have their own local repositories, and then merge their changes (along with the revision history). It's awesome.

      The only reason I haven't switched all of my projects over to it is that the IDEs I use (Xcode and Eclipse) don't have good git integration (as far as I know).

    18. Re:Can't RTFA... by Entrope · · Score: 1

      SVN keeps a .svn metadata folder in each normal directory; hence if you have 1000 normal directories you get 2000 directories.

      Not only that, for each file, Subversion keeps a copy of the last version you checked out of (or in to) the repository, so if you have 10 MB of source code, you end up with 20 MB used on disk. GIT's pack file support lets you keep the entire history of a project in space that is usually comparable to the size of the source code.

      In one of my projects that uses GIT, I have 7.5 MB of tracked source files, about 7.5 MB of compiled binaries and an 8.8 MB .git directory. That 8.8 MB fully describes every commit to every branch of the project for the last eight years. If I want to check out the first commit ever, I can do that. If I want to dig out a commit message from three years ago, no sweat. If I want to switch from one branch to another, it takes a second or two. Best of all, I can do all of those things entirely unplugged.

    19. Re:Can't RTFA... by Anonymous Coward · · Score: 0, Flamebait

      Linus is the creator of Linux, and before that, MS-DOS. You can see the similarities between the two with the blinking cursor.

    20. Re:Can't RTFA... by Anonymous Coward · · Score: 0

      Elaborate please...

      SVN's branching and tagging works PERFECTLY, and it is actually extremely nice because the fact that it is simply copying is a nice form of closure, a branch (or a tag for that matter) is no different from any other copy of an object in the repository. This is a basic principal of good software design. (I know, most of you monkeys out there THINK you know something about that, heh, I look at your system designs and code, I know better...).

      So instead of just saying it needs 'proper branching' you gotta tell us what exactly you think is missing.

      IMHO SVN clients could be improved in that they could use properties to keep track of merge points, or some other means to do that, but as long as you properly comment your branches and merges you will have no problem. And as long as you merge/branch from/to working copy and not directly in the repo you won't have any problems with messing up your repos.

      I've been using SVN exclusively since well before 1.0 on some LARGE and complex commercial code bases, and it has worked flawlessly.

      The inclusion of working copy meta data in the working copy file system is simply common sense. Where else would you WANT those .svn files (or equivalent info). Someplace ELSE in your file system? No thank you! I can tarball a wc and put it on any machine with an svn client and it makes no matter, back up up onto tape, restore them, etc and not have any problems. The last thing I want is my meta-data off in some other place.

      SVN is a highly pragmatic solution, and it works. I have no opinion as to what might be BETTER, but I know it works, it is widely supported, and it does what I want. THAT is what is important. It sure beats the **** out of CVS...

    21. Re:Can't RTFA... by coryking · · Score: 1

      I dont think people care about *how* branching is done, even if it is very elegant under the hood. It is just that without third party tools (svnmerge) subversion's technicaly-elegant branching system is rendered useless.

      If you think it is great, try merging "version" (really changeset is a better word) #4,15,67,93-102,105 and 106 from your development branch to your production branch. That is a very common use case that is very hard to do in subversion.

      Svnmerge + svn = good enough. Svn alone isn't very useful for a good hunk development process.

      Dont get me wrong, subversion is a very nice system. It has the best cross platform support out there, it doesn't treat directories like second class citizens, it is mostly stable, and it has tortise svn. But all said and done, Linus is right, subversion is merely good enough.

    22. Re:Can't RTFA... by krow · · Score: 1

      Hi!

      You certainly have a different experience of Continuus then what I have. My one experience with it involved one company were we had purchased it and then blown hours of consulting time getting it to work. Never happened. The few projects that tried to use it had constant problems with corruption. It was an awful tool, and not one I would recommend any one to use.

      --
      You can't grep a dead tree.
    23. Re:Can't RTFA... by thenerdgod · · Score: 2, Interesting

      What you're really asking for is filesystem-level versioning (splitting and merging)

      The problem is you can have "everything is a file" or you can have "inconspicous metadata".

      This implies a return to the structured-data days and an end to the 'Unix Philosophy'. And you kind of have that these days, with microsoft's offerings. And we all know how much you love the Registry.

    24. Re:Can't RTFA... by statusbar · · Score: 1

      One of the things that I hate about svn is that not only is everything in there duplicated, but svn can't easily revert everything in a tree, I need to rm -r -f X and then svn cleanup; svn update...

      jeffk

      --
      ipv6 is my vpn
    25. Re:Can't RTFA... by Nasarius · · Score: 1

      Define "proper". Subversion does handle tags and branches a little strangely, but once I figured it out, everything works fine. I branch, I tag, I merge changes to/from branches. A nicer interface would help, but that's where things like TortoiseSVN come in.

      --
      LOAD "SIG",8,1
    26. Re:Can't RTFA... by chthon · · Score: 1

      I think you misunderstood, it is Continuus that I refer to as a piece of shit. Unfortunately, I am already 7 years build manager in a Continuus environment. There are two main drawbacks, its slow, slow and slow, and to automate things one always has to work around their built-in features.

      I must say, we have been handling repositories of over 20 Gb with it. Anyone who has experience with SVN in environment with about 100 users and a repository of over 1 Gb ?

    27. Re:Can't RTFA... by coryking · · Score: 1

      "Unix Philosophy" should also mean "tiny programs working together" which is hard to do with SVN's metadata scheme. I cannot use "tiny other programs" that modify any SVN blessed working directory while keeping the metadata intact. For example, I cannot run FreeBSD's portsnap inside a working directory because portsnap will delete any depreciated port from my portstree. It is almost impossible to elegantly manage the portstree with SVN. And if you think my use case isn't worth considering, think about any other vendor tree you want to version and you'll have the same problem - it is very hard to sync with subversion.

      Even if putting the metadata outside the working copy bends the "unix philosophy" (svn also runs on windows too you know) who cares? Polluting the working copy with crap that has nothing to do with my source code really makes certian things like my example a in in the ass. In fact, besides that it might be easier to code and CVS did something like it, I cannot think of a single good reason to pollute my working copy.

      Why not keep the metadata in my homedir outside of the working directory? Just take the metadata and shove it in a place I specify in an environment variable. Perforce does this. I'm sure other systems do this. Why can't subversion?

    28. Re:Can't RTFA... by SnowZero · · Score: 2, Interesting

      It may be a slam, but its true. SVN had a very careful design that they put a lot of effort into -- unfortunately they chose the wrong model to start from, which severely limited what they could do compared to distributed version control systems.

    29. Re:Can't RTFA... by Westley · · Score: 1

      I regularly used to merge revisions in the way you suggested. (I now work with TFS, which is much nastier when it comes to merging. Blech.)

      I set up a small (two line) shell script so I wouldn't have to manually do the -rx:x+1 each time, but it was absolutely fine. In what way is it "very hard" to do with Subversion for you?

      Jon

    30. Re:Can't RTFA... by tobiasly · · Score: 1

      SVN does what it does very well. What more could you really want from a centrally-managed versioning system?

      Exactly. While distributed version control systems may be great for certain scenarios (such as the Linux kernel) there are many situations where it is overkill or even counter-productive. Most commercial systems will never go to a distributed model; it just doesn't make sense there.

    31. Re:Can't RTFA... by coryking · · Score: 2, Informative

      I set up a small (two line) shell script so I wouldn't have to manually do the -rx:x+1 each time You had me staring at that for a minute until I realized you weren't talking about file permissions (ala chmod) and instead talking about command line switches! :-) In truth, it isn't the command line stuff that is hard, it is just svn's merging is very conceptually hard to understand. Instead of the task-based "I want the changes from this version to merge with that version" using native svn forces you to think "I want to merge the difference between two versions in time into this other point in time". The "difference between two points in time" thing is really hard to wrap your head around...

      The trick is to get svnmerge. It handles almost all of the nitty gritty details so you can actually do what you realy want to do, which is "take the changes from branch A and put them into branch B". Say you want to take the junk in changeset 1,2,5 and all the junk between 30 and 35 and merge it into your working copy:

      > svnmerge merge -r 1,2,5,30-35

      First, it remembers where you want to pulls stuff in from - you set that when you initialize a branch by telling it "link the branch in this working copy to branch svn://somewhere/else/". Every time you run it, it looks at what hasn't been merge into your working copy. You can get a list of junk it hasn't merged with:

      > svnmerge avail

      Once you do the "svnmerge merge" it will pull in all the changes and automatically keep track of what it just merged it. You then do a regular commit on the changes and off you go. I usually do this:

      > svnmerge merge -r 4,5,6 -f commit.txt || svn commit -F commit.txt || rm commit.txt

      That command pulls in the revisions to your working copy and creates a commit log "commit.txt". It then commits your crap and removes the log.

      The whole thing is a hackjob for sure, for starters TortiseSVN doesn't know about it and I'd love to do the whole process in some GUI thing. But it does show you that SVN itself is more than capable of handling merges in a "proper" way. Subversion just needs to get this hi-level stuff into it's own codebase so it knows what is up. I know they are working on it, I just hope that I can migrate from svnmerge to whatever native stuff they cook up in an elegant fashion.
    32. Re:Can't RTFA... by haeger · · Score: 1

      How would "git" compare to something like DARCS?

      I tried DARCS once and while it had some great features it was probably a bit early in development to be used at the time. Things might be different now though.
      Has anyone tried both and could give some insights? .haeger

      --
      You are not entitled to your opinion. You are entitled to your informed opinion. -- Harlan Ellison
    33. Re:Can't RTFA... by iluvcapra · · Score: 1

      SVN keeps a .svn metadata folder in each normal directory; hence if you have 1000 normal directories you get 2000 directories.

      Many people have noticed this is a nasty problem when you're on OS X and are working with documents which are NeXT Bundles, a class that includes all applications and most productivity formats (excluding MSs). If I checkout a Numbers or Pages or RTF document with images from a repository, SVN will put it on my system with a .svn dir inside the document's bundle. If you open the document and then save it, the app will overwrite the whole of the previous document, which was in fact a directory, deleting the .svn directory inside, and having the effect of removing the document from revision control. Xcode uses bundles too, but Apple appears to have coded Xcode's saving behavior to allow the .svn directory to persist inside its project document bundle (though this is a one-off behavior; this doesn't happen if you use the standard file wrapper APIs to save a bundle.)

      Many OS X developers are looking seriously at git, since it's doesn't do this (we just need some better integration with XCode's UI).

      --
      Don't blame me, I voted for Baltar.
    34. Re:Can't RTFA... by coryking · · Score: 1

      And by the way, to anybody going "why the fuck would anybody want to piecementally pull in 1,4,7,34-56"...

      Once you start using svnmerge and are blessed with the ability to do piecemental commits you stop doing:

      > cd ; svn commit -R -m 'all my work today' *

      And you start going:

      1> cd ; svn commit -m 'fixed this bug' bug1.c bug1_2.c bug1_3.c
      2> svn commit -m 'added some feature' feature1.c feature2.c
      3> svn commit -m 'some other bug fix...' bug3.c

      now you've got three versions: 1,2,3. Guess what... you can push your changes to production by going:

      > cd ; svnmerge merge -r 1,3

      Congrads, you've just pushed out the two bug fixes you made without pushing out the new feature! Cool huh?

      That very simple example is very, very hard to do using only subversion.

    35. Re:Can't RTFA... by styrotech · · Score: 2, Interesting

      For those that don't know the functionality of svnmerge will be part of the upcoming subversion 1.5.

      I think most criticism of svn comes from thinking that ALL it ever intended doing was to reimplement CVS in a better way. That was kinda the 1.0 goal - things have been moving on since. The svn developers have been discussing ways of making it a bit more "distributed" or able to work better in a decentralised manner.

      And as you say, when subversion is "good enough" for someone the good cross platform support, wide support from 3rd party tools, friendly easy to understand interfaces for version control newbies and Windows users etc etc make it a good choice overall. It has successfully brought open source tools (often dragging Apache with it) into previously MS only development shops and displaced a lot of VSS installations. It has opened the eyes of a lot of Windows developers to the world of open source.

    36. Re:Can't RTFA... by Antique+Geekmeister · · Score: 1

      I have. It's awkward to handle large binary objects, because of one of the fundamental flaws of Subversion that the authors don't admit that it's a good idea to throw things out now and then. But if you throw out the idea of using the "move" function for anything bulky, and instead use the "import" function to create new tags, it becomes possible to actually prune branches that neverb wind up migrated back into the trunk.

    37. Re:Can't RTFA... by GPL+Apostate · · Score: 3, Funny

      The Blinking Cursor was patented by Lear-Siegler in 1973 and incorporated into their ADM-3A terminal. All derivative products using this IP are in infringement.

      --
      Microsoft says legacy (serial/parallel) ports are bad. They don't obfuscate the hardware enough.
    38. Re:Can't RTFA... by Anonymous Coward · · Score: 0

      As a Configuration Manager (I.e. an SVN admin) if you're merging multiple branches onto trunk in one go then your development process is broken and no amount of clever software is going to help you.

    39. Re:Can't RTFA... by Crayon+Kid · · Score: 2, Interesting

      Oh come on, you can't tell me you've moved from CVS to SVN and haven't felt a damn thing. It is bloody better. It doesn't feature distributed repositories, which is Linus' pet peeve, and probably some subtler stuff, but you can't honestly compare it to CVS and say it's "totally unremarkable".

      --
      i ate crayons when i was a kid and now i have two braincells and the blue ones taste nicer
    40. Re:Can't RTFA... by Westley · · Score: 1

      It's really *not* "very, very hard" to do using only Subversion. Yes, you need to get your head round "I want the changes from this location and this time copied over to this *other* location" but once you've done so, it's really not terribly hard to do exactly what you were saying.

      Reading the red book gives a good feeling of the whole "time+location" business - I don't see the problem. If you want to use svnmerge to make life easier for you, that's fine, good for you - but I really think you're overplaying how hard it is with just svn.

      Jon

    41. Re:Can't RTFA... by Daniel+Phillips · · Score: 1

      Did he slam it, or did he say that it's fine, just not appropriate for a project as distributed as the kernel? The former. I was able to load the article, but can't get it back now. He said something like it's "good enough" for many people, but no one's really excited about SVN. To me, that's crap. SVN does what it does very well. What more could you really want from a centrally-managed versioning system? How about a true versioned rename instead of emulation via delete+create? How about not being able to recover in any obvious way if you rm -r a subtree instead of svn rm it? Just two of the more painful issues that come to mind.

      Better than CVS, that about sums it up. I think that anybody still using CVS instead of SVN is crazy, but SVN still delivers less than I had expected. Maybe over time things could improve. Rewrite the whole back end, throw away the versioning filesystem idea and just keep the command set, that would work. The command set is not too bad (well... some oddities but not nearly as bad as cvs). SVN would still not be distributed in any meaningful way, but lots of people don't need that.

      Hmm. And make any local changes be a true branch, now that would be forward progress. Also unlikely to happen because of the huge pile of existing code that makes it hard to even contemplate a deep hack like that. But we shall see.
      --
      Have you got your LWN subscription yet?
    42. Re:Can't RTFA... by Deorus · · Score: 1

      > Define "proper". Subversion does handle tags and branches a little strangely, but once I figured it out, everything works fine.

      Proper tagging: a specific snapshot is marked with a name, only metadata is added to the repository.
      Improper tagging (SVN's hacked way): the whole repository is duplicated.

      Proper branching: a specific snapshot is marked as being the root of a branch, only metadata and changes made since the branch was created are added to the repository.
      Improper branching (SVN's hacked way): the whole repository is duplicated.

      I don't know about you, but the idea of having whole copies of the same repository in which only a few bytes differ is not appealing to me, and I would definitely not call that branching or tagging. I like the idea of being able to tag my projects as much as I want without having to worry about countless old snapshots cluttering up the repository, but that's just me.

    43. Re:Can't RTFA... by Westley · · Score: 1
      Let me just check this: you believe that branching in Subversion requires creating a physical copy of everything you're branching? In other words, that if you take a repository of, say, 10M within the trunk, and create a branch, that will take an extra 10M in the repository server?

      If that's what you believe, you're simply wrong. Here's a test I've just done:

      1) Check out piece of repository I'm branching - 11M (including the extra local copy made of every file, of course)
      2) Create a branch
      3) Look at the size of the revision created: 506 bytes

      So, where's the duplication you were talking about? Where are the "whole copies"?

      *Do* tag your projects as much as you want without having to worry about them cluttering up the repository, unless you count a few hundred bytes as significant clutter.

      From the documentation:

      This is why you'll often hear Subversion users talk about "cheap copies". It doesn't matter how large the directory is--it takes a very tiny, constant amount of time to make a copy of it. Enough evidence from me - do you have any evidence that Subversion behaves as you're claiming?

      Jon
    44. Re:Can't RTFA... by Deorus · · Score: 1

      > SVN's branching and tagging works PERFECTLY, and it is actually extremely nice because the fact that it is simply copying is a nice form of closure, a branch (or a tag for that matter) is no different from any other copy of an object in the repository. This is a basic principal of good software design. (I know, most of you monkeys out there THINK you know something about that, heh, I look at your system designs and code, I know better...).

      Copies are only useful when necessary. One of the goals of a version control system is to eliminate redundancy, and in this regard svn doesn't do well due to not supporting those features.

      > So instead of just saying it needs 'proper branching' you gotta tell us what exactly you think is missing.

      Actually I just did, but you could have gotten there without an explanation if you thought for a while.

      > IMHO SVN clients could be improved in that they could use properties to keep track of merge points, or some other means to do that, but as long as you properly comment your branches and merges you will have no problem. And as long as you merge/branch from/to working copy and not directly in the repo you won't have any problems with messing up your repos.

      What's lacking is the ability to associate release numbers with tags and branch points in the repository (because the client doesn't have to keep track of these things). Yes people came up with a hack, but the hack unnecessarily duplicating data.

      > I've been using SVN exclusively since well before 1.0 on some LARGE and complex commercial code bases, and it has worked flawlessly.

      I could say the same about CVS.

      > The inclusion of working copy meta data in the working copy file system is simply common sense. Where else would you WANT those .svn files (or equivalent info). Someplace ELSE in your file system? No thank you! I can tarball a wc and put it on any machine with an svn client and it makes no matter, back up up onto tape, restore them, etc and not have any problems. The last thing I want is my meta-data off in some other place.

      Don't think that's in response to any of my comments, so I'm skipping it.

      > SVN is a highly pragmatic solution, and it works. I have no opinion as to what might be BETTER, but I know it works, it is widely supported, and it does what I want. THAT is what is important. It sure beats the **** out of CVS...

      I can only assume that you have never used CVS, or if you have, it wasn't for long, because the advantages of SVN aren't that many. It can move/copy files and directories in the repository and keep the logs updated, it's faster, and it doesn't require as much access to the main repository as CVS does, but in the other hand it lacks support for branches, tags, and makes data a lot harder to access manually than CVS (which uses RCS files).

    45. Re:Can't RTFA... by Deorus · · Score: 1

      Ok, you proved me wrong.

    46. Re:Can't RTFA... by Deorus · · Score: 1

      Another poster proved me wrong about the duplication, but this doesn't make the grandparent right either, since he was defending it.

    47. Re:Can't RTFA... by thegrassyknowl · · Score: 1

      How very fitting - I was going to post the same comment!

      --
      I drink to make other people interesting!
    48. Re:Can't RTFA... by smenor · · Score: 2, Insightful

      Sorry but in my experience it was just marginally better (and in day-to-day use, from the end-users perspective, the only real difference I felt was that I was typing "svn commit" or "svn update" instead of "cvs commit" or "cvs update").

      I'm not saying there aren't cool things about SVN (like atomic commits and directories), but Subversion doesn't fundamentally change the way you work like Git.

      You say "it doesn't feature distributed repositories" like that's some sort of trivial throw-away nothing. It's not.

      With Git, every developer gets their own full-fledged repository (or more than one if they like). That means that every time they make a change, they can have the safety net of version control without breaking the codebase for everyone else or having to deal with annoying branching and merging.

      It's also trivial to create a local repository with Git. "git init" and you're running. Sure, you can do it with CVS or SVN, but you've got to create a special directory, check your stuff in and then check it out. It might not sound like much, but that extra little barrier was enough to keep me from even considering SVN/CVS for small throw-away projects that I wouldn't hesitate to keep under version control with Git.

      SVN is essentially what it claims to be - CVS done right. It's a better design and implementation, but using it still feels more or less like using CVS.

    49. Re:Can't RTFA... by coryking · · Score: 1

      I read that part in the book over and over (btw, SVN has great documentation) and I just get more confused. Once I did svnmerge, I never needed to learn :-)

    50. Re:Can't RTFA... by smenor · · Score: 2, Interesting

      I tried DARCS awhile back (like you, I was awestruck by the feature set - especially distributed version control and Haskell)

      It seemed dog slow even for a small repository, and was clunky to use (coming from CVS).

      Like I said - this was awhile back - so maybe they've fixed those issues, but following the tutorial, I was up and running with Git in no time and the commonly used commands are more or less identical to CVS/SVN (though it is a bit idiosyncratic in that it requires something like "git commit -a" where you would normally just use "cvs/svn commit").

    51. Re:Can't RTFA... by coryking · · Score: 1

      Huh? I never said I was merging multiple branches into a trunk. I was cherry-picking versions from the trunk and moving them into the release branch.

    52. Re:Can't RTFA... by coryking · · Score: 1

      someday slashdot will let me edit my comments...

      I wanted to add I'm not really slamming svn. I can't be the only one confused about branching in subversion and svnmerge fixes the confusion. It's a shame it isn't hyped more by the subversion guys - the only way I found it was that it was in the contrib directory of the source tarball.

    53. Re:Can't RTFA... by DECS · · Score: 0

      No Linus wrote Linux as a reimplementation of BSD, during the period that AT&T sued to stop the distribution of BSD. Had BSD not been held up in court, there would have been no need to rewrite BSD from scratch using inferior networking code.

      When Novell bought AT&T's Unix labs it ended the frivilous lawsuit against BSD, but by that time, Linux had gained so much marketing buzz that it overwhelmed both commercial Unix and the free BSD, serving to water down any hope for either of the candidates to prevent the expansion of Micorsoft's DOS and the promise of NT and Cairo.

      By the end of the 90s, Unix vendors had mainly squabbled amongst themselves, BSD had been largely overlooked, and Linux had expended millions of dollars in efforts to reinvent a perfectly good wheel. That allowed Microsoft to take over the desktop.

      Since 2000, the only commercial desktop BSD variant to matter is Mac OS X, while Linux has gone nowhere on the desktop and Microsoft has struggled to deliver upon any of its promises, having only gradually rewarmed NT over the last ~15 years.

      Mac OS X Leopard is now certified as Unix, making it the heir of both BSD and Unix, and primary real competition against Windows on the desktop. Linux exists as a BSD alternative with the entanglements of the GPL.

      MS-DOS was simply Microsoft's rebranding of a CP/M clone as its own technology, a regurgitation of the late 70s played back to haunt the 80s. NT is a similar effort to salvage VMS as a tool against Unix. It will be interesting to see who will continue to back Microsoft as it pretends Vista isn't just another embarrassing placeholder while it touts "Seven" as its real product, perpetually two years out.

      SCO, Linux, and Microsoft in the History of OS: 1990s
      SCO, Linux, and Microsoft in the History of OS: 1980s
      SCO, Linux, and Microsoft in the History of OS: 1970s

    54. Re:Can't RTFA... by grumbel · · Score: 1

      ### SVN does what it does very well. What more could you really want from a centrally-managed versioning system?

      Real diff and patch support (aka Changeset support). This is by far the biggest quirk I currently have with SVN and ironically its one that has basically nothing to do with the architecture itself and is more a case of "we couldn't agree on a perfect solution, so we didn't implement it at all".

      And before somebody jumps and mentioned 'svn diff', yes that is producing a diff, but a very incomplete one and it also helps you nothing with the non-existing 'svn patch' problem. The thing is, there simply is no way to produce a changset from all you have done to a svn repository (file moves, deletions, permission changes, binaries, etc.) and send that to somebody else to apply it, this makes in cooperating bigger changes from people not having repository access extremely annoying. Since it boils down to having to do it completly by hand.

    55. Re:Can't RTFA... by TemporalBeing · · Score: 3, Informative

      No Linus wrote Linux as a reimplementation of BSD, during the period that AT&T sued to stop the distribution of BSD. Had BSD not been held up in court, there would have been no need to rewrite BSD from scratch using inferior networking code.
      Actually, if you read Linus' own book - Just For Fun: The Story of an Accidental Revolutionary - you'd find out that he wrote Linux as (a) a method for learning x86 Assembly for the i386 processor, (b) as a way to get into his school account over dial-up, and (c) as a re-implementation of Minix. It was also highly coupled with Minix for a while until around version 0.10, or shortly thereafter.

      See also: 0.10 history, 0.02 & 0.03 history, 0.01 history
      --
      Truth is like the sun. You can shut it out for a time, but it ain't goin' away. - Elvis Presley (source: imdb.com)
    56. Re:Can't RTFA... by CryBaby · · Score: 2, Insightful

      It's also trivial to create a local repository with Git. "git init" and you're running. Sure, you can do it with CVS or SVN, but you've got to create a special directory, check your stuff in and then check it out. It might not sound like much, but that extra little barrier was enough to keep me from even considering SVN/CVS for small throw-away projects that I wouldn't hesitate to keep under version control with Git.
      On the contrary, until Git has better IDE plugins it's actually easier to use Subversion for "throw-away" projects. First, use a single repository with a top-level directory per project (separate repositories is overkill for all but the largest projects). Second, (this is with Eclipse/Subclipse) right-click on the project and select Team->Share. Done. I assume it's just as easy from other popular IDE's with decent Subversion support.
    57. Re:Can't RTFA... by SnowZero · · Score: 5, Interesting

      No Linus wrote Linux as a reimplementation of BSD Actually Linus started out rewriting Minix as a hobby, and it just so happened he chose the right license and was good an getting people to work with him. It amazes me that after all this time there are still people who don't understand why Linux succeeded... it was by building a better community, not technical superiority. BSD has had a great technical history, but quite a few community problems, leading to community splits and forks. Linus, as a good manager, has managed to hold Linux together, which is an achievement in itself. Of course, with open source "win" and "lose" isn't that meaningful; Linux and *BSD are healthy and continuing in their development. Who cares if your community is the biggest, if your community develops the software you need.

      during the period that AT&T sued to stop the distribution of BSD. Had BSD not been held up in court, there would have been no need to rewrite BSD from scratch using inferior networking code. So, with the SCO suit, BSD was able to make a comeback, right? Or, maybe you are overestimating the impact of the lawsuit. Also, if the BSDs could not stick together, what makes you think all the Linux people could work with them? Theo and Linus sharing the same CVS repository?... I doubt it.

      When Novell bought AT&T's Unix labs it ended the frivilous lawsuit against BSD, but by that time, Linux had gained so much marketing buzz that it overwhelmed both commercial Unix and the free BSD, serving to water down any hope for either of the candidates to prevent the expansion of Micorsoft's DOS and
      the promise of NT and Cairo. Except that the "frivolous" lawsuit actually did find offending code. The only thing that saved BSD is that AT&T/USL had stolen even more code. You can call the lawsuit stupid, annoying, or disrespectful, but there was an element of truth to it. The community should have policed itself a little bit better. To this day we still here software companies decrying open source's disrespect for copyright and properly policing the code; which IMNSHO is fallout from the original attitude taken when BSD was being developed. I like open source too, but the way to go about it isn't by ignoring the licenses for code, no matter how small or insignificant the amount. Hindsight is 20/20, but that was an important lesson.

      By the end of the 90s, Unix vendors had mainly squabbled amongst themselves, BSD had been largely overlooked, and Linux had expended millions of dollars in efforts to reinvent a perfectly good wheel. That allowed Microsoft to take over the desktop. This makes no sense to blame on Linux. The BSD license allowed commercial forks, so they happened, while BSD failed to market itself and grow its development community (instead it forked). Meanwhile Linux was doing its own thing, but was it "wrong" for not spending its funds on supporting BSD instead? If you look at all the money ever spent developing Linux, its probably less than what was spent on one of the major commercial Unixes. Why is this ok in the business world, but not in the open source world? Also, keep in mind a lot of recent investment in Linux is precisely because of the GPL; IBM would not support development of BSD code, as that might help its competitors closed-source products.

      Meanwhile, Microsoft successfully marketed a desktop, and took over a market many feel a free Unix could have occupied. Of course, in that case you should blame X-Windows and the slow development of broadly supported GUI toolkits. Both of those run on both Linux and BSD, so I don't see why this should be blamed on Linux. I guess Linus should have written a BSD-licensed version of KDE to make you happy?

      Once again, technical superiority is not the only thing that matters. It isn't true in business, and it isn't true in the open source world. Building a healthy community and a working development process is just as important for long term success. And, like in business, sometimes a little competition helps, as it spurs development that might not happen in a pure monopoly.
    58. Re:Can't RTFA... by Anonymous Coward · · Score: 0

      Ability to recover from a file delete without having lost the file history pre-delete, plz-thnx.
      Even CVS had that with the Attic.

    59. Re:Can't RTFA... by Bassman59 · · Score: 1

      > Define "proper". Subversion does handle tags and branches a little strangely, but once I figured it out, everything works fine.

      Proper tagging: a specific snapshot is marked with a name, only metadata is added to the repository.
      Improper tagging (SVN's hacked way): the whole repository is duplicated.

      That's not true -- the whole repository is NOT duplicated. When you create a tag, you make a "cheap" copy of the stuff tagged. (Unless, of course, you choose to make a tag of the entire repository, in which case you make a cheap copy of the whole repo. But why would you do that?) A "cheap" copy is smart and knows that it doesn't have to make a physical copy of the data, as the repo structure just stores diffs between revisions. The tag just points to the last revision.

      Proper branching: a specific snapshot is marked as being the root of a branch, only metadata and changes made since the branch was created are added to the repository.
      Improper branching (SVN's hacked way): the whole repository is duplicated.

      In Subversion, a branch and a tag are the same thing (cheap copies). By convention, tags are considered immutable.

      I don't know about you, but the idea of having whole copies of the same repository in which only a few bytes differ is not appealing to me, and I would definitely not call that branching or tagging. I like the idea of being able to tag my projects as much as I want without having to worry about countless old snapshots cluttering up the repository, but that's just me.

      I suppose if you knew more about how Subversion worked, you'd worry less.

    60. Re:Can't RTFA... by smenor · · Score: 1

      If you're using the command line, then what I said still stands, though I'll certainly concede that the biggest weakness of Git (and my single biggest complaint) is the current lack of support in IDEs (though it is my understanding that that will change relatively soon for Eclipse).

      That said, separate repositories only seem like overkill because you're used to CVS/SVN where creating separate repositories is expensive.

    61. Re:Can't RTFA... by Ohreally_factor · · Score: 3, Insightful

      Daniel, you're coming off like a fanboi. I love RD and all, but you're coming across like a Mactard trying to out piss Freetards.

      Besides which, you're missing an important part of the equation: commodity software.

      --
      It's not offtopic, dumbass. It's orthogonal.
    62. Re:Can't RTFA... by Ohreally_factor · · Score: 1

      I think at this point you're supposed to shake your fists and say something like, "Just you wait, Westley! I'll get you next time!"

      My personal favorite is "And I would have gotten away with it, if it weren't for Westley and that mangy dog of his! Curses!"

      --
      It's not offtopic, dumbass. It's orthogonal.
    63. Re:Can't RTFA... by Anonymous Coward · · Score: 0

      'svn revert -R .'

    64. Re:Can't RTFA... by Calinous · · Score: 1

      Linux started out developing on Minix. However, the owner of the Minix operating system (professor Andrew Tanenbaum) wanted to keep Minix small in order to keep it "didactic", the complete operating system for one of its courses. The Linus' additions would have make it too big and complex for that. As such, Linux started its own "minix variant". The restrictions prof. Tanenbaum was able to enforce on minix were probably the reason Linux set no restrictions on its variant (everybody do with it as he wants, at least in the 0. versions). These were later changed to GPL

    65. Re:Can't RTFA... by DrXym · · Score: 2, Interesting

      I'm sure git is wonderful in all sorts of change control related situations but Subversion is a great source control system too partly because it is so unremarkable - it just works. It has also got a great deal more cross-platform support and tools than git. Personally I use it as a distributed filing system because it has fantastic integration with Windows Explorer (via TortoiseSVN) so I can checkin files that I intend to share between machines (Linux & Windows).

    66. Re:Can't RTFA... by SnowZero · · Score: 3, Insightful

      Technical superiority did win in BSD's case.

      That's a pretty bold assumption not born out by the overall market, if you define winning the way you have been.

      While Linux is doing a lot in the server arena, it has accomplished very little on the desktop, despite efforts like OpenLinux and United Linux to create a standard Linux.

      I'd argue that distributions such as Mandrake, Ubuntu and PCLinuxOS have done a lot more for the desktop, but certainly none have taken the overall market by storm.

      The kernel may not have forked like Open/Net/FreeBSD, but there's really no difference between forked kernels and forked distros when it comes to fracturing the market.

      There's a difference between duplication of effort spent packaging existing software (distros) versus developing kernels and supporting libraries from scratch, with only partial code sharing through the heroic efforts of programmers spanning parts of the BSD family. As time goes on, this is not going to get any easier, while standards such as LSB has made packaging on Linux quite a bit simpler.

      There are really no commercial apps for Linux and there is no real market that will ever encourage their development.

      On the desktop there are few, but there certainly are a lot of specialized professional apps available for Linux. For everyday use, I'd question how much that matters. Sure gaming is not in a good state, but its not much better on a Mac; Consoles are even beating Windows FWIW.

      That leaves Apple's Mac OS as the only viable desktop, and its based on BSD, not Linux.

      So, without a commercial software market, a desktop is not viable? I guess you're not really much of an open source person. I must be really good to have been using an unviable desktop exclusively for the last 8 years as a my desktop OS. Or just maybe there's a difference between "viable" and "market leader". As an obvious Mac fanboy, you should know the difference. A 90% market share for Windows hasn't stopped OS-X from being viable, except perhaps for gaming, and (at the whim of Microsoft) office productivity.

      It does however share the same POSIX platform, meaning that there's really nothing of unique value in Linux that can't be ported to Mac OS X

      So if OS-X sharing Posix is good, how are multiple Linux distributions following LSB fractured and broken? You're not being very consistent.

      while there is lots of value associated with Mac OS X that will never make it to Linux: commercial apps, consumer focus, real marketing, retail support and the like.

      None of those have anything to do with BSD or the Mac kernel. Commercial apps in Linux are nearly comparible to Mac (but not Windows). Consumer focused distributions exist (just about anyone can use PCLinuxOS or Linspire). Real marketing, well if you consider that an OS technical feature, it's hard to compete with Apple; They are better at marketing than engineering. Retail support exists just fine if you need it; Several Linux vendors are happy to support their products if you buy them.

      Here's a value that will never come to Mac OS: Linux is Free. Obviously that doesn't matter to you, since you consider the GPL "an entaglement", and you don't even seem to care about open source (BSD) either, since most of the Mac OS advantages have nothing to do with anything that's open source.

      It's not that code associated with Linux isn't a great contribution to technology, it's that it simply won't matter on the desktop.

      It may not matter on your desktop, but it matters on mine (and works just fine). I use Linux at home, on my laptop, and at work. That's relevant enough for me. Unlike some, I do not value my OS software based solely on how many other people are using it (how unfashionable!). I would like to see Linux used widely, but I don't feel it has "failed" unles

    67. Re:Can't RTFA... by chthon · · Score: 1

      But that is to be expected isn't, it ? SVN was developed as a replacement for CVS, and it reached its goal.

    68. Re:Can't RTFA... by chthon · · Score: 1

      What's lacking is the ability to associate release numbers with tags and branch points in the repository (because the client doesn't have to keep track of these things). Yes people came up with a hack, but the hack unnecessarily duplicating data.

      Like I said in previous post, a closed-source tool like Continuus is much worse. To do a freeze/tag one has to checkout a complete project tree (project : something like svn:externals), and then freeze the checked out tree. With a hierarchy of about 200 projects, it takes between one and two hours.

      There are really worse things than SVN. The worst part being that Continuus is an expensive, closed-source tool with much more disadvantages than advantages.

    69. Re:Can't RTFA... by richlv · · Score: 1

      How about not being able to recover in any obvious way if you rm -r a subtree instead of svn rm it?

      i agree that local version control would ease some things considerably. but recovering ? what recovering ?

      not worked much with svn, i decided to try that out. after removing a directory, 'svn status' showed that directory prefixed with '!' - probably meaning that i was missing it.

      'svn up' nicely restored it, no complaints, no problems.

      or have i misunderstood the problem ?
      --
      Rich
    70. Re:Can't RTFA... by Keeper+Of+Keys · · Score: 1

      There are two main drawbacks, its slow, slow and slow, and to automate things one always has to work around their built-in features.
      That's four drawbacks...
    71. Re:Can't RTFA... by smenor · · Score: 1

      You're forgetting that SVN is about 7 years old and Git is closer to 2, and (by Linus' own words) has only been in a state where end-users would be able to use it comfortably for around 6 months.

      A Windows GUI and IDE support both take time. Once developed, you could use a Git version of TortoiseSVN exactly as you are now - with the additional benefit of being able to access your filing system on any of your machines even when you're not connected to a network.

      I think this is just an issue of Git being too new for you at the moment. Give it another 6 months to a year to mature and see if your objections still stand.

    72. Re:Can't RTFA... by tinkertim · · Score: 1

      The former. I was able to load the article, but can't get it back now. He said something like it's "good enough" for many people, but no one's really excited about SVN. To me, that's crap. SVN does what it does very well. What more could you really want from a centrally-managed versioning system?

      Not much at all really, I've had grumbles about SVN but fail to recall them, so I'm quite sure said grumbles were trivial at best. I think it had something to do with svn exiting with 0 when something went wrong, and my script didn't know there was an oops and kept going.

      For distributed stuff I like to use Mercurial because its very, very easy to use and more advanced things aren't so intimidating. Maybe take it for a spin if you want, you can get it here. I also use Mercurial to help manage /etc (really, really handy for that).

      I'm not so sure that there has to be an end-all-be-all of SCM's, why not just use whatever best fits the project and people working on it?
    73. Re:Can't RTFA... by TheRaven64 · · Score: 1

      Most Apple apps play nicely with Subversion to a degree now. I filed a bug about Keynote blowing away .svn directories, and they fixed it. The big problem is more insidious than this. Modifying a bundle can add new files within that bundle. These will not be automatically added to Subversion, and there is no 'automatically add files added in this directory' flag, so you can't fix it easily. This means that it's easy to commit a bundle, forget about it, and then discover that there are missing files when you check it out on a different machine, leaving you with a number of revisions which won't work due to missing files.

      --
      I am TheRaven on Soylent News
    74. Re:Can't RTFA... by smenor · · Score: 1

      If your goal is mediocrity and you achieve it, you've done what you set out to do.

      The GP's claim was that SVN was bloody better than CVS. You're saying SVN is a replacement for CVS so it's not surprising that using SVN is about the same as CVS. You can't have it both ways.

      Like SVN, Git can serve as a stand-in replacement for CVS.

      Just because it's distributed doesn't mean you have to use it that way. If you wanted to, you could set up a central repository and do a "git push" every time you commit and a "git pull" to update.

      But Git gives you so much more.

      You get a full-fledged repository on your local machine. That means you can make changes and do commits without having to worry about breaking the code in the main repository. That might not sound like much, but it has completely changed the way I work - not because it forced me into some new use pattern, but because it enabled me to do things I wouldn't even have considered before.

      Compare that with SVN where in day-to-day use, you're basically doing the same things you could have done in CVS. SVN certainly fixes things that were badly broken with CVS, but it stops there. Git lets you do everything you did before, but also lets you do things you couldn't (or shouldn't) with CVS or SVN.

    75. Re:Can't RTFA... by Abcd1234 · · Score: 1

      unfortunately they chose the wrong model to start from

      Because there's only one "right" model? WTF do you believe that distributed version control is the end-all and be-all for all situations? Did it ever occur to you that a centralized SCM might be more appropriate in some cases?

      For example, suppose you work in an organization using a distributed SCM and you want to cut a release. Where does the code come from? Sure, in an OSS project, you just release the main developer's tree (eg, Linus'), but in a traditional organization, where there is no one person controlling the product, where does that code get cut from?

      Honestly, you centralized SCM folks are as bad as hard-code OOP or functional programmers. You have this bizarre delusion that there's only one best solution for any given SCM problem, ignoring the myriad other possible use cases out there.

    76. Re:Can't RTFA... by cching · · Score: 1

      There are really worse things than SVN. Fortunately, there are also better systems than SVN as well ;-) Check out Monotone, Git, darcs and a few others.
    77. Re:Can't RTFA... by cching · · Score: 1

      I have to agree with you. After having switched away from CVS and SVN (to monotone), it sure is nice not having that garbage messing up my work space. Granted, you *can* deal with it, it's only a bit tedious, but since I've moved to monotone, it's *so* nice *not having to deal with it at all.*

      A small point to be sure, but every time I check out an OS SVN based project, I find myself cursing at this damn convention for one reason or another.

    78. Re:Can't RTFA... by DECS · · Score: 1

      It's easy to wage a war against someone else's comments, but I think you are arguing in circles and far beyond the point.

      I merely pointed out that the world already had a free version of Unix to build upon. You can criticize "technical superiority" and suggest that Linux has a better "community," but the reality is that businesses are wary to deal with the GPL. I called it an "entanglement," not because of my own personal ideology, but because the GPL is a problem for businesses; even those who attempt to work with the "community" are frequently attacked by it.

      Since you asked "with the SCO suit, BSD was able to make a comeback, right?, I pointed out that Linux hasn't made much progress and the uncertainty surrounding SCO really was as big of a problem for Linux as the uncertainty surrounding BSD. That's not my FUD, it's an observation that FUD was generated, and had negative results.

      But the real problem is when you personify Linux as a savior. It's not. It offers really nothing beyond the companies pushing it. If you have a bunch of random distros pushed by tech consultant groups, all you'll ever do is emulate the success of MSCEs pushing Windows for everything. That'll work on the server side, but only until Microsoft starts up its own patent wars. Linux is worthless without a real company standing up for it; without backers like IBM and Novell, the work of the "community" would go nowhere apart from hobbyist activities.

      You can giggle about Mac hardware market share, but the fact is that Apple is now making a third of the revenues and a quarter of the profits of Microsoft with its 3% share of the worldwide PC market. That's a lot of funding for Mac OS X. The only people using Linux on the desktop are companies trying to avoid paying for Windows: WalMart, hobbyists, and a few careful steps from the big Windows OEMs. They will never invest anything into Linux, and all the amazing work individual groups do will be ignored by the wider market.

      As long as consumers are expected to sort out their own window manager, desktop environment, and variant of Linux, there will never be cohesive progress on the desktop. Linux Enthusiasts can ignore the truth and call me a troll for pointing that out, but as long as you insist that the "community" is going to accomplish anything significant without real commercial backing... well, Linux is never going to make any progress on the desktop.

      Along the way, you dig up so many fallacies. Don't stuff words in my mouth about what 'I obviously believe.' Also, Mac OS X doesn't need to be released under the GPL to incorporate GPL software. Surely you are aware that it comes bundled with, among other things, GCC. Name a Linux application that can't run on Mac OS X because of the GPL.

      As far as taking Linux' reinvention of the wheel by writing another free Unix kernel from scratch when the technically superior BSD already existed, and equating that with Apple releasing new versions of NeXT software, well I think your ability to find similarities between events is suffering from logic flaws. Apple used code from various BSD projects and incorporated the latest GPL software, much like any Linux distro might.

      The difference is that Apple actually invested huge resources into its code base rather than just trying to make a quick buck off distributing the work of others. Efforts in the community to develop similar things (such as other advanced graphic compositing systems) haven't done much for actual Linux users, as nobody uses them. Code is only useful it if gets used. Apple has 25 million users that all use the same software, and its outgrowing the growth of the PC industry as a whole by a factor of 3. Linux isn't growing on the desktop at all, and its users--perhaps in the millions, but who knows--all use different versions X Window, KDE/GNOME, and various other fractionalized projects. That's no way to build anything, and certainly isn't going to displace Windows on the desktop.

      Don't jump down my throat for expressing facts based o

    79. Re:Can't RTFA... by cching · · Score: 1

      Caveat, we're in the middle of implementing DVCS using monotone, moving away from CVS.

      I guess if all your developers are in one location, you can get away with centralized revision control. But, even we, a small company, are finding the usefulness of a true DVCS to go beyond what we thought would be "nice to have." Our developers are spread across the US, UK, and Germany and CVCS is killing us. Certainly DVCS isn't for everyone, but for us it's working out very well. I highly doubt you're going to find that now and forever, commercial software vendors are always going to be happy with CVCS.

    80. Re:Can't RTFA... by chthon · · Score: 1

      That is true, but I also use trac, and trac has the best integration with SVN.

      I would like to use a more decentralised model, I tried SVK, which is based upon SVN. Unfortunately, SVK does not support externals.

      To change from SVN to another system, I need three things : I must be able to export my current SVN repository completely to the new system, it must support externals (for modular development), and it must integrate with trac.

    81. Re:Can't RTFA... by turpie · · Score: 1

      For example, suppose you work in an organization using a distributed SCM and you want to cut a release. Where does the code come from? Sure, in an OSS project, you just release the main developer's tree (eg, Linus'), but in a traditional organization, where there is no one person controlling the product, where does that code get cut from? You're still going to have a "Master" tree, it just happens that in Linux the master tree is Linus's.
    82. Re:Can't RTFA... by Abcd1234 · · Score: 1

      You're still going to have a "Master" tree, it just happens that in Linux the master tree is Linus's.

      Uhuh... and in an organization where there is no one person controlling the product, who does this? Or did you just ignore that question because you can't admit there is no good answer?

      Perhaps I should rephrase. In most organizations, there's a central repository of code that people check in to and out of, and occasionally releases are branched and cut from that central repository. So, in a decentralized model, how do you propose this be done? You aren't seriously suggesting that one person's tree become the "official tree", and that person is responsible for merging everyone's changes so a release can be done, are you? Need I go into the many many reasons why this is a remarkably dumb idea for a typical company?

    83. Re:Can't RTFA... by cching · · Score: 1

      To change from SVN to another system, I need three things : I must be able to export my current SVN repository completely to the new system, it must support externals (for modular development), and it must integrate with trac. Monotone does have support for converting from SVN (I think Tailor can do that too).

      Monotone can't do externals now, but there has been some talk about supporting multi-repo modules that would be very similar to SVN externals.

      Monotone does have Trac support, assuming it's still being maintained.
    84. Re:Can't RTFA... by WuphonsReach · · Score: 1

      Even if that's not much of an increase in space, it's ugly and it makes the repository (just files) hard to copy (have no idea why they implemented it this way). Of course there's a backup feature in the program so there's no reason to copy by hand, but still, it's inelegant.

      .svn folders aren't part of the repository, they're part of the working copy.

      SVN just chooses to store the metadata about the working copy in the working copy folders rather then putting it somewhere abstract (such as /var or /usr or /home or C:\Documents and Settings).

      One advantage of the .svn folders... you can use whichever SVN client you have laying around, and not worry that the tool won't be able to read the working copy. For example, in OS X, you can share a working copy between OS X and WinXP (using Parallels) instead of having to have two separate working copies. Another reason for the .svn folders is that they allow you to compare against the last pristine version that you have downloaded, without needing to talk to the server.

      (I have a love/hate relationship with .svn folders... some of my issues will be addressed in 1.5, some will be addressed in SVN 1.6).

      Backing up a SVN repository is as easy as using the svnhotcopy command. Or you can do a svndump. There are even scripts that back up the repository after every commit.

      SVN is a decent VCS, it's not perfect, it's not distributed, but it's got widespread platform support and works well for most uses. It's also being actively developed, which means things are getting fixed, getting better, and getting redesigned periodically. (It also has a good bit of mindshare - which helps get it onto other platforms.)

      --
      Wolde you bothe eate your cake, and have your cake?
    85. Re:Can't RTFA... by NuShrike · · Score: 1

      Sounds like the tool is not the question, but people being too freaking lazy to learn how to work with tags, branches and merges. I'm not reading anything about how Git really changes how you use VCS. Branching isn't annoying, it's a required skill for proper VCS usage which I've found lacking in many.

      Claiming Git is superior because you can substitute "local repositories" for proper tagging and branches is derivative, and isn't enough to convince me that it solves a real problem. I'v dealt with it in CVS every day for the last 7 years in corporate development, so I'm quite open to anything better, but the only improved developments have been atomic commits and changesets, which Perforce has it in spades, and not this local repository ability.

      I can respect separate repositories in that it solves the "open, shared access to one repository" issue, and makes it easier to have loosely coupled development groups working on the same codebase, but that still only delays the inevitable task of merging and working out conflicts at the end. I think it's still better to have little experimental branches that improve a small feature-set and then quickly merges back into trunk.

      What else does Git do that really simplifies and improves the VCS experience?

    86. Re:Can't RTFA... by smenor · · Score: 1

      Having local repositories doesn't replace branches and tags (you can still use them and every local repository is its own branch).

      Resolving the "open, shared access to one repository" issue is a huge deal.

      With a distributed version control system, you don't have to give every developer write access to the main repository. It's great that you and I know how to branch and tag, but there are plenty of people who don't, and with a centralized repository, your choices are to take the risk of someone breaking something that you'll have to go back fix, or forcing people to go through a guru every time they want to start a new branch.

      The biggest thing that Git has changed with how I use a VCS is that now I can commit with impunity.

      If I'm making a big change, I can commit broken code a few times in the process. Even with a private branch in a centralized system, I don't like to commit broken code. That means that before I was losing half of the benefit of version control - leaping without a net, so to speak.

      Sure... I could do that with my own branch in a centralized system (assuming I always have access to a fast and reliable network connection), but somehow I don't.

      Resolving conflicts in merges is a lot easier with Git as well (as is demonstrated with the Linux kernel developers). As you said - if you work with branches, merge issues are inevitable. In addition to having better merge tools, being distributed can actually help make it easier to resolve those conflicts.

      An added bonus is that if you're training someone, by the time you can get them up and running just doing commits and updates with SVN or Perforce, you can have them getting the benefits of branching with Git (on the command line, anyway; Git support is still lacking in most IDEs), and you don't have to worry about them breaking something in the trunk or (as I often see) making a ton of changes without committing.

      What I'd really like to see is a version control system that commits with every save; maybe something like Time Machine with branches, tags, merges, and comments; Git isn't quite there, but it's closer than SVN or Perforce.

  2. Linus would not be pleased... by Anonymous Coward · · Score: 1, Informative

    Microsoft OLE DB Provider for ODBC Drivers error '80004005'

    [Microsoft][ODBC SQL Server Driver][SQL Server]Transaction (Process ID 182) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction. /efytimes/lefthome.asp, line 193

    1. Re:Linus would not be pleased... by gvdkamp · · Score: 4, Funny

      Look at the script... lefthome.asp! Thats what i would do if I had my site running on Microshit stuff.

    2. Re:Linus would not be pleased... by Midnight+Thunder · · Score: 1

      Microsoft OLE DB Provider for ODBC Drivers error '80004005'

      [Microsoft][ODBC SQL Server Driver][SQL Server]Transaction (Process ID 182) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction. /efytimes/lefthome.asp, line 193


      Deadlocked on a read operation of all things!? Bad, very bad.

      --
      Jumpstart the tartan drive.
    3. Re:Linus would not be pleased... by dknj · · Score: 1

      iirc, sql server by default locks on read. this is a prime example of poor programmers/admins (not os or sql product, as others may have you believe)

    4. Re:Linus would not be pleased... by marcello_dl · · Score: 1

      I'm always admiring Microsoft-land, where accessing probably cached html pages requires acquiring a lock on db resources in a transaction. Oops shouldn't have dare spoken, it's probably a patented process.

      --
      ---- MISSING MISCELLANEOUS DATA SEGMENT --- [sigdash] trolololol
    5. Re:Linus would not be pleased... by Colin+Smith · · Score: 1

      not os or sql product, as others may have you believe Well... Oracle doesn't lock on read unless you tell it to...

      It blows it's rollback segments instead.

      --
      Deleted
    6. Re:Linus would not be pleased... by dknj · · Score: 4, Informative

      and if you're a programmer or an admin that knows sql server, then you know to disable this before you go into production. again, this is not a problem with the product. saying such would be like saying solaris is trash because it enables everything plus the kitchen sink, unless you tell it not to...

      oracle is all great and fun if you have the money to cough up for it. sql server has great performance at a fraction of oracle's cost. of course, a competent architect will know when to use sql server and when to use oracle.

    7. Re:Linus would not be pleased... by Anonymous Coward · · Score: 1, Insightful

      It's not a bug, it's a feature people.

      Microsoft software automatically detects when people are bashing them and gracefully shuts down.

    8. Re:Linus would not be pleased... by erroneus · · Score: 2, Interesting

      Wish I had some mod points but I believe you make a really good point.

      But to be sure, allow me to draw a parallel to help illustrate what I understood:

      It's not that Walmart is a crappy store... it's not and they generally have some pretty good stuff there. It's the people who shop at Walmart that gives Walmart its reputation.

      Is this pretty much what you're saying about Microsoft stuff? It's not that the products are bad--they're not. It's the people who use Microsoft products that give Microsoft its bad reputation.

      I think there is a lump of truth to this assertion. Microsoft is a lot more ubiquitous and available than many competing products. Certifications demonstrating expertise typically only require enough money and a list of answers to acquire.

      I think this is an assertion that requires some meditation: It's not the products, it's the users...

    9. Re:Linus would not be pleased... by mikiN · · Score: 1

      I beg to differ. Having sane default settings is very much part of the overall quality of a product. For very complex systems, it is insane to require an user to know the meaning and default setting of every parameter, even if the user is an expert.

      Do you know the default setting of every parameter used in the fuel injection system in your car? My guess is that not even the technician at the car repair shop does. He trusts them to be sane.
      Does the pilot of an airplane know the default setting of every parameter in the flight control system? Not even the pre-flight checklist covers them all. He just trusts them to be sane.

      --
      The Hacker's Guide To The Kernel: Don't panic()!
    10. Re:Linus would not be pleased... by Richard_at_work · · Score: 0, Offtopic

      Yup, just like the extremely high incidence rate of 'MySQL concurrent user count exceeded' errors that front page Slashdot articles seem to induce in other websites, especially for what should be nothing more than static pages! I wonder who owns the patent on those...

    11. Re:Linus would not be pleased... by thephotoman · · Score: 1

      You can run Active Server Pages on Linux, you know. I know that Sun makes an implementation, though it's not compatible with ASP.NET.

      --
      Haec merda tauri est. Ceterum censeo Carthaginem esse delendam.
    12. Re:Linus would not be pleased... by Anonymous Coward · · Score: 0

      No it doesn't, it hasn't since 6.5. And you'll note it's a generic ODBC error, it's not a Microsoft SQL database behind it.

    13. Re:Linus would not be pleased... by Anonymous Coward · · Score: 0

      You've obviously never use Oracle. It's a PITA, it's slow, it needs a massive box to even be remotely decent for heavy lifting. The dev tools are a joke, SQLPlus shell is pathetic. Oh, and it's nowhere near as robust as people claim (or pretend). We have to reboot regularly to give Oracle breathing space. You'd thing a 16 way, 32G RAM Sun monster would do the job? Nope.

    14. Re:Linus would not be pleased... by harlows_monkeys · · Score: 1

      Deadlocked on a read operation of all things!? Bad, very bad.

      A similar thing happens in MySQL. It's been a while since I had to deal with this, so I may be misremembering the details, but it was something like this. You get a read that takes a long time, and that causes a subsequent write to block. Now other reads block, waiting for that write.

      We saw this a lot in a helpdesk system we were using. There was a user table, that kept information on the support technicians. Many reports that involved large, slow queries involved that table. But when a technician would log in, there would be a write to that table, noting that the technician was available. That write would get stuck if one of those big reports was running. And since pretty much everything a support technician would do involved a join on the user table to check permissions, those would all hang. (Again, it's been a while, so I may have the details wrong...the gist is right, though: long read, blocks write, blocks other reads).

    15. Re:Linus would not be pleased... by iluvcapra · · Score: 1

      It isn't really a database thing, it's the web frameworks (of all stripes) and CMSs that don't provide a good caching mechanism for static content. And even on platforms that do provide it, like Ruby on Rails, the devs rarely take advantage of it, since you usually have to be explicit about using it.

      That said, a slashdotting will not stop at the DB layer, and will probably eventually jam the web server on most people's setups.

      --
      Don't blame me, I voted for Baltar.
    16. Re:Linus would not be pleased... by Alioth · · Score: 1

      Actually, a pilot of a plane DOES know all the default settings (at airline transport pilot level) and spends weeks of training learning about it, and is rigorously tested to ensure he knows it, too. Not 'can I regurgitate it' testing, but an oral test from hell where the examiner establishes not only that he knows the aircraft's systems inside out, but knows why the system is like that, understands it at a fundamental level, and the consequences of various subtle differences from normal.

    17. Re:Linus would not be pleased... by Jaime2 · · Score: 1

      You can't get a deadlock on a simple read operation by default in MS SQL Server. The only way to get a deadlock that involves a read is to have already written a record, and are now waiting to read a record that is locked by another user. Then, that other user has to try to read the record that you previously wrote.

      Since SQL has row level locking by default, this couldn't have happened from simply logging traffic as two users would never write the same log record.

      The site had to do something monumentally stupid to make MS SQL produce this error message on a website page view. If they performed the same monumental stupidity on Oracle, they'd get the same deadlock.

    18. Re:Linus would not be pleased... by thegrassyknowl · · Score: 1

      of course, a competent architect will know when to use sql server

      Never

      and when to use oracle.

      as long as you're not using SQL server

      --
      I drink to make other people interesting!
    19. Re:Linus would not be pleased... by Anonymous Coward · · Score: 0

      And the parade of the delusional marches on.

      Sorry to break it to you, but it's both. Microsoft's software is bad. It also tends to attract the paper-certification types who suck at what they do but only want quick $ and make the whole situation worse.

      But I digress. Wake up and get a clue. Microsoft's software sucks.

    20. Re:Linus would not be pleased... by dknj · · Score: 1

      I beg to differ. Having sane default settings is very much part of the overall quality of a product. For very complex systems, it is insane to require an user to know the meaning and default setting of every parameter, even if the user is an expert.

      I beg your pardon? If I am going to pay an engineer $100k/year, they damn well better be an expert at what they do. Again, let's revisit my correct analogy using solaris. Are you telling me an expert solaris admin should not be held responsible when he enables ECHO, DAYTIME, TELNET, RLOGIN, etc and leaves ipfilter wide the fuck open because it's the default and insane for him to know the default setting of COMMON parameters to the OS? If you are this so called "expert", I would not hire you. Hell, I would not even want to work with you. You are probably the type of person that leans on other experts for information.

      The fact that SQL server locks on reads can obviously lead to downtime on a heavily used server. If you are running a heavily used server, you probably need a competent sql server admin or programmer. If you have a competent sql server admin/programmer, they know that locks on read can cause major problems. 2 + 2 = 4, the admin/programmer should prevent it from happening. Then again, maybe some people don't care about uptime or they want to save a buck or two. You get what you pay for.

      Hint: don't argue things you are clueless about.

    21. Re:Linus would not be pleased... by dknj · · Score: 1

      i know you're joking. but this is for the up-and-coming teenagers out there that are looking to get into IT.

      while, microsoft is the devil and postgresql can probably satisfy their needs.. you sometimes are tied into products due to upper management (hint: you can always find a semi-competent microsoft admin and pay them around or below market. you can't always find a postgresql admin on demand). if you are not in a director position or directly below, you probably won't have the ability to persuade them. that being said, always know how to work with what you are given. if upper management says "use microsoft products", designing a project around oracle or mysql will get you fired. sql server costs (including operational costs) a fuckton less than oracle with comparable results. if a shop doesn't have a budget for oracle, sql server is usually next up to the plate. additionally, there are times when you don't want to use oracle and have a need for DB2.

      the younger you grip this mentality, the faster you will advance.

    22. Re:Linus would not be pleased... by Anonymous Coward · · Score: 0

      So you are equalling a situation where mssql goes into a deadlock because of stupid read-locks to a situation where mysql simply runs out of a resource? "Oh look - mysql can fail too!" Are you paid to post this crap?

    23. Re:Linus would not be pleased... by thegrassyknowl · · Score: 1

      the younger you grip this mentality, the faster you will advance.

      The younger you grip this mentality the sooner you will be assimilated. There is zero legitimite use for user MS products in the server market. There are dozens of alternatives that provide similar functions are similar or even less cost. Of all the alternatives all are more stable and more secure than the MS POS.

      It's been my experience that upper management says "microsoft has a product that does this" not because they like Microsoft, but because they're clueless n00bs and the only computer companies they know are Microsoft and Dell.

      The quickest way to advance is to be able to show your boss why MS is a bad choice and why any one of the dozens of alternatives better suits your needs. Telling them that you already know mysql is a good start. Justify it in terms of your cost/hour and number of weeks to learn the MS POS sufficiently to make it work in a sane and secure way. Then tell them after you've learned it and how to secure it you need more time to set it up and configure it. Explain that there are better solutions that you're already proficient with (if this really is the case). I find that at my salary level 1-2 weeks of my time more than offsets the difference in cost between some MS toy and a real piece of software if they really don't want free software.

      Of course, this means you have to know of software to fit a number of needs and be able to quickly dig up documented evidence showing that it performs at least as well as the MS crap (we all know that everything is better, but finding studies that aren't by clueless n00bs that actually prove it is the hard part).

      --
      I drink to make other people interesting!
    24. Re:Linus would not be pleased... by Anonymous Coward · · Score: 0

      Justify it in terms of your cost/hour and number of weeks to learn the MS POS sufficiently to make it work in a sane and secure way. Then tell them after you've learned it and how to secure it you need more time to set it up and configure it.

      I'm not dknj, but I can't leave that statement alone in this context. Perhaps you didn't intend to state it this way, but it essentially boils down to "I don't know X, but I do know Y; it will cost you more to have me learn X and do X than it will cost to have me do the Y I already know." For those who are not self-employed, in my experience telling your boss this is very likely to motivate him to find someone who has the skill set to do what was asked, quite often at your detriment and without regard for the technical merits of one solution over another. For the self-employed contractor, you might get to do what you recommend, or you might find yourself looking for another contract - YMMV.

      - T

  3. GPL Comment by woodchip · · Score: 2, Funny

    I hereby release this comment under a GPL. You are free to use this comment or modify this comment in away you feel fit. But if you distribute this comment or any modifications of it, you need to also publish all the embarrassing things you have said said drunk.

    1. Re:GPL Comment by Anonymous Coward · · Score: 0

      The GPL doesn't allow any additional restrictions.

    2. Re:GPL Comment by Anonymous Coward · · Score: 0

      I hereby release this comment under a GPL.h

      You are free to use this comment or modify this comment in away you feel fit. But if you distribute this comment or any modifications of it, you need to also retain the release statement (first paragraph of the comment).

      (I never was drunk, wine is part of my place's culture so getting drunk is not a transgression. Pity for our youngsters which are becoming idiotic drinkers of shitty stuff like everywhere else.

      There, settled.)

    3. Re:GPL Comment by Anonymous Coward · · Score: 1, Interesting

      He said a GPL. The GNU GPL doesn't allow any additional restrictions, and lazy people commonly use the phrase "the GPL" to refer to the GNU GPL (like they say "wiki" when they mean Wikipedia), but that isn't what he said, so it's reasonable to assume he had a different GPL in mind, namely the one whose simple licensing terms he went on to spell out.

    4. Re:GPL Comment by Slashcrap · · Score: 1

      I hereby release this comment under a GPL. You are free to use this comment or modify this comment in away you feel fit. But if you distribute this comment or any modifications of it, you need to also publish all the embarrassing things you have said said drunk.

      Comment (#20285279) Version 0.102(alpha) :

      Woodchip likes to dress up in women's clothes and spends approximately 90% of his waking hours searching for furry porn on other people's DeviantArt pages.

      Hope you like the new version!

      PS. I don't drink.

  4. Article by Anonymous Coward · · Score: 3, Informative

    Sunday, August 19, 2007: Did Microsoft's Men In Black ever met Linus Torvalds? But why is he so critical of GPLv3? Why does he slam Subversion? What would happen to the kernel development if he chooses to do something else more important? These are some of the questions Linux/open source community from around the globe wanted to ask Linus. And, here is Linus candid and blunt, and at times diplomatic. Check if the question you wanted to ask to the father of Linux is here and what does he have to say...
    Q: What are the future enhancements/paths/plans for the Linux kernel? --Subramani R

    Linus: I've never been much of a visionary -- instead of looking at huge plans for the future, I tend to have a rather short timeframe of 'issues in the next few months'. I'm a big believer in that the 'details' matter, and if you take care of the details, the big issues will end up sorting themselves out on their own.

    So I really don't have any great vision for what the kernel will look like in five years -- just a very general plan to make sure that we keep our eye on the ball. In fact, when it comes to me personally, one of the things I worry about the most isn't even the technical issues, but making sure that the 'process' works, and that people can work well with each other.

    Q: How do you see the relationship of Linux and Solaris evolving in the future? How will it benefit the users?

    Linus: I don't actually see a whole lot of overlap, except that I think Solaris will start using more of the Linux user space tools (which I obviously don't personally have a lot to do with -- I really only do the kernel). The Linux desktop is just so much better than what traditional Solaris has, and I expect Solaris to move more and more towards a more Linux-like model there.

    On the pure kernel side, the licensing differences mean that there's not much cooperation, but it will be very interesting to see if that will change. Sun has been making noises about licensing Solaris under the GPL (either v2 or v3), and if the licence differences go away, that could result in some interesting technology. But I'm taking a wait-and-see attitude to that.

    Q: Now that the GPLv3 has been finalised and released, do you foresee any circumstance that would encourage you to begin moving the kernel to it? Or, from your perspective, is it so bad that you would never consider it? -- Peter Smith / Naveen Mudunuru.

    Linus: I think it is much improved over the early drafts, and I don't think it's a horrible licence. I just don't think it's the same kind of 'great' licence that the GPLv2 is.

    So in the absence of the GPLv2, I could see myself using the GPLv3. But since I have a better choice, why should I?

    That said, I try to always be pragmatic, and the fact that I think the GPLv3 is not as good a licence as the GPLv2 is not a 'black and white' question. It's a balancing act. And if there are other advantages to the GPLv3, maybe those other advantages would be big enough to tilt the balance in favour of the GPLv3.

    Quite frankly, I don't really see any, but if Solaris really is to be released under the GPLv3, maybe the advantage of avoiding unnecessary non-compatible licence issues could be enough of an advantage that it might be worth trying to re-license the Linux kernel under the GPLv3 too.

    Don't get me wrong -- I think it's unlikely. But I do want to make it clear that I'm not a licence bigot, per se. I think the GPLv2 is clearly the better licence, but licences aren't everything.

    After all, I use a lot of programs that are under other licences. I might not put a project I start myself under the BSD (or the X11-MIT) licence, but I think it's a great licence, and for other projects it may well be the right one.

    Q: Currently are there any Indians who you'd like to highlight as key contributors to the Linux kernel?

    Linus: I have to admit that I don't directly work with anybody that I actually realize as being from India. That said, I should clarify a bit: I've very consciously tried

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

      you all should not forget that Linus brought us Linux(TM) and therefore can do no wrong and is exempt from criticism.

    2. Re:Article by LurkerXXX · · Score: 0, Troll

      Yeah, Linux is right. Git is great and CVS and Subversion are crap. That's why everyone has migrated away from CVS and Subversion to Git, the fantastic new tool he wrote. Oh wait. They haven't? Wonder why.

    3. Re:Article by jellomizer · · Score: 2, Insightful

      Well Not everyone is writing and OS Kernel. Different projects need different Code Management Systems. Git works for him, so he likes it. Other people use other stuff. By Your logic you are saying Microsoft Sourcesafe 6 is the best Tool out there because more people use it. CVS is widely used because it is part it have been historically part of most linux distributions.

      --
      If something is so important that you feel the need to post it on the internet... It probably isn't that important.
    4. Re:Article by LurkerXXX · · Score: 1

      I'm well aware why CVS is widely used. There was also a large migration from CVS to Subversion because of the few thing Subversion does better. Sure lots of folks are still using CVS, some because of a few issues with Subversion that would be harder for them, others because they are just used to using CVS and don't want to learn anything new, and other just aren't motivated to move their codebase. Never the less, there was a quite noticeable sized migration to Subversion for a few nicer features. Have you noticed any such to Git of other than Linux kernel developers? Shouldn't there have been one if it's markedly better than either CVS or Subversion?

      Certainly some development projects have different requirements than others, but he doesn't couch his criticism in that frame. He says subversion is only 'good enough', while Git is great because it's real UNIX and has an idea behind it. That's not saying it's better for this type of project. It's just saying this is better.

      It *may* work better for his type of project, but he likes it because he wrote it.

    5. Re:Article by fimbulvetr · · Score: 2, Informative

      Mod parent down, he has altered the article to include things like "What do you think of penis?"

    6. Re:Article by Anonymous Coward · · Score: 0

      And he wrote it because nothing else would allow the large scale development the kernel requires was available after the BK debacle. Care to name a single high change volume project with 1000+ remote developers using CVS or SVN?

    7. Re:Article by Anonymous Coward · · Score: 1, Interesting

      FreeBSD, the whole OS, not just a kernel, is done on CVS.

    8. Re:Article by DaleGlass · · Score: 5, Interesting

      Subversion works, but like Linus says, it's nothing wonderful. You can hardly point at some feature of it and say it was the product of a genius. It does CVS right, and that's about it.

      But SVN is limiting. For example I have a fork of the Second Life source, and SVN was PAIN for that. I ended up switching to SVK because it was the first thing I found that could sync with a SVN repository (which is what LL hosts), but Git would probably be also a fine choice as well.

      SVN's problem is that when you want to branch somebody's source but still follow it by merging improvements it becomes really painful. You have to use svn-load-dirs, which is a hack. You have to give it megabytes of source to process, which can suck really badly when you've got your SNV repository hosted externally so that other people can access it.

    9. Re:Article by russotto · · Score: 1

      Yeah, Linux is right. Git is great and CVS and Subversion are crap. That's why everyone has migrated away from CVS and Subversion to Git, the fantastic new tool he wrote. Oh wait. They haven't? Wonder why.


      They actually have, but haven't figured out how to use git to commit the change yet.
    10. Re:Article by Anonymous Coward · · Score: 0

      Judging by some of the comments from some large projects (Mozilla, the Perl core team) Because it's not cross platform enough yet.

    11. Re:Article by superwiz · · Score: 1

      Well, he actually said why. If, of course, you RTFA. Because CVS and SVN are comfortable and familiar. He actually said that he wouldn't migrate a huge project to Git himself (not at first) because it's more important to make sure people have tools available to them that they are comfortable with. By your rational, people shouldn't migrate from Windows to Linux because most people haven't.

      --
      Any guest worker system is indistinguishable from indentured servitude.
    12. Re:Article by Dogtanian · · Score: 0

      Mod parent down, he has altered the article to include things like "What do you think of penis?" Some of us want to know what Linus thinks of penis, you insensitive clod!
      --
      "Slashdot - News and Chat Sites Deviant". (Click "homepage" link above for details).
    13. Re:Article by smenor · · Score: 1

      Shouldn't there have been one if it's markedly better than either CVS or Subversion?

      I'd assume it's just that most people don't know about Git.

      It just needs a new PR guy and a little bit of time.

      The only reason I've ever heard about it is that I saw some random article here about it a few months back. I tried it on a whim, and found that it's strikingly better than SVN or CVS.

      Creating repositories is trivial (and can be done in place). Merges in large groups are fast, easy, and work well. For almost everything in day-to-day use, the commands are about the same as SVN or CVS (though it does annoyingly require something like "git commit -a" instead of just "git commit").

    14. Re:Article by baxissimo · · Score: 4, Insightful

      I'd assume it's just that most people don't know about Git.

      It just needs a new PR guy and a little bit of time.


      I'd say it's at least in part due to lack of Windows support. Love it or hate it, you don't become the world's foremost anything by ignoring Windows. As can be seen here: http://git.or.cz/#download the developers seem to view "cross-platform" as meaning "We got both kinds! RPMs and debs!".

      There is a partially functional git port in Cygwin, but it doesn't really work as far as I can tell, and it certainly isn't mentioned anywhere on the Git home page. I wanted to like Git, but unfortunately it seems to not be ready for widespread use on the most popular desktop operating system in the world. I'd be happy to try it again someday when it is.

      Compare with SVN or Mercurial or Monotone or most any other SCM system. Most of the others all feature prominent download links on the home page for Windows, Mac, and Linux.

    15. Re:Article by smenor · · Score: 1

      I'd say it's at least in part due to lack of Windows support

      That is an excellent point (and a damn shame).

    16. Re:Article by hitmark · · Score: 1

      this is quite interesting, and he is right about the GPLv3. its kinds moved in the direction of the MS EULA. as in, "if you want to use our product you cant do these things" and then goes on to list just about everything interesting you can do with a computer ;)

      its also interesting that he thinks that if anything can displace X86, its ARM. but as the X86 supporting chips are becoming less power hungry while keeping some kind of speed (via just announced a 500Mhz cpu using 1W at max load or something like that). still, from what i understand, sleep is more important then work load, as a device will spend more time in some kind of sleep state then it will in use. and there ARM still have a edge vs X86. especially if your running a desktop os like windows as iirc it does not understand granular sleep states (could have changed in vista but then vista have its own issues, like more or less requiring both a cpu and gpu, not good on anything but a desktop device).

      but the most interesting thing is that open source makes the instruction set less important. as you have the source, you can recompile it on a different platform. hell, isnt linux one of the kernels that support the most CPU instruction sets? and when you have that, you have the same user space binary interface at the other end. just look at what nokia did with the 770 and N800, or that palm is doing with the foleo. hell, if the latter can do ssh tunneling and X, one is back at some big iron style setup. or for that matter the microsoft smartdisplay (anyone recall that one). drop down on some table somwhere, connect to the net somehow, ssh into your box at home or work, tunnel the X apps onto your foleo ;)

      talk about going full circle, given the current remote desktop and remote office solutions available for windows...

      --
      comment first, facts later. http://chem.tufts.edu/AnswersInScience/RelativityofWrong.htm
    17. Re:Article by Daniel+Phillips · · Score: 2, Interesting

      Q: India is one of the major producers of software engineers, yet we don't contribute much to the Linux domain. The interviewer is not correct. There are a goodly number of India-based developers who contribute to the Linux kernel. Suparna Bhattacharya and Badari Pulavarty come to mind, there are lots more.

      To some extent, the heavy influence of India-based developers on the kernel is due to IBM having a major lab there, which is being emulated by a number of other Linux-backing corporations. The quality of technology education seems exceptionally high from what I can see, and to be honest, the Indian culture seems to be oriented towards higher things than money.
      --
      Have you got your LWN subscription yet?
    18. Re:Article by Crayon+Kid · · Score: 1

      Mod parent down, he has altered the article to include things like "What do you think of penis?"
      No, no, this is Slashdot, he's just following proper procedure. Good God, I'd feel very awkward if there wasn't a penis snuck in there somewhere. Whenever I see some karma whore who reposts a /.ed article and forgets to put their penis in the text I chuckle to myself and think "what a total n00b!" Then I mod their ass down.
      --
      i ate crayons when i was a kid and now i have two braincells and the blue ones taste nicer
    19. Re:Article by jellomizer · · Score: 1

      Well the question is not if a CMS program can do the job but wether if there is something else that does it better. I could manage a large project using other means as well. It would be annoying and a lot of work but it can be done. Never answer an IT Question with can x do it but can y do it better then x.

      --
      If something is so important that you feel the need to post it on the internet... It probably isn't that important.
    20. Re:Article by asuffield · · Score: 1

      There is a partially functional git port in Cygwin, but it doesn't really work as far as I can tell, and it certainly isn't mentioned anywhere on the Git home page. I wanted to like Git, but unfortunately it seems to not be ready for widespread use on the most popular desktop operating system in the world. I'd be happy to try it again someday when it is.


      Trying to use revision control on windows is like trying to drive a car in the sea. It just doesn't make any sense. You need a real platform to build on, not a file manager with issues. Even a full cygwin environment is clumsy without a unix filesystem and network services to back it up.

      Software development on unix is like working with a large box full of tools. Software development on windows is like working with a swiss army knife. There's no way to bridge that gap. If you need real revision control, you also need to get onto a unix platform, so there's little point in porting it to windows. Trying to make it work anyway will be about as effective as pushing your car along the ocean floor.
    21. Re:Article by Zenin · · Score: 1

      In my view it's really hard to say that SVN is CVS done right. While it has improved on a great many aspects of CVS, for others it has been an amazingly huge step backwards. Practical reporting of any kind is a huge feature hole of SVN. It takes an extreme amount of non-trivial wrapper code to even start pulling useful information out of SVN (there are a ton of edge cases). The history of a particular path is incredibly difficult to reconstruct (there's no clean way to list PEG versions). -The developers of SVN don't believe path history matters at all.

      CVS's reporting abilities aren't great either, but at least CVS can let you log from one tag to another...SVN, not at all. -You can...but my god does it take a huge amount of non-trivial code to do so. Scripting reports with CVS is far, far easier to do and do reliably then SVN (and far faster to generate), even allowing for SVN's --xml option (which is great, but doesn't substitute for real reporting functionality).

      SVN can't tell you copied-to points (for example, to tags) only copied-from and so it becomes a significant research effort to figure out what real revision/branch of a file is in which tag. Per file...

      There's a ton more that's flat out bad in SVN. Would I recommend it over CVS? Yes...but just barely. SVN is much more of a step to the side then a step forward.

      That all said...Linus working from his email inbox of patch attachments instead of using CVS, SVN, or anything was just insanely dumb. At least he finally got away from that a few years ago. Linus, like most smart people in the world, is not smart at everything. In fact he excels in only a very, very tiny subset of the software process and is flat out horrible at most of the rest of it. His fan boys however, believe him to be their God and most are simply too ignorant to know any better.

      --
      My /. uid is better then your /. uid
    22. Re:Article by pinky0x51 · · Score: 1

      >this is quite interesting, and he is right about the GPLv3. its kinds moved in the direction of the MS EULA. as in, "if you want to use our product you cant do these things" and then goes on to list just about everything interesting you can do with a computer ;)

      Technically you can do everything you want with GPLv3 code. The only think you can't do is to deny your users freedom. But that's rather an ethical barrier than a technical one and exactly the same barrier which also exists in GPLv2 and which was form the beginning the entire purpose of the GPL.

      --
      Support Free Software! Join FSFE's Fellowship: http://fellowship.fsfe.org
    23. Re:Article by hitmark · · Score: 1

      true, but while the GPLv2 only talks about what you can and cant do with the code, the v3 goes on to talk about what you can and cant do with hardware thats to interact with the code in binary form.

      to me thats like microsoft saying that only their server version of windows can run more then X cpus and Y amounts of ram. there is no technical limitations for this, its just compiled that way and expressed that way in the EULA: or for that matter not being allowed to run their cheapest desktop variants inside a virtual machine.

      i dont have a problem with tivo wanting to lock what can or cant be run on their device because basically they are into selling black boxes. but personally i would not bother as i would go for a generic box in combo with linux and mythtv. hell, it looks like with linuxMCE its a snap to set up: http://linuxmce.org/

      i just wonder if not we will find tivo using the user space driver interface thats being worked on to lock their machines using some kind of binary blob. sure, you can modify the hell of you the kernel or the ui, but screw with the blob and the device is useless.

      --
      comment first, facts later. http://chem.tufts.edu/AnswersInScience/RelativityofWrong.htm
    24. Re:Article by pinky0x51 · · Score: 1

      >true, but while the GPLv2 only talks about what you can and cant do with the code, the v3 goes on to talk about what you can and cant do with hardware thats to interact with the code in binary form.

      Neither GPLv2 nor GPLv3 talks about what you can do with the code. You can do with the code (and with the hardware) whatever you want. But if you distribute the software you have to retain all four freedoms.

      >i dont have a problem with tivo wanting to lock what can or cant be run on their device because basically they are into selling black boxes. but personally i would not bother as i would go for a generic box in combo with linux and mythtv. hell, it looks like with linuxMCE its a snap to set up: http://linuxmce.org/

      If it would be just the hardware, than i would agree with you. But it is not at all about the hardware, it is about the software. If i put my code under the GPL i want that everyone who becomes a copy can use it, improve it and share it. If Tivo denies you this rights, whether by changing the license, by refusing to give you the source code, by using additional software to block you, by using hardware to block you or by any other technical or legal solution someone will find in the future, than Tivo violates the spirit of all GPLs and the license GPLv3.

      --
      Support Free Software! Join FSFE's Fellowship: http://fellowship.fsfe.org
    25. Re:Article by jaavaaguru · · Score: 1

      I evaluated Git and Bazaar, and ended up going with Bazaar for that reason - it works on Windows. It also works on Mac, Linux and Solaris.

    26. Re:Article by Ohreally_factor · · Score: 1

      Trying to make it work anyway will be about as effective as pushing your car along the ocean floor. I'm an aquatic Windows developer (who just ran out of gas), you insensitive clod!
      --
      It's not offtopic, dumbass. It's orthogonal.
    27. Re:Article by Anonymous Coward · · Score: 0

      Sorry, are you talking about Penis or Penix? (And which distro of the latter?) There's often confusion between the two, you know.

    28. Re:Article by Cornelius+the+Great · · Score: 1

      Good God, I'd feel very awkward if there wasn't a penis snuck in there somewhere.

      You aren't by chance posting from prison, are you?
      --
      Sigs are for losers
  5. Alternate link by MythMoth · · Score: 3, Informative

    This one is not (yet) slashdotted:
    http://www.efytimes.com/archive/144/news.htm

    --
    --- These are not words: wierd, genious, rediculous
    1. Re:Alternate link by daveinthesky · · Score: 1
  6. OMG Transaction Svr Killed Microsoft! You Bastard! by nighty5 · · Score: 3, Funny

    [Microsoft][ODBC SQL Server Driver][SQL Server]Transaction (Process ID 666) was summoned by an evil deadlocked process in order to lock up and throw away the key to any IT resources process to request any reasonable requirement for open source software chosen by the deadlock victim. Rerun the transaction with Microsoft products next time and this threat will disappear into thin air - Steve Balmer, Head Deadlocker.

  7. Article Summary Misleading by ahsile · · Score: 4, Insightful

    This article is only slightly about Subversion. A couple paragraphs from the whole thing! They talk about "the plan" for the Kernel, outsourcing to India (they talk a lot about India actually), and other crap. I got bored half way through and just searched for the subversion part, which even then wasn't that interesting.

    1. Re:Article Summary Misleading by nurb432 · · Score: 1

      The interviewer apparently has a issue with outsourcing to india and inserts it into any interview he does.

      ( not saying outsourcing to india is a good thing, just an observation )

      --
      ---- Booth was a patriot ----
    2. Re:Article Summary Misleading by nwbvt · · Score: 4, Informative

      Think that could be because its an Indian news site and the guy himself is Indian?

      Believe it or not, just because something is published on the world wide web doesn't mean it has to cut out everything of local interest.

      --
      Mathematics is made of 50 percent formulas, 50 percent proofs, and 50 percent imagination.
    3. Re:Article Summary Misleading by nurb432 · · Score: 1

      Of course it does, its all about me.

      --
      ---- Booth was a patriot ----
    4. Re:Article Summary Misleading by cyphercell · · Score: 1

      The copy I read gave no hint of it being an Indian site, so reading was a little awkward, but I understood eventually that the interviewer was Indian.

      Now, my take on India and Open Source Software.

      The question of how to start developing OSS is in finding out, what you use it for. What India needs to do, to get into open source is to find out how India uses it. As a developer find out which projects you're best suited for, start using them learn what's on the outside, then learn what's on the inside, if you need to change something create a development copy and work on it. The next part is submission, submit your ideas and on and on. I might be mistaken as I am not a paid Open Source Developer (barely a developer anyways), but I would think most of them have OSS work out there that they did before they were paid. Maybe, it's the hiring process that eludes the Indian market, maybe it's the fact that the best open source software (applications, not CS stuff like kernel hacking) India can write will often be written for problems that exist in India?

      I think I've seen Linus address this somewhere else, but I don't recall where, maybe on youtube.

      --
      Under the influence of Post-Cyberpunk Gonzo Journalism
    5. Re:Article Summary Misleading by bfields · · Score: 2, Insightful

      outsourcing to India (they talk a lot about India actually)

      They don't talk about outsourcing anywhere; the word isn't even used once as far as I can tell.

      The interview appears to have been conducted (and the questions provided by) Indians, so questions like "[how could we] encourage Indians to get involved and contribute heavily [to open source]?" are not surprising. I thought they were interesting questions, actually.

    6. Re:Article Summary Misleading by Ant+P. · · Score: 1

      How does one "outsource" a public open-source project anyway? It's global by definition.

    7. Re:Article Summary Misleading by Chris+Pimlott · · Score: 1

      Are you kidding? You can get 10 volunteer Indian developers for the price of one volunteer Western developer...

    8. Re:Article Summary Misleading by Ohreally_factor · · Score: 1

      Slashdot: News for nurbs, stuff that matters (to nurbs). Yeah, has a ring to it.

      --
      It's not offtopic, dumbass. It's orthogonal.
  8. Linus Slams Big Macs, prefers Double by tjstork · · Score: 0

    Good God. People are pathetic, listening to Linus as if he has great insights as to the mysteries of the universe. He's just a kernel developer that was in the right place at the right time to do the right thing.

    Perspective, please!

    --
    This is my sig.
    1. Re:Linus Slams Big Macs, prefers Double by Anonymous Coward · · Score: 0

      but, some people say he writes all his code in his own blood on the thigh of a virgin, while she gives him a blowjob, all the while listening to William Shatner's version of 'Mr Tambourine man' played backwards!!

      how can we not admire him!?!

      actually, that song would probably sound *better* when played backwards :)

    2. Re:Linus Slams Big Macs, prefers Double by Anonymous Coward · · Score: 0

      to do the right thing? don't you mean to rip off the right thing? linus is the guy who made yet another version of unix and now people are acting like it's revolutionary. he didn't really bring anything new to the table.

    3. Re:Linus Slams Big Macs, prefers Double by dingleberrie · · Score: 1

      tjstork wrote:
      > Good God. People are pathetic, listening to Linus as if he has great insights as to
      > the mysteries of the universe. He's just a kernel developer that was in the right place
      > at the right time to do the right thing.

      AC wrote:
      > to do the right thing? don't you mean to rip off the right thing? linus is the guy
      > who made yet another version of unix and now people are acting like it's revolutionary.
      > he didn't really bring anything new to the table.

      Sorry guys, you posted in the wrong forum. Try www.windowsforum.org :)

      Linus is treated with respect here because he supports his arguments with the reasoning behind them... something that many of us still struggle to do. At least that way you can know whether you disagree with his reasoning or his facts. Props, though, to tjstork for using his real ID to say this.

  9. Indians in open source by JosefAssad · · Score: 0, Offtopic
    Q: India is one of the major producers of software engineers, yet we don't contribute much to the Linux domain. What do you think is keeping Indians from becoming proactive on that front?

    From the opensource.org license-discuss mailing list (just today!):

    From: meteor <emailaddychanged@iiitb.ac.in>
    To: license-discuss@opensource.org
    Subject: Browsers
    Date: Sun, 19 Aug 2007 02:41:00 -0700 (PDT)

    Hi all, as compared to you all am only a starter as far as opensource softwares go and so i need some help from u guys. I am developing an application for PDA and require a light-weight browser for it. I have got an option of using Firefox but can nebody suggest me a lighter browser. Any kind of help will be appreciated.

    Thanks in advance
    Regards
    meteor

    Well, it isn't for lack of trying...

    1. Re:Indians in open source by Anonymous Coward · · Score: 0

      Your point being what?

    2. Re:Indians in open source by Anonymous Coward · · Score: 0

      Some overqualified Indian guy stole his job, took his boyfriend, and bought him out of his house. Currently knee-hugging in his parent's basement, the only thing JosefAssad can do to try to brighten up his miserable existence is to insult Indians on online messaging boards.
      ; -(

    3. Re:Indians in open source by Anonymous Coward · · Score: 0

      This sort of thing happens all the time with sub-continent developers, more usually it's something like:

      > "I'm new to Oracle but I'm having trouble with CREATE TABLE, how do I .....?"

      Someone replies:

      >> RTFM

      The poster responds:

      >>> I don't have the manual, we're supposed to use the online versions on Oracles site but our broadband is down.

      Basically, these guys - although well intentioned and talented (I've worked with many) - are employed by a system with a 1980's proprietory mentality.

      Look at what he says: "I am developing an application for PDA and require a light-weight browser for it..."

      ie. his boss has told him to find something they can steal.

      That's why they don't participate in open-source.

    4. Re:Indians in open source by larry+bagina · · Score: 1

      that makes me pine for the good old days when comp.lang.c et alia were filled with students asking for solutions to their homework.

      --
      Do you even lift?

      These aren't the 'roids you're looking for.

    5. Re:Indians in open source by gilesjuk · · Score: 1

      When there's demand, interest and available skills then there will be Indians doing open source development.

      It's open source, there's no restrictions (other than English as a language?) on any nation working on Linux or open source projects, it will happen.

      It's all about people skills and programming skills, if you can program well, you can accept you don't know everything and listen to others then you'll do well. Also you suggest changes you know will make a difference, changes you've tested and have proven results, not something you read on a website.

    6. Re:Indians in open source by Anonymous Coward · · Score: 0

      I've seen it all too often. I could name some names here but I won't. It has nothing to do with Indians per se, but with Indian _firms_ which, apparently, like to hire underqualified 'warm bodies' on occasion. Nothing new or earth shattering here, but for some reason, said w. b.'s have developed the skill of 'asking people on mailing lists to do their work for them' as a substitute for real work.

    7. Re:Indians in open source by try_anything · · Score: 1

      Nothing new or earth shattering here, but for some reason, said w. b.'s have developed the skill of 'asking people on mailing lists to do their work for them' as a substitute for real work.


      I don't know what w.b.s are, but I have noticed many inappropriate newsgroup and mailing list questions from Indians that show more of a desire (or desperate need) to offload work than a need for assistance with a particular question.

      I also get the feeling with many of those questions that the developer is hopelessly out of his depth. Must be a management issue -- hire cheap people who desperately need a job, then drop impossible tasks on them and watch them scramble. I'm sure it's satisfying if your measurement of management success is paying somebody almost nothing to work his ass off day and night, but I can't imagine that it ever results in usable software.
  10. I liked his take on different distro choices by Anonymous Coward · · Score: 0

    He says this:

    "But in the end, choice may be inefficient, but it's also what keeps everybody involved at least 'somewhat' honest. We all probably wish our politicians were more honest than they are, and we all probably wish that the different distros sometimes made other choices than they do, but without that choice, we'd be worse off."
    ==============

    I personally do get frustrated by all the different distros and their package requirements. But strangely, it's those choices that make it fun and interesting. Yeah, yeah I do get lazy sometimes and would rather install an rpm cleanly without compiling from source sometimes but I wouldn't get better without the challenges. As for politicians, choices, and fair honest government; I live in America so forget it. THE EMPIRE RISES!!

  11. SVN vs. CVS by Anonymous Coward · · Score: 0

    SVN and CVS are version control systems that help to sync the code from different developers into one codebase.

    Both do their job (CVS since years). SVN does some trivial things better than CVS.

    SVN is a little more newbie friendly than CVS because it's cmdlines need less options (e.g. only 'svn update' instead of 'cvs update -PRd').

    git (started and favored by Linus) does everything better but is much more difficult to use.

    If you're a newbie programmer and need version control you might start with CVS and SVN. git might be overkill. Especially for one-man-projects.

    1. Re:SVN vs. CVS by Dan+Ost · · Score: 4, Interesting

      I've never used git on any project big enough to have multiple developers, but I use git for my one-man-projects for the simple fact that it's so easy to create a repository.

      Simply move the directory you're working in and type 'git init' and you're off and running. If you're developing the same code on multiple machines, it's simple to develop on them independently and still sync relevant changes. Frustrating.

      With SVN, you have to set up a central repository (not difficult, but tedious) and if you're working with the code on multiple machines that aren't always on the same network you either have to have a SVN repository on each one and manage syncing them somehow, or one machine can't make commits when the other isn't on the network. Frustrating.

      I still find git to be a little confusing (especially in regards to warnings seen when pushing or pulling changes from one repository to another and merging branches), but I've decided that even if git isn't the best answer, a distributed version control system is closer to the Right Thing than the old way of doing it (for my purposes, at least).

      --

      *sigh* back to work...
    2. Re:SVN vs. CVS by Anonymous Coward · · Score: 0

      "If you're a newbie programmer and need version control you might start with CVS and SVN. git might be overkill. Especially for one-man-projects."

      In that case, you want to look at Mercurial (hg, after the element Mercury). CVS and SVN are Terrible. Really fundamentally the wrong design, and a PITA to use. And yes, I've used CVS, SVN, SCCS, Bitkeeper and git and hg. Save yourself the trouble and learn why a distributed system is important.

    3. Re:SVN vs. CVS by Dan+Ost · · Score: 1

      Oops. Please disregard the first occurance of the world 'Frustrating' in the previous post.

      --

      *sigh* back to work...
    4. Re:SVN vs. CVS by stoicfaux · · Score: 3, Insightful

      Both do their job (CVS since years). SVN does some trivial things better than CVS.

      SVN doesn't do the job because there's no built-in merge tracking, which leads to serious merge bugs.

      Repeated merges (bi-directional merges) between branches generates false positives (the lack of merge tracking causes SVN to re-merge previously merged code.) The lack of true renames, means that you can lose changes during a merge if renamed files are modified on both branches. The svnmerge.py script only works at one directory level, which makes merging a single file deep in the project annoying. Since a checkin and a merge checkin are identical, there's no way to enforce merge tracking standards via hooks. All of these merge weaknesses require extra training and/or merge meisters, which is really clumsy in a large organization.

      SVN is useful if you only use short lived branches (which will minimize the problems listed above.) I would not use it for large organizations due to training issues, nor for branches that require lots of inter-branch merging.

      Hopefully, the merge tracking being implemented for SVN 1.5 will make SVN a real/complete scource code control system.

    5. Re:SVN vs. CVS by mrchaotica · · Score: 1

      With SVN, you have to set up a central repository (not difficult, but tedious) and if you're working with the code on multiple machines that aren't always on the same network you either have to have a SVN repository on each one and manage syncing them somehow, or one machine can't make commits when the other isn't on the network. Frustrating.

      ...what?

      The way SVN is supposed to work is that you set up one machine to hold the repository (which ought to be accessible from either the Internet or a VPN, I suppose, if you move around a lot or something), and you can make commits to it from anywhere. You seem to be trying to say you find this difficult, but I don't understand how. Is it really that hard to connect to the Internet when you want to commit code?

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

    6. Re:SVN vs. CVS by Antique+Geekmeister · · Score: 1

      Yes. If I'm on a problem-solving trip, or a training trip, and the repository is an internal corporate one, I'm reliant on a secure connection all the way back to that repository for every single commit. This creates considerable difficulties in quite a few environments, and that makes frequent, small commits very difficult indeed.

    7. Re:SVN vs. CVS by Dan+Ost · · Score: 1

      If I'm primarily developing code on my laptop, but need to make changes to a test machine, then I'd have to fire up my laptop in order to commit those changes from the test machine if I'm using SVN. With git, I commit those changes locally on the test machine and then, at my leisure, merge the test machine code into the primary code base.

      I find it very convenient to work this way. YMMV.

      --

      *sigh* back to work...
    8. Re:SVN vs. CVS by mrchaotica · · Score: 1

      If I'm primarily developing code on my laptop, but need to make changes to a test machine, then I'd have to fire up my laptop in order to commit those changes from the test machine if I'm using SVN.

      Even if you're primarily developing code on your laptop, the repository still ought to be on a server. Then you don't have to fire up the laptop. That's how SVN is supposed to work -- putting the repository on your laptop is doing it wrong.

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

    9. Re:SVN vs. CVS by Dan+Ost · · Score: 1

      But then I can't make commits to the code unless my laptop is on the same network as the server. No working from home unless VPN is up (which I have little control over). No working outside. No working when out of town.

      No matter where I put the repository, there will be some scenario where I can't make a commit when I'd like to.

      --

      *sigh* back to work...
    10. Re:SVN vs. CVS by Anonymous Coward · · Score: 0

      Even if you're primarily developing code on your laptop, the repository still ought to be on a server. Then you don't have to fire up the laptop. That's how SVN is supposed to work -- putting the repository on your laptop is doing it wrong.

      So, someone working at a project at home would need an extra machine just for SVN... Not exactly a great selling point.

    11. Re:SVN vs. CVS by mrchaotica · · Score: 1

      Okay, but if your distributed "repository" isn't connected to anybody else, then you're still not making a "commit" anyway -- so I still don't see the point.

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

    12. Re:SVN vs. CVS by mrchaotica · · Score: 1

      No, if they're working only at hone then there's no problem keeping the repository on the laptop. Either the development is distributed (and a server is needed), or it's not (and a sever isn't needed). Those are the only two possibilities.

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

    13. Re:SVN vs. CVS by Dan+Ost · · Score: 1

      The point is that I can make as many local commits as I need to while developing before I push any changes to another repository. When I'm finally ready to push my changes upstream, I can preserve as much of my local commit history as I want to. This way I can have very high resolution commit histories while I'm developing something, but give others more human readable commit histories in the upstream repository.

      I realize that in the grand scheme of things, it's a minor point. But, as I said before, it's convenient.

      --

      *sigh* back to work...
    14. Re:SVN vs. CVS by mrchaotica · · Score: 1

      Ah, ok -- now it makes sense!

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

  12. BitKeeper vs. SVN by DrDitto · · Score: 1

    My project recently switched from BitKeeper (Torvalds preferred system before the license issues) to SVN. BitKeeper is a nice system and I think it is better if you have a good development process. For my project with less than 10 developers and with a loose process, SVN is the better tool. SVN allows updates to single files and this really comes in handy whereas BitKeeper forces _everything_ as atomic changesets. For example, if a global.h in the trunk gets updated with new parameters and I only want to incorporate the changes to this file in a branch, it is no problem. But in BitKeeper, I could only make this update if a) the changes to global.h where the only changes in the ChangeSet, and b) if no other changesets were pushed prior to the trunk. BitKeeper does *not* allow cherry-picking of Changesets. I've tried doing so with scripts and patch files, but it is messy at best.

    1. Re:BitKeeper vs. SVN by Anonymous Coward · · Score: 0

      BK is seriously brittle crap. Nothing like corrupted metadata to ruin your day (it's why McVoy threw such a snit over Tridge's interop tool). Darcs can do cherrypicking out of the box afaik (it orders changesets with every update using its weirdo calculus). And Mercurial with patchq does cherrypicking pretty nicely, though it's a bit more bureaucratic.

      I use a two-tiered approach, using darcs for development then CVS on the master repo. You lose meaningful CVS commit comments, but no one in my org reads them anyway.

  13. Re:Oh please.... by dbIII · · Score: 1

    Who really gives a flying hoot what Linus thinks anymore?

    Only people interested in the kernel I suppose. Personally I think people who name non-gnu projects with a gnu in front of the name may have a slight bias against him due to the LiGnuX naming debacle and the repeat with the gnu prefix. Thus the "flying hoot" can be forgiven and understood. Just put up with him even if he has different views on GPLv2 vs GPLv3 - it's not some huge heresy.

  14. Who cares? by Anonymous Coward · · Score: 0

    We don't need any front page stories about Torvalds at all. He wrote an OS... like 20 years ago. Get over it, he's just a guy. No one cares what he thinks about anything unless it has the word "linux" in it.

    1. Re:Who cares? by Anonymous Coward · · Score: 0

      feel free to filter the frontpage to have only stories about rumours of Steve Jobs farting something or other. He's obviously THE man of our times, right?

    2. Re:Who cares? by QuietObserver · · Score: 1

      Come to think of it ... why would anyone care about what Bill Gates thinks? Apart from him still being one of the sharpest cookies in the industry that is. Why indeed? The money he has to spend? Is that your criterion?

      I have no intention of dissing your well thought out and reasoned comment, but Bill Gates has only ever been good at one thing; marketing. When it comes to computers, I don't think there's anyone at Microsoft who has the vaguest idea how to make a decent kernel, except maybe a few peons whose opinions are about as highly regarded by Microsoft as a their customer's opinions are.

  15. Please stop with flamebat summaries by Pecisk · · Score: 1

    Linus isn't slamming SVN and he responses very insightful why he things git is better. Please, stop this propaganda style summary writing, it is getting very old.

    Nevermind that, interview was ok, not lot of new info, but much calmer and clever Linus than last months.

    --
    user@ubuntubox:~$ stfu This server is going down for shutdown NOW!
    1. Re:Please stop with flamebat summaries by Anonymous Coward · · Score: 0

      As already mentioned, he has quite openly slammed SVN and CVS:
      http://video.google.com/videoplay?docid=-219933204 4603874737
      This isn't propaganda - it's actually completely accurate.

    2. Re:Please stop with flamebat summaries by fm6 · · Score: 1

      Don't confuse flamebaiting with simple sloppiness. Which weekend editors do a lot. And ignore my sig: that's directed at moderators who downmod anything they disagree with.

  16. Oh come on by bsander · · Score: 2, Funny

    I love penis. Frankly the batcave scares me. 43 comments already and nobody found that funny?
  17. rerun the transaction... by someone1234 · · Score: 1

    LOL. They actually ask us to perform DDOS?

    --
    Patents Drive Free Software as Hurricanes Drive Construction Industry
  18. Who cares? by golodh · · Score: 1
    Err ... who might be interested in hearing from Linus?

    - anybody who likes to hear an opinion that's usually sensible, well thought-through, honest, and devoid of humbug?

    - someone who is interested in hearing from the guy who succeeds in maintaining sufficient technical credit to have the likes of Alan Cox, Andrew Morton, and a raft of others you've never heard about listen to him?

    - people who think that the ideas of a fellow whose ideas proved fruitful might be interesting?

    Come to think of it ... why would anyone care about what Bill Gates thinks? Apart from him still being one of the sharpest cookies in the industry that is. Why indeed? The money he has to spend? Is that your criterion?

  19. Re:Oh please.... by TheRaven64 · · Score: 1

    I think people who name non-gnu projects with a gnu in front of the name may have a slight bias against him If this is meant to be addressed to the grandparent poster, who is the maintainer of GNUstep, you should be aware that GNUstep is a GNU project. They require copyright assignment to the FSF from contributors, and have since the project began (it grew out of an older GNU project).
    --
    I am TheRaven on Soylent News
  20. why by someone1234 · · Score: 1

    CVS was before SVN which was before git.
    Currently, people migrate from CVS to SVN.
    Migration is painful, people don't like to migrate, because 'if it isn't broken, don't fix it'.
    Linus himself said, SVN is 'good enough', and i agree.
    I won't switch to git, right now. One switch a year was enough, and I did a CVS->SVN switch recently.
    But I don't say, i won't use git in the future.
    Some parts of SVN i dislike, including crashes when writing up the commit comment.
    I just don't want to learn a fundamentally different stuff, and bother with migration.

    --
    Patents Drive Free Software as Hurricanes Drive Construction Industry
    1. Re:why by HighBit · · Score: 1

      crashes while editing commit messages?

      Isn't that your text editor, not svn?

      Try svn -m or svn -F .

    2. Re:why by someone1234 · · Score: 1

      Seriously, i have no idea. The text editor is vim.
      And the crashes come rather randomly, but apparently if i have more stuff to commit, the chance is higher.
      It is very frustrating. Thanks for the svn tips, i will check them out.

      --
      Patents Drive Free Software as Hurricanes Drive Construction Industry
  21. Re:BitKeeper vs. SVN (Bazaar?) by SpzToid · · Score: 1
    I'm not going to argue against what Linus is saying, in fact I'll add my own frustration. However much of my frustration stems from trying to learn what (A.) what options are available, and then (B.) trying to implement them.

    And what I really want to do is simply work in Eclipse. This rant neatly sums up my feelings on the current state of source code version control. From it:

    ...I wouldn't mind some consolidation in the VCS arena so the talented VCS guys can work towards three killer VCSs (Subversion, Mercurial or Bazaar, and Git are my choices). And then they can band together and make sure my life doesn't suck in Eclipse when I am forced to use the editor. =)


    I've already spent *much* time and effort and still I haven't implemented a working version control system, stemming from the source at drupal.org, (my pet project).

    And FWIW, I've ready several docs on Bazaar & Drupal, and what exists leads to a dead dead dead server. It's as if there was a sudden interest among the Drupal community for Bazaar, and then everyone (or at least according to Google) went silent. Like Roanoake.
    --
    You can't be ahead of the curve, if you're stuck in a loop.
  22. Other subversion flaws by Antique+Geekmeister · · Score: 2, Informative

    There are other issues: the Subversion authors have made a very real mistake here in keeping unencrypted passwords online, by default, in every public Linux or UNIX client compiled from Subversion's basic source code.

    I just had to have a polite conversation with a professional peer who kept his home directory on his laptop, then turned on NFS shares "to get work done". I waited, very politely, until he put his laptop on the DMZ with his NFS shares turned on. Then I pulled his SSH keys for a set of sourceforge projects from his directory, and his password from his oher Subversion repositories. Voila! I now have write access to his Sourceforge subversion epositories.

    I'm patient. But crackers aren't, and scan for this sort of vulnerability constantly. The Subversion authors should never have bothered to include the ability to store the password, at all.

    1. Re:Other subversion flaws by Serpent+Mage · · Score: 1, Informative

      I waited, very politely, until he put his laptop on the DMZ with his NFS shares turned on. Then I pulled his SSH keys for a set of sourceforge projects from his directory, and his password from his oher Subversion repositories.

      Considering that both the ssh keys folder and the subversion authorization folders are both chmod 700 by default, it doesn't matter if he tosses up an NFS share. You still cannot access it without being him or root. And of course if you had his password anyway then trying to access his password by him sharing his home directory is pointless anyway as you could simply just ssh into his computer and grab it. I call shenanigans on this one.

      The Subversion authors should never have bothered to include the ability to store the password, at all.

      As I mentioned above, by default, without the author changing permissions manually, the passwords are accessible only to the user. Even the group and world are not allowed access into the folder much less the files in them. And for those of us who live in the real world with real enterprise grade software to work on that span a dozen different repositories with at least 6 different authentication systems, yeah remember passwords is a godsend.

      Then again, all my "file sharing" happens with a special user account that is nothing but filesharing and I just have symlinks into that user. And it is all samba based filesharing not NFS and it is locked down with a user/password to even access the samba share.

      Subversion *does* have many flaws but the storing of passwords is not one of them. That is almost a mandatory feature requirement to work with repositories in most development organizations.
    2. Re:Other subversion flaws by gerddie · · Score: 2, Informative

      Considering that both the ssh keys folder and the subversion authorization folders are both chmod 700 by default, it doesn't matter if he tosses up an NFS share. You still cannot access it without being him or root. In the "simple" setup of an nfs server mounting the nfs share is usually independent of the user doing so, and if the other guy didn't restrict the allowed hosts of the shares, anyone on the net can do it, if he only knows the proper name, no passwords required. After you got this far, being him on nfs is just a matter of having the same user id - at least until nfs v3. Of course there are measures to restrict access, but someone exporting his home "to get work done" might not think that far ...
    3. Re:Other subversion flaws by Antique+Geekmeister · · Score: 3, Insightful

      You've apparently not worked with NFS. Simply setting a username on your NFS client with the same UID as the user on the server allows access to all those contents of the the "chmod 700" home directory and .ssh directory. NFS is commonly known as "No Fucking Security" for a number of powerful historifcal reasons, most especially this one.

      You're also apparently trapped by the same error as the Subversion authors have made. You think the local disabling of permissions to read the data means that someone locally cannot actually read the plain text passwords. Other means for access include:

      * Booting with a live CD to access every file on the local drive.

      * Getting fools to run a USB device on Windows systems (which doesn't accss the TortoiseSVN stored passwords, but can easily access SSH keys and passwords stored under CygWin)

      * Removing hard drives for duplication (apparently a common practice in European hotels before international conferences, where thieves enjoy quite a lot of easy nabbing of passwords or even industrial espionage)

      * Accessing backup tapes (an extremely popular hobby for both amateur and professional system crackers)

      Setting the permissions to 700 keeps out only the most casual and polite of attackers. It's generally no more effective than putting a deadbolt on a screen door.

    4. Re:Other subversion flaws by Antique+Geekmeister · · Score: 1

      Please note that I do not discredit your personal efforts to handle this more securely: your approach seemms fairly sound. But the storing of passwords in plain text is an amazingly stupid part of Subversion, one that is by now a favorite attack vector against people like yourself who don't realize the nature of some of the security risks of it.

    5. Re:Other subversion flaws by GPL+Apostate · · Score: 1

      Simply setting a username on your NFS client with the same UID as the user on the server allows access to all those contents of the the "chmod 700" home directory and .ssh directory.


      I found this out, a few years ago, when I worked at a major medical device manufacturer. I inadvertantly stumbled onto this phenomenon when I discovered that when running Interix on my NT Box on the company network, it didn't prompt for a password (as it did when accessing network shares with plain Windows). I took a chance and set up an account on my NT Box (we all had admin access to our desktop boxes in the lab) to match that of a higher-level collegue. Viola. I had read and write access to all his files on the network.

      This was on a company network which contains the source code and many other controlled documents for implantable medical devices: namely- the source code for pacemakers and implantable defibrillators.

      It scared the crap out of my and I quickly CEASED doing anything like that. It was too scary to admit having done or report to 'the authorities.'

      I hope they've tightened up security some since then.
      --
      Microsoft says legacy (serial/parallel) ports are bad. They don't obfuscate the hardware enough.
    6. Re:Other subversion flaws by Antique+Geekmeister · · Score: 1

      But this is why you need to report it! Give your security and networking people the ammunition they need to do thing right, and explain it in small words to that gentleman who thought "the default permissions are 700, so you can't normally access it".

      There are powerful file sharing systems that do take security more seriously. CIFS is one of them, although its's lack of symlinks and odd permission handling is quite awkward. AFS is another one that has a huge startup cost but scales well and relies on much more serious levels of security (such aa Kerberos authentication.)

    7. Re:Other subversion flaws by myowntrueself · · Score: 1

      Subversion *does* have many flaws but the storing of passwords is not one of them.

      So they aren't stored in plain text then?

      --
      In the free world the media isn't government run; the government is media run.
    8. Re:Other subversion flaws by TheRaven64 · · Score: 1

      No, they're not. Passwords are not stored at all. What the grandparent is discussing is SSH private keys. When using Subversion over SSH, any of the login mechanisms used for SSH are available. One of these is to use passwords, another is to use public key cryptography. If you use public keys, then you have the option, when you create your key (actually, it's the default), of encrypting it with a pass-phrase. This phrase must be entered every time the key is read by SSH. You can also use something like ssh-agent which caches the decrypted key in memory (so root can potentially steal it, but someone who copies the file is still out of luck. Make sure you encrypt virtual memory when you use this).

      If you're going to leave your SSH keys somewhere accessible, then you should encrypt them. If you don't then you are an idiot, and any resulting security breaches are entirely your fault. The fact that the attacker will have shell access on any machine you SSH into is likely to be much more of a problem than the fact that they can access your svn repository.

      --
      I am TheRaven on Soylent News
    9. Re:Other subversion flaws by Anonymous Coward · · Score: 0

      Lets not forget NFSv4, in which they have fixed the inherent problems.

    10. Re:Other subversion flaws by WuphonsReach · · Score: 1

      There are other issues: the Subversion authors have made a very real mistake here in keeping unencrypted passwords online, by default, in every public Linux or UNIX client compiled from Subversion's basic source code.

      Explain to us how they were supposed to *not* store unencrypted passwords and still allow use of the svn: protocol? There's simply no encryption model that allows that possibility to exist.

      (Hint, if you want secure communications, use SSH keys.)

      --
      Wolde you bothe eate your cake, and have your cake?
    11. Re:Other subversion flaws by Antique+Geekmeister · · Score: 1

      If you can't bother to do security right, don't bother writing a protocol. I'm serious: I've seen way, way too many versions of "exciting new protocols!" such as jabber clients where the author added some cool feature and then left everything as porous as a sieve by default. The result is that people like me have to clean up the mess, and then people wonder why it takes us so long to do things when they can just set one up at home in 10 minutes.

      If you can't be bothered to store keys properly, you should at the very minimum not make it the default configuration for your SVN, HTTP, and HTTPS access technologies. It should require at the very minimum an extra command line flag marked something like "--insecure".

  23. Important Differences by One+Childish+N00b · · Score: 2, Interesting

    As to my 'iconic image', I tend to dislike that part personally. I'm not a great public speaker, and I've avoided travelling for the last several years because I'm not very comfortable being seen as this iconic 'visionary'. I'm just an engineer, and I just happen to love doing what I do, and to work with other people in public.

    This, people, is the key difference between Linux and Microsoft, and even Apple. Steves Ballmer and Jobs both want to be seen as visionaries, as all-knowing technological sages of our time. That isn't neccessarily a bad thing, as we've seen with the way Jobs has turned Apple around since he took over, but it does explain the difference between the philosophies of the groups: Apple and Microsoft take the approach of throwing new features in whenever they find them, so as to be seen as forward-thinking and 'next-gen', and sometimes that works and sometimes it doesn't - Spotlight being an example of something that does work (yeah, there had been desktop search before, but nothing quite that efficient and right-on-the-desktop in what can be called the 'Big 3' operating systems), and things like the are-they-in, are-they-out dropped features from Vista being an example of something that doesn't.

    Linux, however, taking it's cues from Linus, approaches things from an engineering perspective. Visionary? That's all well and good, but will it run the risk of breaking? Yes? Then it's not going in. When you don't have a product to sell, it's a lot easier to base your development priorites on a more sound engineering base. Therein lies the difference; Jobs and Ballmer see themselves as visionaries, while Linus - who, whether he likes it or not, is the 'spiritual leader' of the Linux community - sees himself as 'just an engineer'. (Of course, the point could be made that Linus has the luxury of only being concerned with the kernel, where security and stability are the key things and form over function is rarely if ever required - do the likes likes of Mark Shuttleworth, Matthew Szulik, etc see themselves as engineers, or as visionaries?)

    --
    Dealing with lawyers would be a lot less tedious if they all looked like Casey Novak.
    1. Re:Important Differences by Nixoloco · · Score: 1

      On one hand you are talking about an engineer/programmer working directly on an OS kernel. On the other you are referring to CEOs of very large corporations that make a multitude of products far more complex and wide ranging than just a kernel. You would be better off comparing the statements from the CEO of Red Hat, Novell etc. to those of Ballmer/Jobs.. or maybe an engineer within Microsoft/Apple to those of Linus. It is the Job of a CEO to appear as a visionary. It's part of their job to sell both the company and its products.

    2. Re:Important Differences by Antique+Geekmeister · · Score: 1

      Oh. Oh, my. Have you ever looked at the *rest* of the Linux operating system? So much of it is GNU based, it's really unfair to call Linus the spritual leadre. Maybe the rock on which the church of open source was built, rather than its founder. Please review other core components like bash, gcc, and glibc, and look at how those came from Richard Stallman and the Free Software Foundation before you call Linus the spiritual leader.

      Linus is fabulous: I massively approve of his work and his attitude, but spirituals leaders need to be slightly more leading edge than Linus.

    3. Re:Important Differences by samkass · · Score: 1

      FSF did some stuff. MIT did some stuff. The KDE guys did some stuff. BSD even did some stuff.

      They all did it for Linus' system-- that's why he's the spiritual leader. Richard Stallman is hardly a "leader" in the Linux world-- he's done a lot of great stuff, but if it were up to him we wouldn't have anything like Linux.

      If Richard Stallman wanted to be the spiritual leader of an OS, he should have finished Hurd back in '90 before Linux got popular.

      --
      E pluribus unum
    4. Re:Important Differences by TheRaven64 · · Score: 1

      FSF did some stuff. MIT did some stuff. The KDE guys did some stuff. BSD even did some stuff. They all did it for Linus' system

      The FSF was formed in 1984, Linux 0.1 was released in 1991. MIT released X in the early '80s, with X11 coming out in 1987. They did not do it 'for Linus' system,' it just happens to work on Linus' system because it more-or-less implements POSIX (a standard that RMS helped create). All of the FSF stuff, MIT stuff, etc works on BSD UNIX and OpenSolaris, as well as other proprietary UNIX systems (and a lot of it on Windows with SFU or Cygwin). Much of it also runs on HURD and Minix, although I probably wouldn't choose to use either in a production environment.

      To say that projects that started almost a decade before Linux was started were done 'for Linus' system' is idiotic. KDE is the only one of the projects you list that began after Linux, and it works very well on *BSD. You can easily use any of the projects you listed without using Linux, but using Linux without using any FSF code is almost impossible.

      --
      I am TheRaven on Soylent News
    5. Re:Important Differences by Antique+Geekmeister · · Score: 1

      Thank you, you saved me the trouble of looking up these dates. Experience can help you appreciate where these things actually started and why they've evolved in certain ways.

      For goodness's sake, try to compile Linux without the GNU versions of make, gzip, and gcc.

  24. Re:Site is slashdotted by b100dian · · Score: 1

    Yes, slashdotted: but not a bandwidth/clients problem, but a horrible programming error, it seems.

    --
    gtkaml.org
  25. Re: your sig by zippthorne · · Score: 1

    Why did you specify bitlength 4? Wouldn't it work for any unsigned units since the leading zeros would turn into leading ones in the invert operation?

    --
    Can you be Even More Awesome?!
  26. PARADIGM SHIFT! by StCredZero · · Score: 5, Informative

    Damnit, it's a paradigm shift that Linus is talking about. True distributed source code management brings an entirely new way of working. It enables very fast merging at a very fine granularity, which lets you use casually use this information (about what changed and when) in a way that changes the nature of how you work! It's the same sort of difference that code completion or Google search made. Once a certain kind of very useful information -- that has always been available, but a bit inconveniently -- becomes like running water out of the tap, it enables ways of working that just wouldn't have been practical before.

    If you really want to know what Linus is talking about from the man himself, watch this Google Tech Talk. It's over an hour, but there's nothing like hearing it straight from the horse's mouth.

    http://video.google.com/videoplay?docid=-219933204 4603874737&q=git+google+tech+talk&total=3&start=0& num=10&so=3&type=search&plindex=1

    1. Re:PARADIGM SHIFT! by dkf · · Score: 4, Interesting

      Damnit, it's a paradigm shift that Linus is talking about. True distributed source code management brings an entirely new way of working. It enables very fast merging at a very fine granularity, which lets you use casually use this information (about what changed and when) in a way that changes the nature of how you work! It's the same sort of difference that code completion or Google search made. Once a certain kind of very useful information -- that has always been available, but a bit inconveniently -- becomes like running water out of the tap, it enables ways of working that just wouldn't have been practical before. You know, that sounds so much like an advertorial! Would you care to provide a little bit of original analysis to go with your otherwise-unleavened hype? In exactly what way does a distributed source code management system change the way you work? (Remember, some of us have been using 'cvs annotate' and 'svn blame' over high-bandwidth networks for a long time now.) While you're at it, do distinguish between the various aspects (e.g. multiple repositories vs. braided versioning) even if one really implies the other.

      And do try to go easy on the phrase "paradigm shift" in your explanation even if this is one; marketdroids love over-using it and it's come to be a code phrase for "same old, same old". Focus on how things have changed for you and you'll get a better response.
      --
      "Little does he know, but there is no 'I' in 'Idiot'!"
    2. Re:PARADIGM SHIFT! by peterarm · · Score: 5, Insightful

      This is what's great about Linus Torvalds:

      [me using random software]: 'This sucks. I could code something better in two weeks.' [false, or "true in theory, but I didn't do it"]

      [Linus Torvalds using random software]: 'This sucks, and basically 99% of the software in this entire category sucks, for reasons X, Y and Z. I could code something better in two weeks.' [true; done]

      Truly impressive. Whenever I start to think I've accomplished anything programming, I look at video like that (which was on reddit how long ago?) and realize once again that there are people who live on a different planet than I do.

    3. Re:PARADIGM SHIFT! by Anonymous Coward · · Score: 4, Interesting

      In exactly what way does a distributed source code management system change the way you work?

      It gives you private branches and commits, which allow you to work with the power of a VCS, but without having to pollute the main repo with dead ends, poorly written changes, and experiments. It also allows for true disconnected operation, and allows any developer to "pull" from another developer, again without having to pollute the master repository.

      And specifically with git vs. SVN, git offers true branches and tags (unlike SVN's bizarre, nonsensical "simulations"), and true merges.

      And do try to go easy on the phrase "paradigm shift" in your explanation even if this is one; marketdroids love over-using it and it's come to be a code phrase for "same old, same old". Focus on how things have changed for you and you'll get a better response.

      It (git and distributed VCS) is a "paradigm shift" the same way that, say, the relational model is a paradigm shift over the network model. It generalizes the problem and strips it down to certain fundamental concepts, and makes those concepts available to you directly, instead of under a layer of ill-conceived and limited operators.

      For instance, in SVN, how do you move a changeset from the tip of one branch to another? You can't. It's not allowed by the model, even though in terms of more fundamental operations, it's easy to describe. But in git, you can. Just cherry pick it to the new branch, then move the tip of the old branch back one changeset (the "dangling" changeset on the old branch will eventually get garbage collected). You could also write your own "git-move-changeset" command using the existing low-level git commands.

      Instead of considering the deeper, underlying issues, the SVN team just cloned CVS's behavior and made it cleaner. Too bad.

      That's exactly what a "paradigm shift" is: finding the deeper, fundamental operations and then showing how the existing systems are just subsets of that functionality.

    4. Re:PARADIGM SHIFT! by Anonymous Coward · · Score: 0

      He did call Subversion crap for all uses. View the video linked above. He cannot once answer the question on why a corporation would use a system such as git for their projects. Fact is that if you are developing for personal satisfaction you will make sure many get your code but if you are getting paid and couldn't care about the company updating your git with someone else's is the lowest priority. Also if an employee gets canned then IT has to worry about the data in their personal git repository.

      For a large percentage of corporations a centralized repository is the only way to go. I think git has the right idea but needs to integrate with a centralized server.

    5. Re:PARADIGM SHIFT! by wildjim · · Score: 1

      I'd like to second all of the above. I spent a long, long time trying and testing as many OSS SCM's as I could, and have decided that Subversion is "unfortunate". I like their multiple-architecure support -- using the apache cross-platform libs was rather inspired... but that's about it!
          Being able to apply tags and branches on the exact same tree is conceptually more natural, even though Subversion's zero-copy/linking initially looks better.
          I'm a big fan of darcs, too, and creating new repo's as branches is easy to get used to, but a little messy when you want to compare differences/changes.

          In addition to this, the Subversions multiple full-body redesign has always made me very, very nervous. I still find it hard to believe that Subversion won't undergo another major redesign at any point!
          To be honest, SVK almost convinced me of using Subversion, especially as it solved Subversion's fundamental difficulties with merging, but by then, Git and darcs had proved themselves far superior.

    6. Re:PARADIGM SHIFT! by sybesis · · Score: 1

      linus is awesome... :P

    7. Re:PARADIGM SHIFT! by OptimusPaul · · Score: 3, Interesting

      When I first heard this crap about Linus not liking SVN I was thinking what a dork, SVN is great. But then this post opened my eyes. This reminded me of all the crap I have to deal with in SVN, it's a pain. I also have to be honest, I've never heard of git, now I must find out more about it.

    8. Re:PARADIGM SHIFT! by Daniel+Phillips · · Score: 1

      do try to go easy on the phrase "paradigm shift" in your explanation even if this is one; marketdroids love over-using it and it's come to be a code phrase for "same old, same old". It's a paradigm shift. Try it, you will see.

      Simple enough? Oh you want reasons. OK, I will mention just one: have you ever experienced a source control system that can allow an arbitrary number of developers to work in parallel, each with multiple parallel development threads in their own local repository? If not, then you will experience the paradigm shift soon after you begin using it. Soon after that, you will be preaching. Oh, and it is also a passable source control system even for a single developer working with a single repository. Arguably more stable than SVN, which is not too bad in its own right. Git has some amazing features like Git-bisect, which is used to track down regressions.
      --
      Have you got your LWN subscription yet?
    9. Re:PARADIGM SHIFT! by Daniel+Phillips · · Score: 2, Interesting

      For a large percentage of corporations a centralized repository is the only way to go. I think git has the right idea but needs to integrate with a centralized server. What happens in the large corporate is, devs end up keeping their "working copy" of the code on their local machine because if they just checked their experimental/broken stuff in, other devs would complain. Same for creating branches in the central repository, if you are doing it for you own experiments you will get unpopular fast. So what happens instead is, a dev makes changes to their checked out copy and does not check in for days or weeks at a time, then bits of this work get lost for one reason or another. Meanwhile, development on the trunk eventually orphans the experiment, merging is too much work and chances are, the whole experiment will get lost or rot too much to be useful and get thrown away. Don't tell me it doesn't happen - a lot.
      --
      Have you got your LWN subscription yet?
    10. Re:PARADIGM SHIFT! by turbidostato · · Score: 2, Interesting

      "What happens in the large corporate is, devs end up keeping their "working copy" of the code on their local machine because"

      Because they usually don't know the tool or the tool's potential.

      "if they just checked their experimental/broken stuff in, other devs would complain"

      I've been working both on Subversion and CVS (among others) and never experienced it. Why? Maybe because I knew about the use of the tool; about how to deploy "this_is_head" moving tags and how to properly use branches, so one developer's experiments doesn't break other's work and still they are "near enough" to main development lines to merge frecuently as needed (and no, abandoned branches were not a problem since they can be pruned out when needed no more).

      "Same for creating branches in the central repository, if you are doing it for you own experiments you will get unpopular fast."

      That's even more extraneous. Why other developers should have to give a damn about branches they don't use? Clearcase, for instance, is mostly based on the "developer branch" concept to great amount and while the product isn't the most popular among developers, it is not because the "developer branch" concept which is the one they tend to like the most.

      "So what happens instead is, a dev makes changes to their checked out copy and does not check in for days or weeks at a time"

      Because:
      a) They ignore the tools possibilities
      b) Their company ignore the advantages of founding proper SCM (people, tools and time) and the SCM tool manager only too often ends up being one of them, or someone without the knowledge and too overburden to do a proper work.

      "then bits of this work get lost for one reason or another"

      And then the proud git user's hard disk fried and his git repo is lost all the same. And then the devolper gets hit by the bus, or resigns and nobody understands what's the hell on his harddisk.

      "Meanwhile, development on the trunk eventually orphans the experiment, merging is too much work"

      That's just the natural outcome of a too long lived branch, no matter is you use a central or a distributed repo. It is the code the one that distances, not the tool that manages the code.

      Subversion should have proper branching and merging. CVS should properly manage whole hirarchies. Both of them should properly handle deltas. But they are all limitations of the tools, not flaws on the paradigm. Surely distributed SCM has his place but centrally managed SCM has it too and it's much more important the former than the latter in corporate environments. Maybe in a future there will come a tool that will allow seemlessly for proper central or distributed SCM, and I can tell I'll be glad for it, but I can assure that the central paradigm will stay strong within corps, because that's what's needed.

    11. Re:PARADIGM SHIFT! by shadanan · · Score: 1

      mod parent up.

    12. Re:PARADIGM SHIFT! by Anonymous Coward · · Score: 0

      Yes, great. It fits the previous definition of "Paradigm Shift". Unfortunately, this is no longer what it means. As far as I can tell, it now means "quick hit me in the face with a Louisville slugger". So, his suggestion to try and got easy on using the phrase should not be taken lightly.

    13. Re:PARADIGM SHIFT! by linuxrocks123 · · Score: 1

      > It's the same sort of difference that code completion or Google search made.

      Search engines I'll give you; Google is just a good one.

      I've used code completion, and it's annoying. If it makes a difference in the way you work, you're either doing something wrong or using a very bad API.

      --
      vi ~/.emacs # I'm probably going to Hell for this.
    14. Re:PARADIGM SHIFT! by locofungus · · Score: 1

      Subversion should have proper branching and merging.

      The key requirement of any reasonable VCS is that any developer can checkin their version of the code at any time (without having to make any special preparations) and any developer can recover that version at any later time.

      As soon as the problems this causes are solved (and they're not all easy to solve) your VCS can fairly trivially be made distributed.

      Starting from the premise that the VCS will be distributed forces the requirement to be able to checkin to be true because there is a use case where the developer can guarantee that there are no other changes in the repository between them going their checkout and them doing their checkin and therefore there cannot be any conflicts at checkin time.

      (It is possible to design a crippled distributed VCS where all the conflicts MUST be resolved at push/pull synch time but that would then violate the second half of the requirement where every checked in version must be available to everybody. If every version is going to be available after a synch then there can be no need to require any conflicts to be resolved at synchup time.)

      Tim.

      --
      God said, "div D = rho, div B = 0, curl E = -@B/@t, curl H = J + @D/@t," and there was light.
    15. Re:PARADIGM SHIFT! by orcrist · · Score: 1

      I've used code completion, and it's annoying. If it makes a difference in the way you work, you're either doing something wrong or using a very bad API.


      Or -- and maybe I'm reaching here -- different people work and think in different ways...

      e.g. I'm the kind of person who is very good at remembering and visualizing the functionality of a program I'm working on or an API I'm using in terms of program flow, and how it works, etc. (kind of holistically) but I can't remember exact keywords, method names, etc. to save my life. I often have to repeatedly look up the exact name and spelling of a method, even if I've just used it in the last 10 minutes. However, I can recognize the name of the method I want at a glance. That makes something like code-completion a blessing for me since it prevents me switching back and forth between references and my program as much. There are plenty more examples, but hopefully you get the idea. YMMV.
      --
      San Francisco values: compassion, tolerance, respect, intelligence
    16. Re:PARADIGM SHIFT! by L4rd0 · · Score: 1

      From the article it looks like Linus is being advertotial himself, raising awareness of Git and trying to get some market share from CVS and SVN. Anyone her got experience of this Git? (The program...not Linus, he rocks.)

    17. Re:PARADIGM SHIFT! by ajs · · Score: 2, Interesting

      [git] gives you private branches and commits Subversion provides the capability for private branching an commits. Problem is, you failed to define "private". If you mean private in the sense that you can work on your own without having others' changes affect your personal work area (or visa versa), then subversion provides private branching. If you are talking about privacy in the sense of others not knowing what you're doing, then you need svk for that.

      And specifically with git vs. SVN, git offers true branches and tags (unlike SVN's bizarre, nonsensical "simulations") Subversion provides true branches. It just does so in a directory-tree model. There's no mathematical difference between subversion's branches and those of another VCS, just an interface difference which I have come to appreciate. I'll admit, though, that there was a significant mental hurdle for me to get over. Tagging in subversion is another case that feels "odd", but is mathematically identical. Because copying a tree doesn't feel like adding a tag, it's off-putting at first, but there really is no difference due to the copy-on-write nature of subversion's directory management.

      and true merges. You phrased that incorrectly. Subversion has true merges. What it lacks is merge tracking. For that you need to use something like svk.

      For instance, in SVN, how do you move a changeset from the tip of one branch to another? Of course, you're using the terminology of git to ask a subversion question, which isn't exactly reasonable. The real question, here, is how you move changes between branches which is fundamentally an abstraction of merging. As noted above, the merge is trivial. The merge tracking (that allows consistency to be maintained post-merge) is not in subversion's toolkit. svk provides this, and moving changes between branches sensibly is quite easy using it.

      Instead of considering the deeper, underlying issues, the SVN team just cloned CVS's behavior and made it cleaner. This is absolutely untrue. On so many levels that it demonstrates how little you know about those two tools. You cannot emulate subversion using cvs because subversion implements many things that cvs never did (directory tracking, repository versioning, copy/move-on-write, among many others). If you don't understand the tools, you are best avoiding a debate about their capabilities.
    18. Re:PARADIGM SHIFT! by Anonymous Coward · · Score: 0

      Amen to what you say, fellow AC! But...

      That's exactly what a "paradigm shift" is: finding the deeper, fundamental operations and then showing how the existing systems are just subsets of that functionality.

      Um, is it exactly that really? Shouldn't what you describe be called a "paradigm expansion"? "Shift" suggests merely a preference change inside a paradigm.

      Or maybe we are just having a syntagm shift here ;-)

      (And most likely, "paradigm shift" never had any natural, specific meaning, never any practical, real-world use to begin with... it smacks of marketdroid mumbo-jumbo more than anything.)

    19. Re:PARADIGM SHIFT! by erikvcl · · Score: 1

      > Instead of considering the deeper, underlying issues, the SVN team
      >just cloned CVS's behavior and made it cleaner. Too bad.

      Made it cleaner? Or made it worse. SVN is crap and it's a downgrade from CVS in virtually every way. It doesn't support branches or tags (sorry, SVN fanbois, SVN's copy feature does not suffice). SVN far slower than CVS and has tons of quirks that CVS didn't have. Yes, there are a few new features there, but none of them are worth the drawbacks. SVN is not now and never has been a replacement for CVS. SVN is a different kind of centralized SCM with different features.

      I agree with Linus, however, that distributed SCMs (e.g git, Mercurial), are better than centralized ones (e.g. CVS, SVN).

    20. Re:PARADIGM SHIFT! by Gr8Apes · · Score: 1

      CVS has issues as well, and I certainly don't like CVS over subversion. Speedwise I've not noticed a significant difference between them. Featurewise they're both missing some features I'd like regarding branching and merging, but then, I haven't delved too deeply into Subversion yet, so perhaps I've just not run across it.

      I've also had the (dis)pleasure of using Clearcase, Starteam, and MKS. Out of the entire set in my experience, clearcase performs the best on complicated branched codebases. MKS has the best feature set, but is wholly unsuitable for enterprise development. There are no atomic commits in MKS as of 2 years ago. This means you can check something in, your client thinks it's checked in, the server logs say it's checked in, but the code was not actually committed to the codebase. Makes tracking down why the build's broken lots of fun. Starteam, well, I preface this by saying it was an older version, and that experience left me with the impression it's not much better than VSS and MKS was a welcome "upgrade". Anything that allows you to permanently delete the entire source tree and its history with a single operation from a client just violates everything that SCM should be in my opinion.

      Perforce is something I've yet to try. I've heard good things about it, but that was from a team that was "selling" it to the rest of us.

      I'll add the ones listed here to the list to evaluate.

      --
      The cesspool just got a check and balance.
  27. From the Department of Redundancy Department... by Anonymous Coward · · Score: 0

    Do we need a front page story on every interview Torvalds does?

    Yes.

    There are good reasons for this, but it would be redundant to repeat them here on Slashdot.

  28. if it isn't broken by epine · · Score: 2, Interesting


    If CVS isn't broken, I have a three-legged ladder I'd like to sell you. I'll even set it up in the parking lot and, with but a modest presence of mind, balance myself motionlessly on the very top step to prove how very not-broken it really is. On one foot. And I'll juggle, too.

    CVS is what happens when you've roped yourself up into some high, awkward, inaccessible place, then you discover you brought along the wrong toolbox. Subversion is a fancy pair of vise-grips with rubber handles: doesn't hurt your hand so much when you have to grasp with extreme force the bolt head with no remaining flat edges, because you're too damn lazy to rope yourself back down to get the tool you should have used in the first place.

    1. Re:if it isn't broken by someone1234 · · Score: 2, Informative

      You preach to the choir.

      --
      Patents Drive Free Software as Hurricanes Drive Construction Industry
    2. Re:if it isn't broken by JasterBobaMereel · · Score: 0

      the problem with CVS is it has the wrong design and is clunky
      SVN is CVS done right i.e. it removed the clunky aspects of CVS
      Git uses a better design (but is still not cross-platform)

      Linus actually said that the main problem with CVS and SVN that he fixed in Git is merging branches is a pain in CVS and no better in SVN, and as a bonus you can do distributed projects. He seems to go on about the distributed part more than just the fact that merges actually work and are easy...

      --
      Puteulanus fenestra mortis
  29. Try darcs by wurp · · Score: 1

    I haven't done a tremendous amount with it, but it is just as easy to set up a repository, and I never get the weird errors you're talking about.

    Things darcs does that svn/cvs/VSS/ClearCase/etc don't do:
          * name patches (commit sets) & find them trivially by name later
          * trivially apply explicit patches to alternate branches
          * automatically find all patches that a patch depends on
          * create repositories trivially
          * see who committed specific lines of code

    Git didn't appear to do a lot of that - no naming of patches, no seeing who last modified specific lines of code, no automatically determining patch dependencies.

    The big problem is that for long revision histories, darcs seems to have a few bugs. Everything I've seen people talk about on the mailing list they've been able to fix or work around, but I have a very low tolerance for bugs in my revision control tool :-) Even so, the extra features are cool enough that I still use darcs for some projects.

    Oh, the other thing: darcs is written in Haskell. I'm not sure if that's good or bad.

    1. Re:Try darcs by krmt · · Score: 1

      * name patches (commit sets) & find them trivially by name later git-tag

      * trivially apply explicit patches to alternate branches I don't really know what an "explicit patch" is. git-apply is probably what you want though.

      * automatically find all patches that a patch depends on I don't know if git can do this, but you don't end up using it that way really. You can use git-cherry to figure out which commits are different from another branch, and then either cherry pick them as desired. You can also use git-format-patch in combination with git-am to do this as well. It'd be nice to just be able to give git a specific commit and have it figure out the ancestors that are necessary for it to apply cleanly. Generally though, it doesn't matter because you just merge from someone's work and trivially diverge using working branches.

      * create repositories trivially git-init

      * see who committed specific lines of code git-blame
      --

      "I may not have morals, but I have standards."

    2. Re:Try darcs by Anonymous Coward · · Score: 0

      > darcs is written in Haskell. I'm not sure if that's good or bad.

      Keeps the code small, but it certainly does make it hard to hack on. And I'm pretty sure only David Roundy understands its patch ordering algorithm. The fact that it's usually staticly compiled into a single .exe that does everything is pretty nice.

    3. Re:Try darcs by wurp · · Score: 1

      Maybe I don't understand git-tag, but what I want is to take all of the changes for a particular feature or bugfix and apply them to another repository, e.g. applying a bugfix from your latest dev branch to the production branch. Tagging as I've used it is an altogether different thing - it's applying a meaningful label to a complete snapshot of the code, not to one set of changes.

      An explicit patch is just, well, one specific patch. A set of changes that were committed together. Darcs will also figure out which patches are necessary on the other repository to move the desired patch, and tell you those, too.

  30. Not everyone is a Linux kernel developer by kyashan · · Score: 1

    Can't read the article linked as it's being slashdotted but I saw the talk he did at Google and I have to say that he missed two big points:

    1. Need support for the most diffused platforms (most you can get on Windows is a supposedly non-performing Cygwin version)
    2. Need support for actual user interfaces other than "command line"

    ..many people need to version binaries, and many need a simple user interface.
    In fact one of the handicaps of SVN is that it doesn't have a client like WinCVS. TortoiseSVN works nice, but most users just want a separate app.

    So he can make his point as much as he wants, but there is a reason why 5000 employees at Google base their work on Perforce and not on GIT.

    ole'
    --
    "La presi e te la pagai (480.000 Lire)"
    1. Re:Not everyone is a Linux kernel developer by Entrope · · Score: 1

      Perforce is a pretty lousy configuration management system. Wide cross-platform support is the only positive aspect it really has going for it. Other aspects just suck less than certain alternatives: price, ease of use, SCM model, etc. Google probably developed easier front-ends in-house, but things like client specifications are maddeningly unintuitive in Perforce, branching is baroque, and having the *server* keep track of client workspace state is a mind-blowingly stupid performance optimization.

      (GIT has several GUIs -- nicer than what Subversion and CVS have on Unix systems, but not as nice as TortoiseSVN or good commercial offerings. GIT can version binary files. The core-git CLI is continuously getting usability improvements, and there are other porcelains that try to make it even easier.)

    2. Re:Not everyone is a Linux kernel developer by kyashan · · Score: 1

      Yeah well, sorry but you made no point.

      Google uses Perforce.. that's a point. "Maybe, perhaps, Google uses a different front end" is not a point.

      From what I've heard from the Google speaker himself, many just do command line with Perforce at Google.. but then again they aren't a game company with thousands of artists.

      I'm not a Perforce fanboy, in fact I was against at first but there must be a reason if it's alive and well.
      For one thing, game dev business is more and more into perforce because SVN is not as efficient and because not everyone bases his or her work on a command line (you can be a coder and still use icons)

      As far as the GIT UI.. You say it's not "as nice" as TortoiseSVN.. and I'm starting to get the point. Let alone the fact that it's still not for Windows...

      So, while I think Linus Torvalds is a great man of our times I still think that he simply doesn't understand that there is a lot of territory that GIT doesn't even start to cover. ..plus of course I'm sure he doesn't mean people to take his strong opinions too seriously 8)

      --
      "La presi e te la pagai (480.000 Lire)"
    3. Re:Not everyone is a Linux kernel developer by Anonymous Coward · · Score: 0

      You're making unsubstantiated claims for no logical reason. "Aspects"? "Probably"?

      As much as you say Perforce sucks, the fact is that it is the preferred solution for engineers who just want to get their work done, as quickly as possible. It is, and will be for the foreseeable future, the best-of-breed SCM solution there is. Period.

    4. Re:Not everyone is a Linux kernel developer by jabelli · · Score: 2, Interesting

      There are lots of clients to choose from at the tigris.org site. If you don't want or need a file browser plug-in/Explorer extension/IDE integration, there are a number of apps to choose from. Granted, TortoiseSVN and Subclipse track the Subversion releases more closely than the others. Personally I use a combination of TSVN with Kdiff3. I also use AnkhSVN in Visual Studio, just for the auto-add and file icons.

    5. Re:Not everyone is a Linux kernel developer by kyashan · · Score: 1

      Other than TortoiseSVN I remember trying RapidSVN but it wasn't quite usable.
      As far as SVN goes I personally just go by Tortoise.. and at work, it's pretty much Perforce, like for many other game companies.

      The problem with the "lots of clients" thing is that they are all OS projects: the project is there, the actual product not quite.

      --
      "La presi e te la pagai (480.000 Lire)"
    6. Re:Not everyone is a Linux kernel developer by asuffield · · Score: 1

      1. Need support for the most diffused platforms (most you can get on Windows is a supposedly non-performing Cygwin version)
            2. Need support for actual user interfaces other than "command line"


      This is a tool for developers. Developers who "need" these things are quite frankly irrelevant, as nothing they produce will still be in use in five years time, so unless you're trying to make a quick buck by selling them some shiny junk, their "needs" can and should be ignored.
    7. Re:Not everyone is a Linux kernel developer by kyashan · · Score: 1

      Not every developer is a programmer.
      There is a lot of people out there that need to use version control systems without writing code or having to bother with command line.

      --
      "La presi e te la pagai (480.000 Lire)"
    8. Re:Not everyone is a Linux kernel developer by Entrope · · Score: 1

      By that standard, you made no point in your original post -- "one company uses Perforce" is not a point.

      Have you used Perforce? I have used it in an academic environment and a corporate environment. It sucked both places, for the reasons I listed and a few I've probably forgotten. GIT is vastly superior for people who are developing on Unix-like operating systems. GIT is faster, more elegant, and much more functional than Perforce. On Windows, Subversion -- in the form of TortoiseSVN -- is generally better than Perforce, but not by the margin that GIT has. Subversion doesn't have *quite* as many features as Perforce, but the TortoiseSVN UI is better and Subversion is generally easier to use (because of the clientspec-stored-on-server part of Perforce).

    9. Re:Not everyone is a Linux kernel developer by kyashan · · Score: 1

      This is becoming a joke... are you even somewhat close to development ?

      You slashdot fanboys should love google right ?
      Go ask google why it picked perforce, don't even argue with me.

      --
      "La presi e te la pagai (480.000 Lire)"
    10. Re:Not everyone is a Linux kernel developer by Entrope · · Score: 1

      I manage a software development team for a living. Before putting on the pointy-haired manager hat, I wrote software full time. I still write code when necessary. The applications and customers for my day work require close and careful revision control as part of larger configuration management efforts. I would not use Perforce (the software) even if Perforce (the company) paid me to use it. At work, we use Subversion primarily because it has reasonable Windows support.

      You avoided my question and introduced the "fanboy" ad hominem. I can only conclude that means that you have never used Perforce. You are the one acting like a Perforce/Google fanboy: you have provided exactly zero mention of technical merits and offered no rebuttal of my points. You are the one who was advocating for Perforce: it is not *my* job to defend your foolish argument, especially when you are obviously unwilling and/or unable to do so.

      I also write software as a hobby. I wouldn't use Perforce for that, either. I use git for my own projects, and other revision control systems when there is a legacy repository in place.

    11. Re:Not everyone is a Linux kernel developer by kyashan · · Score: 1

      For one thing I was at Perforce User's Conference last May.

      I'm not a version management buff, but I can definitely tell why Perforce is so expensive (compared to free alternatives) yet so widely used.

      I work for a game company and it seems that most other game companies (with a decent budget) prefer Perforce.
      EA also had a lecture at that conference..

      I'm not in the business of explaining why one would choose a version control system over another (surely not in a dying topic on Slashdot 8). I just wanted to make it clear that Linus Torvalds speaks for itself and while he makes many good points, also doesn't consider the world of development in a broader sense.

      --
      "La presi e te la pagai (480.000 Lire)"
  31. Not at all. by Anonymous Coward · · Score: 0

    MS was dead before this. It just has a lot of folks who pay money to them, and are afraid to say that they are wasting money.

  32. Re:Site is slashdotted by ILongForDarkness · · Score: 1
    But it is some much more fun commenting on the opensource community from the outside :)

    P.S. I always found SQL Server weird. Originally coded my Sybase, but much lower performance. It is almost like the goal on the MS side, was to slow it down once the source changed hands, weird.

  33. Why Indians Don't Contribute Much to Linux by RAMMS+EIN · · Score: 4, Insightful

    ``Q: India is one of the major producers of software engineers, yet we don't contribute much to the Linux domain. What do you think is keeping Indians from becoming proactive on that front? How do you feel we could encourage Indians to get involved and contribute heavily? You have a fan following in India; could your iconic image be used to inspire enthusiasts? -- Bhuvaneswaran Arumugam.

    Linus: This is actually a very hard question for me to answer. Getting into open source is such a complicated combination of both infrastructure (Internet access, education, you name it), flow of information and simply culture that I can't even begin to guess what the biggest stumbling block could be.''

    My guess is it's because the _bulk_ of Indian software engineers are being raised on Microsoft technology (the fact that it's Microsoft is irrelevant here; what matters is that it isn't Linux and doesn't resemble Linux). I don't actually know that this is the case, but I suspect it. I've spoken to a number of people from various parts of the world that aren't Europe or North America, and the picture I get is mostly the same: virtually everybody who uses a computer uses (cheap or pirated) Windows, if you take classes in CS you are taught Microsoft tools, and, at work, you use Windows. It's like nothing else exists. Why would you contribute to Linux, coming from such an environment?

    Also, I know for a fact that a lot of people in India get trained on Java. That's yet another platform that isn't Linux and, even if it's more like Linux than Microsoft's platform is, it's still different in important ways. Besides, Java can run under Linux...but that's not what usually happens.

    --
    Please correct me if I got my facts wrong.
    1. Re:Why Indians Don't Contribute Much to Linux by thephotoman · · Score: 2, Interesting

      I'm not so sure about that.

      I work for a company that got burned on outsourcing its support to India. That said, the one guy we hired off of the outsourcing company knows more about Linux than the rest of our system administrators put together. To this day, if anybody has a question that we've found unanswerable by an American employee, we will send him a message.

      --
      Haec merda tauri est. Ceterum censeo Carthaginem esse delendam.
    2. Re:Why Indians Don't Contribute Much to Linux by k8to · · Score: 1

      How is this different from the situation in the United States, for example?

      --
      -josh
    3. Re:Why Indians Don't Contribute Much to Linux by Dodgy_Indian · · Score: 1

      Like Linus says, it is a combination of infrastructure, flow of information and culture. Let me elaborate it from th e Indian perspective a bit.

      The term "Indian infrastructure" is an oxymoron, sure the internet is very much reachable. But, what good is it when you are experiencing blackouts (we call them "load-shedding").

      We have a very high number of "educated" people. If you throw a dime here, you will probably hit 40 engineers, 50 MCSEs, 25 CCNAs, 35 RHCEs, 20 SCSA.... and so on. Suffice, to say we can beat anyone in the world by sheer numbers.

      The only "flow of information" is probably pr0n.

      Culturally, our philosophy is simple - "Will I be able to make a quick buck from it?"

      That should pretty much settle the debate.

      --
      Take it easy people, there is no such thing as "Bangalored" It's "BENGALURU'D" now!
    4. Re:Why Indians Don't Contribute Much to Linux by Anonymous Coward · · Score: 0

      What you say doesn't make sense. On one hand you say that there are a lot of people with certifications -which takes time, money and commitment- yet you conclude that everyone is for a quick buck.

      In my opinion many businesses set themselves for quick profit instead of long term gains which hurts the common IT engeneers the most. Businesses choose that route because only a few are allowed (due to weak regulations and corruption) to profit long term.

    5. Re:Why Indians Don't Contribute Much to Linux by wed128 · · Score: 1

      I can't speak for india, but i just graduated with a Computer Engineering degree from a public university in the US (PSU) and we used almost all Solaris.

  34. Re:Oh please.... by Freed · · Score: 1

    Who cares? People who need Torvalds to think for them. One problem is the first name convention which has the effect of elevating him to somebody special. Impartial people should only use "Linus" by itself only when it would be appropriate for anyone else. Another problem are the contradictions in his widely publicized opinions. E.g., on the one hand, on other occasions he likes to hold up kernel development as akin to science. OTOH, he and his fanboys tout his blunt style as sometimes encouraging strong rebuttals, as if progress requires a blunt style. That's not at all borne out in the history of science and engineering.

    Another problem with his blunt style is how what he considers good is synonymous with what he considers good for the kernel: e.g., git is good for the kernel, therefore, Torvalds concludes, git is the best. It is very likely that at this point, other considerations make other RCS's better than git for the vast majority of projects. Another example is how the GPLv3 prevents something that Torvalds supports--Tivoization. Therefore, he claims, GPLv3 is worse than GPLv2 for the kernel, and thus, he falsely concludes, GPLv3 is worse than GPLv2 in general. GPLv3 may very well be worse than GPLv2, but the only people for whom he has observed it to be true, are those who believe that Tivoization of the Linux kernel should be allowed. But Torvalds always tries to elevate that group to somehow matter more than others.

  35. Re:Site is slashdotted by Shados · · Score: 1

    Actually, one of SQL Server's best feature compared to most RDBMS is performance. I mean, for enterprise level operations (read: not just serving semi-static wiki-style data), there really is only Oracle that can pump something faster (maybe DB2?), and not even close to doing so in all scenarios, so...

    The dev tools, are another story :) "Minimum requirement: Intel Core 2 Quad * 2, 16 gigs of RAM..." or something.

    Though the above error message is almost surely a stupid programmer error, as someone else already pointed out...

  36. Linus admits he's a troll by Anonymous Coward · · Score: 5, Funny

    I like making strong statements, because I find the discussion interesting.
    Isn't that another way of saying "I am a troll?"
    1. Re:Linus admits he's a troll by Per+Wigren · · Score: 1

      I like making strong statements, because I find the discussion interesting. Isn't that another way of saying "I am a troll?" Well, he actually does sound like the Moomin troll, at least when he speaks Swedish.
      --
      My other account has a 3-digit UID.
    2. Re:Linus admits he's a troll by just_another_sean · · Score: 1

      Sure, he's a troll, but he's a benevolent troll. ;-)

      --
      Creationist Textbook Stickers Declared Unconstitutional by CowboyNeal
  37. It's not that he has slammed SVN... by Anonymous Coward · · Score: 0

    He has slammed the practicality of SVN within the Linux project. And the Linux project is a highly unique project. It is worked on by thousands, used passively by millions, it is the subject of constant experimentation (branches), it has no commanding leadership, etc. It needs a version control system which can handle that.

    SVN is fine where there is a central command to control all the source (this is true in all corporate use and most projects in general), people can be assumed to be network connected while accessing the repos (true in corporate use), and there isn't a lot of experimentation / branching (true in corporate use and most projects).

    Every time he's slamming SVN he's slamming how unacceptable it would be for Linux, not saying that it's some curse on the universe. It's a different tools for different jobs thing. I think he's right. And for everything I do I'll continue to use SVN because it's great for the roles I need it for. These are all typical corporate style projects where I want central control of everything, we have a project plan so there isn't a lot of need for branching, etc. SVN is great for that and I don't think Linus would say otherwise.

    ----------------
    Web application development

  38. Not only good, but also easy enough! by Tom · · Score: 3, Insightful

    He's right about Subversion, but he misses one point:

    Putting your project in a Subversion repository takes an hour or two, maybe half a day if you're an idiot. Setting up an arch repository took me at least twice as long. Explaining how to use arch to developers who hadn't worked with it before is an order of magnitude more difficult than explaining Subversion to developers who haven't worked with it before.

    Subversion is "good enough", but it's also simple, straightforward and frankly if you have anything that goes beyond a very simple project or where more than one person is involved, I can't think of many reasons to not put it into a Subversion repository.

    I still like arch more for the concepts. But I don't use it. I might look at git one of those days, if I have a need Subversion doesn't address.

    --
    Assorted stuff I do sometimes: Lemuria.org
    1. Re:Not only good, but also easy enough! by __aawkdb2598 · · Score: 1

      Putting your project in a Subversion repository takes an hour or two, maybe half a day if you're an idiot.
      Oh really? I must be an idiot then. Because I just converted a large (~4GB) and very old (some of the code in there dates ~25 years back) repository from CVS to SVN using the appropriately named "cvs2svn". It took me more than a day to adequately straighten out a bunch of the problems with the old, crufty repository that couldn't adequately be translated into SVN, make all the decisions on ambiguous cases, etc. Then the repository conversion took 9 hours. And I don't *think* that had anything to do with me being an idiot...
      That might not have been what you meant, but you should consider blanket statements like that before you make them.
    2. Re:Not only good, but also easy enough! by orcrist · · Score: 1

      That might not have been what you meant, but you should consider blanket statements like that before you make them.

      That's not only probably not what he meant, it's not what he said either, unless you're trying to contort the statement "put your project into X" into "migrate your project from Y to X". So, yeah, the charitable interpretation of your post is: you're an idiot; the more realistic interpretation is: you're a dick.
      --
      San Francisco values: compassion, tolerance, respect, intelligence
  39. Re:Site is slashdotted by Skapare · · Score: 1

    No. They are just using some bad methodologies for updating the database each time an article is read. Given the variety of places I see errors happening, it appears they are hitting the database many times over the course of constructing one page, and are updating something in the database for each one of those hits in a way that requires a transaction lock. They'd have the same problem on a database run on Linux if they don't change the way they use the database. It's an architecture design problem.

    --
    now we need to go OSS in diesel cars
  40. So negative by Seven001 · · Score: 3, Insightful

    Perhaps slightly off topic, but I realize now that I'm always compelled to read stories with Linus' name because I'm a fan (not fanboy) and user of Linux. However, the man never seems to have anything positive to say. Really, is his opinion all that relevant anymore? Of course he will always be somewhat relevant due to the fact he is pretty much in charge of the kernel and contributes heavily to it, not to mention the trademark holder of Linux, but in the end he really has to answer to the community. He has to know he can't ever bite the hand that feeds him or people will go other directions.

    I'm not trying to troll or insight a flame war, I'm just saying his curmudgeonly ways are getting a bit old already. At some point I imagine him being viewed as the Dvorak of Linux. Anyway, I'll understand if I get modded down, I just wanted to put my opinion in even if it's not worth much.

  41. well, here's my take on the Linux kernel by m2943 · · Score: 1, Interesting

    The Linux kernel is, I think, a classic case of 'good enough'. It's what people are used to, and it's 'good enough' to be used fairly widely, but it's good enough in exactly the sense DOS and Windows were 'good enough'. Not great technology, just very widely available, and it works well enough for people and looks familiar enough that people use it.

    1. Re:well, here's my take on the Linux kernel by m2943 · · Score: 2, Insightful

      It is probably the most advanced and stable kernel out there.

      What kernels do you actually know?

      Why do you think it owns a lot of high end film production? ILM, Pixar and more. It is used for many super computers and kinda owns clustering.

      Well, the Linux kernel is used in all those areas because they don't need a lot of advanced features; in some of them, complexity is downright harmful. In fact, there are few applications that do. That's why a simple, open source kernel with lots of drivers does the trick.

      That's why Linux is so successful: it's simple, it's limited, and it's good enough. Furthermore, the kernel and its maintenance are so byzantine that it simply can't be changed quickly, which is something the market likes (kind of like the market also usually likes it when the US government is deadlocked).

    2. Re:well, here's my take on the Linux kernel by PenGun · · Score: 0, Troll

      So tell me what you are talking about. What example of an advanced kernel would you give? VMS, Slowlaris, IBM's mainframe hypervisor stuff ... do tell. Let me guess ntoskernel .... wmHahaha.

    3. Re:well, here's my take on the Linux kernel by m2943 · · Score: 1

      All of the kernels you list are commercial and technologically.

      If you want to see what's been happening in OS kernels since the 1970's, go read the CS literature.

    4. Re:well, here's my take on the Linux kernel by PenGun · · Score: 0, Troll

      So as I suspected ... you have no idea. Your English is pretty strange too.

    5. Re:well, here's my take on the Linux kernel by Anonymous Coward · · Score: 0

      So as I suspected ... you have no idea.

      As I was saying: go read the literature if you want to know about post-UNIX OS research.

      Your English is pretty strange too.

      It's called a "typo"; keep trying, perhaps even you will be able to deduce the missing word.

    6. Re:well, here's my take on the Linux kernel by PenGun · · Score: 1

      It's called a "typo"; keep trying, perhaps even you will be able to deduce the missing word.

        K ... I'mm unable to guess the next word in:

      "All of the kernels you list are commercial and technologically." well stupid or what?

        I know quite a bit about modern hardware and software. That is why I'm baffled as to what you mean. You make no sense. What are you some disciple of Tanenbaum come to diss me over the lack of microness in the Linux kernel.

        You are a troll pokey. You have no idea what a kernel is even for ... do you? Just typing shit so you can be on slashdot. You got something to say ... say it. I got all night.

    7. Re:well, here's my take on the Linux kernel by PenGun · · Score: 1

      Wow the moderation here is rapidly deteriorating. Having spent a large part of my /. interaction at 0 it's no big deal but the level this is now at is actively hurting the site. Which also is no big deal to me.

    8. Re:well, here's my take on the Linux kernel by m2943 · · Score: 1

      What are you some disciple of Tanenbaum come to diss me over the lack of microness in the Linux kernel.

      Microkernels are only one of the many things that have happened in kernels. There has been a lot of work on static type safety, verification, adaptivity, componentization, message passing, object-orientation, new security techniques, and many others.

      You are a troll pokey.

      No, the "troll" is Linus, I merely used his words, which happen to fit the Linux kernel just as well as they fit Subversion.

      I got all night.

      Well, yes, evidently you have nothing better to do.

  42. Re:Oh please.... by Bloater · · Score: 1

    Linus Torvalds has managed one of the most successful software development programmes ever witnessed and, with git, has sped development up by 2 times or more on the most complexly structured, most variable development team I've ever heard about.

    If all you do is democode then Linus doesn't matter, for everybody else his opinion really counts.

  43. Just a student with homework by JohnQPublic · · Score: 0

    Look at what he says: "I am developing an application for PDA and require a light-weight browser for it..."

    ie. his boss has told him to find something they can steal.

    Nope, he's coming from iiitb.ac.in - the Indian Institue of Information Technology's graduate school in Bangalore. He's trying to avoid doing his own thesis work.

  44. Complexity should be ignored... by Anonymous Coward · · Score: 1, Insightful

    "For very complex systems, it is insane to require an user to know the meaning and default setting of every parameter, even if the user is an expert."

    Then why is an "expert" fooling around with a "complex" system? Maybe there should be "novices" operating "simple" systems so no one goes "insane".

    "Do you know the default setting of every parameter used in the fuel injection system in your car? My guess is that not even the technician at the car repair shop does. He trusts them to be sane.
    Does the pilot of an airplane know the default setting of every parameter in the flight control system? Not even the pre-flight checklist covers them all. He just trusts them to be sane."

    Your examples suck dude. If we were discussing OSS software? You can bet there would be a crowd that would demand you know every parameter of every system and memorize the source code to boot. And calling you a MSCE if you don't.

  45. Re:Linus isn't "Good Enough" by Anonymous Coward · · Score: 1, Interesting

    I think that Linus doesn't really care about Linux competing in the market place.

  46. Not only good, but also easy enough!-Images. by Anonymous Coward · · Score: 0

    Well I see one problem with all of them. They don't work with image-based languages. i.e. Squeak.

  47. No by Anonymous Coward · · Score: 0

    He's a sanctimonious a-hole. The kind that doesn't feel guilty about it either.

  48. In other words by Anonymous Coward · · Score: 0

    GP: The average IQ is 100.
    Parent: I am not so sure about that. I once met a guy with an IQ of 125.

  49. Logical copies by CustomDesigned · · Score: 1
    Proper tagging: a specific snapshot is marked with a name, only metadata is added to the repository. Improper tagging (SVN's hacked way): the whole repository is duplicated.

    I thought the repository was only *logically* copied. Only the differences are actually stored.

  50. And git is even easier by Chemisor · · Score: 1

    > Putting your project in a Subversion repository takes an hour or two

    Indeed. And putting your project in git takes maybe 30 seconds:
    cd project
    git init
    git add .
    git commit

    Takes a few more minutes if you want to put it on a public repository:
    Go to repo.or.cz and register the project (fill out one short form)
    (why aren't there more hosting sites? SourceForge flat out refuses to offer git hosting...)
    Add public target url to .git/config
    git push --all public

    Having only recently switched to git from subversion, I'm still in the state of pure awe at how much easier it is to use...

    1. Re:And git is even easier by CryBaby · · Score: 1

      That list of commands -- while trivial -- is actually more work than right-clicking my project in Eclipse and selecting Team->Share Project. So, I think the "ease of use" argument works in Subversion's favor until Git has better IDE support.

    2. Re:And git is even easier by swillden · · Score: 1

      That list of commands -- while trivial -- is actually more work than right-clicking my project in Eclipse and selecting Team->Share Project. So, I think the "ease of use" argument works in Subversion's favor until Git has better IDE support.

      Not really. The only part of that list that "Team->Share" does for you is the "git add". You have to have already set up and configured your subversion repository, and after "Team->Share" you still have to go do the commit. Not to mention the fact that Eclipse makes handling "conflicts" harder than it is with the command-line version of any major tool (including CVS) and that Eclipse's handling of branch merging is so bad as to be dangerous. I use Eclipse with both CVS and Subversion, and I find I often fall back on the command-line tools because they're simpler and safer.

      --
      Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
    3. Re:And git is even easier by Tom · · Score: 1

      That assumes that the repository is already there. If that's the case, svn is just as trivial.

      I was talking about the regular case - a remote repository that you have to set up first. I don't know about git. I know it was a hassle with arch. Disclaimer: That was two years ago, things might have improved since then.

      --
      Assorted stuff I do sometimes: Lemuria.org
    4. Re:And git is even easier by Chemisor · · Score: 1

      > That assumes that the repository is already there.
      > was talking about the regular case - a remote repository that you have to set up first.

      No, it doesn't. The commands I listed create the repository. The misconception here is that git does not require you to have a remote repository; yours is as valid as any other. Under the git development model you don't have a central repository, you just publish the one you have. I would start a project with a local repository, hack at it for a while, and then, if I wanted to share it with someone I'd push it to a public site like repo.or.cz. The push does take some setting up, since you need the site owner's permission, but no more difficult than, say, publishing a web page.

      The fact that you don't have a central repository is a very important advantage to a single developer. If you work under svn privately and want to publish your project on a public site like SourceForge, you have to pack up the repository and upload it there. From then on you are tied to SourceForge and are forced to be online whenever you want to commit or examine history. With git, nothing changes when you publish a repository. Your workflow is exactly the same, since the published version is just a copy; you still own the master repository. If SourceForge goes down, it doesn't affect you much.

      One last thing is the space savings. In subversion every checkout has two copies of every file and pollutes your source tree with .svn subdirs. With git, your local repository with your checkout take up less space than a single svn checkout, with no .svns to pollute your tree (which cause problems, for example, if you want to search all your source files for some string)

    5. Re:And git is even easier by TheRaven64 · · Score: 1

      > Putting your project in a Subversion repository takes an hour or two

      Indeed. And putting your project in git takes maybe 30 seconds:
      cd project
      git init
      git add .
      git commit
      For reference, doing the same thing with svn is:

      $ cd project
      $ svnadmin create /path/to/repository
      $ svn import . file://path/to/repository
      $ svn commit
      I'm not entirely sure how this would take someone an hour or two, unless they created the repository on a remote machine and had a very slow network. In this case, the steps with git would be longer, since you would also be cloning the repository on a remote machine, which would take a similar amount of time.
      --
      I am TheRaven on Soylent News
    6. Re:And git is even easier by Tom · · Score: 1

      The misconception here is that git does not require you to have a remote repository; yours is as valid as any other. Under the git development model you don't have a central repository, you just publish the one you have. You still have to publish it. In fact, my "remote" Subversion repository is local, too - to the one machine it is on. No matter if SVN, arch or git, you still have to publish it. That means configuring whatever daemon is listening for inbound connections, setting up the firewall, creating user accounts, whatever.

      The difference between centralised and distributed isn't in the work to set it up. Or rather: If anything than a centralised repository is easier, because you only have to set up and run one server.

      And, of course, on the client side Subversion has much better support. Point me to a stable git bundle for TextMate and I'll check git out.
      --
      Assorted stuff I do sometimes: Lemuria.org
  51. A slashdotting would not be pleasent. by Anonymous Coward · · Score: 0

    "Thats what i would do if I had my site running on Microshit stuff."

    Pfft! The only way your site would get any hits is if the server was placed in the middle of the freeway.

  52. Re:So negative: Think so? I don't... just opinion! by Anonymous Coward · · Score: 1, Interesting

    "However, the man never seems to have anything positive to say. Really, is his opinion all that relevant anymore?" - by Seven001 (750590) on Sunday August 19, @01:37PM (#20286737)

    He's VERY relevant, & in 1 regard (imo, @ least) - because Mr. T. holds the dev team to a fairly 'small' (purely relative term) on the CORE development, & the kernel of the LINUX(es) in HIS control?

    SMART!

    Imo, Linus T. keeps what happened to UNIX's from happening to LINUX - fragmentation, SO bad, that one binary on 1 version of *NIX won't run on another version of *NIX...

    I.E.-> IMO? Mr. T.'s control @ the "kernel/core level" of the Linux OS helps (partially @ least) to keep Linux from splintering into a "bunch of warring factions" that cannot "get along" basically...

    & THAT is what happened to UNIX in general!

    (E.G.-> Between Bell Labs original & say, BSD variants (this particular *NIX variant case in particular bugged ME recently - I saw that the multiplatform CIS TOOL (a security benchmark) would run on FreeBSD, but not OpenBSD... though they come from the SAME BASE CODETREE (Berkeley code)), Solaris, SCO, HP-UX, IBM AIX, Linux etc. et al...)

    Imo? Guys, today??

    We should ALL have been running some form of UNIX on our PC's, but this 'war for domination of the PC OS market' (for lack of a better expression on my part, but this WAS what it was no doubt about it between various *NIX vendors on ALL hardware platforms) did THAT concept, right in...

    Good opening for Bill Gates & crew, really...

    They took the biggest share of the market, with inferior OS @ the time no less, in DOS, & even later in Win3.x/9x! UNIX & Os/2 were technically superior... IBM ditched out on Os/2 imo, & UNIX vendors could NOT agree on std.'s & a unified point of control (& thus, today you have what you have, between *NIX's: binary incompatibilities)... Linus T. stops that for Linux @ least.

    However/today? Windows NT-based ones ARE DEFINITELY "on par" with any *NIX, & better in many respects (including device driver capability, more refined applications base, & probably larger than on *NIX in general + of higher quality & compatibility with the majority of users out there & what tools they use, & overall development for the Microsoft Windows NT-based OS platform (where the MONEY IS MADE TODAY, mostly - & money? TALKS LOUD! They say, "talk's cheap", but... not when money does the talking!))

    Money... it spurs developers & companies to create product, more than anything imo, because we all have to eat/make bills/plan for our future & those of our family etc. (big motivator).

    All in all? L.T. & the folks working on Linux are good people, who must REALLY believe in what they're doing... they kept @ it, to compete with Windows, where even HUGE CORPORATIONS LIKE IBM, who had Os/2 which WAS a 'better DOS & better Windows' & better OS period, than Win3.x by a LONGSHOT, gave up.

    Pretty impressive that, imo @ least.

    I personally think Mr. T. is positive on many notes, very thoughtful, and very, VERY intelligent... from a number of his statements in said interview in fact.

    My fav. being this one:

    "Linus: I've never been much of a visionary -- instead of looking at huge plans for the future, I tend to have a rather short timeframe of 'issues in the next few months'. I'm a big believer in that the 'details' matter, and if you take care of the details, the big issues will end up sorting themselves out on their own"


    Because, that man's RIGHT AS RAIN & you can tell he is of a developer's mindset: The "devil's ARE in the details"...

    Without working on them? YOU CANNOT SOLVE THOSE 100,000 foot view visions/problems others have. Every BIG problem, has its roots in MANY smaller ones.

    AND, largely imo?

    Well, & others MAY disagree with me here:

    I think ANYONE can 'do the broad strokes' & spot a problem or whatever...

    HOWEVER

  53. Re:Oh please.... by Anonymous Coward · · Score: 0

    "Linus Torvalds has managed one of the most successful software development programmes ever witnessed and, with git, has sped development up by 2 times or more on the most complexly structured, most variable development team I've ever heard about." - by Bloater (12932) on Sunday August 19, @02:22PM (#20287033)

    Excellent reply... I could not have said it better myself:

    http://linux.slashdot.org/comments.pl?sid=273761&t hreshold=-1&commentsort=0&mode=thread&cid=20288395

    (You said what I was trying to say in the URL above in this very post, albeit myself being perhaps overly detailed + verbose, in a shorter number of words)

    APK

    P.S.=> "Mr. T." as I affectionately call L.T., per the URL above (just as I call Mr. Bill Gates "King Billy", respectfully, not in mockery)?

    Imo, @ least?

    He's a rare type of guy: He can function @ the "devil's in the details" levels, as well as the mgt. "plan ahead/visionary levels", though he tries to downplay it... he does well on BOTH fronts! Linux surviving "unfractured" @ binaries compatibilities levels has a LOT to do with HIM (and the devs of KDE/GNOME & their Qt/GTK usermode code toolkits too)...

    That (incompatibilities between *NIX variants @ binaries levels) is, imo @ least? Is what KILLED UNIX on the PC platform...

    I.E.-> Too many incompatibilities between various *NIX's... AND, this is what partially kept Ms ontop for SO LONG on the converse - compatbility with past OS & software versions!

    A lesson for us all, really... in business, even MORE than computing! apk

  54. LOLLINUS by Synthaxx · · Score: 4, Funny

    (Linus with a little balloon on hovering over his head)
    "Oh hi, i shiftedz ur paradigmses."

    Paradigmses, he shifted them.

  55. Yeah.. by RightSaidFred99 · · Score: 1

    Because I've _never_ seen a MySQL error from some random online forum.

  56. Don't get your hopes up by Slashdot+Parent · · Score: 2, Informative

    Hopefully, the merge tracking being implemented for SVN 1.5 will make SVN a real/complete scource code control system. Don't get your hopes up.

    "Merge Tracking in Subversion 1.5.0 is roughly equivalent in functionality to svnmerge.py, recording and using merge history to avoid common cases of the repeated merge problem, and allowing for cherry-picking of changes." -- http://subversion.tigris.org/merge-tracking/
    --
    They don't grade fathers, but if your daughter's a stripper, you fucked up. --Chris Rock
  57. Re:Oh please.... by borgheron · · Score: 1

    For anyone who can't think for themselves, yes, his opinion really counts.

    I, personally, like to form my own opinions of things. While Linux has been seized upon by people as a great operating system. The only good thing about it is that it's free.

    Linux is a monolithic kernel architecture which, as many operating systems experts will tell you, has number of problems.

    Don't fool yourself into thinking that he's some kind of visionary, when he's not. The man never says anything positive about anyone else's work. I find it really tiring to listen to him rail on everything under the sun... speaking of Sun. Linus railed against them for not giving anything to the community.... let's examine that assertion for a minute:

    Sun has:
    1) Given it's OS out under a Free Software license
    2) Given it's Processor out under the GPL
    3) Released Open Office under the GPL
    4) Is in the process of releasing Java under the GPL.

    What else would you like them to give? Does he want them to drop Solaris and start being a Linux distributor?

    Linus poo-poo's CVS and SVN as being "good enough." While I agree that CVS certainly does suck, SVN is not a the piece of crap he thinks it us.

    He regularly criticizes RMS. I don't agree with everything RMS says, but some of the things that Linus dings him on are completely assinine. The GPLv2 was created before certain technologies existed. The GPLv3 was made to address the problems these new technologies present... and keeps with the spirit of the GPLv2. Linus is too blind to see this.

    Don't kid yourself... he's no one's hero. He's just started to believe his own press.

    Good day.

    --
    Gregory Casamento
    ## Chief Maintainer for GNUstep
  58. git vs alienbrain? by UnknownSoldier · · Score: 1

    Does anyone know how git handles compared to alienbrain?
    i.e. Can it store large binary files? (~64M+)

    How well does it integrate into Dev Studio?

    Are there any plug-ins for previewing binary files (pictures/movies/audio)?

  59. Re:Oh please.... by Bloater · · Score: 1

    > Don't kid yourself... he's no one's hero. He's just started to believe his own press.

    Nono, he's always been an arsehole. But when it comes to "herding cats" you have to listen to his experiences because you can't learn how to do what he's been doing day-in day-out for 15 years without either doing the same or fastforwarding by learning from his time doing it.

  60. Err ... Microsofties incompetent? by golodh · · Score: 1
    Err ... as much as I dislike Bill Gates' hyper-agressive way of doing business, and detest Microsoft's marketing practices and general dishonesty ... I think I should give ole Bill credit for being really sharp.

    First of all: by all accounts he was an extremely good programmer. To the point where the joke in Redmond was: "Can't hack it? Give it to Bill, he'll program it in Basic over the weekend." Well ... there are other very good programmers, and not a few who are better than Bill, but as far as I understand, Bill was also very good at helicoptering between programming detail and marketing significance. There aren't many who can do that.

    Secondly he spotted the main chance and succeeded in grabbing it. Not so much as a visionary, but as someone who carefully listens to what people have to say ... in case they say something that he can use. Personally I think this is reflected in Microsoft's "tail light chaser tactics".

    I think we can agree that although Microsoft hardly ever came up with any *conceptually* new software (except perhaps Clippy the Office Assistant ... may he rest in peace forevermore}, it tended to buy good ideas and usually succeeded in turning those into software that people wanted to buy. Because it was cheaper than the competition, fairly intuitive to use, and "good enough".

    Now that *sounds* easy ... just spot a good idea and do it better. But the industry is awash with people who had a good idea and slipped up because they missed some detail along the line and continued not to spot the problem until it was too late. Like e.g. IBM's micro-computer division to IBM's PC operating system division to the WordPerfect Corporation to Borland to Lotus to Ashton-Tate. All of them had success, and woke up too slowly when things went subtly wrong for them. In most cases that "something" was Microsoft coming up with a competing product (whether home-grown or bought}.

    You can't pull something like that off without a very clear perception of where things stand and where they're moving. I think that that is an area in which Bill excelled.

    Remember when Microsoft threatened to miss the boat on this thing called "Internet"? Remember how a certain Billg first refused to see it, then suddenly did, and then made his company turn on a dime and go all-out for Internet functionality? He later admitted that he'd seen the new development too late ... but he did catch on in the end, and long before many other captains of industry. And when he did, he took the right action.

    That's what I mean. How many big bosses are perceptive enough to spot when they're barking totally up the wrong tree, and objective enough to switch trees? That's what I think we should credit him for. Regardless of anything else.

  61. Re:Site is slashdotted by greenfield · · Score: 1
    Next time I should consider adding a smiley face.... So much for my attempt to make a joke.

    It is funny to have four comments on a post marked as "Redundant"

    --

    --Sam

  62. Game Over, Man.... by El_Oscuro · · Score: 1

    By providing such useful information about the site design in a simple exception, the site is already Pwn3d. Unless the site is really running RHEL with Apache and an error page script that generates messages like this to mess with hackers. Not that I would know anything about using this technique ;)

    --
    "Be grateful for what you have. You may never know when you may lose it."
  63. Solaris Desktop by fm6 · · Score: 2, Interesting

    The Linux desktop is just so much better than what traditional Solaris has, and I expect Solaris to move more and more towards a more Linux-like model there.
    Linus seems unaware that the preferred desktop on Solaris is now a rebranded version of GNOME.
    1. Re:Solaris Desktop by MythMoth · · Score: 1

      I seem to recall reading that he prefers KDE to Gnome though.

      --
      --- These are not words: wierd, genious, rediculous
    2. Re:Solaris Desktop by Xybre · · Score: 1

      Yeah, but have you used their desktop? It's hideous. I love Solaris and all, and I don't recall Gnome sucking as much as the Solaris re-brand, but since my choices are their versions of Gnome and CDE, I'd have to say I agree that Linus has a point, Solaris isn't a strong Desktop contender right now. (leaving out Nexenta of course)

      --
      Eternity is a time bomb.
    3. Re:Solaris Desktop by fm6 · · Score: 1
      If by "hideous" you mean "a pain to use", I certainly agree. But Linus didn't say, "Solaris has a lousy desktop". He said:

      The Linux desktop is just so much better than what traditional Solaris has, and I expect Solaris to move more and more towards a more Linux-like model there.
      If by "traditional Solaris desktop" he means CDE or OpenWindows, he's right. But both these desktops are deprecated in Solaris 10, in favor of JDS, which is a rebranded GNOME, which originated in Linux.
  64. From someone who's actually used git... by robertchin · · Score: 1

    I used git for about three weeks at work, importing the entire SVN repository at work into git. It was pretty nice having the entire repository history on my local machine, and I was able to do cool stuff like running a blame on the entire repository and finding out who was responsible for what percentage of the code base -- and running this was pretty fast (it would have taken forever on a traditional source code control system like subversion).

    I used the git-svn bridge, which allows you to use a subversion repository to sync into your local git repository, so that everyone else can use subversion while you use git and merge back and forth. This worked really well, and merging things was extremely easy, like Linus says.

    Unfortunately the biggest problem with git, at least for a group with a fairly structured development process (i.e., everyone commits into the same main repository) is that git has no sense of a timeline. Well, actually, it does, but you have to use this GUI tool to view where branch merges and such happen so you can figure out what hash to pass in when you want to check out a specific associated subversion revision number. Part of the advantage of subversion is that the revision numbers increment, and it's easy to tell if you have a file that is from an older revision along with some other directories checked out from a newer revision. Another advantage is that it's a lot easier to type in a revision number (which is usually some five or six digit number) than a SHA-1 hash. For example if a bug happens in revision 56384, I can tell a coworker to update to 56384, and that's easy. This is a lot easier than yelling across the hallway, "it's in 832e76a9899f560a90ffd62ae2ce83bbeff58f54." This would require an IM or an e-mail at the least.

    In general I think a lot of projects have a timeline where code develops and becomes better and more complex, and most developers want to have the latest source. In these situations git is just very difficult to deal with, because it is not really designed with this idea in mind.

  65. Just "Linus"? by MilesAttacca · · Score: 1

    I love how Slashdot is the kind of site where one can refer in a subject *and* the article summary itself to just "Linus" and we all know who the person's talking about.

    --
    98% of America's teens drink alcohol, smoke, and have sex. Put this in your sig if you like bagels.
  66. 386BSD and licensing by marcovje · · Score: 1

    From what I recall as both a Linux and BSD hack at the time, the boost to Linux was the earlier addition of an IDE interface, not licensing. BSD required a (more expensive and thus more rare) SCSI controller for much longer which limited the number of users (which then had some effect on developers).

    Same for partitioning, to this day BSD still requires a primary partition, which means potentially more trouble for users to install.

  67. Needs NOLOCK hints by giafly · · Score: 1

    [Microsoft][ODBC SQL Server Driver][SQL Server]Transaction (Process ID 128) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
    The Joys Of NOLOCK and ROWLOCK http://www.4guysfromrolla.com/webtech/101100-1.sht ml
    --
    Reduce, reuse, cycle
  68. ... bye bye karma ... by tomstdenis · · Score: 1

    Just a question, not trying to flame really, but why does anyone care what Linus thinks? I like using OSS, I wrote OSS libaries myself. But honestly, why should I care what Linus thinks? It's a community effort. Not like he wrote the entire kernel, let alone 100s of libraries I use each day.

    --
    Someday, I'll have a real sig.
  69. great comment... by naChoZ · · Score: 2, Insightful

    I like his comment about "rotating" media. What a disdainful term that will become. It immediately made me picture my nine-yr-old son teasing me in 10 years because I still have stuff on my lame rotating media.

    --
    "I can be self-referential if I want to," said Tom, swiftly.
  70. Re:"use git as if it were centralized" by Lord+Bitman · · Score: 2, Informative

    Please correct me if I'm wrong, but when I first looked into git, I was left with the impression that there was /no way/ to use git as if it were centralized: every user had to have the full history, even if 99.99% of that history was irrelevant. I recall reading something where Linus noticed that if everyone used git with full history, they would all wind up with needlessly huge local copies. His solution: rather than fixing this obvious flaw in git, he chose instead to simply not import old version information. Did I read this wrong? Has something changed? These are not rhetorical questions, I have asked them previously and have yet to receive an answer. I just don't know. Why is git superior when it seems that it was fundamentally incapable of handling the full depth of the very project for which it was written?

    My goal of a "perfect" version control system is one that is decentralized, but lets me decide how much history I want, and lets me decide if something is so old as to be irrelevant, not worth having locally. If older versions can be discarded without impacting day-to-day work, why have I not seen this as an option for any decentralized systems?
    It is one of those "seems obvious enough to me that I am probably just using the wrong keywords in Google" things.

    SVN lets me check out just the "most recent" copy, and I can pull whatever I need from the remote repository if I need it.
    git, from what I've read, does not.

    I am not trying to be arrogant here, I would love to be corrected. Given history of other times I've asked this question, I don't expect to.

    --
    -- 'The' Lord and Master Bitman On High, Master Of All
  71. Re:"use git as if it were centralized" by smenor · · Score: 1

    To the best of my knowledge, you are correct that every Git user has the entire history.

    This is really a non-issue, though. Storage is cheap and the history doesn't take up that much space.

    The 2.6 kernel takes about 285MB and the entire 2 year history is about 187MB. The initial release was in 1991 - 16 years ago. Assuming 187MB every two years (which is certainly a gross overestimate) that's still less than 3GB. Not exactly small, but not obscenely huge either by today's standards. But it's not even that bad. You can get the entire kernel bitkeeper history here in under 200MB (which is still comfortably smaller than the kernel, itself).

    The repository size wasn't even the reason that Linus gave for not importing the history. If memory serves, I believe it was more of a technical issue of correctly importing the history from bitkeeper and patches.

  72. I love Linus as much as the next geek. by pclminion · · Score: 1

    But here's an honest question.

    If a person refuses to use a given technology, how can he meaningfully criticize that same technology? Give me a guy who's been using CVS for a decade and wants to vent, and I'll listen.

    1. Re:I love Linus as much as the next geek. by Anonymous Coward · · Score: 0

      Linus mentions in the Google video that he has used CVS for 7 years (at transmeta).

  73. Re:"use git as if it were centralized" by Lord+Bitman · · Score: 2, Informative

    a brief googling reveals hard drive space was not the issue - it was bandwidth. My point is more related to archives in general, not the linux kernel itself, though (that Linus chose not to put the whole tree into git I still think is very telling, though). My primary concern is: if it wasn't worth it to have 3-year-old history THEN, why not three years from then? It just seems like a fundamental design issue that I've never heard explained other than "hard disks are cheap and bandwidth is infinite nowadays!", which is an outright lie and pretty much just says "git: not meant to be portable"
    Perhaps I use SVN in situations where something simpler would suffice, but I /like/ to be able to check out/in from resource-limited systems without resorting to YetAnotherTool.

    mostly, though, it's just the idea of "we don't want to import 3 years of history, it's not worth it right now" + "And this is good for the long term!"

    --
    -- 'The' Lord and Master Bitman On High, Master Of All
  74. Re:"use git as if it were centralized" by smenor · · Score: 1

    Any chance you could post a link to something that says that Linus didn't import the entire history because of bandwidth issue? Everything I could find seemed to suggest it was just the difficulty of importing the history. This really matters because If it was a technical issue, then your argument loses quite a bit of its potency.

    I understand that you were speaking about archives, in general, but the kernel is a great test case considering its size and its rate of development.

    You're more than welcome to use SVN if it suites you. Makes no difference to me one way or another. Heck - I still have to use it for some projects myself because integrated Eclipse support isn't there yet for Git.

    All I'm saying is that you shouldn't discount Git out of hand just because of some perceived issue of bandwidth and storage without trying it out for yourself. If you're working on something modestly sized (on the order of a few megs), you could realistically do it over dialup (I wouldn't envy you, but you could do it... though, if you're the sort of person who needs version control, it seems unlikely that you'd be stuck with something as slow as dialup)

  75. Re:"use git as if it were centralized" by Lord+Bitman · · Score: 2, Informative

    This was very quick googling, of the type "I think I remember reading something like...", typing "linus git kernel import", and clicking until I found something similar to my memory, total time 20 seconds:
    http://kerneltrap.org/node/5014

    Just because I'm the type of person who uses version control and often have access to high-speed internet and large hard drives doesn't mean I'm /ALWAYS/ in a situation where I have a lot of bandwidth and hard disk space at my disposal. When I'm in a resource-limited situation, I still like to be able to check in/out, do other "what went wrong?" type of things without using a second system.

    As for "give it a try", I did, but very early in its history so I don't think enough niceties were there at the time.
    Mostly, it comes down to: sometimes my SVN repository grows very quickly due to all the sometimes unneeded history. There's no "svn obliterate", so we just put up with it. This causes (actual, not hypothetical) storage issues even with centralized version control. I wouldn't want to multiply this problem by the number of developers, while adding bandwidth issues previously not dealt with because some things they just didn't care about, just to allow them access to histories /when they wanted it/.

    --
    -- 'The' Lord and Master Bitman On High, Master Of All
  76. Re:"use git as if it were centralized" by smenor · · Score: 1

    Thanks for the link. I agree it's pretty sad if that was a primary motivation for not importing the whole tree. Fixing that seems like it might take a significant redesign (although I imagine that there's a way that you could automatically merge incomplete histories).

    It occurs to me that when you're in a bandwidth-limited situation (say on a trip with your notebook), distributed systems like Git might actually work better for you. When you have access to a high-speed connection, you can do the more expensive push/pull. When you don't, you can just rely on the local repository - even when you don't have an internet connection.

  77. Re:Oh please.... by WizMaster · · Score: 1

    You didn't RTFA did you? Linus doesn't state that something is better then something else in absolute terms. It's his opinion and his opinion matters regardless of what you think. He will switch to GPLv3 if it suits him but he disagrees with the philosophy of GPLv3. I happen to agree with his decision but like him, I'll use it if it's practical. If you must know, one thing he dislikes about GPLv3 is the "No DRM" type clause. I agree that that's a bad clause but it's not a big deal. He focuses more on the technological side of things. Just because some fans follow his every word doesn't mean his word is worthless. Also, not everyone that happens agrees with him or respect his opinion is blindly following his word.

  78. Re:"use git as if it were centralized" by Lord+Bitman · · Score: 1

    for situations where I'll _never_ have high-speed or (more importantly) lots of hard disk space, this doesn't work. Can I only check out certain branches without getting every branch it's related to? (or even "those which aren't technically related, but are in the same repository"?)

    Being an SVN user I am probably stuck in the mindset of not distinguishing much between branches, revisions, and directories, as far as relationships go. If I could check out only a certain "branch" without checking out what it's related to, git /could/ work for me (potentially), so long as I re-branched every now and then.

    --
    -- 'The' Lord and Master Bitman On High, Master Of All
  79. Re:"use git as if it were centralized" by smenor · · Score: 1

    Can I only check out certain branches without getting every branch it's related to?

    Absolutely.

    Actually... I almost mentioned that before but I wasn't sure that that was *quite* the solution for you (to the extent that it does help though, it's in there).