Re: problems writing a large file to DVD+R Double Layer disk
On Sunday 29 April 2007 16:15:50 you wrote: > Ismail Dönmez <[EMAIL PROTECTED]> wrote: > > > In a few weeks, mkisofs will support single files up to 8 TB and hide > > > these files (if larger tan 234 GB) from the UDF tree for consistency. > > > > So the problem is that currently a file that is larger than 4GB is not > > supported but if the files are smaller than 4 GB there is no problem with > > writing a 7.4 GB isofile ? > > Files in the ISO-9660 namespace are not yet supported to be > 4 GB. > > This will change soon. That clears up everything for me. Thanks for taking time to explain. Best Regards, ismail signature.asc Description: This is a digitally signed message part.
Re: problems writing a large file to DVD+R Double Layer disk
Ismail Dönmez <[EMAIL PROTECTED]> wrote: > > In a few weeks, mkisofs will support single files up to 8 TB and hide these > > files (if larger tan 234 GB) from the UDF tree for consistency. > > So the problem is that currently a file that is larger than 4GB is not > supported but if the files are smaller than 4 GB there is no problem with > writing a 7.4 GB isofile ? Files in the ISO-9660 namespace are not yet supported to be > 4 GB. This will change soon. Note that as this "genisoimage" fork is based on an old version of mkisofs, it does not support more than a recent mkisofs. Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) [EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: problems writing a large file to DVD+R Double Layer disk
On Sunday 29 April 2007 15:31:35 Joerg Schilling wrote: [...] > Seems you did get things wrong. > > Mkisofs theorectically writes ISO image files up to 16 Exabytes. The size > of an ISO image is technically limited (by the ISO-9660 filesystem) to 8 > Terabytes. > > A 7.4 GB filesystem is more than 1000x smaller than what ISO-9660 supports. > > Mkisofs supports single UDF files > 1 GB (up to 234 GB) since November 24th > 2002 If you turn off consistency checks, you may write defective ISO images > that seem to include single files larger than 4 GB since then. > > In a few weeks, mkisofs will support single files up to 8 TB and hide these > files (if larger tan 234 GB) from the UDF tree for consistency. So the problem is that currently a file that is larger than 4GB is not supported but if the files are smaller than 4 GB there is no problem with writing a 7.4 GB isofile ? Regards, ismail signature.asc Description: This is a digitally signed message part.
Re: problems writing a large file to DVD+R Double Layer disk
Ismail Dönmez <[EMAIL PROTECTED]> wrote: > > > > What do you expect from using an unmaintained fork from a > 2.5 year > > > > old version of mkisofs? > > > > > > Well, it may be 2.5 years old, but I managed to burn a 7.4 GB file > > > with it. > > > > Well, I did add large file support to mkisofs on January 25th 2001. > > Hmm but you said mkisofs would support such large files in a later date? Or > did I get it all wrong? Seems you did get things wrong. Mkisofs theorectically writes ISO image files up to 16 Exabytes. The size of an ISO image is technically limited (by the ISO-9660 filesystem) to 8 Terabytes. A 7.4 GB filesystem is more than 1000x smaller than what ISO-9660 supports. Mkisofs supports single UDF files > 1 GB (up to 234 GB) since November 24th 2002 If you turn off consistency checks, you may write defective ISO images that seem to include single files larger than 4 GB since then. In a few weeks, mkisofs will support single files up to 8 TB and hide these files (if larger tan 234 GB) from the UDF tree for consistency. Mkisofs development is oriented on quality and reliability rather than implementing cheep hacks. Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) [EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: problems writing a large file to DVD+R Double Layer disk
On Sunday 29 April 2007 14:18:34 Joerg Schilling wrote: > Dominique Dumont <[EMAIL PROTECTED]> wrote: > > [EMAIL PROTECTED] (Joerg Schilling) writes: > > >> I currently create an udf image with genisofs: > > > > > > What do you expect from using an unmaintained fork from a > 2.5 year > > > old version of mkisofs? > > > > Well, it may be 2.5 years old, but I managed to burn a 7.4 GB file > > with it. > > Well, I did add large file support to mkisofs on January 25th 2001. Hmm but you said mkisofs would support such large files in a later date? Or did I get it all wrong? Regards, ismail signature.asc Description: This is a digitally signed message part.
Re: problems writing a large file to DVD+R Double Layer disk
Dominique Dumont <[EMAIL PROTECTED]> wrote: > [EMAIL PROTECTED] (Joerg Schilling) writes: > > >> I currently create an udf image with genisofs: > > > > What do you expect from using an unmaintained fork from a > 2.5 year old > > version of mkisofs? > > Well, it may be 2.5 years old, but I managed to burn a 7.4 GB file > with it. Well, I did add large file support to mkisofs on January 25th 2001. Dou you like to use a 6+ year old program? Obviously not, so why to you use a nearly 3 year old program? If you like to benefit from development efforts, you should upgrade to a recent version from: ftp://ftp.berlios.de/pub/cdrecord/alpha/ This is where you may also find a complete list of all enhencements and bugfixes since September 2004, the origin of your fork Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) [EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: problems writing a large file to DVD+R Double Layer disk
[EMAIL PROTECTED] (Joerg Schilling) writes: >> I currently create an udf image with genisofs: > > What do you expect from using an unmaintained fork from a > 2.5 year old > version of mkisofs? Well, it may be 2.5 years old, but I managed to burn a 7.4 GB file with it. And I able to read this file in Linux and Windows... Cheers -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: problems writing a large file to DVD+R Double Layer disk
Dominique Dumont <[EMAIL PROTECTED]> wrote: > Kish Shen <[EMAIL PROTECTED]> writes: > > > I am trying to write a .ts file to a DVD+R Double Layer disk, so far > > without success. The file has a size of 4613734320. I issue the > > command: > > > > growisofs -Z /dev/sr1 -R -J pd > > I currently create an udf image with genisofs: What do you expect from using an unmaintained fork from a > 2.5 year old version of mkisofs? If you decouple yourself from the original software, you get decoupled from bugfixes and enhancements. Note that your old version misses 147 enhancements and bugfixes. Several dozens of bugs have been fixed that origin in the very early years of mkisofs (past 1993). Using old versions of software is never a good idea. Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) [EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: problems writing a large file to DVD+R Double Layer disk
Kish Shen <[EMAIL PROTECTED]> writes: > I am trying to write a .ts file to a DVD+R Double Layer disk, so far > without success. The file has a size of 4613734320. I issue the > command: > > growisofs -Z /dev/sr1 -R -J pd I currently create an udf image with genisofs: # -r : Rock ridge avec des perm uid et gid correct # -allow-limited-size: requis pour des fichiers > 2GB # -f: follow sym link (pas de symlink avec udf) genisoimage -udf -f -r -J -allow-limited-size -o ~/dvd.iso * Then I burn the image with growisofs -Z /dev/hda=dvd.iso When you mount the cd, be sure to mount it as udf: mount -t udf /dev/hda /media/cdrom0 You can probably create the image directly while running growisofs, but I have not tried yet. HTH -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: problems writing a large file to DVD+R Double Layer disk
On Tue 24 Apr 2007 02:31:53 NZST +1200, Thomas Schmitt wrote: > There are two old forms of for-loops: > for i ; do Current bash lists it as valid syntax, so it's not "old". > I cannot read from any man pages the correctness of > for i in ; do Read the man bash again. It's the in being present, but the item list being empty. > which seems to be somehow ignored by modern bash. Good thing too. As the loop is iterated for each item specified after in, and none are specified, the expected, pardon me, necesssary, result is to not loop at all. No surprise there. man bash even explicitly states: If the expansion of the items following in results in an empty list, no commands are executed, and the return status is 0. > I got an antiquity online (some SuSE 6.x): > $ uname -a > Linux * 2.2.13 #1 Mon Nov 8 15:51:29 CET 1999 i686 unknown > $ for i in ; do echo $i ; done > bash: syntax error near unexpected token `;' The syntax is valid, therefore the shell is buggy. It works fine on ksh, ash, pdksh on openSUSE 10.2. 2.2.13 allows to deduce the SUSE version to be 6.3. That in turn allows to look up the bash version to have been bash-2.03-24. (If you want to get package info of many historic SUSE versions, download the susegrep-data packages from my website.) Volker -- Volker Kuhlmann is list0570 with the domain in header http://volker.dnsalias.net/ Please do not CC list postings to me. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: autotools. was: problems writing a large file to DVD+R Double Layer disk
"Thomas Schmitt" <[EMAIL PROTECTED]> wrote: > Hi, > > > I understand all about writing portable scripts with autoconf, > > Could you have a look into our autotools configuration ? > The root directory can be inspected at > http://libburnia.pykix.org/browser/libburn/trunk > > Can you spot the reason why our configure gets that > empty loop list ? > A pointer to some autotools specs where i could learn > about the background would be best, of course. The best idea to check for shell portability is to make sure that you have the Bourne shell in /bin/sh for your tests. This will still not give you the kind of portability that allows you to compile on Next Step ;-) The Bourne Shell is free software and published under CDDL, so there is no problem to compile it even on Linux if you do not have a Solaris installation. Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) [EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: autotools. was: problems writing a large file to DVD+R Double Layer disk
"Thomas Schmitt" <[EMAIL PROTECTED]> wrote: > Hi, > > > > This shell silently ignores "for i in ; do something ; done". > > But this does not make the code portable > > For portability i now apply sed to the generated > ./configure. > > But as said, a functional port demands a hand-made > system adapter anyway. The problem is to use any "autoconf" newer than 2.13. After that time, portability has been given up for no reason. The schily makefilesystem uses the schily autoconf which is a largely enhanced GNU autoconf-2.13. I did not yet see any problem with my autoconf on any OS. Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) [EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
autotools. was: problems writing a large file to DVD+R Double Layer disk
Hi, > > This shell silently ignores "for i in ; do something ; done". > But this does not make the code portable For portability i now apply sed to the generated ./configure. But as said, a functional port demands a hand-made system adapter anyway. I can hardly expect autotools to know about the system interfaces for SCSI command transport. Have a nice day :) Thomas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
autotools. was: problems writing a large file to DVD+R Double Layer disk
Hi, > I understand all about writing portable scripts with autoconf, Could you have a look into our autotools configuration ? The root directory can be inspected at http://libburnia.pykix.org/browser/libburn/trunk Can you spot the reason why our configure gets that empty loop list ? A pointer to some autotools specs where i could learn about the background would be best, of course. I am quite sure one can avoid that empty loop list by some variable ... but by which one ? So for now i just run sed -e 's/^for ac_header in$/test -z 1 \&\& for ac_header in dummy/' to get a more portable ./configure. The reasons why we still use autotools although we are not really in control of it are simple: The popularity of "./configure ; make" and the fact that it reduces the complex work of build configuration to fixing a few simple bugs. So for now all its little sins did not count enough to sincerely strive for a change. But there are days like yesterday where i at least dream of shell scripts which are not larger than a few hundred lines. Have a nice day :) Thomas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: problems writing a large file to DVD+R Double Layer disk
"Thomas Schmitt" <[EMAIL PROTECTED]> wrote: > $ bash --version > GNU bash, version 2.05b.0(1)-release (i586-suse-linux) > Copyright (C) 2002 Free Software Foundation, Inc. > $ uname -a > Linux * 2.4.21-215-athlon #1 Tue Apr 27 00:53:38 UTC 2004 i686 athlon i386 > GNU/Linux > > This shell silently ignores "for i in ; do something ; done". But this does not make the code portable Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) [EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: problems writing a large file to DVD+R Double Layer disk
Hi, > Which version of bash is that? I can't reproduce that result at all. The SuSE 6.x is offline. But the result from the younger SuSE 7.2 from where i know the problem with libburn-0.2 should be more interesting anyway: $ bash --version GNU bash, version 2.05.0(1)-release (i386-suse-linux) Copyright 2000 Free Software Foundation, Inc. $ echo $BASH_VERSION 2.05.0(1)-release $ uname -a Linux * 2.4.4-4GB #1 Wed May 16 00:37:55 GMT 2001 i686 unknown This shell shows the same results and error messages as the older system. I.e. it dislikes "for i in ; do something ; done" The next newer one i can get on is a SuSE 9.0 which says: $ bash --version GNU bash, version 2.05b.0(1)-release (i586-suse-linux) Copyright (C) 2002 Free Software Foundation, Inc. $ uname -a Linux * 2.4.21-215-athlon #1 Tue Apr 27 00:53:38 UTC 2004 i686 athlon i386 GNU/Linux This shell silently ignores "for i in ; do something ; done". Have a nice day :) Thomas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: problems writing a large file to DVD+R Double Layer disk
On Mon, Apr 23, 2007 at 04:31:53PM +0200, Thomas Schmitt wrote: > I got an antiquity online (some SuSE 6.x): > $ uname -a > Linux * 2.2.13 #1 Mon Nov 8 15:51:29 CET 1999 i686 unknown > $ for i in ; do echo $i ; done > bash: syntax error near unexpected token `;' > $ for i in > bash: syntax error near unexpected token `in' > $ for i in 1 > > do echo $i > > done > 1 > $ Which version of bash is that? I can't reproduce that result at all. svr1:~$ cat /etc/redhat-release Red Hat Linux release 5.2 (Apollo) svr1:~$ echo $BASH_VERSION 1.14.7(1) svr1:~$ for x in > do > echo > done svr1:~$ for i in ; do echo $i ; done svr1:~$ I'm not saying that the syntax is valid -- just that I can't find ANY system that can reproduce this error. I understand all about writing portable scripts with autoconf, but without a way to TEST various things, writing portable code becomes a whole lot harder. My oldest bash (1.14.7) and dash (0.5.2) both accept it as valid. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: problems writing a large file to DVD+R Double Layer disk
Greg Wooledge <[EMAIL PROTECTED]> wrote: > On Sun, Apr 22, 2007 at 12:17:57PM +0200, Thomas Schmitt wrote: > > I'll have to correct that via sed. > >test -z 1 && for ac_header in dummy > > should be a single line repair of > >for ac_header in > > I don't understand this "repair". test -z 1 will always return "false", > because "1" is not a zero-length string. So you might as well just comment > out the "for ac_header in dummy" line altogether. > > As far as the original code goes, I'd have to see the entire "for" > loop to know what the actual problem is. Since I don't have access to > a Solaris system (with its ancient pre-POSIX /bin/sh), and since dash Sorry, you do not seem to understand POSIX :-( While Solaris is fully POSIX-1-2001 compliant, Linux is not POSIX is a _source_ standard that does not deal with path names at all. POSIX does not care about what you get when you type /bin/sh, POSIX grants you that if you call: PATH=`getconf PATH` sh you get a POSIX shell. An autoconf utility that depends on bash instead of the Bourne shell is not portable. Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) [EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: problems writing a large file to DVD+R Double Layer disk
Hi, me: > >test -z 1 && for ac_header in dummy Greg Wooledge: > I don't understand this "repair". test -z 1 will always return "false", > because "1" is not a zero-length string. So you might as well just comment > out the "for ac_header in dummy" line altogether. If i disable the "for" line then the shell will ask me what i mean with "do". Like: bash: syntax error near unexpected token `do' But if i correct it syntactically so it matches man bash "for name [ in word ] ; do list ; done" and then prevent it from being executed then i hope to achieve the same effect which the bash implementation on Linux produces since about 6 years. The youngest Linux i could find which openly dislikes for ac_header in was a SuSE 7.2 from about 2001. Nevertheless, you do not need a Solaris to see the produce of autotools which does not comply to man bash resp. S.R. Bourne's original description of the shell. The ./configure script gets produced by autotools command ./bootstrap on Linux systems and it currently contains the incorrect gesture. There are two old forms of for-loops: for i ; do for i in item ... item ; do I cannot read from any man pages the correctness of for i in ; do which seems to be somehow ignored by modern bash. Nice gesture. But lets Joerg Schilling think i'd did not care for bugs. Old Linux fails, Solaris fails. This "for" is not portable. autotools claims to produce portable releases. That's why we have 600+ kB of ./configure shell code, after all. I don't know wether Joerg downloaded from our SVN and applied an own ./bootstrap or wether he unpacked a release tarball. About autotools on Solaris i can't say anything. But autotools on Linux produces a problematic ./configure . Well, it does not matter much. libburn won't compile on Solaris unless there would be a Linux sg emulator. With /dev/sg and ioctls and all. (Is there ?) Usually one has to program an adapter to the operating systems's lowlevel SCSI facilities. This remains handwork and demands some system knowledge. > It seems more likely that there's really some sort of mistake *before* > the "for" loop, which would mean tracking backward through 2 lines > of ./configure code to try to find it... good luck with that. I got an antiquity online (some SuSE 6.x): $ uname -a Linux * 2.2.13 #1 Mon Nov 8 15:51:29 CET 1999 i686 unknown $ for i in ; do echo $i ; done bash: syntax error near unexpected token `;' $ for i in bash: syntax error near unexpected token `in' $ for i in 1 > do echo $i > done 1 $ Have a nice day :) Thomas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: problems writing a large file to DVD+R Double Layer disk
On Sun, Apr 22, 2007 at 12:17:57PM +0200, Thomas Schmitt wrote: > I'll have to correct that via sed. >test -z 1 && for ac_header in dummy > should be a single line repair of >for ac_header in I don't understand this "repair". test -z 1 will always return "false", because "1" is not a zero-length string. So you might as well just comment out the "for ac_header in dummy" line altogether. As far as the original code goes, I'd have to see the entire "for" loop to know what the actual problem is. Since I don't have access to a Solaris system (with its ancient pre-POSIX /bin/sh), and since dash gives me no errors when I run for ac_header in do echo done that means I don't have any systems that are prehistoric enough to duplicate the bug -- assuming this "for" loop really is the bug at all. It seems more likely that there's really some sort of mistake *before* the "for" loop, which would mean tracking backward through 2 lines of ./configure code to try to find it... good luck with that. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: problems writing a large file to DVD+R Double Layer disk
Hi, > The fact that som Linux people are working against the usability of Linux > makes you believe that there is a need for a second source? I want to be able to follow their moves by having own souvereignty over what is going on under my backup program. > What really would be needed is more people who dare to tell > those people that they are working against linux > and cause unneeded effort at my side. cdrskin is not a pedagogical project. > > I.e. no way to write a data stream of unpredicted length. > it does not even work in packet mode in DVD-R/RW. The appearent success with growisofs and cdrskin on various DVD burners would need an explanation then. About all DVDs created by the users of my backup tool are written on-the-fly. Afterwards the users check them by a MD5 checksum of the whole image. It verifies. That happens since 2003. Another empiric mountiain are all those users of growisofs who do not have problems with its basic operation (most use cases where option -dvd-compat is omitted). The only way to make DVD-RW Packet fail is to _fast_ blank a DVD-RW. Such media seem restricted to DAO. > > > ./configure: line 21233: `for ac_header in' > > Is this from cdrskin-0.3.4.pl00.tar.gz ? > I did take this from your scdbackup page. Sigh. There is really one of those again in our ./configure. Courtesy of autotools. Unnoticed because bash since years silently ignores this incorrect gesture. I only wonder why you see it in line 21233. My ./configure has "only" 20776 lines. I'll have to correct that via sed. test -z 1 && for ac_header in dummy should be a single line repair of for ac_header in Thanks for finding it. Sorry for my disbelieving. > I don't believe that > there is a will to fix bugs in this software. Not meant as an excuse: It is not a lack of will but a lack of control over autotools. We have to fill some cryptic variables and then it produces some 600+ kB of ./configure script via the ./bootstrap command. This problem had been repaired months ago and sneaked back in by some new little adjustment. autotools is accepted and it happens to work in most cases. I am sure that i could replace it for libburn on Linux by a simple shell script within two hours. So for now it is only embarrassing and not crux of the matter. As said, it is an accepted build tool (whyever) and thus an interface to people who maintain binary software packages. As long as their shell tolerates it ... (sigh again). > > Whatever, there is no system adapter for Solaris yet. > So why do you put effort in nonportable sofware? libburn is intended to be portable. But of course it needs a matching system adapter which implements the interface that is defined for interactions of libburn and the peculiarities of an operating system. It is ready to be ported if there is a user willing to test and if there are specs about how to achieve some fundamental gestures like enumerating potential drive addresses, obtaining SCSI address parameters or performing a SCSI command transaction. Best would be of course if such a user has the necessary system knowledge to help with the adapter's implementation. > There are at least twice as many Solaris users as users for > all *BSDs togther. Shouldn't they get access to libburn then ? You would have the skills to allow them the choice. > As I told, cdrecord is truely portable and there is a > lot of possible things that could help... On the levels of MMC or Linux system adapter ? Let me know some details. > > unpredicted track size DVD+R Packet, > > -multi > I will check whether it makes sense with DVD+ For -tao i just leave out the RESERVE TRACK command. For -multi i use with CLOSE TRACK SESSION Close Function 010b rather than Close Function 101b. DVD+R is the only media for which i found tutorial info in MMC-5. See 4.3.6.2.2 "The Hosts Perspective". > It wuld make sense > to have help with creating rpm and deb packets too. (Cough.) Packaging is not among my sports. But i am checking for new cdrtools every now and then (ftp://ftp.berlios.de/pub/cdrecord/alpha is not responding right now. I'll retry.) > A program that does not work on Solaris is no competition for me ;-) Help to make it one. :) > Sorry, but growisofs is not what I would call userfriendly. The main use case is. >From man growisofs, EXAMPLES: " growisofs -Z /dev/dvd -R -J /some/files To append more data to same DVD: growisofs -M /dev/dvd -R -J /more/files " One can hardly make it more concise. I admit it becomes more demanding if you want to make use of its fundamental DVD writing capabilities. -use-the-force-luke is powerful but you have to read-the-source-luke in order to understand. -dvd-compat is another focus of user riddling. Have a nice day :) Thomas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: problems writing a large file to DVD+R Double Layer disk
"Thomas Schmitt" <[EMAIL PROTECTED]> wrote: > Hi, > > me: > > > My original motivation was a clash between you and some > > > of your critics in november or december 2005. > > Joerg: > > Could you please explain why you did believe the FUD spread by > > malicious people instead of asking me? > > It is not that i take sides in those quarrels. > I used cdrecord with CD for years and trust > its technical and your personal integrity enough > to run it setuid root. So in this case I would asume that you also trust me with respect to OSS. I am working on OSS since a long time (more than 20 years) and this alone should be sufficient to know that I will not change my mind You should however not trust people like Mr. Bloch who constantly spread lies, started to work on OSS very recently and do noe look like they did got the spirit of OSS already. > But i noticed the ongoing rift between you and the > people who decide over the development of Linux. > Since i'm comitted to stay with Linux i felt the > need for a second source of the services usually > provided by cdrecord. > That was mainly about CD data writing at that time. This is a very strange conclusion! The fact that som Linux people are working against the usability of Linux makes you believe that there is a need for a second source? What really would be needed is more people who dare to tell those people that they are working against linux and cause unneeded effort at my side. > > Well, cdrecordwrites DVDs since 1998, what is your problem? > > Not to have -tao. > I.e. no way to write a data stream of unpredicted length. This may work with DVD+R under some conditions, it does not even work in packet mode in DVD-R/RW. > > Reading your README, you seem to claim being interested > > in the spirit of OSS. > > Yep. The peaceful, tolerant and cooperative variation. > > > > ./configure: line 21233: syntax error near unexpected token `in' > > ./configure: line 21233: `for ac_header in' > > Is this from cdrskin-0.3.4.pl00.tar.gz resp. libburn-0.3.4.tar.gz > resp. from the 0.3.5 versions ? I did take this from your scdbackup page. Note that I did report this bug _many_ times before and I don't believe that there is a will to fix bugs in this software. > Whatever, there is no system adapter for Solaris yet. > You'd probably end up with the Linux adapter and the > compiler will probably fail over missing definitions. So why do you put effort in nonportable sofware? > > > checking dynamic linker characteristics... solaris2.9 ld.so > > The spirit of OSS is creating software that compiles and works on as many > > platforms as possible. > > Would you be interested to help me with a Solaris port ? > > The operating system references and especially the > SCSI command transport are encapsulated in files > separate from the main functionality. > Currently there is a Linux and a FreeBSD implementation > of this OS adapter set. There are at least twice as many Solaris users as users for all *BSDs togther. > > You seem to be one of the people who are not confused by the FUD from > > the people who like to harm me and my projects. > > I stay strictly neutral in the historical person-to-person > aspects and i try to keep a clear view on technical aspects. It is sufficient to stay neutral in order to not get catched by the FUD from Mr. Bloch ;-) > > Why do you contribute to a > > nonportable project instead of contributing to a project > > that is in the spirot of OSS? > > Joerg, what shall i contribute to cdrecord ? As I told, cdrecord is truely portable and there is a lot of possible things that could help... > I told you what i learned about DVD write strategies like > unpredicted track size DVD-R[W] Packet (Incremental), > unpredicted track size DVD+R Packet, > unpredicted track size on overwriteable DVR-RW, DVD+RW, DVD-RAM. > I told you what i learned about true multi-session on DVD-R[W] > and DVD+R. Ready for mkisofs -C -M and for Linux mount(8). > All covered by MMC-5. No proprietary commands or heuristic stunts. > All well matching the traditional -multi -data -tao behavior with CD. As I did write above, this definitely does not work reliably with DVD-, I did find a lot of problems while implementing multi border. > It is written down in the libburnia doc/cookbook.txt . > Ask for any clarifications or point me to any mistake. As I see problems at least with DVD-RW, I will not implement this with DVD- and I will check whether it makes sense with DVD+ Note that I am interested in reliable software and thus think a bit different from people who implement hacks. > I doubt that i could help much with implementing those > features into cdrecord. I can do Linux tests for you. Recently, I did write a Schily makefiles extension to auto create Svr4 packets after the sources have been compiled. It wuld make sense to have help with creating rpm and deb packets too. Note that many people seem to be unable or unwilling to install binari
Re: problems writing a large file to DVD+R Double Layer disk
Hi, me: > > My original motivation was a clash between you and some > > of your critics in november or december 2005. Joerg: > Could you please explain why you did believe the FUD spread by > malicious people instead of asking me? It is not that i take sides in those quarrels. I used cdrecord with CD for years and trust its technical and your personal integrity enough to run it setuid root. But i noticed the ongoing rift between you and the people who decide over the development of Linux. Since i'm comitted to stay with Linux i felt the need for a second source of the services usually provided by cdrecord. That was mainly about CD data writing at that time. > Well, cdrecordwrites DVDs since 1998, what is your problem? Not to have -tao. I.e. no way to write a data stream of unpredicted length. > Reading your README, you seem to claim being interested > in the spirit of OSS. Yep. The peaceful, tolerant and cooperative variation. > ./configure: line 21233: syntax error near unexpected token `in' > ./configure: line 21233: `for ac_header in' Is this from cdrskin-0.3.4.pl00.tar.gz resp. libburn-0.3.4.tar.gz resp. from the 0.3.5 versions ? I know this error from the libburn-0.2 of icculus.org. It is supposed to be corrected already in the CVS version there. "Stable" cdrskin is distributed as http://scdbackup.sourceforge.net/cdrskin-0.3.4.pl00.tar.gz or http://libburnia-download.pykix.org/releases/libburn-0.3.4.tar.gz Development version 0.3.5 is best fetched from our SVN svn co http://libburnia-svn.pykix.org/libburn/trunk libburn_pykix Whatever, there is no system adapter for Solaris yet. You'd probably end up with the Linux adapter and the compiler will probably fail over missing definitions. > checking dynamic linker characteristics... solaris2.9 ld.so > The spirit of OSS is creating software that compiles and works on as many > platforms as possible. Would you be interested to help me with a Solaris port ? The operating system references and especially the SCSI command transport are encapsulated in files separate from the main functionality. Currently there is a Linux and a FreeBSD implementation of this OS adapter set. Please read the first 60 lines of libburn/sg-linux.c to get an overview. > You seem to be one of the people who are not confused by the FUD from > the people who like to harm me and my projects. I stay strictly neutral in the historical person-to-person aspects and i try to keep a clear view on technical aspects. > Why do you contribute to a > nonportable project instead of contributing to a project > that is in the spirot of OSS? Joerg, what shall i contribute to cdrecord ? I told you what i learned about DVD write strategies like unpredicted track size DVD-R[W] Packet (Incremental), unpredicted track size DVD+R Packet, unpredicted track size on overwriteable DVR-RW, DVD+RW, DVD-RAM. I told you what i learned about true multi-session on DVD-R[W] and DVD+R. Ready for mkisofs -C -M and for Linux mount(8). All covered by MMC-5. No proprietary commands or heuristic stunts. All well matching the traditional -multi -data -tao behavior with CD. It is written down in the libburnia doc/cookbook.txt . Ask for any clarifications or point me to any mistake. I doubt that i could help much with implementing those features into cdrecord. I can do Linux tests for you. There is no harm in having two programs for the task of CD burning. After all we have no reason to compete other than in a friendly and helpful way. With DVD, there are two programs since quite a while. And wether you accept it or not, for the task of growing an ISO file system on a DVD, growisofs is unsurpassed. Easy to operate and very versatile with media. cdrskin's ecological niche with DVD is currently to provide similar MMC features as growisofs but with the usage concepts like of cdrecord with CD. This comes in very handy if you want to write non-ISO formats or if you want to use it with a cdrecord frontend program. In its combination of CD and DVD capabilities, cdrskin became a compact little all-in-one burn program meanwhile. I'm proud of it. It is entirely up to us how our projects coexist. There are no external forces which can make us enemies. I hope to have expressed my respect for your work often and clear enough. Here and on http://scdbackup.sourceforge.net/cdrskin_eng.html Especially in the last text paragraph there. Have a nice day :) Thomas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: problems writing a large file to DVD+R Double Layer disk
[EMAIL PROTECTED] wrote: > > BTW: it would be intersting to knoe why several people did start own > > CD/DVD writing software project just to learn what they could learn from > > reading my software instead of helping with cdrtools. > > My original motivation was a clash between you and some > of your critics in november or december 2005. I began to > fear for the CD burning support in Linux and googled for > background info in order to write a petition to LKML. > My plan was to ask for some simple Linux builtin CD support. > Like with DVD+RW or DVD-RAM. Could you please explain why you did believe the FUD spread by malicious people instead of asking me? > But i stumbled over libburn and could enhance it to fulfill my > CD needs. Now if you have a thing that burns CD then the wish > to burn DVD is quite natural. > It is an interesting topic and i learned a lot by doing it. Well, cdrecordwrites DVDs since 1998, what is your problem? Why did you contribute to a project that stil is completely non-portable and aborts already in "configure": checking whether the g77 linker (/usr/ccs/bin/ld) supports shared libraries... yes checking dynamic linker characteristics... solaris2.9 ld.so checking how to hardcode library paths into programs... immediate checking for a BSD-compatible install... /opt/sfw/bin/ginstall -c ./configure: line 21233: syntax error near unexpected token `in' ./configure: line 21233: `for ac_header in' Reading your README, you seem to claim being interested in the spirit of OSS. The spirit of OSS is creating software that compiles and works on as many platforms as possible. This is obviously true for cdrecord but unfortunately not true for libburn. You seem to be one of the people who are not confused by the FUD from the people who like to harm me and my projects. Why do you contribute to a nonportable project instead of contributing to a project that is in the spirot of OSS? Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) [EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: problems writing a large file to DVD+R Double Layer disk
Kish Shen wrote: Hi, [I sent this message several hours ago from another email address, but it has not appear yet, so I am trying again with a different e-mail address] I am trying to write a .ts file to a DVD+R Double Layer disk, so far without success. The file has a size of 4613734320. I issue the command: growisofs -Z /dev/sr1 -R -J pd where pd is where my files are. I get the message: mkisofs: Value too large for defined data type. File pd/ts is too large - ignoring and the file is not written. This is with growisofs version 7.0, and mkisofs 2.01.01a24 I updated my growisofs and mkisofs to these versions because those that came with my Linux (growisofs: version 5.17, mkisofs: 2.01a27) does not recognise the DVD+R DL media: linux:/home/kish # growisofs -Z /dev/sr1 -R -J pd :-( /dev/sr1: media is not recognized as recordable DVD: 2B My system configuration is: OS: SuSe Linux 9.1, with kernel 2.6.11.4 DVD Writer: LG GSA 5163D For now, I just want to write the file as a data file to the disk, so I am not worried about DVD compatibility. Thanks in advance for any help/information on how I can write the file to the disk! Cheers, Kish If you are concerned with backing up the data in a way which allows recovery, I can tell you how to do that. I think the portability of any solution to have that file on an optical media is suspect, and may not work in some cases. Solution #1: break into smaller files you can recover as one big file and write to disk: $ split -b 50 my_huge_file hugefile. $ mv my_huge_file some_other_dir_for_safety/ $ growisofs -Z /dev/scd0 -R -J . To recover, mount the disk and: cat /mnt/cdrom/hugefile.?? >file_on_disk Solution #2 - you can play the file from DVD: * Create an empty file of 4400MB (dd if=/dev/zero of=bigfile bs=1024k count=4400) * Loopback mount the file (losetup /dev/loop0 bigfile) * Put an ext2 filesystem on the device (mke2fs -b4096 -N2000 bigfile) * Mount the device as root (mount /dev/loop0 /mnt/temp) * Copy all of the data to the loop mount (cp -r pr /mnt/temp) * Unmount the loop device (umount /dev/loop0) * Now burn the disk, ext2 will hold a 4GB file (growisofs -Z /dev/scd0=bigfile) Do note, no option to growisofs, just the filesystem image. The only issue with the 2nd method is that you can only mount the DVD on a Linux system. -- bill davidsen <[EMAIL PROTECTED]> CTO TMR Associates, Inc Doing interesting things with small computers since 1979
Re: problems writing a large file to DVD+R Double Layer disk
Joerg Schilling wrote: Kish Shen <[EMAIL PROTECTED]> wrote: What is a .ts file? Why do you need it? This is a file I downloaded, and I think .ts is some sort of container format for video (mplayer is able to play it direct). I am trying to archive it so I can remove it from my HD -- I don't really have enough room to keep it around my HD There is a standard that says that no single video file may be > (1 GB - 2k). I assume you mean a standard DVD format disk. By use of growisofs I have to think he wants to write to a disk in ISO format using mkisofs, just to preserve the data. I'm posting a suggestion on that issue in a separate message. In about 2 months, there will be a new version that supports files up to 8 TB. If you use Linux, you then will need to check whether the Linux kernel correctly supports multi-extent files. I will add the needed multi-extent file support to OpenSolaris at the same time That would be great! Would I be able to append to the +R double layer disk that I have written to with a previous version of growisofs? I cannot speak for growisofs. I thought you did see an error message from growisofs. Once cdrecord will support multi-border for DVD+R, it will be done in the official way, it depends on whether growisofs does the same. If you have problems with double layer disks, better use the cdrecord that comes with cdrtools-2.01.01a24. Note that you need to call cdrecord as root or install it suid root. I will take a look at this. I assume I will need to use a new disk to do this, and cannot append the file to the double layer disk I have already partially written to using growisofs. With the current features of cdrecord, you will need a new empty DVD+R/DL. -- Bill Davidsen <[EMAIL PROTECTED]> "We have more to fear from the bungling of the incompetent than from the machinations of the wicked." - from Slashdot -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: problems writing a large file to DVD+R Double Layer disk
Hi, > Please show the cdrecord -v -minfo output for such a disk. Re-reading your mail after my first answer i realize that you might be interested in the output from appendable and closed multi-session DVD-RW as well. Have a nice day :) Thomas One session and appendable after dd if=/dev/zero bs=1M count=500 | cdrskin -v dev=0,0,0 -multi - $ cdrecord -v dev=0,0,0 -minfo Cdrecord-ProDVD-Clone 2.01.01a23 (i686-pc-linux-gnu) Copyright (C) 1995-2006 Jörg Schilling TOC Type: 1 = CD-ROM scsidev: '0,0,0' scsibus: 0 target: 0 lun: 0 Linux sg driver version: 3.1.25 Using libscg version 'schily-0.9'. SCSI buffer size: 64512 atapi: 1 Device type: Removable CD-ROM Version: 0 Response Format: 2 Capabilities : Vendor_info: '_NEC' Identifikation : 'DVD_RW ND-4570A ' Revision : '1.02' Device seems to be: Generic mmc2 DVD-R/DVD-RW/DVD-RAM. Current: DVD-RW sequential overwrite Profile: DVD+R/DL Profile: DVD+R Profile: DVD+RW Profile: DVD-R/DL sequential recording Profile: DVD-RW sequential overwrite (current) Profile: DVD-RW restricted overwrite (current) Profile: DVD-RAM Profile: DVD-R sequential recording Profile: DVD-ROM Profile: CD-RW Profile: CD-R Profile: CD-ROM Profile: Removable Disk Using generic SCSI-3/mmc-2 DVD-R/DVD-RW/DVD-RAM driver (mmc_dvd). Driver flags : DVD MMC-3 SWABAUDIO BURNFREE Supported modes: PACKET SAO Drive buf size : 1769472 = 1728 KB Current Secsize: 2048 book type: DVD-RW, Version > 1.1x -> 1.2 (3.3) disc size: 120mm (0) maximum rate:Not specified (15) number of layers:1 track path: Parallel Track Path (0) layer type: Rewritable Area (2) linear density: 0.267 µm/bit (0) track density: 0.74 µm/track (0) phys start: 196608 (0x3) phys end:452607 end layer 0: 0 bca: 0 phys size:...256000 copyr prot type: 0 region mgt info: 0 cpm: 0 cgms:0 last rma sector: 0 application code:2 physical code: 214 last rec address:16621272 part v./ext code:3/1 ind wr. power: 0 wavelength code: 0 write str. code: 00 00 00 00 Manufacturer: 'MCC 01RW4X ' rzone size: 36 rzone number: 1 border number: 1 ljrs: 0 track mode: 4 copy: 0 damage: 0 reserved track: 0 blank: 0 incremental: 1 fp: 0 data mode: 1 lra valid: 1 nwa valid: 0 rzone start:0 next wr addr: 0 free blocks:0 blocking factor:16 rzone size: 256000 last recorded addr: 255999 Capacity Blklen/Sparesz. Type 256000 2048 Formatted Media 2297888 2048 Reserved (0) 2297888 16 Reserved (0) 2297888 16 Reserved (0) WARNING: Phys disk size 256000 differs from rzone size 0! Prerecorded disk? WARNING: Phys start: 196608 Phys end 452607 Disk Is erasable data type:standard disk status: incomplete/appendable session status: empty BG format status: none first track: 1 number of sessions: 2 first track in last sess: 2 last track in last sess: 2 Disk Is unrestricted Disk type: DVD, HD-DVD or BD Track Sess Type Start Addr End Addr Size == 1 1 Data 0 255999 256000 -1 2 2 Blank 284688 22978872013200 28688 Last session start address: 0 Last session leadout start address: 256000 Next writable address: 284688 Remaining writable size:2013200 Second session, still appendable after another dd if=/dev/zero bs=1M count=500 | cdrskin -v dev=0,0,0 -multi - $ cdrecord -v dev=0,0,0 -minfo Cdrecord-ProDVD-Clone 2.01.01a23 (i686-pc-linux-gnu) Copyright (C) 1995-2006 Jörg Schilling TOC Type: 1 = CD-ROM scsidev: '0,0,0' scsibus: 0 target: 0 lun: 0 Linux sg driver version: 3.1.25 Using libscg version 'schily-0.9'. SCSI buffer size: 64512 atapi: 1 Device type: Removable CD-ROM Version: 0 Response Format: 2 Capabilities : Vendor_info: '_NEC' Identifikation : 'DVD_RW ND-4570A ' Revision : '1.02' Device seems to be: Generic mmc2 DVD-R/DVD-RW/DVD-RAM. Current: DVD-RW sequential overwrite Profile: DVD+R/DL Profile: DVD+R Profile: DVD+RW Profile: DVD-R/DL sequential recording Profile: DVD-RW sequential overwrite (current) Profile: DVD-RW restricted overwrite (current) Profile: DVD-RAM Profile: DVD-R sequential recording Profile: DVD-ROM Profile: CD-RW Profile: CD-R Profile: CD-ROM Profile: Removable Disk Using generic SCSI-3/mmc-2 DVD-R/DVD-RW/DVD-RAM driver (mmc_dvd). Driver flags : DVD MMC-3 SWABAUDIO BURNFREE Supported modes: P
Re: problems writing a large file to DVD+R Double Layer disk
Hi, Joerg Schilling: > I would not believe that this is true > Please show the cdrecord -v -minfo output for such a disk. See post scriptum. > If the size is not needed in advance in this mode, then grosisofa > _definitely_ does not write in the best mode. Well, what is best ? It works in both modes. Option -dvd-compat allows to control this. There seem to be issues with old hardware, especially DVD video players for the livingroom. In that case it is advised to use DAO (growisofs -dvd-compat , cdrskin -sao ). I myself have no substantial reports about any trouble with "-tao" recorded DVD. Possibly there are not enough users of cdrskin yet. Meanwhile i dare to finalize DVD+R although growisofs code warns not to do so. For me it works. For the rest we'll see. me: > > Do i miss something ? Is there a way to use > > Incremental Streaming on DVD-R[W] via cdrecord ? > > It would come in very handy for scdbackup. Joerg: > There is no such mode, what are you talking about? MMC-5: "5.3.11 Incremental Streaming Writable Feature (0021h) The Incremental Streaming Writable Feature identifies a Drive that is able to write data to a contiguous region, and is able to append data to a limited number of locations on the media. On CD media, this is known as packet recording, on DVD and HD DVD media it is known as Incremental Recording, and on a BD-R disc it is known as SRM recording. The Feature descriptor response data is defined in Table 112." All my DVD drives offer this feature with unused DVD-R[W], with appendable DVD-R[W] and with DVD-RW which were blanked fully (e.g. cdrecord blank=all). > BTW: it would be intersting to knoe why several people did start own > CD/DVD writing software project just to learn what they could learn from > reading my software instead of helping with cdrtools. My original motivation was a clash between you and some of your critics in november or december 2005. I began to fear for the CD burning support in Linux and googled for background info in order to write a petition to LKML. My plan was to ask for some simple Linux builtin CD support. Like with DVD+RW or DVD-RAM. But i stumbled over libburn and could enhance it to fulfill my CD needs. Now if you have a thing that burns CD then the wish to burn DVD is quite natural. It is an interesting topic and i learned a lot by doing it. I did not study the CD related code of cdrecord because i wanted to achieve a technically independent implementation of CD burning and because there were already enough projects which maintained programs derived from cdrecord. Nevertheless, i raise my hat in front of your merits. Your program cdrecord guided me through that endeavor by setting the standard to strive for. Many bytes have been copied from its message output. Another reason was that libburn already had CD SAO capabilities and offered enough hints for finding the necessary info in the SCSI specs. As for DVD: Joerg, you are too stubborn with them. Andy Polyakov demonstrated in growisofs that there are more capabilities in DVD than cdrecord is willing to allow its users. His tool dvd+rw-mediainfo tells in the headlines of the info paragraphs what MMC command was used to retrieve. That is very helpful for the purpose of learning. To read the source of dvd+rw-tools is less comfortable. Nevertheless the SCSI commands are clearly recognizable and commented. So it is not too hard to find the decisive spots in the specs. I have to thank Andy a lot for this rich dumpling of info. As a contribution to overall knowledge i compiled my findings in doc/cookbook.txt of cdrskin. It contains summaries of how to deal with the various types of media. There are lots of pointers into MMC-5 specs to justify my statements and to provide further details. Have a nice day :) Thomas - PS: Info output with a fully blanked DVD-RW by cdrecord, dvd+rw-tools, and libburn's demo application telltoc (which comes with cdrskin). $ cdrecord -v dev=0,0,0 -minfo Cdrecord-ProDVD-Clone 2.01.01a23 (i686-pc-linux-gnu) Copyright (C) 1995-2006 Jörg Schilling TOC Type: 1 = CD-ROM scsidev: '0,0,0' scsibus: 0 target: 0 lun: 0 Linux sg driver version: 3.1.25 Using libscg version 'schily-0.9'. SCSI buffer size: 64512 atapi: 1 Device type: Removable CD-ROM Version: 0 Response Format: 2 Capabilities : Vendor_info: '_NEC' Identifikation : 'DVD_RW ND-4570A ' Revision : '1.02' Device seems to be: Generic mmc2 DVD-R/DVD-RW/DVD-RAM. Current: DVD-RW sequential overwrite Profile: DVD+R/DL Profile: DVD+R Profile: DVD+RW Profile: DVD-R/DL sequential recording Profile: DVD-RW sequential overwrite (current) Profile: DVD-RW restricted overwrite (current) Profile: DVD-RAM Profile: DVD-R sequential recording Profile: DVD-ROM Profile: CD-RW Profile: CD-R Profile: CD-ROM Profile: Removable Disk Using generic SCSI-3/mmc-2 DVD-R/DVD-RW/DVD-RAM driver (mmc_dvd). Driver flags
Re: problems writing a large file to DVD+R Double Layer disk
[EMAIL PROTECTED] wrote: > Hi, > > Joerg Schilling: > > The same could be said for e.g. growisofs. Growisofs artificially > > limits the write mode for DVDs to what DVD+R/RW allows ignoring the > > features of DVD-R/RW. > > Indeed ? It writes blank DVD-R[W] as DAO with option -dvd-compat > and it writes them as Incremental Streaming (32 kB fixed packet) > elsewise. Reasons not to use Incremental Streaming with DVD-RW: > - they are formatted to Restricted Overwrite, > - they are fast-blanked, which allows DAO only. > Usually the media is left appendable after Incremental Streaming, > but on appendable DVD-RW growisofs -dvd-compat causes closing > after the session is written. I would not believe that this is true Please show the cdrecord -v -minfo output for such a disk. If the size is not needed in advance in this mode, then grosisofa _definitely_ does not write in the best mode. > > The size is only "unneded" > > in case you use the less compatible packet writing mode. Cdrecord > > by default implements the write mode with the best read-compatibility. > > Do i miss something ? Is there a way to use > Incremental Streaming on DVD-R[W] via cdrecord ? > It would come in very handy for scdbackup. There is no such mode, what are you talking about? Cdrecord implements the most important things first. If there was less FUD from some bad guys at Debian, I did have more time to code but note that I write a lot of OSS software and I prefer to work on _new_ and important technology. The most important new technology currently is libfind which causes much more work than you might imagine. Note that I did write a "find" command from scratch in one week, but I am spending already more than 50x the amount of tim in making it a real universal library that works inside star, mkisofs and as builtin inside "bsh" and "ksh93". BTW: it would be intersting to knoe why several people did start own CD/DVD writing software project just to learn what they could learn from reading my software instead of helping with cdrtools. Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) [EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: problems writing a large file to DVD+R Double Layer disk
Hi, Joerg Schilling: > The same could be said for e.g. growisofs. Growisofs artificially > limits the write mode for DVDs to what DVD+R/RW allows ignoring the > features of DVD-R/RW. Indeed ? It writes blank DVD-R[W] as DAO with option -dvd-compat and it writes them as Incremental Streaming (32 kB fixed packet) elsewise. Reasons not to use Incremental Streaming with DVD-RW: - they are formatted to Restricted Overwrite, - they are fast-blanked, which allows DAO only. Usually the media is left appendable after Incremental Streaming, but on appendable DVD-RW growisofs -dvd-compat causes closing after the session is written. > The size is only "unneded" > in case you use the less compatible packet writing mode. Cdrecord > by default implements the write mode with the best read-compatibility. Do i miss something ? Is there a way to use Incremental Streaming on DVD-R[W] via cdrecord ? It would come in very handy for scdbackup. Don't get me wrong. I am sincerely interested in learning about cdrecord's capabilities. I just tested with cdrecord-2.01.01a23 on a blank DVD-RW dd if=/dev/zero bs=1M count=500 | cdrecord -v dev=0,0,0 -packet - and got cdrecord: Drive does not support TAO recording. cdrecord: Illegal write mode for this drive. The same with dd if=/dev/zero bs=1M count=500 | cdrecord -v dev=0,0,0 -tao - With dd if=/dev/zero bs=1M count=500 | cdrecord -v dev=0,0,0 - i get cdrecord: Track 1 has unknown length. cdrecord: Use tsize= option in SAO mode to specify track size. Testing cdrskin on the very same media: dd if=/dev/zero bs=1M count=500 | cdrskin -v dev=0,0,0 - This works. Also working: dd if=/dev/zero bs=1M count=500 | cdrskin -v dev=0,0,0 blank=all -multi - dd if=/dev/zero bs=1M count=500 | cdrskin -v dev=0,0,0 -multi - producing two recognizable sessions on the media which stays appendable: Media content: session 1 track 1 data lba: 000:02:00 Media content: session 1 leadoutlba:25600056:55:25 Media content: session 2 track 2 data lba:28468863:17:63 Media content: session 2 leadoutlba:540688 120:11:13 Media msinfo : mkisofs ... -C 284688,548384 Much like on CD. Linux mount as of kernel 2.4 recognizes the last session as the thing to mount (and to fail with, in this case). One could use the -C values to produce a third session in mountable ISO-9660 format. If there is a way to do this with cdrecord on DVD-R[W] then please give me an example how to. > I advise to use cdrecord for production quality media... Indeed my advise to write the single large file rawly would match well the characteristics of cdrecord -sao : cdrecord -v dev=... -sao /my/large/file This advise stays valid in case no other suitable formatting can be found. Have a nice day :) Thomas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: problems writing a large file to DVD+R Double Layer disk
[EMAIL PROTECTED] wrote: > Joerg Schilling: > > There is nothing like "speudo SCSI" CD/DVD writers only work with SCSI > > commands. > > That is true of course. > The command set is always SCSI as described in sub specs > SPC, SBC, MMC. > > I meant : > Appearing under Linux as /dev/sg and /dev/sr and not as /dev/hd. > Pseudo-Linux-SCSI. Ok ? This looks a bit confused. There is no problem with allowing to send raw SCSI commands through a high level driver interface like /dev/sr* and /dev/hd* in addition to the SCSI generic driver /dev/sg*. The problem on Linux is that it does not allow to send raw SCSI commands through /dev/sg* if the associated high level driver is /dev/hd* although the same type of devices works with /dev/sg* in case that the high level driver is /dev/sr*. The problem is also, that there are two different high level drivers (/dev/sr* vs. /dev/hd*) for CD-ROM drives depending on the SCSI transport. > me: > > > Programs growisofs or cdrskin are to prefer for that. > Joerg Schilling: > > The preferred program still is cdrecord. > > But not for piping onto DVD and not for multi-session on DVD. This is something that will change in the near future > Joerg, i do not want to diminish your merits about burning. > Nevertheless, currently cdrecord imposes too much restrictions > which cannot be justified on the level of MMC-5 specs. Could you please avoid this kind of writing? It causes wrong connotation at the readers side. The same could be said for e.g. growisofs. Growisofs artificially limits the write mode for DVDs to what DVD+R/RW allows ignoring the features of DVD-R/RW. > growisofs proves it since years, i proved it this year: > With single layer media no predicted size of the logical track > is needed except for DVD-RW treated by e.g. cdrecord blank=fast. > But cdrecord blank=all yields fully capable DVD-RW. This is definitely a wrong statement. The size is only "unneded" in case you use the less compatible packet writing mode. Cdrecord by default implements the write mode with the best read-compatibility. > > For double layer media, you _need_ to know the size in advance in > > order to be able to set the layer break at the right place. > > If you do not know this, please do not give advise > > Well, i did not burn double layers yet, nor did i find anybody > who is willing to try it. Kish Shen wants to use DVD+R/DL. > Maybe he got one left to waste for the progress of science. With cdrecord there is no need to test, as the tests have been done in former times already ;-) > Actually i advise to use growisofs for production purposes > with DVD+R/DL. I advise to use cdrecord for production quality media... Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) [EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: problems writing a large file to DVD+R Double Layer disk
Hi Jörg, Again, thanks for your reply! On Monday 02 April 2007 16:43, Joerg Schilling wrote: > Kish Shen <[EMAIL PROTECTED]> wrote: > > mkisofs â??-R â??-q â??-printâ??size /master/tree > > Why do you belkieve there is a -q option? > > mkisofs did never have a -q option. > This was on the man page I looked at, I copied the above example line from it. Here is some context for the line: To handle drives that need to know the size of a track before starting to write, first run mkisofs -R -q -print‐size /master/tree and then run mkisofs -R /master/tree | cdrecord speed=2 dev=2,0 tsize=XXXs ? This is from the file cdrecord.man in the doc directory, which I read using nroff -man. I downloaded this file yesterday, I think it is version 2.01.01a24. > > > The size for 's' (sector?) seems to be 2048 bytes, and when I hand > > calculated the sector sizes > > for the 7 other files I have in the directory (which were all smaller than > > 4GB and > > so were not ignored), rounding up each file's sector size to the next > > integer, I got a sector > > count of 745189, which is a little less than what mkisofs gives me (745364 > > with -R, or 745370 > > with -R -J). Am I missing something? > > I believe that no. > > > I calculated the sector size for each file by using the size from ls -l, > > and divide this by 2048, > > and rounding it up to the next integer. > > > > Will the written data be shown as files, even for the file that is > 4GB? I > > just want to save > > it as data, and not as a video file that conforms to some standard... > > I do not understand you. > > mkisofs will just skip the files >= 4GB and put the rest into the ISO-9660 > filesystem. > Sorry, I meant when I use cdrecord to try to write the files in the directory. From what you said before, I thought this would write the file >= 4GB to the Double Layer disk: >If you have problems with double layer disks, better use the cdrecord that >comes with cdrtools-2.01.01a24. Note that you need to call cdrecord as root >or install it suid root. Have I misunderstood? I thought the above was saying I could write files >4GB (my problem) to Double Layer disks with cdrecord. > Run cdrecord -scanbus to find the needed dev= parameter in this case. Thanks! > > Jörg > Cheers, Kish
Re: problems writing a large file to DVD+R Double Layer disk
Kish Shen <[EMAIL PROTECTED]> wrote: > Hi Jörg, > > Again, thanks for your reply! > > On Monday 02 April 2007 16:43, Joerg Schilling wrote: > > Kish Shen <[EMAIL PROTECTED]> wrote: > > > mkisofs â??-R â??-q â??-printâ??size /master/tree > > > > Why do you belkieve there is a -q option? > > > > mkisofs did never have a -q option. > > > This was on the man page I looked at, I copied the above example line from > it. Here is some > context for the line: > >To handle drives that need to know the size of a track >before starting to write, first run > >mkisofs -R -q -printâ??size /master/tree the mkisofs never did have the string "-q" not the string "/master/tree" inside But I just did fint that there is a type in the "cdrecord" man page. Thank you for pointing me to this problem. > > I do not understand you. > > > > mkisofs will just skip the files >= 4GB and put the rest into the ISO-9660 > > filesystem. > > > > Sorry, I meant when I use cdrecord to try to write the files in the > directory. From what you > said before, I thought this would write the file >= 4GB to the Double Layer > disk: No, it cannot write things that mkisofs did not put into the image. > >If you have problems with double layer disks, better use the cdrecord that > >comes with cdrtools-2.01.01a24. Note that you need to call cdrecord as root > >or install it suid root. > > Have I misunderstood? I thought the above was saying I could write files >4GB > (my problem) > to Double Layer disks with cdrecord. You did _also_ complain about a problem when writing to the media using growisofs. This is why I pointed you to cdrecord. Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) [EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: problems writing a large file to DVD+R Double Layer disk
Hi, Kish Shen: > Anyway, it [mkisofs] again said my file is too large and ignored it. Even if you can talk some mkisofs into formatting a file system with a file >= 2 GB, even then you might have difficulties to read that file on arbitrary computer systems. You'll have to split your file or use a large-file capable archiver rather than mkisofs. To my experience Joerg's program "star" is well suited. If it is about a single file, you may also write it on media flatly and memorize the size (i.e. write it on the media's upside with a pen). To write: growisofs -Z /dev/sr1=/my/fat/file To get it back: dd if=/dev/dvd bs=2048 count=... of=/my/copy/on/disk with count=... giving the memorized number of blocks. Joerg Schilling: > There is nothing like "speudo SCSI" CD/DVD writers only work with SCSI > commands. That is true of course. The command set is always SCSI as described in sub specs SPC, SBC, MMC. I meant : Appearing under Linux as /dev/sg and /dev/sr and not as /dev/hd. Pseudo-Linux-SCSI. Ok ? me: > > Programs growisofs or cdrskin are to prefer for that. Joerg Schilling: > The preferred program still is cdrecord. But not for piping onto DVD and not for multi-session on DVD. Joerg, i do not want to diminish your merits about burning. Nevertheless, currently cdrecord imposes too much restrictions which cannot be justified on the level of MMC-5 specs. growisofs proves it since years, i proved it this year: With single layer media no predicted size of the logical track is needed except for DVD-RW treated by e.g. cdrecord blank=fast. But cdrecord blank=all yields fully capable DVD-RW. One can justify the SCSI gestures of growisofs by the MMC-5 specs. I looked at what Andy Polyakov's program does, then i learned in the specs what this means and then i did my own implementation of those specs (not of growisofs code). It works on various DVD drives in the age of 3 to 0 years. It is written down in http://libburnia.pykix.org/browser/libburn/trunk/doc/cookbook.txt?format=raw paragraphs - Overwriteable DVD Cookbook (DVD-RAM, DVD+RW, DVD-RW) - Sequential DVD-R[W] Cookbook - DVD+R Cookbook (still emerging) with lots of references into the SCSI specs. Be invited to read it and to point me to any errors. > For double layer media, you _need_ to know the size in advance in > order to be able to set the layer break at the right place. > If you do not know this, please do not give advise Well, i did not burn double layers yet, nor did i find anybody who is willing to try it. Kish Shen wants to use DVD+R/DL. Maybe he got one left to waste for the progress of science. Actually i advise to use growisofs for production purposes with DVD+R/DL. Default cdrskin refuses to risk those expensive media. Anybody who is ready to risk a DVD+R/DL or DVD-R/DL media is hereby called up to pipe the output of some formatter (e.g. afio, star, ...) into the stdin of growisofs. More than 4.7e9 bytes, of course. Do not use ISO-9660 format because growisofs will recognize its size from the data. Then let's see wether it works. I bet on Yes. :)) Have a nice day :) Thomas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: problems writing a large file to DVD+R Double Layer disk
Kish Shen <[EMAIL PROTECTED]> wrote: > Hi Jörg, > > Thanks again for your quick reply! > > On Monday 02 April 2007 13:17, Joerg Schilling wrote: > > Kish Shen <[EMAIL PROTECTED]> wrote: > > > mkisofs -R /master/tree | cdrecord speed=2 dev=2,0 > > > > See the man page for cdrecord > > This will not work as you need to know the size of the session in advance. > > There are examples in the man page how to specify the size. > > > > Is this the tsize=s option? I tried using mkisofs -R as shown on the man > page to get the > size: > > mkisofs â??-R â??-q â??-printâ??size /master/tree Why do you belkieve there is a -q option? mkisofs did never have a -q option. > but the '-q' option was not recognised -- should this be -quiet? Anyway, it > again said my file is too > large and ignored it. correct > The size for 's' (sector?) seems to be 2048 bytes, and when I hand calculated > the sector sizes > for the 7 other files I have in the directory (which were all smaller than > 4GB and > so were not ignored), rounding up each file's sector size to the next > integer, I got a sector > count of 745189, which is a little less than what mkisofs gives me (745364 > with -R, or 745370 > with -R -J). Am I missing something? I believe that no. > I calculated the sector size for each file by using the size from ls -l, and > divide this by 2048, > and rounding it up to the next integer. > > Will the written data be shown as files, even for the file that is > 4GB? I > just want to save > it as data, and not as a video file that conforms to some standard... I do not understand you. mkisofs will just skip the files >= 4GB and put the rest into the ISO-9660 filesystem. > > dev= is unneeded in case that you only have one single CD/DVD writer. > > > > Jörg > > > Although I have one CD/DVD writer only, I do have another DVD reader (IDE) > and a > Panasonic PD/CD-ROM dual that is a SCSI device (it can read/write PD (the > predecessor to > DVD-RAM) disks, but can only play CDs)). Is there some way I can check if > dev= is > needed or not? If you have more than one device that identifies as "CD-ROM", you need to specify dev= Run cdrecord -scanbus to find the needed dev= parameter in this case. Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) [EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: problems writing a large file to DVD+R Double Layer disk
Hi Jörg, Thanks again for your quick reply! On Monday 02 April 2007 13:17, Joerg Schilling wrote: > Kish Shen <[EMAIL PROTECTED]> wrote: > > mkisofs -R /master/tree | cdrecord speed=2 dev=2,0 > > See the man page for cdrecord > This will not work as you need to know the size of the session in advance. > There are examples in the man page how to specify the size. > Is this the tsize=s option? I tried using mkisofs -R as shown on the man page to get the size: mkisofs ‐-R ‐-q ‐-print‐size /master/tree but the '-q' option was not recognised -- should this be -quiet? Anyway, it again said my file is too large and ignored it. The size for 's' (sector?) seems to be 2048 bytes, and when I hand calculated the sector sizes for the 7 other files I have in the directory (which were all smaller than 4GB and so were not ignored), rounding up each file's sector size to the next integer, I got a sector count of 745189, which is a little less than what mkisofs gives me (745364 with -R, or 745370 with -R -J). Am I missing something? I calculated the sector size for each file by using the size from ls -l, and divide this by 2048, and rounding it up to the next integer. Will the written data be shown as files, even for the file that is > 4GB? I just want to save it as data, and not as a video file that conforms to some standard... > dev= is unneeded in case that you only have one single CD/DVD writer. > > Jörg > Although I have one CD/DVD writer only, I do have another DVD reader (IDE) and a Panasonic PD/CD-ROM dual that is a SCSI device (it can read/write PD (the predecessor to DVD-RAM) disks, but can only play CDs)). Is there some way I can check if dev= is needed or not? Thanks in advance for any more help! Cheers, Kish
Re: problems writing a large file to DVD+R Double Layer disk
[EMAIL PROTECTED] wrote: > Kish Shen: > > use it -- can I use it to create a backup of my file(s)?i > > My DVD rewriter is a USB device, and not > > a SCSI device, and I am not sure what the device number and LUN etc. > > are for it (I only know that /dev/sr1 and /dev/scd1 both map to it). > > As it is pseudo-SCSI, try this There is nothing like "speudo SCSI" CD/DVD writers only work with SCSI commands. > cdrecord -scanbus As you might know that more than 6 months ago, cdrecord has been enhanced to autoselect the target in case that there is inly one possible drve in the system. Verify by: cdrecord -inq If this gives you the inquiry data for your drive you may omit the dev= parameter. > Programs growisofs or cdrskin are to prefer for that. The preferred program still is cdrecord. > Both are able to pipe a data stream of unpredicted > size onto DVD. > cdrskin is untested with double layer media, so you will > have to be adventurous or use growisofs. Cdrecord has been tested to correctly support double layer DVD+R media. If you prefer to write in a less compatible way, go for other programs than cdrecord. For double layer media, you _need_ to know the size in advance in order to be able to set the layer break at the right place. If you do not know this, please do not give advise Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) [EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: problems writing a large file to DVD+R Double Layer disk
Hi, Kish Shen: > use it -- can I use it to create a backup of my file(s)?i > My DVD rewriter is a USB device, and not > a SCSI device, and I am not sure what the device number and LUN etc. > are for it (I only know that /dev/sr1 and /dev/scd1 both map to it). As it is pseudo-SCSI, try this cdrecord -scanbus > Should I do something like: > mkisofs -R /master/tree | cdrecord speed=2 dev=2,0 There's a track source missing with cdrecord. For CD media, '-' would be ok. With DVD media, piping becomes cumbersome. Programs growisofs or cdrskin are to prefer for that. Both are able to pipe a data stream of unpredicted size onto DVD. cdrskin is untested with double layer media, so you will have to be adventurous or use growisofs. Usually growisofs does its own internal mkisofs piping. But if you want to use it as a plain DVD writer, try this: mkisofs -R /master/tree | growisofs -Z /dev/sr1=/dev/fd/0 (/dev/fd/0 is one way to say "standard input" as file address.) With cdrskin and single layer media, the same would be: mkisofs -R /master/tree | cdrskin -v speed=2 dev=/dev/sr1 -multi - Testers for double-layer media are wanted. Gallant wealthy users please contact me. :)) If you are interested in multi-volume backup on CD or DVD, i got a tool for that: scdbackup. Joerg Schilling: > Once cdrecord will support multi-border for DVD+R, it will be done in the > official way, it depends on whether growisofs does the same. At least according to MMC-5 there is not much danger that multi-session on DVD+R will be incompatible between the programs which are capable of it. We all close a track before we start the next one and thus it makes hardly a difference in the result wether we reserve the track size in advance or wether we just write away. Decisive is rather the CLOSE TRACK/SESSION function which is used at the end of a track. 010b keeps appendable, 101b and 110b finalize the disc. (mmc5r03c.pdf, 6.3.3.4) growisofs obviously refuses to finalize any DVD+R. So does cdrskin-0.3.4. In the development version cdrskin-0.3.5 DVD+R get finalized by 101b unless option -multi is present. I.e. just like with CD-R[W] or DVD-R[W]. Maybe i learn why growisofs has this reluctance. Cautious cdrskin-0.3.5 users might want to add -multi to any run on DVD+R until then. Have a nice day :) Thomas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: problems writing a large file to DVD+R Double Layer disk
Hi Jörg, On Monday 02 April 2007 00:02, Joerg Schilling wrote: > If you have problems with double layer disks, better use the cdrecord that > comes with cdrtools-2.01.01a24. Note that you need to call cdrecord as root > or install it suid root. > > Jörg > I took a look at cdrecord, and looked at the man page, but I am not sure if I understand how to use it -- can I use it to create a backup of my file(s)? My DVD rewriter is a USB device, and not a SCSI device, and I am not sure what the device number and LUN etc. are for it (I only know that /dev/sr1 and /dev/scd1 both map to it). Should I do something like: mkisofs -R /master/tree | cdrecord speed=2 dev=2,0 from the man page's example, where /master/tree is the directory I want to write out, but what should be the arguments for dev= ? Thanks again for your help! P.S. I hope my earlier message reached you, I still don't see it on the cdwrite mailing list... Cheers, Kish
Re: problems writing a large file to DVD+R Double Layer disk
Hi Joerg, Thanks for your quick reply! On Monday 02 April 2007 00:02, Joerg Schilling wrote: > Kish Shen <[EMAIL PROTECTED]> wrote: > > > Hi, > > [I sent this message several hours ago from another email address, but it > > has not appear yet, so > > I am trying again with a different e-mail address] > > > > I am trying to write a .ts file to a DVD+R Double Layer disk, so far > > without success. The file has a size of 4613734320. I issue the command: > > What is a .ts file? > Why do you need it? This is a file I downloaded, and I think .ts is some sort of container format for video (mplayer is able to play it direct). I am trying to archive it so I can remove it from my HD -- I don't really have enough room to keep it around my HD > In about 2 months, there will be a new version that supports files up to 8 TB. > If you use Linux, you then will need to check whether the Linux kernel > correctly > supports multi-extent files. I will add the needed multi-extent file support > to > OpenSolaris at the same time > That would be great! Would I be able to append to the +R double layer disk that I have written to with a previous version of growisofs? > > If you have problems with double layer disks, better use the cdrecord that > comes with cdrtools-2.01.01a24. Note that you need to call cdrecord as root > or install it suid root. > I will take a look at this. I assume I will need to use a new disk to do this, and cannot append the file to the double layer disk I have already partially written to using growisofs. > Jörg > Thanks again! Kish
Re: problems writing a large file to DVD+R Double Layer disk
Kish Shen <[EMAIL PROTECTED]> wrote: > Hi Jörg, > > On Monday 02 April 2007 00:02, Joerg Schilling wrote: > > > If you have problems with double layer disks, better use the cdrecord that > > comes with cdrtools-2.01.01a24. Note that you need to call cdrecord as root > > or install it suid root. > > > > Jörg > > > I took a look at cdrecord, and looked at the man page, but I am not sure if I > understand how to > use it -- can I use it to create a backup of my file(s)? My DVD rewriter is a > USB device, and not > a SCSI device, and I am not sure what the device number and LUN etc. are for > it (I only know > that /dev/sr1 and /dev/scd1 both map to it). Should I do something like: > > mkisofs -R /master/tree | cdrecord speed=2 dev=2,0 See the man page for cdrecord This will not work as you need to know the size of the session in advance. There are examples in the man page how to specify the size. dev= is unneeded in case that you only have one single CD/DVD writer. Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) [EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: problems writing a large file to DVD+R Double Layer disk
Kish Shen <[EMAIL PROTECTED]> wrote: > > What is a .ts file? > > Why do you need it? > > This is a file I downloaded, and I think .ts is some sort of container format > for video (mplayer > is able to play it direct). > > I am trying to archive it so I can remove it from my HD -- I don't really > have enough room to > keep it around my HD There is a standard that says that no single video file may be > (1 GB - 2k). > > In about 2 months, there will be a new version that supports files up to 8 > > TB. > > If you use Linux, you then will need to check whether the Linux kernel > > correctly > > supports multi-extent files. I will add the needed multi-extent file > > support to > > OpenSolaris at the same time > > > That would be great! Would I be able to append to the +R double layer disk > that I have > written to with a previous version of growisofs? I cannot speak for growisofs. I thought you did see an error message from growisofs. Once cdrecord will support multi-border for DVD+R, it will be done in the official way, it depends on whether growisofs does the same. > > If you have problems with double layer disks, better use the cdrecord that > > comes with cdrtools-2.01.01a24. Note that you need to call cdrecord as root > > or install it suid root. > > > > I will take a look at this. I assume I will need to use a new disk to do > this, and cannot append > the file to the double layer disk I have already partially written to using > growisofs. With the current features of cdrecord, you will need a new empty DVD+R/DL. Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) [EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: problems writing a large file to DVD+R Double Layer disk
Kish Shen <[EMAIL PROTECTED]> wrote: > Hi, > [I sent this message several hours ago from another email address, but it has > not appear yet, so > I am trying again with a different e-mail address] > > I am trying to write a .ts file to a DVD+R Double Layer disk, so far without > success. The file has a size of 4613734320. I issue the command: What is a .ts file? Why do you need it? > growisofs -Z /dev/sr1 -R -J pd > > where pd is where my files are. > > I get the message: > > mkisofs: Value too large for defined data type. File pd/ts is too large > - ignoring > > and the file is not written. This is with growisofs version 7.0, and mkisofs > 2.01.01a24 mkisofs currently only allows to write file with a max. size of 4 GB - 2k. In about 2 months, there will be a new version that supports files up to 8 TB. If you use Linux, you then will need to check whether the Linux kernel correctly supports multi-extent files. I will add the needed multi-extent file support to OpenSolaris at the same time > I updated my growisofs and mkisofs to these versions because those that came > with my Linux (growisofs: version 5.17, mkisofs: 2.01a27) does not recognise > the DVD+R DL media: > > linux:/home/kish # growisofs -Z /dev/sr1 -R -J pd > :-( /dev/sr1: media is not recognized as recordable DVD: 2B If you have problems with double layer disks, better use the cdrecord that comes with cdrtools-2.01.01a24. Note that you need to call cdrecord as root or install it suid root. Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) [EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
problems writing a large file to DVD+R Double Layer disk
Hi, [I sent this message several hours ago from another email address, but it has not appear yet, so I am trying again with a different e-mail address] I am trying to write a .ts file to a DVD+R Double Layer disk, so far without success. The file has a size of 4613734320. I issue the command: growisofs -Z /dev/sr1 -R -J pd where pd is where my files are. I get the message: mkisofs: Value too large for defined data type. File pd/ts is too large - ignoring and the file is not written. This is with growisofs version 7.0, and mkisofs 2.01.01a24 I updated my growisofs and mkisofs to these versions because those that came with my Linux (growisofs: version 5.17, mkisofs: 2.01a27) does not recognise the DVD+R DL media: linux:/home/kish # growisofs -Z /dev/sr1 -R -J pd :-( /dev/sr1: media is not recognized as recordable DVD: 2B My system configuration is: OS: SuSe Linux 9.1, with kernel 2.6.11.4 DVD Writer: LG GSA 5163D For now, I just want to write the file as a data file to the disk, so I am not worried about DVD compatibility. Thanks in advance for any help/information on how I can write the file to the disk! Cheers, Kish -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Writing DVD-R Double Layer
> :-( /dev/hdc: media is not recognized as recordable DVD: 10015 Output of dvd+rw-mediainfo? Are you sure the drive can handle this media type, this particular media brand, and this particular disk? > >From looking at source of growisofs.c and growisofs_mmc.cpp, it appears > that growisofs does not support DVD-R DL. Is that correct? Which version growisofs? Is DVD-R DL different to DVD+R DL? Did you try a DVD+R DL? What drive? > Any ideas when that support is going to appear? Pointers on where to > find the necessary information, so I could implement it? Andy seems to have gone offline, but his website http://fy.chalmers.se/~appro/linux/DVD+RW/ has a lot of info and some pointers. The MMC docs (drive command sets) should be the authoritative source. HTH, Volker -- Volker Kuhlmann is possibly list0570 with the domain in header http://volker.dnsalias.net/ Please do not CC list postings to me. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Writing DVD-R Double Layer
I have BENQ DW1640 burner using firmware BSLB. When trying to write DVD-R Double Layer media with k3b, I get the following message: :-( /dev/hdc: media is not recognized as recordable DVD: 10015 The growisofs command used is /usr/bin/growisofs -Z /dev/hdc=/dev/fd/0 -use-the-force-luke=notray -use-the-force-luke=tty -use-the-force-luke=break:2082944 -use-the-force-luke=dummy -dvd-compat -speed=4 >From looking at source of growisofs.c and growisofs_mmc.cpp, it appears that growisofs does not support DVD-R DL. Is that correct? Any ideas when that support is going to appear? Pointers on where to find the necessary information, so I could implement it? Marcus -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: DVD-R double layer ?
On Mon, 15 Nov 2004, Joerg Schilling wrote: > Bill Davidsen <[EMAIL PROTECTED]> wrote: > > > www.newegg.com has the DL writers (cheap) and the media ($24 ea last > > At Bloediamackt (Mediamarkt) 9.98 Euro. > > I hope you mean Canadian $ or something similar. Thank you for the price update, it has come down to $12US + shipping since I looked the last time. That's close enough to ten Euro to pretty much match. The price is still too high, careful buying gets DVD-R 4.7GB blanks down to $0.40US, so DL blanks at 20 times that aren't reasonable backup media. I suppose that if you were copying a movie DVD or something it would make sense, but many DVDs are on sale for less than the blank, so even that depends on the cost of just buying a copy. I hope the price will come down eventually, backups are still an issue. -- bill davidsen <[EMAIL PROTECTED]> CTO, TMR Associates, Inc Doing interesting things with little computers since 1979. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: DVD-R double layer ?
Bill Davidsen <[EMAIL PROTECTED]> wrote: > www.newegg.com has the DL writers (cheap) and the media ($24 ea last At Bloediamackt (Mediamarkt) 9.98 Euro. I hope you mean Canadian $ or something similar. Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) If you don't have iso-8859-1 [EMAIL PROTECTED](work) chars I am J"org Schilling URL: http://www.fokus.fraunhofer.de/usr/schilling ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: DVD-R double layer ?
Helmut Jarausch wrote: Hi, does anybody know if and when DVD writers for the -R format with double layer capabilities appear on the market? Thanks for a hint. www.newegg.com has the DL writers (cheap) and the media ($24 ea last time I looked!). I also have one of the HD burners which can put 1.4GB on a standard CD (under Windows). cdrecord doesn't support it, and I lack the time and debugger to find out what vendor commands it uses to select that mode. It's cost effective to make the ISO images in a Windows partition, reboot, and do the burn. Unfortunately it's not time effective, so it was a proof of concept only. -- bill davidsen <[EMAIL PROTECTED]> CTO TMR Associates, Inc Doing interesting things with small computers since 1979 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: DVD-R double layer ?
Helmut Jarausch <[EMAIL PROTECTED]> wrote: > Hi, > > does anybody know if and when DVD writers for the -R format with double > layer capabilities appear on the market? I am sure that recent Pioneer drives should be able to write to them if only media was available. Last week, there was a DL Mnt. Fuji conference if they did decide on DVD-R/DL, we will see the media soon. Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) If you don't have iso-8859-1 [EMAIL PROTECTED](work) chars I am J"org Schilling URL: http://www.fokus.fraunhofer.de/usr/schilling ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: DVD-R double layer ?
> does anybody know if and when DVD writers for the -R format with double > layer capabilities appear on the market? I can only speak for the market "on the other side", but tastech.co.nz has had a number of them (e.g. Pioneer A108) for weeks now. Media too. Volker -- Volker Kuhlmann is possibly list0570 with the domain in header http://volker.dnsalias.net/ Please do not CC list postings to me. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
DVD-R double layer ?
Hi, does anybody know if and when DVD writers for the -R format with double layer capabilities appear on the market? Thanks for a hint. Helmut Jarausch Lehrstuhl fuer Numerische Mathematik RWTH - Aachen University D 52056 Aachen, Germany -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
