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."
Look it moves... It must be alive!
great, I just installed 4.7 last night...
...because those Linux folks started to get to culty--kinda like the Mac people.
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
BSD is dead?
BSD sux, Linux rocks!
"I switched to FreeBSD and was amazed..."
"I tried FreeBSD and it sucked..."
"Not to troll, but why should I use FreeBSD instead of Linux"
FreeBSD and SMP sucks!
"In Soviet Russia, the RC1 releases YOU!"
"BSD != DEAD"
So you se my friends, no need to post further! Thank you, come again.
Why do you think they call it a "release candidate"?
Programming can be fun again. Film at 11.
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...
Isn't it great how people can release things for hardware you wouldn't even know how to buy if you wanted to. I've often wondered how elements like the FreeBSD team and Linux get people interested in doing these things. Its not like an "itch you need to scratch" because you don't even have the body part to have the itch on!
An Eye for an Eye will make the whole world blind - Gandhi
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?
That is the funny part. VMWare runs courtesy of the Linux ABI. So you'd be running a Linux OS on a FreeBSD system using a Linux binary.
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
A major improvement in FreeBSD 5.x over 4.x is the new modular init. Instead of one monolithic script (classical BSD) or several scripts in a symlink farm with manual sorting and dependency resolution (SysV / Debian, RedHat, SuSE...), it uses an internal automatic sorting and dependency resolution comparable to apt-get or modprobe on GNU/Linux. I would like to see mainstream adoption of this in the GNU/Linux world of this. To date, Gentoo Linux is the only distribution offering and supporting this excellent feature.
gopher://cramer.plaintext.cc http://cramer.plaintext.cc:70
02-12-09 14:33 BSD: FreeBSD 5.0-RC1 Now Available
My monitor sometimes thinks it is a crystal ball; using it I can predict future /. headlines. Here goes:
03-01-06 9:25 BSD: FreeBSD 5.0-RC2 Now Available
03-01-14 9:25 BSD: FreeBSD 5.0-RC3 Now Available
03-01-25 9:25 BSD: FreeBSD 5.0-RC4 Now Available
03-02-02 9:25 BSD: FreeBSD 5.0-RC5 Now Available
03-02-17 9:25 BSD: FreeBSD 5.0 Released
03-02-19 9:25 BSD: FreeBSD 5.0.1 Released
Funny thing though, apart from the different version numbers the discussion is always exactly the same...
Wenn ist das Nunstueck git und Slotermeyer? Ja! Beiherhund das Oder die Flipperwaldt gersput.
Vinum has not been mantained at a high level for some time and I have heard that there is a replacement in 5.0 that emulates the IBM AIX volume manager (which kicks ass in my opinion).
Any word on this?
Either give it away or get top dollar, but never sell yourself cheap.
I was going to say...not necessarily support I'd be looking for. Unless of course you're going to build a DNS server - you know, one server to rule them all, one server to BIND them...
I want to delete my account but Slashdot doesn't allow it.
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?
You can help by getting off your rear and writing to your congressman or senator. Tell them FreeBSD is important to you. Tell them that without FreeBSD, you would have to find less managable and intelligently designed alternatives. Let them know that this is an issue that effects YOU directly, that YOU vote, and that your vote will be influenced, indeed dependent, on his or her policy on FreeBSD.
You CAN make a difference. Don't treat voting as a right, treat it as a duty. Keep informed, keep your political representatives informed on how you feel. And, most importantly of all, vote.
KMSMA (WWBD?)
FreeBSD has grown larger and larger -- back in the 3.x days I could run it easily. The 4.x series have consumed much more memory, even when the kernel is compiled to use the same features. I had heard that one of the 5.x trees goals was to regain some of that "thin" nature which IMHO is one of FreeBSD's biggest draws. Anyone know how that is coming along?
MORTAR COMBAT!
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?
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."
Actually, I've had no problems with x.0-RELEASEs. We installed 3.0-RELEASE on our machines the day it was released. We were waiting for it because we needed support for our SCSI card. This was before I knew about -SNAPSHOTs. Anyway, we installed it and ended up running it for like two years without a reboot. I remember a few security issues that could be patched while the machine was running but I don't remember any showstopper stability issues or system corruption issues. In fact, in all the releases that I've installed since 2.something-really-low, I don't think I've ever seen an unstable or dangerous -RELEASE.
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.
Now that FreeBSD has cardbus support can we expect Apple to grab some code and improve their cardbus support. While Apple's CardBus support does the basics there are many drivers that I have heard could not be written simply because the API support did not exist. Is this something Apple can grab. I'm not funny up to date on what Apple grabs from which various BSD projects. -Tim
Tim Smith - Ramblings from Nerd Land
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
You're looking at the wrong page, you want PicoBSD.
I used to have a full development system with BSDI or NetBSD on two 100MB drives, with Xwindows source. Those days are well behind us now.
I'm not sure I mind, seeing that disk is cheap these days, but the disk footprint of the 5.0 DP2 kernel was just shocking (filling the better part of a 128MB root partition). Now, I realize that is probably because that kernel was built with -g, but it is shocking nonetheless to see that an out of the box kernel takes up more disk space than my entire production systems in the BSDI 0.9.3 era.
Bert Driehuis -- All I asked was a friggin' rotatin' chair. Throw me a bone here, people.
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