MidnightBSD 0.4 Betters The FreeBSD Desktop

[Cthulhux]

Meh, its Linux

... so you're using code from FreeBSD. Point proven. Thanks and good night.

edit: And no, Mac OS X is no "full-featured BSD", it uses FreeBSD parts for its (Apple) userland and (Mach-based) kernel, so it's pretty much a fork of BSD but not a "full-featured BSD".

[brosis]

Name your OS then. Because EVERY OS on the PLANET uses SOME portion of BSD code. Even the linux kernel has BSD code, every GPL project has SOME BSD code. So unless you're about to tell me that you went through, made your own operating system, used ALL GPL projects, checked the source OF those projects and if you found one file that was tagged as BSD-licensed you rewrote that file yourself, and did that for ALL components of your chosen operating system.

So yeah, name your OS Brosis. Because you had to have written most of it by yourself.

Meh, its Linux and it has no BSD license, just GPL.
If it would be windows, it would be EULA.
If Solaris - then CDDL.
Or any proprietary OS that just gives a damn about BSD, simply stripping its code. Like windows.
And how about Linux+GNU userland+Emacs+W3 on top of it? Possible.

Either way, I claimed that BSD is parts-bin license and Cthulhux asked if my OS is without BSD code. Of course, it is without -- cut it, change it, copy paste it, rename it. Thing is - EULA protects the contents and restricts license modifications; GPL protects the contents and restricts license modifications. Parts bin license? How about companies releasing everything via BSD, not connected to BSD or partially (interfaces), but just "dumping"? Its like giving away the work. Never claimed if its bad, but its sure bad for a company. Its like carrying water in a sieve. Hence BSD is not a stable spot to build upon. Hence BSD OS is always awkward, incomplete or outclassed. Usually by proprietary equivalents. Because,.. if BSD dev's would realize that, they would have picked GPL license - unless they are actually proprietary developers, in disguise - or for laughs. Usually in disguise, because they start to shift from topic right on, or try to pick different argumentation vector.
That said, I am not against people using BSD - its their own "problem".. Most of the times they are either working for proprietary or just can't afford a better proprietary solution yet misunderstand and hate GPL. "Full featured BSD", hehe. MacOSX is your "full featured BSD", get over it, Cthulhux.

Not sure about Windows (MS has probably completely rewritten the TCP/IP stack by now) but AFAIK pretty much every other OS out there has some BSD-licensed code in it. Even if most of the OS code has a different license (eg Linux kernel and GPL) the BSD or X11 bits retain their original license...

... or maybe when you say "parts-bin license" that's code for BSD ?

Two times on spot, you are a sniper, Sir.
X11 and Wayland refrain from removing BSD license, because it would make no sense.. It would make Ctulhux cry -___- and reduce testing area for no benefit. Mir choice of GPL3 would be nice thing, if just Canonical won't be so hideous and CLA'neous.. and also, we don't want BSD guys to stick with outdated X11... I mean, they already have no systemd and are dying out of self-poisoning. We are sure no meanies,.. kinda unlike their proprietary chiefs they work for in prime time.

[brosis]

Would you care to explain just what you're needing to do with static linking that can't be handled by bundling the libraries into your package and dynamically linking them? The Unreal engine after all did this to great success (didn't have anything to do with Qt but all of the important libraries were dynamically linked so you could just swap them out) and it is a proprietary application.

Yes, that's possible; but UI isn't most critical part of their application, so why not.

Only two I could think of are embedded applications and security, but if you're doing embedded applications you really shouldn't be bundling or doing static linking as opposed to linking to the system copy to save both on space and memory, and for security it's really nonsense because if the attacker has the rights to switch out the library then the system is compromised anyway.

Embedded when not low on resources, but strong DRM; or security in field with no network or direct access to code are my bets.

[Artemis3]

What I find more interesting is their use of GNUStep and ?toil?.

Window Maker lives!

[Luke_Wolf]

You need to static-link Qt and for that you need proprietary license from (pay to) Digia.
If you don't static-link or don't release, then you can use GPLed Qt, but none of the proprietaries can do that.

Would you care to explain just what you're needing to do with static linking that can't be handled by bundling the libraries into your package and dynamically linking them? The Unreal engine after all did this to great success (didn't have anything to do with Qt but all of the important libraries were dynamically linked so you could just swap them out) and it is a proprietary application. Only two I could think of are embedded applications and security, but if you're doing embedded applications you really shouldn't be bundling or doing static linking as opposed to linking to the system copy to save both on space and memory, and for security it's really nonsense because if the attacker has the rights to switch out the library then the system is compromised anyway.

[bridgman]

Maybe Plan 9 ?

[Ericg]

Hah! Windows uses BSD code and my OS doesn't - it's not licensed under BSD so where is it? Fix your license, then come back trolling. But most likely you won't - and nobody cares. A parts bin license is also needed, but only for interoperability - otherwise, we will have proprietary mushroom and no opensource competitor will make it, just because proprietaries will re-use BSD and a little extra to the "top" - exactly why everyone uses MacOSX instead of BSD. Still clueless?

Name your OS then. Because EVERY OS on the PLANET uses SOME portion of BSD code. Even the linux kernel has BSD code, every GPL project has SOME BSD code. So unless you're about to tell me that you went through, made your own operating system, used ALL GPL projects, checked the source OF those projects and if you found one file that was tagged as BSD-licensed you rewrote that file yourself, and did that for ALL components of your chosen operating system.

So yeah, name your OS Brosis. Because you had to have written most of it by yourself.

[Cthulhux]

That brosis guy seems not to understand the meaning of either "code" or "license"...

[bridgman]

Not sure about Windows (MS has probably completely rewritten the TCP/IP stack by now) but AFAIK pretty much every other OS out there has some BSD-licensed code in it. Even if most of the OS code has a different license (eg Linux kernel and GPL) the BSD or X11 bits retain their original license...

... or maybe when you say "parts-bin license" that's code for BSD ?

[brosis]

Your OS uses BSD code, unless you use Windows.

Hah! Windows uses BSD code and my OS doesn't - it's not licensed under BSD so where is it? Fix your license, then come back trolling. But most likely you won't - and nobody cares. A parts bin license is also needed, but only for interoperability - otherwise, we will have proprietary mushroom and no opensource competitor will make it, just because proprietaries will re-use BSD and a little extra to the "top" - exactly why everyone uses MacOSX instead of BSD. Still clueless?