Re: DNS-like idea for SCSI (NIS+ maybe)
On Sat 21 August 2004 18:06, Albert Cahalan wrote: On Sat, 2004-08-21 at 14:28, Joerg Schilling wrote: Check the man page of cdrecord for a decription of the features that are handled by /etc/default/cdrecord Hmmm, that's pretty good. Do you think you could make all the other programs use that file too? If I define my CD-RW as QueFire in that file, then mount QueFire /mnt had ought to mount it I think. Also, dd if=QueFire should read from the device, and cat QueFire too. It could get kind of confusing if I had a file named QueFire as well though. Perhaps there is a better solution? Uhhm, symlink? Just make a symlink /dev/FancyName (or wherever you want to put it) and point it to the relevant device. I don't mount /dev/hdc either, I mount /dev/cdrom. XMMS opens /dev/cdrom if it plays an audio CD. If I decided to swap around my devices, I'd just change the symlink and be done. I'm don't know much about Solaris, but I imagine mount, dd and cat work with device files there too, which to dd and cat are just files to read from, and to mount are just strings to be passed to the kernel mount command. Of course, this won't do anything for programs that actually send SCSI command directly (like cdrecord et al), since they use bus,target,lun triples. So you'd need a separate system for that, like /etc/default/cdrecord or this NIS+. Lourens -- GPG public key: http://home.student.utwente.nl/l.e.veen/lourens.key
Re: cdrtools-2.01a37 ready
On Thu 19 August 2004 14:35, Joerg Schilling wrote: From: Volker Kuhlmann [EMAIL PROTECTED] Obviously you're on the back foot and ran out of arguments, otherwise you wouldn't spend a whole email on discussing a minor point (so I didn't check my PPS carefully enough) and nothing else, instead of sticking to the 2 points in question. And so that even you can understand it: introducing bugs is not a violation of the GPL. It's a right of the GPL. You still did not understand the problem :-( A program is an artwork (this is what the European Union did write into laws). Since both you and SuSE are in Germany, I would think that German law would apply. There are of course the Berne treaty and the EU Copyright Directive, but neither are laws. In the case of the EUCD, it is up to the member states to make local laws that implement the EUCD. Incidentally, which law are you referring to? I couldn't really find anything in the text of the EUCD. Even though you may get the permission to modify an artwork, you will not get the permission to create bad carricatures and call them just modified versions. The GPL requires you not to impact the original authors' reputations, but this is what they are doing by publishing defective variants. Which is why they stick a big notice on it that literally says that they changed it and that they may have introduced new bugs. The problem is that people don't read the notice, and then start bothering you. But can you really blame SuSE for that? What more can they do about it? Send over an employee to each buyer to explain the situation? Lourens PS: congratulations on the new mail client. It's much better. -- GPG public key: http://home.student.utwente.nl/l.e.veen/lourens.key
Re: Adding MD5 to Image...
On Fri 13 August 2004 21:21, Mike 'Fox' Morrey wrote: Sorry, my bad. Misunderstood. I don't mean *ADD* it to an image, but simply REPORT it when the image is finished... And example of what I do daily..: mkisofs -J -R -V toolbox#0327 -v -split-output -o /usr/image/archive.iso -iso-level 3 -path-list /usr/image/filelist.out /usr/image/ [...] Total translation table size: 0 Total rockridge attributes bytes: 68578 Total directory bytes: 0 Path table size(bytes): 10 Done with: The File(s) Block(s)2290479 Writing: Ending Padblock Start Block 2290813 Done with: Ending Padblock Block(s)150 Max brk space used 1dc784 2290963 extents written (4474 Mb) Add the line like I have below to the output.. Chksum: 5b2b214d09a5d8a9ea35dc32614dedb7 /usr/image/archive.iso So then scripts could grep out the chksum, and write it to an *.MD5 file at the same time the image is made... How about using tee(1)? You could have mkisofs write the image to stdout, then use tee to put it into a file as well as pipe it into md5sum. Lourens -- GPG public key: http://home.student.utwente.nl/l.e.veen/lourens.key
Re: mkisofs udf help!
On Mon 9 August 2004 21:41, Carsten Neumann wrote: On Mon, 09 Aug 2004, Joerg Schilling wrote: Just read the OSTA UDF documents. It is not helpful to post such comments without an appropriate link. Try typing OSTA UDF documents into Google. www.osta.org seems to be down, but otherwise the first result gets you pretty close. Now if they were stored in a vault in a bank in some quiet backwater town at the edge of the internet a link would be necessary, but in this case... Lourens -- GPG public key: http://home.student.utwente.nl/l.e.veen/lourens.key
Re: Check / verify and test quality of burned CD/DVD's
On Thu 15 July 2004 14:20, Oliver Schuetz wrote: HI, I would like to know which tools are out there to verify burned CD's/DVD's and which tools or ways are out there for linux to see what quality my burned media is. I can verify a burned media with cmp. But this doesn't give any information about quality. Any hints? Have a look at the readcd manpage. Maybe the -c2scan option may be of use? Lourens -- GPG public key: http://home.student.utwente.nl/l.e.veen/lourens.key
Re: Check / verify and test quality of burned CD/DVD's
On Thu 15 July 2004 16:50, Ashish Rangole wrote: I usually calculate the md5sum of the iso image before writing it to the disc. After successful write I use readcd to read the iso image back, calculate its md5sum and compare. But that doesn't give you any quality information does it? And that was what you were asking about? From the readcd manpage: -c2scan Scans the whole CD or the range specified by the sectors=range for C2 errors. C2 errors are errors that are uncorrectable after the second stage of the 24/28 + 28/32 Reed Solomon correction system at audio level (2352 bytes sector size). If an audio CD has C2 errors, interpolation is needed to hide the errors. If a data CD has C2 errors, these errors are in most cases corrected by the ECC/EDC code that makes 2352 bytes out of 2048 data bytes. The ECC/EDC code should be able to correct about 100 C2 error bytes per sector. If you find C2 errors you may want to reduce the speed using the speed= option as C2 errors may be a result of dynamic unbalance on the medium. If it finds a lot of C2 errors, quality is low, if not, quality is high. Unless I misunderstood your question... Lourens -- GPG public key: http://home.student.utwente.nl/l.e.veen/lourens.key
Re: DVD burning problem Plextor PX-708A using xcdroast cdrecord.prodvd
On Thu 3 June 2004 01:33, martin laurberg wrote: Dear All, Has anyone got a Plextor PX-708A working under linux? I followed the Thomas Chungs instructions on http://www.xcdroast.org/ for using xcdroast with cdrecord.ProDVD but without success. The plextor takes both DVD-R and DVD+R. I tried dvd burning of a 4.2 GB iso-image on DVD-R media, both as normal user and as root (from 1x to 4x speed). I guess the essential error is an illegal writing request to the drive Sense Key: 0x5 Illegal Request, Segment 0 Thanks in advance for any hints, Martin System: Redhat 8.0. Check to see if you don't have either magicdev (used with GNOME) or automount (for KDE) installed. These are Red Hat programs that attempt to autostart a CD when you insert it. Unfortunately, this interferes with the burning process. Try removing these programs (there's no real use for them anyway) and try again. Lourens -- GPG public key: http://home.student.utwente.nl/l.e.veen/lourens.key
Re: cdrtools-2.01a28 ready
On Wed 21 April 2004 09:24, Helmut Jarausch wrote: On 21 Apr, Joerg Schilling wrote: The files are located on: ftp://ftp.berlios.de/pub/cdrecord/alpha ... Am I the only one having problems to access this site? I get 421 Service not available, remote server has closed connection most of the time. Doesn't work for me either right now. Lourens -- GPG public key: http://home.student.utwente.nl/l.e.veen/lourens.key
Re: cdrtools-2.01a28 ready
On Wed 21 April 2004 09:24, Helmut Jarausch wrote: On 21 Apr, Joerg Schilling wrote: The files are located on: ftp://ftp.berlios.de/pub/cdrecord/alpha ... Am I the only one having problems to access this site? I get 421 Service not available, remote server has closed connection most of the time. Doesn't work for me either right now. Lourens -- GPG public key: http://home.student.utwente.nl/l.e.veen/lourens.key
Re: growisofs minus_rw_quickgrow question
On Wed 24 March 2004 23:18, chen zhao wrote: Andy, snip Can you please explain what happened, thanks in advance, Chen You create a disk with growISOfs, and then try to mount it as a UDF filesystem. That's not going to work. growisofs makes ISO9660 filesystems, so you should mount with -t iso9660, not with -t udf. Lourens -- GPG public key: http://home.student.utwente.nl/l.e.veen/lourens.key
Re: growisofs minus_rw_quickgrow question
On Wed 24 March 2004 23:18, chen zhao wrote: Andy, snip Can you please explain what happened, thanks in advance, Chen You create a disk with growISOfs, and then try to mount it as a UDF filesystem. That's not going to work. growisofs makes ISO9660 filesystems, so you should mount with -t iso9660, not with -t udf. Lourens -- GPG public key: http://home.student.utwente.nl/l.e.veen/lourens.key
Re: CD/DVD writing on IRIX6.5
On Tue 16 March 2004 02:03, Ashish Rangole wrote: I have a SGI IRIX 6.5 system with external DVD writer capable of burning DVD+RW and DVD-RW media. This device is connected as SCSI device through a SCSI HBA. I would like to know what software is available if I want to :- 1. Write CD-R,DVD-R 2. Optionally also write DVD+R,DVD+RW, with incremental writes. I understand that there are tools available to do this on Linux but not so sure about IRIX 6.5. Any response shall be greatly appreciated. Well, basically for writing CDs on UNIX there is cdrecord, which works on just about any OS you can think of. See README.sgi in the source distribution as well. For DVDs, there is cdrecord-ProDVD which is a (non-GPL but free as in beer for noncommercial use) version of cdrecord that can also burn DVDs, and there is Andy's growisofs. I'm not sure if that works on IRIX though, but you can always try. cdrecord: http://www.fokus.gmd.de/research/cc/glone/employees/joerg.schilling/private/cdrecord.html growisofs: http://fy.chalmers.se/~appro/linux/DVD+RW/ HTH, Lourens -- GPG public key: http://home.student.utwente.nl/l.e.veen/lourens.key
Re: Strange behaviour of growisofs
On Mon 8 March 2004 19:05, Michael Mess wrote: This is the last output from writing a DVD: [EMAIL PROTECTED]:~uname -a Linux rakete 2.2.20 #21 SMP Sat Jan 24 22:02:53 CET 2004 i686 unknown [EMAIL PROTECTED]:~ I compiled dvd+rw-tools-5.17.4.8.6 with kernel-headers of linux.2.4.20 (gcc -I linux.2.4.20-direcory/include/linux/), the rest is like from the makefile which is generated from the Makefile (It uses m4 to create something for make in a pipe). Erm, you compiled against 2.4.20, but are using it with 2.2.20? I'd say that's a receipe for disaster... Lourens -- GPG public key: http://home.student.utwente.nl/l.e.veen/lourens.key -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Strange behaviour of growisofs
On Mon 8 March 2004 19:05, Michael Mess wrote: This is the last output from writing a DVD: [EMAIL PROTECTED]:~uname -a Linux rakete 2.2.20 #21 SMP Sat Jan 24 22:02:53 CET 2004 i686 unknown [EMAIL PROTECTED]:~ I compiled dvd+rw-tools-5.17.4.8.6 with kernel-headers of linux.2.4.20 (gcc -I linux.2.4.20-direcory/include/linux/), the rest is like from the makefile which is generated from the Makefile (It uses m4 to create something for make in a pipe). Erm, you compiled against 2.4.20, but are using it with 2.2.20? I'd say that's a receipe for disaster... Lourens -- GPG public key: http://home.student.utwente.nl/l.e.veen/lourens.key
Re: writing speed issue with dvd+rw-tools
On Wed 3 March 2004 14:04, Joerg Schilling wrote: If you don't understand that you get a valuable piece of software and don't like to even do simple tests, then you are just the kind of person nobody likes to get in contact with. But then you should be consistent and stay away from this mailing list! Note that this is _not_ a cdrecord mailinglist. It is a Debian mailinglist about writing CDs in general. It also seems to be an important support forum for growisofs. Jon came here asking for advice about a problem he had with growisofs (which Andy helped him with). You started about cdrecord-ProDVD, Jon explained why he doesn't use cdrecord-ProDVD, and now you are complaining that he he is a freeloader because he doesn't want to test cdrecord-ProDVD? That is simply unfair. Jon does _not_ use your software, and he does _not_ owe you anything. I realise that you're greatly frustrated with open source in general and the GNU/Linux community in particular, but taking it all out on Jon is simply unfair and uncalled for. Lourens -- GPG public key: http://home.student.utwente.nl/l.e.veen/lourens.key -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Updated DVD patch for cdrecord
On Wed 3 March 2004 14:09, Joerg Schilling wrote: From: Warly [EMAIL PROTECTED] scanbus will also display dev=ATA scanning if no dev option is passed on the command line, mostly because we are defaulting on ide-cd with 2.6 linux kernel. Another attempt to break portability of portable software by adding Linux specific changes that are even questionable on Linux If you don't use Linux, don't use the patch. If you don't like it, don't use the patch. Open source is about choice. Period. Lourens -- GPG public key: http://home.student.utwente.nl/l.e.veen/lourens.key -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: writing speed issue with dvd+rw-tools
On Wed 3 March 2004 14:07, Joerg Schilling wrote: From: Lourens Veen [EMAIL PROTECTED] WRONG - RTFM ftp://ftp.berlios.de/pub/cdrecord/ProDVD/README I just read that document, and I'm curious what exactly is wrong. To split up Jon's statement: - cdrecord-ProDVD will burn a maximum of 1 GB of data without a key - cdrecord-ProDVD will burn more than 1 GB of data, but only with a key - the key must be obtained from you - the key is time limited - the key restricts usage (burning speed for CDs) - it is your right to licence cdrecord-ProDVD like this So which one is wrong? It all seems to match the README to me... It seems that you did not really read the README. your statements do not match what's inside the README Endlessly repeating you're wrong does not magically make you win an argument. It's also a waste of time, since it doesn't enlighten anyone. But okay, if you want it spelled out: 1) cdrecord-ProDVD will burn a maximum of 1 GB of data without a key The binaries allow you to write either complete DVD-R DVD-RW media when using the -dummy option or to write up to 1 GB of real data to a single media. As DVD+R/DVD+RW does not support a -dummy mode, you do not have the option to write a full DVD+R/RW medium in dummy mode. Seems pretty accurate to me. 2) cdrecord-ProDVD will burn more than 1 GB of data, but only with a key You need a key to unlock unlimited writing. cdrecord-ProDVD has been free for research or educational porposes since January 2002. cdrecord-ProDVD is now free for private non-commercial purposes too. If you have this key (this one has been renewed on Jan 26th 2004): [...] as environment variable, cdrecord-ProDVD will not be limited when writing DVDs. Again, looks correct. 3) The key must be obtained from you The README doesn't say anything about obtaining keys elsewhere. We could try and reverse-engineer ofcourse... 4) The key is time limited As I am not sure if people will follow my licensing rules, so these keys are time limited and will expire on 2004 Aug 20 13:06:40 I will continue to make private/educational/research use free, but it may be that you need to request your private key for free after August 20th 2004. Seems pretty clear to me. 5) The key restricts usage (burning speed for CDs) However, it is limited to 4x or the lowest possiblespeed of the drive (whatever value is higher) if you write a CD. Cdrecord-ProDVD-1.11a34 and before did limit the CD writing speed to 1. If the environment variable CDR_SECURITY= is not present, the cdrecord-ProDVD binaries don't limit the CD write speed. It makes sense to write a wrapper script for DVD only for this reason (see below). If you use the key, burning speed for CDs is reduced. Ofcourse, you can create a wrapper script and only use the key if you need it, or just use an ordinary cdrecord binary to burn CDs at full speed, so this whole thing is pretty pointless, but it's there nonetheless. 6) It is your right to licence cdrecord-ProDVD like this If German Urhaberrecht is anything like the Dutch Auteursrecht, it simply prohibits distribution and distribution of modified versions, giving the author an opportunity to licence his work. I have not been able to find a copyright licence for the cdrecord-ProDVD binaries. You putting them up on the web seems to imply permission to download them, but other than that it's all rather unclear. The key is really not a copyright licence thing since it restricts usage, not copying. It's more like a technical protection. I'm not sure whether Germany implemented the EUCD yet, but that would probably protect trying to break it. At any rate, I don't think you're disputing this point. So, I showed you that I did in fact do my homework. The only thing is that apparently I'm too stupid to understand. I realise that. Repeating it isn't going to make me smarter. So, please, explain where I went wrong. I want to learn, but I can't do it without some help. Lourens -- GPG public key: http://home.student.utwente.nl/l.e.veen/lourens.key -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: writing speed issue with dvd+rw-tools
On Wed 3 March 2004 14:04, Joerg Schilling wrote: If you don't understand that you get a valuable piece of software and don't like to even do simple tests, then you are just the kind of person nobody likes to get in contact with. But then you should be consistent and stay away from this mailing list! Note that this is _not_ a cdrecord mailinglist. It is a Debian mailinglist about writing CDs in general. It also seems to be an important support forum for growisofs. Jon came here asking for advice about a problem he had with growisofs (which Andy helped him with). You started about cdrecord-ProDVD, Jon explained why he doesn't use cdrecord-ProDVD, and now you are complaining that he he is a freeloader because he doesn't want to test cdrecord-ProDVD? That is simply unfair. Jon does _not_ use your software, and he does _not_ owe you anything. I realise that you're greatly frustrated with open source in general and the GNU/Linux community in particular, but taking it all out on Jon is simply unfair and uncalled for. Lourens -- GPG public key: http://home.student.utwente.nl/l.e.veen/lourens.key
Re: Updated DVD patch for cdrecord
On Wed 3 March 2004 14:09, Joerg Schilling wrote: From: Warly [EMAIL PROTECTED] scanbus will also display dev=ATA scanning if no dev option is passed on the command line, mostly because we are defaulting on ide-cd with 2.6 linux kernel. Another attempt to break portability of portable software by adding Linux specific changes that are even questionable on Linux If you don't use Linux, don't use the patch. If you don't like it, don't use the patch. Open source is about choice. Period. Lourens -- GPG public key: http://home.student.utwente.nl/l.e.veen/lourens.key
Re: writing speed issue with dvd+rw-tools
On Wed 3 March 2004 14:07, Joerg Schilling wrote: From: Lourens Veen [EMAIL PROTECTED] WRONG - RTFM ftp://ftp.berlios.de/pub/cdrecord/ProDVD/README I just read that document, and I'm curious what exactly is wrong. To split up Jon's statement: - cdrecord-ProDVD will burn a maximum of 1 GB of data without a key - cdrecord-ProDVD will burn more than 1 GB of data, but only with a key - the key must be obtained from you - the key is time limited - the key restricts usage (burning speed for CDs) - it is your right to licence cdrecord-ProDVD like this So which one is wrong? It all seems to match the README to me... It seems that you did not really read the README. your statements do not match what's inside the README Endlessly repeating you're wrong does not magically make you win an argument. It's also a waste of time, since it doesn't enlighten anyone. But okay, if you want it spelled out: 1) cdrecord-ProDVD will burn a maximum of 1 GB of data without a key The binaries allow you to write either complete DVD-R DVD-RW media when using the -dummy option or to write up to 1 GB of real data to a single media. As DVD+R/DVD+RW does not support a -dummy mode, you do not have the option to write a full DVD+R/RW medium in dummy mode. Seems pretty accurate to me. 2) cdrecord-ProDVD will burn more than 1 GB of data, but only with a key You need a key to unlock unlimited writing. cdrecord-ProDVD has been free for research or educational porposes since January 2002. cdrecord-ProDVD is now free for private non-commercial purposes too. If you have this key (this one has been renewed on Jan 26th 2004): [...] as environment variable, cdrecord-ProDVD will not be limited when writing DVDs. Again, looks correct. 3) The key must be obtained from you The README doesn't say anything about obtaining keys elsewhere. We could try and reverse-engineer ofcourse... 4) The key is time limited As I am not sure if people will follow my licensing rules, so these keys are time limited and will expire on 2004 Aug 20 13:06:40 I will continue to make private/educational/research use free, but it may be that you need to request your private key for free after August 20th 2004. Seems pretty clear to me. 5) The key restricts usage (burning speed for CDs) However, it is limited to 4x or the lowest possiblespeed of the drive (whatever value is higher) if you write a CD. Cdrecord-ProDVD-1.11a34 and before did limit the CD writing speed to 1. If the environment variable CDR_SECURITY= is not present, the cdrecord-ProDVD binaries don't limit the CD write speed. It makes sense to write a wrapper script for DVD only for this reason (see below). If you use the key, burning speed for CDs is reduced. Ofcourse, you can create a wrapper script and only use the key if you need it, or just use an ordinary cdrecord binary to burn CDs at full speed, so this whole thing is pretty pointless, but it's there nonetheless. 6) It is your right to licence cdrecord-ProDVD like this If German Urhaberrecht is anything like the Dutch Auteursrecht, it simply prohibits distribution and distribution of modified versions, giving the author an opportunity to licence his work. I have not been able to find a copyright licence for the cdrecord-ProDVD binaries. You putting them up on the web seems to imply permission to download them, but other than that it's all rather unclear. The key is really not a copyright licence thing since it restricts usage, not copying. It's more like a technical protection. I'm not sure whether Germany implemented the EUCD yet, but that would probably protect trying to break it. At any rate, I don't think you're disputing this point. So, I showed you that I did in fact do my homework. The only thing is that apparently I'm too stupid to understand. I realise that. Repeating it isn't going to make me smarter. So, please, explain where I went wrong. I want to learn, but I can't do it without some help. Lourens -- GPG public key: http://home.student.utwente.nl/l.e.veen/lourens.key
Re: writing speed issue with dvd+rw-tools
On Tue 2 March 2004 17:10, Joerg Schilling wrote: From: Jon Wilson [EMAIL PROTECTED] WRONG No need to shout, Joerg. It is: see below. If I want to burn more than 1G, I have to get a time limted, usage restricted key from you. It's your right to license it like this. But I have given you no indication whether my use will comply with these restrictions, so you are wrong to assume that I am able to do so (or that I am happy to do so, but that's a seperate issue). WRONG - RTFM ftp://ftp.berlios.de/pub/cdrecord/ProDVD/README I just read that document, and I'm curious what exactly is wrong. To split up Jon's statement: - cdrecord-ProDVD will burn a maximum of 1 GB of data without a key - cdrecord-ProDVD will burn more than 1 GB of data, but only with a key - the key must be obtained from you - the key is time limited - the key restricts usage (burning speed for CDs) - it is your right to licence cdrecord-ProDVD like this So which one is wrong? It all seems to match the README to me... Lourens -- GPG public key: http://home.student.utwente.nl/l.e.veen/lourens.key -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: writing speed issue with dvd+rw-tools
On Tue 2 March 2004 17:10, Joerg Schilling wrote: From: Jon Wilson [EMAIL PROTECTED] WRONG No need to shout, Joerg. It is: see below. If I want to burn more than 1G, I have to get a time limted, usage restricted key from you. It's your right to license it like this. But I have given you no indication whether my use will comply with these restrictions, so you are wrong to assume that I am able to do so (or that I am happy to do so, but that's a seperate issue). WRONG - RTFM ftp://ftp.berlios.de/pub/cdrecord/ProDVD/README I just read that document, and I'm curious what exactly is wrong. To split up Jon's statement: - cdrecord-ProDVD will burn a maximum of 1 GB of data without a key - cdrecord-ProDVD will burn more than 1 GB of data, but only with a key - the key must be obtained from you - the key is time limited - the key restricts usage (burning speed for CDs) - it is your right to licence cdrecord-ProDVD like this So which one is wrong? It all seems to match the README to me... Lourens -- GPG public key: http://home.student.utwente.nl/l.e.veen/lourens.key
Re: Automounters - more info wanted (was Re: Re: plextor px-708uf: cannot get disk type)
On Sat 31 January 2004 22:46, Volker Kuhlmann wrote: What I meant was those autothingies should keep their hands off a disk while a burn process is happening. Dunno whether it's possible to detect this, but isn't that the way it should be? The burner software can open exclusive - see man open. Yes, even better if the burning software can get access to the device in such a way that accesses from other processes result in in use - go away. You mean O_EXCL? That doesn't seem to make sense? O_EXCL When used with O_CREAT, if the file already exists it is an error and the open will fail. My man page doesn't mention anything about E_EXCL when used without O_CREAT, but if the behaviour is return success only when the device isn't in use (r or w elsewhere) and to prevent subsequent processes from opening even read-only, then that looks As far as I can tell, it says that it won't create or open the file if it already exists. I'm just going by the manpage, but it doesn't say anything about just opening without O_CREAT (and I reckon the device file would exist), let alone that this would prevent other programs from opering. If it would work without O_CREAT _and_ these automounter opened with O_EXCL, then it might be the solution. But I don't see that written down anywhere... Lourens -- GPG public key: http://home.student.utwente.nl/l.e.veen/lourens.key
Re: Automounters - more info wanted (was Re: Re: plextor px-708uf: cannot get disk type)
On Sat 31 January 2004 16:30, Rob Bogus wrote: Volker Kuhlmann wrote: What I meant was those autothingies should keep their hands off a disk while a burn process is happening. Dunno whether it's possible to detect this, but isn't that the way it should be? The burner software can open exclusive - see man open. You mean O_EXCL? That doesn't seem to make sense? Lourens -- GPG public key: http://home.student.utwente.nl/l.e.veen/lourens.key -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Automounters - more info wanted (was Re: Re: plextor px-708uf: cannot get disk type)
On Sat 31 January 2004 22:46, Volker Kuhlmann wrote: What I meant was those autothingies should keep their hands off a disk while a burn process is happening. Dunno whether it's possible to detect this, but isn't that the way it should be? The burner software can open exclusive - see man open. Yes, even better if the burning software can get access to the device in such a way that accesses from other processes result in in use - go away. You mean O_EXCL? That doesn't seem to make sense? O_EXCL When used with O_CREAT, if the file already exists it is an error and the open will fail. My man page doesn't mention anything about E_EXCL when used without O_CREAT, but if the behaviour is return success only when the device isn't in use (r or w elsewhere) and to prevent subsequent processes from opening even read-only, then that looks As far as I can tell, it says that it won't create or open the file if it already exists. I'm just going by the manpage, but it doesn't say anything about just opening without O_CREAT (and I reckon the device file would exist), let alone that this would prevent other programs from opering. If it would work without O_CREAT _and_ these automounter opened with O_EXCL, then it might be the solution. But I don't see that written down anywhere... Lourens -- GPG public key: http://home.student.utwente.nl/l.e.veen/lourens.key -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Automounters - more info wanted (was Re: Re: plextor px-708uf: cannot get disk type)
On Sat 31 January 2004 16:30, Rob Bogus wrote: Volker Kuhlmann wrote: What I meant was those autothingies should keep their hands off a disk while a burn process is happening. Dunno whether it's possible to detect this, but isn't that the way it should be? The burner software can open exclusive - see man open. You mean O_EXCL? That doesn't seem to make sense? Lourens -- GPG public key: http://home.student.utwente.nl/l.e.veen/lourens.key
Re: Automounters - more info wanted (was Re: Re: plextor px-708uf: cannot get disk type)
On Thu 29 January 2004 12:34, Joerg Schilling wrote: From [EMAIL PROTECTED] Wed Jan 28 21:01:50 2004 Is there any way at all to check whether a CD is being written without disturbing the writing process? NO, if you like to check for a media change you need to access the TOC. Thanks, but that's not what I was asking. What I want to know is, if I were writing a volume management system, and I wanted to make sure it didn't interfere with a write in progress, is there any way for it to find out if a disk is being written without disturbing a write in progress? If this is impossible, then for the volume management not to interfere with cdrecord, cdrecord must tell the volume manager that it is writing. Lourens -- GPG public key: http://home.student.utwente.nl/l.e.veen/lourens.key -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Automounters - more info wanted (was Re: Re: plextor px-708uf: cannot get disk type)
On Tue 27 January 2004 11:16, Lourens Veen wrote: On Tue 27 January 2004 08:06, Lourens Veen wrote: Then there is autofs (http://freshmeat.net/projects/autofs/?topic_id=142, can't find a real homepage) and KDE uses fam (http://oss.sgi.com/projects/fam/), however I don't think fam actually mounts devices by itself, it just watches files. I use (parts of) KDE myself and fam is almost always running; it's never given me any problems with writing CDs. It turns out that there is a daemon similar to magicdev, which is used with KDE: autorun (http://sourceforge.net/projects/autorun/). From the description: I just found out that both magicdev and autorun originated at Red Hat. It seems somebody decided they needed automounting functionality, even if it meant a security weakness, and they implemented it for both GNOME and KDE, as magicdev and autorun respectively. It seems like these are separate packages, so I think the best thing to do is to recommend uninstalling them wholesale. I'll try and get a patch to README.volmgt together this weekend. Lourens -- GPG public key: http://home.student.utwente.nl/l.e.veen/lourens.key -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Automounters - more info wanted (was Re: Re: plextor px-708uf: cannot get disk type)
On Wed 28 January 2004 16:07, Joerg Schilling wrote: From [EMAIL PROTECTED] Tue Jan 27 21:08:37 2004 Aha, thanks for explaining that. This does pose a bit of a problem though if you have both: say I insert a CD, then the volume manager sees it and mounts it. Then I go to my magic automounter directory and it tries to mount it too. Problem. Doing away with the automounter means users have to mount disks by hand (which my mum would probably find too complicated), while doing away with the volume management means that users get no feedback after they inserted a CD in the drive, which is less bad but still undesirable from a user interface perspective. This is a reason why Apple and Sun introduced such a beast on the 1980s So how about this. We run a normal automounter. The volume manager does not actually mount disks, but just reads the volume label. This is enough to interrupt the CD writing process in a way that creates a coaster. Is there any way at all to check whether a CD is being written without disturbing the writing process? Lourens -- GPG public key: http://home.student.utwente.nl/l.e.veen/lourens.key -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Automounters - more info wanted (was Re: Re: plextor px-708uf: cannot get disk type)
On Wed 28 January 2004 00:28, Volker Kuhlmann wrote: or whatever. Then when the user actually opens the drive, the automounter kicks in and it is mounted. In this case, you simply don't need an automounter, and SuSE shows that nicely. User wants to open hard disk? - Click harddisk icon. User wants to open CD? - Click CD icon. I'm sure my mother would be able to manage that. Neither KDE nor gnome automounters are even shipped by SuSE. Given the amount of trouble with them, one could call it foresight ;) I use autofs because I chose to manually enable it. True, but having an automounter like autofs would be an easy way of implementing this, and it has the advantage that it'll also work from outside of the DE. To reiterate, we still need to know how to disable KDE autorun and GNOME magicdev for a single drive. I'd say these programs are broken if they cause coasters during burning. This is not for cdrecord/growisofs to fix. Lodge a problem report and urgent fix request with their maintainers, and meanwhile include a stern warning with burning software to obliterate this kind of nuisance software from the system during burning. Well, I'd prefer to be a bit more subtle, and explain how to disable it for selected drives rather than removing it entirely. But to write the doc I need to know how... Ideally, there would be a way to tell automount and magicdev to turn this off from a program. IMHO ideally these programs would be smart enough to keep their hands off things which they otherwise break. But that means that you lose all functionality if you have a single writer in the machine that is also used for reading. If you want it to work for already-written CDs, and yet not interfere with burning, then unless there is a non-interfering way of determining the disk type and/or whether it is being written, this is impossible. Lourens -- GPG public key: http://home.student.utwente.nl/l.e.veen/lourens.key
Re: Automounters - more info wanted (was Re: Re: plextor px-708uf: cannot get disk type)
On Wed 28 January 2004 16:07, Joerg Schilling wrote: From [EMAIL PROTECTED] Tue Jan 27 21:08:37 2004 Aha, thanks for explaining that. This does pose a bit of a problem though if you have both: say I insert a CD, then the volume manager sees it and mounts it. Then I go to my magic automounter directory and it tries to mount it too. Problem. Doing away with the automounter means users have to mount disks by hand (which my mum would probably find too complicated), while doing away with the volume management means that users get no feedback after they inserted a CD in the drive, which is less bad but still undesirable from a user interface perspective. This is a reason why Apple and Sun introduced such a beast on the 1980s So how about this. We run a normal automounter. The volume manager does not actually mount disks, but just reads the volume label. This is enough to interrupt the CD writing process in a way that creates a coaster. Is there any way at all to check whether a CD is being written without disturbing the writing process? Lourens -- GPG public key: http://home.student.utwente.nl/l.e.veen/lourens.key
Automounters - more info wanted (was Re: Re: plextor px-708uf: cannot get disk type)
On Tue 27 January 2004 00:51, Joerg Schilling wrote: From: Lourens Veen [EMAIL PROTECTED] On Fri 23 January 2004 20:39, Thomas J Magliery PhD wrote: Joerg, I only can detect one message in single-user mode, and it's not too helpful: Jan 23 14:23:09 reganlinux kernel: cdrom: This disc doesn't have any tracks I recognize! Jan 23 14:23:40 reganlinux last message repeated 31 times This is from /var/log/messages. I can't find anything else that seems to be relvent anywhere else. Just in case, at the end of my email is the whole contents of /var/log/messages from my last restart... Well, actually it is. I dropped it into Google, and it turns out that this error comes from magicdev. From what I understand, magicdev is the GNOME automounter. Try setting it to not do anything automatically in Nautilus, or just kill the process and see if that helps. Please give us more information. I can't I'm afraid, I don't use GNOME, and I don't use any kind of automounter either. I read something in an email in a web mail archive that talked about disabling automounting for a device. I figure you can just right-click on it in Nautilus and change some settings, but I've never used Nautilus. Debian has the following to say about magicdev: Package: magicdev (1.1.5-1) A GNOME daemon for automatically mounting/playing CDs Magicdev is a daemon that runs within the GNOME environment and detects when a CD is removed or inserted. Magicdev handles running autorun programs on the CD, updating the File Manager, and playing audio CDs. So my above statement was inaccurate, it's not a generic automounter. Volume management inside KDE or GNOME is completely wrong - it does not belong into a GUI. Well, I haven't looked at it in-depth, but it seems to me that magicdev is an independent daemon that knows about GNOME and what to do when it detects a CD in a drive. It's distributed with GNOME, and provides services to it, but that's it. And calling KDE or GNOME a GUI is a bit of an understatement too; they're a lot more powerful and complex than say, CDE. I agree that it would be better to have this in a separate subsystem though, which could be accessible through HAL (http://www.ometer.com/hardware.html). As more and more people get such problems, it would be nice to have an easy to understand desription for recognising the procress from a ps output and what to do to get rid of at least the problems with the burner. From what I've found on the web, to turn off magicdev people just uninstall it. Magicdev can be recognised from the above error message This disc doesn't have any tracks I recognize!. Then there is autofs (http://freshmeat.net/projects/autofs/?topic_id=142, can't find a real homepage) and KDE uses fam (http://oss.sgi.com/projects/fam/), however I don't think fam actually mounts devices by itself, it just watches files. I use (parts of) KDE myself and fam is almost always running; it's never given me any problems with writing CDs. If there's anyone here actually using magicdev or autofs, more information on how to see if it's running and how to configure it to stay away from CD writers would be very much appreciated Lourens -- GPG public key: http://home.student.utwente.nl/l.e.veen/lourens.key -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Automounters - more info wanted (was Re: Re: plextor px-708uf: cannot get disk type)
On Tue 27 January 2004 08:06, Lourens Veen wrote: Then there is autofs (http://freshmeat.net/projects/autofs/?topic_id=142, can't find a real homepage) and KDE uses fam (http://oss.sgi.com/projects/fam/), however I don't think fam actually mounts devices by itself, it just watches files. I use (parts of) KDE myself and fam is almost always running; it's never given me any problems with writing CDs. It turns out that there is a daemon similar to magicdev, which is used with KDE: autorun (http://sourceforge.net/projects/autorun/). From the description: autorun automagically recognizes all available CDROMs in the system, mounts them upon insertion of a media and executes a possible autorun executable on the CD. The user can remove the media; autorun will call unmount after that. I did a quick download and looked through the source, and it seems that the binary will be called autorun. I also did a search through the archives and found a reference to supermount (http://supermount-ng.sourceforge.net/). There is also amd, but that doesn't seem to be very widely used, and certainly not installed by default. If someone installed that by hand, they can probably figure out how to fix it. So we have the following table of possible automounters interfering with cdrecord on Linux: Name Type Process name magicdev daemon magicdev? autorundaemon autorun autofsmodule + daemon automount supermountmodule N/A Detecting automounters magicdev and autorun can probably be detected by ps, supermount (or at least supermount-ng) has a /proc/fs/supermount directory. If you are running autofs, you likely have a file called /etc/auto.global, and there is the automount process. Preventing automounters from interfering Ideally, an automounter would detect writing in progress and stay away from the drive while the CD is being written. I don't think any of the abovementioned automounters has such a feature. As an alternative, automounting could be disabled for the writer. autofs is configured through a map file (see the man page) and supermount is configured through /etc/fstab (see the readme). I don't know about autorun and magicdev. As a last resort, the daemon-based automounters could be disabled completely by killing the process and/or uninstalling. The in-kernel ones would have to be disabled through their configuration files, by unloading the module or by recompiling the kernel. Some other bits of information - GNOME uses magicdev - KDE uses autorun, at least on Red Hat - Mandrake includes supermount, but outside of Mandrake it's probably rather rare More info, especially on configuring magicdev and autorun, is still very welcome! Lourens -- GPG public key: http://home.student.utwente.nl/l.e.veen/lourens.key -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: plextor px-708uf: cannot get disk type
On Tue 27 January 2004 20:11, Thomas J Magliery PhD wrote: You might recall from my first emails that I was also getting this error from within xcdroast, which used the (same) authentic binary from your site. I didn't realize that the command line used the RLH9 RPM installation of dvdrecord. Sorry for the confusion. Incidentally, do I correctly understand that the dvdrecord command no longer exists (or that cdrecord-ProDVD is the new dvdrecord)? Or was dvdrecord just some Red Hat package of cdrecord-ProDVD? Well, first there was cdrecord, which is GPL. Then DVD writers appeared, and someone adapted cdrecord to be able to record to his DVD drive, and called it dvdrecord. He didn't make very clear that this was a modified version of cdrecord (or at least not clear enough as far as Jörg's concerned) which according to Jörg violates section 2a of the GPL. Hence his calling it illegal. In the mean time, Jörg published cdrecord-ProDVD under a proprietary license. cdrecord-ProDVD is better tested than dvdrecord, and it works with most if not all drives currently on the market, and not just the one or two that dvdrecord works with. cdrecord development was then suspended for a while, and Andy Polyakov made dvd+rw-tools (growisofs) which is mainly meant for DVD+ drives, and is open source under the GPL. It seems to work very well, and is well-supported. So, in summary, and regardless of whether dvdrecord is illegal or not, you're probably better off using either cdrecord-ProDVD or dvd+rw-tools to write DVDs, since they're better on a technical level, and have good support. (Note to Jörg and Andy: that was off the top of my head, if anything is inaccurate, please correct me) Lourens -- GPG public key: http://home.student.utwente.nl/l.e.veen/lourens.key -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Automounters - more info wanted (was Re: Re: plextor px-708uf: cannot get disk type)
On Tue 27 January 2004 12:06, Joerg Schilling wrote: From: Lourens Veen [EMAIL PROTECTED] Package: magicdev (1.1.5-1) A GNOME daemon for automatically mounting/playing CDs Magicdev is a daemon that runs within the GNOME environment and detects when a CD is removed or inserted. Magicdev handles running autorun programs on the CD, updating the File Manager, and playing audio CDs. So my above statement was inaccurate, it's not a generic automounter. Well, if you do it right, then then the automounter is the wrong place for this functionality: - The task os an automounter is to watch where you try to step in. If you step into some magic land, it opens a door for you. If you go out of the magic land, the automounter will make it disappear. - The task of a volume management system in on contrary is to watch the media. If someone inderts a medium, it mounts this medium if possible. This is independent to where you step in. It does _not_ unmount the medium if you are obviously not interested in it. Aha, thanks for explaining that. This does pose a bit of a problem though if you have both: say I insert a CD, then the volume manager sees it and mounts it. Then I go to my magic automounter directory and it tries to mount it too. Problem. Doing away with the automounter means users have to mount disks by hand (which my mum would probably find too complicated), while doing away with the volume management means that users get no feedback after they inserted a CD in the drive, which is less bad but still undesirable from a user interface perspective. So how about this. We run a normal automounter. The volume manager does not actually mount disks, but just reads the volume label. This volume label is then sent to the Desktop Environment with a disk change event, so that the DE can do it's You just inserted X, do you want me to do Y thing or blink the icon and change its name or whatever. Then when the user actually opens the drive, the automounter kicks in and it is mounted. This way, the user could insert a CD, the cut-down volume manager would detect it as empty and leave it be. The DE, now knowing the CD is empty, can launch the CD writing application either immediately or when the user clicks the drive's icon. If the cut-down volume manager and the automounter can communicate (or are the same system), the automounter could even refuse to mount the CD when it knows it's an empty one, thus preventing unwanted accesses that interfere with writing. It seems a clean solution to me, and implementable as well. Perhaps having autofs generate events via DBUS and modifying magicdev and automount to listen to that instead of to the drive directly, or removing them entirely, would be enough already. That doesn't mean it's not a big amount of work though :-). I agree that it would be better to have this in a separate subsystem though, which could be accessible through HAL (http://www.ometer.com/hardware.html). It makes no sense to have a zillion different volume management systems on one OS. If you do, it is close to impossible for software authors to find out how they work and how they might be influenced by programs like cdrecord. Well, given the amount and size of the differences between different Linux distributions, perhaps it's time to start thinking of them as different operating systems rather than variations of the same one. You could do as many other vendors of proprietary software do and only support one or a few distributions explicitly. They may still be broken, but at least it makes the job of tracking the problems a lot more manageable. After all, Linux is just a kernel. If there's anyone here actually using magicdev or autofs, more information on how to see if it's running and how to configure it to stay away from CD writers would be very much appreciated I would be happy, to see people working on contributions... Me too, and I volunteer to wrap it all up into a patch to README.volmgt and a blurb for the dvd+rw-tools website. To reiterate, we still need to know how to disable KDE autorun and GNOME magicdev for a single drive. Note that if the support is put into e.g. cdrecord.c, it cannot make it into the official version because this would break portability. Volmgt support belongs into the OS specific part of libscg. I understand that, but I don't think it's up to cdrecord to fix this. Automount and magicdev assume that it's always ok to access the CD drive, which is wrong, because it might interfere with CD burning. If the user turns them off for the writer, the problem will be solved, at least for current Linux systems. Ideally, there would be a way to tell automount and magicdev to turn this off from a program. If they actually do have such a feature, it may be possible to have cdrecord disable them automatically before burning. I don't know enough about either
Re: plextor px-708uf: cannot get disk type
On Tue 27 January 2004 21:25, Joerg Schilling wrote: From: Lourens Veen [EMAIL PROTECTED] Well, first there was cdrecord, which is GPL. Then DVD writers appeared, and someone adapted cdrecord to be able to record to his DVD drive, and called it dvdrecord. He didn't make very clear that this was a modified version of cdrecord (or at least not clear enough as far as Jörg's concerned) which according to Jörg violates section 2a of the GPL. Hence his calling it illegal. WRONG! There is only one cdrecord source. A reduced version of the source is available under GPL. Cdrecord-ProDVD is now nearly 6 years old! My bad, I should have thought a bit better and realise that dvdrecord was created as an open source alternative to cdrecord-ProDVD, and hence that cdrecord-ProDVD already existed. On October 22th 2001, a week after the test binary has been available, a first DVD patch to cdrecord appeared. The illegal version that is found on RedHat systems is just made by applying this completely outdated patch. The patch itself is not illegal but it has many bugs. If somebody creates a binary from it and don't makes clear that this is not the official cdrecord, then he is violating the GPL. Almost. The GPL states that You must cause the modified files to carry prominent notices stating that you changed the files and the date of any change. in section 2a. Hence what makes dvdrecord violate the GPL is the fact that there is no mention of the changes in the sources, not the fact that it is not mentioned in the binary or the output. Section 2c says it must display an appropriate copyright notice whenever the original cdrecord would have done so, which it does, if I read the source correctly. Lourens -- GPG public key: http://home.student.utwente.nl/l.e.veen/lourens.key -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: [Cdrecord-developers] Cdrtools-2.01a25: Patch to make cdrtools 2.01a25 Linux compatible
On Tue 27 January 2004 21:41, Robert S. Dubinski wrote: On Tue, Jan 27, 2004 at 03:10:42PM -0500, Ambrose Li wrote: Yes, myself is to blame for not checking the updated FHS. But why would anyone upgrading from libc5 to libc6 suspect that a change in the FHS should affect the upgrade (esp. if the libc6 docs do not refer to the FHS)? So my main complaint will be that I'll need to dig around per se, in unknown places for random upgrades. If upgrading to libc6 means I should rm the symlink, the libc6 docs should point this out, or at least refer me to the LHS. I didn't see either when I did the upgrade. The standard response to that is, Leave it to your friendly distribution vendor to take care of. If you're interested in upgrading libc yourself, then you're usually at the point of rolling your own distribution, and might want to concern yourself with LSB/FHS. Yeah, locating all these docs can be a bear, but if you don't do things by hand and instead use a major distribution vendor, you really shouldn't have to worry. But how is the vendor supposed to know that GNU libc6 requires the files to be oriented according to the FHS? That should be in the glibc docs, period. Lourens -- GPG public key: http://home.student.utwente.nl/l.e.veen/lourens.key -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Automounters - more info wanted (was Re: Re: plextor px-708uf: cannot get disk type)
On Wed 28 January 2004 00:28, Volker Kuhlmann wrote: or whatever. Then when the user actually opens the drive, the automounter kicks in and it is mounted. In this case, you simply don't need an automounter, and SuSE shows that nicely. User wants to open hard disk? - Click harddisk icon. User wants to open CD? - Click CD icon. I'm sure my mother would be able to manage that. Neither KDE nor gnome automounters are even shipped by SuSE. Given the amount of trouble with them, one could call it foresight ;) I use autofs because I chose to manually enable it. True, but having an automounter like autofs would be an easy way of implementing this, and it has the advantage that it'll also work from outside of the DE. To reiterate, we still need to know how to disable KDE autorun and GNOME magicdev for a single drive. I'd say these programs are broken if they cause coasters during burning. This is not for cdrecord/growisofs to fix. Lodge a problem report and urgent fix request with their maintainers, and meanwhile include a stern warning with burning software to obliterate this kind of nuisance software from the system during burning. Well, I'd prefer to be a bit more subtle, and explain how to disable it for selected drives rather than removing it entirely. But to write the doc I need to know how... Ideally, there would be a way to tell automount and magicdev to turn this off from a program. IMHO ideally these programs would be smart enough to keep their hands off things which they otherwise break. But that means that you lose all functionality if you have a single writer in the machine that is also used for reading. If you want it to work for already-written CDs, and yet not interfere with burning, then unless there is a non-interfering way of determining the disk type and/or whether it is being written, this is impossible. Lourens -- GPG public key: http://home.student.utwente.nl/l.e.veen/lourens.key -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Automounters - more info wanted (was Re: Re: plextor px-708uf: cannot get disk type)
On Tue 27 January 2004 00:51, Joerg Schilling wrote: From: Lourens Veen [EMAIL PROTECTED] On Fri 23 January 2004 20:39, Thomas J Magliery PhD wrote: Joerg, I only can detect one message in single-user mode, and it's not too helpful: Jan 23 14:23:09 reganlinux kernel: cdrom: This disc doesn't have any tracks I recognize! Jan 23 14:23:40 reganlinux last message repeated 31 times This is from /var/log/messages. I can't find anything else that seems to be relvent anywhere else. Just in case, at the end of my email is the whole contents of /var/log/messages from my last restart... Well, actually it is. I dropped it into Google, and it turns out that this error comes from magicdev. From what I understand, magicdev is the GNOME automounter. Try setting it to not do anything automatically in Nautilus, or just kill the process and see if that helps. Please give us more information. I can't I'm afraid, I don't use GNOME, and I don't use any kind of automounter either. I read something in an email in a web mail archive that talked about disabling automounting for a device. I figure you can just right-click on it in Nautilus and change some settings, but I've never used Nautilus. Debian has the following to say about magicdev: Package: magicdev (1.1.5-1) A GNOME daemon for automatically mounting/playing CDs Magicdev is a daemon that runs within the GNOME environment and detects when a CD is removed or inserted. Magicdev handles running autorun programs on the CD, updating the File Manager, and playing audio CDs. So my above statement was inaccurate, it's not a generic automounter. Volume management inside KDE or GNOME is completely wrong - it does not belong into a GUI. Well, I haven't looked at it in-depth, but it seems to me that magicdev is an independent daemon that knows about GNOME and what to do when it detects a CD in a drive. It's distributed with GNOME, and provides services to it, but that's it. And calling KDE or GNOME a GUI is a bit of an understatement too; they're a lot more powerful and complex than say, CDE. I agree that it would be better to have this in a separate subsystem though, which could be accessible through HAL (http://www.ometer.com/hardware.html). As more and more people get such problems, it would be nice to have an easy to understand desription for recognising the procress from a ps output and what to do to get rid of at least the problems with the burner. From what I've found on the web, to turn off magicdev people just uninstall it. Magicdev can be recognised from the above error message This disc doesn't have any tracks I recognize!. Then there is autofs (http://freshmeat.net/projects/autofs/?topic_id=142, can't find a real homepage) and KDE uses fam (http://oss.sgi.com/projects/fam/), however I don't think fam actually mounts devices by itself, it just watches files. I use (parts of) KDE myself and fam is almost always running; it's never given me any problems with writing CDs. If there's anyone here actually using magicdev or autofs, more information on how to see if it's running and how to configure it to stay away from CD writers would be very much appreciated Lourens -- GPG public key: http://home.student.utwente.nl/l.e.veen/lourens.key
Re: Automounters - more info wanted (was Re: Re: plextor px-708uf: cannot get disk type)
On Tue 27 January 2004 08:06, Lourens Veen wrote: Then there is autofs (http://freshmeat.net/projects/autofs/?topic_id=142, can't find a real homepage) and KDE uses fam (http://oss.sgi.com/projects/fam/), however I don't think fam actually mounts devices by itself, it just watches files. I use (parts of) KDE myself and fam is almost always running; it's never given me any problems with writing CDs. It turns out that there is a daemon similar to magicdev, which is used with KDE: autorun (http://sourceforge.net/projects/autorun/). From the description: autorun automagically recognizes all available CDROMs in the system, mounts them upon insertion of a media and executes a possible autorun executable on the CD. The user can remove the media; autorun will call unmount after that. I did a quick download and looked through the source, and it seems that the binary will be called autorun. I also did a search through the archives and found a reference to supermount (http://supermount-ng.sourceforge.net/). There is also amd, but that doesn't seem to be very widely used, and certainly not installed by default. If someone installed that by hand, they can probably figure out how to fix it. So we have the following table of possible automounters interfering with cdrecord on Linux: Name Type Process name magicdev daemon magicdev? autorundaemon autorun autofsmodule + daemon automount supermountmodule N/A Detecting automounters magicdev and autorun can probably be detected by ps, supermount (or at least supermount-ng) has a /proc/fs/supermount directory. If you are running autofs, you likely have a file called /etc/auto.global, and there is the automount process. Preventing automounters from interfering Ideally, an automounter would detect writing in progress and stay away from the drive while the CD is being written. I don't think any of the abovementioned automounters has such a feature. As an alternative, automounting could be disabled for the writer. autofs is configured through a map file (see the man page) and supermount is configured through /etc/fstab (see the readme). I don't know about autorun and magicdev. As a last resort, the daemon-based automounters could be disabled completely by killing the process and/or uninstalling. The in-kernel ones would have to be disabled through their configuration files, by unloading the module or by recompiling the kernel. Some other bits of information - GNOME uses magicdev - KDE uses autorun, at least on Red Hat - Mandrake includes supermount, but outside of Mandrake it's probably rather rare More info, especially on configuring magicdev and autorun, is still very welcome! Lourens -- GPG public key: http://home.student.utwente.nl/l.e.veen/lourens.key
Re: plextor px-708uf: cannot get disk type
On Tue 27 January 2004 20:11, Thomas J Magliery PhD wrote: You might recall from my first emails that I was also getting this error from within xcdroast, which used the (same) authentic binary from your site. I didn't realize that the command line used the RLH9 RPM installation of dvdrecord. Sorry for the confusion. Incidentally, do I correctly understand that the dvdrecord command no longer exists (or that cdrecord-ProDVD is the new dvdrecord)? Or was dvdrecord just some Red Hat package of cdrecord-ProDVD? Well, first there was cdrecord, which is GPL. Then DVD writers appeared, and someone adapted cdrecord to be able to record to his DVD drive, and called it dvdrecord. He didn't make very clear that this was a modified version of cdrecord (or at least not clear enough as far as Jörg's concerned) which according to Jörg violates section 2a of the GPL. Hence his calling it illegal. In the mean time, Jörg published cdrecord-ProDVD under a proprietary license. cdrecord-ProDVD is better tested than dvdrecord, and it works with most if not all drives currently on the market, and not just the one or two that dvdrecord works with. cdrecord development was then suspended for a while, and Andy Polyakov made dvd+rw-tools (growisofs) which is mainly meant for DVD+ drives, and is open source under the GPL. It seems to work very well, and is well-supported. So, in summary, and regardless of whether dvdrecord is illegal or not, you're probably better off using either cdrecord-ProDVD or dvd+rw-tools to write DVDs, since they're better on a technical level, and have good support. (Note to Jörg and Andy: that was off the top of my head, if anything is inaccurate, please correct me) Lourens -- GPG public key: http://home.student.utwente.nl/l.e.veen/lourens.key
Re: Re: plextor px-708uf: cannot get disk type
On Fri 23 January 2004 20:39, Thomas J Magliery PhD wrote: Joerg, I only can detect one message in single-user mode, and it's not too helpful: Jan 23 14:23:09 reganlinux kernel: cdrom: This disc doesn't have any tracks I recognize! Jan 23 14:23:40 reganlinux last message repeated 31 times Jan 23 14:24:41 reganlinux last message repeated 59 times Jan 23 14:25:42 reganlinux last message repeated 60 times Jan 23 14:26:43 reganlinux last message repeated 60 times Jan 23 14:27:44 reganlinux last message repeated 60 times Jan 23 14:28:45 reganlinux last message repeated 59 times Jan 23 14:29:46 reganlinux last message repeated 58 times Jan 23 14:30:47 reganlinux last message repeated 60 times Jan 23 14:31:48 reganlinux last message repeated 60 times Jan 23 14:32:49 reganlinux last message repeated 60 times Jan 23 14:33:50 reganlinux last message repeated 60 times === This error is obviously independent of my running dvdrecord, which I did during this time, also. It gives the same error as below. I am using: dvdrecord -atip /dev=0,0,0. This is from /var/log/messages. I can't find anything else that seems to be relvent anywhere else. Just in case, at the end of my email is the whole contents of /var/log/messages from my last restart... Well, actually it is. I dropped it into Google, and it turns out that this error comes from magicdev. From what I understand, magicdev is the GNOME automounter. Try setting it to not do anything automatically in Nautilus, or just kill the process and see if that helps. Lourens -- GPG public key: http://home.student.utwente.nl/l.e.veen/lourens.key -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Problems burning CD-R's with Plextor PX-708A and cdrecord
On Sat 24 January 2004 21:17, jeff beck wrote: I'm sure I am doing something wrong and am only allowing myself to get yelled at by Mr. Schilling by posting, but I can't seem to write CD-R's successfully with my new Plextor PX-708A. I am using SONY CD-R 80's which are 32 speed. Nearly all the burns I try fail unless I use driveropts=burnfree - which I understand lessons the quality of my CD. I do not know whether the quality is lower only at the instant of bufferunderun or throughout the entire CD. I also am not sure how the quality of the CD is lower. I have tried using the cdrecord that comes with my redhat9, current binaries, or, as you see now, the latest alpha. I upgraded my firmware to 1.04. My burner is primary-slave, the wav files are on secondary-master. I have DMA enabled everywhere. Changing the speed and turning off pad or dao seem to make no difference. As I mentioned, burnfree works great. If you're burning audio CD's on Linux 2.4, be aware that DMA is only supported for a block sizes that are multiples of 512 there, while burning audio uses larger blocks (2352 bytes?). How does burning data discs go? If that works fine, then this is probably the problem. write error - loss of streaming definitely is a buffer underrun though, which matches the fact that enabling burnfree fixes the problem. Lourens -- GPG public key: http://home.student.utwente.nl/l.e.veen/lourens.key -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Compiling programs that depend on kernel/user interfaces
On Sun 25 January 2004 20:55, Joerg Schilling wrote: If somebody is interested in getting a description of the usual way to deal with dependencies on kernel/user interfaces and the resulting contraints, I am willing to send one. As I got the impression that this discussion has been already extended too long, I don't append the text here as it would take me extra time to write it. Yes, I would love such an explanation. I'm a computer science student, and while I'm currently more into software engineering than into operating systems, it is an interesting problem that has some SE implications as well. It seems to me that this is a design issue more than an implementation problem. I'd like to know the points of view of the various people involved, and see how it compares to what I'm learning in class. First things first though: what is the goal of a kernel-userland interface? Without a clear definition of what it's supposed to do, it's impossible to compare approaches. Lourens -- GPG public key: http://home.student.utwente.nl/l.e.veen/lourens.key -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Problems burning CD-R's with Plextor PX-708A and cdrecord
On Sat 24 January 2004 21:17, jeff beck wrote: I'm sure I am doing something wrong and am only allowing myself to get yelled at by Mr. Schilling by posting, but I can't seem to write CD-R's successfully with my new Plextor PX-708A. I am using SONY CD-R 80's which are 32 speed. Nearly all the burns I try fail unless I use driveropts=burnfree - which I understand lessons the quality of my CD. I do not know whether the quality is lower only at the instant of bufferunderun or throughout the entire CD. I also am not sure how the quality of the CD is lower. I have tried using the cdrecord that comes with my redhat9, current binaries, or, as you see now, the latest alpha. I upgraded my firmware to 1.04. My burner is primary-slave, the wav files are on secondary-master. I have DMA enabled everywhere. Changing the speed and turning off pad or dao seem to make no difference. As I mentioned, burnfree works great. If you're burning audio CD's on Linux 2.4, be aware that DMA is only supported for a block sizes that are multiples of 512 there, while burning audio uses larger blocks (2352 bytes?). How does burning data discs go? If that works fine, then this is probably the problem. write error - loss of streaming definitely is a buffer underrun though, which matches the fact that enabling burnfree fixes the problem. Lourens -- GPG public key: http://home.student.utwente.nl/l.e.veen/lourens.key
Re: XCDRoast (was: Re: plextor px-708uf: cannot get disk type)
On Sat 17 January 2004 15:19, j_post wrote: On Saturday 17 January 2004 04:39 am, Joerg Schilling wrote: People who used Xcdroast once, mostly don't like to use other GUIs anymore. Is that because Xcdroast is somehow better than the other GUIs, or just because people tend to think it works, so why bother with anything else? In my case, it was Huh? Okay, I'll use the command line, that's probably easier to learn which I subsequently did for a while. Then I found K3B, and although I was a bit afraid that it might be as bad as Xcdroast, I tried it anyway, and found it very intuitive. I now use either K3B or the command line, rather randomly. I think Xcdroast is nice if you (want to) know what happens when you burn a CD, ie creating an image and burning it in a specific way. If you're just an end user who wants to put his latest digital photos on a CD for mum and don't care how or what then I recommend using something else. Lourens -- GPG public key: http://home.student.utwente.nl/l.e.veen/lourens.key -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: XCDRoast (was: Re: plextor px-708uf: cannot get disk type)
On Sat 17 January 2004 15:19, j_post wrote: On Saturday 17 January 2004 04:39 am, Joerg Schilling wrote: People who used Xcdroast once, mostly don't like to use other GUIs anymore. Is that because Xcdroast is somehow better than the other GUIs, or just because people tend to think it works, so why bother with anything else? In my case, it was Huh? Okay, I'll use the command line, that's probably easier to learn which I subsequently did for a while. Then I found K3B, and although I was a bit afraid that it might be as bad as Xcdroast, I tried it anyway, and found it very intuitive. I now use either K3B or the command line, rather randomly. I think Xcdroast is nice if you (want to) know what happens when you burn a CD, ie creating an image and burning it in a specific way. If you're just an end user who wants to put his latest digital photos on a CD for mum and don't care how or what then I recommend using something else. Lourens -- GPG public key: http://home.student.utwente.nl/l.e.veen/lourens.key
Re: cdrtools-2.01a22 ready
On Thu 8 January 2004 13:47, Joerg Schilling wrote: From [EMAIL PROTECTED] Wed Jan 7 16:34:14 2004 If you unpack this on a Linux-2.6 system using a star binary that has been compiled on Linux-2.4, you will extract a character special with minor 88 instead of minor 7000. This proves that you cannot run binaries from Linux-2.4 on Linux-2.6 correctly. Well, it proves that you cannot run _some_ binaries that were compiled under linux 2.4 on linux 2.6 correctly. Well as you may easily read frm the mail to this thread, most people are unable to understand which programs would have such problems. For this reason, I did use a general warning. No, you did not. You said, and I quote (module formatting): It has _always_ been wrong to compile software only once for different kernel versions (e.g. for compile Linux-2.4 and later install a 2.2 kernel on the so created system). Now that Linux-2.6 introduces incompatible changes to kernel/user interfaces, the resulting binaries will not work correctly anymore. You did not issue a warning, you said it was impossible, and that no matter what kind of program it is, it will never work. As I said before, you should either say that it _may_ not work for software in general, or that it _will_ not work for cdrecord and star. Incidentally, your announcements are still a mess. I keep thinking that the BerliOS Open Source center is a new feature of cdrtools each time I read them. Advertisements should be at the bottom. Well I could put the first line a bit lower, but I cannot understand that people could take the sentence starting with Please have a look... as an announcement for a new feature. Well, your first line reads: NEW features of cdrtools-2.01a22: Generally, a colon is followed by an enumeration of things described. Hence, after reading the first line, I expect new features of cdrtools, not an advertisement for BerliOS. It's rather obvious that it is an advertisement, and not a description of a cdrtools feature, but that doesn't make it any better. Lourens -- GPG public key: http://home.student.utwente.nl/l.e.veen/lourens.key -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: How to contact Jörg Schilling? - cdrecord.1 patch
On Thu 8 January 2004 13:59, Joerg Schilling wrote: From: Lourens Veen [EMAIL PROTECTED] On Wed 7 January 2004 17:49, Jens Seidel wrote: Hi, PS: If you reply to this mail I'm willing to help polishing your website. Most of your .html files look weird! (Is .html or sgml, ... the source of it?) Have a look at http://cdrecord.berlios.de/test/ That's what I built a while ago, but I got stuck on no replies by Jörg, due to him having suspended cdrtools development for a while then. He seems to be back at it again, but I don't have time to work on it anymore at present. If you want to take over you're more than welcome. Well, I did contact you twice (about half a year ago) and you signalled to me that you are no longer interested. I should have mentioned that I did get a reply eventually, but had moved on to other things by then. The way I described it makes it sound more negative than I intended; I did not mean this to sound like an attack at you, just a description of what happened. I'm sorry if it came across that way. As your draft is only a skeleton, it currently cannot replace the old web page. Agreed. That's why I'm hoping someone else steps up to finish it. Lourens -- GPG public key: http://home.student.utwente.nl/l.e.veen/lourens.key -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: cdrtools-2.01a22 ready
On Thu 8 January 2004 16:24, Joerg Schilling wrote: From: Lourens Veen [EMAIL PROTECTED] No, you did not. You said, and I quote (module formatting): It has _always_ been wrong to compile software only once for different kernel versions (e.g. for compile Linux-2.4 and later install a 2.2 kernel on the so created system). Why do you repeat this? The current discussion proves that you cannot expect more than 1% of the audience to understand the background. There is so much confusion in this thread that it's getting funny :-). For this reason, it is better to write a general warning. It _is_ wrong to assume that a random program compiled for OS revision A will run correctly on OS revision B Yes. I agree completely. My point is not that you _shouldn't_, my point is that you _didn't_. That is why I quoted you. Incidentally, you cut off the second part of that quote, which was really the problematic portion. This first part is fine. Lourens -- GPG public key: http://home.student.utwente.nl/l.e.veen/lourens.key -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: cdrtools-2.01a22 ready
On Thu 8 January 2004 17:07, Matthias Schniedermeyer wrote: On Thu, Jan 08, 2004 at 04:24:22PM +0100, Joerg Schilling wrote: It _is_ wrong to assume that a random program compiled for OS revision A will run correctly on OS revision B Definetly NOT. e.g. grep. Aaargh! Perhaps we should communicate in proposition logic instead af English? Jörg is right, it is wrong to assume that any random program compiled for OS revision A will run correctly on OS revision B. If you disagree, you have to show that every single possible program _will_ work, not just give one example. Lourens -- GPG public key: http://home.student.utwente.nl/l.e.veen/lourens.key -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: cdrtools-2.01a22 ready
On Thu 8 January 2004 18:42, Matthias Schniedermeyer wrote: On Thu, Jan 08, 2004 at 05:37:33PM +0100, Lourens Veen wrote: On Thu 8 January 2004 17:07, Matthias Schniedermeyer wrote: On Thu, Jan 08, 2004 at 04:24:22PM +0100, Joerg Schilling wrote: It _is_ wrong to assume that a random program compiled for OS revision A will run correctly on OS revision B Definetly NOT. e.g. grep. Aaargh! Perhaps we should communicate in proposition logic instead af English? Jörg is right, it is wrong to assume that any random program compiled for OS revision A will run correctly on OS revision B. If you disagree, you have to show that every single possible program _will_ work, not just give one example. If you say it this way, then you even have to say: You can't assume that a random programm compiled for OS Revision A.0.0.0.0.0 will run correctly on OS revision A.0.0.0.0.1 They MAY be a subtle bug that prevents the 10thousands program to run correctly. Agreed. Ofcourse, if you start assuming that there are bugs, anything might happen and the entire discussion is moot. Lourens -- GPG public key: http://home.student.utwente.nl/l.e.veen/lourens.key -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: cdrtools-2.01a22 ready
On Thu 8 January 2004 20:10, Scott Bronson wrote: Arguing about MAY vs WILL and the proper use of a colon is just a waste of time don't you think? How does any of this noticeably impact _your_ life? Well, the original statement was false (at least IMHO, it seems we disagree a bit, about what the statement was, whether it was true, and about another zillion things that are somehow related :-), although we do seem to agree that some programs will work between kernel versions, and others won't). If someone acts on it and then posts here, then we'll have to help them solve the problem. Better to get it correct in the first place. As for the BerliOS advertisement, I've been looking at it for a long time now, and it just bugs me. If I'm promised new features, I want new features, not an advert. After all, I'm not watching television. Also, Jörg spends a lot of time and effort making cdrtools into a high-quality professional set of tools, and I think it's a shame that the presentation is the way it is. Any chance this thread can be put to rest here? Well it is getting silly I guess, and I think everyone now basically believes the same thing, but we can't seem to convince one another that we all agree. Just letting it go doesn't seem like a bad idea really... Lourens -- GPG public key: http://home.student.utwente.nl/l.e.veen/lourens.key -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: How to contact Jörg Schilling? - cdrecord.1 patch
On Thu 8 January 2004 13:59, Joerg Schilling wrote: From: Lourens Veen [EMAIL PROTECTED] On Wed 7 January 2004 17:49, Jens Seidel wrote: Hi, PS: If you reply to this mail I'm willing to help polishing your website. Most of your .html files look weird! (Is .html or sgml, ... the source of it?) Have a look at http://cdrecord.berlios.de/test/ That's what I built a while ago, but I got stuck on no replies by Jörg, due to him having suspended cdrtools development for a while then. He seems to be back at it again, but I don't have time to work on it anymore at present. If you want to take over you're more than welcome. Well, I did contact you twice (about half a year ago) and you signalled to me that you are no longer interested. I should have mentioned that I did get a reply eventually, but had moved on to other things by then. The way I described it makes it sound more negative than I intended; I did not mean this to sound like an attack at you, just a description of what happened. I'm sorry if it came across that way. As your draft is only a skeleton, it currently cannot replace the old web page. Agreed. That's why I'm hoping someone else steps up to finish it. Lourens -- GPG public key: http://home.student.utwente.nl/l.e.veen/lourens.key
Re: cdrtools-2.01a22 ready
On Thu 8 January 2004 16:24, Joerg Schilling wrote: From: Lourens Veen [EMAIL PROTECTED] No, you did not. You said, and I quote (module formatting): It has _always_ been wrong to compile software only once for different kernel versions (e.g. for compile Linux-2.4 and later install a 2.2 kernel on the so created system). Why do you repeat this? The current discussion proves that you cannot expect more than 1% of the audience to understand the background. There is so much confusion in this thread that it's getting funny :-). For this reason, it is better to write a general warning. It _is_ wrong to assume that a random program compiled for OS revision A will run correctly on OS revision B Yes. I agree completely. My point is not that you _shouldn't_, my point is that you _didn't_. That is why I quoted you. Incidentally, you cut off the second part of that quote, which was really the problematic portion. This first part is fine. Lourens -- GPG public key: http://home.student.utwente.nl/l.e.veen/lourens.key
Re: cdrtools-2.01a22 ready
On Thu 8 January 2004 18:42, Matthias Schniedermeyer wrote: On Thu, Jan 08, 2004 at 05:37:33PM +0100, Lourens Veen wrote: On Thu 8 January 2004 17:07, Matthias Schniedermeyer wrote: On Thu, Jan 08, 2004 at 04:24:22PM +0100, Joerg Schilling wrote: It _is_ wrong to assume that a random program compiled for OS revision A will run correctly on OS revision B Definetly NOT. e.g. grep. Aaargh! Perhaps we should communicate in proposition logic instead af English? Jörg is right, it is wrong to assume that any random program compiled for OS revision A will run correctly on OS revision B. If you disagree, you have to show that every single possible program _will_ work, not just give one example. If you say it this way, then you even have to say: You can't assume that a random programm compiled for OS Revision A.0.0.0.0.0 will run correctly on OS revision A.0.0.0.0.1 They MAY be a subtle bug that prevents the 10thousands program to run correctly. Agreed. Ofcourse, if you start assuming that there are bugs, anything might happen and the entire discussion is moot. Lourens -- GPG public key: http://home.student.utwente.nl/l.e.veen/lourens.key
Re: cdrtools-2.01a22 ready
On Thu 8 January 2004 20:10, Scott Bronson wrote: Arguing about MAY vs WILL and the proper use of a colon is just a waste of time don't you think? How does any of this noticeably impact _your_ life? Well, the original statement was false (at least IMHO, it seems we disagree a bit, about what the statement was, whether it was true, and about another zillion things that are somehow related :-), although we do seem to agree that some programs will work between kernel versions, and others won't). If someone acts on it and then posts here, then we'll have to help them solve the problem. Better to get it correct in the first place. As for the BerliOS advertisement, I've been looking at it for a long time now, and it just bugs me. If I'm promised new features, I want new features, not an advert. After all, I'm not watching television. Also, Jörg spends a lot of time and effort making cdrtools into a high-quality professional set of tools, and I think it's a shame that the presentation is the way it is. Any chance this thread can be put to rest here? Well it is getting silly I guess, and I think everyone now basically believes the same thing, but we can't seem to convince one another that we all agree. Just letting it go doesn't seem like a bad idea really... Lourens -- GPG public key: http://home.student.utwente.nl/l.e.veen/lourens.key
Re: cdrtools-2.01a22 ready
On Wed 7 January 2004 11:37, Joerg Schilling wrote:
For all people who have enough background knowledge in software
engineering, here is a text that I did write for another purpose:
/*---
---*/
star -tv /tmp/cdev.tar.bz2
star: WARNING: Archive is 'bzip2' compressed, trying to
use the -bz option.
star: Blocksize = 7 records.
Release star 1.5a35 (i386-pc-solaris2.9)
Archtypeexustar
Dumpdate1073336802.243055000 (Mon Jan 5 22:06:42 2004)
Volno 1
Blocksize 20
255 7000 crw-r--r-- 1 root/other Jan 5 22:06 2004 cdev
star: 1 blocks + 0 bytes (total of 3584 bytes = 3.50k).
AS you see, this is a tar archive that includes a character
special with major 255 and minor 7000. You can list the correct
major/minor numbers on any OS if you use star -tv, as the content
of the tar archive is kernel interface independent.
If you unpack this on a Linux-2.6 system using a star binary
that has been compiled on Linux-2.4, you will extract a character
special with minor 88 instead of minor 7000.
This proves that you cannot run binaries from Linux-2.4 on
Linux-2.6 correctly.
Well, it proves that you cannot run _some_ binaries that were
compiled under linux 2.4 on linux 2.6 correctly.
If you compile on Linux-2.6, there is a big chance that the
autoconf run will detect interfaces that are not present on
Linux-2.4, so trying the other direction will most likely give
just other problems.
I am sorry, but the current work on the Linux kernel is
overshadowed by severe missunderstandings. Linus and other people
from LKML seem to be unable to understand how interfaces work.
Let me explain it to you. There are three types of interfaces,
you can see in libc and /usr/include/*:
1)Interfaces that are fully created by libc, such as strcpy()
2)Interfaces that are defined by the kernel but propagated by
libc. Interfaces of this type are things similar to
open()/read()/write(),..
3)Interfaces that libc is not even aware of (like ioctl()
functions). If major()/minor()/makedev() are CPP macros and not
functions in libc, then they are part of this group of
interfaces.
Not necessarily. If the macros only call functions in libc, then
they're in category 1. But I see your point.
Interfaces of type 1) are independent of the kernel and for this
reason, the statements from Linus on how (from his belief)
include files should be treatened apply _only_ to these
interfaces.
To allow an application to match the interface, you need an
include file that is published by the same instance or person who
does work on libc.
Interfaces of type 2) require that libc and the kernel version
match. This means, that you need to recompile and in some cases
even to modify the libc sources in order to get a working
complete system every time the kernel interface (used by libc)
changes. This is needed to keep the upper level interface from
libc stable.
Interfaces of type 3) are independent of libc!
Any application that likes to use them, _needs_ to use the
include files from the kernel they are going to be run on. This
is the only way, to make sure that the user level application
uses an interface that matches the adjacent interface from the
kernel. If you use different include files, you are unable to
even test the kernel interface. For this reason, it is important
that all include files from the kernel (that define interfaces
that are visible from user land) are written in a way that allows
a consistent usage from a user land application (which does never
#define __KERNEL or similar).
Cdrecord is definitely a user land application that needs to be
compiled with the include files from the current kernel -
otherwise it could not e.g. use new features from SCSI drivers
inside the kernel.
Star with respect to device major/minor handling is another one.
There are most likely a lot more user land applications that will
observe incompatibilities from changes in the Linux kernel
interfaces.
Ofcourse, but are they a majority? There aren't that many programs
that talk directly to hardware. There aren't that many programs
that create device files. This email program manages some files on
the disk and it makes some network connections and that's it. Other
office software likely doesn't do this either. And audio and video
servers such as MAS or X abstract away from the hardware, so that
client programs don't use the kernel interface directly either.
I could live with Do not use cdrtools on a different kernel than it
was compiled against or even I don't recommend using software
with a different kernel than it was compiled under. Simply stating
that it will never work...well, try this:
#include stdio.h
int main()
{
printf(Hello, world!\n);
}
Compile under 2.4, run under 2.6. I'm sure it'll work fine, because
it falls in your category 1 above.
Incidentally, your
Re: How to contact Jörg Schilling? - cdrecord.1 patch
On Wed 7 January 2004 17:49, Jens Seidel wrote: Hi, PS: If you reply to this mail I'm willing to help polishing your website. Most of your .html files look weird! (Is .html or sgml, ... the source of it?) Have a look at http://cdrecord.berlios.de/test/ That's what I built a while ago, but I got stuck on no replies by Jörg, due to him having suspended cdrtools development for a while then. He seems to be back at it again, but I don't have time to work on it anymore at present. If you want to take over you're more than welcome. Lourens -- GPG public key: http://home.student.utwente.nl/l.e.veen/lourens.key -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: cdrtools-2.01a22 ready
On Wed 7 January 2004 11:37, Joerg Schilling wrote:
For all people who have enough background knowledge in software
engineering, here is a text that I did write for another purpose:
/*---
---*/
star -tv /tmp/cdev.tar.bz2
star: WARNING: Archive is 'bzip2' compressed, trying to
use the -bz option.
star: Blocksize = 7 records.
Release star 1.5a35 (i386-pc-solaris2.9)
Archtypeexustar
Dumpdate1073336802.243055000 (Mon Jan 5 22:06:42 2004)
Volno 1
Blocksize 20
255 7000 crw-r--r-- 1 root/other Jan 5 22:06 2004 cdev
star: 1 blocks + 0 bytes (total of 3584 bytes = 3.50k).
AS you see, this is a tar archive that includes a character
special with major 255 and minor 7000. You can list the correct
major/minor numbers on any OS if you use star -tv, as the content
of the tar archive is kernel interface independent.
If you unpack this on a Linux-2.6 system using a star binary
that has been compiled on Linux-2.4, you will extract a character
special with minor 88 instead of minor 7000.
This proves that you cannot run binaries from Linux-2.4 on
Linux-2.6 correctly.
Well, it proves that you cannot run _some_ binaries that were
compiled under linux 2.4 on linux 2.6 correctly.
If you compile on Linux-2.6, there is a big chance that the
autoconf run will detect interfaces that are not present on
Linux-2.4, so trying the other direction will most likely give
just other problems.
I am sorry, but the current work on the Linux kernel is
overshadowed by severe missunderstandings. Linus and other people
from LKML seem to be unable to understand how interfaces work.
Let me explain it to you. There are three types of interfaces,
you can see in libc and /usr/include/*:
1)Interfaces that are fully created by libc, such as strcpy()
2)Interfaces that are defined by the kernel but propagated by
libc. Interfaces of this type are things similar to
open()/read()/write(),..
3)Interfaces that libc is not even aware of (like ioctl()
functions). If major()/minor()/makedev() are CPP macros and not
functions in libc, then they are part of this group of
interfaces.
Not necessarily. If the macros only call functions in libc, then
they're in category 1. But I see your point.
Interfaces of type 1) are independent of the kernel and for this
reason, the statements from Linus on how (from his belief)
include files should be treatened apply _only_ to these
interfaces.
To allow an application to match the interface, you need an
include file that is published by the same instance or person who
does work on libc.
Interfaces of type 2) require that libc and the kernel version
match. This means, that you need to recompile and in some cases
even to modify the libc sources in order to get a working
complete system every time the kernel interface (used by libc)
changes. This is needed to keep the upper level interface from
libc stable.
Interfaces of type 3) are independent of libc!
Any application that likes to use them, _needs_ to use the
include files from the kernel they are going to be run on. This
is the only way, to make sure that the user level application
uses an interface that matches the adjacent interface from the
kernel. If you use different include files, you are unable to
even test the kernel interface. For this reason, it is important
that all include files from the kernel (that define interfaces
that are visible from user land) are written in a way that allows
a consistent usage from a user land application (which does never
#define __KERNEL or similar).
Cdrecord is definitely a user land application that needs to be
compiled with the include files from the current kernel -
otherwise it could not e.g. use new features from SCSI drivers
inside the kernel.
Star with respect to device major/minor handling is another one.
There are most likely a lot more user land applications that will
observe incompatibilities from changes in the Linux kernel
interfaces.
Ofcourse, but are they a majority? There aren't that many programs
that talk directly to hardware. There aren't that many programs
that create device files. This email program manages some files on
the disk and it makes some network connections and that's it. Other
office software likely doesn't do this either. And audio and video
servers such as MAS or X abstract away from the hardware, so that
client programs don't use the kernel interface directly either.
I could live with Do not use cdrtools on a different kernel than it
was compiled against or even I don't recommend using software
with a different kernel than it was compiled under. Simply stating
that it will never work...well, try this:
#include stdio.h
int main()
{
printf(Hello, world!\n);
}
Compile under 2.4, run under 2.6. I'm sure it'll work fine, because
it falls in your category 1 above.
Incidentally, your
Re: How to contact Jörg Schilling? - cdrecord.1 patch
On Wed 7 January 2004 17:49, Jens Seidel wrote: Hi, PS: If you reply to this mail I'm willing to help polishing your website. Most of your .html files look weird! (Is .html or sgml, ... the source of it?) Have a look at http://cdrecord.berlios.de/test/ That's what I built a while ago, but I got stuck on no replies by Jörg, due to him having suspended cdrtools development for a while then. He seems to be back at it again, but I don't have time to work on it anymore at present. If you want to take over you're more than welcome. Lourens -- GPG public key: http://home.student.utwente.nl/l.e.veen/lourens.key
Re: Problem with LG cd-rw HL-DT-ST GCE-8520B
On Sun 28 December 2003 13:03, Mihai Florescu wrote: Hi, The problem is that the cd-rw can't copy from a cd to hard disk anything. This happens only in Windows XP. Strange is that in XP can write to a cd without any trouble. I don't know what to do. I tried to go to the LG site but it seems it doesn't work. Another strange thing is that Windows tells me that everything is in order. Now i'm operating Windows 2000 Pro and everything with the cd-rw is ok. Please help me. Erm, this mailinglist is about writing CD's and DVD's under UNIX, most often Linux. Unless you want help upgrading to Linux or some other UNIX, I don't think we can help you. Lourens -- GPG public key: http://home.student.utwente.nl/l.e.veen/lourens.key -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Problem with LG cd-rw HL-DT-ST GCE-8520B
On Sun 28 December 2003 13:03, Mihai Florescu wrote: Hi, The problem is that the cd-rw can't copy from a cd to hard disk anything. This happens only in Windows XP. Strange is that in XP can write to a cd without any trouble. I don't know what to do. I tried to go to the LG site but it seems it doesn't work. Another strange thing is that Windows tells me that everything is in order. Now i'm operating Windows 2000 Pro and everything with the cd-rw is ok. Please help me. Erm, this mailinglist is about writing CD's and DVD's under UNIX, most often Linux. Unless you want help upgrading to Linux or some other UNIX, I don't think we can help you. Lourens -- GPG public key: http://home.student.utwente.nl/l.e.veen/lourens.key
Re: I/O Magic idvdrw4db
On Thu 18 December 2003 17:38, Geoffrey wrote: Andy Polyakov wrote: As it's SANYO/Optorite unit, you probably should keep in mind issues discussed in Dual format DVD burner drive problem thread. Summary there is that DVD+RW support (and DVD+RW support only to my best knowledge) appears to be deficient, more details are soon to come [workaround is being worked on]. A. Is there an archive of this thread? Try http://lists.debian.org/cdwrite/2003/cdwrite-200312/threads.html Lourens -- GPG public key: http://home.student.utwente.nl/l.e.veen/lourens.key
Re: LF-D311 support?
On Wed 10 December 2003 06:15, James Lancaster wrote: Any idea if this is supported (doesn't seem to be working) DVD-RAM/DVD-R drive (write speed on DVD-R is 1x) currently burns under cdrecord-prodvd but I would like to use it under k3b. Well, k3b is just a GUI frontend. It uses dvd+rw-tools to do the burning, so what you really want to know is whether it works with dvd+rw-tools. So, have you tried to burn with growisofs and if so, what were the results? See http://fy.chalmers.se/~appro/linux/DVD+RW/ for more information about dvd+rw-tools and a tutorial. Lourens -- GPG public key: http://home.student.utwente.nl/l.e.veen/lourens.key -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: LF-D311 support?
On Wed 10 December 2003 17:55, Joerg Schilling wrote: From: James Lancaster [EMAIL PROTECTED] Any idea if this is supported (doesn't seem to be working) DVD-RAM/DVD-R drive (write speed on DVD-R is 1x) currently burns under cdrecord-prodvd but I would like to use it under k3b. I am Off-list, so if anyone replies a cc would be apreciated :) If anyone needs me to try anything out I am perfectly willing to. You did not tell us what you like to do. How should it be possible to answer. Both DVD-RAM and DVD-R are supported as mentioned in the information for cdrtools. If you have problems due to firmware bugs, you should send a note... That does not compute. Please re-read the original post and reconsider your answer. Lourens -- GPG public key: http://home.student.utwente.nl/l.e.veen/lourens.key -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: LF-D311 support?
On Wed 10 December 2003 20:45, Joerg Schilling wrote: From: Lourens Veen [EMAIL PROTECTED] On Wed 10 December 2003 17:55, Joerg Schilling wrote: From: James Lancaster [EMAIL PROTECTED] Any idea if this is supported (doesn't seem to be working) DVD-RAM/DVD-R drive (write speed on DVD-R is 1x) currently burns under cdrecord-prodvd but I would like to use it under k3b. I am Off-list, so if anyone replies a cc would be apreciated :) If anyone needs me to try anything out I am perfectly willing to. You did not tell us what you like to do. How should it be possible to answer. Both DVD-RAM and DVD-R are supported as mentioned in the information for cdrtools. If you have problems due to firmware bugs, you should send a note... That does not compute. Please re-read the original post and reconsider your answer. What should I change? He did not tell us what he likes to do and we don't know what k3b does. Well, he did. He wants to use his drive with k3b. Of course, problems may also be caused by miss usage of cdrecord by k3b, but if he is interested in k3b problems, he should ask the authors. Well, incidentally, k3b doesn't use cdrecord at all for DVD burning, it uses dvd+rw-tools. Here we are on another problem: as the k3b authors never did try to get into contact with me and I know from many contacts with Thomas Neiderreither that it is not simple to design a gui the right way. So I stand with my first mail: If the OP tells me what he does at cdrecord level, I may be able to help. I'm not sure what you mean by that, the k3b authors should ask you how to design a GUI? I find k3b quite intuitive and easy to use actually. The problem with your reply was that he was asking for support for his drive with k3b. The only thing he said about cdrecord-ProDVD was that it worked fine. After which you asked him what was wrong specifically. Well, nothing... Lourens -- GPG public key: http://home.student.utwente.nl/l.e.veen/lourens.key -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: LF-D311 support?
On Wed 10 December 2003 06:15, James Lancaster wrote: Any idea if this is supported (doesn't seem to be working) DVD-RAM/DVD-R drive (write speed on DVD-R is 1x) currently burns under cdrecord-prodvd but I would like to use it under k3b. Well, k3b is just a GUI frontend. It uses dvd+rw-tools to do the burning, so what you really want to know is whether it works with dvd+rw-tools. So, have you tried to burn with growisofs and if so, what were the results? See http://fy.chalmers.se/~appro/linux/DVD+RW/ for more information about dvd+rw-tools and a tutorial. Lourens -- GPG public key: http://home.student.utwente.nl/l.e.veen/lourens.key
Re: LF-D311 support?
On Wed 10 December 2003 17:55, Joerg Schilling wrote: From: James Lancaster [EMAIL PROTECTED] Any idea if this is supported (doesn't seem to be working) DVD-RAM/DVD-R drive (write speed on DVD-R is 1x) currently burns under cdrecord-prodvd but I would like to use it under k3b. I am Off-list, so if anyone replies a cc would be apreciated :) If anyone needs me to try anything out I am perfectly willing to. You did not tell us what you like to do. How should it be possible to answer. Both DVD-RAM and DVD-R are supported as mentioned in the information for cdrtools. If you have problems due to firmware bugs, you should send a note... That does not compute. Please re-read the original post and reconsider your answer. Lourens -- GPG public key: http://home.student.utwente.nl/l.e.veen/lourens.key
Re: LF-D311 support?
On Wed 10 December 2003 20:45, Joerg Schilling wrote: From: Lourens Veen [EMAIL PROTECTED] On Wed 10 December 2003 17:55, Joerg Schilling wrote: From: James Lancaster [EMAIL PROTECTED] Any idea if this is supported (doesn't seem to be working) DVD-RAM/DVD-R drive (write speed on DVD-R is 1x) currently burns under cdrecord-prodvd but I would like to use it under k3b. I am Off-list, so if anyone replies a cc would be apreciated :) If anyone needs me to try anything out I am perfectly willing to. You did not tell us what you like to do. How should it be possible to answer. Both DVD-RAM and DVD-R are supported as mentioned in the information for cdrtools. If you have problems due to firmware bugs, you should send a note... That does not compute. Please re-read the original post and reconsider your answer. What should I change? He did not tell us what he likes to do and we don't know what k3b does. Well, he did. He wants to use his drive with k3b. Of course, problems may also be caused by miss usage of cdrecord by k3b, but if he is interested in k3b problems, he should ask the authors. Well, incidentally, k3b doesn't use cdrecord at all for DVD burning, it uses dvd+rw-tools. Here we are on another problem: as the k3b authors never did try to get into contact with me and I know from many contacts with Thomas Neiderreither that it is not simple to design a gui the right way. So I stand with my first mail: If the OP tells me what he does at cdrecord level, I may be able to help. I'm not sure what you mean by that, the k3b authors should ask you how to design a GUI? I find k3b quite intuitive and easy to use actually. The problem with your reply was that he was asking for support for his drive with k3b. The only thing he said about cdrecord-ProDVD was that it worked fine. After which you asked him what was wrong specifically. Well, nothing... Lourens -- GPG public key: http://home.student.utwente.nl/l.e.veen/lourens.key
Re: LF-D311 support?
On Wed 10 December 2003 22:28, Joerg Schilling wrote: From [EMAIL PROTECTED] Wed Dec 10 22:05:42 2003 Of course, problems may also be caused by miss usage of cdrecord by k3b, but if he is interested in k3b problems, he should ask the authors. Well, incidentally, k3b doesn't use cdrecord at all for DVD burning, it uses dvd+rw-tools. How should I know? I don't see why you should. I didn't either, I looked it up on their page. Perhaps the question should be why you assumed that they used cdrecord-ProDVD. Here we are on another problem: as the k3b authors never did try to get into contact with me and I know from many contacts with Thomas Neiderreither that it is not simple to design a gui the right way. So I stand with my first mail: If the OP tells me what he does at cdrecord level, I may be able to help. I'm not sure what you mean by that, the k3b authors should ask you how to design a GUI? I find k3b quite intuitive and easy to use actually. Well, they e.g. use cdrdao which leads to the assumption that they don't know how to _use_ cdrecord. Hmm, that makes sense actually. Like I use Linux because I don't understand how to use Windows, or my mum drives a Nissan because she doesn't understand how to use an Opel. Also, I don't see how being able to design a good GUI and knowing how to use cdrecord are related. The point of having a GUI is to hide as much technical complexity from the user as possible, and provide them with an interface that matches their understanding of the task they want to perform. How the underlying technology works is only relevant insofar as it has an impact on the actions the user can perform. For example, when burning an iso9660 CD-R you need to burn a whole session at a time, you can't just go around adding and deleting files at random like on a random access medium. The interface needs to reflect this, it can't allow random writing and deleting and overwriting to the medium, because that is technically impossible. Designing user interfaces requires knowledge of the limits of the technology, cognitive psychology, and user interface standards, and a good lot of careful testing in a usability lab. Designing a mental model that fits the technology and is easy to understand, and designing a user interface that suggests that mental model to the user and correctly supports its use is hard indeed. Comparing xcdroast and k3b, it's clear that xcdroast is a thin shell that allows you to use cdrecord and mkisofs without touching the keyboard, while k3b is a cd creation program that uses cdrecord and mkisofs to implement a part of the required functionality. The problem with your reply was that he was asking for support for his drive with k3b. The only thing he said about cdrecord-ProDVD was that it worked fine. After which you asked him what was wrong specifically. Well, nothing... You should reread the OP. Thei is not true: He did send s cdrecord -prcap output from the Non DVD enabled version and asked _if_ (not how) it works. This is why I did send my reply with the question. Quote the original post: === Subject: LF-D311 support? Any idea if this is supported (doesn't seem to be working) DVD-RAM/DVD-R drive (write speed on DVD-R is 1x) currently burns under cdrecord-prodvd but I would like to use it under k3b. === Now this could have been a bit more verbose and it could have been an actual English sentence, but I don't see how you can interpret this to mean Does the LF-D311 work with cdrecord-ProDVD?, since he explicitly mentions the answer to that question, that is, it works. The alternative interpretation, that he wants to know if the drive is supported for use with k3b, makes a lot more sense. He mentions that it works with cdrecord-ProDVD, and he includes some information about the drive in the form of -prcap output so that Andy knows what kind of drive it is. Lourens -- GPG public key: http://home.student.utwente.nl/l.e.veen/lourens.key
Re: Fehler beim cd-schreiben
On Fri 5 December 2003 21:04, Robert Schwede wrote: hallo, cdrecord hat mir grade gesagt, dass ich Ihnen eine email schreiben soll. Es ist der unbekannte Fehler 254 aufgetreten. Sorry, this mailinglist is English-only, so I'm going to translate your question and answer in English. See http://www.debian.org/MailingLists/ for more information. Translation: Hello, cdrecord told me to write you an email. Unknown error 254 has occurred. Answer: Well, I'm not a cdrecord developer, but that doesn't give all that much information. What operating system are you using, what version of cdrecord, what were you trying to do when you got the error, what was the full output, etc. See http://www.fokus.gmd.de/research/cc/glone/employees/joerg.schilling/private/problems.html for information on what to include. Lourens -- GPG public key: http://home.student.utwente.nl/l.e.veen/lourens.key -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Fehler beim cd-schreiben
On Fri 5 December 2003 21:04, Robert Schwede wrote: hallo, cdrecord hat mir grade gesagt, dass ich Ihnen eine email schreiben soll. Es ist der unbekannte Fehler 254 aufgetreten. Sorry, this mailinglist is English-only, so I'm going to translate your question and answer in English. See http://www.debian.org/MailingLists/ for more information. Translation: Hello, cdrecord told me to write you an email. Unknown error 254 has occurred. Answer: Well, I'm not a cdrecord developer, but that doesn't give all that much information. What operating system are you using, what version of cdrecord, what were you trying to do when you got the error, what was the full output, etc. See http://www.fokus.gmd.de/research/cc/glone/employees/joerg.schilling/private/problems.html for information on what to include. Lourens -- GPG public key: http://home.student.utwente.nl/l.e.veen/lourens.key
Re: New Lite-On 4X DVD plus/dash RW drive
On Mon 1 December 2003 16:26, Joerg Schilling wrote: From: Clarence Wilkerson [EMAIL PROTECTED] Pardon me. I've missed the discussion of dvdrecord and non GPL compliance. But I was trying out my new Lite-On DVD writer this last weekend ( $80 after rebates at Best Buy ). With dvdrecord, it would not detect as a dvd, but only as a cd. It also gave me certain scsi command errors. Is this a known problem with the Lite-On and dvdrecord? a dvd This list is not the place to discuss problems of this dvdrecord it has plenty of known problems and the self called maintainter does not fix them And if you want Jörg's earlier comments, see http://www.mail-archive.com/[EMAIL PROTECTED]/msg02397.html Lourens -- GPG public key: http://home.student.utwente.nl/l.e.veen/lourens.key -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: New Lite-On 4X DVD plus/dash RW drive
On Mon 1 December 2003 16:26, Joerg Schilling wrote: From: Clarence Wilkerson [EMAIL PROTECTED] Pardon me. I've missed the discussion of dvdrecord and non GPL compliance. But I was trying out my new Lite-On DVD writer this last weekend ( $80 after rebates at Best Buy ). With dvdrecord, it would not detect as a dvd, but only as a cd. It also gave me certain scsi command errors. Is this a known problem with the Lite-On and dvdrecord? a dvd This list is not the place to discuss problems of this dvdrecord it has plenty of known problems and the self called maintainter does not fix them And if you want Jörg's earlier comments, see http://www.mail-archive.com/cdwrite@other.debian.org/msg02397.html Lourens -- GPG public key: http://home.student.utwente.nl/l.e.veen/lourens.key
Re: cdrecord -scanbus strangeness?
On Fri 28 November 2003 23:24, Ambrose Li wrote: Hello, sorry if this is a stupid question. I just downloaded cdrtools-2.01a20pre2 to try out its ATAPI support. (Linux 2.4's ide-scsi seems to be very broken.) I noticed the following: - cdrecord dev=help says bus scanning is supported for the ATAPI transport; - However, if I run cdrecord -scanbus, I just get snip See README.ATAPI in the source distro. Lourens -- GPG public key: http://home.student.utwente.nl/l.e.veen/lourens.key -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: LG GSA-4040B and dvdwrite
On Mon 24 November 2003 13:20, Ole Jacob Taraldset wrote: I'm trying to get my LG GSA-4040B attached to a RedHat 8 box burn a iso doing dvdrecord -v dev=0,0,0 -dao -dummy /iso/shrike-i386-disc1.iso, but nothing is written and I'm note sure what the error is. The disk is a DVD-R. dvdrecord is ancient and doesn't seem to be supported really. I'd recommend growisofs (see http://fy.chalmers.se/~appro/linux/DVD+RW/) or cdrecord-ProDVD (see http://www.fokus.gmd.de/research/cc/glone/employees/joerg.schilling/private/cdrecord.html) Lourens -- GPG public key: http://home.student.utwente.nl/l.e.veen/lourens.key -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: LG GSA-4040B and dvdwrite
On Mon 24 November 2003 13:20, Ole Jacob Taraldset wrote: I'm trying to get my LG GSA-4040B attached to a RedHat 8 box burn a iso doing dvdrecord -v dev=0,0,0 -dao -dummy /iso/shrike-i386-disc1.iso, but nothing is written and I'm note sure what the error is. The disk is a DVD-R. dvdrecord is ancient and doesn't seem to be supported really. I'd recommend growisofs (see http://fy.chalmers.se/~appro/linux/DVD+RW/) or cdrecord-ProDVD (see http://www.fokus.gmd.de/research/cc/glone/employees/joerg.schilling/private/cdrecord.html) Lourens -- GPG public key: http://home.student.utwente.nl/l.e.veen/lourens.key
Re: DVD recording adventures continued
On Wed 19 November 2003 10:13, Andy Polyakov wrote: As pointed out in another thread (look for Plextor PX-504A can't write 2nd session at http://lists.debian.org/cdwrite/2003/cdwrite-200311/threads.html) the error code of , or F/FF/FF for that matter, essentially means that there was a communication problem between kernel and recording unit. At transport level I'd say. In that case it was some kind of USB-IDE gadget which caused the trouble (user confirmed this in private mail). No, I'm not saying that you have USB-IDE gadget too, but it doesn't change that fact that it's a failure at transport level. Might be firmware deficiency, might be IDE misconfiguration in your system: kernel: hdc: ATAPI reset timed-out, status=0x80 kernel: ide1: reset: master: ECC circuitry error *** resulting coaster (not recognized by any system) INQUIRY:[PLEXTOR ][DVDR PX-708A ][1.02] - [unable to READ DVD STRUCTURE#0 (52400)] Can I suggest a bad IDE cable as a possible cause? Noise on the cable might lead to ECC errors I'd say. Lourens -- GPG public key: http://home.student.utwente.nl/l.e.veen/lourens.key -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: problems with xcdroast + ide-scsi
On Tue 18 November 2003 23:22, Volker Kuhlmann wrote: I can't. xcdroast doesn't recognize non-SCSI devices, that's why I've switched to SCSI Hmm, and neither does readcd on inspection. readcd pretty much supports the same device specification as cdrecord, which means IDE drives can be accessed with dev=ATAPI:x,y,z. Run cdrecord dev=ATAPI: -scanbus. Unfortunately using ATAPI: changes the designation of the SCSI devices, so you have to memorise 2 sets of numbers (IMO device names could be seriously improved). Aha. Yeah, that works. Thanks! Lourens -- GPG public key: http://home.student.utwente.nl/l.e.veen/lourens.key
Re: DVD recording adventures continued
On Wed 19 November 2003 10:13, Andy Polyakov wrote: As pointed out in another thread (look for Plextor PX-504A can't write 2nd session at http://lists.debian.org/cdwrite/2003/cdwrite-200311/threads.html) the error code of , or F/FF/FF for that matter, essentially means that there was a communication problem between kernel and recording unit. At transport level I'd say. In that case it was some kind of USB-IDE gadget which caused the trouble (user confirmed this in private mail). No, I'm not saying that you have USB-IDE gadget too, but it doesn't change that fact that it's a failure at transport level. Might be firmware deficiency, might be IDE misconfiguration in your system: kernel: hdc: ATAPI reset timed-out, status=0x80 kernel: ide1: reset: master: ECC circuitry error *** resulting coaster (not recognized by any system) INQUIRY:[PLEXTOR ][DVDR PX-708A ][1.02] - [unable to READ DVD STRUCTURE#0 (52400)] Can I suggest a bad IDE cable as a possible cause? Noise on the cable might lead to ECC errors I'd say. Lourens -- GPG public key: http://home.student.utwente.nl/l.e.veen/lourens.key
Re: problems with xcdroast + ide-scsi
On Tue 18 November 2003 21:15, obarrot wrote: Random thoughts: - Try getting the latest version of cdrtools, and compile and install them from source I'll try what you suggest Okay. I'm starting to suspect the kernel and/or setup though, so this is probably not top priority. - From your lsmod output, ide-scsi isn't loaded? that's right. it's a copy/paste typo Ok. - The error message Warning: controller returns wrong size for CD capabilities page. could be due to a firmware bug - The output from readcd you pasted seems to be fine. Does it read it correctly? no, the PC freezes after a few minutes and the output can't be read with -o loop Hmm. Freezing, but only after a few minutes. Could be an IRQ problem, but then that's done by the controller, not the drive. Maybe a chipset problem? See below... - DGB10: readtoc: no MMC seems to say that the drive is not MMC compliant. If this is an old Goldstar drive, you may need the gscd.o kernel module. - How is the drive attached to the system? What kind of mainboard do you have? you're right, it's an old IDE ATAPI Goldstar drive attached on the mother board ctler (secondary slave) I also have a Traxdata CD writer attached to SCSI (only device in the chain). My MB is a DFI K6BV3+, VIA MVP3 chipset + with K6-2/500 Make sure you've got VIA chipset support enabled in your kernel, and perhaps enable PCI Quirks as well. See Documentation/sound/VIA-chipset about that. - Does it work without ide-scsi, ie with ide-cd? If so, you could add the line yes, it used to work that way before I swithed to ide-scsi.o. I'll try the gscd.o driver options ide-cd ignore=hdx with hdx the device of your writer, to use the reader with ide-cd and the writer with ide-scsi. This is not a solution, but may be a workaround. I can't. xcdroast doesn't recognize non-SCSI devices, that's why I've switched to SCSI Hmm, and neither does readcd on inspection. Sorry about that, it works for me because I only use my reader to rip audio CDs with cdparanoia, and my burner to burn ISOs from the net, and backups. If I want to read an image off a CD, I just use the burner. But ofcourse that's no good for on-the-fly copying. Anyway, I'd go with the kernel configuration first. If that doesn't work, I suggest asking for help on lkml, this sounds like a kernel/hardware problem rather than a problem with readcd. Lourens -- GPG public key: http://home.student.utwente.nl/l.e.veen/lourens.key
Re: DVD+/-R writers
On Mon 17 November 2003 15:37, Jose Casasnovas wrote: Which double format DVD writers can be used under Linux?? Is Sony supported?? I was wondering on drivers and software to run those writers under Linux. In case of a single format DVD writer, which format (+R or -R) is recommended to be run under Linux?? See http://fy.chalmers.se/~appro/linux/DVD+RW/ for a lot of information on DVD writing on Linux. Lourens -- GPG public key: http://home.student.utwente.nl/l.e.veen/lourens.key -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: problems with xcdroast + ide-scsi
On Mon 17 November 2003 22:50, obarrot wrote: Hi, I can't use my CD-ATAPI cdrom with xcdroast + the ide-scsi.o module I had to disable DMA on this CD drive as any operation on the device freezed totally the machine! now I can mount acccess this /dev/sg1 device ok but readcd does detect a garbled disk: a music disk instead of a data disk (see below) any hints? thanks snip Random thoughts: - Try getting the latest version of cdrtools, and compile and install them from source - From your lsmod output, ide-scsi isn't loaded? - The error message Warning: controller returns wrong size for CD capabilities page. could be due to a firmware bug - The output from readcd you pasted seems to be fine. Does it read it correctly? - xcdroast doesn't seem to detect anything, it just starts cdda2wav. Although it seems that you snipped some output. Could you try without XCDRoast? That would give some more legible output as well as remove a potential source of error - DGB10: readtoc: no MMC seems to say that the drive is not MMC compliant. If this is an old Goldstar drive, you may need the gscd.o kernel module. - How is the drive attached to the system? What kind of mainboard do you have? - Does it work without ide-scsi, ie with ide-cd? If so, you could add the line options ide-cd ignore=hdx with hdx the device of your writer, to use the reader with ide-cd and the writer with ide-scsi. This is not a solution, but may be a workaround. Lourens -- GPG public key: http://home.student.utwente.nl/l.e.veen/lourens.key -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: DVD+/-R writers
On Mon 17 November 2003 15:37, Jose Casasnovas wrote: Which double format DVD writers can be used under Linux?? Is Sony supported?? I was wondering on drivers and software to run those writers under Linux. In case of a single format DVD writer, which format (+R or -R) is recommended to be run under Linux?? See http://fy.chalmers.se/~appro/linux/DVD+RW/ for a lot of information on DVD writing on Linux. Lourens -- GPG public key: http://home.student.utwente.nl/l.e.veen/lourens.key
Re: problems with xcdroast + ide-scsi
On Mon 17 November 2003 22:50, obarrot wrote: Hi, I can't use my CD-ATAPI cdrom with xcdroast + the ide-scsi.o module I had to disable DMA on this CD drive as any operation on the device freezed totally the machine! now I can mount acccess this /dev/sg1 device ok but readcd does detect a garbled disk: a music disk instead of a data disk (see below) any hints? thanks snip Random thoughts: - Try getting the latest version of cdrtools, and compile and install them from source - From your lsmod output, ide-scsi isn't loaded? - The error message Warning: controller returns wrong size for CD capabilities page. could be due to a firmware bug - The output from readcd you pasted seems to be fine. Does it read it correctly? - xcdroast doesn't seem to detect anything, it just starts cdda2wav. Although it seems that you snipped some output. Could you try without XCDRoast? That would give some more legible output as well as remove a potential source of error - DGB10: readtoc: no MMC seems to say that the drive is not MMC compliant. If this is an old Goldstar drive, you may need the gscd.o kernel module. - How is the drive attached to the system? What kind of mainboard do you have? - Does it work without ide-scsi, ie with ide-cd? If so, you could add the line options ide-cd ignore=hdx with hdx the device of your writer, to use the reader with ide-cd and the writer with ide-scsi. This is not a solution, but may be a workaround. Lourens -- GPG public key: http://home.student.utwente.nl/l.e.veen/lourens.key
Re: cdrtools-2.01a19 - strange errors
On Wed 12 November 2003 11:16, Helmut Jarausch wrote: Hi, I have a seldomly used PlexWriter 24/10/40A . Using cdrtools-2.01a19 and different media I always get strange errors: The cd is written without any error messages. But comparing it to the orignal I get mismatches always at a bytes with offset n*2048 where n is integer. Has anybody any idea? (Previously, at least with previous versions of cdrtools this drive worked OK) Could you give some more information? Like the command line you use to burn the CD, and how you compare them. What OS are you using? Lastly, when you say that it works with previous versions, do you mean earlier alpha versions, or the latest stable release? Could you try to find out in what version things went broke? Lourens -- GPG public key: http://home.student.utwente.nl/l.e.veen/lourens.key -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: cdrtools-2.01a19 - strange errors
On Wed 12 November 2003 11:33, Helmut Jarausch wrote: I can't remember the version, but I'm quite sure it was a 2.01a* version. I'll try to use the driver under Win2K first, to check if it's a hardware problem. Okay. How do you compare the CD to the original? Read it out with readcd and then do a cmp on the images? Or using cmp on the device directly? Lourens -- GPG public key: http://home.student.utwente.nl/l.e.veen/lourens.key -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: cdrtools-2.01a19 - strange errors
On Wed 12 November 2003 11:16, Helmut Jarausch wrote: Hi, I have a seldomly used PlexWriter 24/10/40A . Using cdrtools-2.01a19 and different media I always get strange errors: The cd is written without any error messages. But comparing it to the orignal I get mismatches always at a bytes with offset n*2048 where n is integer. Has anybody any idea? (Previously, at least with previous versions of cdrtools this drive worked OK) Could you give some more information? Like the command line you use to burn the CD, and how you compare them. What OS are you using? Lastly, when you say that it works with previous versions, do you mean earlier alpha versions, or the latest stable release? Could you try to find out in what version things went broke? Lourens -- GPG public key: http://home.student.utwente.nl/l.e.veen/lourens.key
Re: cdrtools-2.01a19 - strange errors
On Wed 12 November 2003 11:33, Helmut Jarausch wrote: I can't remember the version, but I'm quite sure it was a 2.01a* version. I'll try to use the driver under Win2K first, to check if it's a hardware problem. Okay. How do you compare the CD to the original? Read it out with readcd and then do a cmp on the images? Or using cmp on the device directly? Lourens -- GPG public key: http://home.student.utwente.nl/l.e.veen/lourens.key
Re: problems with growisofs on Fedora 1.0
On Sat 8 November 2003 22:22, Maciek Kozyrczak wrote: Hi, I am wondering if any 'growisofs' users have upgraded their distros to Fedora 1.0. I have a Sony DRU-510A drive that I had working under Red Hat 9.0. After upgrading to Fedora 1.0, I recompiled the dvd tool chain, just to ensure library compatibility. But neither the RH9-compiled nor the Fedora-compiled versions of 'growisofs' have been producing reliable burns on Fedora 1.0. I don't end up with any errors during the burn, but reading back the burned disk gives me input/output errors. Is anyone out there experiencing similar problems? Thanks, Maciek Kozyrczak PS: I'm almost suspecting the ide-scsi layer, but I have no evidence to support this. The reason I'm suspicious is because I can only burn CD-Rs in my Plextor drive in RAW mode (cdrecord), or else I also get I/O errors on read-back. Is there some known issue with the 'sg' driver? Well for starters, see this thread: http://www.mail-archive.com/[EMAIL PROTECTED]/msg04512.html I did some more experimentation after that, and found out that the disc that gave I/O errors actually had three tracks, not one. Another disc that had only one track worked perfectly. I haven't had time to do more research and figure out what that means and how to fix it though. Lourens -- GPG public key: http://home.student.utwente.nl/l.e.veen/lourens.key -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: problems with growisofs on Fedora 1.0
On Sat 8 November 2003 22:22, Maciek Kozyrczak wrote: Hi, I am wondering if any 'growisofs' users have upgraded their distros to Fedora 1.0. I have a Sony DRU-510A drive that I had working under Red Hat 9.0. After upgrading to Fedora 1.0, I recompiled the dvd tool chain, just to ensure library compatibility. But neither the RH9-compiled nor the Fedora-compiled versions of 'growisofs' have been producing reliable burns on Fedora 1.0. I don't end up with any errors during the burn, but reading back the burned disk gives me input/output errors. Is anyone out there experiencing similar problems? Thanks, Maciek Kozyrczak PS: I'm almost suspecting the ide-scsi layer, but I have no evidence to support this. The reason I'm suspicious is because I can only burn CD-Rs in my Plextor drive in RAW mode (cdrecord), or else I also get I/O errors on read-back. Is there some known issue with the 'sg' driver? Well for starters, see this thread: http://www.mail-archive.com/cdwrite@other.debian.org/msg04512.html I did some more experimentation after that, and found out that the disc that gave I/O errors actually had three tracks, not one. Another disc that had only one track worked perfectly. I haven't had time to do more research and figure out what that means and how to fix it though. Lourens -- GPG public key: http://home.student.utwente.nl/l.e.veen/lourens.key
Re: DVDs created with too large files
On Mon 3 November 2003 00:06, Volker Kuhlmann wrote: But can a file span multiple extents? The way I read the comment Gary quoted, it's legal to have an image that is over 2GB in size, as long as each file inside that image is no larger than 2GB. Careful - the comment was about mkisofs, although it was in the kernel source. It definitely says file*systems* 2GB are legal, otherwise it says mkisofs can't handle single *files* 2GB - that doesn't necessarily mean they're illegal. The comment may also be old and no longer true for current versions of standards. Good point. [...] That seems to me like the only logical way to explain why the comment says it's legal, but the code claims it's illegal to have files that are more than 2GB in size. You're mixing up file with filesystem here? Erm, actually, what I said doesn't make sense at all. Never mind... so apparently at least someone looked at ISO Level 3 support. I'd say send a message to linux-kernel and see what they say about it... Yes, together with a raft of other iso9660 issues :( Perhaps mkisofs is now able to handle files 2GB, the lack of a suitable error when creating the filesystem does suggest so. However, for Linux that's a moot point as Linux doesn't handle 2GB, but mkisofs isn't only used on Linux. Thanks Gary for the warning about that. Linux in general does have large file support now doesn't it? Incidentally, I had a quick look at the same file in 2.6.0-test9, but apart from adding support for compressed iso9660 filesystems (zisofs?) and some stuff apparently to do with multisession handling nothing much seems to have changed here. Lourens -- GPG public key: http://home.student.utwente.nl/l.e.veen/lourens.key -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: DVDs created with too large files
On Mon 3 November 2003 00:06, Volker Kuhlmann wrote: But can a file span multiple extents? The way I read the comment Gary quoted, it's legal to have an image that is over 2GB in size, as long as each file inside that image is no larger than 2GB. Careful - the comment was about mkisofs, although it was in the kernel source. It definitely says file*systems* 2GB are legal, otherwise it says mkisofs can't handle single *files* 2GB - that doesn't necessarily mean they're illegal. The comment may also be old and no longer true for current versions of standards. Good point. [...] That seems to me like the only logical way to explain why the comment says it's legal, but the code claims it's illegal to have files that are more than 2GB in size. You're mixing up file with filesystem here? Erm, actually, what I said doesn't make sense at all. Never mind... so apparently at least someone looked at ISO Level 3 support. I'd say send a message to linux-kernel and see what they say about it... Yes, together with a raft of other iso9660 issues :( Perhaps mkisofs is now able to handle files 2GB, the lack of a suitable error when creating the filesystem does suggest so. However, for Linux that's a moot point as Linux doesn't handle 2GB, but mkisofs isn't only used on Linux. Thanks Gary for the warning about that. Linux in general does have large file support now doesn't it? Incidentally, I had a quick look at the same file in 2.6.0-test9, but apart from adding support for compressed iso9660 filesystems (zisofs?) and some stuff apparently to do with multisession handling nothing much seems to have changed here. Lourens -- GPG public key: http://home.student.utwente.nl/l.e.veen/lourens.key
Re: DVDs created with too large files
On Sun 2 November 2003 19:03, ljknews wrote: At 5:27 PM + 11/2/03, Gary Houston wrote: I have been using dvd+rw-tools (5.13.4.7.4) and mkisofs (cdrtools 1.11a29) to write backups to DVD. This generally works. However I encountered a problem when one of the files was 2351679431 bytes in size: the disk was written with no errors reported, but on testing proved to be unreadable to linux 2.4.21. On mounting the disk a warning was reported: Warning: defective CD-ROM. Enabling cruft mount option. Defective CD-ROM is a misleading statement. Interchange Level 3 ISO-9660 volumes are not handled by this OS would be more accurate. /* * The ISO-9660 filesystem only stores 32 bits for file size. But the ISO-9660 _standard_ stores 32 bits for the size of each _extent_ and there can be a virtually unlimited number of _extents_ in a single file at ISO-9660 Interchange Level 3. But can a file span multiple extents? The way I read the comment Gary quoted, it's legal to have an image that is over 2GB in size, as long as each file inside that image is no larger than 2GB. I haven't actually read the spec though. But then the whole comment seems odd. It looks to me like the WARNING was added later, and written by Jörg. That seems to me like the only logical way to explain why the comment says it's legal, but the code claims it's illegal to have files that are more than 2GB in size. Lastly, at the top of the file, there is * 1998 Eric Lammerts - ISO 9660 Level 3 so apparently at least someone looked at ISO Level 3 support. I'd say send a message to linux-kernel and see what they say about it... Lourens -- GPG public key: http://home.student.utwente.nl/l.e.veen/lourens.key -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: DVDs created with too large files
On Sun 2 November 2003 19:03, ljknews wrote: At 5:27 PM + 11/2/03, Gary Houston wrote: I have been using dvd+rw-tools (5.13.4.7.4) and mkisofs (cdrtools 1.11a29) to write backups to DVD. This generally works. However I encountered a problem when one of the files was 2351679431 bytes in size: the disk was written with no errors reported, but on testing proved to be unreadable to linux 2.4.21. On mounting the disk a warning was reported: Warning: defective CD-ROM. Enabling cruft mount option. Defective CD-ROM is a misleading statement. Interchange Level 3 ISO-9660 volumes are not handled by this OS would be more accurate. /* * The ISO-9660 filesystem only stores 32 bits for file size. But the ISO-9660 _standard_ stores 32 bits for the size of each _extent_ and there can be a virtually unlimited number of _extents_ in a single file at ISO-9660 Interchange Level 3. But can a file span multiple extents? The way I read the comment Gary quoted, it's legal to have an image that is over 2GB in size, as long as each file inside that image is no larger than 2GB. I haven't actually read the spec though. But then the whole comment seems odd. It looks to me like the WARNING was added later, and written by Jörg. That seems to me like the only logical way to explain why the comment says it's legal, but the code claims it's illegal to have files that are more than 2GB in size. Lastly, at the top of the file, there is * 1998 Eric Lammerts - ISO 9660 Level 3 so apparently at least someone looked at ISO Level 3 support. I'd say send a message to linux-kernel and see what they say about it... Lourens -- GPG public key: http://home.student.utwente.nl/l.e.veen/lourens.key
Re: Sarge netinst: CD-RW Sony CRX175A1
On Wed 29 October 2003 19:58, Dani wrote: Hi. I'm netinstalling Debian Sarge from a minimal CD. I boot the CD and it fails to autodetect the CD drive, maybe because it's a CD-RW. It's Sony CRX175A1. The installation show me the following list of kernel modules: aztcd, cdu31a, cm206, gscd, isp16, mcd, mcdx, optcd, sbpcd, sjcd, sonycd535. Which may I choose? I suspect that none of the above because my drive is CD-RW. These kernel modules are not for your drive, they're for old interfaces that a drive may be attached to. If your drive is simply attached to the IDE on your mainboard as is usually the case, then you need none of the above modules, but you do need the other CD related drivers, and ide-scsi and related modules if you want to burn CDs as well as read them. If your CD drive is connected to an old soundcard or other multimedia card, you should find out its type and select the appropriate driver from the list. HTH, Lourens -- GPG public key: http://home.student.utwente.nl/l.e.veen/lourens.key -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: readcd fails on ATAPI drive
On Fri 24 October 2003 18:28, Ashish Rangole wrote: I am trying to read a CD that I burnt on a ATAPI CD writer. The cdrecord dev=ATAPI: -scanbus tells me that the writer device is: 0,0,0 'HL-DT-ST' 'RW/DVD GCC-4240N' 'E112' Removable CD-ROM When I run readcd: readcd dev=ATAPI:0,0,0 f=readback.iso , I get the following error message: readcd: Invalid argument. Can not send SCSI cmd via ioctl I am enclosing the dmesg output for more details. Please advise me what I am doing wrong and how I can correct the problem. What OS do you have? What driver are you using? Do you have an automounter running? Lourens -- GPG public key: http://home.student.utwente.nl/l.e.veen/lourens.key
Re: linux kernel error reading end of cd/dvd
On Wed 15 October 2003 16:19, Joerg Schilling wrote: From: Andy Polyakov [EMAIL PROTECTED] [...] 75 blocks exist nowhere in a seek related paper The basic position accuracy (without starting to read!) for a CD player must be 2 seconds (150 sectors). This is why at least 150 sectors of lead out are required to prevent the drive from hitting the outer barrier. That makes sense. Do you know for sure whether the capacity that is returned by READ CAPACITY is actually supposed (as in according to the SCSI bus spec) to be sector accurate? Lourens -- GPG public key: http://home.student.utwente.nl/l.e.veen/lourens.key -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: linux kernel error reading end of cd/dvd
On Wed 15 October 2003 16:19, Joerg Schilling wrote: From: Andy Polyakov [EMAIL PROTECTED] [...] 75 blocks exist nowhere in a seek related paper The basic position accuracy (without starting to read!) for a CD player must be 2 seconds (150 sectors). This is why at least 150 sectors of lead out are required to prevent the drive from hitting the outer barrier. That makes sense. Do you know for sure whether the capacity that is returned by READ CAPACITY is actually supposed (as in according to the SCSI bus spec) to be sector accurate? Lourens -- GPG public key: http://home.student.utwente.nl/l.e.veen/lourens.key
