Lazy Reading for 2012/09/23

The weather is finally turning cooler, which makes me happy.

  • I don’t think I’ve seen this before: Very old UNIX releases, listed for running in emulation.  (via)
  • Where the red-black tree name came from.  A red-black tree underpins Hammer 1’s data structures, though it does not in Hammer 2.  (also via)
  • Someone with a HP passport login want to help this guy?  He just needs to reinstall Windows in IDE mode, or perhaps find the right sysctl to toggle.
  • The acme editor, from Plan 9.  I didn’t realize it’s 20 years old.
  • Speaking of editors, Replace in Multiple Files with Vim.  I haven’t seen the argdo command before, or the Vim Ninjas site.  Their color schemes article is useful just for the screenshots. (via)
  • Adbuntu.  It’s not as bad or as inconsequential as most reactions would lead you to believe, but advertising within an OS seems heavy-handed.  The BSD model has been to use the operating system as a vehicle for selling hardware, and that’s been much more successful.  (see iOS, PC-BSD.)
  • Where Did the Internet Come From?
  • The map for Adventure.  (via)

Your unrelated link of the day: Victorian Sci-Fi.  It’s not just a reference list, it’s a link to a lot of the original material, since copyright no longer applies.

Lazy Reading for 2012/08/26

There’s certainly no theme to this week’s links.  I even manage to avoid my usual git and vim links, strangely.

Your unrelated comic link of the week: Cul De Sac.   The strip is ending due to the creator’s health issues, but what he has done is marvelous.  This is one of the few newspaper strips that is both visually interesting and often abruptly laugh out loud funny, without being patronizing.

Hammer 2 status report

Matthew Dillon recent posted a status report for Hammer 2.  Of interest is the spanning tree protocol being built to handle messages between Hammer volumes.  As he says in the message:

For example, we want to be able to have millions of diskless or cache-only clients be able to connect into a cluster and have it actually work…

(No, it doesn’t do this, yet.)

Deleting too fast

Here’s an interesting side effect that came up in Hammer 2 development: deleting files can potentially require modification of only one parent element.  If I’m reading it right, that means deletion always takes about the same time, independent of the amount of data being deleted.  Your ‘rm -rf /largedrive’ could complete, removing multiple terabytes of data before you realize it.  I suppose it’s silly to complain about speedy results.  Of course, being Hammer, it would still be available in history.

 

How much RAM is too little?

If you’re running DragonFly on a very low-end system, you may be wondering about memory requirements for Hammer.  Hammer is much less RAM-hungry than ZFS, so it looks like you can get away with 128M, as long as you don’t mind the occasional error message.  You can manually tweak settings for it if you like.  256M is plenty.

It still strikes me as odd to consider systems with less than 1G of RAM as “low-memory”.  What rich times we live in!