If you’re in New York City or the UK, there’s two new DragonFly mirrors for your downloading pleasure. Check the mirrors page for details.
Matthew Dillon’s CPU bug hunt has scattered its way across various news sites, some more accurate than others. He’s posted a followup that is probably a more valuable read than any of the news reports.
A few days ago, I posted about Python 2.4 and Python 2.5 leaving pkgsrc – it looks like it’ll be a little bit longer, at least for the 2.5 version. This means the Zope packages will be gone too, since they depend on Python 2.4. This won’t affect you if you aren’t using these packages, of course.
If you said “Yes!”, you’re in luck. Markus Pfeiffer got ghc to compile on DragonFly, and his fixes (for DragonFly at least) to enable it are already committed.
The default version of Python in pkgsrc is going to become 2.7. This will mean the 2012Q1 release will use that version by default. Older versions, meaning Python 2.4 and 2.5, may be going away. At least, that’s how the linked thread started but I’m not totally sure about it as I read farther through.
Take a look at the schedule if you’ve been thinking about going… (seen via multiple places) This is as good a time as any to point out, once again, the very valuable BSD Events Twitter feed.
That’s exactly what Michael Lucas talks about in this recent post; using ssh to browse from a different machine, but using a local web browser. He uses it to get around a network problem, but I imagine there’s a number of other applications. This is one of the valuable tips from his recent book.
See the release page for details. This release took longer than normal because of a crazy bug hunt, but the payoff is that this version performs better than ever.
Note: The x86_64 GUI ISO image had a problem due to file size (over 2G); redownload if you’ve had trouble booting it.
I was reading an article about how Tumblr scaled to handle the huge amount of data it’s regularly pushing out. Apparently, it started life as a traditional LAMP stack, but they’ve since moved on – to software packages I have not yet needed to ever use. Being open source software, it all has crazy names. Some of these packages are perfectly familiar to me now, but others are completely new.
Anyway, for fun, I decided to see how many of these sometimes new-to-me packages were present in pkgsrc. I’ll reproduce a paragraph from the story that lists the software they use, and link each one that I found in pkgsrc.
- Apache
- PHP, Scala, Ruby
- Redis, HBase, MySQL
- Varnish, HA-Proxy, nginx,
- Memcache, Gearman, Kafka, Kestrel, Finagle
- Thrift, HTTP
- Func
- Git, Capistrano, Puppet, Jenkins
That’s actually more than I thought I’d find, though I can’t articulate why. Anyway, if any of the names are unfamiliar to you, now is the time to follow up. Redis, for example, looks more interesting to me at a casual glance than the normal NoSQL models I’ve heard about.
The “Institut de Recherche et Coordination Acoustique/Musique” is mirroring DragonFly – it’s on the mirrors page or you can just go right to it if a French mirror is useful to you.
I’m planning to tag the 3.0.1 release of DragonFly this weekend. There’s still a few bugs, so if you are able to help, please do. Otherwise, they will be errata.
Michael Lucas installed WHMCS, a commerical hosting management tool, on FreeBSD. He tells a story of doing so, and in the process happened to list all the PHP modules needed for it to run. I’m linking it because that list is going to come in useful for someone, someday.
If you’ve noticed the main dragonflybsd.org website being down, that’s because both network connections (on different networks!) serving it are down. This makes the website unavailable, and the source code, but you can still pull down images, packages, and the like from avalon.dragonflybsd.org. Hopefully this warning will be out of date soon.
Note: It’s back.
Hey, it’s snowing here! Finally.
- I remember when fractal zooming would bring a desktop computer to its knees. Now, you can do it in a web browser. (via) This exists as a standalone application (x11/XaoS) too.
- I see content from here get splogged, from time to time, and I think that’s what’s happening here. Someone throws “BSD” into a content generator, with ads slapped on top of it? Honestly, I’m not sure what it is. (via)
- Hammer 2 work is starting, as noted earlier this week. Let’s see some details on a similar filesystem project, btrfs. (via)
- You should quit Facebook because privacy etc. you’ve heard it from me before. The arguments are getting more thorough, though.
- Here’s an article from independent game developer Jeff Vogel about serving a niche with your independent work. I like his writing, plus if you squint your eyes and sorta look at that article’s point sideways, you could construe it as relevant for BSD.
- For fun, spot the two things I mention/link to here frequently, in this somewhat hypey article about Tumblr. (via)
- An Economist article about shifting from computer to computer. I read that and realized the one computer constant for me isn’t my desktop – it’s “~”.
- If you ever played games on the Amiga, you may want to watch this movie. It’s clips from a lot of Amiga games. By a lot, I mean an hour and a half of footage total. There were some really advanced games for the time there. (via)
Your unrelated comic link of the week: Shut Up About Cats. The rest of that site’s good too.
Also! On a related link, Venkatesh Srinivas, one of the DragonFly developers, is participating in a bike ride to raise cash for the Ulman Cancer Fund. If you’d like to pledge some money, he’ll feel better as he cycles a ridiculous 4,000 miles across the US.
There’s 7 bug reports to close before releasing DragonFly 3.0. Most of them have dumps to go with them, so each one should be solvable. Please take a look if you have the time and inclination,
There’s a Hammer 2 branch in the DragonFly git repo now, for the next generation of DragonFly’s native file system. Don’t get too excited; as Matthew Dillon explains, it won’t be operational for months, and features won’t get added until much later this year. It’s neat to see the work happening, though, and there’s a new design document to show what’s coming.
If you were thinking about implementing DNSSEC, Michael Lucas did it himself and wrote down his notes. You can read them and either follow along to implement it yourself, or just spectate. The one disadvantage is that it uses BIND 9.9, and I only see 9.8 and 10 in pkgsrc.
I’ve reviewed Michael Lucas’s book here before, so when he offered a chance to read his newest, SSH Mastery, I jumped at the chance. Michael Lucas has published a number of technical books through No Starch Press, and started wondering out loud about self-publishing. This is, I think, his first self-published technical volume.
It’s a very straightforward book. The introduction opens with a promise not to waste space showing how to compile OpenSSH in text. Chapter 2 ends with the sentence, “Now that you understand how SSH encryption works, leave the encryption settings alone.” This stripping-down of the usual tech-book explanations gives it the immediacy of extended documentation on the Internet. Not the multipage how-to articles used as vehicles for advertising, but an in-depth presentation from someone who used OpenSSH to do a number of things, and paid attention while doing it.
It’s a fun read, and there’s a good chance it covers an aspect of SSH that you didn’t know. In my case, it’s the ability to attach a command to a public key used for login. It even covers complex-but-oh-so-useful VPN setups via SSH.
If you’re looking for philosophical reasons to buy it, how about the lack of DRM?
The physical version is not available yet, but the electronic version is available at Amazon (Kindle), Barnes & Noble (Nook), or from Smashwords (every other format ever, including .txt). The Smashwords variety of formats means that you’ll be able to read it on your phone, one way or another; I’d like to see more books that way in the future.
Deb Goodkin of the FreeBSD Foundation gets 24 minutes of interview on BSDTalk.
Ulrich Habel wants to update some of the Perl 5 modules in pkgsrc. He published a request for comments, describing what he plans to do for changing some dependencies. He does note that Perl 5 in pkgsrc is at 5.14.2, which is very recent.
I was talking to a relative today who works at a large financial company, which is standardizing on Red Hat Enterprise. I find it strange that Red Hat, which has a lot of money behind it, still ships a years-old and arguably broken version of perl. By using pkgsrc, you’re getting more up-to-date software than people that actually shell out money for the privilege of compiling software.