Should There Be A Unified BSD Operating System?

[BitRot]

Macs are for girls and gays.

Back to the "Linux and BSD should work together" part: They do. They are inspired by each other.

I suggest you stop this childish behaviour.

[Cthulhux]

Nah. When people start to call Macs "elitist systems", it can't be much more childish.

[0xBADCODE]

Oh, it's exactly like this comix. Will not work: different projects have different goals and managed to change both parts of user-mode code and kernel code in incompatible ways.

And they also failed to integrate corporations into their working processes. You see, BSD license allows to close code and don't give back anything. That's where it backfires. Corporations close all the code they can and never contribute anything to upstream. So whole project is slowed down. Linux does not haves this issue due to GPL requirements.

[LightBit]

And they also failed to integrate corporations into their working processes. You see, BSD license allows to close code and don't give back anything. That's where it backfires. Corporations close all the code they can and never contribute anything to upstream. So whole project is slowed down. Linux does not haves this issue due to GPL requirements.

http://www.phoronix.com/scan.php?pag...tem&px=MTIyNzU

[joe_gunner]

Oh, it's exactly like this comix. Will not work: different projects have different goals and managed to change both parts of user-mode code and kernel code in incompatible ways.

And they also failed to integrate corporations into their working processes. You see, BSD license allows to close code and don't give back anything. That's where it backfires. Corporations close all the code they can and never contribute anything to upstream. So whole project is slowed down. Linux does not haves this issue due to GPL requirements.

That's right, Linux only has the 1 x month obligatory GPL violation and everyone arguing politics instead of writing code. Oh please.

[vermaden]

There are hundreds of Linux distributions and several BSD's ... and BSD needs unification?

But jokes aside, one unified BSD 'to rule them all' would be nice. Is the name TheBSD already taken?

[a user]

Nah. When people start to call Macs "elitist systems", it can't be much more childish.

you proved the opposite.

[V!NCENT]

Ask yourself why these forks exist. Then revisit the question, and the simple answer is; no.

Why?
1. OpenBSD does puts too much emphasis on security, with a development model that hinders developmental progres on anything that is not security. This alone already invaliddates the question.

2. Dragon wants different scheduling styles, not compatible with FreeBSD.

3. NetB-...

Oh fsck it; NO!

[ryao]

Oh, it's exactly like this comix. Will not work: different projects have different goals and managed to change both parts of user-mode code and kernel code in incompatible ways.

And they also failed to integrate corporations into their working processes. You see, BSD license allows to close code and don't give back anything. That's where it backfires. Corporations close all the code they can and never contribute anything to upstream. So whole project is slowed down. Linux does not haves this issue due to GPL requirements.

The GPL allows corporations to avoid disclosing changes to code too. Facebook uses a ton of GPL software and I have not seen them disclose their changes to the GPL licensed components. For example, they maintain their own internal fork of MySQL and I doubt that any of the code in it will ever be released for use outside of Facebook. At the same time, Netflix is in a similar position with FreeBSD, but they are upstreaming their modifications:

http://lists.freebsd.org/pipermail/f...ne/068129.html

Juniper Networks also contributes code to FreeBSD. They are one of the companies that would have been forced to disclose changes under the GPL, yet they use FreeBSD and contribute improvements without a legal requirement to release anything.

With that said, nearly all of the code being contributed to Linux was written to further corporate interests and would have likely been contributed anyway. Virtually none of the code contributions are things that corporations were forced to release. Whenever a company has code that they do not want to release, they either use something other than Linux or keep it internal.

[crazycheese]

Exactly how it is written in Linux From Scratch book:


Unification of Linux was only interesting for proprietary software.

Dear BSD, go unify, crap even more Instead of fighting with proprietary, you are fighting with a FLOSS operating system like a parasite. I bet, you already got blessing from your holy fathers microsoft & apple


When I see claims from BSD parasites like "BSD should work with Linux" or "Linux should not implement features that are not welcome/accepted within BSD", you only confirm your parasite behaviour. You essentially make the same developers to carry DOUBLE weight. The only reason why someone would claim this - is to slow down the development and fragment it.

BSD license is only good for *parts*. And even then, it is not far from "public domain", why bother?