Previously I was running KDE 4.3.3 on top of Fedora 11 (for the first experiment) and KDE 4.6.5 on top of Gentoo (for the second experiment).
Check out my profile for more information.
It is a pretty common practice to use the command dd to make backup images of drives and partitions. It’s as simple as the command:
dd if=[input] of=[output]
A while back I did just that and made a dd backup of not just a partition but of an entire hard drive. This was very simple (I just used if=/dev/sda instead of something like if=/dev/sda2). The problem came when I tried to mount this image. With a partition image you can just use the mount command like normal, i.e. something like this:
sudo mount -o loop -t [filesystem] [path to image file] [path to mount point]
Unfortunately this doesn’t make any sense when mounting an image of an entire hard drive. What if the drive had multiple partitions? What exactly would it be mounting to the mount point? After some searching I found a series of forum posts that dealt with just this scenario. Here are the steps required to mount your whole drive image:
1) Use the fdisk command to list the drive image’s partition table:
fdisk -ul [path to image file]
This should print out a lot of useful information. For example you’ll get something like this:
foo@bar:~$ fdisk -ul imagefile.img You must set cylinders. You can do this from the extra functions menu. Disk imagefile.img: 0 MB, 0 bytes 32 heads, 63 sectors/track, 0 cylinders, total 0 sectors Units = sectors of 1 * 512 = 512 bytes Disk identifier: 0x07443446 Device Boot Start End Blocks Id System imagefile.img1 * 63 499967 249952+ 83 Linux imagefile.img2 499968 997919 248976 83 Linux
2) Take a look in what that command prints out for the sector size (512 bytes in the above example) and the start # for the partition you want to mount (let’s say 63 in the above example).
3) Use a slightly modified version of the mount command (with an offset) to mount your partition.
mount -o loop, offset=[offset value] [path to image file] [path to mount point]
Using the example above I would set my offset value to be sector size * offset, so 512*63 = 32256. The command would look something like this:
mount -o loop, offset=32256 image.dd /mnt/point
That’s it. You should now have that partition from the dd backup image mounted to the mount point.
I recently re-built an older PC from a laundry list of Frankenstein parts. However before installing anything to the hard drive I found I wanted to check it for physical errors and problems as I couldn’t remember why I wasn’t using this particular drive in any of my other systems.
From an Ubuntu 12.04 live CD I used GParted to to delete the old partition on the drive. This let me start from a clean slate. After the drive had absolutely nothing on it I went searching for an easy way to test the drive for errors. I stumbled across this excellent article and began using badblocks to scan the drive. Basically what this program does is write to every spot on the drive and then read it back to ensure that it still holds the data that was just written.
Here is the command I used. NOTE: This command is destructive and will damage the data on the hard drive. DO NOT use this if you want to keep the data that is already on the drive. Please see the above linked article for more information.
badblocks -b 4096 -p 4 -c 16384 -w -s /dev/sda
What does it all mean?
A new episode of the Listener Feedback podcast has been released. This episode features the Internet nerdcore gangster rap super group Futuristic Sex Robotz with their album Hotel Coral Essex. Download it here.
I have been running Sabayon Linux (Xfce) for the past couple of months and figured I would throw a post up on here describing my experience with it.
Reasons for Running
The reason I tried Sabayon in the first place is because I was curious what it would be like to run a rolling release distribution (that is a distribution that you install once and just updates forever with no need to re-install). After doing some research I discovered a number of possible candidates but quick narrowed it down based on the following reasons:
Experience running Sabayon
Sabayon seems to take a change-little approach to packaging applications and the desktop environment. What do I mean by this? Simply that if you install the GNOME, KDE or Xfce versions you will get them how the developers intended – there are very few after-market modifications done by the Sabayon team. That’s not necessarily a bad thing however, because as updates are made upstream you will receive them very quickly thereafter.
This distribution does live up to its promise with the codecs and drivers. My normally troublesome hardware has given me absolutely zero issues running Sabayon which has been a very nice change compared to some other, more popular distributions (*cough* Linux Mint *cough*). My only problem with Sabayon stems from Entropy (their application installer) being very slow compared to some other such implementations (apt, yum, etc). This is especially apparent during the weekly system wide updates which can result in many, many package updates.
For anyone looking for a down to basics, Ubuntu-like (in terms of ease of install and use), rolling release distribution I would highly recommend Sabayon. For someone looking for something a bit more polished or extremely user friendly, perhaps you should look elsewhere. That’s not to say that Sabayon is hard to use, just that other distributions might specialize in user friendliness.