Recently, Sascha Wildner committed a huge number of changes to the various games, bringing them in line with what’s on NetBSD and style(9). This was all put together by Ulrich Spoerlein.
I draw attention to this not because it changed anything with the games in a functional sense, but because it’s huge (450 files changed, 31450 insertions(+), 29998 deletions(-)) and because it came out of nowhere. It’s always nice to have new surprise contributions arrive.
It’s New Year’s Eve Eve, and so here are a bunch of links I’ve built up over the past few days.
Everything that _why the lucky stiff did. (via) _why is one of those things that only the Internet lets exist. And he used DragonFly!
Roguelike games, evaluated via the Berlin Interpretation, on @Play. Also, a dedicated Roguelike handheld?
Naoya Sugioka is working on bringing tmpfs to DragonFly – I am a big fan of that idea.
top now uses CTIME, not WCPU.
Where I get more linkbloggy than usual:
Johannes Hofmann has taken over estd, a “frequency scaling daemon for NetBSD and DragonFly”. The newest release brings multicore support on DragonFly.
Stathis Kamperis, as part of his Summer of Code work, ported NetBSD’s POSIX message queues to DragonFly. He has a writeup of all the details, and even has test cases! It should be showing up in 2.5 soon.
Hubert Feyrer, for his PhD, put together a Virtual Unix Lab – a whole lab of NetBSD systems for teaching System Administration. It’s a good strategy for an environment where some percentage of the systems will be irretrievably mangled. It’s available as a book.
NetBSD now has a Projects Blog and a Twitter account. I’m not taking credit for the idea, but I do note a definite similarity between that and the DragonFly Digest, to which I say: quick, someone do this for FreeBSD and/or OpenBSD! More attention to all the BSD work being done is positive.
Daniel Lorch is working on a port of Hammer to Linux’s VFS, though since he’s using FUSE, it will be able to reach other systems, like NetBSD. The code is accessible.
There is, of course, DragonFly project ideas for Google’s Summer of Code. There are also idea pages up for FreeBSD and NetBSD, both also participating this year.
Nikita Glukhov is porting tmpfs from FreeBSD/NetBSD, and is looking for some feedback.
I’ve wanted tmpfs or something similar for a while; I have a reoccurring (if not quite realistic) fantasy of building a system with a ridiculous amount of RAM and using it as a disk.
BSDTalk has Andrew Doran of NetBSD talking about the not-yet-out NetBSD 5 release, for 22 minutes.
“Desktop NetBSD” – with the DragonFly LiveDVD and installer, we’re almost able to do the same thing now – a skim of that project page seems to imply we just need to add some more packages. (via)
A vulnerability in telnetd code common to FreeBSD and DragonFly was just discovered; it’s been fixed in DragonFly using code from NetBSD in 1995, strangely enough. (via #dragonflybsd on EFNet)
This has been all over the Intarwebs at this point, but: there’s a good rumor that the next Sidekick phone will be running NetBSD on the inside. Danger, the company that makes the Sidekick, was bought by Microsoft, which makes this a BSD-based phone produced by Microsoft. I never thought I’d type that sequence of words together.
hubertf has a post up about NetBSD’s work to move to a different multiprocessing scheme, along with a 1:1 threading model.Â This is similar to what DragonFly is doing, though a different methodology.
Charles M. Hannum, one of the originators of the NetBSD project, posted what I’ll call a rant about the state of NetBSD; he wants NetBSD to lead system development and he blames the organizational layout for slowing development.
It appears he wants to return to the less complex organization of the early days of NetBSD; I don’t think that’s relevant in this stage of NetBSD’s development.Â Â (Is NetBSD the oldest existing open source operating system project?)
Daemonnews has an interview with Jan Schaumann up;
the interview is about NetBSD as a desktop system. Many of the answers also apply to DragonFly, as NetBSD and DragonFly both use pkgsrc.
NetBSD now has a wiki up as an experiment in making documentation easier, much like our own.
(Thanks, hubertf, who writes some good points about how (un)easy it is to create documentation…)