Normally I hold this for Sunday, but I’ve got a good batch of links already. Something here for everyone, this week.
- A git cheatsheet, and another git cheatsheet. I may have linked to the latter one before, as it looks vaguely familiar. Anyway, bookmark. (Thanks, luxh on EFNet #dragonflybsd)
- What should you do about bad blocks on a disk? Get a new disk.
- If you ever wanted to port software, there’s a pkgsrc developer’s guide (thanks Francois Tigeot) that shows you how.
- It’s NOT LINUX, for the billionth time. It’s BSD UNIX (certified, even) under there!
- “Children of the Cron“. An entertaining pun. (via)
- Nothing to do with BSD, or even computers, really: Gary Gorton, interviewed about the recent financial crisis, at a Fed bank website (!?). Interesting because I like economic matters, and because it’s the first web page where I’ve ever seen pop-up links added usefully, as a sort of footnote that you don’t have to scroll. (via)
- Michael Lucas recently had a machine broken into. Since everything on the machine is suspect, he’s using Netflow data to figure out when it happened, and how, which is not surprising given his most recent book. He has two posts describing how he backtracks his way to the probable source.
I never really noticed this before, but it’s possible to include your own patchsets into pkgsrc and have them picked up as part of the build process, using $LOCALPATCHES.
If you were dying to have less behave like more, it’s possible to do so with these tips from Oliver Fromme. I don’t know if it’s that desirable, but it’s an interesting thing.
Somehow I ended up with a zillion links for this week’s Lazy Reading. I hope you’ve got some spare time for this… Let’s get right into it:
- Michael Lucas, BSD book author (see links on site), has started Twittering. He’s also found the Wikileaks/NetBSD association that I didn’t know about, as Julian Assange even shows up in the NetBSD fortunes file. Also, while linking to his blog, I’ll point at his post on “Write what you don’t know“. Think of that article next time you feel you don’t know enough to contribute to something – especially open source.
- There’s a lengthy dialog on the firstname.lastname@example.org mailing list about pkgsrc, and “Making it easier to get and use pkgsrc“. You can follow the whole thread on the listing page. I am all for the idea. Everybody and their brother has an App Store these days. Ports/pkgsrc are perhaps the original app store ideas, and I’d like to see them brought to the same level as these commercial entitites. This is important: pkgsrc is perhaps the only app store equivalent in existence that is not tied to a platform; that exists only to get you software rather than to provide a way to tie a platform into its developers profits.
- Hey, a roguelike zombie apocalypse game! Aw, it’s Windows-only.
- Mikel King has an editorial that sums up the many places BSD serves as an underpinning to products – a good checklist, if you don’t know of them. He’s also written an instructional article on passwordless/SSH setup.
- Along the same lines, Promote Perl by Building Great Things. This applies to BSD products too; telling people it’s great doesn’t work as well as making something great and showing that a BSD system is part of what makes it so.
- Did you know there are even BSD Certification classes in Iran? I really need to do that… though probably not at that location.
- Yacc is not dead. (via) I link to this because I had a moment of nerd excitement realizing that blog’s title is intended to look like a bang path.
- Database design ideas. There’s been a good series of posts there lately, good for anyone wanting to move beyond the basic CRUD details.
I was reading this Perl Advent Calendar (that would be good for DragonFly, come to think of it) post about ack, and came across a interesting line:
curl http://betterthangrep.com/ack-standalone > ~/bin/ack && chmod 0755 !#:3'
fetch’ would work just as well on a BSD system. The interesting thing is that it’s a one-liner for installing software that doesn’t make any assumptions about having an existing framework like pkgsrc or aptitude or anything like that – it just grabs the code and plops it in place. It wouldn’t work for more complex software, but the simplicity is intriguing, to match the Unix-like single, chainable program idea.
For those who haven’t seen it, ‘ack‘ is a grep replacement that automatically takes care of common activities around searching – skipping files that would cause duplicate matches, binary files, etc., handles a larger range of regular expressions, and runs startlingly fast.
Siju George noticed that his mouse would stop working in X, perhaps every hour. Restarting X would fix it, but he didn’t have a clear cause. Antonio Huete Jimenez suggested turning the sysctl ‘debug.psm.loglevel’ to 9 to at least see what messages cropped up, and that seemed to fix it. I don’t think it’s a good long-term solution, but it’s worth mentioning in case this odd bug bites someone else.
Naoya Sugioka had trouble booting DragonFly on his Dell M4400. He updated ACPICA with this patch, and was able to boot. I link to it in case someone else with a recent Dell model (or perhaps just a laptop with the same chipset?) has the same issues.
A number of people have encountered this: while installing some larger pkgsrc package, the process stops on a strange DocBook error. Alex Hornung has a fix: symlink /usr/pkg/etc/xml/catalog to /usr/pkg/share/xml/catalog.
Alex Hornung is having trouble getting his power consumption as low as it could be on his DragonFly laptop. A side effect of this problem is that when he posts about it, he also manages to enumerate all the various ways you can reduce power consumption and heat usage on a laptop. (Follow the thread for more.)
If your system has trouble when APIC_IO is enabled, and you’re tracking DragonFly 2.9, you may have trouble on your next build. The fix is putting this in your loader.conf:
I know this has already been covered, to some extent, but one can never be too clear with solutions.
YONETANI Tomokazu wrote out a nice explanation of acpi(4) and the myriad ACPI subsystems which can be enabled or disabled at boot time. If you do have booting problems, it’s usually ACPI, and it’s usually only one small part. Finding that small part is easier with this list.
Something that always got with with Linux binary support was that I couldn’t get the Linux /proc filesystem to automatically mount on boot. I’d end up doing it by hand later, right after I tried to start a Linux binary and had all sorts of issues. Pierre Abbat had this same problem, and Sascha Wildner has the answer: “
linux_load=yes” in /boot/loader.conf.
When compiling software on DragonFly but outside of pkgsrc, and you have trouble with configure, remember you can always manually pull down new versions. You’re welcome, future me.
I’m linking to this commit message from Matthias Schmidt simply because it has the correct invocation for installing a vkernel, and I know this will come in handy, someday.
There’s a whole lot of options for bmake, used in pkgsrc, and they aren’t immediately obvious. I’ve linked to a reference before, but it’s no longer at that location. However, I found a new link!
Link dumps just so I can get caught up.
Using ‘serno’, meaning specifying disks by serial number rather than path, is a good idea. If you have a machine that started out as an older DragonFly installation, it may be a good idea to use this feature.
I apologize; I’ve been missing. Here’s some misc links while I get back in gear:
- A very good reason to be interested in Hammer over ZFS: nobody will threaten lawsuits over Hammer.
- 10 tricks for admins. I’m posting it cause I can never remember that thing with tunneling ssh out. (via)
- This Gaming Life, as a free download. An excellent book that is in physical form on my shelf right now. Yes, unrelated.
Sometimes, packages are renamed in pkgsrc, usually because of a version change. If that happens, it can be hard to find the replacement. You can manually add them, or there’s a trick to make the build ‘jump’ to the new name.