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!

Lazy Reading for 2011/10/09

Getting close to 2.12 release…

Lazy Reading for 2011/10/02

Yep, fall hits and it’s easier to find links.

Your unrelated link of the week: Scientific Illustration.  Not a comic, but still visually interesting.

Lazy Reading for 2011/09/04

It’s almost the end of summer here, or at least the traditional end of summer in North America.  About time, too!  I don’t like the heat.  Anyway, as people trickle back to school, some more interesting doodads should show up for these weekly Lazy Reading posts…

Your unrelated comic link of the week: Jack Kirby art on what would have been his 94th birthday.  I have trouble communicating how dramatic and influential his art has been.

Lazy Reading for 2011/07/24

Lazy reading is easy when it’s been this hot out.  In fact, I may melt before this article gets published.

  • Ecdysis – a NAT64 gateway program.  I link to it for two reasons.  1: You will probably need to NAT 6-to-4 sooner or later, and 2: it uses PF and so is BSD-compatible. (via)
  • Don’t not copy that floppy! (also via)  My original Apple ][ disk for Castle Wolfenstein is probably no longer functional.  Not that I have equipment to play it on…
  • World timezones, as a visible map.  (via)   I mention time zone updates here on occasion, and this is a immediate guide to what a strange patchwork of zones it is.  You can’t even see some of the really tiny/crazy ones.
  • A crappy way to start your day.  Nobody ever enjoys that call from work…

And now, a link that has nothing to do with this.

Practical Packet Analysis: a review

Background: You may remember some time ago, I posted a review of Michael Lucas’s Network Flow Analysis.  He’s written several BSD books and so I figured it was worth reading further, knowing that this network-specific book would be BSD-friendly.  Also, he made it easier by sending me a copy.

No Starch Press, the company that published all the books linked in the previous paragraph, asked if I’d read/review another book from them. This would be Practical Packet Analysis, 2nd edition.  (Review continues after the break…)

Continue reading “Practical Packet Analysis: a review”

Lazy Reading

You can probably infer the new (to me) blog I found this week from some of the links…

  • Adding IPv6 to a FreeBSD Mail/Web Server – from Michael Lucas, repeat BSD author.  I link to this because we’re all going to have to do something similar in the next year or so, I bet..
  • A visual guide to TMUX, part 1 and part 2.  tmux has usually been introduced to me as “It’s BSD-licensed and not screen”, which is good, but not compelling on its own.  The first of the articles linked here goes over the comparative differences in some detail.  (via)
  • Speaking of screen-ish things, do you leave an irssi session running in screen so that you can rejoin IRC conversations at any time?  I sure do.  Sometimes I even reconnect through ConnectBot on my Android phone.  There’s now a Connectbot variation for irssi, just for people who do such a thing.  Don’t forget: #dragonflybsd on EFNet.
  • Also still on the topic: forgetting to use screen and then being stuck with a long-running process is lousy.  There’s ways to deal with it, though.  (via, from a blogroll link)
  • Hey, it’s neat to see a new business built on BSD – OpenBSD, in this case: Tunnelr.  (via)
  • We’re still doing great in terms of pkgsrc packages building successfully on DragonFly.
  • An hour+ recording of the recent NYCBUG meeting about BSD networking is online.  (Link is to a MP3 – via)
  • How not to comment code.
  • AT&T -> BSD -> AT&T.