Tip 1: You can’t have too big a volume for Hammer.
Tip 2: Snapshots are the easiest way to track historical data.
A running description of activity related to DragonFly BSD.
Tip 1: You can’t have too big a volume for Hammer.
Tip 2: Snapshots are the easiest way to track historical data.
Pulled from previous comments: there’s a Last.FM DragonFly group.
I’ve completed a full build of binary pkgsrc packages. However, bandwidth to dragonflybsd.org is getting hit pretty hard right now, so please, be patient and use a mirror if possible. (once they update…)
The DragonFly 2.0 release announcement is popping up in various places around the web: DistroWatch, Unix.com, LinuxQuestions.org, and of course KernelTrap.
I’ve created a DragonFly BSD group at LinkedIn, a business networking site. If you’re already using it, search for that group name and add yourself – I’ll get the request and approve it. There’s no major purpose, other than getting a group formed. It is a good place to find potential job candidates…
Read and go! Please use a mirror if possible. If you’re feeling torrentish, Christian Sturm has a BitTorrent link.
BSDTalk 155 is a short 7 minute interview with Martin Tournoij from DaemonForums.org.
Do you run a mirror? Make sure you’re downloading the 2.0 release ISO. The release won’t officially happen until there’s enough ISOs floating around for people to actually reach it.
Matthew Dillon made some last-minute changes to Hammer mirroring;Â it’s made the options a lot simpler.
If you want to commit something for 2.0, do it now!
If you are so inclined, test 2.0 building with a ‘cd /usr/src/nrelease; make installer release‘
More links for fun:
Matthew Dillon posted a July 16th Hammer update where he details causing a lot of write activity on a USB-connected, Hammer-formatted hard drive, and then yanking the USB connector out. Apparently, doing that 50 times over didn’t even faze Hammer. (Of course, be careful trying that with power.) He’s been committing a lot for Hammer, along with Sascha Wildner and Thoman Nikolajsen. A side benefit is that the Hammer work has exposed some issues in CAM.
Bonus link: Matthew Dillon talks about ‘purposeful destabilization‘, and man pages for hammer(8) and mount_hammer(8) are now available online.
It’s been 5 years since Matthew Dillon announced DragonFly. Happy 5th birthday, us!
2.0 is going to be released on the 20th. If you’re committing, make sure to put it both in the 2.0 and 2.1 branches, please. And get it in quickly! If you’ve contributed changes to this release, please get them listed in the 2.0 release document that Matthias Schmidt has been conscientiously updating.
Sometimes BSD references show up in wierd places. (marginally NSFW) (Via)
The 2.0 release of DragonFly will be on the 20th of this month. I’ll be working on a new set of pkgsrc packages to match.
Matthew Dillon posted a note about a last-minute bug in Hammer – make sure you sync before unmounting. It will only lose about 30 seconds of data at worst. He should have it fixed today, with the 2.0 branching tonight.
Matthew Dillon’s posted another one of his Hammer updates: mirroring is done, and there’s a few outstanding issues he lists.
There’s been a lot of linkworthy things lately, which I will list here in an effort to catch up:
I know I just posted something like this, but Dru Lavigne’s got another link collection. The story about dsw is a gem.