I’ve got “coverage” of most every BSD this week.
- OpenBSD has brought in OpenSSL – and is modifying it severely. Instead of linking to the many commits as they tear it into little bits, I’ll just link to this Lobste.rs post. Will it be OpenOpenSSL? It looks like it’s for internal consumption only. Undeadly has a similar summation. Apparently there’s a running blog of the changes, or at least the snarky comments.
- Have you never been to BSDCan? Dan Langille asks the question. As he points out, BSD conventions are awesome, where you get to meet some smart people and put names to faces.
- “I have been given the option of Linux or BSD at work…” A discussion of BSD as a Java development platform.
- FreeBSD has added the if_nf10bmac(4) driver, for the “NetFPGA-10G Embedded CPU Ethernet Core”, which appears to be a programmable network card? I’m not sure how it all works together.
- Goodbye EISA on FreeBSD. (Gone long ago on DragonFly.)
- NetBSD src and pkgsrc changes are being twittered. (NetBSD link does not work just now when I tried it.)
- PC-BSD Digest 26 mentions the addition of a new desktop environment called Lumina, built just for PC-BSD.
> Will it be called OpenOpenSSL?
Without permission any fork can’t have the name OpenSSL in it. From http://www.openssl.org/source/license.html:
* 4. The names “OpenSSL Toolkit” and “OpenSSL Project” must not be used to
* endorse or promote products derived from this software without
* prior written permission. For written permission, please contact
* openssl-core@openssl.org.
*
A shame that no one is defending the honor of dragonflybsd on the redit post.
I posted and noted I’ve been running java programs on DragonFly without trouble. There aren’t a lot of Java developers on DragonFly that are also reading that particular article, anyway, and a lot of the conversation is empty boosterism.
The NetBSD src twitter account should have been: https://twitter.com/netbsdsrc