Re: cdio burning images
If you are using a CD-RW -- make sure you have blanked it first by cdio blank Also, if you're using the first drive, i.e. cd0, you don't have to specify the device, you can just type cdio tao image.iso On Fri, 11 Nov 2011 23:07:41 +1100 John Tate j...@johntate.org wrote: # cdio -f cd0c tao /home/john/ubuntu-11.10-desktop-i386.iso cdio: The media can't be written in TAO mode What am I doing wrong? -- www.johntate.org
Re: cdio burning images
I did, I have actually solved the problem now. On Sat, Nov 12, 2011 at 11:11 PM, Norman Golisz li...@zcat.de wrote: Hi John, On Fri Nov 11 2011 16:44, Norman Golisz wrote: On Fri Nov 11 2011 23:07, John Tate wrote: # cdio -f cd0c tao /home/john/ubuntu-11.10-desktop-i386.iso cdio: The media can't be written in TAO mode What am I doing wrong? You don't read manuals. cdio(1): -f device Specifies the name of the CD device, such as /dev/rcd0c. Both absolute and relative paths to /dev filenames are possible; the raw partition name is added if needed. Meaning that when you specify -f cd0 it internally converts it to -f /dev/rcd0c. Also, you probably want to explore disklabel(8) and the difference between raw-level and block-level access of block devices. Read a UNIX book of your choice, or stick with Google hunting for an explanation. even though this information is not principally wrong, it was unrelated, incomplete and written inadequately rude. Sorry for that. However, did you compare the ISO's checksum after downloading it? Norman. -- www.johntate.org
Re: cdio burning images
On Sat, 12 Nov 2011 16:19:31 +1100, John Tate wrote: Recap... cdio... # cdio tao /home/john/ubuntu-11.10-desktop-i386.iso cdio: The media can't be written in TAO mode Well, I don't know if you have media that will take 788MB images. Who is silly enough to make those ISOs that big? Or are you supposed to be putting them on DVD? If that turns out to be the problem, I'd be running ISO Master to delete some of the cruft. It's what I use to add a swag of packages to a snapshot installxx.iso so I keep the OS and pkgs in sync but I never hit 700MB. As far as cdio is concerned, I run the following command line several times a week when I'm messing with current: #cdio -f cd0c tao /usr/src/distrib/i386/iso/obj/install50.iso and never have a problem. NB: if you only have one CD drive that will work if it is known to the OS as an internal drive and whatever your drive is you should avoid using the full /dev/cd0c name and never use cd0a. I'm guessing I get that one because ISO distribution has deviated a long way from formally defined standards towards spontaneously defined ones. Well my ISOs are made by mkhybrid and (AFAICT) cleave solidly to the ISO spec. *** NOTE *** Please DO NOT CC me. I am subscribed to the list. Mail to the sender address that does not originate at the list server is tarpitted. The reply-to: address is provided for those who feel compelled to reply off list. Thankyou. Rod/ --- This life is not the real thing. It is not even in Beta. If it was, then OpenBSD would already have a man page for it.
Re: cdio burning images
Hi John, On Fri Nov 11 2011 16:44, Norman Golisz wrote: On Fri Nov 11 2011 23:07, John Tate wrote: # cdio -f cd0c tao /home/john/ubuntu-11.10-desktop-i386.iso cdio: The media can't be written in TAO mode What am I doing wrong? You don't read manuals. cdio(1): -f device Specifies the name of the CD device, such as /dev/rcd0c. Both absolute and relative paths to /dev filenames are possible; the raw partition name is added if needed. Meaning that when you specify -f cd0 it internally converts it to -f /dev/rcd0c. Also, you probably want to explore disklabel(8) and the difference between raw-level and block-level access of block devices. Read a UNIX book of your choice, or stick with Google hunting for an explanation. even though this information is not principally wrong, it was unrelated, incomplete and written inadequately rude. Sorry for that. However, did you compare the ISO's checksum after downloading it? Norman.
Re: cdio burning images
On Fri, Nov 11, 2011 at 6:07 AM, John Tate j...@johntate.org wrote: # cdio -f cd0c tao /home/john/ubuntu-11.10-desktop-i386.iso cdio: The media can't be written in TAO mode What am I doing wrong? I'm guessing the full device path is needed (i.e., /dev/cd0c). However, consider the faq ( http://www.openbsd.org/faq/faq4.html#MkInsMedia ): faq 4.3.1 - Making a CD-ROM You can create a CD-ROM using the cd50.iso or install50.iso files. The exact details here are left to the reader to determine with the tools they have at their disposal. In OpenBSD, you can create a CD from an ISO image using cdio(1): # cdio tao cd50.iso Most CD recorders sold for Windows and Macintosh systems come with software that can burn ISO images to blank media. If yours does not, there are various no-cost applications that can do this for you. /faq -Neal
Re: cdio burning images
On Fri Nov 11 2011 23:07, John Tate wrote: # cdio -f cd0c tao /home/john/ubuntu-11.10-desktop-i386.iso cdio: The media can't be written in TAO mode What am I doing wrong? You don't read manuals. cdio(1): -f device Specifies the name of the CD device, such as /dev/rcd0c. Both absolute and relative paths to /dev filenames are possible; the raw partition name is added if needed. Meaning that when you specify -f cd0 it internally converts it to -f /dev/rcd0c. Also, you probably want to explore disklabel(8) and the difference between raw-level and block-level access of block devices. Read a UNIX book of your choice, or stick with Google hunting for an explanation. Norman.
Re: cdio burning images
Recap... cdio... # cdio tao /home/john/ubuntu-11.10-desktop-i386.iso cdio: The media can't be written in TAO mode I'm guessing I get that one because ISO distribution has deviated a long way from formally defined standards towards spontaneously defined ones. cdrecord...# cdrecord -vv -dao dev=/dev/cd0c /home/john/ubuntu-11.10-desktop-i386.iso Cdrecord-Clone 2.01 (--) Copyright (C) 1995-2004 Jvrg Schilling TOC Type: 1 = CD-ROM scsidev: '/dev/cd0c' devname: '/dev/cd0c' scsibus: -2 target: -2 lun: -2 Using libscg version 'schily-0.8'. Using libscg transport code version 'schily-scsi-bsd.c-1.42' SCSI buffer size: 61440 atapi: 0 Device type: Removable CD-ROM Version: 0 Response Format: 2 Capabilities : Vendor_info: 'ASUS' Identifikation : 'DRW-20B1LT ' Revision : '1.00' Device seems to be: Generic mmc2 DVD-R/DVD-RW. Current: 0x0011 Profile: 0x002B Profile: 0x001B Profile: 0x001A Profile: 0x0016 Profile: 0x0015 Profile: 0x0014 Profile: 0x0013 Profile: 0x0012 Profile: 0x0011 (current) Profile: 0x0010 Profile: 0x000A Profile: 0x0009 Profile: 0x0008 Profile: 0x0002 cdrecord: Found DVD media but DVD-R/DVD-RW support code is missing. cdrecord: If you need DVD-R/DVD-RW support, ask the Author for cdrecord-ProDVD. cdrecord: Free test versions and free keys for personal use are at ftp://ftp.berlios.de/pub/cdrecord/ProDVD/ cdrecord: This version of cdrecord does not include DVD-R/DVD-RW support code. cdrecord: If you need DVD-R/DVD-RW support, ask the Author for cdrecord-ProDVD. cdrecord: Free test versions and free keys for personal use are at ftp://ftp.berlios.de/pub/cdrecord/ProDVD/ Drive current speed: 125 Drive default speed: 125 Drive max speed: 125 Selected speed : 125 Using generic SCSI-3/mmc CD/DVD driver (checks media) (mmc_cd_dvd). Driver flags : MMC-3 SWABAUDIO BURNFREE FORCESPEED Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R RAW/R16 RAW/R96P RAW/R96R Drive buf size : 1310720 = 1280 KB FIFO size : 4194304 = 4096 KB Track 01: data 695 MB track: 1 start: 0 pregap: 150 Total size: 798 MB (79:06.53) = 355990 sectors Lout start: 798 MB (79:08/40) = 355990 sectors Track 1 start 0 Track 2 start 355990 41 00 A0 00 00 00 00 01 00 00 00 00 41 00 A1 00 00 00 00 01 00 00 00 00 41 00 A2 00 00 00 00 79 08 40 00 00 41 00 01 00 00 00 00 00 02 00 00 00 Current Secsize: 2048 cdrecord: Unspecified command not implemented for this drive. cdrecord: WARNING: Data may not fit on standard 74min disk. Forcespeed is OFF. Starting to write CD/DVD at speed 125 in real SAO mode for single session. Last chance to quit, starting real write0 seconds. Operation starts. Waiting for reader process to fill input buffer ... input buffer ready. Writing pregap for track 1 at -150 cdrecord: Input/output error. write_g1: scsi sendcmd: retryable error CDB: 2A 00 FF FF FF 6A 00 00 1E 00 status: 0x0 (GOOD STATUS) resid: 61440 cmd finished after 0.018s timeout 200s write track pad data: error after 0 bytes BFree: 0 K BSize: 1280 K Starting new track at sector: 0 Track 01:0 of 695 MB written.cdrecord: Input/output error. write_g1: scsi sendcmd: retryable error CDB: 2A 00 00 00 00 00 00 00 1E 00 status: 0x0 (GOOD STATUS) resid: 61440 cmd finished after 0.020s timeout 200s write track data: error after 0 bytes cdrecord: A write error occured. cdrecord: Please properly read the error message above. Writing time:5.061s Average write speed 938.1x. Fixating... Fixating time:0.000s cdrecord: fifo had 68 puts and 1 gets. cdrecord: fifo was 0 times empty and 0 times full, min fill was 100%. John Tate On Sat, Nov 12, 2011 at 1:14 AM, Neal Hogan nealho...@gmail.com wrote: On Fri, Nov 11, 2011 at 6:07 AM, John Tate j...@johntate.org wrote: # cdio -f cd0c tao /home/john/ubuntu-11.10-desktop-i386.iso cdio: The media can't be written in TAO mode What am I doing wrong? I'm guessing the full device path is needed (i.e., /dev/cd0c). However, consider the faq ( http://www.openbsd.org/faq/faq4.html#MkInsMedia ): faq 4.3.1 - Making a CD-ROM You can create a CD-ROM using the cd50.iso or install50.iso files. The exact details here are left to the reader to determine with the tools they have at their disposal. In OpenBSD, you can create a CD from an ISO image using cdio(1): # cdio tao cd50.iso Most CD recorders sold for Windows and Macintosh systems come with software that can burn ISO images to blank media. If yours does not, there are various no-cost applications that can do this for you. /faq -Neal -- www.johntate.org
