Hasso Tepper has added Objective C support for gcc 4.1.2.
Month: June 2008
Just because I don’t think I’ve mentioned it specifically yet: it will not be possible for Hammer to serve as a bootable volume in the 2.0 release.Â 2.2, definitely.
I’ve been traveling for a few days, so it’s time you break out the bullet points again in an effort to catch up.
Matthew Dillon posted a Hammer summary and warning on the 25th, along with another update today, mostly about mirroring and very large (terabyte!) files. Michael Neumann is also adding to Hammer functionality.
You know how I always post about roguelike games here? The ultimate form of the roguelike has been announced.
Dru Lavigne says “Grs!“.Â A bonus point to whomever figures out that reference…
Matthew Dillon’s posted another Hammer update, this one looking forward to pseudo file systems and mirroring, and perhaps a bit farther.
Here’s some BSD and Linux comparisons that happened to come up recently:
First, NetBSD is moving to a 2-clause BSD license. Hubert Feyrer has mention of this, along with a small graph contrasting the word count of the GPL vs. the BSD license used in NetBSD, over time.
KernelTrap has a post up about a position statement from the Linux Foundation that “urge[s] vendors to adopt a policy of supporting their customers on Linux with open-source kernel code.” Compare that to the OpenBSD position on binary blobs.
The @Play column at GameSetWatch has another article on roguelikes. This covers early roguelike software that has become lost; a strange concept in today’s world where everything is saved somewhere out there on the Internet. For an added bonus, the column has a link to a newspost from Moria’s original author, which includes this interesting quote:
I plan to download it and Angband and play them… Maybe something has been added that will surprise me! That would be nice… I never got to play Moria and be surprised…
Is that perhaps the worst part of game development? You always know how the story ends.
The June issue of the Open Source Business Resource is out, with Security being this month’s theme. There’s an article that covers a presentation on my favorite topic, “Building Technical Communities“. The Coverity Report is also interesting as it talks about the Coverity open source analysis and what the parts mean. And it has infoporn, in the form of graphs!
More conversations about Hammer capabilites has been going on, on the kernel@ mailing lists, including where Matthew Dillon describes where Hammer’s mirroring concept came from, and the possibilities of growing and shrinking filesystems. (Read to the end.) Also, he’s put up a preliminary paper describing Hammer – what it does, how to use it, and future plans. There’s a section on porting for those who might be interested.
KernelTrap’s still tracking progress, too.
(Apparently Hammer does not need to be in all caps as I’ve been writing it, going by the paper.)
Matthew Dillon’s latest HAMMER update warns of the usual need for a newfs, but says that the last change requiring this will go in today. Performance is on a par with UFS; this would be interesting for someone to benchmark and graph…
I have a number of links to dump:
Dru Lavigne has found that Verio is offering BSD hosting (specifically, FreeBSD). She’s also got her own recent linkpile which mentions this odd thing, plus a Federico Biancuzzi BSD interview I think I missed.
Also! There’s a June 13th HAMMER update From Matthew Dillon, just to continue the trend.Â Recompile and re-newfs, as usual.
“Building OpenSolaris Communities“, found on an OpenSolaris blog, is a generally excellent guide on how to build an open-source community. It’s based around OpenSolaris, which isn’t a surprise, but almost everything discussed applies equally well to DragonFly or other projects without a corporate source. (via… I lost track, sorry!)
Hasso Tepper recently completed a bulk build of pkgsrc on DragonFly 1.13. He’s posted the end result, and it’s looking much better than it did at the last quarterly release: 87% complete, and only 5% of the remaining amount were actual build failures – the rest were dependencies on those failed items.
Aggelos Economopoulos, who is working on making the network stack multiprocessor safe, has a page up on the DragonFly wiki describing his work. Normally I’d link to his recent conversations about this on the kernel@ mailing list, but he’s already done a nice job describing/linking it on the wiki.
Benchmarks would be good. I bring this up because Hubert Feyrer has a post about various NetBSD happenings, which includes some interesting benchmark work. It doesn’t include DragonFly, but it’s a good model from which to work. Notice the hint there? Was it too subtle?
Most of the benchmarking work these days seems to focus on multi-cpu scalability… I would like to just see comparative numbers, especially since there’s still plenty of single-cpu systems around.
Hasso Tepper, who has been submitting many pkgsrc changes lately, noticed a few non-trivial pkgsrc issues.Â He listed them out as available projects for anyone who wants to help out.
- Waxy.org has a complete version of the 5-part series, The Machine That Changed the World. This aired in 1992 and is both an excellent history of computing and also an interesting glimpse of the computing world before the World Wide Web steamrolled into the public eye. Part 1, part 2, part 3, part 4, and part 5 are available. If you don’t have a Flash-enabled browser to watch them, part 5 has a link to a torrent of H.264 MP4 files that contain the same complete broadcase.
- More old school nerditry: Dungeons & Dragons history, plus a rebuttal, all in far more depth than I thought possible.Â (Via)
- New school (rejectionist) nerditry: Ten ways to make an iPhone killer.
Undeadly.org has an interesting article about sticking to base applications. It’s all about making the programs that come in the base system install work instead of needing to install third-party packages to get a comfortable work environment.
It’s OpenBSD specific, but it is generally applicable to any system with a base set of included tools, which generally means all BSDs. The comments have some interesting parts, too, like using a source control system to synchronize dotfiles across multiple systems. (just having one consistent .vimrc would make me happy)
KernelTrap has a very nice summation of Constantine Murenin’s BSDCan 2008 talk about the OpenBSD sensors framework. This framework is in DragonFly now. It was also in and then out of FreeBSD; the KernelTrap article (in addition to describing how the actual code works) covers some of the conversation between Poul Henning-Kamp and Constantine Murenin at the BSDCan event about why that happened with FreeBSD.
Updated again: description changed, at Constantine’s request.
In my ongoing effort to stray farther off the beaten path than other nerdblogs, I bring you a link to this post at the Nonist: Objectified Circuitry.Â Think of it this way: the computer you are sitting at right now has probably at least a million of each circuit type pictured in that article.
For some end-of-the-work-week reading: Aggelos Economopoulos posted some of his thoughts on in_pcbs for his planned work on removing the Big Giant Lock from networking.
GameSetPlay has another @Play column, with comparisons of roguelike games to Dungeons and Dragons. If you find this interesting, you may be an old-school geek. Like me.
This week’s BSDTalk has an nearly half-hour interview, from BSDCan 2008, with 7 different members of the FreeBSD Core Team.
I think I already read about this, but it didn’t really sink in until I read this commit message: HAMMER will allow multiple physical devices to be mounted as a single volume.Â Wait!Â That’s in the wrong tense: it’s possible now.
Robert Luciani (yes, they’re related) recently finished a school project evaluating threading on DragonFly; his poster and paper (PDF) are available. Appropriately,he’s working on multiprocessing support.
(typos fixed – thanks, smtms on EFNet #dragonflybsd)
Among other HAMMER work, Matthew Dillon has added a “softprune” option. With this option, historical versions of a HAMMER filesystem can be tracked by maintaining a list of soft links. There’s some sort of joke about ‘regularity’ to make here.