Slashdot Mirror


FreeBSD 5.3-BETA2 available

Nirbo writes "One week after FreeBSD 5.3-BETA1, FreeBSD 5.3-BETA2, is now available to those wishing to update to the most current FreeBSD on the 5.x branch. It's available from the Main FTP servers, and probably a few more places by this point. BETA-3 is due out September 3rd, but for those who don't want to go a single day without updating, you can find snapshots (and the ISO images) here."

100 comments

  1. *BSD will live forever! by Nirbo · · Score: 5, Insightful

    Just because the *BSD's explosive growth is minscule compared to Linux's explosive growth, that hardly means it's dying...

    For every 10 Linux users, every 1 has enough sense to fall through the cracks in the Linux Kernel and land in BSD-country (See, we can troll too :D)

    Rather, the boom of Linux in recent history has sparked a lot of BSD numebrs to jump too :D... now if only we could get off such dependancies as Linux Compatibility for out Flash plugins, we'd be set as both a Linux-ally, and a Linux competitor...

    With 2.5 Million active sites according to Netcraft (Who also run BSD... coincidence? Not really.), *BSD is hardly dead... just too busy disputing the death rumours to really make a show of it's vast and productive life :D

  2. Definately a beta by Anonymous Coward · · Score: 2, Interesting

    Just like 5.3 BETA1, BETA2 does not detect my network card automatically, and nothing I do makes any difference (it's always been found by every Linux distribution and all other BSDs, including all previous releases of FreeBSD since 4.7).

    I can only hope that someone fixes this before it's released, because I've long been waiting to try a truely modern version of FreeBSD (with KSE, ULE and now X.org all as defaults).

    I guess it makes little difference in the long run, as I've mostly switched over to the (admittedly too new to realistically be used in a production environment, yet utterly promising) DragonFly BSD and Mac OS X.

    This version has been in the works for over three years now (5.x that is), and I am getting tired of waiting for something that could have been out and stable a year and a half ago were the developers not constantly adding to the feature list while trying to stablise the core architecture of the system.

    DragonFly seems to be doing better in this department (it looks as if thier "light weight kernel threading" subsystem has allowed them to almost completely multi-thread their network stack in roughly a one month period (the project itself being little over one year old) while the FreeBSD folks *still* have not made significant progress doing the same with 5.x (no, even with 5.3 there is more code that cannot function without the big giant lock than there is code that can run happily without it)).

    I can't wait for version 1.1 of DragonFly (due in some six to eight months). It'll be very interesting to see how far they've come at that time when compared to FreeBSD.

    1. Re:Definately a beta by Anonymous Coward · · Score: 0

      Why wait for DF 1.1 ? Download a snapshot today!
      It's a live CD so no harm done, but if you like it really than login in as installer and do your thing.

    2. Re:Definately a beta by BSDimwit · · Score: 2, Insightful

      Guess I don't understand why you think that your NIC being detected is the the end all be all for an OS. If you have been around a the BSD circles for a while you should know that it does not support as much hardware as Linux. However, what it does support is usually supported quite well. Instead of complaining about it, go to the store and buy one it does support, it's not like they are expensive...at the very least, see what you can do to get support for the NIC you are talking about. Open Source operating systems are open so that folks like you, can contribute code to fill in the known holes. If you aren't a programmer, fine, but look for other ways of helping. Yeah, FreeBSD 5-stable has been a long time coming, but like you said, there are alternatives for those who simply cannot wait.

    3. Re:Definately a beta by Anonymous Coward · · Score: 0

      Well smart guy, if you had of actually read my post, you'd see that I said that I've mostly switched over to both DragonFly and Mac OS X.

      However, version 1.1 of DragonFly should see some interesting things like a large part of the threaded/ports/message based VFS susbsystem, a fully multi-threaded and big giant lock free networking stack, a new and improved VFS based packaging system, asynchronous message passed system calls, the beginings of native kernel level clustering capability, meta-data journalling for all supported filesystems, N:M threading system based on the threaded message passing system, and most importantly of all, a stable (and unbeatably flexible and extensible) kernel API.

      I've been using DragonFly since February, and have been following it closely since it forked, so I am quite aware of what's in, what's going in, what's currently half-baked, and what beats the pants off of other operating systems.

      Please read more carefully before you post.

    4. Re:Definately a beta by Anonymous Coward · · Score: 0

      If you have been around a the BSD circles for a while you should know that it does not support as much hardware as Linux

      If you had actually read and understood his first post, you'd have noticed that he mentioned that FreeBSD has for nearly three years, fully supported his NIC.

      Learn to read.

    5. Re:Definately a beta by Homology · · Score: 1
      Just like 5.3 BETA1, BETA2 does not detect my network card automatically, and nothing I do makes any difference (it's always been found by every Linux distribution and all other BSDs, including all previous releases of FreeBSD since 4.7).

      Similar problem with my testing of 5.3 BETA1 : A wireless NIC that worked in current (when I tried it earlier this spring) is now not detected. Hope that is fixed with BETA2.

    6. Re:Definately a beta by tdelaney · · Score: 1

      Have you posted a bug report with your NIC, etc? It's unlikely to be fixed unless they know about it.

      Regressions happen regrettably, and no one has a large enough range of hardwre available to do all the testing themselves.

    7. Re:Definately a beta by MavEtJu · · Score: 1, Informative

      Just like 5.3 BETA1, BETA2 does not detect my network card automatically.

      You won't get much help if you don't give a little bit more information like which brand and which type.

      because I've long been waiting to try a truely modern version of FreeBSD

      If so, you would have known that you always had the possibility of running 5.2.1 and to keep current with the latests patches. Cvsup is your friend.

      by Anonymous Coward

      That's what I thought.

      --
      bash$ :(){ :|:&};:
    8. Re:Definately a beta by Brandybuck · · Score: 1

      Forget it. This guy posts the same rant on every forum, but never provides the information necessary to actually help someone solve his problem. This is a troll.

      --
      Don't blame me, I didn't vote for either of them!
    9. Re:Definately a beta by Anonymous Coward · · Score: 0

      You know, you can search the PR database. It appears you have not filed one as you claim to have - what is your pr number?

    10. Re:Definately a beta by SillyNickName4me · · Score: 2, Insightful

      Hmm, it would be interesting to know what network card you are having trouble with. This quite sounds like a bug to me.

      With regards to your comments about FreeBSD 5.x and Dragonfly, I'd like to mention a few things..

      - It is very easy to have a high speed of development in a new project. People are focussed on the project goals and there is little 'distraction' in the form of people actually using the project. It is about as difficult to keep an old project making progress because of the opposite conditions being true in general.

      - If KSE and ULE are such good ideas is debatable, but seeing your post, you are interested in trying them. This architecture took its time to develop, and if you followed the smp mailinglist in the last few years, you'd see that that development was not easy, and in fact, noone before FreeBSD managed to implement this architecture in a workable way (while it looks very promising in theory, in practise it comes with lots of nice little problems)

      I think Dragonfly is a very usefull addition to the *BSD family because of the exact work that you mention, a multithreaded network stack.
      It may bring more equally important new developments in the future if it can keep up its pase of development.

      > DragonFly seems to be doing better in this department (it looks as if thier "light weight kernel threading" subsystem has allowed them to almost completely multi-thread their network stack in roughly a one month period (the project itself being little over one year old)

      I did my own reimplementation of the FreeBSD network stack at some point so I do have some idea what the code looks like and what kind of work would be involved..

      The biggest part of it is properly splitting up the code, as it is now, it is mostly concentrated in a few HUGE functions that are almost impossible to maintain.

      From there to a multithreaded implementation is not such a big issue once you have settled on an architecture for multithreading inside the kernel.

      It seems that the method chosen by Dragonfly results in a lot less work in the kernel then what FreeBSD chose.

      > while the FreeBSD folks *still* have not made significant progress doing the same with 5.x (no, even with 5.3 there is more code that cannot function without the big giant lock than there is code that can run happily without it)).

      How much code can run without it is hardly relevant. How much time is spent running such code is of major relevance.

      This of course would suggest that the network stack is something to look at....

      At any rate, lightweight kernel threads lead to fast results for Dragonfly. If it will keep supporting that in the future is a question for me. Almost always such quicker solutions come to bite you a little bit later. If it does however then all the better. It is good to actually see multiple different branches of development for this.

    11. Re:Definately a beta by SillyNickName4me · · Score: 1

      Hrm... your submit button seems to have an auto repeat function.. tell me, how do you get it to do that?

    12. Re:Definately a beta by Brandybuck · · Score: 2, Interesting

      That is a supported card. It uses the "rl" Realtek driver. See p os=0&sektion=0&manpath=FreeBSD+6-current&format=ht ml> for more information. Searching the bug database I find... no open problem reports on this card! Are you sure you submitted a bug? The last reported bug on this card was in FreeBSD 4.2.

      Is this the SAME card you used sucessfully with FreeBSD 4.x? D-Link is notorius for changing the chipsets in their cards while keeping the model number. Make sure it's really a Realtek 8129/8139 chip. What does dmesg say? You are going to submit a problem report, right? Bitching about the quality of a BETA release without submitting a bug report is silly. Make sure you include the full output of dmesg in your problem report.

      --
      Don't blame me, I didn't vote for either of them!
    13. Re:Definately a beta by Anonymous Coward · · Score: 0

      You're calling this guy a member of the BSD community? Does that mean I can call most packet kiddies part of the Linux community? Give me a break.

    14. Re:Definately a beta by Anonymous Coward · · Score: 0

      You might be right. So, I'll try it in a couple years.

      You think I'm going to bet my company's ass on it now?

      That's what I thought.

    15. Re:Definately a beta by Anonymous Coward · · Score: 0

      "At least the slackware...folks hold civil conversations."

      Now I know you're talking through your hat.

  3. Fast... by JamesTRexx · · Score: 3, Insightful

    I'm quite impressed how quickly the beta's follow eachother. Even if changes between 5.2 and 5.3 aren't major. (haven't read the changelog though)
    It makes me wonder why it takes so much longer for Microsoft with all its resources to go from one beta to the next, even with all the software that has to be tested.

    --
    home
    1. Re:Fast... by x3ro · · Score: 3, Insightful
      It makes me wonder why it takes so much longer for Microsoft with all its resources to go from one beta to the next, even with all the software that has to be tested.

      I assume you're referring to beta versions of Windows? If so, remember that Windows is a kernel, window manager, desktop environment, set of APIs, blah blah blah, all in one. Imagine trying to change versions of not just FreeBSD itself, but also X.org, KDE/Gnome, and probably quite a few apps that aren't part of the OS but come bundled with it (eg Konqueror) .. that would be a better comparison.

      Of course the other reason would be bugs being shallower with more eyes etc, closed vs. OSS. But I'm inclined to think that the more significant contrast is OS-as-monolith vs. Unix-style small, atomic utilities. Not talking monolithic vs. micro kernels here .. I mean the OS as a whole, or in MicroSoft's case, as a product.

      --
      [ UNSIGNED NOT NULL ]
    2. Re:Fast... by JamesTRexx · · Score: 1

      Exactly what I was thinking of, if I think of all the components together as X and KDE/Gnome, etc., it still feels like it's going much faster than the complete package of Windows. The FreeBSD itself is smaller, but even then, a few weeks seems very short.

      --
      home
  4. Example "direct link" to 5.3-BETA2 .iso by Helevius · · Score: 4, Informative

    For the install CD, use:

    ftp://ftpX.freebsd.org/pub/FreeBSD/ISO-IMAGES-i3 86 /5.3/5.3-BETA2-i386-disc1.iso

    Replace "X" with 1 to 14 to use the US mirrors.

    For a "live CD" to test hardware compatibility, use disc2:

    ftp://ftpX.freebsd.org/pub/FreeBSD/ISO-IMAGES-i3 86 /5.3/5.3-BETA2-i386-disc2.iso

    Helevius

    1. Re:Example "direct link" to 5.3-BETA2 .iso by discogravy · · Score: 1

      about the 2nd disc (the LiveCD) thing: does it just boot the OS and drop you on the command line? or does it do X/windowing stuff a la Knoppix etc?

    2. Re:Example "direct link" to 5.3-BETA2 .iso by Eil · · Score: 2, Informative


      It actually boots into sysinstall. Far as I can tell, the only difference from the install CD is that it doesn't contain any packages but does include a live filesystem that you can use to repair a broken system.

    3. Re:Example "direct link" to 5.3-BETA2 .iso by SillyNickName4me · · Score: 1

      It would better be called the 'rescue cd'

    4. Re:Example "direct link" to 5.3-BETA2 .iso by Eil · · Score: 1


      I concur.

  5. Re:Beta 3 Due This Week by Anonymous Coward · · Score: 4, Insightful

    I, FreeBSD, have NOT failed:

    --To support SMP
    FreeBSD has SMP support and has for a long long time. SMPnG is SMP Next Generation. It's a complete overhaul of a feature that's already supported.

    --To generate media attention
    Mac OS X is based on BSD. That's generated lots of media attention. I should also mention that slashdot is a form of media, and has gotten your attention.

    --To spawn a professionally managed distribution
    Did I mention mac OS X yet? No, oh. How about BSDi? That doesn't count? Oh. Well, I'll have to argue that FreeBSD is much more professionally managed than most Linux distro's (which are a hodgepodge shit-show of amateur code).

    --To innovate
    FreeBSD SoftUpdates. Ports (which the beloved Gentoo copied and is what most people claim is Gentoo's best feature).

    --To be relevant.
    BSD is generating news on slashdot, therfore it is relevant and very very important.

  6. Re:Why BSD is dying by Anonymous Coward · · Score: 2, Funny

    Just because there isn't a ________ community on slashdot, doesn't mean that community doesn't exist.

    I guess by your logic we can conclude windows is dying as well. There's never a positivly moderated post about Microsoft, therefore windows must be dying.

  7. Re:beta2 changelog? by Anonymous Coward · · Score: 0, Troll

    Good News Everyone!
    Fact: There are 307 FreeBSD developers. And there never was a fistfight
    Fact: X.org does in fact support all of the BSDs
    Fact: Michael Curry doesn't even know what netbsd is
    Fact: There are over 55 BSD books
    Fact: Gimp has always worked on all BSDs and always will.
    Fact: OpenBSD has had the fewest security holes of all OS's
    Fact: Truth is not relative

  8. Re:*BSD is dying by Anonymous Coward · · Score: 1, Informative

    Good News Everyone!
    Turns out that *BSD is stronger than ever!
    According to an Inernetnews article, Netcraft has confirmed that *BSD has "dramatically increased its market penetration over the last year."
    There has been a steady increase in *BSD developers over the past decade.
    There are currently 307 FreeBSD developers as of the 2004 core team election.
    You can read more about FreeBSD here

    If you would like to try out a BSD, you can download: FreeBSD, OpenBSD, NetBSD, or DragonflyBSD
    Enjoy!

  9. Re: by DashEvil · · Score: 3, Insightful

    Have you submitted a bug report of any kind about this? That is what the BETA is for, and it is why it has the BETA tag.

    While I respect your opinion, I do wish you would hold judgement until the final release is made.

    --
    -If God wanted people to be better than me, he would have made them that way.
  10. good sources for BSD newbs OTHER than Handbook? by discogravy · · Score: 4, Informative
    I'm looking for lots of short how-tos and best-practices stuff (security, notably,) and not just "do this to that file and killall -HUP the service to affect changes" -- I'd like some theory behind some of it so that I can understand the whys and hows a BSD system is different from a Linux or Solaris box.

    There's BSDWiki, which I contribute to now and again, but it's still early in that project's development and although I know a lot of linux stuff, I am not nearly as conversant in the differences between FreeBSD and Linux, and quite frankly, the handbook makes my eyes gloss over.

    1. Re:good sources for BSD newbs OTHER than Handbook? by IamInsane · · Score: 3, Informative

      Here's a list of links that you might find useful:

      Interesting read's for all newbies to FreeBSD:
      http://www.freebsd.org/projects/newbies. html

      Some tutorials, very short list but interesting none the less:
      http://freebsdaddicts.org/

      Some outdated but still usefull articles here:
      http://www.freebsddiary.org/

      Excellent information on setting up a new FreeBSD host
      http://users.rcn.com/rneswold/fbsd-init.html

  11. The Design and Implementation of the FreeBSD OS by ubiquitin · · Score: 4, Informative
    www.mckusick.com/FreeBSDbook.html

    The book is divided into five parts, organized as follows:

    Part I, Overview

    Three introductory chapters provide the context for the complete operating system and for the rest of the book.

    History and Goals, sketches the historical development of the system, emphasizing the system's research orientation.

    Design Overview of FreeBSD, describes the services offered by the system, and outlines the internal organization of the kernel. It also discusses the design decisions that were made as the system was developed.

    Kernel Services, explains how system calls are done, and describes in detail several of the basic services of the kernel.

    Part II, Processes

    Process Management, lays the foundation for later chapters by describing the structure of a process, the algorithms used for scheduling the execution of the threads that make up a process, and the synchronization mechanisms used by the system to ensure consistent access to kernel-resident data structures.

    Memory Management, the virtual-memory-management system is discussed in detail.

    Part III, I/O System

    I/O System Overview, explains the system interface to I/O and describes the structure of the facilities that support this interface.

    Following this introduction are four chapters that give the details of the main parts of the I/O system.

    Devices, gives a description of the I/O architecture of the PC, describes how the I/O subsystem is managed, and how the kernel initially maps out and later manages the arrival and departure of connected devices.

    Local Filesystems, details the data structures and algorithms that implement filesystems as seen by application programs as well as how local filesystems are interfaced with the device interface described earlier.

    The Network Filesystem, explains the network filesystem from both the server and client perspectives.

    Terminal Handling, discusses support for character terminals, and provides a description of the pseudo-terminal device driver.

    Part IV, Interprocess Communication

    Interprocess Communication, describes the mechanism for providing communication between related or unrelated processes.

    Network Communication and Network Protocols, are closely related, as the facilities explained in the former are implemented by specific protocols, such as the TCP/IP protocol suite, explained in the latter.

    Part V, System Operation

    Startup and Shutdown, discusses system startup and shutdown and explains system initialization at the process level, from kernel initialization to user login.

    --
    http://tinyurl.com/4ny52
  12. Re:Beta 3 Due This Week by SillyNickName4me · · Score: 2, Informative

    First of all, congrats on writing an actually somewhat funny troll.

    As is the case with most trolls, the 'information' provided is incorrect. Lets look at the specifics..

    > --To support SMP

    FreeBSD has supported SMP for years, and 5.3 still does. You can argue all you want about which smp implementation is better, but that doesn't change that it is supported.

    > --To generate media attention

    Your post was a reply to one form of media attention it is getting. Don't think it needs any further comments.

    > --To spawn a professionally managed distribution

    Ah... like the 200+ incompatible Linux distributions? I'd seriously look at this one again because this is one of the things where it does better then any linux distribution.

    > --To innovate ...

    > --To be relevant.

    Maybe not to you. I'd hope you refrain from using for exampel Yahoo and Hotmail in the future tho.. else it might just become somewhat relevant for you also.

    At any rate.. I had a bit of a chuckle, you at least found a funny way for posting your nonsense.

  13. A valid criticism by nutznboltz · · Score: 1

    When I first used mergemaster I thought it was the greatest thing since before that I had to tediously hand-pick through /usr/src/etc on OpenBSD and NetBSD in order to keep /etc up-to-date.

    But now the luster has worn off and I'm seeing things a bit differently especially after using Gentoo's etc-update.

    So what about mergemaster?

    1) split screen mode - mergemaster splits your screen into a left and right half with no scrolling. You get a whopping 40 columns of truncated file to look at on an 80 column display in single-user mode with no network or GUI. The first thing you will notice on the screen is the CVS tags which will almost help you tell which is the new and which is the old file except that they are cut off at 40 columns

    2) "l for left" and "r for right" - you type the "l" for "left" with your right hand and the "r" for "right" with your left hand. Screws me up since I have typing skills.

    1. Re:A valid criticism by Anonymous Coward · · Score: 0

      When I first used mergemaster I thought it was the greatest thing since before that I had to tediously hand-pick through /usr/src/etc on OpenBSD and NetBSD in order to keep /etc up-to-date.

      uname -a
      NetBSD geonosis 2.0_BETA NetBSD 2.0_BETA (GEONOSIS) #0: Fri Jul 9 19:23:31 CEST 2004 root@geonosis:/usr/src/sys/arch/i386/compile/GEONO SIS i386

      ---snip---

      ETCUPDATE(8) NetBSD System Manager's Manual ETCUPDATE(8)

      NAME
      etcupdate - update the configuration and startup files in /etc

      SYNOPSIS
      etcupdate [-ahlv] [-b srcdir] [-p pager] [-s srcdir] [-t temproot]
      [-w width]

      DESCRIPTION
      etcupdate is a tool that lets the administrator update the configuration
      and startup files in /etc (and some other directories like /dev, /root
      and /var) without having to manually check and modify every file. The
      administrator should run this script after performing an operating system
      update (e.g. after running make build in /usr/src or after extracting new
      binary distribution files) to update to the latest configuration and
      startup files.

      ---snip---

      have a nice day.

    2. Re:A valid criticism by Matty_ · · Score: 1

      This isn't really the fault of mergemaster as much as it is simply sdiff, which mergemaster calls to handle the the merging.

      I do know what you mean. It doesn't work very well when you're in the regular 80x24 mode on your console, but I usually just remember that the left version if the old copy, and the new version is on the right.

    3. Re:A valid criticism by Homology · · Score: 1
      When I first used mergemaster I thought it was the greatest thing since before that I had to tediously hand-pick through /usr/src/etc on OpenBSD and NetBSD in order to keep /etc up-to-date.

      OpenBSD has mergemaster in ports, while NetBSD uses etcupdate.

  14. linux lamers by hugo_pt · · Score: 1

    ... strike back again. Get a life idiots

  15. Re: by BasharTeg · · Score: 4, Funny
    The beta is broken, plain and simple. No networking ability means it's not ready for prime time. Can you understand that?

    BETA. B-E-T-A. BETA TESTING. BETA
    • BETA


    B
    E
    T
    A

    Can you understand that?
  16. Re:beta2 changelog? by hugo_pt · · Score: 0, Troll

    Fact: BSD's dont have several critical security advisories which could lead to root access EVERY months Fact: Linux apps running under emulation will sometimes run faster on BSD than on native linux Fact: Linux community = bunch of script kiddies & pseudo-leet (and as we can see, dozens of trolls) ; BSD Community = Technical guys Fact: FreeBSD is not dead, 4.11 is still coming, 5.3 is near the release.

  17. Re: by Anonymous Coward · · Score: 0

    You're an idiot. Of course I do, but am I supposed to sit here with my thumbs up my ass, because this might still be an issue AFTER the beta, even with problem reports.

    Do *you* understand? Thought not.

  18. Easy, buddy by Anonymous Coward · · Score: 0

    "Fact: Linux community = bunch of script kiddies & pseudo-leet (and as we can see, dozens of trolls) ; BSD Community = Technical guys"

    I think both FreeBSD and Linux are pretty cool, but it is not in anyone's interest to talk trash like this. Do you want people saying that BSD users are arrogant? I think not. I have two machines at home, my main Debian box, and another one that I set up with FreeBSD out of curiosity and a general desire to broaden my knowledge. I like both, although I must admit I have a much better grasp of Debian.

    1. Re:Easy, buddy by Anonymous Coward · · Score: 0

      looks like the guy said that there were actually good linux sysadmin/users but that most of them that are trolling around are just a bunch of lamers that think they are leet coz they installed fedora without pictures and drawings.

  19. Re:beta2 changelog? by Anonymous Coward · · Score: 1

    Funny, I just checked amazon.com and there is 1027 *bsd related books.
    Funny^2, me and a bunch of freebsd users use gimp for ages and never saw a single problem with it.
    Funny^3 me and a bunch of freebsd users use oo.org, staroffice, abiword, etc without any problem.
    Funny^4, if you just check www.bsdforums.org you will see a minium fraction of the total bsdusers (55K registred).
    Funny^5 X.org will be the default X server for 5.3 release and it is working as well as in linux.

    Regarding to the media, that's a big difference. BSD community is focused on getting things to work and has a commitment to technical excellence while the linux community has few good sysadmin that work with the linux the way it should be used and you have loads of pseudo-leet-hackers and non-sense troll /. posters like you, heh.
    Go get a life boy.

  20. "mergemaster considered harmful" by kace · · Score: 3, Insightful

    mergemaster is the most painful part of a FreeBSD upgrade. 20 minutes of paging through files that I've never touched and probably never will (with a couple of minor exceptions).

    I see its purpose, but it could be made much less painful by putting most of those files into /usr/defaults/ and then letting the user put his overrides into a file of the same name in /etc/. Just as we do with rc.conf. Throw in a switch to mean "update everything in /etc/defaults/ without asking me" and everyone should be happy. (That is, the curious and the masochists can still page through every changed config' file.)

    K.C.

    1. Re:"mergemaster considered harmful" by Ecks · · Score: 1

      Agreed, in fact the FreeBSD team should declare that they own the contents of the /etc/defaults directory.. All files within should be chflags schg so that you would have to utterly clueless to actually edit any of them. Finally the default action of make installworld should be to completely wipe new files in /etc/defaults with new stuff from source.

      --ecks

  21. Ahem. Tap Tap. Is This Thing On? by Anonymous Coward · · Score: 1, Funny

    Erm. Ahem. Tap tap tap.

    Attention, everyone who responded to this post.

    YOU HAVE BEEN TROLLED. YOU HAVE LOST. HAVE A NICE DAY.

    Or, abbreviated for convenience: YHBT. YHL. HAND.

    See http://en.wikipedia.com/wiki/YHBT

  22. OK what NIC is it? by BSDimwit · · Score: 2, Informative
    No where in your post do you mention which card it fails to detect. I happen to have an nforce2 chipset with NVIDIA's proprietary NIC built in, which is also not supported, but I also have another NIC installed that it does support...so while I agree with you that networking is of prime importance, there are viable workarounds such as the one I mentioned.

    If you are truly trying to get a working version of FreeBSD onto your system, I suggest you go back to the one of the -RELEASE versions you have had success with in the past. Otherwise, post your findings to the bug database and be patient for just a while longer.

    Since you are obviously much more enamored with Dragonfly, Linux, and the other flavors of BSD, I am still puzzled as to why you are even bothering with FreeBSD in the first place. You obviously are more interested in bashing FreeBSD than getting it running on your system.

  23. intel e1000 by preposterity · · Score: 1, Interesting

    let's hope they've fixed those buffer problems with the intel e1000 network cards. i'm tired of having to restrict my card to 100mbps

  24. Re:Beta 3 Due This Week by SillyNickName4me · · Score: 1

    Reading is very difficult isn't it?

    I bet it takes you so much energy that you give up after a few words, and consequentely also fail to say anything relevant or usefull at all.

    Ah well, whats in a name.

  25. YHBT YHL HAND by Anonymous Coward · · Score: 0

    you fell for a troll

  26. Re:Beta 3 Due This Week by Loki_1929 · · Score: 1

    Complete and utter troll, obviously, but this:

    "hodgepodge shit-show of amateur code"

    made me laugh my ass off. Thank you, dear troll.

    --
    -- "Government is the great fiction through which everybody endeavors to live at the expense of everybody else."
  27. Re:Beta 3 Due This Week by SillyNickName4me · · Score: 2, Informative

    > Yeah, it really pisses me off that The GIMP only works on two distros.

    > FFS, get over it, man. There's no "incompatible Linux distributions". You name me THREE open source apps (exclusing the obvious installers and config tools) that only work on one distribution.

    Ignoring the point is not really going to help.

    Yes, I can run vrtually any opensource package on any linux distribuion and any bsd distribution.

    Since each and every linux distribution comes with a slightly (or at times wildly) different set of libraries and versions of libraries, there is no guarantee that you can take a binary from distrivution x, and expect it to run without any hastle on distribution y. Yeah, you can definitely get it to work by installing extra libraries or recompiling the thing.

    > Struggling? Thought so. Your talk about "incompatible distributions" is ignorant and ill-informed. 99.99999% of open source apps work on all distros without any hassle.

    Did you ever build comemrcial Linux software? I did. I also did the installer. There is a good reason for most commercial software either supporting only a few distributions (officially at least) or being statically linked to most stuff they happen to depend on.

    You obviously never looked at what those nice installer scripts do but you may find funny things as binary distributed software installing differently based on for example your version of gcc, glibc and a few other such things.

    > ATEOTD, Linux has broader hardware support,

    Possibly, especially when it comes to non x86 hardware.

    I use fairly modern x86 hardware for a whole variety of purposes (including hosting and network infrastructure), and I have yet to encounter a device that I actually want to use that is not supported.

    The same can be said about Linux, so no difference there as long as you keep to a supported platform of course..

    > runs faster, has better SMP,

    If Linux runs faster is rather debatable. My test server runs both FreeBSD current and gentoo with linux 2.6 kernel in a multiboot config. (it is a dual cpu machine btw)

    Running exactly the same Apache configuration, in both cases compiled from source, results in the fbsd version handling between 5 and almost 20% more requests/time on a mix of static and dynamic (php and perl) content.

    I have the same systems installed on my workstation, an adm athlon xp 2600+ with 512mb and a gforce4 mx.. When running FreeBSD 5, my favorite multiplayer fps (Enemy Territory) runs substantially better then when running Linux (somewhat interesting seeing how this is in fact a Linux binary)

    Both annecdotal evidence at best, but definitely 2 cases where Linux doesn't run faster.

    With regards to SMP, esp. on non x86 hardware Linux does a lot better, but then, FreeBSD doesn't run on most such hardware to begin with.

    If this is true for x86 hardware is debatable, and I'd like to see what things look like once 5.x has been 'stable' for a while, and I keep an eye on dragonfly and their smp work.

    I have seen some performance comparisons that were at least trying to measure things instead of basing themselves on annecdotal evidence.. I have yet to see one that is not flawed in how it implements its tests tho.

    > has more available commercial software,

    Almost all of which also runs on FreeBSD tho,and usually with less trouble, and at times with better performance, so no reason to use one over the other.

    > has wider backing,

    Definitely. Windows has even wider backing..

    > and most of all IS SUPPORTED LONGER

    And needs to be supported longer also.

    But let's see. Versioning in FreeBSD works somewhat different then in Linux since there is a much closer relation between kernel and userland. Transition between versions is rather painless (unlike upgrading a redhat installation for example) and one of my servers here has not seen an install cd for half a decade now, nor has it been d

  28. FreeBSD by oKtosiTe · · Score: 2

    I have never used a BSD before, but I think I'll give it a try when this release hits stable, as I've read a lot of good stuff about FreeBSD. What will be the first differences I will encounter? Is it easy to set up a fully functioning GNOME environment on FreeBSD?
    Thanks in advance.

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

      Yes there is, you can checkout the freebsd gnome project:

      www.freebsd.org/gnome/

    2. Re:FreeBSD by TheRaven64 · · Score: 1
      The first thing you will notice is that the documentation is actually both useful and readable. The second thing you will notice is that the community has no patience with people who haven't bothered to read it. Make sure you at least skim the FreeBSD handbook before you ask for help.

      The first thing I noticed is that sound actually worked sensibly. FreeBSD includes sound mixing in the kernel, presenting multiple /dev/dsps which can each be accessed independently by an application (e.g. the GNOME and KDE sound daemons, xmms and a game can all make sounds at once, even on sound cards that don't support hardware mixing), something that was not present on Linux last time I looked.

      The second thing you will probably notice is that a lot of things you are used to finding in /etc, or /bin are now in /usr/local/*. Only things that are maintained by the FreeBSD project are in the root FS. Everything that is third party (e.g. bash, Apache) is in /usr/local/*. If you are using any third party software (`ports') then install the portupgrade package* and read the documentation - you'll find it makes keeping things up to date a whole lot easier.

      Finally, you will probably notice that the init system is significantly different from the SysV init used by Linux

      * Software that is not part of the base distribution is referred to as a port if built from source, or a package if installed from a binary. The two can be used interchangeably, and portupgrade includes the ability to grab packages when available and ports when not (packages may not appear for a day or so after ports do).

      --
      I am TheRaven on Soylent News
  29. Re: by Anonymous Coward · · Score: 0
    am I supposed to sit here with my thumbs up my ass

    If you do, we promise not to judge you, or your lifestyle choices.
  30. Memory Footprints and Performance by devphaeton · · Score: 1

    Hi! :o)

    I'm trying out the BETA on my k6-II... I always want to have a FreeBSD box lying around. I like FreeBSD and its philosophy, but i'm not completely ready to make the jump from linux yet- there are certain things i'm accustomed to in the linux OS that are different or less-implemented in Fbsd.

    but anyways....

    Granted *this* is a beta and is full of debugging code and watchdogs and such, but even on official releases i've noticed that FreeBSD tends to have a much larger memory footprint than linux.

    Of course, this is most visible when running X (which isn't officially part of the OS). But say, for instance on the k6-II, i can have both Debian Unstable and FreeBSD on the hdd. In both cases i will have just the base system, and then only what is necessary to run windowmaker, gkrellm, firebird, gaim and bitchx- a moderately lean desktop installation.

    On disk, linux is about ~250MB, FreeBSD is about ~700.

    Boot up, startx, load windowmaker and gkrellm ONLY (aside from standard daemons and services)...

    gkrellm reports the linux installation as having 90 of 128mb free, but on FreeBSD (in the same state) it shows 10 of 128mb free. Obviously performance is gravely different between the two- anything else i open or use in FreeBSD lives in swap.

    Now i'm not illustrating this as a criticism of FreeBSD- I'm just curious if anyone has an explanation. I'm sure there is a valid reason for this, or it's a matter of ignorance on my part of setting up/configuring between the two.

    I do hold FreeBSD in high regard, but it is discouraging to run it on my k6-II. 300mhz and 128mb of ram aren't really limited resources, in my book- one should be able to expect a reasonable and useable desktop experience. No KDE or Enlightenment or Gnome or things like that, but i'm not a fan of heavy DEs (XFCE, Wmaker, bbox are just fine for me :-))

    Hell, even WindowsXP (ugh) outperforms FreeBSD (which surprised the hell out of me)

    --


    do() || do_not(); // try();
    1. Re:Memory Footprints and Performance by Eivind+Eklund · · Score: 1
      Answers to your questions:

      (A) That beta is still running with our debugging code enabled, which will slow you down a lot. That's done intentionally, as it helps us catch bugs. This is why it is slow.

      (B) That on-disk footprint sounds like you've added ports or src; that will take a lot of space, but the space does not increase based on the number of apps installed.

      (C) When you are looking at how much memory is free, free memory is wasted memory. FreeBSD use as much of your memory as it can. "Free" is memory that FreeBSD at the moment has no data in, and thus memory that is wasted. I have less than 100MB free on a 2.5GB system here; but I have a heap of "Inactive" memory, which means the memory is used for disk cache.

      Eivind.

      --
      Doubting the existence of evolution is like doubting the existence of China: It just shows that you're uninformed.
  31. BSD vs. Linux by Anonymous Coward · · Score: 0
  32. Re:Beta 3 Due This Week by the+chao+goes+mu · · Score: 1
    Hate to add to the flame war, but...

    One area in which BSD's are definitely superior (not just to Linux, but to SunOs/Solaris too) is in the reaping of closed sockets. I had numerous test machines (hit very,very heavily with outside connections) where the Linux/Sun boxes would choke due to the slow pace with which they cleaned up old sockets. BSD on the other hand never suffered from that particular problem. It isn't a big issue in most cases, but there are certain real world situations in which Linux cannot be used for the same purposes as BSD.

    --
    Boys from the City. Not yet caught by the Whirlwind of Progress. Feed soda pop to the thirsty pigs.
  33. Re: by the+chao+goes+mu · · Score: 1
    I would agree except that I have been arguing since 3.X that they should support the ATA-2 standard for hard drives, and they still use a hack solution rather than respecting the LBA bit. (CYL=16383 is seems as indicating LBA, but LBA-bit=1 is not...) The argument is that a change would break pre ATA-2 disk drives. But, as ATA-2 was written in 1986, I think this is taking backwards compatability a bit far.

    Other than that little rant, I have found bugs@ and current@ very responsive...

    --
    Boys from the City. Not yet caught by the Whirlwind of Progress. Feed soda pop to the thirsty pigs.
  34. Re:*BSD is dying by Anonymous Coward · · Score: 0

    Trolled again.
    There ain't no netcraft confirmation.

    this linux dudes just like to troll around bsd news.

  35. Re:Why BSD is dying by fm6 · · Score: 1

    I can understand the temptation to respond to a "BSD is Dying" troll. But please wait for an actual trollpost. Responding to a post that mentions the "BSD is Dying" troll is premature.

  36. Re:Beta 3 Due This Week by SillyNickName4me · · Score: 1

    Heh, for example for webservers this is kindof relevant...

  37. Slow=!? by Anonymous Coward · · Score: 0

    I know its a BETA. But just curios.
    It is horrible slow to compile with it. my system is very poor in performence. And GNOME is hardly unusuable it look likes it running on a 486 machine on a dual p3 500. /newb