Slashdot Mirror


FreeBSD 4.11-RC2 Available

hugo_pt writes "The FreeBSD Release Engineering Team is pleased to announce the availability of FreeBSD 4.11-RC2. This is the second of three scheduled release candidates. At the moment there are no known severe issues. However the Linux Emulation subsystem (mostly added as a package) has been completely updated based on Red Hat 8.0. We would appreciate people testing the Linux emulation support. In particular testing to see if Linux applications continue to behave correctly if the linux_* packages get installed while using sysinstall(8) during the initial installation of the machine. The package set for disc1 is still being decided on, what is on disc1 for this RC will most likely change before the release."

55 comments

  1. Why RedHat 8? by Trevin · · Score: 2, Interesting

    Forgive my ignorance, since I don't usually follow the FreeBSD distro (having moved from NetBSD to RedHat over four years ago). But it seems a bit late to be targeting the Linux emulation towards RedHat 8.0. Not only has RedHat 9 already been obsoleted by Fedora, but 8.0 was extremely short-lived (even by RedHat's usual release timeline) having had numerous problems. In addition, before the days of RedHat Enterprise, RedHat recommended that users requiring stability stick with 7.2 (or something around there).

    1. Re:Why RedHat 8? by ValiantSoul · · Score: 3, Informative

      The RedHat 8 emulation has been around for a long time in FreeBSD, it has just been updated. I'm not positive why its only version 8, but I'm guessing its because most applications that will work on today's distibutions probably work on RedHat 8 (with minor updates such as glibc).

    2. Re:Why RedHat 8? by molnarcs · · Score: 4, Informative
      As ValiantSoul said, rh8 has been there for a long time, but the default was rh7.x - which has changed to 8 now. The reason is that a few linux-apps didn't work with rh7 (a few!). All current linux-apps in FreeBSD ports works well with rh8, (most of them work well with rh7 as well), so I guess for at least a year 8 will be sufficient. Since FreeBSD is all about stability (even cutting edge ports), it makes sense that they switched to a well tested default. I, for instance, changed the default linux base to linux_base8 right when I began using FreeBSD (in 2003 september) with 5.1 release, and no ports gave me trouble. For your interest: rh-9 is already in ports btw, along with a few others:

      linux_base/ # stands for rh7
      linux_base-6/
      linux_base-8/
      linux_base-debi an/
      linux_base-gentoo-stage1/
      linux_base-rh-9/
      linux_base-suse-9.1/
    3. Re:Why RedHat 8? by Anonymous Coward · · Score: 5, Informative

      It works and has no security issue (like 7) and is well enough tested (unlike 9).

      Luckily it was already in the port system (just as 7,9, debian ,gentoo and suse 9.1) so it was "easy" to make that the standard port (linux_base). Perhaps when Fedora gets in the ports that will become the standard for the linux emulation.

      BTW FreeBSD (like any other BSD) is not a distro, it is an OS.
      The difference in words is subtile but for everything else it is a real different way of thinking.

      --
      Martin P. Hellwig

    4. Re:Why RedHat 8? by endx7 · · Score: 3, Informative

      The biggest reason why they changed from rh7 as default in ports to rh8 was that rh7 had an unpatched vulnerability. Redhat seems to have no interest in maintaining and updating these outdated versions, so the default had to change.

      It probably wouldn't be terribly hard to get FC3 working as a base since it, like the other redhat-related releases that we have already, use rpms, which we already know how to handle. Although, I haven't tried it, so I can't tell you for definite.

    5. Re:Why RedHat 8? by TheGratefulNet · · Score: 3, Interesting

      rh7 was a hack. its emulation was very broken for me (see my mp3 encoder post).

      rh8 libs and such finally make things work.

      in short, they did The Right Thing.

      --

      --
      "It is now safe to switch off your computer."
    6. Re:Why RedHat 8? by cant_get_a_good_nick · · Score: 1

      I can't say "why RH8" but I can give one issue that is sufficient to say "Why not 7.3" (which is one of your options) - g++296. The g++ issue has proven to be a major PITA for RH 7.3. The system compiler is a redhat fork of gcc, is incompatible with everything both before and after it, and 7.3 is already end of lifed, so no support from redhat. You's stuck with a system compiler with absolutely zero support, outside of some guys from Fedora that keep a compat RPM around, that you'd have to backport all their changes into your package because the specfile is different (being a compat package and all).

    7. Re:Why RedHat 8? by molnarcs · · Score: 2, Interesting

      Of course, you are right, thanks.

  2. Requiem for the FUD by AgainstTheFUD · · Score: 1, Offtopic
    ... facts are facts. ;)

    FreeBSD:
    FreeBSD, Stealth-Growth Open Source Project (Jun 2004)
    "FreeBSD has dramatically increased its market penetration over the last year."
    Nearly 2.5 Million Active Sites running FreeBSD (Jun 2004)
    "[FreeBSD] has secured a strong foothold with the hosting community and continues to grow, gaining over a million hostnames and half a million active sites since July 2003."
    What's New in the FreeBSD Network Stack (Sep 2004)
    "FreeBSD can now route 1Mpps on a 2.8GHz Xeon whilst Linux can't do much more than 100kpps."

    NetBSD:
    NetBSD sets Internet2 Land Speed World Record (May 2004)
    NetBSD again sets Internet2 Land Speed World Record (30 Sep 2004)

    OpenBSD:
    OpenBSD Widens Its Scope (Nov 2004)
    Review: OpenBSD 3.6 shows steady improvement (Nov 2004)

    *BSD in general:
    Deep study: The world's safest computing environment (Nov 2004)
    "The world's safest and most secure 24/7 online computing environment - operating system plus applications - is proving to be the Open Source platform of BSD (Berkeley Software Distribution) and the Mac OS X based on Darwin."
    ..and last but not least, we have the cutest mascot as well - undisputedly. ;)

    --
    Being able to read *other people's* source code is a nice thing, not a 'fundamental freedom'.

    1. Re:Requiem for the FUD by BossMC · · Score: 5, Interesting

      Dear AgainstTheFUD (840249), Being a FreeBSD user, I find myself reading the Slashdot BSD section once in a while. In light of the fact that your posts are somehow modded above 0, I end up reading your same stupid post over and over again. This is becoming a nuisance, as it is irrelevant to the story. At least the *BSD is dying trolls are modded down, thus shielding my eyes from "The FUD." I am politely asking you to shut the hell up. You are not providing a service; you are feeding the trolls in a routine fashion, and I hate it. Stop. Thanks in advance.

    2. Re:Requiem for the FUD by AgainstTheFUD · · Score: 0, Offtopic

      Dear BossMC (696762),
      definitely you're not "politely asking", and I really don't think that's a "stupid post" either, considered what it contains and how it has been modded up in the past threads..

      Anyway, from now on I'll post it at 0, adding a one-line request not to mod it up, so that it stays under the +1 threshold - and that is actually the best thing, agreed, since that post is not meant to annoy, it's meant to dispel the "BSD is dying" FUD (FUD without quotes, because that's what it is).

      But when you say it's useless, you're plain wrong. FUD can hurt, unless it's quickly dispelled.
      And this is not troll-feeding by any means, since it's not a reply to a troll (that most often, I agree, would just be a counterproductive waste of time).

      --
      Being able to read *other people's* source code is a nice thing, not a 'fundamental freedom'.

  3. Re:Kreskin said it ! by chinhngt · · Score: 2, Interesting

    May be you miss a thing, FreeBSD is not a commercial project/OS. The market share or some other shits is not a goal of FreeBSD (and maybe it's also right for others *BSD). So, please stop trolling here. I use both Windows and FreeBSD, and I love them, I don't care if they are popular or not. They help me solve my problems, help me understanding more prety things and that's enough.

    --
    MS-DOS since 6.0, Windows since 3.1, Novell Netware since 4.5 and FreeBSD since 4.5
  4. linux emulation FINALLY WORKS! by TheGratefulNet · · Score: 3, Interesting
    yay!

    the issue I had was with some closed-source (sigh) software that was linked against old old libc. it was a $200 mp3 encoder that I bought and ran fine under RH6.x. but never under later versions. even running this binary under modern LINUXs caused problems. this being the best encoder I have ever heard - and having paid $200 of my own money for it - I really wanted this to work. and since I'm now a 100% freebsd user, I needed this to work with bsd.

    it does now. I'm sooo happy about it. finally I can get rid of all my linux compute-servers on my mp3 render farm. they are now all 4.11 bsd boxes and couldn't be happier.

    I'll probably submit this to the bsd guys, but it would be nice if they included these files as well. I needed them for this last level of linux emulation:

    compat/linux/lib/libc.so.5
    compat/linux/lib/lib m.so.5
    compat/linux/lib/ld-linux.so.1

    those get you libc (not glibc) compat, from what I can tell. when I did an LDD on the mp3 encoder binary, it showed this:
    /usr/local/bin/mp3enc31:
    /lib/libNoVersion.so.1 => /lib/libNoVersion.so.1 (0x280ad000)
    libm.so.5 => /lib/libm.so.5 (0x280b3000)
    libc.so.5 => /lib/libc.so.5 (0x280bb000)
    libc.so.6 => /lib/libc.so.6 (0x28184000)
    /lib/ld-linux.so.1 => /lib/ld-linux.so.1 (0x2809a000)
    this is the first time since freebsd 3.4 (I think) that I've gotton this old linux binary to run under freebsd.

    again, yay!

    great work guys. you made my week.

    --

    --
    "It is now safe to switch off your computer."
    1. Re:linux emulation FINALLY WORKS! by TheGratefulNet · · Score: 1

      oh, one gotcha. I see TONS of these in my syslog:


      linux: syscall mmap2 is obsoleted or not implemented (pid=39894)


      so maybe there is still more work left to be done..

      --

      --
      "It is now safe to switch off your computer."
  5. 2nd of 3 "Release Candidates"? by r7 · · Score: 3, Insightful

    Can someone clarify FreeBSD's terminology? I thought a release candidate was different from a beta (known in FreeBSD-speak as a -STABLE).

    1. Re:2nd of 3 "Release Candidates"? by ArbitraryConstant · · Score: 1

      I think a beta means "enough of the stuff is there for us to want the public to test it". RC means "if the problems are cleared up we can release this unchanged".

      --
      I rarely criticize things I don't care about.
    2. Re:2nd of 3 "Release Candidates"? by Anonymous Coward · · Score: 0

      Beta is before RC, of course. I think the big difference is that the betas have debugging turned on.

    3. Re:2nd of 3 "Release Candidates"? by TheRaven64 · · Score: 5, Informative
      Can someone clarify FreeBSD's terminology? I thought a release candidate was different from a beta (known in FreeBSD-speak as a -STABLE).

      Wrong. -STABLE and -RELEASE are two different things. FreeBSD is divided into 3 categories of branch.

      -CURRENT This is the bleeding edge. Code here will probably work. More or less. It may break, or it may only be partially functional. This branch should not be used on production machines, since there is no guarantee that changes to the -CURRENT branch will not break things. There is usually one -CURRENT branch for each major release in active development (e.g. 4-CURRENT and 5-CURRENT) -STABLE Changes to -CURRENT that have undergone sufficient testing to be deemed stable are moved into the corresponding -STABLE branch. There is no restriction on the kind of changes that can be made to -STABLE except that they are not allowed to break things. -RELEASE These branches start life as snapshots of -STABLE. Once a -RELEASE branch has become a release (e.g. 4.10-RELEASE) the only changes allowed to it are security and bug fixes. No feature enhancements are allowed. If you have a production system, it is usually better to track a -RELEASE than to track -STABLE because, although -STABLE is not supposed to break anything, it is not possible to test it with every possible combination of hardware and software. Beta and release candidate builds are stages between a -STABLE branch becoming a -RELEASE branch. Once build is named a beta, new features are not (usually) allowed to be added. When it is named a release candidate, it is even harder to add changes. Ideally, a release candidate will, after a period of testing, be renamed a -RELEASE.
      --
      I am TheRaven on Soylent News
    4. Re:2nd of 3 "Release Candidates"? by endx7 · · Score: 2, Informative

      Well, not only that, but -RELEASE can refer to -CURRENT snapshots as well (such as the early 5.x releases when 5.x was still -CURRENT). Also, after a certain amount of time, -STABLE branches become errata branches. 4.x has become this. You basically come out with: "Production Release" (STABLE), "Technology Preview" (CURRENT), and "Production (Legacy) Release" (errata, a type of STABLE).

      Also, there is only "one" -CURRENT, at least in terms of CVS at least. This is HEAD and the main cvs trunk, and that is where -CURRENT lives. There are no separate -CURRENT branches; when -CURRENT gets branched the branches become -STABLE or -RELEASEs. -CURRENT only gets a version number as the next upcoming "branch". The only way you can find other "CURRENTs" is by going up and down the trunk.

      I had a nice "ascii" tree laid out which explained it better, but slashdot shot it down with its lame lameness filter.

      Also, this is the way things are laid out today as I can see it. Releases/branches may have been done differently in the past.

    5. Re:2nd of 3 "Release Candidates"? by r7 · · Score: 1

      Wrong. -STABLE and -RELEASE are two different things

      I think you missed my point. Obviously -STABLE is not a release. But going by FreeBSD's terminology it's not a release candidate either. The category before RC is BETA. By that common definition -STABLE is no different from BETA whereas -CURRENT is ALPHA.

      My main question was how do you have 3 RCs without the first 2 not being RCs at all?

      Really looks like a bad case of NIH to me.

      R7

    6. Re:2nd of 3 "Release Candidates"? by Anonymous Coward · · Score: 0

      You're confusing things. STABLE would be like a BETA except that it is not a release at all. It is just the name of a development branch! So is current! They are always moving targets.

      Yes, CURRENT and STABLE could be thought of as continuous ALPHA and BETA development branches. This makes sense because Release Candidates and Releases are culled from these branches, but they are still not releases themselves. Just branches.

      My main question was how do you have 3 RCs without the first 2 not being RCs at all?

      What??

      Really looks like a bad case of NIH to me.

      What??

  6. No Linux Base 8 package yet? by Anonymous Coward · · Score: 0

    Usually with a Linux base update there is a package for it. So far the only ones available are:

    linux_base-6.1_6
    linux_base-7.1_7

    The package spare those of us with limited bandwidth from having to download a billion rpms and the tools needed to manage those rpms.

  7. FreeBSD Release Engineering by bsd4me · · Score: 1

    The difference has to do with the types of changes that can be committed. Basically, it is harder to get a change approved after the RC stage.

    Check out the FreeBSD Release Engineering page for more info.

    --

    (S(SKK)(SKK))(S(SKK)(SKK))

  8. Re:For whom by ulib · · Score: 1, Funny
    These are the latest data I could find about FreeBSD market share - and they say it's gaining it.
    Nearly 2 Million Active Sites running FreeBSD (July 2003)
    "[FreeBSD] is the only other operating system [the other ones are windows and linux] that is gaining, rather than losing share of the active sites found by the Web Server Survey."

    I think it's true that market share has little importance for the BSDs, but before taking for granted what a troll says, it's always good to check it out. ;)

    One more thing: I don't think that guy simply "wants to troll" as you put it. Since his/her/its FUD-spreading activity has been going on for *years*, that would probably qualify as something else.
    (Of course I wouldn't completely rule out the possibility of a mental issue :)
    --
    Being able to read *other people's* source code is a nice thing, not a 'fundamental freedom'.

  9. Re:For whom by chinhngt · · Score: 1

    Oh, thank you a lot for your comment. I'm just new here and I really misunderstand the situation :)

    --
    MS-DOS since 6.0, Windows since 3.1, Novell Netware since 4.5 and FreeBSD since 4.5
  10. Same old FUD... by Anonymous Coward · · Score: 0

    Same old FUD, that has been disproved countless times...

  11. Benchmark: NetBSD 2.0 beats FreeBSD 5.3 in server by hubertf · · Score: 2, Interesting
    ``With the recent releases of NetBSD 2.0 and FreeBSD 5.3 operating system, many new and exciting features have been implemented. Both criticism and commendation on performance, reliability and scalability have been directed towards these releases.

    This paper presents a suite of benchmarks and results for comparing the performance of these operating systems. The benchmarks target core operating system functionality, server scalability and thread implementation. These benchmarks are useful server-based criteria for demanding applications such as loaded webservers, databases, and voice-over-IP (VoIP) media relays. The results indicate that NetBSD has surpassed FreeBSD in performance on nearly every benchmark and is poised to grab the title of the best operating system for the server environment.''

    Full paper: http://www.feyrer.de/NetBSD/gmcgarry/

  12. Re:Benchmark: NetBSD 2.0 beats FreeBSD 5.3 in serv by Chreo · · Score: 1

    "The results indicate that NetBSD has surpassed FreeBSD in performance on nearly every benchmark and is poised to grab the title of the best operating system for the server environment."

    While an interresting UP benchmark it in no way says anything about performance for SMP machines and 64-bit CPUs. That is what matters for most servers today (at least those that would be suitable for a new OS) and that's where all servers will be tomorrow.

    --

    Life is what happened when Good Intentions met Harsh Reality (the brother of the more infamous Chaos).
  13. Re:Benchmark: NetBSD 2.0 beats FreeBSD 5.3 in serv by setagllib · · Score: 1

    FreeBSD is already known to have made a lousy AMD64 implementation, a lousy SMP implementation (which, on 2-way and probably 4-way SMP machines, is actually SLOWER than NetBSD 2's giant lock model), and haven't even finished supporting their new kernel facilities on Sparc64 and Alpha.

    So if this test was even possible on a 64 bit CPU in SMP mode, it wouldn't save FreeBSD. The source is out there though, so why not run it yourself? Of course it won't help because all of those are UP-centric micro benchmarks, and you'll just have to run, say, an Apache or MySQL bench.

    We're waiting for your report eagerly.

    --
    Sam ty sig.
  14. Re:Benchmark: NetBSD 2.0 beats FreeBSD 5.3 in serv by setagllib · · Score: 1

    Actually, I just re-read your post, and noticed you have no clue at all. Let me explain: an algorithm is an algorithm. It doesn't matter if it's running on a machine with one or two procs, one instance of the algorithm will still only run on one processor at a time. It doesn't matter if it's 64 bit or 32 bit, since NetBSD is 64-bit-clean and hence doesn't have nasty side effects; let's assume FreeBSD is up to scratch on this as well. The algorithms will still scale the same and, if the instruction horse power is equivalent, take the same time.

    What you said was "this is a great display of how a person can run, but it doesn't say anything about how he would run with a friend or on a Thursday!"

    --
    Sam ty sig.
  15. Re:Benchmark: NetBSD 2.0 beats FreeBSD 5.3 in serv by molnarcs · · Score: 1
    It's a pity that your first reference to the massive barrage of criticism FreeBSD received is to this guy's crappy journalism.

    On the other hand: nice (micro)benchmarks! Thanks :) It appears that FreeBSD developers know of these issues:

    Since the performance optimization on FreeBSD for the last few years, with features like SMPng, libpthread, and UMA, has been focussed on macro performance not micro performance, it's not surprising the micro performance requires tuning. However, there is lots of on-going work on this front so I'd expect to see continued improvement in the immediate (5.4) life time. There are a number of optimizations in 6.x that are on the merge path for 5.x that will directly impact the results in these measurements -- in particular, what is clearly a bug in the way mutexes are released on UP kernels that adds almost a hundred cycles to every mutex release operation. This was identified in my micro-benchmarking shortly after the release of 5.3, and may play a substantial part in the posted results, especially for the very micro benchmarks that involve kernel memory allocation.
    You may find the the rest here. It is also a pity that some troll spammed every single FreeBSD mailing list with a "haha, freebsd developers suxorz, especiall PHK and DES" kinda message. Reminds you anyone we know? :))))
  16. Re:Benchmark: NetBSD 2.0 beats FreeBSD 5.3 in serv by Chreo · · Score: 1

    If you read my post again then you must also have noted that I never mentioned algorithms but the notion parent used that "is poised to grab the title of the best operating system for the server environment."

    What I did not clarify is that I ment proper server tests with actual workloads where SMP machines are used. The benchmarks are mostly checking the microoptimisations of a UP machine and it is well known that the current state of FreeBSD 5 is not optimized towards that. I also assume that you have missed the bug where hundreds of cycles where wasted when doing Mutex releases. A lot has happened since 6-CURRENT was created and 5.4 is only looking nicer day by day.

    You also fail to realise that I in no way have any problems with NetBSD being faster (as I use it on my backup machine).

    However, as history with FreeBSD and Linux have shown, why do you think a BGL SMP implementation would scale better than a FGL implementation? Even given the clean lean source of NetBSD? Just curious.

    NetBSDs performance is looking very nice but don't make too sweeping assumptions about actual server performance based on this alone and that is also what the paper says in the end. More benchmarks needed.

    BTW, regarding the actual benchmarks, rwatson had an interresting comment about it http://lists.freebsd.org/pipermail/freebsd-perform ance/2005-January/001019.html

    --

    Life is what happened when Good Intentions met Harsh Reality (the brother of the more infamous Chaos).
  17. Re:Benchmark: NetBSD 2.0 beats FreeBSD 5.3 in serv by setagllib · · Score: 1

    Apologies, I guess I misunderstood your post as saying the benchmarks were run on the wrong kind of system, rather than the benchmarks being used for sweeping assumptions.

    So 5-STABLE is actually becoming worth using, you say? I'd like to try that, in fact I will when I can afford to (currently only two machines under my control and both are life-critical, for my life anyway). I've really wanted to get back into FreeBSD, it's highly usable and all, but my negative experience with 5.3 (yes, even tracking -STABLE for a month or so) put me off.

    Has anything been said on the topic of the new, stupid disk sync style? Unlike all other systems which sync their dirty buffers quickly and know about it, FreeBSD 5 now can generate MORE dirty buffers during syncing and has to wait for 3 consecutive "no really, it's all clear this time" checks before being satisfied; and each check is spaced about a second. This results in possibly 5-10 seconds spent just waiting for disk syncing, which is digusting compared to near-instant syncs in other systems.

    Anyway, does anyone want to run an Apache or other bench on a 64-bit SMP system with NetBSD 2_stable and FreeBSD 5.3-STABLE? Be worth a look I'd say. I wouldn't run a server based on small performance merit myself, it'd all come down to administration, cleanliness, security and stability... but then I don't pay for my hardware myself.

    --
    Sam ty sig.