Slashdot Mirror

How can BSD be dying when it has a mascot like this?! Linux needs to get its act together if it's going to compete with the kind of hot chicks and gorgeous babes that BSD has to offer!

You just can't take Linux seriously when its fronted by losers like these. You Linux groupies need to find some sexy girls like her! I mean just look at this girl! Doesn't she make you hard? I know this little hottie floats my boat! 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 cock teaser. Even this old bearded Unix guru is apparently unable to take his eyes off her!

With sexy chicks like the lovely Ceren you will have people queuing up to buy open source products. Look! This guy can't get in there fast enough with her in the doorway! Come on, you must admit she is better than an overweight penguin! Don't you wish you could get one of these? Join the campaign for more cute open source babes today!

How can BSD be dying when it has a mascot like this?! Linux needs to get its act together if it's going to compete with the kind of hot chicks and gorgeous babes that BSD has to offer!

You just can't take Linux seriously when its fronted by losers like these. You Linux groupies need to find some sexy girls like her! I mean just look at this girl! Doesn't she make you hard? I know this little hottie floats my boat! 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 cock teaser. Even this old bearded Unix guru is apparently unable to take his eyes off her!

With sexy chicks like the lovely Ceren you will have people queuing up to buy open source products. Look! This guy can't get in there fast enough with her in the doorway! Come on, you must admit she is better than an overweight penguin! Don't you wish you could get one of these? Join the campaign for more cute open source babes today!

How can BSD be dying when it has a mascot like this?! Linux needs to get its act together if it's going to compete with the kind of hot chicks and gorgeous babes that BSD has to offer!

You just can't take Linux seriously when its fronted by losers like these. You Linux groupies need to find some sexy girls like her! I mean just look at this girl! Doesn't she make you hard? I know this little hottie floats my boat! 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 cock teaser. Even this old bearded Unix guru is apparently unable to take his eyes off her!

With sexy chicks like the lovely Ceren you will have people queuing up to buy open source products. Look! This guy can't get in there fast enough with her in the doorway! Come on, you must admit she is better than an overweight penguin! Don't you wish you could get one of these? Join the campaign for more cute open source babes today!

cvsup, portupgrade and it is working like charm.

the antitrust service pack

For those of you who haven't heard of this, yet, here are places you can get it:

Mirror 1a
Mirror 1b
Mirror 2
Mirror 3
Mirror 4

These mirrors also work well:

Mirror 5
Mirror 6

How can BSD be dying when it has a mascot like this?! Linux needs to get its act together if it's going to compete with the kind of hot chicks and gorgeous babes that BSD has to offer!

You just can't take Linux seriously when its fronted by losers like these. You Linux groupies need to find some sexy girls like her! I mean just look at this girl! Doesn't she make you hard? I know this little hottie floats my boat! 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 cock teaser. Even this old bearded Unix guru is apparently unable to take his eyes off her!

With sexy chicks like the lovely Ceren you will have people queuing up to buy open source products. Look! This guy can't get in there fast enough with her in the doorway! Come on, you must admit she is better than an overweight penguin! Don't you wish you could get one of these? Join the campaign for more cute open source babes today!

How can BSD be dying when it has a mascot like this?! Linux needs to get its act together if it's going to compete with the kind of hot chicks and gorgeous babes that BSD has to offer!

You just can't take Linux seriously when its fronted by losers like these. You Linux groupies need to find some sexy girls like her! I mean just look at this girl! Doesn't she make you hard? I know this little hottie floats my boat! 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 cock teaser. Even this old bearded Unix guru is apparently unable to take his eyes off her!

With sexy chicks like the lovely Ceren you will have people queuing up to buy open source products. Look! This guy can't get in there fast enough with her in the doorway! Come on, you must admit she is better than an overweight penguin! Don't you wish you could get one of these? Join the campaign for more cute open source babes today!

A naked freeBSD BoothBabe has been spotten naked in the wild! Some say it's a hoax, but should be regarded as a threat to vaginal security!

Let your concious decide...
From the anals of the LinuxWorld 2000 Expo: freeBSD BoothBabe

From the anals of the Internet: FreeBSD BoothBabe gone a'whorein'

What is it? Is it real or fake? I'm going to LinuxWorld 2003 Expo to find out for myself to make sure *BSD sure as fuck isn't dying!

A naked freeBSD BoothBabe has been spotten naked in the wild! Some say it's a hoax, but should be regarded as a threat to vaginal security!

Let your concious decide...
From the anals of the LinuxWorld 2000 Expo: freeBSD BoothBabe

From the anals of the Internet: FreeBSD BoothBabe gone a'whorein'

What is it? Is it real or fake? I'm going to LinuxWorld 2003 Expo to find out for myself to make sure *BSD sure as fuck isn't dying!

That link you provided doesn't seem to work, here is the correct link.

BSD/OS, a commercial version of FreeBSD

The BSD Family Tree

Quite sad to see Wind River in trouble ("The companyâ(TM)s revenue declined 20 percent last quarter" - Electronic News) as it decreases FreeBSD deployement among enterprises.

I don't know much about other firms using BSD (like Wasabi Systems) however it seems it's more difficult for them to sell BSD systems compared with Linux distributors.

Quite contradictoraly, BSD license is more "liberal" than Linux from the enterprise point of view which can use the code with minimal restrictions (FreeBSD License) Wind River and Wasabi Systems gives a generous access to their proprietary source to some bsd developpers)

As Linux gains momentum, I hope IT managers will see those nice BSD lurking around, using them, and helping maintaining them (like hiring developpers to work on these systems).

"[...] without GNU, there never would have been OS [...]"

If by OS you mean OSS and not Operating System then I'm afraid that I respectfully disagree.

• Pentium 4 2.8GHz with HyperThreading (2 CPUs in 1): $266.00
• Asus P4C800 motherboard & 800MHz frontside bus: $190
• 512MB 5ns RAM: $89.99
• Enlight case: $59.00
• ATI Radeon 9600 AGP 8x 128MB video: $178.00
• Western Digital 120GB 7200RPM hard drive: $108.00
• Generic DVD drive: ~$30
• Can of metallic blue spray-paint to personalise the case: $5
• FreeBSD 5.1: $free

Hah. Not a chance. You see, that Apple has a daemon inside it, and that pitchfork looks sharp.

Okey, what is this? Isn't this the sort of question you usually ask in a discussion forum or even IRC? I don't see why someone whould make a slashdot article over it. I did a search on google and found many resources for how to fix this, take a look here, here and here. And if you want to browse the results yourself, here.
I've googled and found nothing of real use there.
I don't have a device like this myself, but from the results I got I'll say it looks quite useful.

Since Panther is based on FreeBSD 5.0 you may want to check out the release notes for it.

Of course FreeBSD 5.1 just came out last week or so (release notes.).

Since Panther is based on FreeBSD 5.0 you may want to check out the release notes for it.

Of course FreeBSD 5.1 just came out last week or so (release notes.).

FreeBSD 5.0

Huh? That doesn't make much sense. Perhaps they've integrated more code from FreeBSD, but FreeBSD 5.1 has been out for some time now.

WTF is the $129 price tag for? Can you imagine the uproar if Microsoft were to charge $129 for minor version upgrades, then immediately announce the previous version was "over" and force everyone to upgrade?

Why the fuck would anyone pirate or purchase Windows XP? I can understand settling for it if it came with your computer and you don't want to bother with making a new partition or something, but if you're getting a new operating system, might as well make it one that doesn't suck, like FreeBSD for example.

Ok, here's the patch.

The Open Group already spoke to the FreeBSD Project about it, you can read the thread here. And the CVS commit here.

The Open Group already spoke to the FreeBSD Project about it, you can read the thread here. And the CVS commit here.

It is an obvious troll, but I'll bite anyway.

FreeBSD has Linux Binary Compatibility which allows Linux binaries to run on FreeBSD.

"It is also reported that in some situations, Linux binaries perform better on FreeBSD than they do under Linux."

It's my understanding that BSD was originally based on BSD UNIX 4.3 (lite?) and now contains code from 4.4-lite and of course many other sources now. I don't know nearly as much about it as I would like to, or would need to in order to speak knowledgeably about that aspect of things.

Anyway, it will be interesting to see how this comes out, and what arguments Apple uses. IANAL (had to get that in there somewhere) and I don't know any details either but it seems to me like that could be a possible defense if they don't already have another one.

Do you mean the Look and Feel case that Apple lost?

In fact, I don't see Open Group suing FreeBSD over *their* use of the UNIX trademark, right on their front page!

It is official; Netcraft now confirms: *BSD is growing

One more crippling bombshell hit the already beleaguered Windows community when IDC confirmed that *BSD market share has risen yet again, now up to more than 30 percent of all servers. Coming on the heels of a recent Netcraft survey which plainly states that *BSD has gained more market share , this news serves to reinforce what we've known all along. *BSD is sending other OSes into complete disarray, as fittingly exemplified by topping the charts in the recent Sys Admin comprehensive networking test.

You don't need to be a Daemon to predict *BSD's future. The hand writing is on the wall: *BSD faces a long and prosperous future. In fact there won't be any future at all for Windows Server because *BSD is growing. Things are looking very good for *BSD. As many of us are already aware, *BSD continues to gain market share. Red ink flows from Redmond like a river of blood.

FreeBSD is the most loved of them all, having gained 93% more core developers. The sudden and pleasant release of the long developed 5.0 only serves to underscore the point more clearly. There can no longer be any doubt: FreeBSD is growing.

Let's keep to the facts and look at the numbers.

FreeBSD leaders state that there are innumerable users of FreeBSD. How many users of FreeBSD are there? Let's see. Every time FreeBSD a huge number of FreeBSD users cvsup their tree with the closest mirror. Notice there are hundreds of FreeBSD mirrors under constant stress. This is consistent with the number of FreeBSD Usenet posts, of which there are many hundreds per day.

Due to the merger of Walnut Creek and BSDi, and Juniper JunOS, cool new technologies and so on, FreeBSD is expanding into more markets than ever. FreeBSD has become more than the sum of its parts.

All major surveys show that *BSD has steadily gained in market share. *BSD is very powerful and its long term survival prospects are very bright. If Windows is to survive at all it will be among OS dilettante dabblers. *BSD continues to improve. The progress achieved is nothing short of a miracle. For all practical purposes, *BSD is alive and kicking.

Fact: *BSD will kick your ass

As the release notes state, FreeBSD 5.1 includes the latest stable releases of GNOME and KDE, 2.2.1 and 3.1.2 respectively.

Getting FreeBSD 5.1 would be a great way to easily get the latest stable versions of these desktop environments as they were intended to be (without all the distribution-specific customizations made by Red Hat, SuSE, and so on).

Granted, you could also use Gentoo current or Debian unstable, but FreeBSD 5.1 is likely to be more stable (in the sense of not frequently changing) and you can get it on CD.

As the release notes state, FreeBSD 5.1 includes the latest stable releases of GNOME and KDE, 2.2.1 and 3.1.2 respectively.

Getting FreeBSD 5.1 would be a great way to easily get the latest stable versions of these desktop environments as they were intended to be (without all the distribution-specific customizations made by Red Hat, SuSE, and so on).

Granted, you could also use Gentoo current or Debian unstable, but FreeBSD 5.1 is likely to be more stable (in the sense of not frequently changing) and you can get it on CD.

After the problems that occurred when the last release was announced early, the FreeBSD release team created a new permissions scheme so that only mirror admins could access the 5.1 release directory before the official release. If anybody else tried to access the 5.1 release directory (even on a mirror site), they would get a 403 (access denied) error.

In this case, clearly it was of little use for Slashdot to announce the availability of FreeBSD 5.1 early.

After the problems that occurred when the last release was announced early, the FreeBSD release team created a new permissions scheme so that only mirror admins could access the 5.1 release directory before the official release. If anybody else tried to access the 5.1 release directory (even on a mirror site), they would get a 403 (access denied) error.

In this case, clearly it was of little use for Slashdot to announce the availability of FreeBSD 5.1 early.

You should ask here:

http://lists.freebsd.org/mailman/listinfo/freebsd- current

• A number of features are not yet finished. Examples from the
  feature list above include SMPng and KSE. While suitable for testing
  and experimentation, these features may not be ready for production
  use.
• Because of changes in kernel data structures and ABIs/APIs,
  third-party binary device drivers will require modifications to work
  correctly under FreeBSD 5.1. There is a possibility of more minor
  ABI/API changes before the 5-STABLE branch is created.
• Several parts of FreeBSD's base system functionality have been
  moved to the Ports Collection. Notable examples include Perl,
  UUCP, and most (but not all) games. While these programs are
  still supported, their removal from the base system may cause some
  confusion.
• Some parts of the FreeBSD base system have fallen into a state of
  disrepair due to a lack of users and maintainers. These have been
  removed. Specific examples include the generation of a.out-style
  executables, XNS networking support, and the X-10 controller
  driver.
• A number of ports and packages do not build or do not run
  correctly under FreeBSD 5.0, whereas they did under FreeBSD
  4-STABLE. Generally these problems are caused by compiler toolchain
  changes or cleanups of header files.
• Many FreeBSD 5.1 features are seeing wide exposure for the first
  time. Many of these features (such as SMPng) have broad impacts on
  the kernel.
• A certain amount of debugging and diagnostic code is still in
  place to help track down problems in FreeBSD 5.1's new features. This
  may cause FreeBSD 5.1 to perform more slowly than 4-STABLE.
• Features are only added to the 4-STABLE development branch after
  a ``settling time'' in -CURRENT. FreeBSD 5.1 does not have the
  stabilizing influence of a -STABLE branch. (It is likely that the
  5-STABLE development branch will be created sometime after
  5.2-RELEASE.)
• Documentation (such as the FreeBSD Handbook and FAQ) may not reflect changes recently made to
  FreeBSD 5.1.

• A number of features are not yet finished. Examples from the
  feature list above include SMPng and KSE. While suitable for testing
  and experimentation, these features may not be ready for production
  use.
• Because of changes in kernel data structures and ABIs/APIs,
  third-party binary device drivers will require modifications to work
  correctly under FreeBSD 5.1. There is a possibility of more minor
  ABI/API changes before the 5-STABLE branch is created.
• Several parts of FreeBSD's base system functionality have been
  moved to the Ports Collection. Notable examples include Perl,
  UUCP, and most (but not all) games. While these programs are
  still supported, their removal from the base system may cause some
  confusion.
• Some parts of the FreeBSD base system have fallen into a state of
  disrepair due to a lack of users and maintainers. These have been
  removed. Specific examples include the generation of a.out-style
  executables, XNS networking support, and the X-10 controller
  driver.
• A number of ports and packages do not build or do not run
  correctly under FreeBSD 5.0, whereas they did under FreeBSD
  4-STABLE. Generally these problems are caused by compiler toolchain
  changes or cleanups of header files.
• Many FreeBSD 5.1 features are seeing wide exposure for the first
  time. Many of these features (such as SMPng) have broad impacts on
  the kernel.
• A certain amount of debugging and diagnostic code is still in
  place to help track down problems in FreeBSD 5.1's new features. This
  may cause FreeBSD 5.1 to perform more slowly than 4-STABLE.
• Features are only added to the 4-STABLE development branch after
  a ``settling time'' in -CURRENT. FreeBSD 5.1 does not have the
  stabilizing influence of a -STABLE branch. (It is likely that the
  5-STABLE development branch will be created sometime after
  5.2-RELEASE.)
• Documentation (such as the FreeBSD Handbook and FAQ) may not reflect changes recently made to
  FreeBSD 5.1.

• A number of features are not yet finished. Examples from the
  feature list above include SMPng and KSE. While suitable for testing
  and experimentation, these features may not be ready for production
  use.
• Because of changes in kernel data structures and ABIs/APIs,
  third-party binary device drivers will require modifications to work
  correctly under FreeBSD 5.1. There is a possibility of more minor
  ABI/API changes before the 5-STABLE branch is created.
• Several parts of FreeBSD's base system functionality have been
  moved to the Ports Collection. Notable examples include Perl,
  UUCP, and most (but not all) games. While these programs are
  still supported, their removal from the base system may cause some
  confusion.
• Some parts of the FreeBSD base system have fallen into a state of
  disrepair due to a lack of users and maintainers. These have been
  removed. Specific examples include the generation of a.out-style
  executables, XNS networking support, and the X-10 controller
  driver.
• A number of ports and packages do not build or do not run
  correctly under FreeBSD 5.0, whereas they did under FreeBSD
  4-STABLE. Generally these problems are caused by compiler toolchain
  changes or cleanups of header files.
• Many FreeBSD 5.1 features are seeing wide exposure for the first
  time. Many of these features (such as SMPng) have broad impacts on
  the kernel.
• A certain amount of debugging and diagnostic code is still in
  place to help track down problems in FreeBSD 5.1's new features. This
  may cause FreeBSD 5.1 to perform more slowly than 4-STABLE.
• Features are only added to the 4-STABLE development branch after
  a ``settling time'' in -CURRENT. FreeBSD 5.1 does not have the
  stabilizing influence of a -STABLE branch. (It is likely that the
  5-STABLE development branch will be created sometime after
  5.2-RELEASE.)
• Documentation (such as the FreeBSD Handbook and FAQ) may not reflect changes recently made to
  FreeBSD 5.1.

If RH is pricing itself out of the market you have other choices.

Here you go :))

... is always fun to whatch when a new big release comes out.

The release notes mention that an experimental amd64 release is available, but don't mention that it can be downloaded from here, including ISO images.

Most of the credit for its rapid development goes to Peter Wemm, who nearly single-handedly took the X86-64 architecture from "it can't even mount the root filesystem or exec init" to a nearly-polished release in little more than a month. (And, no, it wasn't just a matter of copying what NetBSD did; the processor-specific parts of FreeBSD and NetBSD are quite different.)

-Ed

The release notes mention that an experimental amd64 release is available, but don't mention that it can be downloaded from here, including ISO images.

Most of the credit for its rapid development goes to Peter Wemm, who nearly single-handedly took the X86-64 architecture from "it can't even mount the root filesystem or exec init" to a nearly-polished release in little more than a month. (And, no, it wasn't just a matter of copying what NetBSD did; the processor-specific parts of FreeBSD and NetBSD are quite different.)

-Ed

If you are interested in the respective merits of FreeBSD 5.1 over 4.x and are unsure which one to install, you might want to see the Early Adopter's Guide for FreeBSD 5.1-RELEASE

Does it run lunix?

I don't know what lunix is, but it does run Linux.

Since *BSD is obviously dying, let's ./ it just like we do with SCO.

Download a large file from here.

or launch wget processes:

wget http://www2.freebsd.org/ports/os2/perl_inf.zip

Excuse me, but that is the wrong removal utility. The correct one is here

Well I'm thinking long term, but what if instead of error checking now like in TCP, there was some hardware processing of checksums....

Excerpt:

This is somewhat similar to the situation that FreeBSD faced in the 3.X series. Work on 3-CURRENT trudged along seemingly forever, and finally a cry was made to ``just ship it'' and clean up later. This decision resulted in the 3.0 and 3.1 releases being very unsatisfying for most, and it wasn't until 3.2 that the series was considered ``stable''. To make matters worse, the RELENG_3 branch was created along with the 3.0 release, and the HEAD branch was allowed to advance immediately towards 4-CURRENT. This resulted in a quick divergence between HEAD and RELENG_3, making maintenance of the RELENG_3 branch very difficult. FreeBSD 2.2.8 was left for quite a while as the last production-quality version of FreeBSD.

Our intent is to avoid repeating that scenario with FreeBSD 5.x. Delaying the RELENG_5 branch until it is stable and production quality will ensure that it stays maintainable and provides a compelling reason to upgrade from 4.X, To do this, we must identify the current areas of weakness and set clear goals for resolving them.

I think that the main problem is that the average /. reader (and probably OSS developer) has a different view of what a computer is for. They view it as a tool (an incredibly powerful, and almost indispensible tool, to be fair), which is interesting in its own right, while for me (and I think most computer users) the computer is a tool which is doing its job best when you don't notice it's there. I consider any UI element which forces me to conciously think that I am using a computer to be a bug.

If you're looking for a UN*X to run on x86 hardware, take a look at FreeBSD. It is a lot easier to admin than Linux (coming from a Linux background...) and doesn't suffer from dependency hell. On the other hand, you will want a fairly wide pipe to the Internet, or a DVD distribution for installing software, since it will auto-fetch dependencies, which would be painful over a modem. Still not at OS X levels of ease, but not so hard to admin as Linux. Oh, and if you're using OS X you'll already be familiar with the FreeBSD userland (noticed how everything is in a logical place, instead of randomly scattered across the disk?)

The release schedule had this release planned for may 30, and the release of 5.1 set for June 5. Is it just me, or is 6 days between first release candidate and final release cutting it a bit fine? I know that 5.1 is not -STABLE (which is why I'm using 4.8, and looking forward to 5.2), but even so...

linux
bsd