Slashdot Mirror


DTrace Becomes Usable on FreeBSD

daria42 writes "A project to port Sun Microsystems' Dynamic Tracing (DTrace) tool to FreeBSD appears to have achieved some initial success. DTrace was open sourced last year and is one of the coolest features in Solaris 10."

128 comments

  1. Cool. by grub · · Score: 3, Funny


    Now we can have Netcraft confirmation of the death with a long DTrace log to back it up.

    --
    Trolling is a art,
    1. Re:Cool. by Anonymous Coward · · Score: 0

      More FreeBSD hype for a barely working feature. DTrace is yesterday's news anyway: SystemTap is the new hotness.

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

      SystemTap is the new hotness

      Only for the worst breed of inept, disgustingly ugly Linucks-monkeys who would not even admit their OS is crap if it would be ready for the desktop.

    3. Re:Cool. by DAldredge · · Score: 1

      It would appear that SystemTap barely works, for their site.

      "SystemTap is still under rapid development, so it is not appropriate to use it on production systems."

    4. Re:Cool. by Anonymous Coward · · Score: 0

      So? You are under developed but we let you post on /.

    5. Re:Cool. by Anonymous Coward · · Score: 0, Troll

      Elegy For *BSD


      I am a *BSD user
      and I try hard to be brave
      That is a tall order
      *BSD's foot is in the grave.

      I tap at my toy keyboard
      and whistle a happy tune
      but keeping happy's so hard,
      *BSD died so soon.

      Each day I wake and softly sob
      Nightfall finds me crying
      Not only am I a zit faced slob
      but *BSD is dying.

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

      Let us know when you are using DTrace in a production system with your FreeBSD box.

    7. Re:Cool. by DAldredge · · Score: 2

      One can use DTrace in production under Solaris 10.

    8. Re:Cool. by Anonymous Coward · · Score: 0

      DAldredge can go fuck himself with his Pink Ranger Action Figure/Dildo.

    9. Re:Cool. by Anonymous Coward · · Score: 0

      Hello... FreeBSD plug/article.

  2. DTrace scripts by Life700MB · · Score: 5, Informative


    Here you got some dtrace scripts, direct from my firefox bookmarks.


    --
    Superb hosting 20GB Storage, 1_TB_ bandwidth, ssh, $7.95

  3. Linux pwn3d j00 by Anonymous Coward · · Score: 0, Funny

    Dtrace is useless, transparent xterms are the new hotness.

  4. STUB! by corychristison · · Score: 5, Funny
    This description is a stub. Please help extend it by contributing some real information!

    ... sorry. :-P

  5. Re:It is official; Netcraft confirms it: BSD is dy by antik2001 · · Score: 0, Troll

    I see... "BSD is dying" trolls are immortal... Netcraft confirms it!!!

  6. Re:NOT Open Source (was: GPL) by DrSkwid · · Score: 1, Troll

    So, let me get this right, the developers of FreeBSD, OpenBSD and NetBSD have 0 value in their work. The code they have written in will be ripped off and sold back to them, as proved by ClosedBSD, an improved BSD OS that I can buy.

    > This encourages collaboration, and thus helps the advancement of software engineering.

    Is this some sort of joke ?

    --
    There are places where the networks are not touching,and there are places where they are-Boeing's Lori Gunter
  7. Re:It is official; Netcraft confirms it: BSD is dy by Anonymous Coward · · Score: 0
    ..."BSD is dying" trolls are immortal.

    I'm sure that this stuff will be ported to DeadBSD. See DeadBSD.org for downloads and information.

  8. Re:NOT Open Source (was: GPL) by Anonymous Coward · · Score: 0, Troll

    The code they have written in will be ripped off and sold back to them, as proved by ClosedBSD, an improved BSD OS that I can buy.

    http://www.apple.com/macosx/

  9. Re:It is official; Netcraft confirms it: BSD is dy by antik2001 · · Score: 1

    http://deadbsd.org/

    Authorization Required
    Browser not authentication-capable or authentication failed.

    Ouch- my browser:
    Mozilla/5.0 (compatible; Konqueror/3.5; FreeBSD 6.1-STABLE) KHTML/3.5.2 (like Gecko)

  10. I think the GPL weenies are jealous by Dopeskills · · Score: 2, Insightful

    Sorry, but DTrace is a really great feature regardless of what your political OSS views are. Porting it to BSD only makes it that much cooler.

    1. Re:I think the GPL weenies are jealous by ThePhilips · · Score: 1, Flamebait

      The point is how useful the gathered info is. In my experience more or less all OSs do not have problems with stats one can gather. It's the stats one can NOT gather.

      E.g. under Linux most of the memory is file cache. What would you gain by knowing that cache went from 95% to 96% of RAM and then went down to 94%?If you can't dissect the value (e.g. 10% belong to that file, 20% to that process, 40% are that info, etc) nor change the behaviour of kernel - there is no point in knowing that info.

      And again, if there is tool which provides some info, there are good chances that people looked at that info and already optimized/tuned all what was possible to optimize/tune.

      Remember, problems most of the time lie somewhere we cannot look at.

      --
      All hope abandon ye who enter here.
    2. Re:I think the GPL weenies are jealous by Winter+Lightning · · Score: 4, Informative

      The whole point of DTrace is that it allows you to gather information
      that you couldn't obtain before. See some examples here:
        http://blogs.sun.com/roller/page/bmc/20040805
      here:
        http://users.tpg.com.au/adsln4yb/dtrace.html#OneLi ners
      and here:
        http://www.sun.com/software/solaris/howtoguides/dt racehowto.jsp

      Declaration of interest: I work for Sun, use DTrace, demonstrate it and
      see the expressions of stunned delight on the faces of people
      when they suddenly recognise its power.

    3. Re:I think the GPL weenies are jealous by penguin-collective · · Score: 1

      Sorry, but DTrace is a really great feature regardless of what your political OSS views are. Porting it to BSD only makes it that much cooler.

      There are lots of "really great features" you could put into an OS. The devil is in the details. What's the cost of maintaining it? What is the actual utility? Etc.

      I think DTrace doesn't come out well in that regard. Pretty much all the things people regularly want to measure already have hooks in BSD and Linux. Furthermore, if one is going to put something of DTrace's complexity and pervasiveness into the kernel, I'd like to be able to use it for other purposes as well.

      To me, DTrace is typical Sun thinking: too focused on kernel and systems issues. It's the reason I quit Solaris long ago, and I hope this sort of stuff won't infect too many other operating systems.

    4. Re:I think the GPL weenies are jealous by ThePhilips · · Score: 1

      To be frank, I needed such tool only once in my whole 15 years carrier - to prove that performance problem users where experiencing wasn't mine.

      And from the demos it looks way too complicated to be used by mere mortals. Bit like good ol' "expect": great tool, but beyond comprehension of most mere mortals. IMHO.

      Thou, I'm quite an exception. For example I do not use debuggers at all. And I do not need one - I can tell precisely what went wrong in my program by just description of the symptoms. Other (normal) guys spend 90% of their working time in debuggers. Probably normal developers would appreciate the tool.

      It's just my experience that in many case additional info on how program runs does HARM development process: people concentrate too much micro optimizations and miss completely overall performance picture.

      To reiterate classics: "Premature optimization is the root of all evil" (c) Hoare.

      P.S. The only viable application of dtrace (or any other profiler for that sake) I know is the improved communication between users and developers. With dtrace user can profile application in his configuration and then send report to developer so he can try to evaluate what/why went wrong at user's site. But again, most of the applications already have some sort of logging facility specifically for that purpose developed.

      --
      All hope abandon ye who enter here.
    5. Re:I think the GPL weenies are jealous by Anonymous Coward · · Score: 0

      I'm not sure what your "15 years carrier" means- unless you were in the Navy.

      That said- If you don't see the amazing usefulness of D-trace then you aren't doing any sort of high end administration/development. D-trace is a tool and it's damned valuable. That's you don't use a debugger at all makes me realize you've never written anything complicated. D-trace is not for mere mortals- it's for gods of administration and programming.

    6. Re:I think the GPL weenies are jealous by setantae · · Score: 1

      For example I do not use debuggers at all. And I do not need one - I can tell precisely what went wrong in my program by just description of the symptoms. Other (normal) guys spend 90% of their working time in debuggers. Probably normal developers would appreciate the tool.

      Ha ha, what a prick.

  11. Re:NOT Open Source (was: GPL) by jack_csk · · Score: 1

    Huh? Is your ClosedBSD same as my ClosedBSD?

  12. GPL != Open Source by nsayer · · Score: 5, Informative
    The GPL is not the only Open Source license. Dig your head out of the sand and see how may others there are.

    The CDDL under which the code in question was released is a slightly modified version of the Mozilla Public License. So if you used Mozilla or firefox or whatever to post that screed, then you've clearly sinned against the church of RMS.

    Oh, and the CDDL IS an OSI approved license, so that means DTrace IS (by the definition most programmers who don't wear Birkenstocks agree on) Open Source.

    As a developer, if you value your work, the GPL is the better license under which to release code, as it means no-one can take your work, close the source, and sell it as their own.

    CDDL Section 3.1:

    Any Covered Software that You distribute or otherwise make available in Executable form must also be made available in Source Code form and that Source Code form must be distributed only under the terms of this License. You must include a copy of this License with every copy of the Source Code form of the Covered Software You distribute or otherwise make available. You must inform recipients of any such Covered Software in Executable form as to how they can obtain such Covered Software in Source Code form in a reasonable manner on or through a medium customarily used for software exchange.
    So try again.
    1. Re:GPL != Open Source by cortana · · Score: 2, Informative
      The CDDL under which the code in question was released is a slightly modified version of the Mozilla Public License. So if you used Mozilla or firefox or whatever to post that screed, then you've clearly sinned against the church of RMS.
      Nonsense; Mozilla is tri-licensed under the GPL, LGPL and MPL.
    2. Re:GPL != Open Source by nsayer · · Score: 0, Troll

      I stand by my statement - Church of RMS commandment #1 is that thou shalt have no other licenses other than GPL. Tri-licensing is clearly sinful. It may not be a mortal sin, like the Microsoft EULA, but clearly the Mozilla folks have strayed off the straight and narrow.

    3. Re:GPL != Open Source by at_slashdot · · Score: 2, Informative

      Directly from the Church of RMS (http://www.gnu.org/philosophy/license-list.html ):
      ------
      This is a free software license which is not a strong copyleft; it has some complex restrictions that make it incompatible with the GNU GPL. It requires that all attribution notices be maintained, while the GPL only requires certain types of notices. Also, it terminates in retaliation for certain aggressive uses of patents. So, a module covered by the GPL and a module covered by the CDDL cannot legally be linked together. We urge you not to use the CDDL for this reason.

      Also unfortunate in the CDDL is its use of the term "intellectual property".
      ---------
      Also (http://www.eweek.com/article2/0,1895,1754155,00.a sp): "according to Mark Webbink, Red Hat Inc.'s associate general counsel. "Some of the license attributes that Sun trumpets actually have the potential of making the software not fully open," he said. "For example, by permitting a different license for the binaries, it will be possible for the binaries to have all of the attributes of proprietary code."

      --
      "It is our choices, Harry, that show what we truly are, far more than our abilities." -- Prof. Dumbledore
    4. Re:GPL != Open Source by killjoe · · Score: 1

      The Mozilla was re-licensed to be more compatible with the GPL. CDDL was very carefully written so as to prevent their code to be migrated to GPLed software. Sun is deathly afraid that their software will fork under a GPL license and that they won't be able to keep up with the GPLed coders.

      They wanted to make sure the no extra features of Solaris made it into Linux.

      Looks like it's not going to work though. My guess is that there is already a port of dtrace happening in Linux and if they get stuck there is all the BSD code that can be used.

      --
      evil is as evil does
    5. Re:GPL != Open Source by killjoe · · Score: 1

      Wow that looks like a lot of fun. Let's all make up arguments for other people and then shoot the arguments down with nonsensical rhetoric.

      You should get a patent on that idea.

      --
      evil is as evil does
    6. Re:GPL != Open Source by eviltypeguy · · Score: 2, Informative

      CDDL was very carefully written so as to prevent their code to be migrated to GPLed software. Sun is deathly afraid that their software will fork under a GPL license and that they won't be able to keep up with the GPLed coders.

      Stop spreading FUD. Anyone involved in the pilot process for OpenSolaris can tell you that those are NOT the reasons why the CDDL was created or used for SUN's code. The GPL was also one of the licenses considered.

      Personally, I think the GPL is very selfish. GPL projects can take all the BSD code or code from other compatibly licensed files they want, incorporate and improve it but the GPL prevents BSD developers from getting back most of those improvements unless the project incorprating gives them back under the original license (so it would seem anyway, someone correct me if wrong and explain).

    7. Re:GPL != Open Source by jrockway · · Score: 1

      > GPL projects can take all the BSD code or code from other compatibly licensed files they want, incorporate and improve it but the GPL prevents BSD developers from getting back most of those improvements unless the project incorprating gives them back under the original license (so it would seem anyway, someone correct me if wrong and explain).

      Whoa, whoa, whoa! That is the whole point of the BSD license, and is why many slashdotters dislike it. If you want your changes back, you would NEVER license code under the BSD license!

      This is why we have the GPL. The developer of (and community around) the software will ALWAYS get ALL changes back, and will be able to merge those changes with the mainline version of the application (no matter what).

      --
      My other car is first.
    8. Re:GPL != Open Source by NuShrike · · Score: 1

      Nope, GP is quite correct. If GPL code took from BSD code, it can only be one way. You can not inject code relicensed as GPL back into BSD because of GPL's restrictions.

      GPL by definition infects and affects code that has nothing to do with it just by simple source mixing.

    9. Re:GPL != Open Source by eviltypeguy · · Score: 1

      Whoa, whoa, whoa! That is the whole point of the BSD license, and is why many slashdotters dislike it. If you want your changes back, you would NEVER license code under the BSD license!

      Yes, but the irony is that a license about "sharing" doesn't really "share" except with itself. Incestous licensing if you ask me :)

  13. Re:NOT Open Source (was: GPL) by antik2001 · · Score: 3, Interesting

    All the code Apple borrowed from BSDs and changed is contributed back with DarWin OS. It is also the core set of components upon which Mac OS X was developed. In July 2003 Apple released Darwin under version 2.0 of the APSL license, which the Free Software Foundation (FSF) approved as a free software license. Previous releases had taken place under an earlier version of the APSL that did not meet the FSF's definition of free software, although it met the requirements of the Open Source Definition.

  14. Holyshit! by Anonymous Coward · · Score: 0

    There's actually a site called "deadbsd.org" ?!? I posted the gp as a joke. Holyshit!

    1. Re:Holyshit! by antik2001 · · Score: 1

      dead...bsd.org but I see FreeBSD live and kicking here: Telekom Malaysia Berhad Network Strategy 5th Floor, North Wing Menara Telekom Jalan Pantai Baru 50672 Kuala Lumpur 218.111.126.29 FreeBSD Apache 4-May-2004

    2. Re:Holyshit! by trewornan · · Score: 1

      It's registered to some Real Estate Company, "Windermere Technology" in Seattle, Washington. Odd domain name for a Real Estate Company to register.

  15. U send me by Anonymous Coward · · Score: 0, Funny

    U send me dtrace to hlp me do ur outsourced job plz.

    http://www.opednews.com/articles/opedne_runner_060 525_h1_b_visa_foreign_it.htm

    U hlp ur old frend 2 take ur job plz.

    Thx.

  16. HAH! by wmajik · · Score: 0

    You think this will let my employer figure out where that memory leak is coming from?! You can't trace me! I've got... TraceBuster!

    (Ok that was seriously cheesy, but I relive the golden days of my youth by quoting movies with Marky Mark apparently. *sob*)

  17. Re:NOT Open Source (was: GPL) by mccp · · Score: 1

    The code they have written in will be ripped off and sold back to them, as proved by ClosedBSD, an improved BSD OS that I can buy.
     
    Wrong. Very very wrong. ClosedBSD is a stripped down implementation of the FreeBSD kernel used for booting a machine as a router.
     
    From the ClosedBSD mainpage: "ClosedBSD is a firewall and network address translation utility which boots off of a single floppy disk or CDROM, and requires no hard drive. ClosedBSD is based off of the FreeBSD kernel, and uses ipfw as its native ruleset management system, and natd as it's network address translation utility."
     
    The BSD name is trademarked, so you won't have linux-like branches coming around that cost money. If it's BSD, it's free.

  18. Re:NOT Open Source (was: GPL) by Anonymous Coward · · Score: 1, Funny

    is contributed back with DarWin OS

    Yeeps! Don't do that! I got a horrible shiver up my spine when I read that...

  19. Re:NOT Open Source (was: GPL) by mwvdlee · · Score: 4, Insightful

    Linux already uses BSD code, so why wouldn't they want to use some more?

    I develop under both GPL and BSD licenses, based on the particular piece of code. If I think the code has strategic value (typically a library or framework), I'll develop under BSD so I can use it in any of my closed-source software too. Software which only has utilitarian value is typically released under GPL.

    GPL is of good use to a lot of projects, but IMHO it's a terrible license for frameworks and libraries. The LGPL does improve the situation for libraries somewhat, but it's won't work for all situations. That's why many "standard" libraries use more open licenses than (L)GPL; if you're not allowed to use the canonical library in all situations, it's not a useable standard.

    --
    Slashdot social media options: AIM, ICQ, Yahoo, Jabber and Mobile Text. Why no MySpace?
  20. Re:NOT Open Source (was: GPL) by DrSkwid · · Score: 1

    hehe no, I thought I was making it up !

    --
    There are places where the networks are not touching,and there are places where they are-Boeing's Lori Gunter
  21. Re:NOT Open Source (was: GPL) by QuietLagoon · · Score: 2, Insightful
    As a developer, if you value your work, the GPL is the better license under which to release code

    Isn't it up to each individual developer to decide what license to use for their original code? Isn't that what choice is all about? If I choose not to use one license or another for my code, why should you care? It is, after all, my code.

  22. Re:NOT Open Source (was: GPL) by DrSkwid · · Score: 1

    my fault, I thought I was making the name up.

    --
    There are places where the networks are not touching,and there are places where they are-Boeing's Lori Gunter
  23. Re:NOT Open Source (was: GPL) by DrSkwid · · Score: 2, Funny

    you missed the caveat : IMPROVED

    --
    There are places where the networks are not touching,and there are places where they are-Boeing's Lori Gunter
  24. Re:NOT Open Source (was: GPL) by Eivind+Eklund · · Score: 4, Insightful
    So, let me get this right, in your world you get ZERO value from utilization of code, and you get ZERO value from having people contribute changes back, ALL your value is from "not getting ripped off"?

    That's one hell of an emotional world.

    I'm glad I don't live in that world, and can be a FreeBSD developer instead ;)

    Eivind, who recognize that when people develop things based on his code, he's got a chance of getting things back, and when they choose another codebase because his is GPL-licensed, he has ZERO chance of getting anything back.

    --
    Doubting the existence of evolution is like doubting the existence of China: It just shows that you're uninformed.
  25. Re:NOT Open Source (was: GPL) by Eivind+Eklund · · Score: 1
    Apart from the public release of Darwin, we (FreeBSD) have gotten changes back from that. Not an infinite amount of changes, yet still noticable value.

    Eivind.

    --
    Doubting the existence of evolution is like doubting the existence of China: It just shows that you're uninformed.
  26. Re:NOT Open Source (was: GPL) by msh104 · · Score: 1

    I don't think any commericial distro would call itself closedbsd...
    for some reason i think it doesn't look good in your advertisement :p
    but it's still quite funny to see that it actually exists.

  27. I'm suprised... by Anonymous Coward · · Score: 0

    You didn't call it "Spinal Tap".

  28. Re:NOT Open Source (was: GPL) by foreverdisillusioned · · Score: 4, Insightful

    In a word, yes. You just need to replace "ClosedBSD" with "OS X."

    Fortunately, Apple was kind enough to open source Darwin, but it didn't need to, and it choose not to open source the Aqua UI and the Finder shell. I could be mistaken, but I don't think they would have been able to do this had Darwin been based on GPL'ed software.

    A better example of the GPL's strength would be the Linksys WRT54G router. I've got one myself and it does all kinds of awesome things it wasn't able to do out of the box (hell, you can even run an OpenVPN server on it), all because Linksys was forced to release their source code under the GPL.

    That said, the BSDs are great projects (as are public domain projects like SQLite) and I wouldn't want to see them disappear. I believe that the core focus of the OSS community should be on GPL'ed software (because "embrace and extend" does in fact happen), but there's definitely an argument and a place for BSD-style licenses.

  29. objectivity? by XiQ · · Score: 0, Flamebait
    "...and is one of the coolest features in Solaris 10."
    This is clearly an objective writer.

    (and he doesn't even say why)
    1. Re:objectivity? by lpq · · Score: 1

      "'...and is one of the coolest features in Solaris 10.'

      This is clearly an objective writer."
      --

      No, its simply putting the tool in context for you. Like saying "Internet Explorer is the coolest feature in Windows NT 5.1"... :-)

  30. You can do that under the GPL by Morosoph · · Score: 1
    I'll develop under BSD so I can use it in any of my closed-source software too.
    ...You own the copyright, after all.
  31. Re:NOT Open Source (was: GPL) by antik2001 · · Score: 1
    is contributed back with DarWin OS Yeeps! Don't do that! I got a horrible shiver up my spine when I read that...
    Calm down, this is tYpo mkEy?
  32. Re:Dtrace - is often referred to as "error vomit" by asaul · · Score: 5, Informative

    Dtrace is the exact opposite of error vomit, and I dont recall ever hearing it called that anyway. The entire principle is that you dont need to go inserting metric shitloads of debugging and printf("we got here") statements all through your code, recompile it and then see that the error doesnt occur because all your debugging has now slowed your code enough to prevent the race condition that caused the original error.

    True - its a L3 and developer tool for the most part, but there are plenty of scripts out there to show what it can do for an admin. Take a look at http://users.tpg.com.au/adsln4yb/dtrace.html for starters. Stuff like iosnoop, iotop, opensnoop and kill.d can be used quite regularly by admins without the need for putting debugging into active applications.

    --
    "If everybody is thinking alike, somebody isn't thinking" - Gen. George S. Patton
  33. Re:NOT Open Source (was: GPL) by LarsWestergren · · Score: 4, Interesting

    I dont think DTrace on FreeBSD is going to sway over and change the mind of those who use and pay and contribute to the GPL. From a strategy point of view it just made BSD's that much more competitive with Solaris and Sun offers. With the GPL you at least get some improvemnts back if your contribution is of value and nobody can close its acess.

    Well, or GPL people could take the fine contribution of the BSD people, and port it to GPL. Therefore both communities can benefit. If Sun had released it under GPL, the BSD people would have been prevented from doing this. At least that is my understanding. So in this case the BSD licence seemed like a good choice, the one that maximises freedom for developers.

    Furthermore, I believe Sun has stated that they would be happy if DTrace was ported to Linux, and though they can't pay developers to do it, they can provide other help (perhaps like the testsuites).

    Again I'm baffled by the level of hostility towards Sun on Slashdot. Here they open source an amazing tool, and help us port it, and they get a lot of nasty comments for it.

    --

    Being bitter is drinking poison and hoping someone else will die

  34. Not ready for -CURRENT? by Anonymous Coward · · Score: 4, Informative

    Dtrace is one of the best Unix development tools around, no joke. However the project is nowhere near available for FreeBSD users....

    From Bryan Cantrill's blog: "If you run FreeBSD in production, you're going to want John's port as it stands today -- and if you develop for the FreeBSD kernel (drivers or otherwise), you're going to need it."

    Now compare this to Birrell's announcement: "There is still a lot of work to do and while that goes on, the code has to remain in the FreeBSD perforce server. It isn't ready to get merged into CVS-current yet."

    Great news and nicely done... but, um, come back when it's ready for -CURRENT primetime before telling Zdnet it's ready ;)

    1. Re:Not ready for -CURRENT? by HaydnH · · Score: 1

      "Now compare this to Birrell's announcement:..."

      Also from tfa:

      According to Birrell, the FreeBSD DTrace port passes 793 of Sun's 1039 tests for the application.

      "That means that there are some very exciting traces that can be done on FreeBSD right now," he said. "Every syscall can be traced, including those that are loaded in kernel modules. Every function in the kernel can be traced from the low-level interrupts up."


      While it's not as useful as the Solaris DTrace, it certainly looks like it's ready for primetime already.

      --
      Time is an illusion. Lunchtime doubly so. - Douglas Adams
  35. Re:NOT Open Source (was: GPL) by Anonymous Coward · · Score: 0

    LGPL is the most misunderstood open source license.

    LGPL allows you to create both "derived works" and "works based on the library" and provides an option for either using LGPL or "using your own terms" for the resulting work.

    HOWEVER: if you choose to "use your own terms" then those terms MUST include certain conditions required by LGPL such as allowing reverse engineering, etc.

    I bet 99+% of coders that use LGPL libraries don't understand that their "own terms" must include certain conditions.

    In other words, "your own terms" cannot be whatever the hell you like.

  36. Maybe you should wipe your mouth after vomiting by gd23ka · · Score: 4, Insightful

    Last week I had a major problem trying to get Linux nfs4 clients to mount from Solaris 10 servers. Even though on the Linux client the domain uid mapping superficially worked (I saw the correct user/groups displayed) the NFSv4 Server Kernel Module was still using LINUX uid/gid combinations supplied by the linux client to go to the filesystem driver with to ask for permission.

    You, sir, obviously don't have the slightest clue what you're talking about.

    Here's my script, btw

    #!/usr/sbin/dtrace -Cs

    #define ACCESS4_READ 1
    #define ACCESS4_LOOKUP 2
    #define ACCESS4_MODIFY 4
    #define ACCESS4_EXTEND 8
    #define ACCESS4_DELETE 16
    #define ACCESS4_EXECUTE 32

    fbt:nfssrv:rfs4_op_access:entry {
            requested_access = ((struct ACCESS4args *) arg0)->access;
            cs = (struct compound_state *) arg3;
            cr = (struct cred *) cs->cr;
            printf ("uid = %d gid = %d\n", cr->cr_uid, cr->cr_gid);
            printf ("ACCESS4_READ = %s\n", requested_access & ACCESS4_READ ? "yes" : "no");
            printf ("ACCESS4_LOOKUP = %s\n", requested_access & ACCESS4_LOOKUP ? "yes" : "no");
            printf ("ACCESS4_MODIFY = %s\n", requested_access & ACCESS4_MODIFY ? "yes" : "no");
            printf ("ACCESS4_EXTEND = %s\n", requested_access & ACCESS4_EXTEND ? "yes" : "no");
            printf ("ACCESS4_DELETE = %s\n", requested_access & ACCESS4_DELETE ? "yes" : "no");
            printf ("ACCESS4_EXECUTE = %s\n", requested_access & ACCESS4_EXECUTE ? "yes" : "no");
    }

    1. Re:Maybe you should wipe your mouth after vomiting by plembo · · Score: 0

      Really, I don't? You sir were too busy with dreams of 3l33t points...

      Try refuting my argument instead of my catchy subject line next time. Let's review -

      1. Dtrace has got hordes of people adopting Solaris again?
      2. Its going to do wonders for BSD too?
      3. Dtrace is useful for regular IT folks, i.e. people who don't read and write C every day?

      Its just another engineer tool for engineers, and thats fine, really, but despite SUNs attempt to trumpet this tool as a revolution, no one much cares and I don't think its going to do much for BSD either. Do you think it will?

      I never said it sucks or it doesn't work. Error vomit is what some Level 3 support guys @ SUN in Bulington call it that I've spoken with, they dislike it for the reasons I've mentioned above. I didn't make that up either way so go tell them they don't know.

    2. Re:Maybe you should wipe your mouth after vomiting by cduffy · · Score: 1, Troll
      Dtrace is useful for regular IT folks, i.e. people who don't read and write C every day?

      I don't care about choosing an OS and toolkit for people that suck, I care about choosing a toolkit for me. Seriously. I'm responsible for maintaining the template that our servers (which run a *lot* of interdependent services -- Oracle, Tomcat, etc) are built off of. Finding and fixing performance problems in the template means that the low-level support folks have less angry customers on the phone -- and having the tools to find hard-to-locate issues on the deployed servers means customers' issues, once elevated, can get resolved quickly. Will the low-level support staff understand or use DTrace? Maybe not. Do I care? No. Right now I'm stuck using OProfile -- and while it's a good tool as far as it goes, I've seen what DTrace can do and I want some of that, damnit!

      Error vomit is what some Level 3 support guys @ SUN in Bulington call it that I've spoken with, they dislike it for the reasons I've mentioned above.

      They're not using it correctly, then. The whole point of folks writing scripts for DTrace is to provide the information one needs (as opposed to "vomit"). If you're using pre-canned scripts that spit out everything under the sun -- that's your problem, not the tool's.

    3. Re:Maybe you should wipe your mouth after vomiting by gd23ka · · Score: 1

      I just can't resist. I think you meant to say: If you're using pre-canned scripts that spit out everything IN the sun -- that's your problem, not the tool's.

  37. Re:NOT Open Source (was: GPL) by SillyNickName4me · · Score: 5, Insightful

    From a strategy point of view it just made BSD's that much more competitive with Solaris and Sun offers.

    Now, last time I checked, Sun regards Redhat as one of its main competitors for 'enterprise unix' systems. So, since you are saying is that due to dtrace, FreeBSD became more competitive with Solaris, doesn't that mean it became that much more competitive with at least Redhat Linux?

    With the GPL you at least get some improvemnts back if your contribution is of value and nobody can close its acess.

    What the fuck does this have to do with anything? Ah, I see, you were just looking for a reason to do some 'GPL advocacy'.. Let me make some small suggestion: Advocacy like this is just annoying the hell out of people, and makes you look like a fanatic idiot.

    Not to mention that the fud you are spreading is just that, fud. Nobody can close access to existing BSD licenced code EVER, got that? (and yes, people can derive from a BSD licenced work, and keep their source changes private while distributing the binaries. If people want to do that with GPLed code, they cannot distribute, or have to obtain an alternative licence from the authors, see the Trolltech business model)

    As a developer, if you value your work, the GPL is the better license under which to release code, as it means no-one can take your work, close the source, and sell it as their own.

    Now, the modern BSD licence only contains 2 clauses, is really easy to read, and yet you fail to understand it. You think anyone should take your advice?

    You can NOT take a BSD licenced work and claim it as your own, that is basicly the one and only thing that licence prevents you from doing. All you can do which you cannot do with the GPL is keep changes to the source private while distributing the binary result. You may believe that is bad, and you are entitled to your own beliefs there. I happen to believe otherwise, and with me, there seem thousands of people who believe otherwise, but again, that is a matter of opinion, and not a matter of fact.

    It means every change is visible to you,

    No, it does not. It only guarantees that if you get back a binary of some derived program, that you also have a right on getting the source with the changes. You have no right to see anyones changes if they decide to not distribute the result but use it for their own internal work for example.

    and that you are free to incorporate the changes other people have made to your product back into it, or into other projects you are working on.

    Not if you are for example called Trolltech (qt), Sun (OpenOffice) or anyone else who deals with dual licencing, but generally that is the idea of the GPL indeed. It is a good argument for it, despite it not always working out.

    This encourages collaboration, and thus helps the advancement of software engineering.

    The fact that all TCP/IP (ip4) implementations are mostly compatible, that most of the basic protocols used on it are compatible between vendors and such are pretty much because there is good and for any purpose usable BSD code around to implement those things, which was either used directly or used as a reference implementation to test against.

    This single tiny detail makes that there is actually some choice instead of having ended up with a proprietary network owned by either aol, microsoft, ibm or some other big entity.

    I leave it to your imagination what this means for software development.

    I will give you one more suggestion, learn to appreciate someone elses work, esp. when that work is pretty good and they actually insist on publishing that work such that everyone can use it. If you just feel that instead of appreciating such things, you must use the occation to spread lies and fud then I call you a moron.

  38. Re:NOT Open Source (was: GPL) by DrSkwid · · Score: 1, Troll

    Yeah, killing the product line of a Linux based router is definitely a win, they won't make that mistake again.

    OSX - you seem to have missed the caveat : improved.

    License wars, yawn.

    --
    There are places where the networks are not touching,and there are places where they are-Boeing's Lori Gunter
  39. Re:NOT Open Source (was: GPL) by DrSkwid · · Score: 2, Insightful

    hmm, did you reply to the wrong post ?

    --
    There are places where the networks are not touching,and there are places where they are-Boeing's Lori Gunter
  40. Re:NOT Open Source (was: GPL) by timeOday · · Score: 1
    I develop under both GPL and BSD licenses, based on the particular piece of code. If I think the code has strategic value (typically a library or framework), I'll develop under BSD so I can use it in any of my closed-source software too. Software which only has utilitarian value is typically released under GPL.
    That makes no sense at all. Of course you can license your code to others under the GPL and still use it in your own proprietary products. You're not limited by the terms under which you license your code to others. That's like accusing Microsoft of hypocrisy for mass-duplicating their own software while also pressing piracy charges.
  41. Re:NOT Open Source (was: GPL) by Anonymous Coward · · Score: 0

    Try leaving things "up to each individual developer" in a basic include file. Licenses are not a good place to be "individual", they're a place where using a standard saves time, space, and money wasted on weird lawsuits and legal conferences to protect people's work.

    If your license is weird and prevents us from doing good work with it, then we will choose not to use it. Please look at the demise of the WU mail client, Pine, for an example. The software was written by people like Mark Crispin, the creator of IMAP. But because the licensing is so restrictive, no Linux distribution can include it as part of their default installation without facing lawsuit from WU for patching it to fit their layout, at last without explicit permission from Washington University. And WU just doesn't grant such permission, or at least never that I have seen. Qmail has the same problem, so did XFree86: by tightening up licensing to prevent software forks, they've effectively doomed their software.

    XFree86, fortunately, got forked off to Xorg. Pine and Qmail, however, seem to be evaporating from servers and distributions as "too dangerous to use". Those are real licensing issues where "individual" licensing efforts have interfered with the software's development and use.

  42. Re:NOT Open Source (was: GPL) by Anonymous Coward · · Score: 0
    Fortunately, Apple was kind enough to open source Darwin, but it didn't need to, and it choose not to open source the Aqua UI and the Finder shell. I could be mistaken, but I don't think they would have been able to do this had Darwin been based on GPL'ed software.

    The probability that Apple would have based OS X on GPL'd code is approximately zero. If there had been no BSD codebase to use, Apple most probably would have either licensed a proprietary Unix implementation, or developed its own (non-standard) kernel in-house.

    Developing a kernel for a small set of hardware (like Apple's) isn't a monumental task, and could easily have been done. Apple clearly benefits from being able to use BSD codebases instead, and vice-versa, but it was not at all necessary.

  43. Re:NOT Open Source (was: GPL) by trifish · · Score: 3, Informative

    > It means every change is visible to you,

    That's not always true. If you modify a GPL-ed web application (or server software) and don't distribute it (only run it for / show output to your visitors) -- the you don't have to publish (open source) the modifications.

  44. Re:NOT Open Source (was: GPL) by rainman_bc · · Score: 1, Flamebait

    Fortunately, Apple was kind enough to open source Darwin, but it didn't need to.

    Apple has closed part of the Kernel now called XNU.

    Is Apple kind, or are they just putting up a facade, closing the source where they see fit?

    --
    09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0
  45. Re:NOT Open Source (was: GPL) by trip23 · · Score: 2, Insightful
    That makes no sense at all. Of course you can license your code to others under the GPL and still use it in your own proprietary products. You're not limited by the terms under which you license your code to others. That's like accusing Microsoft of hypocrisy for mass-duplicating their own software while also pressing piracy charges.
    The point is that if others contributed to your GPL'ed code, you have to get their permission to use the code in a closed-source environment. With a BSD license you don't have to worry about this. With the GPL it's hard to change the license, if there are a lot of contributors. Just take a look at the discussion about the Linux Kernel und GPL 3.0. Getting the consent of all copyright-holders in order to upgrade to 3.0 would be a nightmare.
  46. Highly desirable toolkit, but not universal. by Anonymous Coward · · Score: 3, Interesting

    I saw Bryan Cantrill give a demo of DTrace at my university. I was pretty impressed.

    I wanted to use it for my application to diagnose performance and race condition problems. However, then I realized I'd have to wrap all the instrumentation so that it would still work portably. Then I thought it seemed like an awful lot of bother just to get some profiling in there, especially if I was going to support an alternate method of collecting the same events so as to make the whole application (which includes profiling support) portable.

    "Sorry, we have to run it on Solaris or FreeBSD to debug/optimize" was ultimately what made me stay away from it. I looked into getting OpenSolaris working, and by the time I'd finally finally discovered from Sun's extremely confusing website and the equally confusing OpenSolaris webpages that what I wanted was Solaris Express:Community Release (SX:CR) so that I could get some interesting DTrace fixes and features, and had even burnt the 4 CDs and was all ready to commit to the Solaris way of life, I just got the heebie jeebies.

    Hopefully, just hopefully, the FreeBSD port works out well, and there will be a version for Linux sometime soon... there's hope that the advent of the GPLv3 will ease a lot of political slash licensing problems.

    DTrace is really incredible for application developers. You can insert lightweight, shippable, debugging and profiling points wherever you want them. I just feel you can't outright commit your project to it yet which is sad. It's the kind of stuff that should be made a POSIX standard, quite frankly.

    1. Re:Highly desirable toolkit, but not universal. by Profound · · Score: 1

      I have also heard about this tool and wanted to try it out but didn't have Solaris. From reading about it, it appears to be very system specific for speed reasons, I think you could get it to work with porting effort, or perhaps adding a virtualization layer. A hack would be a VM w/no cost Solaris.

    2. Re:Highly desirable toolkit, but not universal. by sethmeisterg · · Score: 1

      There is way too much FUD around people who "thought they wanted to try DTrace but it was just too hard to get Solaris running". That's a total cop-out. So it took you a few clicks to download Solaris Express-- big freakin' deal. If you're not willing to put in a little time to get Solaris running, you won't reap the reward. Solaris runs out of the box on tons of hardware, including VMware. Just grab a free copy of VMware, then load a free copy of Solaris and you're done. It'll take you an hour (after you download the images). If that's too long for you, then don't bitch about it-- just realize that you skipped the benefit because you were too damn lazy to put in some time up front.

    3. Re:Highly desirable toolkit, but not universal. by Anonymous Coward · · Score: 0

      If you were referring to my post and not the parent's, it was my personal experience, not FUD. I did get SX:CR build 33 finally downloaded. Note that this is NOT the same as SX, and it did take me lots of looking, digging through bug reports (build 33 has features build 32 does not, etc.) and ultimately a conversation on irc to find out what I really wanted.

      Anyway, it's not the time necessary to get Solaris running. You're making assumptions about laziness. It's the fact that although I would love to have DTrace support, I can't depend on it, because that would make me tied to Solaris. So then it becomes a "cool optional feature available under one OS" and by then it seems like to much effort to integrate.

      Hence the comment about me wishing it were part of some POSIX standard.

  47. Here. Use one of my napkins then. by gd23ka · · Score: 3, Informative

    Hi there, first I don't give a flying fsck whether i get l33t points over this or really whether I get modded down.
    I hope however that either of our posts get modded up so that people actually take notice of this thread.

    That out of the way I don't really care whether droves of Linux/FreeBSD/OpenBSD etc.etc. users rush and adopt
    (Open)Solaris. I would definitely switch to Solaris also at home instead of Linux if it supported all of my hardware
    but I guess the home-user is besides the point I suppose you trying to make. Suffice it to say I can see no rush to
    AIX on the pseries or to HP-UX either but that has more to do with market saturation than anything else.
    The more interesting statistic to look into is how many Solaris 2.5-9 users have upgraded to Solaris 10. We admittedly
    didn't get all excited about DTrace alone, actually it was Solaris Zones that pulled us in.
    Oh I forgot. Microsoft Windows. Either risking to come off arrogant or preaching to the choir here, I suppose people
    using that can't be expected to migrate to Solaris either, mainly because of their investment in "Microsoft Technologies" but also from my personal experience due to an (utter) lack of broad technical background on behalf of their staff.
    These people for the most part don't trace first and see if they can tackle the problem. They consult "Knowledgebases" or call Microsoft.

    So the question is, what rush are you expecting that nobody else is (well apart from the marketing/sales depts trying
    to justify their upkeep) ??

    2. Is it definitely going to work wonders for BSD. It made my life on Solaris a hell of a lot easier. It'll make
    people's lives on (Free)BSD a hell of a lot easier. Soon I'm sure it will do that on Linux and after that on AIX,
    HP-UX oh and maybe in a few years hence even on more esoteric systems like Stratus VOS etc.

    As an administrator it does wonders for me over and over, because now I can trace SCSI cmds/responses from devices,
    trace NFS problems like the one I just bragged about and the like. I get so much faster and easier clued in where
    the problem is by looking at what's going on under the hood so yes it is making me vastly more productive as an admin.

    3. DTrace is also useful for "regular IT folks" and I guess that's where our real mentality problem kicks in. Firstly,
    even you who is definitely not an engineer can use DTRACE scripts other people develop. It's easy, at times all you
    need to do is dtrace -s script.d and there you are. But going back to our mentality problem. You're right. I think
    DTRACE is not really made for "regular IT folks" that are not fluent in C or don't have a working knowledge of processes/threads/user virtual address space vs. kernel address space etc. etc. I guess "regular IT folks" like that wont get much mileage out of DTRACE but still like I said they can use already developed scripts with maybe someone over the phone helping them. And that brings us to some Level 3 support guys @ SUN in Bulington... their main problem with DTRACE is not that it's of no help or no value. In fact our competition at one site opened a call with Sun on an issue we were already working on and then sent us a DTRACE script Sun support wanted to run. We compared it to our own script we had started on the problem and Sun support was looking exactly at the same cause of the problem we were :-). I guess the real
    issue some of the Level 3 Support guys @ SUN in Bulington have is that DTRACE gives third parties like us a hell of a lot more clout in diagnosing problems which results in a lot less calls to them and that's making them vomit.
    To tell you the truth I mulled this aspect of DTRACE over too, that it would give the customer and competitors more
    insight and transparency into the system, but like you said yourself DTRACE is nothing for "regular IT folks" so
    on the bottomline it's a definite plus for us.

  48. Re:NOT Open Source (was: GPL) by compass46 · · Score: 1

    "Well, or GPL people could take the fine contribution of the BSD people, and port it to GPL. Therefore both communities can benefit. If Sun had released it under GPL, the BSD people would have been prevented from doing this."

    Sun's Dtrace is CDDL licensed, not BSD. Also, we wouldn't have been prevented from anything if Sun had released it under the GPL. We just would have imported GPL software over CDDL software.

  49. Re:NOT Open Source (was: GPL) by Anonymous Coward · · Score: 0

    The only joke in this thread is you, asshat.

  50. Re:NOT Open Source (was: GPL) by SillyNickName4me · · Score: 3, Insightful

    Fortunately, Apple was kind enough to open source Darwin, but it didn't need to,

    Not only that, they also contribute code back to FreeBSD, which they also don't have to. It is directly to their advantage to do this however (if it gets accepted it means it gets maintained without Apple having to pay developers to do so). Now, Apple isn't exactly alone in this either, considering things like FreeBSD's netgraph and jails just to name some other things contributed by conpanies who could also have decided to keep those things to themselves.

    and it choose not to open source the Aqua UI and the Finder shell. I could be mistaken, but I don't think they would have been able to do this had Darwin been based on GPL'ed software.

    You are wrong.

    Those are applications runniong on top of the core system, and they can be kept closed source just as much as you can have a closed source application for the GPLed Linux, and it is legal to create a CD that distributes both.

    For that matter, there exist closed source X implementations and desktops that run on Linux as well, giving you a near equivalent (as in, a gui 'engine' and a desktop environment, not judging that they are of eqivalent quality)

  51. Re:NOT Open Source (was: GPL) by QuietLagoon · · Score: 1
    You misread my message. I did not mean to imply that each developer should create his or her own new license, but that each developer has the right to choose what existing license to use.

    On the other hand, if a developer wants to create a new license, who are we to say he cannot? I appreciate the concern regarding the proliferation of OSS licenses of late, and I (as a user of and contributor to OSS) agree with you that fewer licenses are better than more licenses. However, we cannot dictate to anyone which license must be used for their original code. If you don't like the license someone chooses to use, then don't use the code that was written under that license. It's really a simple concept.

  52. Re:NOT Open Source (was: GPL) by Anonymous Coward · · Score: 0

    You just got schooled and you didn't even know it. Too funny.

  53. moderate this shit down by Anonymous Coward · · Score: 0

    it's old, tired crap.

  54. Video... by epiphany_man · · Score: 0, Offtopic
    1. Re:Video... by Sancho · · Score: 1

      Was this somehow posted to the wrong story?

  55. Plembo - Troll account by gd23ka · · Score: 1

    On an impulse I looked up what other things Plembo has to say on slashdot and I found only today's two posts.

    http://slashdot.org/~plembo

    Re:Maybe you should wipe your mouth after vomiting Monday May 29, @11:51AM 2 0
    Dtrace - is often referred to as "error vomit" Monday May 29, @10:37AM 2 0, Redundant

    Of course, either this gentle(wo)man happened across Slashdot where he or she saw DTrace on FreeBSD being discussed
    and feeling strongly about DTrace and how it was purportedly perceived as "error vomit" by one or two individuals at Sun Support in Bullington and immediately signed up over that... or a really envious Troll who just dropped by to upset some
    (Free|Net|Open|Dying)BSD people either for fun or profit. We'll never know what's the score here but I also doubt we'll hear much more from Plembo.

    A couple of years ago I busted a wannabe Monsanto shill who just had three posts to his name. Professional shills take time on a discussion board to build reputable accounts developing rapport with the group and then in time become opinion leaders. On second thought if you work for one of Sun's PR companies and just conned me into attacking and beating the shit out of would-be Solaris 10 deriders, man you did a great job here, more power to you.

  56. Re:NOT Open Source (was: GPL) by Anonymous Coward · · Score: 0

    you have to get their permission to use the code in a closed-source environment. With a BSD license you don't have to worry about this... .. because nobody will contribute to your project.. :o) /me ducks!

    (man, these license wars are FUN!)

  57. systemtap works for me by j0el · · Score: 2, Informative
    1. Re:systemtap works for me by Anonymous Coward · · Score: 0

      SystemTap is like playdoo compared to DTrace

  58. Re:NOT Open Source (was: GPL) by smash · · Score: 1
    Erm... actually it goes like this:

    Free OS (the BSDs) gets DTrace. If a commercial OS wants to implement it, they get DTrace (easily, as the code is open). Net result = better software in BOTH the free and payware segments.

    How is this bad?

    One thing the GPL weenies just don't seem to get, is that BSD people *DON'T CARE* if people use their code to make money/sell commercial software, because the aim is to improve the quality of software in general - not to impose some sort of political agenda.

    No one is going to FORCE you to BUY Dtrace in a commercial OS when the free version exists - but, if the commercial OS has features that you personally need, the option is there.

    --
    I run: Windows, OS X, Linux, FreeBSD. Just because you have a hammer, doesn't mean everything is a nail.
  59. Re:NOT Open Source (was: GPL) by evilviper · · Score: 1
    I could be mistaken, but I don't think they would have been able to do this had Darwin been based on GPL'ed software.

    A good point. You have BSD software to thank for all standards.

    NFS still hasn't seen any replacement, even though it has serious limitations, because most all the alternatives are GPLd, or otherwise encumbered like AFS.

    Telnet had vastly outlived it's useful life, but was still forced into service, with a few hacks like skey auth, kerberos auth, and encryption. It remained in service until OpenSSH came along.

    PGP/GPG, though being very good, have not become standard at all, and instead e-mail and other communications channels remain plain-text.

    The MKV (matroska) file format is quite good, but GPLd, and so the Ogg/Ogm container remains more popular, although it is admitedly quite limited and flaky, so it isn't getting too widely adopted, either.

    Hardware players like the Rio Karma include support for formats like Vorbis and FLAC, but not musepack and the like, because it was previously GPL'd, and releasing their firmware, or making the firmware modular to keep the code seperate, was unacceptable to the developers. While Vorbis and FLAC may not be quickly taking over the world, they do continue to get wider support every day. Before FLAC was BSD licensed, you couldn't even find any hardware players with lossless compression at all, even though there were several popular formats. Their license were too restrictive.

    People talk about how great Aqua is, but it's not exactly taking the world by storm. OpenStep is GPLd, and is really failing miserably to get a foothold against GTK, QT and Motif toolkits, as well as native X11 (QT and Lestif are GPL'd, but they have closed-source commercial counterparts for those willing to pay).

    I could go on, and on, but I think that's enough to make my point. If you want a standard, you can't use the GPL.

    A better example of the GPL's strength would be the Linksys WRT54G router. I've got one myself and it does all kinds of awesome things it wasn't able to do out of the box (hell, you can even run an OpenVPN server on it), all because Linksys was forced to release their source code under the GPL.

    That's a very trivial example. The same could be said of something like the iPod, which doesn't use GPL'd software at all, and you can still load Linux on it and get extra features unavailable with the built-in firmware. Or most other embedded hardware, like hundreds of handhelds which have Linux/BSD ported to them.

    I believe that the core focus of the OSS community should be on GPL'ed software (because "embrace and extend" does in fact happen)

    What people fail to realize is that "embrace and extend" doesn't take away any of the work you've done, never manages to catch-on, and you're really throwing the baby out with the bathwater trying to prevent it.
    --
    Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
  60. Re:Developer Laments: What Killed FreeBSD by linimon · · Score: 0

    msmith's last commit was 20020504. This posting probably predates that.

    Since his last commit, FreeBSD has released, in order: 4.6, 4.7, 5.0, 4.8, 5.1, 4.9, 5.2, 4.10, 5.3, 4.11, 5.4, 6.0, 6.1, and 5.5. That's 14 releases from 3 different release branches.

    The current codebase bears only a vague resemblance to what was in 4.6. After 4.6, 4.X was made far more stable; then 5.X incorporated major new features including rewritten SMP support and added support for laptops and wifi; and now 6.X is consolidating those changes and concentrating on performance and bugfixing as well as adding features.

    We probably have far more developers now than we ever have had in the past. People have come and go but development has continued, if not accelerated.

    Four years is an eternity in Open Source. Our troll needs to get over it.

  61. Re:Dtrace - is often referred to as "error vomit" by Anonymous Coward · · Score: 0

    Something as FUCKING AWESOME as DTRACE and YOU DARE to come here and open our SHIT MOUTH and speak out against it?

  62. Re:NOT Open Source (was: GPL) by Anonymous Coward · · Score: 0

    Clearly you have not read why they've done it. To prevent piracy of their source. Do some google searches before spouting off.

  63. real men don't use licenses ... by retiarius · · Score: 2, Funny

    ... they use the public domain. public domain is the stem cell
    of licensing, whereby you can take such code and graft any damnfool
    license onto it if you have the inexplicable urge to think smaller.

    oh, and real men don't use 'dtrace', they use 'printf()' --
    if it's good enough for ritchie & thompson, it's good enough for me!

    1. Re:real men don't use licenses ... by discogravy · · Score: 1

      how's that desktop PDP-11 working out for you, btw?

  64. Re:NOT Open Source (was: GPL) by DrSkwid · · Score: 1

    That's right. The GPL just don't get that.

    I've never seen anyone complain that a commercial entity used some BSD code as the basis for a project (except for Theo and his SSH rant =).

    Imagine the devastation if the first TCP/IP stack out of Redmond had been all their own work!

    I wonder how many of the "gpl stops you getting ripped off" people have ever PAID for Linux ?

    I've bought it twice and I don't even like it !

    --
    There are places where the networks are not touching,and there are places where they are-Boeing's Lori Gunter
  65. Re:NOT Open Source (was: GPL) by Eivind+Eklund · · Score: 1
    No, I replied to the one where you had the naive idea that we (BSD developers) have zero value in our work, and that we get "ripped off". Of course, your naivety is sort of excusable - the GPL contains propaganda to encourage it, it is common among the GPL people, and parrotting your peer group is easy.

    However, if you read the signature to my previous reply, you'll find a crucial clue for why the BSD license usually is MORE efficient for getting changes back (with the occasional generic closed derivate as a result; SunOS was the last one we didn't get much back from, AFAIK.)

    Eivind.

    --
    Doubting the existence of evolution is like doubting the existence of China: It just shows that you're uninformed.
  66. Re:NOT Open Source (was: GPL) by DrSkwid · · Score: 1

    haha, you TOTALLY misunderstood me =)

    I was replying to this from the parent to my post :

    "As a developer, if you value your work, the GPL is the better license under which to release code"

    Because of that confusion it took me a few reads of your post (after I replied) to work out what you actually meant - and it was a spot on reply.

    I'm not surprised you took umbrage if you missed that bit. I'm a FreeBSD user and am totally behind the BSD philosophy.

    keep up the good work =)

    --
    There are places where the networks are not touching,and there are places where they are-Boeing's Lori Gunter
  67. Already out there... if you got $$$ by speedplane · · Score: 1

    Green Hills Software already has a product which can trace anything. I think it does it by recompiling (or relinking?) the software with its proprietary compiler. But once you do that you can trace anything, not just system code. Seems like a cool product if you have the dough. Here's more info, with screenshots: http://www.ghs.com/products/timemachine.html

    --
    Fast Federal Court and I.T.C. updates
    1. Re:Already out there... if you got $$$ by Anonymous Coward · · Score: 0

      You're changing the actual code that's running. Many problems being debugged just go away when that happens. DTrace works without even having the source to the application you're profiling/debugging.

      That said, Nortel Networks have the functionality that Greenhills provides WITHOUT having to recompile - the hardware can tracks every jump/jump subroutine executed by the CPU, to give a complete list of branches taken through the code.

  68. Re:NOT Open Source (was: GPL) by vga_init · · Score: 1

    What the fuck does this have to do with anything? Ah, I see, you were just looking for a reason to do some 'GPL advocacy'.. Let me make some small suggestion: Advocacy like this is just annoying the hell out of people, and makes you look like a fanatic idiot.

    Three guesses who is being annoying and acting like a fanatical idiot, and it's not him.

  69. Re:NOT Open Source (was: GPL) by MichaelSmith · · Score: 2, Insightful
    why the BSD license usually is MORE efficient for getting changes back

    As far as I am aware, the BSD license was not designed with this goal in mind. The GPL was designed with the goal of keeping the source code available to the developer community.

    Whether this goal is achieved is debatable, but I think the GPL (or licenses similar to it) deliver the best chance of keeping systems open as we move into a heavily DRM'd world.

  70. Re:NOT Open Source (was: GPL) by wysiwia · · Score: 1

    People talk about how great Aqua is, but it's not exactly taking the world by storm. OpenStep is GPLd, and is really failing miserably to get a foothold against GTK, QT and Motif toolkits, as well as native X11 (QT and Lestif are GPL'd, but they have closed-source commercial counterparts for those willing to pay).

    Yet a framework needs a license as wxWidgets so it can be used everywhere. Anything else is IMO ridiculous.

    I could go on, and on, but I think that's enough to make my point. If you want a standard, you can't use the GPL.

    That's not entirely correct, it quite much depends on what kind of object is licensed. While it may make sense to license an OS or an application GPL, anything which don't need to be linked, it's no questions a framework or a file/music format can't have the same license. In a such case the wxWindows or a BDS license is much more appropriate.

    O. Wyss

    --
    See http://wyoguide.sf.net/papers/Cross-platform.html
  71. Re:NOT Open Source (was: GPL) by Eivind+Eklund · · Score: 1
    why the BSD license usually is MORE efficient for getting changes back
    As far as I am aware, the BSD license was not designed with this goal in mind. The GPL was designed with the goal of keeping the source code available to the developer community.
    Neither the BSD nor the GPL was designed with the goal of getting as many changes back as possible. And I believe the GPL was designed with a slightly different goal than you describe. Both the GPL and the BSD license keep the source code available to the developer community. What the GPL does is block commercial development and, with it, the temptation of the people that write code of using that code commercially. If you look at the history of the GPL, it originated after most of the AI lab at MIT started working commercially, removing Stallmann's beloved sociotechnical arena. This happened when the people that worked on various projects decided to take those projects commercial, and so the "open source" version was stuck at the previous version.

    Whether this goal is achieved is debatable, but I think the GPL (or licenses similar to it) deliver the best chance of keeping systems open as we move into a heavily DRM'd world.

    Maybe. I'd have to do a proper analysis of the different economic modes here, and so far I feel there's too many variables for it to be possible to do properly. I'm sure that a world where we're forced to use the GPL for open source is a poorer world, at least - it lose us a lot of positive economic modes.

    BTW: Are you the same Michael Smith I know as msmith@ ?

    Eivind.

    --
    Doubting the existence of evolution is like doubting the existence of China: It just shows that you're uninformed.
  72. Re:NOT Open Source (was: GPL) by Anonymous Coward · · Score: 0

    90% of gpl projects don't really get any _real_ contributions aswell,
    so nothing lost here as long as `only` 10% of bsd people get contribution.

    lately i have started to keep away from gpl. opensource'n'shit is nice, but
    business is business. i "need to/want to/will" keep my some stuff closed
    just to keep the competitors one step behind. otherwise i'd be doing work
    for them and they'd get a cost/development advantage over me with you using
    my gpl-d code.

    this is like giving the hand to the people that
    are cutting it off from you with a chainsaw.

    gpl is good idea for some stuff but certainly not everything.
    bsd is much more universal.

    ps. real bad boys (billy, larry, steve) will eventually get your opensource code
    anyway (they can rewrite it from the scratch, they have the dev. power for it),
    no matter how you license it. and they will sell it to you.

  73. OpenBSD by Anonymous Coward · · Score: 0

    So what are the plans on porting dtrace to OpenBSD?

    1. Re:OpenBSD by weaselcho · · Score: 1

      Do you think Theo would accept CDDL?

  74. Re:NOT Open Source (was: GPL) by MichaelSmith · · Score: 1
    BTW: Are you the same Michael Smith I know as msmith@ ?

    No sorry. I am smithm@ or smithmr@. I was once a member of the Michael Smith webring, though :)

  75. Re:NOT Open Source (was: GPL) by Eivind+Eklund · · Score: 1
    OK. msmith@(FreeBSD.org, but we usually don't write that) was another FreeBSD developer and now work for Apple, and I would be a little surprised if he had changed to liking the GPL, though not THAT surprised.

    Eivind.

    --
    Doubting the existence of evolution is like doubting the existence of China: It just shows that you're uninformed.
  76. Re:NOT Open Source (was: GPL) by Anonymous Coward · · Score: 0

    The point is that if others contributed to your GPL'ed code, you have to get their permission to use [their] code in a closed-source environment.

    Thats only half the point. It also applies to your competitors. It goes like this: Company A has a product which consists of an extensible core and a bunch of plugins. How do you kill the competition? Release a GPL 'community edition' of the core, and *some* plugins. Release patches to the community edition, but never take patches back into the commercial version. A thriving community evolves around LGPL plugins, and some users who wouldn't have bought anyway upgrade to your pay-for version. Meanwhile, your competitor dies the death of a thousand cuts.

    Alternatively you can release the core under a BSD+advertising clause. If your competitors want to use your core instead of their own, they have to advertise for the opposition.

  77. Re:NOT Open Source (was: GPL) by Anonymous Coward · · Score: 0

    > Imagine the devastation if the first TCP/IP stack out of Redmond had been all their own work!

    It doesn't contain any BSD code either. When are you morons going to stop perpetuating this myth?

    Microsofties must be getting a good laugh at your pathetic investigation skills when strings ftp.exe comprises all of it.

  78. Re:NOT Open Source (was: GPL) by 99BottlesOfBeerInMyF · · Score: 1

    Fortunately, Apple was kind enough to open source Darwin, but it didn't need to, and it choose not to open source the Aqua UI and the Finder shell.

    Kind enough? Apple wasn't kind, they just recognize the value of the open source model. By contributing changes back, they maintain more parity with other software developers using the same or very similar code. Thus, they can pull in more changes and improvements others make, more easily.

    I could be mistaken, but I don't think they would have been able to do this had Darwin been based on GPL'ed software.

    The GPL certainly is a barrier to some usages, which is probably why Apple chose to use mostly BSD licensed software, and license much code they develop with a similar license.

    That said, the BSDs are great projects (as are public domain projects like SQLite) and I wouldn't want to see them disappear. I believe that the core focus of the OSS community should be on GPL'ed software (because "embrace and extend" does in fact happen), but there's definitely an argument and a place for BSD-style licenses.

    If I was starting a new project in a new area, I'd likely pick GPL for the license, with one exception. If I was building a core architectural feature, like a new form of networking or filesystem, and I wanted that to be as widely adopted as possible, I'd go with a BSD style license. Sometimes you want Apple and Microsoft to integrate your code, even if it means they will maintain their own closed source version. ZeroConf is a good example. By licensing their implementation with a FreeBSD style license, Apple got printer manufacturers on board and made it a killer feature. This is much more palatable than a GPL license to them and even MS will probably have to integrate the code eventually or suffer comparisons about how hard it is to setup LAN networking and device discovery compared to other OS's.

  79. Where is the Port? by fak3r · · Score: 1

    I've read about dtrace and wanted to try it for awhile, posts to BSDForums haven't helped me either. I don't have it in my ports tree, and it's not listed on Freshports: http://www.freshports.org/search.php?query=dtrace& search=go&num=10&stype=name&method=match&deleted=e xcludedeleted&start=1&casesensitivity=caseinsensit ive

    Anyone know how to get ahold of a copy? I've created ports before so I'm not afraid to try some 'testing' version.

    Thanks

  80. Re:It is official; Netcraft confirms it: BSD is dy by antik2001 · · Score: 0

    No shit, I am officially moderated to troll now... :(

    Next time YOU, MODERATOR read PARENT post and THINK!!!

    slashdot is sick place...I'm leaving...

  81. Re:NOT Open Source (was: GPL) by SillyNickName4me · · Score: 1

    Three guesses who is being annoying and acting like a fanatical idiot, and it's not him.

    You
    You
    You

    Now.. what do I win?

  82. Re:NOT Open Source (was: GPL) by DrSkwid · · Score: 1

    http://www.kuro5hin.org/?op=displaystory;sid=2001/ 6/19/05641/7357

    Intimates that the BSD was used as the basis, if not copy & pasted.

    But thanks, it made me look up the subject for real.

    As I said, not "all their own work".

    If you re-read my post without your angry glasses on, you'll see it doesn't say what you think it does.

    --
    There are places where the networks are not touching,and there are places where they are-Boeing's Lori Gunter