Too much ram: it’s possible

I’ve always said you can’t be too rich, too thin, or have too much RAM.  (I’m paraphrasing a quote from the Dutchess of Windsor.)  However, maybe you can have too much RAM.  Recent changes by Matthew Dillon have made it possible to run the kernel_map out of RAM depending on the quantity of video RAM and system RAM in use.

This isn’t a significant danger; I’m highlighting it because it’s an odd problem.  It’s easy to work around for now.  There’s a new utility, kmapinfo, to show mow much kernel memory is being used.

Update for spamassassin

This has been bouncing around other news outlets, but I’ll mention it here: There’s an out of data SpamAssassin rule that can potentially mark mail as spam because of the 2010 date.  A mail to tech-pkg@netbsd.org describes the various fixes.

The step of ‘sa-update && /etc/rc.d/spamd restart’ seems to have fixed it for me.  Incidentally, if you are using SpamAssassin, sa-update is a good tool to run on a regular basis.

Messylaneous for 2009/12/30

It’s New Year’s Eve Eve, and so here are a bunch of links I’ve built up over the past few days.

Chaos Communication Congress notes

Matthias Schmidt is posting to Twitter about his time at 26c3 with other DragonFly developers, on his own feed and in @dragonflybsd.  (if you are reading this via a Twitter link, you may already know that.)  Follow the #26c3 tag if you want to see all the news about the event.  A quick scan shows some interesting mobile phone security problems have been discovered.  There’s streaming video too.