Slashdot Mirror

see ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/5. 0-RELEASE/RELNOTES.HTM for details...

Even more perplexing, why would anyone use Linux?

FreeBSD 5.0-RELEASE.

Haha! Microsoft will upgrade you

They are too late. I already upgraded.

Not to sound like a bitch; but if any you want to understand the concept of a good VM, you should read this which is a proven VM, and has been proven vastly superior to the new Linux VM(s).

Well no offence but I hope you don't recommend it to newbies.

i think freebsd is a better choice for newbies who actually want to learn about unix, and i say this from experience. when i started playing with *nix, i tried linux and freebsd, and i found freebsd to be much more consistant in general. in linux, things tend to vary drastically between distros and versions, but freebsd has pretty much stayed the same over the last few years that ive used it. i've also found the freebsd handbook to be very helpful, since it doesnt become obsolete with every new release (unlike a lot of linux documentation).

An elaborate troll. You have way too much free time on your hands, friend.

Let me direct you all to the FreeBSD Java Project webpage.

Or you could read their Early Adopter's Guide and wait until 5.1-RELEASE or 5.2-RELEASE as suggested if stability is an issue.

WRT FreeBSD, read Chapter 21 of the Handbook.

Sure, FreeBSD makes it easy to do an upgrade. You have to compile everything from source, but that only takes a few hours.

For more information, check out Chapter 21 of the FreeBSD Handbook.

Sure, FreeBSD makes it easy to do an upgrade. You have to compile everything from source, but that only takes a few hours.

For more information, check out Chapter 21 of the FreeBSD Handbook.

freeswan

freesbd ipsec

both found using google with a blod alcohol of at least 3 o/oo (it's about 8 in the morning in norway, and just typing this took at least 10 minutes).

However, I don't think for a minute that all the clone MB manufacturers will make it impossible to boot an unsigned OS. I mean, most have setting that allow you to use processors whose frequency multipliers has been unlocked.

I'm using the Makefile that comes with FreeBSD. You can check it out at the web CVS browser. You might find some of the features kind of interesting.

Toxen is recognized for developing the BSD lock(1) program.

MindGuard protects your mind by jamming and/or scrambling psychotronic mind-control signals and removing harmful engrammic pollutants from your brain. It also has the ability to scan for and decipher into English specific signals so you can see exactly Who wants to control you and what They are trying to make you think. With MindGuard, you can rest assured that your most valuable possession - your mind - is safe from the nefarious tinkering of evil-doers. This port is cleverly hidden in the games category rather than sysutils where it belongs, so the forces of evil are less likely to find it.

Incorrect... this affects 4.3 and later. It does effect -STABLE up until the point where the patch was installed. -STABLE is a line off of a release where tested new features, bug fixes, and security patches are applied. Thus, you could install a -RELEASE and then track -STABLE, but you would generally only do this if you were engaged in actively developing (on) FreeBSD. If you were using a -STABLE before this came to light, you are still vulnerable unless you've updated since.

5.0 may or may not be affected - I would assume the former, but I may be wrong.

For more information on -CURRENT and -STABLE...

The FreeBSD security advisory is available at ftp://ftp.freebsd.org/pub/FreeBSD/CERT/advisories/ FreeBSD-SA-02%3A44.filedesc.asc, including patch.

I think that you missed the great documentation that accompanies FreeBSD. I installed FreeBSD as a *Totall* BSD, Linux, SCO, Solaris newbie. Now when I install any NIX or UNIX system I think how nice it would be to have the same simplicity that is the FreeBSD installer. I honestly have tried to install Mandrake and get so frustrated and angry that I just stop. I like FreeBSD and Debian's installers the best. Just give me the basic system and let me build what I want. I laugh when people talk about how hard installing FreeBSD is. Look at the handbook it is the single most usefull *nix manual out there. Oh and by the way its "menu" not "menue"

It brings up an interesting use for having source though, even if you don't code. Before buying a particular bit of hardware it might be interesting to read the driver comments to see what the programer thought of the thing at the low level.

It brings up an interesting use for having source though, even if you don't code. Before buying a particular bit of hardware it might be interesting to read the driver comments to see what the programer thought of the thing at the low level.

It's probably not as elegant or as well known as Beowulf clustering, but it has been done :)

The first thing I see when I go to the FreeBSD website is this:

FreeBSD is an advanced operating system for x86 compatible, DEC Alpha, and PC-98 architectures. It is derived from BSD UNIX, the version of UNIX developed at the University of California, Berkeley. It is developed and maintained by a large team of individuals. Additional platforms are in various stages of development.

Frankly, branching a new distro for some petty reason (I'm going to assume that's what it is since it is so damn hard to find out) instead of contributing tools and patches to an existing BSD seems just a tad too reminiscent of that other large free OS community.

[...]
macs have three layers of file permissions where unix has one. Macs have the usual unix permissions. Plus there is an ability to lock a file against changes or deletion, and finally there is the ability to lock a file against modification even by root. generally you wont ever need either of the latter two, but you may someday find a file you cant seem to delete!

It is called "flags" and comes, I suppose, from BSD. See, for example, FreeBSD's chflags(1). The possible flags -- from chflags(2):

• UF_NODUMP Do not dump the file.
• UF_IMMUTABLE The file may not be changed.
• UF_APPEND The file may only be appended to.
• UF_NOUNLINK The file may not be renamed or deleted.
• UF_OPAQUE The directory is opaque when viewed through a union stack.
• SF_ARCHIVED The file may be archived.
• SF_IMMUTABLE The file may not be changed.
• SF_APPEND The file may only be appended to.
• SF_NOUNLINK The file may not be renamed or deleted.

[...]
just in case, the normal file lock is accessed via "get info"

Or ``ls -o'' :-) I wonder, why I'd go with Mac, though, when the real FreeBSD runs on a more powerfull and cheaper hardware... The nice commercial apps? Perhaps...

[...]
macs have three layers of file permissions where unix has one. Macs have the usual unix permissions. Plus there is an ability to lock a file against changes or deletion, and finally there is the ability to lock a file against modification even by root. generally you wont ever need either of the latter two, but you may someday find a file you cant seem to delete!

It is called "flags" and comes, I suppose, from BSD. See, for example, FreeBSD's chflags(1). The possible flags -- from chflags(2):

• UF_NODUMP Do not dump the file.
• UF_IMMUTABLE The file may not be changed.
• UF_APPEND The file may only be appended to.
• UF_NOUNLINK The file may not be renamed or deleted.
• UF_OPAQUE The directory is opaque when viewed through a union stack.
• SF_ARCHIVED The file may be archived.
• SF_IMMUTABLE The file may not be changed.
• SF_APPEND The file may only be appended to.
• SF_NOUNLINK The file may not be renamed or deleted.

[...]
just in case, the normal file lock is accessed via "get info"

Or ``ls -o'' :-) I wonder, why I'd go with Mac, though, when the real FreeBSD runs on a more powerfull and cheaper hardware... The nice commercial apps? Perhaps...

FreeBSD license

"Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.

2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution."

Where does it give permission to slap a new license on it?

I converted to FreeBSD 3 from RedHat 5 and have not looked back since. It just makes more sense structurally and is more solid than anything I have found on i386. BSD argueably has the most solid TCP/IP stack out there. A few examples:

- F5 BigIP's converted from BSDi to a modified FreeBSD kernel in v4 (microsoft uses these for Windows update)

- Also I had to laugh when I found out F5 inserted the BSD TCP/IP stack in one of their "Red Hat" cache appliances (EdgeFX) for performance resons. :)

- The evil empire also uses FreeBSD for hotmail. You didn't think Winders could hang?

- Nokia/Checkpoint FW1 and IDS sensors run BSD kernels

- Can you folks think of anymore on the resume?
The interesting history is that Bill Joy (went on to help form SUN) was behind the original BSD movement. I heard it used to be called Bills' Software Distro... Wasn't Berkley behind tcp/ip? You folks probably know more of the history than me.

Anyways, I had a crash and burn attempt at 5.0RC2 last night so I'll probably wait for 1/17/03 and get a new box for 5.0 Release.

FYI - looks like RC2 is posted.

Upgrading within 4.x has been pretty smooth

4.x to 5.0 may not be however. This from the 5.0-DP2 release notes "Warning: Binary upgrades to FreeBSD 5.0-DP2 from FreeBSD 4-STABLE are not supported at this time. This may change by the time 5.0 is released."

You install FreeBSD, of course.

I'm sure there are exploitable buffer overflows in Vorbis too but as the format is so little used (relatively), hackers ain't looking for them. The day Vorbis is more popular than mp3 is the day the hackers change what they're targeting.

Much like people used to claim in days of old that certain message base formats (BBS / FTN message 'echoes') were faster than others, this is also a bit of rubbish. The format doesn't contain vulnerabilities; the players that implement the format have vulnerabilities. It is, in point of fact, perfectly feasable to assume that the same, if only slightly different vulnerability could possibly be exploited with the Ogg Vorbis format.

Unchecked buffers (read: lazy/braindead programming and poor code audits) are at fault here. MP3 is merely the current carrier.

But you're right; it is a feeble excuse to switch formats. It would be more apt to suggest that people switch to a different player, or use a different operating system, but I'm not going to do that.

Like other posters have noted before, Darwin/Mac OS X is actually based on BSD-licensed software, not GPL-licensed software. If you want Linux on PPC, there are other alternatives.

However, that kind of problems only points at a much greater problem. Namely, the fact that a commercial entity (Apple) is heavily using open source in their latest software offering, even though their behaviour clearly indicates they are not interested in the philosophy of open source.

Finally, honestly, what's the point of Darwin only on x86? If I want BSD-style operating system on Intel x86, I'll use FreeBSD, or one of the other two, not some sort of bastardized version, which does not offer the reliability, security, or portability for which the other versions are well-known.

The evil girl-Terminator can be seen in this photo where she is using her striking appearance to gather intelligence on the primative life forms.

Some how, I think from this image, I can tell there is a much deeper, more hate-filled conflict being developed here. Anything could happen before this war hits.

Patches
are
available

well, since FreeBSD isn't a publicly traded company I can't really speak for their profits, or lack thereof, but this shows that the second rc of FreeBSD 5.0 is due out today....

Given the qualifications and history of Ken Biba listed in the article

Biba started in security and networking R&D 30 years ago with Mitre Corp. and was a member of the Advanced Research Projects Agency Transmission Control Protocol (TCP) Working Group

I wonder if he is the same Ken Biba that worked on/devised Mandatory Access Control (MAC) and the Biba Integrity Model.

There is a good description of MAC here, and an explanation of the Biba Integrity Model here.

This isn't just a pattern/antipattern thing. Many discussions er... have this pattern. Its the reason why we have the phrase "constructive criticism".

Another extreme of criticism is Bikeshed Painting, where you get swamped with alternative designs; I only mention this because of the nice story behind that link.

FreeBSD 5 will have to show its mettle before Apple officially integrates the 5.0BSD subsystem in a later OS X update.

Are you confusing the "4.4BSD" that gets thrown around a lot, with FreeBSD 4.4?

Because 4.4BSD does not mean FreeBSD 4.4, it usually refers to the last official release of the Berkeley Software Distribution.

From this: The UNIX system family tree: Research and BSD

we can see that Darwin is made up in parts from 4.4BSD Lite2 for Rhapsody, FreeBSD 3.2 and NetBSD 1.4 for Darwin/Mac OSX 10.0, then updated with FreeBSD 4.4 for OSX 10.2.

Looking at the family tree, you can see that the current versions of FreeBSD, OpenBSD, NetBSD, BSDI and Darwin are all 4.4BSD Lite2 based.

There will probably never be a 5.0BSD, unless Berkeley picks BSD up again (and does a lot with it), since the legacy of 4.4BSD is mostly a foundation now.

Troll.

OpenBSD has had IPv6 since version 2.7 out in June 2000.

And for the record, FreeBSD has had IPv6 since March, 2000, version 4.0

And let's not forget who brought you OpenSSH.

SMP isn't the top priority. Giving up stability and security for the latest and greatest features are not what everyone wants. A friend of mine complained about FreeBSD not having good SMP support, I asked him if he had an SMP machine, he said "No." I hope that is enough to illustrate my point.

Sorry to go off on this, but mod the parent down if you mod me down please. People always trounce on any of the BSD's while praising Linux here.

Hear that? That's my karma in the toilet. Flush.

My mistake, 3.5 is not officially supported, 3.5 is in maintenance mode, but still available.

I don't think there's anything stopping you from still using the older code. From what I hear, there's stil the occasional update to the 2.x series still. FreeBSD 3.5.1 is still available from the ftp server. It's not a dead codebase, and nothing stopping you from using it. Granted, none of the new features will be in there, but there will always be a features/space trade-off.

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.

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.

The rc(8)man page in FreeBSD 5.0-CURRENT describes how the new init works. Docs are also available for Gentoo's init.

You can get the schedule here

Thanks. Looks like they have a month of slippage on 5.0, so Jan maybe. With normal last second bug fixes, maybe end of Jan. No estimate on 5.1 though, sucks.

You can get the schedule here

According to the FreeBSD Handbook under Appendix A, section 6, the tag that you want is: *default tag=.

RAIDframe. Not sure what the current status of it is.

(FreeBSD 5.0 suffers from what has been described as a ``chicken and egg'' problem. The entire project has a goal of producing a 5.0-RELEASE that is as stable and reliable as possible. This stability and reliability requires widespread testing, particularly of the system's newer features. However, getting a large number of users to test the system, in a practical sense, means building and distributing a release first!)

• 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.

• 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.