ConstantThought

I've recently been working extensively with disk image files (actually Compact Flash images, but that's not a useful differentiation). The first time I tried to mount one to work on, with a simple "mount -o loop hd.img /mnt", I was confronted with "mount: you must specify the filesystem type". Okay, then -- "mount -o loop hd.img /mnt -t ext2". Still no love. What gives? A couple of seconds of actually thinking about it gives the answer -- mount mounts partitions -- not disks.

The solution is straightforward enough, but somewhat burdensome. I'll present a shell script to make it easy.

Many have been the times when I wished the dd utility gave progress messages. It's annoying to be some unknown percentage through some gigantic operation. Somehow, despite the fact that I must have read the help a million times, I never noticed that there was a way to do this. Maybe you didn't either.

When building a pipeline for a shell script, you may come across an unpleasant situation: some program fails and returns a nonzero exit code, but one of the subsequent programs does not register an error and returns an exit code of zero.

If you find that dhclient (the common DHCP client for Linux) mysteriously fails -- check that the loopback interface is up. "ifconfig lo up".

To quote: The ext3 filesystem is a journaling extension to the standard ext2 filesystem on Linux.

What's interesting here is that it's basically just the unjournalled ext2 filesystem, but with journalling added on. Even with journalling, it's still ext2. That is, an ext3 filesystem is still an ext2 filesystem. For that matter, an ext2 filesystem is already basically an ext3 filesystem. The matter of how and where journalling actually comes in to play is really quite interesting.