Slashdot Mirror
FreeBSD 5.3 Release Candidate Released
Cronopios writes "The FreeBSD Release Engineering Team has just announced the availability of FreeBSD 5.3-RC1. This will likely be the only Release Candidate before the final release of 5.3, so please give it a try and report/fix any bug you find.
You can read the announcement, check the schedule and the 'Known Issues' (problems that
are still being worked on at this time)."
An important difference is that BIND 9.3.0 has replaced BIND 8.x as the default name server.
Windows users:
Internet Explorer is obsolete. Please upgrade to Google Chrome or Mozilla Firefox.
This is very good news.
:)
:)
I've been working with 5.3 beta 7 for the last few weeks. It is such a great system!
Perl 5.8.something is on there and even applications like WebGUI work like a charm.
I hope the official will be out soon.
sig not found
Basic binutils are upgraded too, but I find it particularly interesting that the Darwin msdosfs tools are getting incorporated into the BSD tree.
Cool.
So how come they're not using the new scheduler?
Hi
I have been following news for quite a while now and I have tested several fbsd releases form
4.X and 5.2.1 releases from all I have noticed is that I liked 4.X very much especially the memory management, harvest performance, actually the overall performance and the widely available documentation, well that's one of the main reasons why freebsd is known to me.
Know you guys coming close to the 5.3 -stable release alot of users are going to upgrade/switch, right, because this is what we have been waiting for. What about the performance that 4.X had? Will the performance be equal ? Will it be having better performance? Even on low end machines? And especially sinds freebsd is becoming more and more ready for desktop use, performance is a big issue on desktops.(look at Gnu/Linux for example, which I have been using for a very long time know, and all I can remember is that almost all of the releases have scheduling/latency issues. When I was using 2.2/2.4/2.6 All I have seen where low latency patches. What about freebsd?
I'm so exited to try out the new freebsd release. Butt a couple of questions are desired first.
As all you have noticed the above^ part, will fbsd have the same performance or better? When will this be ready 5.3.X ? Could I get some more accurate information about this? Since I'm planning to use it on my desktop.
I have only been reading the bsd section at slashdot so I don't know much about the progress you guys are making on the feature release. Is there a offical news site for freebsd users? Like openbsd has *deadly.org.
What about the compile flags freebsd RC is using compared to 5.3 -stable will there be a lot of changes? What about gnome packages? Will 2.8 make it in 5.3 stable (iso)?
If those things are taking a while to be there, does fbsd have any kernel patches like linux does to improve desktop performance? For example like: http://members.optusnet.com.au/ckolivas/kernel/
Joe
Am I the only one that feels that FreeBSD 5.X has gone in the wrong direction?
... it sounds promising, although only time will tell...
I run FreeBSD 5.X on my desktop since I don't feel it's ready to replace the production servers running happily with 4.X; and 5.X and the desktop feels very sluggish and slow in many areas compared to 4.X.
Maybe 5.X is faster on SMP, but on uniprocessor I think it's definitely a set-back compared to 4.X.
I feel FreeBSD 5.x is not yet ready, even it's almost 2 years late based on the original predictions(5.X-STABLE at least).
I don't want to start a flamewar, it's just that I cannot get rid of this bad aftertaste that 5.X left me with.
I really really hope FreeBSD improves over time - it was a fine OS. Meantime DragonFlyBSD is something to keep an eye on
Yes, this is going to be -STABLE. Work on 6.X has already begun on the -CURRENT branch.
My experiences with USB on FreeBSD is very positive. I tried three different digital cameras and two external disks, mouse etc. and everything was autodetected, although I never tried a USB 2.0 mass storage device. The best thing to do is try out it yourself.
I have a question. I have a number of small systems of varying specifications (all x86) and I'd love to be in on stress-testing 5.x; I'd love to have been in on testing all the BETAS. But my daily operations in FreeBSD are limited to working in Gnome or XFCE under a few IDEs, compiling ports, doing some maintenance work on servers, playing games, reading Slashdot, etc., none of which I find particularly stressful to the system. If it was, I would be inclined to believe it was a port problem, not a system problem.
What is the best way to stress test FreeBSD that will put it through its paces?
If you've been tracking 5.3-Beta and want to switch to the RCs and eventual RELEASE, don't forget to change your cvsup tag to RELENG_5_3 else you will end up with 5.3-STABLE, which isn't.
Music is everybody's possession.
It's only publishers who think that people own it.
Fuck Beta
~John Lenno
Anyone have any predictions?
Your CPU is not doing anything else, at least do something.
Yes, it is:
5.3-STABLE FreeBSD 5.3-STABLE #0: Sun Oct 17 13:50:02 CDT 2004
"To those who are overly cautious, everything is impossible. "
DragonFlyBSD
DragonFly is an operating system and environment designed to be the logical continuation of the FreeBSD-4.x OS series. These operating systems belong in the same class as Linux in that they are based on UNIX ideals and APIs. DragonFly is a fork in the path, so to speak, giving the BSD base an opportunity to grow in an entirely new direction from the one taken in the FreeBSD-5 series.
Likewise. Works better for me than hotplugd Recently when helping out a friend with suse, I didn't know how to make a flashdrive work. Partly this is because of my negligence: I forgot a lot about how linux works. Hotplugd was running, yet the system didn't gave any indication of what happens when I plugged it in. On the other hand:
Plug in flash drive in freebsd (5.x) :
plug out flash driveplug out my usb mouse (samsung optical)plug mouse back in Note that even Z dir is detectedHopefully, as soon as the release process is over, they will switch back to ULE in -current (officially, that is. in every dmesg/kernel config file I have seen on current, most developers run ULE). And I hope 5.4 will be the ULE release!
So, to answer your question: yes, 5.3 will be STABLE (and not only in name. the whole 5.x series is fairly stable, at least beginning with 5.1, or at least as stable as your average linux distro). I think it will be out on my birthday :))) (nov 11). But I also think that 5.x will be really ready when they have ULE back as default (ditch preemption if it needs be, ULE is so much better in every other aspect).
looking over various 4.x release dates I'm guessing5 months till 5.4 and ULE as default.
Your CPU is not doing anything else, at least do something.
The ndiscvt tools that allow you to convert your NDIS network drivers into kernel modules works really well (at least in BETA7). I'm very impressed. (My only gripe was that it had problems reading my .INF file because it was unicode; I converted to ANSI and all was well). I can now run a pretty good GNOME desktop on my Acer laptop with wireless access.
Is Matt Dillon aware that you are copy/pasting his reply to R. Watson from current@frebsd.org?
This is getting embarrasing for you
Life is what happened when Good Intentions met Harsh Reality (the brother of the more infamous Chaos).
5.3-STABLE FreeBSD 5.3-STABLE #0: Sun Oct 17 13:50:02 CDT 2004
actually that's not QUITE true.. well yet anyways.
Spot the difference.. He's substituted "HawkinsOS" for "DragonFly" !
t /2004-September/036930.html
http://lists.freebsd.org/pipermail/freebsd-curren
I hope these anonymous postings are not really by "Hawkins", but just some other people pretending to be nutjobs...
Sig out of date
Lucky - if I have EHCI in kernel, USB hubs don't work (the hubs are found but no devices beyond them).
:P
FreeBSD's hotplugging architecture is pretty backward though, especially for USB (and you can only use one keyboard at a time). You have to have a user-space daemon spawn moused for mice and kbdcontrol (not even in default usbd.conf) to set the newly inserted keyboard as the default.
I don't know about OpenBSD (assuming it's more like NetBSD), but NetBSD and Linux do this all kernel-level, including transparently mixing multiple keyboard and mouse inputs, and don't need anything in user-space (assuming drivers are already in kernel or modules are loaded). This is clearly the better way to approach USB.
I have not tried EHCI in NetBSD but don't see any reason for it to be broken. As per the features list: "NetBSD was the first free OS to provide USB support, and was using USB on Apple Power Macintosh machines before Apple had MacOS X even booting."
If they can get it that Right first time, getting it Right in the next generation should come naturally.
Unless somebody has evidence to the contrary
Sam ty sig.
Why?
Generally speaking everything which needs to be in the kernel is an indication of a kernel design failure. Ideally the kernel would be empty:-)
_O_
.|< The named which can be named is not the true named
Such a persuasive technical argument, I am sure we are all almost as impressed by your insight as by your inability to work out how to log in.
_O_
.|< The named which can be named is not the true named
renice -20 *setiathome pid* will kill pretty much any OS
I have had almost no problems. My system is almost always under load. Except randomly when compiling I get "cc:segfaults". I can restart the make process and it will skip on through. Some times it will segfault elsewhere depends on how long the compile is. Then sometimes it will go through a long compile without incident. Doing a "make -jX" doesn't seem to make a difference. My cflags are basic "-O2 -pipe" with the processor type set at "p2". I don't think it's hardware no other applications segfault or any strange problems. I'm upding to RC1 now, maybe that will stop it, but I've been hoping that for the past few Beta releases. Just curious if I'm the only one.
Understanding is a three-edged sword. -- Kosh Naranek
Errr. I bought a USB 2.0 disk yesterday, and to my disppointment, FreeBSD doesn't support USB 2.0 very well. man ehci(the USB 2.0 controller driver) says that the driver is currently buggy and does not build by default.
> actually that's not QUITE true.. well yet anyways.
Interestingly enough, it IS what a kernel built from approx 1 week old sourcecode claims to be.
Hmm, it seems to build... but not work very well here.
On one system it causes problems with usb hubs conencted to a 2.0 controller (on a pci card), while the same hubs work on the same machine with the same kernel but connected to the onboard 1.1 controller. My other FreeBSD machine simply crashes while detaching/reattaching for a 2.0 device during boot of the kernel.
Maybe the later might be fixable by using modules for usb devices instead of having themn in the kernel tho.
R.I.P. ULE. For now at least.
It's simple logic. Any idiot will understand this, and if they don't they just have to take a CS101.
Hell, even Linus appear to understand it.
Form the last paragraph, if you're too lacy to read the short article:
The kernel is definitely maturing in the sense that a lot of the exciting really _new_ things are all in user space, and the kernel is sometimes called upon to make them easier to work with...