Mailing List ArchiveSupport open source code!
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]tlug: Xcdroast verification failure
- To: "Tokyo Linux Abusers' Group" <tlug@example.com>
- Subject: tlug: Xcdroast verification failure
- From: "Stephen J. Turnbull" <turnbull@example.com>
- Date: Tue, 5 Oct 1999 13:51:18 +0900 (JST)
- Content-Transfer-Encoding: 7bit
- Content-Type: text/plain; charset=us-ascii
- In-Reply-To: <Pine.LNX.4.10.9910051212411.749-100000@example.com>
- References: <Pine.LNX.4.10.9910051212411.749-100000@example.com>
- Reply-To: tlug@example.com
- Sender: owner-tlug@example.com
>>>>> "Dennis" == Dennis McMurchy <denismcm@example.com> writes: Dennis> My question is: why does this happen Probably because the data in the image file on the hard drive does not match the data written to the CD-ROM. You should be able to use `dd' to make file copies of the differing blocks, then use hexl mode of [X]Emacs to look at the data. If the CD-R is actually written incorrectly, there must be a utility to find out which file owns a given block. Depending on the file you may not care about the error. You can also mount the image file somewhere (directly, if it's a partition, or by loopback, if it's a file) and do "diff -ru /image /cdrom 2>&1 >/tmp/cdrom.diff". This will take a long time, but it will identify any differing files, and you will be able to recognize binary ones because it will simply tell you the files differ, whereas text files will give you the familiar patch-like output. Possible causes of the hardware error are out-of-spec media or hardware, dirty lenses in the drive, the cat jumped on your box, random interference from JASRAC, bad luck, and the new Obuchi-naikaku. You may get better results if you burn at a lower multiple of standard CD-ROM rates. Dennis> (of course, it's only with certain disks), Do mean you've recopied a given disk and gotten an error in the same place or for the same disk, or just that it only happens occasionally? Dennis> and is it something that I should worry about, i.e. that Dennis> could compromise the completeness of the data on the disk? Oh, the data is pretty surely compromised. You need to figure out how much and where. I doubt you much care if in your 5123rd copy of the GNU GPL the "GNU" became a "GRU," or if in an image it turns one pixel of your brown eyes blue, but if it's in an executable or statistical data file, that's not good. -- University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Institute of Policy and Planning Sciences Tel/fax: +81 (298) 53-5091 __________________________________________________________________________ __________________________________________________________________________ What are those two straight lines for? "Free software rules." ------------------------------------------------------------------- Next Technical Meeting: October 9 (Sat), 13:30 place: Temple Univ. * Linux Internationalisation Initiative (Li18nux) speaker: Akio Kido * Japanese TrueType Fonts speaker: Adrian Havill Next Technical Meeting: November 13 (Sat), 13:30 place: Temple Univ. * Network Security speaker: Steve Baur Next Nomikai: December 17 (Fri), 19:00 Tengu TokyoEkiMae 03-3275-3691 ------------------------------------------------------------------- more info: http://www.tlug.gr.jp Sponsor: Global Online Japan
- References:
- tlug: Xcdroast verification failure
- From: Dennis McMurchy <denismcm@example.com>
Home | Main Index | Thread Index
- Prev by Date: tlug: Xcdroast verification failure
- Next by Date: tlug: msword files
- Prev by thread: tlug: Xcdroast verification failure
- Next by thread: tlug: msword files
- Index(es):
Home Page Mailing List Linux and Japan TLUG Members Links