Slashdot Mirror

Since the introduction of the FreeBSD-5 branch, FreeBSD enthusiasts have been eagerly awaiting the day when the new codebase would stabilize. After much development and four previous releases, FreeBSD-5 has finally gone stable with version 5.3. But don't mistake a stable codebase with stable software. While the development team will no longer accept major changes to the base system, FreeBSD 5.3 still has bugs and problems.

FreeBSD is a complete Unix-like operating system entirely developed by a single large team of programmers. This is in stark contrast to GNU/Linux which, as a complete operating system, has no central, cohesive developer base and is packaged in myriad different ways by myriad different distribution projects and companies; and proprietary Unixes, which are closed-source, restrictively licensed, and work on a comparatively small number of usually proprietary hardware architectures. FreeBSD has historically been clean, fast, reliable, and scalable. It's easy to use, learn, set up, and navigate from the command line, has more than 10,000 software programs in the Ports system, runs on a wide variety of hardware, and can easily be used for either a desktop or a server.

The transition to 5.x

Until the release of 5.3, the most recent "production release" was the FreeBSD-4 series, which is presently at version 4.10 and has been deemed the "Legacy" release in the wake of the 5.x branch going to STABLE. FreeBSD-5 was supposed to be a grand introduction of new technology -- a revolutionary improvement to the tried and true 4.x branch -- but soon after it left the gate, it got caught up in developer politics and failed implementations of too-ambitious theories among other questionable design decisions, causing some developers to fork the FreeBSD-4 project into a separate and more focused operating system.

The ULE (which is not an acronym; its full name is SCHED_ULE as opposed to the older SCHED_4BSD) scheduler continues to have stability and performance problems and was totally disabled instead of being made the default process scheduler in 5.3 as planned. The mix of threading subsystems still yields problems with efficiency and stability. Also, the networking subsystem may now be multithreaded and therefore faster on SMP systems, but users with some implementations of the 3Com (SysKonnect/Yukon) gigabit LAN chip are now unable to access their network at all because of new bugs that have popped up in the driver; other SysKonnect/Yukon users have problems under heavy network traffic, along with those using Intel Pro/1000 chips. Unfortunately all of our test systems use these network chips for onboard LAN; coincidentally they are two of the most popular gigabit LAN chipsets used on modern motherboards from major manufacturers. We also experienced lockups during boot if a custom-compiled kernel did not have SMP enabled on a Hyper-Threaded computer. A list of these and other errata can be found right here.

Considering the long list of significant problems in FreeBSD 5.3-RELEASE, it would seem irrational to recommend that anyone switch a production server from 4.x or any previous known-working 5.x release to 5.3. Just the same, the FreeBSD project maintains a migration guide for this purpose.

A l

Since the introduction of the FreeBSD-5 branch, FreeBSD enthusiasts have been eagerly awaiting the day when the new codebase would stabilize. After much development and four previous releases, FreeBSD-5 has finally gone stable with version 5.3. But don't mistake a stable codebase with stable software. While the development team will no longer accept major changes to the base system, FreeBSD 5.3 still has bugs and problems.

FreeBSD is a complete Unix-like operating system entirely developed by a single large team of programmers. This is in stark contrast to GNU/Linux which, as a complete operating system, has no central, cohesive developer base and is packaged in myriad different ways by myriad different distribution projects and companies; and proprietary Unixes, which are closed-source, restrictively licensed, and work on a comparatively small number of usually proprietary hardware architectures. FreeBSD has historically been clean, fast, reliable, and scalable. It's easy to use, learn, set up, and navigate from the command line, has more than 10,000 software programs in the Ports system, runs on a wide variety of hardware, and can easily be used for either a desktop or a server.

The transition to 5.x

Until the release of 5.3, the most recent "production release" was the FreeBSD-4 series, which is presently at version 4.10 and has been deemed the "Legacy" release in the wake of the 5.x branch going to STABLE. FreeBSD-5 was supposed to be a grand introduction of new technology -- a revolutionary improvement to the tried and true 4.x branch -- but soon after it left the gate, it got caught up in developer politics and failed implementations of too-ambitious theories among other questionable design decisions, causing some developers to fork the FreeBSD-4 project into a separate and more focused operating system.

The ULE (which is not an acronym; its full name is SCHED_ULE as opposed to the older SCHED_4BSD) scheduler continues to have stability and performance problems and was totally disabled instead of being made the default process scheduler in 5.3 as planned. The mix of threading subsystems still yields problems with efficiency and stability. Also, the networking subsystem may now be multithreaded and therefore faster on SMP systems, but users with some implementations of the 3Com (SysKonnect/Yukon) gigabit LAN chip are now unable to access their network at all because of new bugs that have popped up in the driver; other SysKonnect/Yukon users have problems under heavy network traffic, along with those using Intel Pro/1000 chips. Unfortunately all of our test systems use these network chips for onboard LAN; coincidentally they are two of the most popular gigabit LAN chipsets used on modern motherboards from major manufacturers. We also experienced lockups during boot if a custom-compiled kernel did not have SMP enabled on a Hyper-Threaded computer. A list of these and other errata can be found right here.

Considering the long list of significant problems in FreeBSD 5.3-RELEASE, it would seem irrational to recommend that anyone switch a production server from 4.x or any previous known-working 5.x release to 5.3. Just the same, the FreeBSD project maintains a migration guide for this purpose.

A l

Since the introduction of the FreeBSD-5 branch, FreeBSD enthusiasts have been eagerly awaiting the day when the new codebase would stabilize. After much development and four previous releases, FreeBSD-5 has finally gone stable with version 5.3. But don't mistake a stable codebase with stable software. While the development team will no longer accept major changes to the base system, FreeBSD 5.3 still has bugs and problems.

FreeBSD is a complete Unix-like operating system entirely developed by a single large team of programmers. This is in stark contrast to GNU/Linux which, as a complete operating system, has no central, cohesive developer base and is packaged in myriad different ways by myriad different distribution projects and companies; and proprietary Unixes, which are closed-source, restrictively licensed, and work on a comparatively small number of usually proprietary hardware architectures. FreeBSD has historically been clean, fast, reliable, and scalable. It's easy to use, learn, set up, and navigate from the command line, has more than 10,000 software programs in the Ports system, runs on a wide variety of hardware, and can easily be used for either a desktop or a server.

The transition to 5.x

Until the release of 5.3, the most recent "production release" was the FreeBSD-4 series, which is presently at version 4.10 and has been deemed the "Legacy" release in the wake of the 5.x branch going to STABLE. FreeBSD-5 was supposed to be a grand introduction of new technology -- a revolutionary improvement to the tried and true 4.x branch -- but soon after it left the gate, it got caught up in developer politics and failed implementations of too-ambitious theories among other questionable design decisions, causing some developers to fork the FreeBSD-4 project into a separate and more focused operating system.

The ULE (which is not an acronym; its full name is SCHED_ULE as opposed to the older SCHED_4BSD) scheduler continues to have stability and performance problems and was totally disabled instead of being made the default process scheduler in 5.3 as planned. The mix of threading subsystems still yields problems with efficiency and stability. Also, the networking subsystem may now be multithreaded and therefore faster on SMP systems, but users with some implementations of the 3Com (SysKonnect/Yukon) gigabit LAN chip are now unable to access their network at all because of new bugs that have popped up in the driver; other SysKonnect/Yukon users have problems under heavy network traffic, along with those using Intel Pro/1000 chips. Unfortunately all of our test systems use these network chips for onboard LAN; coincidentally they are two of the most popular gigabit LAN chipsets used on modern motherboards from major manufacturers. We also experienced lockups during boot if a custom-compiled kernel did not have SMP enabled on a Hyper-Threaded computer. A list of these and other errata can be found right here.

Considering the long list of significant problems in FreeBSD 5.3-RELEASE, it would seem irrational to recommend that anyone switch a production server from 4.x or any previous known-working 5.x release to 5.3. Just the same, the FreeBSD project maintains a migration guide for this purpose.

A l

...FreeBSD is getting a new logo (well, 0 submissions to date, but still !

Hopefully, this will mean a lot more people buying one of these and using something like this, this, this, this or this!

Seriously. Why on Earth are people still putting up with these MS fuckers when Mac OSX and Apple hardware is so damn nice? I like a mix of Sun and Apple gear. The thought of actually deciding on MS just makes me shudder. And MS just keeps giving me more and more reason to hate them and the shit they peddle.

The regents don't "own" the rights per se, they simply over see them. Since BSD wasn't developed by anyone person, the copyright was assigned to the University of California as a whole. The University of California itself is governed by the Regents, as mandated by the California constitution:

The University of California is governed by The Regents, a 26-member board, as established under Article IX, Section 9 of the California Constitution. The board appoints the President of the University and the principal officers of The Regents: the General Counsel, the Treasurer, and the Secretary. The current Chairman is Gerald Parsky and the Vice Chairman is Richard Blum.

http://www.universityofcalifornia.edu/regents/

So basically since the copyright is assigned to the school, they are in charge of managing it, and therefore their name appears in the text. You can check out the original 4.4 BSD copyright here:

http://www.au.freebsd.org/copyright/license.html

> Is there a bug in mkdir? I don't bloody think so.

This is because you don't know anything about software development. You are a wanabee developer that believes his shit doesn't stink. We do error. Everybody do error. This difference is how we deal with it, and do we plan for those errors. I do, and obviously you don't.

When you said 'there is no bug in mkdir', I instantly thought of 3 or 4 obscure bugs that can be into it (for instance with -p, weird paths, devfs, mount points, unicode filenames, case-insensitive filesystems and disks full).

I was *absolutely* sure that there are bugs in mkdir. So I thought about FreeBSD, one of the most robust OS out there, which have its cvs web-accessible.

mkdir source code in the repository is 10 years old, and got 32 revisions. Of course, this code was written even before.

Latest bug in mkdir: http://www.freebsd.org/cgi/query-pr.cgi?pr=71743

Closed 6 feburary 2005.

Not even three weeks ago.

I urge you to reconsider your wisdom on software engineering. Read 'Writing Solid Code'.

And stop assuming anything is bug free. Even TeX.

I totally see the point. It's not currently used in a lot of enterprise situations but it sure could make a great mail server, NFS point for a workgroup or even a large SMB server. It can handle huge Apache loads and costs much less than Red Hat. It's all very open and very stable. It scales and it can handle significant loads for long periods of time without getting crushed. I'm not saying RHEL can't do that. I'm just saying, admittedly in a *wink-wink* manner, there's other robust platforms available that have not been fully exploited.

My point in posting was to inform others about another choice available. Red Hat's got a big name, and that's what most Enterprises will go for. Many smallers businesses, however, don't need "all that." Obviously, IT managers need to make their own decisions.

What's more valuable than choice when making important decisions? I'm not claiming to be an authority. I'm not saying - "Use FreeBSD instead of Red Hat." I'm just saying, "Here's a link. Check it out. Do what you will."

I think it's very nice to use and I can see many people currently on Red Hat systems falling in love with FreeBSD. It doesn't get in the way and is extremely capable. Maybe not RHEL capable, but in many cases, worth a look.

Oh well.. Thank you.

I'm sure RHEL is nice and everything. I'm sure RH has changed since using it back at version 7 or so, but FreeBSD is just so refreshing to use. The RPMs were a huge hassle and configuration was just kludgy. I just have a few FreeBSD machines myself, and run a small hosting biz. It's nothing but a joy to use.

The comment was somewhat trollish, but I guess that was intentional. Anybody clicking on "the Red Hat article" might come across my link and check it out.

Commercial supporters can't help but move FreeBSD forward. I'm happy if even a few see the comparison between FreeBSD and Red Hat and, at least for a moment, consider it's usage.

It's really a wonderful platform on which many, many businesses could build extremely stable servers. Don't want to pay Red Hat for a licence to run a SMB, NFS, or Apache server? Check out FreeBSD and thank me with a +mod :)

If you can answer "yes" to any of these questions, you're probably already running FreeBSD : )

IMPORTANT UPDATE: Please show your support for Ceren in this poll of Geek Babes!

Is it any wonder people think Linux users are a bunch of flaming homosexuals when its fronted by obviously gay losers like these?! BSD has a mascot who leaves us in no doubt that this is the OS for real men! If Linux had more hot chicks and gorgeous babes then maybe it would be able to compete with BSD! Hell this girl should be a model!

Linux is a joke as long as it continues to lack sexy girls like her! I mean just look at this girl! Doesn't she excite you? I know this little hottie puts me in need of a cold shower! This guy looks like he is about to cream his pants standing next to such a fox. As you can see, no man can resist this sexy little minx. Don't you wish the guy in this pic was you? Are you telling me you wouldn't like to get your hands on this ass?! Wouldn't this just make your Christmas?! Yes doctor, this uber babe definitely gets my pulse racing! Oh how I envy the lucky girl in this shot! Linux has nothing that can possibly compete. Come on, you must admit she is better than an overweight penguin or a gay looking goat! Wouldn't this be more liklely to influence your choice of OS?

With sexy chicks like the lovely Ceren you could have people queuing up to buy open source products. Could you really refuse to buy a copy of BSD if she told you to? Personally I know I would give my right arm to get this close to such a divine beauty!

Don't be a fag! Join the campaign for more cute open source babes today!

$Id: ceren.html,v 9.0 2004/08/01 16:01:34 ceren_rocks Exp $

# Uncomment this if you want libc_r to contain debug information for
# thread locking.
CFLAGS+=-D_LOCK_DEBUG

# enable extra internal consistancy checks
CFLAGS+=-D_PTHREADS_INVARIANTS

It was foolish, in my opinion, to keep this in the release. I wonder, how many points the OS lost in the benchmarks because of it...

Nevertheless, this is a very good benchmark conducted in a fair manner. I was pretty much surprised at how the guy lacking support (from Solaris no less) went on to find out by himself how to increase performance. This also underlies the point made by many in the "netbsd vs. free" benchmarK about the focus of FreeBSD being SMP in the past few years ... which has payed off nicely it seems.

Does it fix this fatal XFree/XOrg infinite loop bug?

What business?

Take a look at their home page. Things like... "...makes FreeBSD a very economical alternative to commercial UNIX® workstations" or "The FreeBSD Foundation is a non-profit organization for which direct contributions are fully tax deductible.". I think it's a given that without commercial support and/or use FreeBSD wouldn't be where it's at today. So that's the business I was talking about.

Anyone who seriously considers the need to "un-cute" the logo of someone's software is entirely too concerned...

It doesn't really matter. What's the bottom line? Depends where you're at...but I would think that for those that run the FreeBSD project it has alot to do with getting their OS used extensively. That includes people who are too concerned with what people who watch "Queer Eye" think of them.

I really don't think all this work is being done so that geeks around the world can have secure networks. It's larger than that...and by larger i mean big corporations. (No, I'm not saying that's their only or even primary target...but surely it is one)

Nobody is suggesting that Beastie should cease to be the FreeBSD mascot; this is about selecting a new logo.

The reasons for this include not just that some people consider the daemon to be offensive, but also legal issues: The daemon image is owned by Kirk McKusick and right now if companies want to use the image, they need to get permission from him. A "powered by FreeBSD" logo which is actually free for everybody to use would make things much easier.

I've already submitted my entry. I've got my fingers crossed!

2o7.net is a web analysis company, used explicitly by the BBC and other sites. See the replies on the freebsd-chat mailing list where the parent message was posted:

1 2

2o7.net is a web analysis company, used explicitly by the BBC and other sites. See the replies on the freebsd-chat mailing list where the parent message was posted:

1 2

Look it up in the s/key dictionary. There are several words in it that make me think that when the dictionary was made they pulled words out of a daily newspaper.

For your edification, here's a link to one copy.

It's not really missing a ports tree. Now there is Darwin Ports which is written, at least in part, by Jordan Hubbard, who also created the ports system on FreeBSD. It uses Tcl as its scripting language, and all the "portfiles", which are similar to the port makefiles on FreeBSD, are written in Tcl. It's fuller featured than FreeBSD's ports, but has far fewer ports available. I personally prefer it over Fink.

Seriously, for any CLI that is needed, man works just fine. For GUI programs like iWork you read the manual, and for OS type things such as configuring IPs the Help system is technical enough to get you through quite happily.

What I don't understand is how poorly written linux howto's are deemed acceptable. They are almost invariably written for one specific case of one specific flavor of Linux and outdated. Give me the BSD Handbook any day over that.

I do this for quite a few other pieces of work (the Gentoo handbook, PHP Documentation (in 21 languages, it looks spectacular in color), the Creating XPCOM book is even available in Plucker format, as well as many others.

These are not straight conversions, they require actual human eyes to look over them, test them, add navigation and other elements. For example, look at the Plucker version of the 9/11 Report that I did. I added a LOT of functionality that wasn't there in the original version. (I also put my pristine HTML source version online for anyone to read. You can see the additional features I've added in that copy).

I'll be making a lot more of my stealth works public soon.

When they're finished with the Slackware Handbook, I'd be more than happy to look it over, do the conversion, and provide it in a mobile format for our user community.

I hope the original author knows better than to take your advice, which is to effectively strongarm him/her into using the GPL regardless of what he/she wants.

I'm pretty sure that I'm going to adopt the OSSAL for my own code, specifically to PROTECT it from being GPLed.

Agreed. An on-site compilation server that builds all neccessary packages weekly (and possibly serves as an intranet server for webmail/samba donmain controller/etc), along with a handful of dedicated servers and however many desktops managment decides to float away from windows - all running FreeBSD - would be my option of choice. Cap it off with an OpenBSD gateway and you would have a very stable, smoothly-running, well integrated, time-tested, mature network. All that's missing is high-level support

Of course, he asked about linux, didn't he? It's a shame.

Some would disagree.

Ummm.... FreeBSD isn't GPLed, it's distributed under a BSD licence.

http://www.freebsd.org/copyright/freebsd-license.h tml

Basically you can do whatever you like with the code, as long as you retain their copyright notices in any of their code you use.

Many of the utilities and applications in a standard FreeBSD system are GPLed, of course, but the kernel is not.

Don't worry, that moron's post is totally made up...

I'm pretty sure there are plenty of open source developers who have never touched GNU Make.
Open source on windows, OMG it does exist!!!!
Step out of your Linux bubble.

What's Linux-centric about GNU make?

I'm primarily a Windows user, and I used to use GNU make all the time. Until I realised I preferred omake.

I spent roughly 80 hours a week for 2 years of the prime of my life developing an application. I rewrote virtually 80% of the 150,000 line C++ codebase. In short, it was forked by very hostile and childish people who continually kry [sic] "Leave us alone" at my program's site, lol.

The hostile fork started when I was personally targeted by the MPAA for my development efforts on 23 August, 2003

The GPL provides *zero* possibilities for overcoming hostile forks. If they want to copy your CVS (and keep their's private) they can effectively publish your own code before you release your program...which technically makes it "their" code. You cannot obfuscate code in order to get an advantage because the GPL forbids this.

How they won the battle was a systemmatic assault of every website comment section (just search for "xmule and comment") on the internet, attacking both myself (Un-Thesis | HopeSeekr) and the program. When this fails my program's site (www.xmule.ws) is routinely DDoS'd, the worst occuring when our original domain (www.xmule.org) was DDoS'd for approximately THREE months and had its DNS hijacked because of it.

Use the OSSAL dual licensed with the Creative Commons License to defeat the GPL! CCL is JUST AS FREE as the GPL (including no commercialization of *straight copies*) yet doesn't have the viral clause. OSSAL License expressly prevents the use of OSSAL code in GPLd products.

For detailed description of the difference between xMule and its hostile fork, see The Coding Philosophies of aMule and xMule . For a summary of some of the most blatant attacks against xMule by this fork, see Part III: On Hostile Forks.

Sincerely,
Ted R. Smith | HopeSeekr

IMPORTANT UPDATE: Please show your support for Ceren in this poll of Geek Babes!

Is it any wonder people think Linux users are a bunch of flaming homosexuals when its fronted by obviously gay losers like these?! BSD has a mascot who leaves us in no doubt that this is the OS for real men! If Linux had more hot chicks and gorgeous babes then maybe it would be able to compete with BSD! Hell this girl should be a model!

Linux is a joke as long as it continues to lack sexy girls like her! I mean just look at this girl! Doesn't she excite you? I know this little hottie puts me in need of a cold shower! This guy looks like he is about to cream his pants standing next to such a fox. As you can see, no man can resist this sexy little minx. Don't you wish the guy in this pic was you? Are you telling me you wouldn't like to get your hands on this ass?! Wouldn't this just make your Christmas?! Yes doctor, this uber babe definitely gets my pulse racing! Oh how I envy the lucky girl in this shot! Linux has nothing that can possibly compete. Come on, you must admit she is better than an overweight penguin or a gay looking goat! Wouldn't this be more liklely to influence your choice of OS?

With sexy chicks like the lovely Ceren you could have people queuing up to buy open source products. Could you really refuse to buy a copy of BSD if she told you to? Personally I know I would give my right arm to get this close to such a divine beauty!

Don't be a fag! Join the campaign for more cute open source babes today!

$Id: ceren.html,v 9.0 2004/08/01 16:01:34 ceren_rocks Exp $

>I never found adequate documentation for how to deal with it (most seemed to assume I already knew what I was doing).

I would suggest this excellent trilogy of articles about FreeBSD ports:
Ports Tricks
portupgrade
Cleaning and Customizing Your Ports
Together with the ports chapter on the FreeBSD Handbook, they should pretty much cover anything you'd need to know to work with ports - they did for me.
And btw, as another poster already pointed out, the BSD section of Onlamp is a *great* source for BSD technical info.

I've also heard great things about NetBSD's pkgsrc system - I have to try it out some day.
--
Being able to read *other people's* source code is a nice thing, not a 'fundamental freedom'.

The NetBSD Packages Collection (pkgsrc) is a framework for building third-party software on NetBSD and other UNIX-like systems, currently containing nearly 5000 packages.

[graph with a y-value of 12,000 at the current time]

Which brings us back to my statement:

Besides being the easiest, FreeBSD has by far the largest collection of ported software.

info about bugfixes would have gone into the release notes. errata paper contains info about bugs/problems that were discovered late in the release cycle and not yet fixed. they state it pretty clearly in the beginning of both papers:
4.11R errata
4.11R relnotes

info about bugfixes would have gone into the release notes. errata paper contains info about bugs/problems that were discovered late in the release cycle and not yet fixed. they state it pretty clearly in the beginning of both papers:
4.11R errata
4.11R relnotes

The other gotcha was the whole system startup area. FreeBSD has you enable the script (chmod 755, rename) *AND* put a variable in /etc/rc.conf. That sometimes messes me up. There are no runlevels in FreeBSD.

I have quite a bit of experience with FreeBSD since I switched away from Linux, and a good chunk of OpenBSD under my belt, too.

The nice thing about OpenBSD is that it is amazingly clean. Bare to the bones, etc. It seems to work well on a lot of hardware, and is super-secure. The big downside that I found when I was first getting into it is that the OpenBSD community is very -- how shall we put this delicately -- impatient with newbies. RTFM is a popular response to most questions. I always did my best to search through the mailing list archives (they have the worst searching engine I've ever seen!), but so long as you can show that you've made a concerted effort in understanding and solving the problem, there should be at least one person who will help you. The OpenBSD documentation is quite thorough, though I have found it lacking in the example department, which for me, is a really important thing in helping me understand something. Oh yeah, and Theo de Raadt is kinda nasty and abusive, but you gotta love him anyway.

FreeBSD, on the other hand, is really easy to figure out without needing support from the community. The Handbook is an amazing resource, and has answers to pretty much all of the questions I've ever had. I've always found FreeBSD to be particularly stable, and to handle high server loads much better than Linux. Updating the system is easy, and the ports system is to die for. With Linux, I was always having to stay on top of security updates and hope that my server wouldn't get hacked through yet another exploit; while FreeBSD is occasionally subject to the same exploits (eg. BIND, Sendmail), the overall maintenance is much less demanding.

My own server cluster has three FreeBSD machines and a little OpenBSD companion. I generally find FreeBSD to be friendlier and less-frustrating, but OpenBSD has some definite advantages and uses.

Patrick

There are several that are quite good, IMHO.

And ultimately, it depends on what you want, too.

Personally, I've had great experiences with all of the above OSes. While issues do crop up from time to time, it would be unwise to assume that they would not, in the future.

I say without a doubt they should try FreeBSD first. It'll run almost any application they are used to either natively or through the Linux compatibility layer.

Also, reading through the FreeBSD Handbook will answer almost any question that one could have regarding getting the system up and going.

Combine all of this with the extremely expansive collection of ported applications (it's often as easy as 'cd /usr/ports/net/whatever ; make all install clean ; rehash' for almost anything) and it's a really, really nice way to work.

I say without a doubt they should try FreeBSD first. It'll run almost any application they are used to either natively or through the Linux compatibility layer.

Also, reading through the FreeBSD Handbook will answer almost any question that one could have regarding getting the system up and going.

Combine all of this with the extremely expansive collection of ported applications (it's often as easy as 'cd /usr/ports/net/whatever ; make all install clean ; rehash' for almost anything) and it's a really, really nice way to work.

Please help to save bandwidth by using BitTorrent to download FreeBSD.

Please don't download FreeBSD but prefer to buy it on CDROM, preferably from FreeBSDmall.com, which is linked from FreeBSD "Getting" page. This way you can support FreeBSD. Another way to help the project is to donate money.

Please don't download FreeBSD but prefer to buy it on CDROM, preferably from FreeBSDmall.com, which is linked from FreeBSD "Getting" page. This way you can support FreeBSD. Another way to help the project is to donate money.

IMPORTANT UPDATE: Please show your support for Ceren in this poll of Geek Babes!

Is it any wonder people think Linux users are a bunch of flaming homosexuals when its fronted by obviously gay losers like these?! BSD has a mascot who leaves us in no doubt that this is the OS for real men! If Linux had more hot chicks and gorgeous babes then maybe it would be able to compete with BSD! Hell this girl should be a model!

Linux is a joke as long as it continues to lack sexy girls like her! I mean just look at this girl! Doesn't she excite you? I know this little hottie puts me in need of a cold shower! This guy looks like he is about to cream his pants standing next to such a fox. As you can see, no man can resist this sexy little minx. Don't you wish the guy in this pic was you? Are you telling me you wouldn't like to get your hands on this ass?! Wouldn't this just make your Christmas?! Yes doctor, this uber babe definitely gets my pulse racing! Oh how I envy the lucky girl in this shot! Linux has nothing that can possibly compete. Come on, you must admit she is better than an overweight penguin or a gay looking goat! Wouldn't this be more liklely to influence your choice of OS?

With sexy chicks like the lovely Ceren you could have people queuing up to buy open source products. Could you really refuse to buy a copy of BSD if she told you to? Personally I know I would give my right arm to get this close to such a divine beauty!

Don't be a fag! Join the campaign for more cute open source babes today!

$Id: ceren.html,v 9.0 2004/08/01 16:01:34 ceren_rocks Exp $

Instead of looking for something current not existing on Solaris, why don't you consider FreeBSD?

And if you follow the development you'll note

FreeBSD's advantages are thinning out fast

IMPORTANT UPDATE: Please show your support for Ceren in this poll of Geek Babes!

Is it any wonder people think Linux users are a bunch of flaming homosexuals when its fronted by obviously gay losers like these?! BSD has a mascot who leaves us in no doubt that this is the OS for real men! If Linux had more hot chicks and gorgeous babes then maybe it would be able to compete with BSD! Hell this girl should be a model!

Linux is a joke as long as it continues to lack sexy girls like her! I mean just look at this girl! Doesn't she excite you? I know this little hottie puts me in need of a cold shower! This guy looks like he is about to cream his pants standing next to such a fox. As you can see, no man can resist this sexy little minx. Don't you wish the guy in this pic was you? Are you telling me you wouldn't like to get your hands on this ass?! Wouldn't this just make your Christmas?! Yes doctor, this uber babe definitely gets my pulse racing! Oh how I envy the lucky girl in this shot! Linux has nothing that can possibly compete. Come on, you must admit she is better than an overweight penguin or a gay looking goat! Wouldn't this be more liklely to influence your choice of OS?

With sexy chicks like the lovely Ceren you could have people queuing up to buy open source products. Could you really refuse to buy a copy of BSD if she told you to? Personally I know I would give my right arm to get this close to such a divine beauty!

Don't be a fag! Join the campaign for more cute open source babes today!

$Id: ceren.html,v 9.0 2004/08/01 16:01:34 ceren_rocks Exp $

Now try to visualize that story with FreeBSD's Scott Long (2nd on the left) and his Linux mullet-sporting namesake counterpart. I don't know about you, but I think Linux has finally found its poster guy, he and Tux look so happy together in that photo, don't you think? Of course, they'll also need a new slogan to go with the new poster, so I propose "Linux: the bare essentials open source OS. Who do you want to get friendly with today?"

IMPORTANT UPDATE: Please show your support for Ceren in this poll of Geek Babes!

Is it any wonder people think Linux users are a bunch of flaming homosexuals when its fronted by obviously gay losers like these?! BSD has a mascot who leaves us in no doubt that this is the OS for real men! If Linux had more hot chicks and gorgeous babes then maybe it would be able to compete with BSD! Hell this girl should be a model!

Linux is a joke as long as it continues to lack sexy girls like her! I mean just look at this girl! Doesn't she excite you? I know this little hottie puts me in need of a cold shower! This guy looks like he is about to cream his pants standing next to such a fox. As you can see, no man can resist this sexy little minx. Don't you wish the guy in this pic was you? Are you telling me you wouldn't like to get your hands on this ass?! Wouldn't this just make your Christmas?! Yes doctor, this uber babe definitely gets my pulse racing! Oh how I envy the lucky girl in this shot! Linux has nothing that can possibly compete. Come on, you must admit she is better than an overweight penguin or a gay looking goat! Wouldn't this be more liklely to influence your choice of OS?

With sexy chicks like the lovely Ceren you could have people queuing up to buy open source products. Could you really refuse to buy a copy of BSD if she told you to? Personally I know I would give my right arm to get this close to such a divine beauty!

Don't be a fag! Join the campaign for more cute open source babes today!

$Id: ceren.html,v 9.0 2004/08/01 16:01:34 ceren_rocks Exp $

FreeBSD appears agnostic in this matter.

FreeBSD switched to X.org in -current in July of 2004. See Eric Anholt's post to freebsd-current here, or the Slashdot writeup here. You can still use XFree86 if you like, but X.org is the default.