G4U and G4L don't
require an FTP server, that is just one way to use them (and probably the most efficient). They can also make local images.
That said, both G4L and G4U are simply wrappers for "dd" itself. So your results when using one of those is going to be the same as if you just used dd. Neither product guarantees that you will be able to use your images on anything other than an identical disk.
If you want to be positive that you can use the backup on any disk, then the best thing to do is just tar and compress the entire file system itself, rather than actually making an image of it. Something like:
Code:
mount -t msdos /dev/hda2 /mnt/dos
tar cvf /tmp/dosbackup.tar /mnt/dos/*
gzip -c 9 /tmp/dosbackup.tar > /tmp/dosbackup.tar.gz
Then it is just a matter of expanding that archive onto the destination disk if you needed to restore it. With this method, the physical properties of the volume you are restoring to are inconsequential, since the backup never even took them into account.
You could even use dd to backup the MBR and insert that into the compressed image as a regular file.
Code:
dd if=/dev/hda of=/tmp/mbr.bak bs=512 count=1
Alternately, you could make an image of the single partition itself rather than the entire disk. For that I would suggest
Partimage. With this, you are only making images of specific partitions, so the only thing that matters is the partition size itself. There is no difference between a 2 GB partition on a 20 GB drive or a 120 GB drive, the partition size is still going to be the same. It sounds like this might actually work well for what you are trying to do.
Do note that Partimage (to my knowledge) does not have the capability of backing up MBRs since it is not in the business of full drive backups. To backup the MBR you could use the dd line I gave above, and then restore the MBR from the live CD containing Partimage before rebooting.