From owner-freebsd-bugs Sun Jul 16 03:01:31 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id DAA16890 for bugs-outgoing; Sun, 16 Jul 1995 03:01:31 -0700 Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id DAA16860 for ; Sun, 16 Jul 1995 03:01:24 -0700 Received: from sax.sax.de by irz301.inf.tu-dresden.de with SMTP (5.67b+/DEC-Ultrix/4.3) id AA23551; Sun, 16 Jul 1995 12:01:21 +0200 Received: by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id MAA00590; Sun, 16 Jul 1995 12:01:10 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.6.11/8.6.9) id JAA16040; Sun, 16 Jul 1995 09:01:22 +0200 From: J Wunsch Message-Id: <199507160701.JAA16040@uriah.heep.sax.de> Subject: Re: CDROM Reading "errors" To: tweten@frihet.com Date: Sun, 16 Jul 1995 09:01:21 +0200 (MET DST) Cc: info@cdrom.com, hahn@and.com, bugs@freebsd.org In-Reply-To: <199507131618.JAA15057@tale.frihet.com> from "David E. Tweten" at Jul 13, 95 09:18:39 am Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 1608 Sender: bugs-owner@freebsd.org Precedence: bulk As David E. Tweten wrote: > > 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 Looking at the code in FreeBSD 1's isofs handling, there's a bunch of blatant printf's that apparently do nothing and have been omitted in FreeBSD 2's cd9660 file system. Is the CD unreadable, or is it just that the printf's are annoying? If it's really unreadable, the problem must be the ``name '' - type ...'' thingie, the RR[5]'s are benign. From a quick glance over the code, i've got no idea. If it's simply annoying, kill the printf's out of isofs_rrip.c, and recompile your kernel. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ Never trust an operating system you don't have sources for. ;-)