Follow Slashdot blog updates by subscribing to our blog RSS feed

 



Forgot your password?
typodupeerror
×
BSD Operating Systems

FreeBSD 5.0-RC2 Now Available 60

An anonymous reader writes "FreeBSD 5.0-RC2 has been uploaded to ftp-master and is showing up on most of the primary mirrors. ia32, ia64, pc98, and alpha images are available now; sparc64 will be pushed out once it becomes available. The plan going forward is to cut an RC3 in early January, followed by 5.0-RELEASE a week later."
This discussion has been archived. No new comments can be posted.

FreeBSD 5.0-RC2 Now Available

Comments Filter:
  • by Anonymous Coward
    Does this release candidate have a native pthreads implementation that uses rfork to provide kernel level threads?
    • by cant_get_a_good_nick ( 172131 ) on Sunday December 22, 2002 @04:13PM (#4941473)
      Re:pthreads using rfork?
      I looked at the man page, this seems similar to the clone call on Linux, which they wrapped pthreads around. Aren't there performance issues on this, that it's a process not a thread? I could see issues with signals as well.
      • by Leimy ( 6717 )
        I thought pthreads were going to be based on KSE's [Kernel Scheduling Entities and yes it is possible to see something less than a kernel process as a schedulable context and to build one's threads and processes upon it.. though I will admit to not being very familiar with the architecture of KSE's yet. :)] and not be full processes. In fact I am 100% positive that FreeBSD 5.0 is going for M:N mapping of threads to processes meaning that they are not planning to do the 1:1 that linux had for years up until NPTL came out.

        Linux used to use clone to get a new LWP but 2.6 should have some much newer, better stuff.

    • by Anonymous Coward
      No, threads based on fork/rfork/clone is a horrible idea. threads will be based upon KSEs, which will give solaris level threading performance, and much less overhead. This basically splits the process into an equal number of threads as you have processors, scheduling is done by the kernel of those threads, and user-level threading is done within each of those. This means you can fully utilize all the CPUs in your machine with only that number of kernel schedule entries, the overhead of managing thousands of threads is pushed off to that applicaton (where it should be). In terms of scalability, this is where it is at. Its simply a briliant idea. I'm surprised it took OpenSource this long to get it.
    • FreeBSD has linux threads which do something similar.... FreeBSD 5.0-RELEASE (as far as I know) will also have it's own form of kernel threading called KSE's... These are much better than the rfork threads.
  • by Groganz ( 552205 ) on Sunday December 22, 2002 @10:57PM (#4942699)

    Tomorrow: Freebsd 5.0-RC2 one day old.

    • by Anonymous Coward
      This afternoon:

      Freebsd 5.0-RC2 ALMOST one day old.

      LMAO ;o)
    • hehe but this joke is gettin' really old. FreeBSD is a big thing so why not give it the attention it deserves. We dont want articles about every security patch M$ is releasing right? So why not some attention for this instead. One thing though, FreeBSD 5.0 RC2 almost ready is A BIT over the top.
  • os vs os wars should be moded to -1 but I just saw something I thought was odd...

    In the "related links" section for this topic there is a link: Compare the best prices on: Software/Operating Systems [pricegrabber.com]

    so which has the best price, Free BSD or Linux :-)
  • If you'd like to use cvsup to get to this release, change your current

    <i>*default release=cvs tag=</i>
    to:
    <i>*default release=cvs tag=RELENG_5</i>

    Note: You may have to run this 2 times - the first time it will <B>DELETE</B> the contains of your existing src dir, the second time it will inflate it.
    • Re:CVS Tree created (Score:2, Informative)

      by pfish ( 576318 )
      Cute...it didn't post in HTML as i selected.

      If you'd like to use cvsup to get to this release, change your current

      *default release=cvs tag=
      to:
      *default release=cvs tag=RELENG_5


      Note: You may have to run this 2 times - the first time it will DELETE the contains of your existing src dir, the second time it will inflate it.

It is now pitch dark. If you proceed, you will likely fall into a pit.

Working...