A Random Walk Down Tech Street

In an earlier post I discussed how to trace calls using GDB so that function calls and their arguments can easily be viewed.

In my previous post I went over two ways to mount a partition within a disk image file.

Last time I walked through creating a sparse disk image using dd and cp --sparse=always.

Recently I purchased a new laptop.

Sometimes it is easier to debug when you are able to view a call trace of all function calls in a particular program.

I often find myself in situations where I need to share information or files between a KVM host and KVM guest.

It is common practice among Linux users to exchange ssh keys between machines so that you can ssh between them without having to authenticate.

Part of the reason I use Logical Volumes for my block devices rather than standard partitions is because LVs are much more flexible when it comes to sizing/resizing.

When a linux computer is “hung” or “frozen” you can use a Magic SysRq key sequence to send various low level requests to the kernel in order to try to recover from or investigate the problem.

Traditionally with script you have really only been able to log the output of a simple “single session” terminal window.

A while back I set up mdadm to monitor my RAID array and send email alerts to notify me of failures.

Snapshot logical volumes are a great way to save the state of an LV (a special block device) at a particular point in time.

In my Desktop computer I use a software RAID1 to protect against a data loss due to a hard drive failure.

The other day I was trying to clean out some space on an almost full filesystem that I use to hold some video files.

I recently ran into an issue where I needed to demo a project without actually being present for the demo.

Hi Everyone!