News
Tips for git
Saifi Khan asked some questions about using git; I link to two sets of answers, because these little things are useful when you are starting with git. Or, in my case, don’t use it frequently enough to remember.
OpenSSL updated
OpenSSL has been updated to version 0.9.8l by Aggelos Economopoulos; this fixes a security vulnerability. The update is available for 2.4.1 and 2.5 – update to get it.
Messylaneous for 2009/11/07
Where I get more linkbloggy than usual:
According to the 5th slide in this presentation, Android’s libc, “Bionic”, is BSD-derived. Anyone know which BSD? It looks like “whatever” is the answer.
There’s a video out about
BSDCan 2010: May 13-14
BSDCan 2010 will be May 13th and 14th in Ottawa, Canada, with 2 days of classes beforehand. Maybe I’ll actually make it this year, like I wish every time…
pkg_rr extensions for the net-challenged
If you are often offline – voluntarily or involuntarily – there’s some changes coming to pkg_rolling-replace to deal with spotty online access.
Using NVIDIA on DragonFly
This has been around for a while, but I’m re-mentioning it because it’s not really linked anywhere: Simon ‘corecode’ Schubert has a version of the FreeBSD NVIDIA video driver that should work on DragonFly:
It’s x86_64 now, not amd64
Simon ‘corecode’ Schubert has changed 64-bit DragonFly to be tagged “x86_64″ instead of “amd64″. It seems most other operating systems use that for 64-bit system architechure names. So does pkgsrc, which may fix some recent builds on amd64 x86_64
BSDTalk 179: Jacek Masiulaniec on OpenSMTPd, Epitome
OpenBSD developer Jacek Masiulaniec gets 14 minutes of airtime in the most recent BSDTalk podcast.
ACPI update soon
Alexander Polakov has a further update for his new ACPI code. He now even provides a DragonFly ISO image and USB image so that a new system can be installed for testing. There’s already one positive report. It will probably go in this weekend.
More parallelism tests: NCPUs + 1 still
Saifi Khan ran Simon ‘corecode’ Schubert’s make parallelism test on a dual-cpu system, and the theory holds up: ‘make -j N’ where N == the number of CPUs, plus 1, will give the fastest build time. (graphed again!)