Linked by Julian Djamil Fagir on Thu 14th Feb 2013 22:23 UTC
Thread beginning with comment 552701
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/18/13 21:06 UTC
Linked by Thom Holwerda on 05/18/13 7:37 UTC
Linked by fran on 05/18/13 1:38 UTC
Linked by Thom Holwerda on 05/17/13 23:35 UTC, submitted by kragil
Linked by MOS6510 on 05/17/13 22:22 UTC
Linked by Thom Holwerda on 05/17/13 22:15 UTC, submitted by Tom
Linked by Thom Holwerda on 05/16/13 21:41 UTC
Linked by Thom Holwerda on 05/16/13 17:04 UTC
Linked by Thom Holwerda on 05/16/13 13:17 UTC
Linked by Thom Holwerda on 05/16/13 12:06 UTC
More News »
Sponsored Links



Member since:
2010-12-22
Dragonfly is one of the more distinctive variants of BSD. It has a whole boat load of features not seen in FreeBSD.
Yeah. It started with just the desire of make the Operation System more scalable and "cluster oriented from roots", and today we have wonderfull features in it.
Unless things have changed significantly recently, PC-BSD isn't really a fork of FreeBSD, it's more a "distribution". It's point was to give users a no-fuss desktop ready version of FreeBSD. And as PC-BSD is 100% FreeBSD compatible (after all, it /IS/ FreeBSD), I think it deserves it's place as it takes any pressure off the FreeBSD devs from having to cater their limited resources to a multitude of different users expectations (or in layman's terms, FreeBSD can focus on building a solid base and PC-BSD and focus on shipping FreeBSD with the desktop preinstalled and
configured to run perfected out-of-the-box).
Yeah. I´ve used bad example here, sorry. PC-BSD helped a lot with docs. I could use bitrig and mirOS here. Both of them want a more "permissive" or less "Theo centric" version of the ol´good OpenBSD