syntax and logic for writing .iso using cdrecord?
Hi all, I have couple of queries. This is the normal/usual syntax told about using cdrecord when writing an .iso image file. cdrecord dev=/dev/cdrom driveropts=burnfree -v -data cd_image.iso I am interested in this particular path of the syntax dev=/dev/cdrom I have a Liteon DVD writer+ CD-Writer. This is the output when I use scanbus $ cdrecord --scanbus scsibus1: 1,0,0 100) 'LITE-ON ' 'DVDRW SOHW-1633S' 'BS0S' Removable CD-ROM 1,1,0 101) * 1,2,0 102) * 1,3,0 103) * 1,4,0 104) * 1,5,0 105) * 1,6,0 106) * 1,7,0 107) * Now please lemme know if this logic is correct or not? cdrecord dev=1,0,0 driveropts=burnfree -v -data cd_image.iso Is the above correct or should it have any errors? If needed can give dmesg as well. Looking forward to know a bit more. -- Regards, Shirish Agarwal My quotes in this email licensed under CC 3.0 http://creativecommons.org/licenses/by-nc/3.0/ http://flossexperiences.wordpress.com 065C 6D79 A68C E7EA 52B3 8D70 950D 53FB 729A 8B17 -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@other.debian.org
Is ulimit -l unlimited or limit memorylocked unlimited still needed?
Hi all, I went to the homepage of the dvd+rw-tools homepage. http://fy.chalmers.se/~appro/linux/DVD+RW/tools/ It gave me the following warning IMPORTANT NOTE for 6.0 users! Newer Linux kernels have ridiculously low default memorylocked resource limit, which prevents privileged users from starting growisofs 6.0 with unable to anonymously mmap 33554432: Resource temporarily unavailable error message. Next version will naturally have workaround coded in, but meanwhile you have to issue following command at command prompt prior starting growisofs: * if you run C-like shell, issue 'limit memorylocked unlimited'; * if you run Bourne-like shell, issue 'ulimit -l unlimited'; IMPORTANT NOTE for 5.19 users! A bug was introduced in version 5.19, which manifests itself by inability to finalize recording, it takes forever to flush cache. Apply hotfix or download patched tar-ball. If you have suffered from this bug and have non-finalized DVD±R media, you can use this snippet to revive it. DVD+RW media can be finalized with dvd+rw-format -lead-out. Now I'm running $ growisofs --version * growisofs by ap...@fy.chalmers.se, version 7.1, front-ending to genisoimage: genisoimage 1.1.8 (Linux) So does this still to be patched or has the workaround been applied in the newer version. -- Regards, Shirish Agarwal My quotes in this email licensed under CC 3.0 http://creativecommons.org/licenses/by-nc/3.0/ http://flossexperiences.wordpress.com 065C 6D79 A68C E7EA 52B3 8D70 950D 53FB 729A 8B17 -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@other.debian.org
Re: syntax and logic for writing .iso using cdrecord?
shirish shirisha...@gmail.com wrote: Hi all, I have couple of queries. This is the normal/usual syntax told about using cdrecord when writing an .iso image file. cdrecord dev=/dev/cdrom driveropts=burnfree -v -data cd_image.iso I am interested in this particular path of the syntax dev=/dev/cdrom Using dev=/dev/cdrom is dprecated and unsupported. It may work in some conditions but there is no guarantee. The dev=/dev/cdrom will not work at all on many operating systems and even on UNIX-like systems, there are dvices without a dedicated device driver that for this reason don't have any /dev/* entry. I have a Liteon DVD writer+ CD-Writer. This is the output when I use scanbus $ cdrecord --scanbus scsibus1: 1,0,0 100) 'LITE-ON ' 'DVDRW SOHW-1633S' 'BS0S' Removable CD-ROM 1,1,0 101) * 1,2,0 102) * 1,3,0 103) * 1,4,0 104) * 1,5,0 105) * 1,6,0 106) * 1,7,0 107) * Now please lemme know if this logic is correct or not? cdrecord dev=1,0,0 driveropts=burnfree -v -data cd_image.iso Is the above correct or should it have any errors? It is correct, but in case you only have one drive in your system, there is no need to spesify dev= at all. Jörg -- EMail:jo...@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin j...@cs.tu-berlin.de(uni) joerg.schill...@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@other.debian.org
Re: Is ulimit -l unlimited or limit memorylocked unlimited still needed?
shirish shirisha...@gmail.com wrote: Hi all, I went to the homepage of the dvd+rw-tools homepage. http://fy.chalmers.se/~appro/linux/DVD+RW/tools/ It gave me the following warning IMPORTANT NOTE for 6.0 users! Newer Linux kernels have ridiculously low default memorylocked resource limit, which prevents privileged users from starting growisofs 6.0 with unable to anonymously mmap 33554432: Resource temporarily unavailable error message. Next version will naturally have workaround coded in, but meanwhile you have to issue following command at command prompt prior starting growisofs: There is no need to do this in case you are using cdrecord. Cdrecord includes a workaround for the named problem since January 2006. Jörg -- EMail:jo...@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin j...@cs.tu-berlin.de(uni) joerg.schill...@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@other.debian.org
Re: syntax and logic for writing .iso using cdrecord?
Reply in-line :- On Mon, Jan 26, 2009 at 04:19, Joerg Schilling joerg.schill...@fokus.fraunhofer.de wrote: shirish shirisha...@gmail.com wrote: Hi all, I have couple of queries. This is the normal/usual syntax told about using cdrecord when writing an .iso image file. cdrecord dev=/dev/cdrom driveropts=burnfree -v -data cd_image.iso I am interested in this particular path of the syntax dev=/dev/cdrom Using dev=/dev/cdrom is dprecated and unsupported. It may work in some conditions but there is no guarantee. The dev=/dev/cdrom will not work at all on many operating systems and even on UNIX-like systems, there are devices without a dedicated device driver that for this reason don't have any /dev/* entry. Hi Joerg, If dev=/dev/cdrom is deprecated then what syntax is used nowadays? I have a Liteon DVD writer+ CD-Writer. This is the output when I use scanbus $ cdrecord --scanbus scsibus1: 1,0,0 100) 'LITE-ON ' 'DVDRW SOHW-1633S' 'BS0S' Removable CD-ROM 1,1,0 101) * 1,2,0 102) * 1,3,0 103) * 1,4,0 104) * 1,5,0 105) * 1,6,0 106) * 1,7,0 107) * Now please lemme know if this logic is correct or not? cdrecord dev=1,0,0 driveropts=burnfree -v -data cd_image.iso Is the above correct or should it have any errors? It is correct, but in case you only have one drive in your system, there is no need to specify dev= at all. Then, in my case how should I have given it? like this ? cdrecord driveropts=burnfree -v -data cd_image.iso Also is there a syntax or notation of speed which can be put up somewhere? Jörg -- Regards, Shirish Agarwal My quotes in this email licensed under CC 3.0 http://creativecommons.org/licenses/by-nc/3.0/ http://flossexperiences.wordpress.com 065C 6D79 A68C E7EA 52B3 8D70 950D 53FB 729A 8B17 -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@other.debian.org
