Linked by Julian Djamil Fagir on Thu 14th Feb 2013 22:23 UTC
Thread beginning with comment 552580
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.
The previous poster meant integration at the system level, not between projects. FreeBSD for example is responsible for the kernel, kernel modules, userland, toolchain, and installer, they are all managed, developed and tested together. Compare to linux where the kernel comes from one place, the userland from another, and they are integrated downstream from the initial developer.
They are as about badly integrated project wise as the 100s of Linux distros, but there are only 4 or 5, so that is an easier problem to deal with.
They created some forks when could be avoided:
While I agree with you point in theory, your examples are pretty terrible:
- Matt creater DragonFly because he was tired of people putting "band-aids" on FreeBSD, that should fix at one side and break other. This and the desire of have a better "cluster native OS" created this wonderfull piece of software.
Dragonfly is one of the more distinctive variants of BSD. It has a whole boat load of features not seen in FreeBSD.
- PC-BSD = Lack of a stronger desktop initiative by the FreeBSD guys. You know, if they have a installer for "desktop fluffy things" this could be avoided.
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).
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




Member since:
2010-12-22
Better integrated? They already have their incompatibilies between them and have to "cross-polenize" each other on the points where they lack of innovation/functionality. I love BSD but i disgree when people say that BSDs just create a fork when is needed. They created some forks when could be avoided:
- Matt creater DragonFly because he was tired of people putting "band-aids" on FreeBSD, that should fix at one side and break other. This and the desire of have a better "cluster native OS" created this wonderfull piece of software.
- Bitrig is a OpenBSD less conservative. I still se no other than "lego play" utility to this. I know that OpenBSD guys works hard, but their decisions tend to make all thing difficult, and create this fork.
- PC-BSD = Lack of a stronger desktop initiative by the FreeBSD guys. You know, if they have a installer for "desktop fluffy things" this could be avoided.
Some "BSD decisions" would not change, if Linux didn't existed.