Stories
Slash Boxes
Comments

News for nerds, stuff that matters

Slashdot Log In

Log In

Create Account  |  Retrieve Password

OpenSolaris Code Released

Posted by CmdrTaco on Tue Jun 14, 2005 11:20 AM
from the today-is-the-day dept.
njcoder writes "C|net's news.com.com has reported that Sun Microsystems is releasing parts of the OpenSolaris code today licensed under the OSI-approved CDDL . The release consistes of over 5 million lines of code for the base system OS/Net (kernel and networking). OpenSolaris is based on Solaris 10, the current version of Sun's Unix Operating System. Back in January, Sun released the code for DTrace, a dynamic tracing tool for analyzing and debugging kernel and userland events. DTrace is one of the big features in Solaris 10. Some other highlights include the GRUB bootloader, SMF (Service Management Facility) which replaces init.d scripts, it starts up processes in parallel for faster boots (7 second boot on a dual opteron workstation I think that was the setup) as well as providing features for automatically restarting. OpenSolaris provides support for x86/x86-64 processors as well as Sparc. The Blastware guys are working on Polaris which is an OpenSolaris port to PowerPC. Sun has been working on opening Solaris for over a year now. The OpenSolaris project started with a pilot group of Sun and non-Sun users. During the pilot program a lot of info including screenshots could be found on various OpenSolaris member blogs. (My favorite is Ben Rockwood's blog). Teamware is the source code management system Sun uses for Solaris and OpenSolaris. Which was designed by Larry McVoy (now of BitKeeper) while he was at sun. No word yet on if Teamware will be available for OpenSolaris developers or not. Sun also uses CollabNet for it's Open Source project websites so that might be a possibility as well."
+ -
story
This discussion has been archived. No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More
Loading... please wait.
  • Rock on! (Score:5, Interesting)

    YES! This completely rocks! Check it out:



    Combined with an Open Source/Forkable license, what more could a Solaris Geek want? Get out the party hats people, because this has got to be THE most awesome thing Sun has ever done!

    (I'm excited, can you tell? *Happy Dance* *Happy Dance*) :-P

    Now for the bad news. Sun has taken the tack of encouraging users to build their own system. That is a good thing. Unfortuntely, all builds require a system to bootstrap the build. At the moment, the only option is Solaris Community Edition [sun.com], a non-Torrented download. (Boo!) That being said, I don't think we'll have to wait too long for the OSS community to fix that little issue. :-D
    • Also check out Jim Grisanzio's blog [sun.com]. It explains a bit about what's been going on with the pilot program.
    • When will the Sun compiler be released under the CDDL? Currently, Sun Studio is under a different license. [opensolaris.org]
    • Unfortuntely, all builds require a system to bootstrap the build. At the moment, the only option is Solaris Community Edition, a non-Torrented download. (Boo!) That being said, I don't think we'll have to wait too long for the OSS community to fix that little issue.

      Sadly, that might not necessarily be the case - OpenDarwin has been around for five years and you still need a Darwin system [including some non-free tools] to bootstrap the build. But as Solaris Express is free as in non-costworthy, I don't

    • Re:Rock on! (Score:5, Funny)

      by kbmccarty (575443) <.moc.liamg. .ta. .ytraccmk.> on Tuesday June 14 2005, @04:33PM (#12817801) Homepage Journal

      Now for the bad news. Sun has taken the tack of encouraging users to build their own system.

      Countdown to Debian GNU/Solaris in T minus 10... 9...

      • Proper CD recording support because the makers understand the need for backwards compatibility, and don't go around breaking APIs just because they feel like it.
        • Proper CD recording support because the makers understand the need for backwards compatibility, and don't go around breaking APIs just because they feel like it.

          Joerg Schilling [linux.com], is that you?

          • So, tell me exactly which features are in Linux/FreeBSD/etc that I don't have or can't get for Solaris? Assertion that my statement is not true doesn't prove a damn thing.

            Does Solaris want to be the hacker's desktop OS? I really doubt it. Does Solaris want to be an OSS player in the data center? Absolutely. And for data center features, Solaris does very well against the competitors. If you think Sun's OSS strategy is to get joe hacker to run his OS, of course you're going to be disappointed, because

  • by emptybody (12341) on Tuesday June 14 2005, @11:22AM (#12814147) Homepage Journal
    now maybe we will see some driver development for all the cool hardware that is out there?

    • When things like the 'dad' & 'uata' (IDE drivers), and 'todsg' drivers are still in the closed source tarballs, I'm not hopeful for the 'open'ness of 'opensolaris' (Come on, they can't release drivers for their own hardware clocks?! (todsg))
      • by Nerant (71826) on Tuesday June 14 2005, @12:00PM (#12814607)
        Believe it or not, there are numerous legal issues that Sun has to work through in order to ensure code that is open sourced doesn't get anyone in trouble.

        Be patient. They're working on it. Or would you rather they open source some code they don't have the right to, and get people who see that code into trouble?

        There is still alot of work to be done, but it is a huge first step.

        For more, take a look at the roadmap at

        http://opensolaris.org/os/about/roadmap/ [opensolaris.org]
  • Zfs? (Score:4, Interesting)

    by astrashe (7452) on Tuesday June 14 2005, @11:24AM (#12814179) Journal
    Is zfs included?
  • I'm unfamiliar (Score:3, Interesting)

    by udderly (890305) on Tuesday June 14 2005, @11:26AM (#12814196)
    Since I'm mostly unfamiliar with Solaris, what are the main advantages it has over Linux, BSD and Windows? Just curious.
    • by Anonymous Coward on Tuesday June 14 2005, @11:45AM (#12814458)

      what are the main advantages it has over Linux, BSD and Windows?

      Well Solaris is +3 vs. undead, while Linux, BSD and Windows are: +1 icy blast, +2 flaming and -4 cursed respectively.

    • Re:I'm unfamiliar (Score:5, Informative)

      by ahl_at_sun (853337) on Tuesday June 14 2005, @11:56AM (#12814559) Homepage
      That answer depends on who you are. If you're a system administrator Predictive Self-Healing is going to raise the reliability of your systems and make management scads easier; SMF makes configuring the system a snap and lets you identify problems quickly and easily; Zones lets you partition the system without the management overhead of a bazillion OS instances; DTrace lets you understand everything that's happening on your system -- and who's responsible for the latest crap-up; Solaris Process Rights improve security and administrative overhead by splitting up the traditional binary notion of the super user. If you're a developer, you'll love DTrace -- I can't imagine developing with out it; the p-tools, truss(1) and mdb(1) are also great. If you're an end-user, well, Solaris's gnome sucks as much as anyone's gnome -- go use Mac OS.
      • you just said mdb = great. Now I know you're just making it up. Mdb is just about useless when the core file is generated on a system other than the one you're debugging with. (always the case if the binary crashes at a customer site, rather than the test-lab) We just went through a lot of effort to convert from using sun CC to compiling with gcc, not because gcc produces better code, but so we could get the right symbols for using gdb.

        mdb is the biggest pain in the world; gdb isn't perfect, but it's a lot
        • Re:I'm unfamiliar (Score:5, Interesting)

          by ahl_at_sun (853337) on Tuesday June 14 2005, @01:09PM (#12815422) Homepage
          Yes! That was true, but not as of Solaris 10. The reason core files needed to be on the same machine that produced them was because they didn't include all the necessary information. In particular, they didn't include read-only data. Their genesis was around debugging on a given machine and in that case, dumping the read-only sections is kind of pointless. This was a frustration that affected every application developer who cared about post-mortem analysis; we in Solaris really care about debugging from first failure.

          In Solaris 10, I did some work [sun.com] to make the content of core files adjustable and added text (aka code) to the default. Now when you get a core file, you can debug it on any other system regardless of the patch level, libraries installed or the version of your application that was running. Using coreadm(1M) you can adjust the content to, say, add the symbol table to the core dump or omit the gigantic ISM segment that you don't care about for.

          So, yes, mdb(1) had some limitations in the past -- we've tried to address them in Solaris 10. If you have other issues preventing you from using mdb(1), post a comment on the OpenSolaris [opensolaris.org] site.

          I thought I was going to have to find a shill to ask that question... "Sir, we've never met before, have we?"
    • For Linux and FreeBSD and common packages/ports on opteron and ultrasparc there's still 64 bit cleanliness issues, and there's BSD issues running on Ultrasparc III and above chips (as in, can't do it). FreeBSD is still trying to implement fine grained SMP spinlocks which don't sieze up under heavy load & to get fine grained locks into tcp stack. Solaris builds backward compatibiity into libraries that Linux dosen't have, which is why when installing proprietary app binaries there's all kinds of neat
    • Re:I'm unfamiliar (Score:4, Informative)

      by bdgregg (744616) on Tuesday June 14 2005, @12:05PM (#12814660) Homepage
      Probably the most clear and undenyable feature that is unique to OpenSolaris/Solaris is DTrace [sun.com].

      DTrace lets us examine just about anything, with minimal impact on the system. It's way cool, and other OSes have nothing that is close (for details covering the Linux Trace Toolkit (LTT), DProbes, K42 and Kerninst see the USENIX paper [sun.com].

      DTrace solves disk I/O by PID, network activity by PID, elapsed and on-cpu times for syscalls, libcalls and user funcs, and much more.

      DTrace is great if you are a programmer with a little kernel knowledge, but if not you may find the DTraceToolkit [brendangregg.com] helpful - it is a collection of ready-to-roll scripts.

      For a list of many OpenSolaris features with screenshots, see the OpenSolaris Guide [opensolaris.org].

  • by jhfry (829244) on Tuesday June 14 2005, @11:26AM (#12814209)
    Solaris doesn't stand a chance against *BSD or Linux... their logo sucks! Come on... seriously... what's more cuter than a Penguin or a Daemon?
  • so.. (Score:4, Funny)

    by brickballs (839527) <brickballs@@@gmail...com> on Tuesday June 14 2005, @11:28AM (#12814223) Homepage
    automatically restarting

    windows automaticay restarts for me all the time. I get a quick flash of blue and then bam! restart.

  • by Anonymous Coward on Tuesday June 14 2005, @11:28AM (#12814237)
    "Teamware is the source code management system Sun uses for Solaris and OpenSolaris. Which was designed by Larry McVoy (now of BitKeeper) while he was at sun. No word yet on if Teamware will be available for OpenSolaris developers or not."

    Remember folks. You hate Larry.
  • by m50d (797211) on Tuesday June 14 2005, @11:33AM (#12814296) Homepage Journal
    http://www.sun.com/software/solaris/get.jsp [sun.com]. Requires registration though.
  • openoffice... (Score:3, Insightful)

    by torrents (827493) on Tuesday June 14 2005, @11:33AM (#12814297) Homepage
    if this project is half as successful for sun as openoffice is i'm sure they'll be happy they decided to open it...
  • Great. (Score:4, Funny)

    by Telastyn (206146) on Tuesday June 14 2005, @11:33AM (#12814299)
    Perfect. An open source OS backed by a well known name. The perfect stepping stone to get hesitant PHBs to accept an open source OS without a big company behind it into their shops.
  • SMF vs InitNG? (Score:3, Interesting)

    by yerdaddie (313155) on Tuesday June 14 2005, @11:34AM (#12814319) Homepage
    I'm curious about how the SMF boot parallelization code stacks up against the InitNG project [thinktux.net], which does the same for Linux. Anyone had experience with both?
  • by Zemplar (764598) on Tuesday June 14 2005, @11:36AM (#12814348) Journal
    Ckeck out Blastwave.org http://www.blastwave.org/ [blastwave.org] for some torrents, apps, guides, and other goodies.

    Additionally, SunFreeware http://www.sunfreeware.com/ [sunfreeware.com] is another great site for getting applications.
  • by Anonymous Coward on Tuesday June 14 2005, @11:37AM (#12814363)
    "7 second boot on a dual opteron workstation I think that was the setup"

    You don't have to think, just RTFA, where you can see that it was a single AMD64 setup.
    Still, I guess that would be too much trouble for the simple gain of being correct ?

  • by CyricZ (887944) on Tuesday June 14 2005, @11:42AM (#12814431)
    I believe we are seeing the monopoly finally begin smashed to pieces. Besides the Linux and *BSD alternatives, we now have open-source x86 Solaris at our disposal, as well as the upcoming release of yellowTAB Zeta (based on BeOS). And with Mac OS X coming to the x86, things may really start to get interested. Just as people thought the x86 PC operating system market would start to stagnate, we have all sorts of innovation coming our way!
  • by NatteringNabob (829042) on Tuesday June 14 2005, @02:02PM (#12816104)
    Larry McVoy designed a prototype called 'NSE Lite' which was based on concepts developed by Eric Schmidt and Bunker Lampson which were incorporated into NSE which was built by a host of people including, but not limited to, Jon Fieber, Marty Honda, Ethan Adams, Terry Miller, David Hendricks, and Jill Foley. Larry McVoy had absolutely nothig to do with NSE or the core concepts of copy-modify-merge except for being an unhappy NSE customer. Glenn Skinner is listed as the patent author for 'smoosh' which is the central technology to both NSE-lite and Teamware. Larry claims that he is co-inventor. I don't know, I was in the NSE group, Larry was in the OS group at the time. Teamware itself was designed and implemented by Ethan Adams, Terry Miller, Jill Foley, Mark Sabiers, Lewie Knapp, Josh Sirota and Mitchell Nguyen. Larry's primary contribution was to complain a lot. Larry is a bright guy, but he didn't design Teamware anymore than Bill Joy designed Unix. He deserves a tremendous amount of credit for sucessfully productizing the technologies invented by the NSE team (and a lot of others) something that Sun, with substantially more resources, was unable to do, but it is an extreme stretch to call Larry the designer of Teamware (even though if Larry thinks so).
    • by Chyeld (713439) <chyeldNO@SPAMnewsguy.com> on Tuesday June 14 2005, @11:41AM (#12814412)
      One [apple.com]. Big one comes to mind.

      Don't know about the rest.

    • Are there parallel boot scripts made for other distro's? Fedora or Red Hat or Slackware etc...

      I don't know.

      --- If you found this answer helpful, click HERE.

      --- If not click HERE.
    • by chegosaurus (98703) on Tuesday June 14 2005, @12:02PM (#12814627) Homepage
      They aren't exactly parallel boot scripts. It's a part of something called the Service Management Facility. You write XML manifests describing how services should be started, stopped, restarted, refreshed, and what the SMF should do in the event of failure events. It intruduces the concept of dependencies between services, and makes a lot of things more coherent and logical. It also means you have to learn a lot of new stuff.

      The SMF has a concept of milestones, which groups of scripts "belong" to. This is not unlike the principle of run levels, and when moving between milestones the SMF can fire off a whole bunch of services in parallel. It usually does this through scripts akin to the old init scripts, but doesn't have to.

      That's not a very good description, but it might give someone who can't be bothered to RTFM some idea of one of the big new features.

      Solaris 10 is great. IMHO there's no Unix (or clone) to touch it. That's just my opinion, and I CAN NOT be bothered to argue about it, so don't start!
    • by WindBourne (631190) on Tuesday June 14 2005, @11:43AM (#12814437) Journal
      MS moved to "Shared Source" sometime ago. It was done in hopes that Linux coders would borrow from MS. So far, it has not happened.

      But this has potential to do what MS could not. Solaris is at least respected by the development world. This is simply another trap being laid by Sun and MS against Linux.

      What is funny is how little ppl seem to remember from just 7 years ago. Sun actually ported to X86 once before AND "opened" their source code. Then when they thought that things were going well, they dropped it. If Sun ever feels like things are going in their favor, it is almost certain that they will do it again.
      • "But this has potential to do what MS could not. Solaris is at least respected by the development world. This is simply another trap being laid by Sun and MS against Linux."

        Try reading the CDDL FAQ [opensolaris.org] before you start trolling.

        Can code licensed under the CDDL be combined with code licensed under other open source licenses?

        CDDL is file-based; that means that files licensed under the CDDL can be combined with files licensed under other licenses, whether open source or proprietary. However, other licenses

      • by starfishsystems (834319) on Tuesday June 14 2005, @12:57PM (#12815255) Homepage
        This is simply another trap being laid by Sun and MS against Linux.

        It may be. I know a very bright Microsoft zealot who thinks it is, and couldn't be more delighted at the prospect.

        I don't think it is, myself. For one thing, the internal cultures of these two organizations, and the personalities they attract to senior positions, could not be more different. You just have to look at their past conduct to see this. Microsoft does lay traps, systematically, all the time. Sun is a corporate player too, thus in the game for profit, but its strategies are much more symbiotic in their essential character.

        When Sun puts someone on a standards committee, it's to make the standard more valuable for everyone, on the express theory that it's better to share a growing market than have all of a stagnant one. When Microsoft puts someone on the same committee, it's to "embrace and extend" the standard so as to exclude competition, and the expressed goal is to eliminate all competition.

        Another thing worth remembering is that an organization as big as Sun has substantial internal struggles from time to time. Such was the case with Solaris on X86. The project took off energetically at first, but it was a risky venture which happened to fall out of political favor just at the point when driver support was becoming most critical. The result was not a strategic withdrawl, it was a conspicuous fumble which cost Sun a lot of internal morale, hurt its reputation, and lost it a golden opportunity whose extent has only become more apparent in recent years.

        So yes, it could all happen again, but not because of some nefarious strategy on the part of Sun Microsystems. Sun does not have a history of executing that way.

        • They are not as different as you think. I have worked at IBM and HP and have seen first-hand how Sun does things. Most of the traps that they have laid in the past have been in sales for other companies (IBM/HP being just 2 of many ).

          As it is, McNeally's collaboration with MS makes me very edgy. Consider how much McNeally hates Gates and MS. It does not make sense for them to work together.

          I have some friends who work for Sun and some others that work for MS (one who is on the linux tiger team - when he c
          • One of the MS guys claims that this is a long term trap. In particular, both MS's and Sun's license allows the use of the patents in the files (not code) for the system use. If anybody "borrows" the code, then they are no longer protected. Both companies are supposedly hopeful that the Linux world will pick up from either (interestingly, MS no longer thinks that it will come from their stuff, so Shared source will probably die or be severely limited). I no longer code on Solaris just due to my not trusting
      • by justins (80659) on Tuesday June 14 2005, @01:27PM (#12815636) Homepage Journal
        What is funny is how little ppl seem to remember from just 7 years ago. Sun actually ported to X86 once before AND "opened" their source code. Then when they thought that things were going well, they dropped it. If Sun ever feels like things are going in their favor, it is almost certain that they will do it again.

        I won't be the only one, but I just thought I'd point out that the license they are using this time around is quite different, and they literally cannot take away your right to use the code once you've got it. You might read the (OSI-approved) license before spouting off, although I know that is asking a lot.

        http://www.opensolaris.org/os/licensing/ [opensolaris.org]
      • Re:Finally! (Score:5, Interesting)

        by elmegil (12001) * on Tuesday June 14 2005, @12:14PM (#12814750) Homepage Journal
        rc.d? I see those on my Solaris system too. Don't you mean "rc.boot" and "rc.local"?? The "init.d" method has a master that runs subscripts from rc*.d directories too, so I fail to see how that's any different.

        SMF is going to be a head check for a lot of people who LIKE init.d/rc.d (though backward compatability with that has been retained so far). Myself, I like the fact that it's more robust and faster, and I don't like the fact that it's managed with a handful of different commands depending on what you want to do. And I'm not terribly thrilled that the backend is XML, but you'll have that.