Comments on "FreeBSD 9.0-BETA1 Available"

can i use it? [kinda newbie on BSD]

i do not want to format 'every 6 months' like buntus!

it is possible to maintain 'update' with few commands? {type rolling release}
 
d_mon said:
can i use it? [kinda newbie on BSD]

i do not want to format 'every 6 months' like buntus!

it is possible to maintain 'update' with few commands? {type rolling release}
Click to expand...

Unless your interested in testing you shouldn't run it on production. If you have a machine and just want to play... go for it. If not wait for it to be done.( in fact most people running production servers wait for a point release like 9.1 just to be sure)
 
I will give it a try once STABLE is created in a few weeks, because I can't wait to get shared semaphores but on the other hand don't want to use a premature OS either.
 
I wouldn't say that the 9.0 CURRENT is premature. Whitehorn, Grehan, Hibbits, members such as Tingo, and quite a few of the hackers and the developers of different projects are making it a constantly more stable release before it is branded as RELEASE.
I'll vie for the fact that 9.0 CURRENT on PowerPC outperforms Debian in many areas. An OpenBSD member helped with a temporary solution to mouse grabbing on PowerPC machines. The Qemu developer group and Nox have been helpful and informative with Qemu on SPARC64. FreeBSD GNOME allowed me to try porting GNOME 3 to PowerPC and SPARC 64; the status is not ready due to some code and me being busy somewhat. FreeBSD KDE has allowed me to build KDE on both platforms mentioned with only PowerPC being successful.
Small ports such as xxxterm- killasmurf86's port- have made it easier to look up information when the system cannot handle memory and CPU stress/overload/waste from Firefox.
 
The more people try it the more stable it becomes. If we all waited for 9.1-RELEASE then there would never be one!

That said, I am not urging anyone to use 9.0-BETA1 for their high critical production servers. That would be silly. But for desktop and SOHO use, those who followed 8.2-STABLE can safely upgrade and help the community by doing some debugging.
 
I installed it on a test system earlier today, updated source to most recent version and recompiled everything with clang and CPUTYPE?=westmere, resulting in a nonworking userland (shell-autocompletion, gcc, and cvsup would crash with SIGBUS). Chrooting into the BETA-1 rescue system of the USB image would get me a working shell, cvsup and gcc so it's definately an userspace error rather then a kernel one.
I'll rebuild without CPUTYPE, hope that's the cause.
 
d_mon said:
can i use it? [kinda newbie on BSD]
Click to expand...
You can, but you should keep in mind that it is a beta - or test version. There might still be problems with it, which you are encouraged to report (and, if you can, even propose a fix for). That's what betas are for.

d_mon said:
i do not want to format 'every 6 months' like buntus!
Click to expand...
Since 9.0-BETA1 is exactly that - a beta - you shouldn't hang on to it. It's not much more than a snapshot.

Reformatting is rarely needed between updates (that's what Microsoft is for), but both -STABLE and -CURRENT will require that you regularly recompile the system. Beta versions and release candidates are for testing and not meant to be kept around.

Judging from your previous posts, I recommend you stick to -RELEASE (currently 8.2-RELEASE, 9.0-RELEASE is in the pipeline) versions of FreeBSD until you gain more understanding of the system.

Fonz
 
Rebuilding everything without CPUTYPE fixed the SIGBUSes for me. Most of the base is working here, with a noteworthy exception of the nfs-server. The FreeBSD-9's nfs-client can connect to FreeBSD-8's nfs servers, but the new server can't be connected to neither by the old client nor by the new one (and it's not a clang bug this time).

It seems others also have issues with it, according to the mailing list.
 
For me STABLE is stable. I've had more stability issues with RELEASE than STABLE. I don't recompile STABLE every day either, its more like "once in a while".
 
You must log in or register to reply here.
Back
Top