Slashdot Mirror
FreeBSD 5.0-RC1 Now Available
Dan writes "Murray Stokely of FreeBSD release engineering team announces that they're one milestone closer with the immediate availability of FreeBSD first release candidate for the i386, alpha, sparc64, and ia64 platforms. ISO images and FTP installation directories are available now from the FreeBSD FTP site."
Here's a direct link to the pertinent section. It details kernel, userland, and security updates that have gone into the 5.0 tree of FreeBSD.
If you celebrate Xmas, befriend me (538
I wouldn't worry about it. Stick with 4.7 (or move to 4.8 when it's available) until 5.2 is released for anything important. My experience with releases is that a system runs much more reliably once a release has had time to mature. Of course, if it is a home machine or test box, I kinda understand, except why not follow -CURRENT if you want the latest-greatest of gizmos, gadgets, features, and shiny new toys?
I don't know whether you're just a troll or unclear on basic concepts, but you're wrong on multiple counts. 802.11b cards are well-supported, and journalling is a band-aid for a filesystem. FreeBSD's filesystem is well-designed and doesn't need that band-aid. As for token ring, ehh...
For more information about the Linux ABI, see this manpage.
Beware, Nugget is watching... See?
SMPng: The next generation support for SMP machines (work in progress). There is now partial support for multiple processors to be running in the kernel at the same time.
KSE: Kernel Scheduled Entities allow a single process to have multiple kernel-level threads, similar to Scheduler Activations.
New architectures: Support for the sparc64 and ia64 architectures, in addition to the i386, pc98, and alpha.
GCC: The compiler toolchain is now based on GCC 3. X , rather than GCC 2.95. X .
MAC: Support for extensible, loadable Mandatory Access Control policies.
GEOM: A flexible framework for transformations of disk I/O requests. An experimental disk encryption facility has been developed based on GEOM.
FFS: The FFS filesystem now supports background fsck (8) operations (for faster crash recovery) and filesystem snapshots.
UFS2: A new UFS2 on-disk format has been added, which supports extended per-file attributes and larger file sizes.
Cardbus: Support for Cardbus devices.
Beware, Nugget is watching... See?
Definitely not. Please stick with 4.x.x line for a while yet, and your satisfaction (from the POV of production use) will be greater.
Due to massive changes ans some binary incompatibilities, you should wait with using 5.x line for any serious production until x >= 1.
However, if you want to test it in a light and inconsequential scenario, by all means you should do it, to reduce the shock later on, and to play with some really cool stuff... Things like native kernel threads, GEOM disk abstraction layer, background fsck and a lot of others make 5.x line a distinct flavor...
Don't forget to brandelf it too, if said sick-linux-binary happens to have a broken elf header which says it's a Solaris binary or whatever, i.e:Since while FreeBSD will use the elf header to make things like Linux emulation work, Linux just ignores it, meaning a lot of tools like to produce incorrect headers. Tsk
Ofcourse I have 'kern.fallback_elf_brand=3' before even starting to think about running sick-linux-binary without brandelf ;)
Take a look at this... my favourite part is this:
So maybe in ten years or so we'll see jinit or a similar need/provide system in Debian!
By the way, I think Mac OS X has had the system FreeBSD 5 implements since inception... so maybe it dates back to NeXTSTEP or earlier?
I understand fully, and also agree. Getting VMware to work fully on FreeBSd is a kluge, especially if you want to do full screen mode. It just doesn't work. I've found that vmware1 works better than vmware2. Getting it networked has also proved difficult, though I've seen it done. One of the nasty parts of VMware is its use of that Linux /proc filesystem, which contains way more than just process information...
Overall, I think VMware is too expensive now. I'd rather see a VirtualPC for FreeBSD.
Beware, Nugget is watching... See?
Well, FreeBSD can run linux binaries. Observe:
/compat/linux
bash# uname -a
FreeBSD abox.some.dom 4.7-STABLE FreeBSD 4.7-STABLE: Sun Dec. 8 19:28:39 EDT 2002
root@abox.some.dom:/usr/obj/usr/src/sys/abox i386
bash-2.05b# chroot
%uname -a
Linux linuxbox.some.dom 2.4.2 FreeBSD 4.7-STABLE: Sun Dec. 8 19:28:39 EDT 2002
user@abox i386 unknown
So, does it run linux? Of course. It can also run SCO unix. "Does linux run FreeBSD or SCO?" is a better question. There's an effort to provide similar capabilities in linux, but it looks like they've just started. Help 'em out, ok?
RAIDframe. Not sure what the current status of it is.
Beware, Nugget is watching... See?
You're quite confused, but I don't blame you.
4.4BSD was the last full release from the Computer
Science Research Group at UC Berkeley. I think it
was in 1994. FreeBSD and NetBSD were based in large
part on this code. (This is an oversimplification
but it's good enough.)
Mac OS X is based on NeXTStep, which includes BSD
code from 4.3BSD, which came before 4.4BSD. Mac OS
X was updated using FreeBSD 3.4 as a reference.
There was no wholesale integration of FreeBSD 3.4.
Mac OS X 10.2 was updated using FreeBSD 4.3 as a
reference, I believe. Again, no wholesale
integration. The same will be the case with
FreeBSD 5.
Ben "You have your mind on computers, it seems."
You can get the schedule here
Darwin uses a monolithic kernel based on FreeBSD 4.4 and the OSF/mk Mach 3, combining BSD's POSIX support with the fine-grained multithreading and real-time performance of Mach.
The previous was correct in his post.
This won't be the case with 5.0. Its a well know fact that the maintainers of the project have said that 5.0 is not going to be ready for production or other machines that are critical. They've asked people to hold off and wait for 5.1 or even 5.2.
scott
The KSE facility will not, in all probability, be production-ready in time for the 5.0-RELEASE. See FreeBSD KSE Project page. For SMP, see FreeBSD SMP Project.
-- Sig down
Doesn't work on a pre release? Go figure
I have full screen running on a neomagic chipset
under 4.4, 4.6 and 4.7.
I had to comment out the 'no ddg' statement in
Don't Steal - The Government Hates Competition
PS. Google on "PicoBSD".
Journaling has nothing to do with "band aids." Journaling makes sure that if a system suddenly loses power it can recover its file system. By keeping track of changes BEFORE making them, the FS can look at where it was last planning to change and, if something's wrong, change it back to what it used to be.
Hard to use? Jesus. The reason I use FreeBSD is because it is EASY to use. Linux drives me fucking batty every time I try to use it. Get some sort of bloody standard for system upgrades and I might use Linux. Get some sort of standard package system and I might use Linux. Get some sort of standard startup scripts and I might use Linux.
Frankly, if you had a hard time using FreeBSD, then noone showed you how to use the system and that is a shame. If you spent more than a few days with a working FreeBSD system and understood how it worked, I doubt you would ever go back to Linux.
-sirket