FreeBSD 4.10-RC3 is available. Changes from RC2 include a full package set for Alpha, fixes for the twe(4) driver under load, fixes for the twa drives not being seen by sysintall, along with various other bug fixes. i386 ISO images are available now, Alpha ISO images are still uploading.
FreeBSD 4.10-RC3 Available
About The Author
Eugenia Loli
Ex-programmer, ex-editor in chief at OSNews.com, now a visual artist/filmmaker.
Follow me on Twitter @EugeniaLoli
Whoa, release 4.10-RC3 .. now THIS is news!!
I’m new to FreeBSD. Played around with 5.2 in school, liked it alot. Soo, what is wrong with 5.x? A lot of people seams to prefere 4.x and dragonfly bsd, whay?
MAN, the central server is BLAZING! I’m getting solid speeds above 400kb/second!
Looks liek I’ll be installing FBSD tonight =) first on my test partition, and if all goes well, ill either setup a FBSD router-pc(if i can find some NICS around here) or replace my Slackware install on my main PC w/ FBSD!
/me loves the daemon
Nothing is wrong, but I think it is still considered kind of “development” whereas 4.x won’t be changing *much* since I think this si the last 4.x release…
Also, I think, the nvidia drivers(official) only work with 4.x right now.
FreeBSD 4 is marked stable, whereas 5.x is still considered unstable/current.
I’m using 4.9 on my server now and I’m also thinking about converting my new AMD64 desktop to FreeBSD. I love the dual bladed nature of the FreeBSD package management. There are packages AND ports(Arch Linux also does something like this).
I’m new to FreeBSD. Played around with 5.2 in school, liked it alot. Soo, what is wrong with 5.x? A lot of people seams to prefere 4.x and dragonfly bsd, whay?
Well, from my experience, and from talking with other users, I’d say that it comes down to stability. Currently, 5.x isn’t production quality, and therefore many folks (especially anyone doing anything important) are using FreeBSD 4.x instead.
I am a tremendous fan of DragonFly (I’ve been a FreeBSD user for quite a while), but you’d be crazy to use it for any “mission critical” operations before it’s second release. I say second release, because not all the low level stuff (new APIs and architecture ect.) will have had a chance to stablize before then. The first DragonFly release is going to be more of a “technology preview” than anything else, and you’ll be lucky if it comes with it’s own packages and an installer.
Except for the the odd time when Matt makes really big changes (the switch to the new token code, or the new device “reference-count” code and so on), I’d go so far as to say that it’s been far more stable than has 5.x (for me, at any rate), but that’s really beside the point I suppose.
> Also, I think, the nvidia drivers(official) only
> work with 4.x right now.
From nvidia.com: “Please note that FreeBSD -STABLE, version 4.7 or later is required.”
5.x is later and it works.
From nvidia.com: “Please note that FreeBSD -STABLE, version 4.7 or later is required.”
5.x is not -STABLE. 4.9 is the latest version of FreeBSD -STABLE. 4.10 will be the new version of -STABLE when it comes out.
If nVidia had said “Please note that FreeBSD version 4.7 or later is required.” Then you would be correct.
The fact that the nVidia driver works is coincidental.
What sort of upsets me is that some of the newer drivers in the 5.X tree have not been back ported. I know the argument that people should start using the 5.X tree, but what if someone does not feel comfortable yet, for exmaple the newer nvidia chipsets (motherboards not graphics) and Promise Add on raid card are not support as of 4.9 and probably 4.10
5.x does not have the number of packages that 4.x has. 5.x has support for many drivers, etc. but lags 4.x in binary packages. Sure you can spend 2 days compiling and fixing broken ports but then again ….
You can do what I did. Switch to Linux and wait for 5.x to go stable and become the only one. Some people will say 5.x is already stable … for some of us that stability is too much pain.
It does?
Odd, I’ve not noticed this at all on my machine running the current 5_2 RELENG with a uptodate ports tree.
Why switch to linux, when 4x works just as nicely, when waiting for 5stable.
BTW most ports are not dependent on a certian FBSD version. Nearly work across the board with out problems. There are a few exceptions, but those are ones that actually want something in a newer release. CVSUP or the like will give you the same portstree regardless of what version you are running.
BTW you don’t have to compile, binary packages are aviable too.
You can do what I did. Switch to Linux and wait for 5.x to go stable and become the only one
So, what you’re saying is that people should downgrade before they upgrade? ;^D
“You can do what I did. Switch to Linux…”
Don’t you just long for the day when there’s a BSD thread where a Linux troll DOESN’T appear to say “Switch to Linux…”
Actually, I’ve been very impressed by the way that both Linux distros using the kernel 2.6 and FreeBSD 5.x have been developing. In my mind, FreeBSD 4.x should be rather compared with Linux distros that use the 2.4 kernel than with distros that use the 2.6 kernel.
Just give them both (Linux 2.6 & FreeBSD 5.x) six months more to mature, and you’ll notice that they’ll be striving towards the same goals, just like two rival dolphins striving after the same kipper. At the moment Linux has a slight advantage, but things may change very fast. I’m personally quite happy that there are choices available in Open Source Software, so that we are not entirely dependent on the success or failure of the one and only Linux kernel.
In my humble opinion, it would be a sorry state of affairs if all Open Source Software depended on the success or failure of just one kernel. At the moment, FreeBSD is doing better job than anyone else to advance the idea that OSS is all about keeping our choices open.
Forgive me, it actually says in the nvidia README that they work with -CURRENT as well(anything above 5.0 should be fine).