Date: Thu, 13 Jul 1995 09:18:39 -0700 From: "David E. Tweten" <tweten@tale.frihet.com> To: info@cdrom.com Cc: hahn@and.com Subject: CDROM Reading "errors" Message-ID: <199507131618.JAA15057@tale.frihet.com> Resent-Message-ID: <1539.805705811@time.cdrom.com>
next in thread | raw e-mail | index | archive | help
Previously, I've never had any trouble reading Rock Ridge format CDROMs from
Walnut Creek. Recently, a friend asked that I try reading a Walnet Creek
Linux CDROM he couldn't get to boot, or to read on MS-Windows. It generated
large volumes of syslog messages on my FreeBSD 1.0.1 and 1.1.5.1 systems. The
same effect now happens with the new FreeBSD 2.0.5 CDROM. A sample of syslog
output follows:
Jul 13 00:20:23 tale /386bsd: isofs: name '' - type [f177517e/f17751a0]...not
found
Jul 13 00:20:23 tale /386bsd: isofs: 00 00 3c 00 00 00 00 10 00 00 01 00 00 00
00 00 : <
Jul 13 00:20:23 tale /386bsd: isofs: 00 00 ff ff ff ff 00 00 00 00 33 33 00 00
00 00 : 33
Jul 13 00:20:23 tale /386bsd: isofs: 00 00 :
Jul 13 00:20:23 tale /386bsd:
Jul 13 00:20:43 tale /386bsd: isofs:RR[5] idflag=0xf153f120
Jul 13 00:20:43 tale /386bsd: isofs:RR[5] idflag=0xf153f1a2
Jul 13 00:20:44 tale /386bsd: isofs:RR[5] idflag=0xf153f21c
Jul 13 00:20:44 tale /386bsd: isofs:RR[5] idflag=0xf153f292
Jul 13 00:20:44 tale /386bsd: isofs:RR[5] idflag=0xf153f30c
Jul 13 00:20:44 tale /386bsd: isofs:RR[5] idflag=0xf153f384
Jul 13 00:20:44 tale /386bsd: isofs:RR[5] idflag=0xf153f3f6
Jul 13 00:20:44 tale /386bsd: isofs:RR[5] idflag=0xf153f470
Jul 13 00:20:44 tale /386bsd: isofs:RR[5] idflag=0xf153f4f2
Jul 13 00:20:44 tale /386bsd: isofs:RR[5] idflag=0xf153f570
Jul 13 00:20:44 tale /386bsd: isofs:RR[5] idflag=0xf153f5e8
Jul 13 00:20:44 tale /386bsd: isofs:RR[5] idflag=0xf153f660
Jul 13 00:20:44 tale /386bsd: isofs:RR[5] idflag=0xf153f6d8
Jul 13 00:20:44 tale /386bsd: isofs:RR[5] idflag=0xf153f754
Jul 13 00:20:44 tale /386bsd: isofs:RR[5] idflag=0xf179902c
Jul 13 00:20:44 tale /386bsd: isofs:RR[5] idflag=0xf17990a6
Jul 13 00:20:44 tale /386bsd: isofs:RR[5] idflag=0xf1799124
Jul 13 00:20:44 tale /386bsd: isofs:RR[5] idflag=0xf179919a
Jul 13 00:20:44 tale /386bsd: isofs:RR[5] idflag=0xf1799214
Jul 13 00:20:44 tale /386bsd: isofs:RR[5] idflag=0xf1799290
Jul 13 00:20:44 tale /386bsd: isofs:RR[5] idflag=0xf1799306
Jul 13 00:20:44 tale /386bsd: isofs:RR[5] idflag=0xf179937a
Jul 13 00:20:44 tale /386bsd: isofs:RR[5] idflag=0xf17993f2
Jul 13 00:20:44 tale /386bsd: isofs:RR[5] idflag=0xf179946c
Have you folks changed CD mastering systems since FreeBSD 2.0 (whose CDROM
causes no such flood of complaints)? Is this a Walnut Creek problem or a
FreeBSD 1 problem? Thanks in advance for any enlightenment you can provide.
--
David E. Tweten | PGP Key fingerprint = | tweten@frihet.com
12141 Atrium Drive | E9 59 E7 5C 6B 88 B8 90 | tweten@and.com
Saratoga, CA 95070-3162 | 65 30 2A A4 A0 BC 49 AE | (408) 446-4131
The only flags worth saluting are those you are permitted to burn.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199507131618.JAA15057>