Re: Unified BSD?

[pete wright]

On Mon, Nov 12, 2012 at 12:37 PM, Robin  Björklin
robin.bjork...@gmail.com wrote:



 Am I bat crap crazy for thinking it could be good to merge the four largest
 BSD variants out there, take the best bits and pieces out of each and
 create a Unified BSD?


you are not crazy for thinking this, and fortunately there is nothing
prohibiting you from doing so (or a collective group of people, or
company etc...).  One thing you will see in the BSD Unix systems is
there is quite a bit of cross pollination between projects.  The
largest example current example of this from my perspective is support
for OpenBSD's pf packet filter in FreeBSD.  This is a packet filter
built to suit the OpenBSD developers goals, but it did not restrict
FreeBSD from supporting this packet filter and hopefully both projects
benefit from this collaboration (wider code exposure of the pf code,
and wider choice of packet filters for FreeBSD users).

My opinion is that with the current state of the BSD's this is one of
its stronger suits - we have multiple projects right now building
entire operating systems to suit each of the projects stated goals and
developer wishes.  this would be opposed to gnu/linux where you are
cobbling together many disparate sources to build your distribution
(some of which will have goals that may not line up with your goals).
with this diversity we still cross pollinate ideas and methods, but
are still allowed to spend our limited resources focusing on our
projects core goals.

-pete

-- 
pete wright
www.nycbug.org
@nomadlogicLA

Re: #define failure opportunity

[pete wright]

On 11/28/05, Qv6 [EMAIL PROTECTED] wrote:
 On Monday 28 November 2005 04:04 pm, Theo de Raadt wrote:
  This is why OpenBSD/OpenSSH does not need to hire a spin doctor.
 
  Other people do it for us ;)
 
  http://www.ssh.com/company/newsroom/article/684/
 
  And... thanks to those of you who supported us when they were
  threatening to sue us years ago..


 Intersting news.

 I once worked for a major Telecom firm that used a commercial
 implementation of ssh. I was curious and I asked one of the other
 techies why pay for ssh when openssh is available. Because we can go
 to the company for support was his answer.

 I couldn't help but wonder what type of issues people encounter while
 using openssh. Aside from the usuall software bugs, has there really
 been any major problems with openssh that the community has not fixed
 promptly?


Not that I don't think openssh is superior for the fact that it *is*
open software, I bet that the company in question needs software
support lisc. for legal issues.  If the software goes tit's up and
costs the company N dollar's it is easier to get that money from a
commercial entity whom you have a contract with (or more likely get
money via a insurance broker of some sort).  At least that's the best
I've been able to see through that line of reasoning :^)

-p


--
~~o0OO0o~~
Pete Wright
www.nycbug.org
NYC's *BSD User Group