It is possible that the original file has holes, and the cp expanded the holes. Thus the md5sum computed different checksums. Maybe this is the reason?
Note that holes can be created by write(...), lseek(...), write(...). Pablo Manalastas *** --- On Mon, 6/1/09, Edel SM <[email protected]> wrote: > From: Edel SM <[email protected]> > Subject: [plug] md5sum > To: "Philippine Linux Users' Group (PLUG) Technical Discussion List" > <[email protected]> > Date: Monday, June 1, 2009, 5:32 AM > ano kaya prob nito? > > r...@gw:~# cp appVM-cos5x.tar.7z /data/ && md5sum > `pwd`/appVM-cos5x.tar.7z /data/appVM-cos5x.tar.7z > d02e4f177a6c634496a7cb8a7c5c85bb > /root/appVM-cos5x.tar.7z > f54fd2f63d6561678ac7e76353c9bb33 > /data/appVM-cos5x.tar.7z > r...@gw:~# > > i always end up two different files. could it be because i > have a > slower processor (pentium4 2.4ghz)? or my memory module is > faulty? > > i havent done doing a mem check yet. > > thanks. > > -- > edel _________________________________________________ Philippine Linux Users' Group (PLUG) Mailing List http://lists.linux.org.ph/mailman/listinfo/plug Searchable Archives: http://archives.free.net.ph
