From owner-freebsd-hackers@FreeBSD.ORG Thu Jun 23 19:32:29 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 328AE16A41C; Thu, 23 Jun 2005 19:32:29 +0000 (GMT) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.FreeBSD.org (Postfix) with ESMTP id CD4C743D53; Thu, 23 Jun 2005 19:32:28 +0000 (GMT) (envelope-from des@des.no) Received: from tim.des.no (localhost [127.0.0.1]) by spam.des.no (Postfix) with ESMTP id 4540060FA; Thu, 23 Jun 2005 21:32:23 +0200 (CEST) Received: from xps.des.no (des.no [80.203.228.37]) by tim.des.no (Postfix) with ESMTP id 101E160F7; Thu, 23 Jun 2005 21:32:23 +0200 (CEST) Received: by xps.des.no (Postfix, from userid 1001) id 8D29133D39; Thu, 23 Jun 2005 21:32:22 +0200 (CEST) To: John Baldwin References: <42BAC058.3040603@squbes.com> <42BAC1CB.30402@samsco.org> <86mzphcc0z.fsf@xps.des.no> <200506231337.27239.jhb@FreeBSD.org> From: des@des.no (=?iso-8859-1?q?Dag-Erling_Sm=F8rgrav?=) Date: Thu, 23 Jun 2005 21:32:22 +0200 In-Reply-To: <200506231337.27239.jhb@FreeBSD.org> (John Baldwin's message of "Thu, 23 Jun 2005 13:37:25 -0400") Message-ID: <86zmtglvi1.fsf@xps.des.no> User-Agent: Gnus/5.110002 (No Gnus v0.2) Emacs/21.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Spam-Tests: ALL_TRUSTED,AWL,BAYES_00 X-Spam-Learn: ham X-Spam-Score: -5.2/5.0 X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on tim.des.no Cc: freebsd-hackers@freebsd.org, Scott Long , Gregg Cooper Subject: Re: Duplicate inodes in 5.4-RELEASE-i386-disc1.iso X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Jun 2005 19:32:29 -0000 John Baldwin writes: > Even if mkisofs is patched this change isn't a bug in mkisofs. It's > really a bug in our iso9660 filesystem. :( Yes, but it's a lot harder to fix there than in mkisofs :) Actually, -CURRENT doesn't have this bug, but it has another: it bases the inode number on the position of the directory entry, so hard links are lost. It doesn't make a big difference, because mkisofs seems unable to generate ISO 9660 file systems with hard links. DES --=20 Dag-Erling Sm=F8rgrav - des@des.no