On Tue, Aug 04, 2009 at 05:07:31AM -0700, Thomas C Gilliard wrote:
ie: The over-riding determining factor is that the copied to USB stick has to have equal or greater capacity than the copied from USB stick for the dd process to be sucessful.
Exactly.
* Do you have a suggestion on how to determine the actual size of a USB stick without seeing the error message if the dd command fails?On Debian you can install a tool called disktype that can print the size of a device:
sascha.si...@twin:~$ disktype /dev/disk/by-id/usb-CHIPSBNK_USB_2.0_260917004B813900-0\:0
--- /dev/disk/by-id/usb-CHIPSBNK_USB_2.0_260917004B813900-0:0 Block device, size 999.5 MiB (1048051712 bytes) [...] Alternatively you can check the kernel logs: sascha.si...@twin:~$ grep sectors /var/log/syslogAug 4 14:37:47 twin kernel: [202233.115200] sd 8:0:0:0: [sdc] 2046976 512-byte hardware sectors (1048 MB)
Depending on distribution and installed syslogger, the file you need to check might be called /var/log/syslog, /var/log/messages, /var/log/everything or similar.
CU Sascha -- http://sascha.silbe.org/ http://www.infra-silbe.de/
signature.asc
Description: Digital signature
_______________________________________________ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
