From owner-freebsd-questions@FreeBSD.ORG Fri Mar 23 00:54:52 2007 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 32D3816A403 for ; Fri, 23 Mar 2007 00:54:52 +0000 (UTC) (envelope-from pauls@utdallas.edu) Received: from mail.stovebolt.com (mail.stovebolt.com [66.221.101.249]) by mx1.freebsd.org (Postfix) with ESMTP id 0E07B13C46A for ; Fri, 23 Mar 2007 00:54:52 +0000 (UTC) (envelope-from pauls@utdallas.edu) Received: from [192.168.2.102] (adsl-209-30-153-15.dsl.rcsntx.swbell.net [209.30.153.15]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.stovebolt.com (Postfix) with ESMTP id 65979114313; Thu, 22 Mar 2007 18:59:08 -0600 (CST) Date: Thu, 22 Mar 2007 19:54:48 -0500 From: Paul Schmehl To: UCTC Sysadmin , freebsd-questions@freebsd.org Message-ID: <9236D72618FBF0DAF3BA29FA@paul-schmehls-powerbook59.local> In-Reply-To: <46030E6A.4000308@transpacific.net> References: <4602D994.3080801@transpacific.net> <20070322214252.GB22055@gizmo.acns.msu.edu> <46030E6A.4000308@transpacific.net> X-Mailer: Mulberry/4.0.7b1 (Mac OS X) MIME-Version: 1.0 Content-Type: multipart/signed; micalg=sha1; protocol="application/pkcs7-signature"; boundary="==========5D94FE3C0D12076F2986==========" X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Jerry McAllister , Mark Busby Subject: Re: SOLVED: Re: Problems with "burncd" - cannot mount result on unix or windows X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Mar 2007 00:54:52 -0000 --==========5D94FE3C0D12076F2986========== Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline --On March 22, 2007 4:16:58 PM -0700 UCTC Sysadmin=20 wrote: > > So THE FAQ and/or HOWTO SUCKS, is the problem. If that offends purists, > try fixing your transmission > under deadline with a japanese shop manual translated into english and > no diagrams. Documentation makes > all the difference, both to novices and to professionals. Someone who > knows the how and what should > write a contributed thing - whenever they have the time and desire to > educate the unwashed masses. > man (8) burncd " In the examples above, the files burned to data CD-Rs are assumed to be ISO9660 file systems. mkisofs(8), available in the FreeBSD Ports=20 Collec- tion, as part of the sysutils/cdrtools port, is commonly used to=20 create ISO9660 file system images from a given directory tree." Hmmmmm..... man (8) mkisofs "mkisofs is effectively a pre-mastering program to generate an ISO9660/JOLIET/HFS hybrid filesystem. mkisofs is capable of generating the System Use Sharing=20 Protocol records (SUSP) specified by the Rock Ridge Interchange Protocol.=20 This is used to further describe the files in the iso9660 filesystem=20 to a unix host, and provides information such as longer filenames,=20 uid/gid, posix permissions, symbolic links, block and character devices." If you don't like man pages, there's always the handbook: "CDs have a number of features that differentiate them from conventional=20 disks. Initially, they were not writable by the user. They are designed so = that they can be read continuously without delays to move the head between = tracks. They are also much easier to transport between systems than=20 similarly sized media were at the time. CDs do have tracks, but this refers to a section of data to be read=20 continuously and not a physical property of the disk. To produce a CD on=20 FreeBSD, you prepare the data files that are going to make up the tracks=20 on the CD, then write the tracks to the CD. The ISO 9660 file system was designed to deal with these differences. It=20 unfortunately codifies file system limits that were common then.=20 Fortunately, it provides an extension mechanism that allows properly=20 written CDs to exceed those limits while still working with systems that=20 do not support those extensions. The sysutils/cdrtools port includes mkisofs(8), a program that you can use = to produce a data file containing an ISO 9660 file system. It has options=20 that support various extensions, and is described below. Which tool to use to burn the CD depends on whether your CD burner is=20 ATAPI or something else. ATAPI CD burners use the burncd program that is=20 part of the base system. SCSI and USB CD burners should use cdrecord from=20 the sysutils/cdrtools port. It is also possible to use cdrecord and other=20 tools for SCSI drives on ATAPI hardware with the ATAPI/CAM module. If you want CD burning software with a graphical user interface, you may=20 wish to take a look at either X-CD-Roast or K3b. These tools are available = as packages or from the sysutils/xcdroast and sysutils/k3b ports.=20 X-CD-Roast and K3b require the ATAPI/CAM module with ATAPI hardware." Unix systems *assume* you can read. Perhaps that's a bad assumption, but=20 that's the assumption they make. Unfortunately, many people are impatient = and get ahead of themselves, thinking that partial knowledge is all that's = required. Sometimes that works. Sometimes it doesn't. Paul Schmehl (pauls@utdallas.edu) Senior Information Security Analyst The University of Texas at Dallas http://www.utdallas.edu/ir/security/ --==========5D94FE3C0D12076F2986==========--