From owner-freebsd-questions@FreeBSD.ORG Wed May 14 21:35:10 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B649637B401 for ; Wed, 14 May 2003 21:35:10 -0700 (PDT) Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by mx1.FreeBSD.org (Postfix) with ESMTP id D5F8B43F85 for ; Wed, 14 May 2003 21:35:08 -0700 (PDT) (envelope-from grog@lemis.com) Received: by wantadilla.lemis.com (Postfix, from userid 1004) id 646F851A78; Thu, 15 May 2003 14:04:52 +0930 (CST) Date: Thu, 15 May 2003 14:04:52 +0930 From: Greg 'groggy' Lehey To: Greg Lane Message-ID: <20030515043452.GF21491@wantadilla.lemis.com> References: <20030515013732.GL4390@wantadilla.lemis.com> <3EC2F97E.7040702@vagner.com> <20030515023954.GB80240@localhost.bigpond.net.au> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Y1L3PTX8QE8cb2T+" Content-Disposition: inline In-Reply-To: <20030515023954.GB80240@localhost.bigpond.net.au> User-Agent: Mutt/1.4i Organization: The FreeBSD Project Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.FreeBSD.org/ X-PGP-Fingerprint: 9A1B 8202 BCCE B846 F92F 09AC 22E6 F290 507A 4223 cc: freebsd-questions@freebsd.org Subject: Re: How can I mount a cdrom .bin file? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 May 2003 04:35:11 -0000 --Y1L3PTX8QE8cb2T+ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thursday, 15 May 2003 at 12:39:54 +1000, Greg Lane wrote: > Hi, > > See earlier in the thread for one method (which I have never > personally tried) or do the following which I normally use: > > vnconfig /dev/vn0c /path/to/cd1.iso > mount -t cd9660 /dev/vn0c /mnt > > To unmount: > > umount /mnt > vnconfig -u /dev/vn0c > > Obviously the man page for vnconfig will be of interest to you! vn goes away in release 5 of FreeBSD. Use the md device instead. Here's an extract from the fourth edition of "The Complete FreeBSD": Testing the CD-R ________________ =20 So now you have an ISO image. How do you know it's correct? It's j= ust a single file, and it could have just about anything on it. You can burn= a CD, of course, but if it's junk, you have another coaster. If you're not = sure, it's better to look inside first. You can do that by using it as the bas= is for an md vnode device. =20 The md driver creates a number of different kinds of pseudo-device. Se= e the man page md(4) for more details. We use the vnode device, a special fil= e that refers to file system files. Support for md is included in the GENERIC k= ernel, but if you've built a kernel without the md driver, you can load it as = a kld. If you're not sure, try loading the kld anyway. Then you associate a = vnode device with the ISO image iso-image using the program mdconfig: =20 # kldload md load the kld module if necessary kldload: can't load md: File exists already loaded or in the kernel # mdconfig -a -t vnode -f iso-image configure the device md0 this is the name assigned # mount -t cd9660 /dev/md0 /mnt mount it =20 After this, you will be able to access the image at /mnt as a norma= l file system. Don't forget to unmount and unconfigure the file when you're fin= ished: =20 # umount /mnt # mdconfig -d -u 0 =20 Older releases of FreeBSD used the vn driver, which used different syntax. Greg -- When replying to this message, please copy the original recipients. If you don't, I may ignore the reply or reply to the original recipients. For more information, see http://www.lemis.com/questions.html See complete headers for address and phone numbers --Y1L3PTX8QE8cb2T+ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.0 (FreeBSD) iD8DBQE+wxjsIubykFB6QiMRAk+EAJ4oSeVXaZOF0BehUUDYLdN+zhBdTwCePKqO Lu3y91em5AnLRJzoKLcJPlA= =96Cl -----END PGP SIGNATURE----- --Y1L3PTX8QE8cb2T+--