Orange_Papers

I just used Clonezilla to transfer an installation of Debian Linux from a 16GB thumb drive to a 64GB drive (because I ran out of space). There were just a few hickups. Clonezilla is smart enough to fix the UUID in the file /etc/fstab, which is essential so that you will be able to boot the new installation, but it does not fix the swap space UUID. So you have to do that manually. Get the UUID with the command (as root, or else precede every one of the following commands with sudo. But sudo doesn't...

I just used Clonezilla to transfer an installation of Debian Linux from a 16GB thumb drive to a 64GB drive (because I ran out of space). There were just a few hickups. Clonezilla is smart enough to fix the UUID in the file /etc/fstab, which is essential so that you will be able to boot the new installation, but it does not fix the swap space UUID. So you have to do that manually. Get the UUID with the command (as root, or else precede every one of the following commands with sudo. But sudo doesn't...

I just used Clonezilla to transfer an installation of Debian Linux from a 16GB thumb drive to a 64GB drive (because I ran out of space). There were just a few hickups. Clonezilla is smart enough to fix the UUID in the file /etc/fstab, which is essential so that you will be able to boot the new installation, but it does not fix the swap space UUID. So you have to do that manually. Get the UUID with the command (as root, or else precede every one of the following commands with sudo. But sudo doesn't...

I just used Clonezilla to transfer an installation of Debian Linux from a 16GB thumb drive to a 64GB drive (because I ran out of space). There were just a few hickups. Clonezilla is smart enough to fix the UUID in the file /etc/fstab, which is essential so that you will be able to boot the new installation, but it does not fix the swap space UUID. So you have to do that manually. Get the UUID with the command (as root, or else precede every one of the following commands with sudo. But sudo doesn't...

I just used Clonezilla to transfer an installation of Debian Linux from a 16GB thumb drive to a 64GB drive (because I ran out of space). There were just a few hickups. Clonezilla is smart enough to fix the UUID in the file /etc/fstab, which is essential so that you will be able to boot the new installation, but it does not fix the swap space UUID. So you have to do that manually. Get the UUID with the command (as root, or else precede every one of the following commands with sudo. But sudo doesn't...

I just used Clonezilla to transfer an installation of Debian Linux from a 16GB thumb drive to a 64GB drive (because I ran out of space). There were just a few hickups. Clonezilla is smart enough to fix the UUID in the file /etc/fstab, which is essential so that you will be able to boot the new installation, but it does not fix the swap space UUID. So you have to do that manually. Get the UUID with the command (as root, or else precede every one of the following commands with sudo. But sudo doesn't...

I just used Clonezilla to transfer an installation of Debian Linux from a 16GB thumb drive to a 64GB drive (because I ran out of space). There were just a few hickups. Clonezilla is smart enough to fix the UUID in the file /etc/fstab, which is essential so that you will be able to boot the new installation, but it does not fix the swap space UUID. So you have to do that manually. Get the UUID with the command (as root, or else precede every one of the following commands with sudo. But sudo doesn't...

There is something wrong with the ISO image. I get that the file /vim/src/vim70src.gpk is bad -- it creates an Input/output error when I try to copy it. Which is very strange, since I have the ISO image mounted on Linux with a loopback mount. I didn't know that ISO images store their own sector checksums inside of the image. I thought that generating and checking the sector checksums was done by the drive controller circuitry. Whatever. I downloaded the ISO file a second time, assuming that it had...