[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: merger

They also have a nice login.conf (at least from the admin perspective).
It might be very similiar to the freebsd login.conf, so open sourcing
may be negligable.

- BSDi has a semi-SPARC port, FreeBSD has wanted to tackle that next,
  but Net/Open already have this.
- SMP is in both of those BSDs.  Whose is better?
- MAXIM - the admin interface.  Sort of moot given webmin.
- Install junk/look and feel.
- sysctl differences.  
- BSDi has a different filtering mechanism which includes rate limiting
  (I always used ipfilter, ANYHOW), FreeBSD has their own, plus
  dummy net for rate limiting and WAN emulation (eg. add 2000 miles
  of time to the packets and drop 8% of them - cool for testing).
Dunno what Mr. McKusick has done for BSDi's FFS, if anything.
BSDi had a different VM, but UVM seems to have wended it's way
through everyone's system.

- Full time, paid support?  A corporate shelter for those companies
  that insist on providing object only drivers and such.

Bigger diff for FreeBSD (obv).

Quoting Todd C. Miller (Todd.Miller@courtesan.com):
> In message <38C65D62.3D8BFF3@thinkquest.org>
> 	so spake Russ (demarest):
> 
> > This may not be the appropriate place but what effect with the BSDI and
> > Walnut Creek CDROM merger have on OpenBSD?
> 
> None really.  It does mean that most of BSDI's code will now be available
> under a BSD-style license.  I want their sort(1) fixes ;-)
> 
>  - todd