KernelTrap has a post up about the clustering file system that Matthew Dillon is designing.Â That’s not news to regular readers here, but there was an interesting comment on the story about an existing clustered filesystem called “Lustre“.
Month: February 2007
If you are running a DragonFly system older than version 1.6, and you are in North America using something other than UTC time, you will need to manually update your tzinfo files to reflect the changed (in 2005, taking effect this year) Daylight Savings Time start and stop dates.Â If you are on UTC or are running 1.6+, you are fine.
I didn’t know this, but it’s very simple to assign VLANs to your network interfaces in DragonFly.
YONETANI Tomokazu happens to know the secret to building multiple kernels at once.
This week on UnixReview.com: the Regular Expressions article “Tcl Scores High in RE Performance“, “Examining the Novell Certified Linux Engineer 10 Certification“, “Test Your Knowledge of HTML Topics” in Q&A format, a book review of “The Relational Database Dictionary“, and a very silly “Codysseus: A Geek Travesty by Erudil“.
Sascha Wildner has a version of DragonFly 1.8 compiled using NATA, the new ATA system, available onÂ leaf.dragonflybsd.org.Â (Link goes directly to a bzipped ISO)Â Try it if you’ve had trouble getting DragonFly to install on a system with a very new SATA controller.
Simon ‘corecode’ Schubert has committed changes from Kimura Fuyuki that should make it possible to build KDE with SSL support and also a native JDK. If you don’t want to wait, and you are running bleeding-edge code, it’s possible to add it without rebuilding world.Â There will probably be a .1 release to 1.8 that includes this.
Matthew Dillon has written an extensive description of the plan for the as-yet-unnamed Dragonfly clustering file system.
It looks like Matthew Dillon is going for his own filesystem to meet DragonFly’s clustering goals.Â According to his recent post, it will be a (deep breath) 64-bit fsckless logged filesystem with collapsible snapshots limited only by disk space, local caching, and logical-level multi-master replication.Â It should have a lasting effect. ETA: summer release, in some form.
Thomas E. Spanjaard has NATA, the ‘new ATA’ code from FreeBSD, in the DragonFly source tree.Â It’s in, but not yet enabled, in release 1.8.Â If you want to try it out, or if you have certain newer hardware that demands it, he’s written how a document on how to enable NATA, on the wiki.
OnLAMP/BSD has a new article up comparing a few firewalls.Â It only mentions “OpenBSD” as a software firewall, though what it’s really talking about is PF, which DragonFly also uses.
It wouldn’t be hard.Â There’s only two steps, neither of which are new, and it would be cool in a super-nerdy way to be able to save the state of an entire running virtual kernel.
Matthew Dillon has gone into some detail on his thoughts on what a clustering filesystem needs.
Sepherosa Ziehau, master of network drivers, has an update to test for the ipi(4)/ipw(4) driver.
Via waxy.org, a textfiles blog entry that describes the structure and events that happen to online communities.Â Some of it can be thought to apply to DragonFly or other BSDs.
Preview, the version of DragonFly inbetween released code and bleeding edge, has been slipped forward.
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.
UnixReview has several new articles up: “Sprints Important in Open-Source World“,
a certification article: “Examining the Novell Certified Linux Engineer 10 Certification“, and
a book review of “WarDriving and Wireless Pen Testing“
It’s not possible yet, but Matthew Dillon outlined the steps needed to get checkpointing and virtual kernels working together – you could start a kernel, and ‘freeze’ its state – even sending the resultant file to someone to restart and debug.
Jonathan Weeks noticed this thread about DragonFly’s 1.8 release on OSNews, with much ensuing discussion.Â (it’s somewhat partisan, so don’t put too much work into reading it.)