using the command
# dd if=/dev/hda of=/dev/hdc bs=2048k
The thing is I dont know if its working, dd gives no active feedback. I dont think i could even ^C it. I left it running for some >12hrs, hard reboot, jumped back to fdisk and a partition table was written of some sort (well there was a hdc1 now, just like how there was only hda1). It was fresh from the shop, so the disk was completely blank.
First time i tried, while dd was running I did a `fdisk -l /dev/hdc` and I was given constant hdc errors. So basically can I query the destination the disk and see...something?!
Further, is
# cat /dev/hda > /dev/hdc
slower than doing the above dd command? I've had cat running for around 22hrs now.
I have a little theory that running top may freeze the process, because since running top once, the dd or cat process cpu time has not changed.
-- Simon Males <[EMAIL PROTECTED]> No More AOL CDs Australia - www.anticd.org -- SLUG - Sydney Linux User's Group - http://slug.org.au/ More Info: http://lists.slug.org.au/listinfo/slug
