“Robert Watson has started the automatic posting of open issues for the upcoming 5.1 and 5.2 releases. The list for 5.1 is automatically posted to -current every other day, with the most up-to-date version found here. The list is divided into the following four sections: “Must Resolve Issues”, “Desired Features”, “Documentation items that must be resolved”, and “Areas requiring immediate testing”. Read it at KernelTrap.
I’m fairly intrested in trying out FreeBSD after a couple years on Slackware, Gentoo, those types of Linux distros… only thing I’m worried about is how well Winex works under FreeBSD. Anyone have any info?
blitzoid: I read on slashdot a while back that it is possible to get winex running, but there was something to be done….sorry I dont remember what that something was…
Does anyone know when 5.2 will be released…I have seen the page for 5.1 but cannont find it for 5.2
http://www.freebsd.org/releng/
That page is kept up-to-date with the lastest release plans. There is an approximate date for FreeBSD 5.1’s release.
http://www.bsdforums.org/forums/showthread.php?threadid=4793
This is the page that was linked to from Slashdot. Not sure if the code was ever MFC’ed (merged from current – available in the stable branch), or even in the current branch, but it is the article Yousef is referring to (I believe).
I am interested in is the fast progress being made on the KSE/libpthreads front. From what it looks like, it will be complete and in 5.2 thus fully replacing libc_r which should making porting applications that little bit easier and there should be a noticeable speed and responsiveness improvement.
You might need to compile from CVS, in which case you won’t have all the copy protection stuff <– from my understanding. I haven’t seen anyone use the WineX compiled binaries and run them under emulation (would be interesting to see if they run).
It will be fun to compare FreeBSD vs. Linux performance on the new 4-way Opterons. It’s rather incredible to have an affordable non-shared memory multiprocessor system even available, much less have two great operating systems to run on it.
Well that’s the problem because I HAVE winex binaries… I guess I could give it a shot once I take this box out of production
I am interested in is the fast progress being made on the KSE/libpthreads front. From what it looks like, it will be complete and in 5.2
No one knows if userland support for KSEs will be completed by 5.2. There are major problems with implementing signal delivery to threads reliably at this point. See http://www.freebsd.org/kse/
thus fully replacing libc_r which should making porting applications that little bit easier and there should be a noticeable speed and responsiveness improvement.
There aren’t compatibility issues with libc_r, just performance issues, and those can be eliminated by using the LinuxThreads port. Most performance instensive applications can be built out of the ports collection using the LinuxThreads port by building with WITH_LINUXTHREADS defined.