Lazy Reading for 2011/05/15

This week: lots more reading!

  • Michael Lucas describes an extra layer of protection for when you can’t force public key usage on every SSH user.
  • Cool, but obscure Unix tools (via)  The screenshots are all from a Mac… How many of the 24 tools listed are in pkgsrc/pkgsrc-wip?   Almost all of them.  (tpp sounds entertaining.)
  • NYCBUG, in addition to having a really fun convention, has been regularly posting audio of the presentations they host.  The most recent is “William Baxter’s NYCBUG presentation on The Unix Method of Development Management”.   See the BSD Events tweet for the download.
  • What Ubuntu means.  (via)
  • Here’s a nice explanation of Intel’s new Tri-Gate design and with it, an incidental explanation of the processor market.
  • This ycombinator post about Hammer2 work has an in-depth comment from Venkatesh Srinivas about DragonFly’s network setup, memory allocator, and token use.  (Ignore the trolling in other comments.)
  • Michael Lucas’s next No Starch Press book is Absolute OpenBSD, second edition.
  • Pictures and video are starting to show up from the just-passed BSDCan 2011. (via this and also thesjg on EFNet #dragonflybsd)
  • My first experience of The Internet was very similar to this.  It should be bizarrely unfamiliar to anyone under 20 or so.  (via)  Get this: I typed ‘exit’ instead of just closing the browser window when I was done messing with it, because some habits cannot be broken.
Really old systems and libpthread

If you have a really old DragonFly system, meaning you’ve been upgrading it since version… 1.8 (I think?), you may have libpthread linked to libc_r instead of libxu.  This means that if you have a system that old, you will now need to set THREAD_LIB or just recompile your pkgsrc programs on your next upgrade to something after DragonFly 2.10.   I don’t think this is going to apply to a lot of people.

(I hope I got the lib details right…)

Hammer and the future

Matthew Dillon’s been thinking about Hammer, and how to implement clustering well enough to work as a sort of RAID replacement.  He’s written up a document describing his plans.  Some highlights:

  • writable history snapshots
  • quotas and accounting
  • live rebuilds of data from mirrors
  • and the same history, mirroring, and snapshots as before.

It’s going to be a while before this “Hammer 2” becomes a finished product, though, so don’t count on it for the next release.

A start on TRIM support

Tim Bisson has inital TRIM support working for UFS.  His lengthy posting talks about how it’s done, and shows how much it speeds things up.  He’s looking for testers, so please try it if you have a SSD.  (The usual warnings apply about testing code that specifically deletes things.)

For those not familiar with TRIM in SSD context, here’s the least annoying page with an explanation that I could find in a few seconds of Googling.