Tiny Core Linux
		Tiny Core Base => Raspberry Pi => Topic started by: Јаневски on December 24, 2016, 05:33:59 AM
		
			
			- 
				tc@box:~$ tce-load -i -w tcpdump
 tcpdump.tcz.dep OK
 libpcap.tcz.dep OK
 libusb.tcz.dep OK
 libudev.tcz.dep OK
 Downloading: gcc_libs.tcz
 Connecting to repo.tinycorelinux.net (89.22.99.37:80)
 wget: server returned error: HTTP/1.1 416 Requested Range Not Satisfiable
 gcc_libs.tcz: FAILED
 md5sum: WARNING: 1 of 1 computed checksums did NOT match
 Error on gcc_libs.tcz
 tc@box:~$ uname -a
 Linux box 4.4.20-piCore_v7+ #1 SMP Wed Sep 7 22:53:19 CEST 2016 armv7l GNU/Linux
 tc@box:~$ date
 Sat Dec 24 10:41:38 UTC 2016
 tc@box:~$
- 
				...
 tc@box:/mnt/mmcblk0p2/tce/optional$ wget http://89.22.99.37/8.x/armv7/tcz/gcc_libs.tcz
 Connecting to 89.22.99.37 (89.22.99.37:80)
 gcc_libs.tcz         100% |*************************************************************************************|  5412k  0:00:00 ETA
 tc@box:/mnt/mmcblk0p2/tce/optional$ tce-load -i -w tcpdump
 tcpdump.tcz.dep OK
 libpcap.tcz.dep OK
 libusb.tcz.dep OK
 libudev.tcz.dep OK
 Downloading: gcc_libs.tcz
 Connecting to repo.tinycorelinux.net (89.22.99.37:80)
 wget: server returned error: HTTP/1.1 416 Requested Range Not Satisfiable
 gcc_libs.tcz: FAILED
 md5sum: WARNING: 1 of 1 computed checksums did NOT match
 Error on gcc_libs.tcz
 ...
 tc@box:/mnt/mmcblk0p2/tce/optional$ rm -f /mnt/mmcblk0p2/tce/optional/gcc_libs.tcz
 tc@box:/mnt/mmcblk0p2/tce/optional$ tce-load -i -w tcpdump
 tcpdump.tcz.dep OK
 libpcap.tcz.dep OK
 libusb.tcz.dep OK
 libudev.tcz.dep OK
 Downloading: gcc_libs.tcz
 Connecting to repo.tinycorelinux.net (89.22.99.37:80)
 gcc_libs.tcz         100% |*************************************************************************************|  5412k  0:00:00 ETA
 gcc_libs.tcz: FAILED
 md5sum: WARNING: 1 of 1 computed checksums did NOT match
 Error on gcc_libs.tcz
 tc@box:/mnt/mmcblk0p2/tce/optional$
 ...
- 
				SUCCESS!
 But i wonder, why there would be MD5 discrepancy, something is fishy.  :o
 
 tc@box:/mnt/mmcblk0p2/tce/optional$ rm -f /mnt/mmcblk0p2/tce/optional/gcc_libs.tcz
 tc@box:/mnt/mmcblk0p2/tce/optional$ cat /mnt/mmcblk0p2/tce/optional/gcc_libs.tcz.md5.txt
 ea96b6e13036c47c38dd8e7a946fe53a  gcc_libs.tcz
 tc@box:/mnt/mmcblk0p2/tce/optional$ rm -f /mnt/mmcblk0p2/tce/optional/gcc_libs.tcz.md5.txt
 tc@box:/mnt/mmcblk0p2/tce/optional$ tce-load -i -w tcpdump
 tcpdump.tcz.dep OK
 libpcap.tcz.dep OK
 libusb.tcz.dep OK
 libudev.tcz.dep OK
 Downloading: gcc_libs.tcz
 Connecting to repo.tinycorelinux.net (89.22.99.37:80)
 gcc_libs.tcz         100% |*************************************************************************************|  5412k  0:00:00 ETA
 gcc_libs.tcz: OK
 Downloading: libudev.tcz
 Connecting to repo.tinycorelinux.net (89.22.99.37:80)
 libudev.tcz          100% |*************************************************************************************| 32768   0:00:00 ETA
 libudev.tcz: OK
 Downloading: libusb.tcz
 Connecting to repo.tinycorelinux.net (89.22.99.37:80)
 libusb.tcz           100% |*************************************************************************************| 40960   0:00:00 ETA
 libusb.tcz: OK
 Downloading: libpcap.tcz
 Connecting to repo.tinycorelinux.net (89.22.99.37:80)
 libpcap.tcz          100% |*************************************************************************************|   104k  0:00:00 ETA
 libpcap.tcz: OK
 Downloading: libcap-ng.tcz
 Connecting to repo.tinycorelinux.net (89.22.99.37:80)
 libcap-ng.tcz        100% |*************************************************************************************| 20480   0:00:00 ETA
 libcap-ng.tcz: OK
 Downloading: tcpdump.tcz
 Connecting to repo.tinycorelinux.net (89.22.99.37:80)
 tcpdump.tcz          100% |*************************************************************************************|   368k  0:00:00 ETA
 tcpdump.tcz: OK
 tc@box:/mnt/mmcblk0p2/tce/optional$ cat /mnt/mmcblk0p2/tce/optional/gcc_libs.tcz.md5.txt
 5eebce8d36d336e0b2868ad07157ac0d  gcc_libs.tcz
 tc@box:/mnt/mmcblk0p2/tce/optional$
- 
				That's the kind of thing that happens when the connection is interrupted/corrupted
			
- 
				Yep, md5 did it's job. :)