From owner-freebsd-questions@FreeBSD.ORG Wed Jul 22 04:11:12 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6DBD8106566C for ; Wed, 22 Jul 2009 04:11:12 +0000 (UTC) (envelope-from bryant.eadon@gmail.com) Received: from mail-qy0-f191.google.com (mail-qy0-f191.google.com [209.85.221.191]) by mx1.freebsd.org (Postfix) with ESMTP id 1DFC48FC18 for ; Wed, 22 Jul 2009 04:11:12 +0000 (UTC) (envelope-from bryant.eadon@gmail.com) Received: by qyk29 with SMTP id 29so499368qyk.3 for ; Tue, 21 Jul 2009 21:11:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:reply-to :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=b2/A8z7CfT918fla22rKQG1GEq8rD8pA9ZdGpCdzXFM=; b=q/DsxUu+4mT02h7MFwA24OWGmr7cqwcAALCKKcFpftO7u3c+H95y0A/WzbruHp4xjE Gur0qm00BR9wuMlTW+3gEd6s2KjAdKnTjVLoof778Kj9NrmggaAbLTx05G5U5R76UQqd 266rXtclRAiyXvX4VIfSOsDzHlsSDJHwTyPfw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:reply-to:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=iM2zInw2J249V4rTLAfgyOG3vfvOJx6FIK4SYGBgbUnu5Ld3LsRDovPKuSKbvMjfcE zzU6DtV89TZshxtJm2pJTn+ic0Vzk2KzBMi11J4Vc/FN8h00pfN9caplQ4APoSm2NPee pePhNzVLNgneOqpcd/tzVWTFlkwf+pBDQN2ks= Received: by 10.224.6.148 with SMTP id 20mr385110qaz.203.1248235871563; Tue, 21 Jul 2009 21:11:11 -0700 (PDT) Received: from ?192.168.1.4? (rrcs-24-103-43-79.nyc.biz.rr.com [24.103.43.79]) by mx.google.com with ESMTPS id 6sm9554039qwk.44.2009.07.21.21.11.09 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 21 Jul 2009 21:11:10 -0700 (PDT) Message-ID: <4A66914B.4050909@gmail.com> Date: Wed, 22 Jul 2009 00:10:51 -0400 From: Bryant Eadon User-Agent: Thunderbird 2.0.0.22 (Windows/20090605) MIME-Version: 1.0 To: "b. f." References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-questions@FreeBSD.org Subject: Re: Support of UDF ISO-13346 on 7.1-RELEASE-p2 [SOLVED] X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: bryant.eadon@gmail.com List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Jul 2009 04:11:12 -0000 b. f. wrote: > #How can I mount this disc ? Does udf.ko support this format ? > > I don't often use memory disks, so I'm not quite sure what is going > wrong here. You could try configuring it and mounting it as > read-only, to see if that helps. But you should be aware that FreeBSD > does not support _all_ UDF filesystems, only some of them, and there > were some shortcomings with the earlier implementation of udf.ko that > you are using. For more information, see for example: > > http://en.wikipedia.org/wiki/Universal_Disk_Format > > So your disk image, if it really has an intact and valid UDF > filesystem, may still be unmountable even if you are doing everything > properly. I would suggest that you install the sysutils/udfclient > port or package, and use it to try to read the disk image. It > supports a slightly wider range of UDF filesystems than the kernel > module, and you don't have to go to the trouble of mounting the disk > image to read it. Of course, if you need to mount it, you could try > dumping it to a different filesystem and then mounting it as a memory > disk or otherwise. If that doesn't work, then it may be easiest to > use the native tools in some other OS (e.g., NetBSD, Vista ... ) > > b. I'm disappointed that FreeBSD mount_udf doesn't support this disc. to those trying: the solution is to use udfclient and browse that way. Alternatively there is a refuse package that makes UDFclient into a FS to mount. Do not be deterred by the complicated first-level directory : 97505d80MS UDFBridge:UDF Volume:GRC1CULXFRER_EN_DVD:GRC1CULXFRER_EN_#503F Yes, there are spaces in it, you'll want to quote it to access it properly.