Re: cdrecord floating point exception
Hi, > It's not quite the same and also FreeBSD-specific. You don't want that. FreeBSD is the other operating system which the libburnia project supports. The bad-hald-experience reports were all from scdbackup users on Linux of different ages and distros. Before hald there were other disturbing automats. > BTW, for testing if/how hald stomps over writing: can I trigger hald > corruption by just writing some data to CD-RW on a modern (MMC) DVD writer > (NEC) while hald is probing? This depends on the ever changing habits of hald when and how to probe. I once straced one on a SuSE 9 kernel 2.6 system (i.e. an hald early version). It opened with and without O_EXCL several times after the tray was loaded. After some time it ended teasing the drive. So a good reciepe seems to be to let the burn program load the tray and to set eventual gracetime=0. The mishap usually happens during the first 100 MB. But somtimes later. Do not expect this to be deterministic. My experiments yielded failure with about 50% of the tries. On SuSE 10.2 it seems to be more reliably ill. And of course, lots of media are immune: DVD+RW, formatted DVD-RW, DVD-RAM, BD-RE. I never saw anything fail other than CD but did not test DVD-R[W], DVD+R, BD-R for that. > "PHONE CARD", unmountable by FreeBSD+GNOME+HAL Just naive. Have a nice day :) Thomas -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@other.debian.org
Re: cdrecord floating point exception
Am 04.02.2009, 12:07 Uhr, schrieb Thomas Schmitt : Hi, Matthias Andree wrote: http://www.freebsd.org/gnome/docs/halfaq.html#q2 I'll put that into libburn docs. It's not quite the same and also FreeBSD-specific. You don't want that. Johannes Meixner's comment quoted by Matthias https://bugzilla.novell.com/show_bug.cgi?id=438867#c23 "Why the hell is this HAL stuff always all the time changing arbitrarily ..." I can only join in with his lament. Since i hear about hald it is ever changing. Well - it's only a small part of the story; read for instance Comments #44, #48, 51 in the same bug (quoted above) - apparently HAL fails to provide the promised abstraction and exposes kernel internals - which subverts the whole point of "abstraction". My very convenient killing of particular hald-addon-storage processes does not work for several users of my programs. They simply see no such processes. Only the failures. Which operating system does this happen on? Darwin, FreeBSD, NetBSD, DragonflyBSD, openSolaris, Linux version X, Linux version Y, are all very different beasts. FreeBSD's GEOM layer has several, um, let's put it mildly, "interesting" interactions. Write 0-length to a device to reprobe for labels. If you don't do that, you miss the "slices" (partitions in Linux lingo). Same for optical media, although it doesn't hurt you here to not have label and partitions -- these media are unpartitioned. But woe betide the poor soul who has a media with blanks in its label. SonyEricsson phone somewhere? My Memory Stick was dubbed "PHONE CARD", unmountable by FreeBSD+GNOME+HAL due to alleged hal bugs. Luckily, my phone (W810i) doesn't care, so relabeling PHONE_CARD did the job. The mess begins already with the project docs which naturally assume that everybody is using a Mac-Windows-style computer which by accident is based on Linux. I never bothered to check the background of the freedesktop folks. If HAL shall be a central system component then it must have a stable C API and a stable model of operations. Seems rather a mix-and-match for everything. Some kernel info here, some kernel internals exposed there, gazillions of device-specific "20thirdparty" annotations to fill in missing info because HAL apparently can't identify subdevices in the same physical case (All-in-one-printers seem very common here), policy there. Hm. I should have a second look if I were really interested in this. Another group of developers to blame are those who began to depend on hald without first insisting in said model and API. That's IMO what let hald dependencies proliferate. Depend on something that's not finished. OTOH, it's good that vendor-specific hacks such as resmgr are going away now. But there's a lot of half-baked stuff around. PolicyKit (which together with pulseaudio bug prevented my running the latter with real-time scheduling on FreeBSD), HAL, and more cruft. BTW, for testing if/how hald stomps over writing: can I trigger hald corruption by just writing some data to CD-RW on a modern (MMC) DVD writer (NEC) while hald is probing? -- Matthias Andree -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@other.debian.org
Re: cdrecord floating point exception
Hi, Matthias Andree wrote: > http://www.freebsd.org/gnome/docs/halfaq.html#q2 I'll put that into libburn docs. Johannes Meixner's comment quoted by Matthias > https://bugzilla.novell.com/show_bug.cgi?id=438867#c23 > "Why the hell is this HAL stuff always all the time changing > arbitrarily ..." I can only join in with his lament. Since i hear about hald it is ever changing. My very convenient killing of particular hald-addon-storage processes does not work for several users of my programs. They simply see no such processes. Only the failures. The mess begins already with the project docs which naturally assume that everybody is using a Mac-Windows-style computer which by accident is based on Linux. If HAL shall be a central system component then it must have a stable C API and a stable model of operations. Another group of developers to blame are those who began to depend on hald without first insisting in said model and API. I understand why a central device manager is appealing. I would like to join in. But not under these technical conditions, and actually not so enthusiastically with a project that appears quite naive. Systemwide device management should not depend on anything else than the core system. It is a bit like with CD burning: Actually a task for the operating system, not for user applications. For some reason, the Linux kernel code has a large hole of exactly the shape of a sequential burn facility. So we small people from userland have our peculiar SCSI playground :)) Have a nice day :) Thomas -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@other.debian.org
Re: cdrecord floating point exception
Hi, Rob Bogus wrote: > There is no doubt that a system can run without hald, if you assume that the > administrator is willing to do the same things by hand, and the user > understands how to do all the things which hald typically does. Personally i am a non-admin and leave my SuSEs quite as they come out of the box. Up to one year ago i had no hald running (SuSE 9 with kernel 2.4) and really did not miss it in any way. The only device automat i want is the USB plug-and-pull recognizer. That worked already on the old SuSEs without hald. I am not curious enough to explore whether hald is involved meanwhile. What i experienced at the first day of 10.2 was CD-RW burn failure due to hald-addon-storage processes. One per drive. They confessed by telling the drive addresses in ps output. Although i do not see it as necessary and do not like its behavior, i acknowledge that hald is there and that a burn program should seek coordination with it. > either using applications which understand hald > or making a simple one time change in the hald config. Any pointer to tutorial documentaion is higly welcome. Topics of interest: - Sysadmin: How to keep hald away from the CD burner ? (I would point from libburn docs to that.) - Burn programmer (C language, console environment): How to negociate with hald in order to either get exclusivity at the drive or to learn that it is already occupied ? What i would deem not acceptable for a burn program: - unstable API form and semantics - fat desktop libraries - non-C languages Have a nice day :) Thomas -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@other.debian.org
Re: cdrecord floating point exception
Thomas Schmitt wrote: Hi, Joerg Schilling wrote: If a burner does not like some media, cdrecord usually prints a related SCSI error message. There was no such message in the log send to this list. Parker Jones wrote: Track 01:0 of 4391 MB written.Errno: 5 (Input/output error), write_g1 scsi sendcmd: no error CDB: 2A 00 00 00 00 00 00 00 1F 00 status: 0x2 (CHECK CONDITION) Sense Bytes: 70 00 05 00 00 00 00 0A 00 00 00 00 30 10 00 00 Sense Key: 0x5 Illegal Request, Segment 0 Sense Code: 0x30 Qual 0x10 (medium not formatted) Fru 0x0 Although this is from wodim the report is obviously about an SCSI error and i would bet it stems from a 1:1 copy of your code. I still believe that there is some other problem like e.g. "hald": hald can make CD/DVD burns fail. But hardly DVD+RW. On overwriteables you can freely mix read and write operations. I do not believe that hald interrupts background formatting. I would also expect from the specs that DVD+R and BD-R can stand hald interference. Both are allowed to have more than one logical track open and you hardly can manage them without intermediate inquiry commands. After system startup i kill the processes named hald-addon-storage. They are the ones on my SuSE 10.2 which quite reliably spoild CD-RW burns. I cannot agree to the opinion that a _modern_ Linux system could not live without hald. It is about the playfulness of the user interface and the incapacitation of its user. There is no doubt that a system can run without hald, if you assume that the administrator is willing to do the same things by hand, and the user understands how to do all the things which hald typically does. And if you are comfortable with the idea that some of these things will require root access. :-( For some special system used only by someone trusted and capable who's time has no value (I find the mix of "time has no value" and "trusted and capable" unlikely), of course you could run that way, Other than as a proof of concept I can't believe that would ever by useful compared with either using applications which understand hald or making a simple one time change in the hald config. -- E. Robert Bogusta It seemed like a good idea at the time -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@other.debian.org
Re: cdrecord floating point exception
The only code that probably could be called free was growisofs, but growisofs at that time was not under GPL (altough the Author claimed so) because commercial publishing was not allowed. Growisofs is now free, but the change to a real free license was made after the complete cdrecord source was published under a free license. dvd+rw-tools were available under same license, GPL, all along, and nothing has changed "after the complete cdrecord source was published under a free license." I suppose the above comment refers to http://fy.chalmers.se/~appro/linux/DVD+RW/solaris.com.html. Quoting it: "The agreement is not meant to encumber GPL-compliant usage of the sofware in question, for example no explicit permission/license is required, if the same party chooses to download and deploy it internally in their Solaris environment, e.g. for backup purposes, or even re-distribute it under GPL terms." I can assure that this was the intention from the moment of agreement, I believe you that you may have intended to have it be free. The named limitation however caused e.g. Sun to make an agreement with you before Sun started to publish growisofs. So at least Sun also had the impression that the license situation was unclear. If there was an obvious and definitive GPL on growisofs, Sun did just take it. The situation in Germany is definitively that a Judge would take the named limitytion as an expression of will from the author that is wheighted more heavy than the GPL. This is amongst others, because the GPL is a license written by other people. I fail to understand point with these rants. Why do you undertake role of interpreter of an agreement that doesn't concern you? Have you experienced legal problems using dvd+rw-tools? Or do you perhaps represent [or represented at the time] Sun's interests? Have you been asked for an opinion? If yes, how come they asked you and not me? Are you "a Judge"? Do I need your approval? I bet not. So what is the drift here? Anyway, the above quoted note openly admits that original note was poorly formulated and clarification was provided. I take blame for poor formulation, but [once again] assure that no changes in licensing terms took place at alleged time [or any other time]. Sun indeed contacted Inserve (not me!) and I've got a note about the fact and that Inserve proceeded as agreed. Sun did wonder if notice can be removed from my page, but I left the decision to Inserve. Apparently clarification sufficed. A. -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@other.debian.org
Re: cdrecord floating point exception
Andy Polyakov wrote: > > The only code that probably could be called free was growisofs, but > > growisofs > > at that time was not under GPL (altough the Author claimed so) because > > commercial publishing was not allowed. Growisofs is now free, but the change > > to a real free license was made after the complete cdrecord source was > > published > > under a free license. > > dvd+rw-tools were available under same license, GPL, all along, and > nothing has changed "after the complete cdrecord source was published > under a free license." I suppose the above comment refers to > http://fy.chalmers.se/~appro/linux/DVD+RW/solaris.com.html. Quoting it: > > "The agreement is not meant to encumber GPL-compliant usage of the > sofware in question, for example no explicit permission/license is > required, if the same party chooses to download and deploy it internally > in their Solaris environment, e.g. for backup purposes, or even > re-distribute it under GPL terms." > > I can assure that this was the intention from the moment of agreement, I believe you that you may have intended to have it be free. The named limitation however caused e.g. Sun to make an agreement with you before Sun started to publish growisofs. So at least Sun also had the impression that the license situation was unclear. If there was an obvious and definitive GPL on growisofs, Sun did just take it. The situation in Germany is definitively that a Judge would take the named limitytion as an expression of will from the author that is wheighted more heavy than the GPL. This is amongst others, because the GPL is a license written by other people. Jörg -- EMail:jo...@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin j...@cs.tu-berlin.de(uni) joerg.schill...@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@other.debian.org
Re: cdrecord floating point exception
On Mo, 02 Feb 2009, Joerg Schilling wrote: > > > cdrecord-ProDVD becomes free for everyone > > > > > > later, someone takes parts of the cdrecord DVD code by reverse > > > engineering and > > > publishes patches that cause cdrecord to fail even with CD media. > > > > You are lying: Proof: > > > > From your website: ftp://ftp.berlios.de/pub/cdrecord/ProDVD/README: > > > > NOTE: the DVD-recording drivers have been added to the OpenSource > > part on May 15th 2006 with cdrtools-2.01.01a09. > > > > That was 2006. > > > > The first patch for adding DVD support to cdrecord I found in 1min > > searching was for cdrecord 1.11a08: > > http://www.abcpages.com/~mache/cdrecord-dvd.html > > cdrecord 1.11 was already released before 2001. At that time > > cdrecord-ProDVD was for sure not free. > > This is rather just another poor dumb attempt for lying from you! > > The code you are referring has been created by reverse engineering cdrecord. > It has been published 2 weeks _after_ cdrecord-ProDVD was available for free. Your wording: "... becomes free for everyone" which includes commercial operations etc etc, which was not true at the time of 2001. Do you disagree? Best wishes Norbert --- Dr. Norbert Preining Vienna University of Technology Debian Developer Debian TeX Group gpg DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094 --- DAMNAGLAUR (n.) A certain facial expression which actors are required to demonstrate their mastery of before they are allowed to play MacBeth. --- Douglas Adams, The Meaning of Liff -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@other.debian.org
Re: cdrecord floating point exception
The only code that probably could be called free was growisofs, but growisofs at that time was not under GPL (altough the Author claimed so) because commercial publishing was not allowed. Growisofs is now free, but the change to a real free license was made after the complete cdrecord source was published under a free license. dvd+rw-tools were available under same license, GPL, all along, and nothing has changed "after the complete cdrecord source was published under a free license." I suppose the above comment refers to http://fy.chalmers.se/~appro/linux/DVD+RW/solaris.com.html. Quoting it: "The agreement is not meant to encumber GPL-compliant usage of the sofware in question, for example no explicit permission/license is required, if the same party chooses to download and deploy it internally in their Solaris environment, e.g. for backup purposes, or even re-distribute it under GPL terms." I can assure that this was the intention from the moment of agreement, to be specific the moment Solaris support made its appearance in dvd+rw-tools in 2003. The note was indeed updated/clarified in 2006, but once again it has nothing to do with any cdrecord time-frame. Well, it might have been affected *indirectly*, as those who asked for clarification at the time might have been confused by misleading claims just like one in the very beginning of this message. A. -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@other.debian.org
Re: cdrecord floating point exception
Norbert Preining wrote: > On Mo, 02 Feb 2009, Joerg Schilling wrote: > > > 1) cdrecord writes to CDs. > > > > > > 2) cdrecord gets DVD writing code added and becomes cdrecord-ProDVD > > > which is not free software. The free version of cdrecord continues > > > to exist, without DVD writing capability. > > > > cdrecord-ProDVD becomes free for everyone > > > > later, someone takes parts of the cdrecord DVD code by reverse engineering > > and > > publishes patches that cause cdrecord to fail even with CD media. > > You are lying: Proof: > > From your website: ftp://ftp.berlios.de/pub/cdrecord/ProDVD/README: > > NOTE: the DVD-recording drivers have been added to the OpenSource > part on May 15th 2006 with cdrtools-2.01.01a09. > > That was 2006. > > The first patch for adding DVD support to cdrecord I found in 1min > searching was for cdrecord 1.11a08: > http://www.abcpages.com/~mache/cdrecord-dvd.html > cdrecord 1.11 was already released before 2001. At that time > cdrecord-ProDVD was for sure not free. This is rather just another poor dumb attempt for lying from you! The code you are referring has been created by reverse engineering cdrecord. It has been published 2 weeks _after_ cdrecord-ProDVD was available for free. This is exactly the time (_after_ cdrecord was made available for everyone) you need to reverse engineer this half hearted code... Jörg -- EMail:jo...@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin j...@cs.tu-berlin.de(uni) joerg.schill...@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@other.debian.org
Re: cdrecord floating point exception
Joerg Schilling schrieb: > Bill Davidsen wrote: > > >>> Try to learn that hald on Linux is broken and acts on wrong status changes. >>> >>> >> Nothing is ever your fault. Instead of learning from the applications >> which burn CDs and DVDs without being root, your software has problems >> with hald and you refuse to accept that changing the hald config fixes >> the problems and others can work with hald as is, and insist hald is at >> fault. >> > > besides the fact that you _need_ root privileges in order to do the tasks > cdrecord does, Not true. 1. You tend to mix up the goal and the way to get there. Your goals are: being permitted to open a device, send raw commands, lock pages into memory, and use real-time scheduling, perhaps more. There is not only one way there. Your way there is to require super user permissions, which means that at the same time you get permission for all privileged operations at the same time. It goes without saying that from a programmer's POV super user permission is an easily solution, since that's universal (not system-specific) thus you need not port this part to different operating systems. 2. You mix up cdrecord's ambitions and those other applications may have. Other applications may decide to restrict their offerings when they cannot obtain all privileges. For instance, an application that cannot obtain realtime permissions and cannot lock pages into memory may refuse to write media that do not allow single-block overwrites. Such applications can still write DVD-whatever. Or, if the user requests reduced quality and enables Burnproof/Justlink/whatever, can still write a CD without realtime scheduling. HOWEVER your wording often reads as though the decisions you made for cdrecord were the only possible ones. That's true for cdrecord and for software that you write, but not for other applications, or other programmers. > I am of course willing to help the hald people to fix their software. > After a bit of behind-the-scenes discussion with Thomas of scdbackup fame, I start wondering if Linux's device access model is up to the task. Let's collect some facts first, before we start pointing fingers at anyone. How do operating systems (Solaris/openSolaris, *BSD, Linux) provide EXCLUSIVE access to a device? I'd naively tend to believe that if MyCdWriteApplication has /dev/blahwriter0 open for exclusive access, no other application should be able to bypass that exclusive reservation. Yet Thomas claims he's seen such things happen. I'm not sure if that's a user-space or kernel-space problem. -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@other.debian.org
Re: cdrecord floating point exception
Sorry to chime in again. Jörg Schilling is playing the funny guy twisting facts again: On Mo, 02 Feb 2009, Joerg Schilling wrote: > > 1) cdrecord writes to CDs. > > > > 2) cdrecord gets DVD writing code added and becomes cdrecord-ProDVD > > which is not free software. The free version of cdrecord continues > > to exist, without DVD writing capability. > > cdrecord-ProDVD becomes free for everyone > > later, someone takes parts of the cdrecord DVD code by reverse engineering and > publishes patches that cause cdrecord to fail even with CD media. You are lying: Proof: >From your website: ftp://ftp.berlios.de/pub/cdrecord/ProDVD/README: NOTE: the DVD-recording drivers have been added to the OpenSource part on May 15th 2006 with cdrtools-2.01.01a09. That was 2006. The first patch for adding DVD support to cdrecord I found in 1min searching was for cdrecord 1.11a08: http://www.abcpages.com/~mache/cdrecord-dvd.html cdrecord 1.11 was already released before 2001. At that time cdrecord-ProDVD was for sure not free. One of the Debian bug reports discussing that #248187 starts Sun, 9 May 2004 for cdrtools release 2.0+a30 Guys please see the the reality WHO is lying here. Or is Schillings missing at least 5 years??? Norbert --- Dr. Norbert Preining Vienna University of Technology Debian Developer Debian TeX Group gpg DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094 --- CAMER (n.) A mis-tossed caber. --- Douglas Adams, The Meaning of Liff -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@other.debian.org
Re: cdrecord floating point exception
Bill Davidsen wrote: > > Try to learn that hald on Linux is broken and acts on wrong status changes. > > > > Nothing is ever your fault. Instead of learning from the applications > which burn CDs and DVDs without being root, your software has problems > with hald and you refuse to accept that changing the hald config fixes > the problems and others can work with hald as is, and insist hald is at > fault. besides the fact that you _need_ root privileges in order to do the tasks cdrecord does, cdrecord exists many years longer than hald. I am of course willing to help the hald people to fix their software. Jörg -- EMail:jo...@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin j...@cs.tu-berlin.de(uni) joerg.schill...@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@other.debian.org
Re: cdrecord floating point exception
Joerg Schilling wrote: Rob Bogus wrote: Joerg Schilling wrote: >From zoubi...@hotmail.com Fri Jan 30 21:07:19 2009 You did not install cdrecord correctly as you see from this messages. Cdrecord needs to be installed suid root in order to be able to open all needed devices and in order to send all needed SCSI commands. When are you going to fix that? Other software can burn without being root, clearly it can be done. If there are better commands to use with a This is a definitive wrong claim. There is No way to correctly write without root privileges. Try to kill hald and retry cdrecord after correctly installing it suid root. Time to learn to use a scalpel instead of a chain saw... You don't just "kill hald" on most modern distributions, things stop working. And the Try to learn that hald on Linux is broken and acts on wrong status changes. Nothing is ever your fault. Instead of learning from the applications which burn CDs and DVDs without being root, your software has problems with hald and you refuse to accept that changing the hald config fixes the problems and others can work with hald as is, and insist hald is at fault. -- Bill Davidsen "Woe unto the statesman who makes war without a reason that will still be valid when the war is over..." Otto von Bismark -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@other.debian.org
Re: cdrecord floating point exception
Greg Wooledge wrote: > > > Perhaps before the name was used, but there was a fork with DVD > > > capability before cdrecord got the ProDVD code. I used it because I had > > > too many problems with the licensing of ProDVD and couldn't get > > > permission to install it. > > > Well, please try to find a proof that someone different did add DVD support > > to cdrecord before February/March 1998. > > You're playing with words. This is the timeline as I remember it: You are playing too > 1) cdrecord writes to CDs. > > 2) cdrecord gets DVD writing code added and becomes cdrecord-ProDVD > which is not free software. The free version of cdrecord continues > to exist, without DVD writing capability. cdrecord-ProDVD becomes free for everyone later, someone takes parts of the cdrecord DVD code by reverse engineering and publishes patches that cause cdrecord to fail even with CD media. > 4) growisofs (dvd+rwtools) comes along, adds DVD writing that works > pretty well. > > 5) cdrecord's DVD writing code is merged into the free version of cdrecord. > License is changed to a different free license. As there never have been two versions of cdrecord, there was of code no merge. > 6) Debian forks "wodim" from an older cdrecord because they're uncertain > of the new license. Not true - sorry. The license that is use with cdrecord was an aproved free license since more than a year at that time. These people never have been uncertain about the license, they just wanted to spread FUD. > Nobody claims their DVD writing code is better than yours or older than > yours. They just claim (correctly) that other code was FREE during a > time when yours was not. The only code that probably could be called free was growisofs, but growisofs at that time was not under GPL (altough the Author claimed so) because commercial publishing was not allowed. Growisofs is now free, but the change to a real free license was made after the complete cdrecord source was published under a free license. > > You will not be able to do this because the official cdrecord DVD support > > has been introduced at a time, when only two other DVD recording programs > > have been available at all, one of them was from Pioneer. At the time > > cdrecord introduced DVD support, only 35 DVD recorders existed in the whole > > world. > > All well and good, but the resulting program was non-free and therefore > many people could not use it, or chose not to use it. It is free NOW, > and thank you for that, but we're discussing the state of affairs during > the time cdrecord-ProDVD was non-free. As I mentioned many times before: There was an NDA at that time and you could not even buy the related writers without a personal permission from the chief of Pioneer. Jörg -- EMail:jo...@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin j...@cs.tu-berlin.de(uni) joerg.schill...@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@other.debian.org
Re: cdrecord floating point exception
> > Perhaps before the name was used, but there was a fork with DVD > > capability before cdrecord got the ProDVD code. I used it because I had > > too many problems with the licensing of ProDVD and couldn't get > > permission to install it. > Well, please try to find a proof that someone different did add DVD support > to cdrecord before February/March 1998. You're playing with words. This is the timeline as I remember it: 1) cdrecord writes to CDs. 2) cdrecord gets DVD writing code added and becomes cdrecord-ProDVD which is not free software. The free version of cdrecord continues to exist, without DVD writing capability. 3) dvdrecord (dvdrtools) forks the free cdrecord and adds DVD writing code that only works for a few drives under a few situations. 4) growisofs (dvd+rwtools) comes along, adds DVD writing that works pretty well. 5) cdrecord's DVD writing code is merged into the free version of cdrecord. License is changed to a different free license. 6) Debian forks "wodim" from an older cdrecord because they're uncertain of the new license. Nobody claims their DVD writing code is better than yours or older than yours. They just claim (correctly) that other code was FREE during a time when yours was not. > You will not be able to do this because the official cdrecord DVD support > has been introduced at a time, when only two other DVD recording programs > have been available at all, one of them was from Pioneer. At the time > cdrecord introduced DVD support, only 35 DVD recorders existed in the whole > world. All well and good, but the resulting program was non-free and therefore many people could not use it, or chose not to use it. It is free NOW, and thank you for that, but we're discussing the state of affairs during the time cdrecord-ProDVD was non-free. -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@other.debian.org
Re: cdrecord floating point exception
"Thomas Schmitt" wrote: > Matthias Andree wrote: > > Debian need not offer resources for someone damaging the project, so how > > about committing to the action you suggested and have Jörg removed? > > Debian generously offers a place for technical > discussions of CD burning affairs (including CD > successor technologies). My due thanks for that. Berlios also offers mailing lists for this purpose. > > cdrecord had better play nice with hald, else cdrecord is going to > > disappear sooner or later for lack of users... > > I would be glad if i knew any documentation > about reliable and stable ways to influence > hald's access to CD devices. > Something like a locking protocol or so. > And maybe without getting dependent on Glib > or Mono. As long as hald tries to mount the media on a not-ready to ready transition, hald is horrobly broken and needs to be fixed first. BTW: hald on Solaris works correctly. > As for being away from the window, look at #3 of > http://freshmeat.net/stats/#popularity > > It's not that easy. > Before cdrecord would vanish due to lack of good > cooexistence with Linux there first would have to The popularity of cdrtools is based on the good coexistence with Linux and maybe because of the bad coexistence of the Debian fork... Other reasons for the popularity are the fact that virtually any Operating system is supported and that reported bugs are usually fixed in less than a week. > be established alternatives. (I could offer some > interesting candidates, btw.) I don't see that your software is a real alternative as it is limited to Linux. There is a difference between feeding a hype and doing long term support for everybody who is interested in a OSS solution. BTW: I am doing more than just cdrtools and I am now supporting most of my software since more than 25 years. > And then one have to make GUI apps and people > go away from cdrecord. Good luck with that part. Why should they go away from cdrecord? The people who write GUIs get a lot of bug reports and know which software causes less problems. The main problem we have in this mailing list is that people like Mr. Andree and Mr. Preining appear from time to time just to spread FUD. They did never contribute anything useful AFAIK. With this background, it is interesting to see that the initiators of the Debian fork fear this mailing list ;-) Jörg -- EMail:jo...@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin j...@cs.tu-berlin.de(uni) joerg.schill...@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@other.debian.org
Re: cdrecord floating point exception
Hi, Matthias Andree wrote: > Debian need not offer resources for someone damaging the project, so how > about committing to the action you suggested and have Jörg removed? Debian generously offers a place for technical discussions of CD burning affairs (including CD successor technologies). My due thanks for that. So please let us ignore any non-technical ornaments rather than making them an issue which obscures the original purpose of this list. One can live well with anybody here if one just does not put too much weight on people's personal way of expression. > cdrecord had better play nice with hald, else cdrecord is going to > disappear sooner or later for lack of users... I would be glad if i knew any documentation about reliable and stable ways to influence hald's access to CD devices. Something like a locking protocol or so. And maybe without getting dependent on Glib or Mono. As for being away from the window, look at #3 of http://freshmeat.net/stats/#popularity It's not that easy. Before cdrecord would vanish due to lack of good cooexistence with Linux there first would have to be established alternatives. (I could offer some interesting candidates, btw.) And then one have to make GUI apps and people go away from cdrecord. Good luck with that part. > and I see that now, three years later, nothing has changed. Hey. Several things have changed: libburn and its apps work for CD, DVD and BD. cdrskin can substitute for cdrecord in most of the CD use cases and outperforms it with DVD and BD. xorriso combines a versatile multi-session ISO 9660 editor with the appropriate burn capabilites. I dare to amend that i myself can now give user support about MMC problems here. I could not have done that 3 years ago. So there has been progress since then. Have a nice day :) Thomas -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@other.debian.org
Re: cdrecord floating point exception
Am Samstag, den 31.01.2009, 16:22 +0100 schrieb Joerg Schilling: > "Thomas Schmitt" wrote: > > > Hi, > > > > > There always was only one cdrecord source code since it's > > > creation in late 1995. The first DVD support code was added in > > > February 1998 but could not be made OpenSource due to an NDA. > > > Anyway, the DVD support in cdrecord code became OpenSource long > > > before the fork "wodim" was created. > > > > Indeed the sequence was > > 1) End of ProDVD (May 2006) > > 2) Fork of cdrkit (Oct 2006) > > > > But the release of ProDVD functionality in cdrtools > > source tarballs marks exactly the point where the > > fork took off: > > http://lists.debian.org/cdwrite/2006/05/msg00021.html > > Here you announce cdrtools-2.01.01a09 and mention CDDL. > > The fork of cdrkit is based on cdrtools-2.01.01a08. > > http://en.wikipedia.org/wiki/Cdrkit > > > > So they probably did not take your DVD code because they > > assumed that it is not under GPL. > > The DVD code of course is not under GPL. > > The Debian people who started the fork claimed that they did this > because they found a GPL violation in cdrecord. > > Judge yourself on whether this is a lie > > > How can cdrecord be in a GPL violation when it is completely licensed > under the aproved free CDDL? AFAIR the point was that Debian considered the new license situation unclear enough that they wanted to avoid being drawn into lawsuits. They're not the original authors or copyright bearers, so mixed licenses or unclear relicensing from GPL to CDDL may be rather harmful for them. I think - someone check the archives - that was the actual concern they've had. > As a hint, one of my other projects "star" is also 100% CDDL and distributed > by Debian without problems. AFAICT, it doesn't have contributions from different parties under different licenses. If you think it's safe that Debian redistribute a CDDL-ed cdrecord, try to convince them, perhaps present evidence that all contributors consent with the license change. Calling people names, or liars, certainly isn't going to convince them... and your view on certain abstraction layers in some open source operating systems, or freedesktop.org abstractions, also make it difficult for them to ship your software. cdrecord often fights against Linux, rather than use its offers. While all the world talks of cross-layer optimization, a certain Jörg Schilling rather discussed weeks over weeks (2005) about one device offering mid- and blocklayer access at the same time... you're what Germans call a "Prinzipienreiter", and that's what makes people think it's hard to work with you. I've tried to moderate once, wasted a lot of time since you were unwilling or uncapable of sticking to objective facts and started to call people impolite terms... and I see that now, three years later, nothing has changed. (I'm not going to try again.) Also, you would refuse some of my bug analyses at the time when cdrecord had hard times. And BTW, not to send too many messages, hald is exactly the device enumerator that interfaces between Desktop and low-layer stuff, operating system APIs and such. hald isn't a Debian or Linux specific, but also used by FreeBSD, for instance. cdrecord had better play nice with hald, else cdrecord is going to disappear sooner or later for lack of users... -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@other.debian.org
Re: cdrecord floating point exception
Am Samstag, den 31.01.2009, 15:13 +0100 schrieb Norbert Preining: > On Sa, 31 Jan 2009, Rob Bogus wrote: > > Maybe you and Dr Norbert could take your pissing contest to email and > > off this list. > > I don't discuss with Mr Schilling (and he not with me). I just want to > get some things straight that are always reiterated here on a Debian > list insulting Debian Developers and the Debian Project. I'd consider this 'biting the hand that feeds you', thus severe and ungraceful ingratitude. Debian need not offer resources for someone damaging the project, so how about committing to the action you suggested and have Jörg removed? Alternatively, someone addressed by Jörg's calling him a liar can file a complaint for libel (Verleumdung in the German penal code) - that's not possible for third parties though, only for the insulted parties. This isn't the first time he's insulting the project that hosts this list (and Debian isn't the only addressee...). -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@other.debian.org
Re: cdrecord floating point exception
"Thomas Schmitt" wrote: > Hi, > > Joerg Schilling wrote: > > If a burner does not like some media, cdrecord usually prints a related SCSI > > error message. There was no such message in the log send to this list. > > Parker Jones wrote: > > > Track 01: 0 of 4391 MB written.Errno: 5 (Input/output error), > > > write_g1 scsi sendcmd: no error > > > CDB: 2A 00 00 00 00 00 00 00 1F 00 > > > status: 0x2 (CHECK CONDITION) > > > Sense Bytes: 70 00 05 00 00 00 00 0A 00 00 00 00 30 10 00 00 > > > Sense Key: 0x5 Illegal Request, Segment 0 > > > Sense Code: 0x30 Qual 0x10 (medium not formatted) Fru 0x0 > > Although this is from wodim the report is > obviously about an SCSI error and i would > bet it stems from a 1:1 copy of your code. But this is from the time _before_ cdrecord formatted the medium. > > > I still believe that there is some other problem like e.g. "hald": > > hald can make CD/DVD burns fail. But hardly > DVD+RW. On overwriteables you can freely hald definitely makes CD writes in SAO Mode fail because it starts to read from the medium while is is still written to. hald may still interrupt other actions by issuing unsynchronized other SCSI commands at the same time when a SCSI command from cdrecord is running. This is is special true for Linux where more than one device driver exists at the same time for the same hardware. For this reason, in any case when the error situation is unclear, it makes sense to do a test where hald is definitely not running. Jörg -- EMail:jo...@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin j...@cs.tu-berlin.de(uni) joerg.schill...@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@other.debian.org
Re: cdrecord floating point exception
Hi, Joerg Schilling wrote: > If a burner does not like some media, cdrecord usually prints a related SCSI > error message. There was no such message in the log send to this list. Parker Jones wrote: > > Track 01: 0 of 4391 MB written.Errno: 5 (Input/output error), > > write_g1 scsi sendcmd: no error > > CDB: 2A 00 00 00 00 00 00 00 1F 00 > > status: 0x2 (CHECK CONDITION) > > Sense Bytes: 70 00 05 00 00 00 00 0A 00 00 00 00 30 10 00 00 > > Sense Key: 0x5 Illegal Request, Segment 0 > > Sense Code: 0x30 Qual 0x10 (medium not formatted) Fru 0x0 Although this is from wodim the report is obviously about an SCSI error and i would bet it stems from a 1:1 copy of your code. > I still believe that there is some other problem like e.g. "hald": hald can make CD/DVD burns fail. But hardly DVD+RW. On overwriteables you can freely mix read and write operations. I do not believe that hald interrupts background formatting. I would also expect from the specs that DVD+R and BD-R can stand hald interference. Both are allowed to have more than one logical track open and you hardly can manage them without intermediate inquiry commands. After system startup i kill the processes named hald-addon-storage. They are the ones on my SuSE 10.2 which quite reliably spoild CD-RW burns. I cannot agree to the opinion that a _modern_ Linux system could not live without hald. It is about the playfulness of the user interface and the incapacitation of its user. Nevertheless it is cumbersome to strip a SuSE Linux from all unnecessary automats. So one better selectively disables those which are known to make trouble. Have a nice day :) Thomas -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@other.debian.org
Re: cdrecord floating point exception
Rob Bogus wrote: > Joerg Schilling wrote: > > >From zoubi...@hotmail.com Fri Jan 30 21:07:19 2009 > > > > > > You did not install cdrecord correctly as you see from this messages. > > Cdrecord needs to be installed suid root in order to be able to open all > > needed > > devices and in order to send all needed SCSI commands. > > > > > When are you going to fix that? Other software can burn without being > root, clearly it can be done. If there are better commands to use with a This is a definitive wrong claim. There is No way to correctly write without root privileges. > > Try to kill hald and retry cdrecord after correctly installing it suid root. > > > > > Time to learn to use a scalpel instead of a chain saw... You don't just > "kill hald" on most modern distributions, things stop working. And the Try to learn that hald on Linux is broken and acts on wrong status changes. Jörg -- EMail:jo...@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin j...@cs.tu-berlin.de(uni) joerg.schill...@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@other.debian.org
Re: cdrecord floating point exception
Rob Bogus wrote: > > It looks as if you are a victim of the FUD spread by Debian :-( > > > > There always was only one cdrecord source code since it's > > creation in late 1995. The first DVD support code was added in > > February 1998 but could not be made OpenSource due to an NDA. > > > > Anyway, the DVD support in cdrecord code became OpenSource long > > before the fork "wodim" was created. > > > > > Perhaps before the name was used, but there was a fork with DVD > capability before cdrecord got the ProDVD code. I used it because I had > too many problems with the licensing of ProDVD and couldn't get > permission to install it. Well, please try to find a proof that someone different did add DVD support to cdrecord before February/March 1998. You will not be able to do this because the official cdrecord DVD support has been introduced at a time, when only two other DVD recording programs have been available at all, one of them was from Pioneer. At the time cdrecord introduced DVD support, only 35 DVD recorders existed in the whole world. Jörg -- EMail:jo...@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin j...@cs.tu-berlin.de(uni) joerg.schill...@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@other.debian.org
Re: cdrecord floating point exception
Mario wrote: > Friends, if we can't live together in harmony, lets just leave each other > alone. Every time, I see a mail from Mr. Preining, I get the impression that he cannot live in harmony woth other people. Jörg -- EMail:jo...@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin j...@cs.tu-berlin.de(uni) joerg.schill...@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@other.debian.org
Re: cdrecord floating point exception
Norbert Preining wrote: > On Sa, 31 Jan 2009, Rob Bogus wrote: > > 1 - that the changes from cdrecord to wodim were done by people called > > "Debian packet maintainer" > > Debian Developers. > > > 2 - that those changes don't introduce bugs (or the failures to work are > > somehow not bugs) > > That they fixed some bugs, and some bugs are still open. Right. They introduced many bugs and it is easy to verify this by looking into the Debian bug tracking system. It lists bugs that never have been in the original software, so it is obvious that the related bugs have been introduced by the people who started the fork. > > 3 - that wodim is distributed under a different and conflicting license > > from the original cdrecord > > ?? You guess WHO changed the license of cdrecord and forced the fork? It > was no Debian Developer. > > The fork was made when the license was still GPL. And there has been > enough discussions on that, and both sides disagree on the validity of > their proper action. These "Debian packet maintainers" introduced changes that are in conflict with GPL and Copyright law. The GPL does not allow to anything you might like to do. You still have to honor the GPL and the Copyright. The related people did not honor GPL and Copyright. Jörg -- EMail:jo...@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin j...@cs.tu-berlin.de(uni) joerg.schill...@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@other.debian.org
Re: cdrecord floating point exception
Rob Bogus wrote: > > I tried cdrecord because growisofs didn't work (see thread about a > > fortnight ago). So this may not be software related. But it would > > still be nice to get a clear error message indicating what has gone wrong. > > I don't think you burner likes this media, but I would suggest > formatting as a separate step, with cdrecord or dvd+rw-format, then > leave off options like "-dao" and let the software pick a mode. If a burner does not like some media, cdrecord usually prints a related SCSI error message. There was no such message in the log send to this list. I still believe that there is some other problem like e.g. "hald": Jörg -- EMail:jo...@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin j...@cs.tu-berlin.de(uni) joerg.schill...@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@other.debian.org
Re: cdrecord floating point exception
"Thomas Schmitt" wrote: > Hi, > > > There always was only one cdrecord source code since it's > > creation in late 1995. The first DVD support code was added in > > February 1998 but could not be made OpenSource due to an NDA. > > Anyway, the DVD support in cdrecord code became OpenSource long > > before the fork "wodim" was created. > > Indeed the sequence was > 1) End of ProDVD (May 2006) > 2) Fork of cdrkit (Oct 2006) > > But the release of ProDVD functionality in cdrtools > source tarballs marks exactly the point where the > fork took off: > http://lists.debian.org/cdwrite/2006/05/msg00021.html > Here you announce cdrtools-2.01.01a09 and mention CDDL. > The fork of cdrkit is based on cdrtools-2.01.01a08. > http://en.wikipedia.org/wiki/Cdrkit > > So they probably did not take your DVD code because they > assumed that it is not under GPL. The DVD code of course is not under GPL. The Debian people who started the fork claimed that they did this because they found a GPL violation in cdrecord. Judge yourself on whether this is a lie How can cdrecord be in a GPL violation when it is completely licensed under the aproved free CDDL? As a hint, one of my other projects "star" is also 100% CDDL and distributed by Debian without problems. Jörg -- EMail:jo...@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin j...@cs.tu-berlin.de(uni) joerg.schill...@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@other.debian.org
Re: cdrecord floating point exception
Joerg Schilling wrote: >From zoubi...@hotmail.com Fri Jan 30 21:07:19 2009 You did not install cdrecord correctly as you see from this messages. Cdrecord needs to be installed suid root in order to be able to open all needed devices and in order to send all needed SCSI commands. When are you going to fix that? Other software can burn without being root, clearly it can be done. If there are better commands to use with a drive a check can be made to see if cdrecord is running as root. Actually I thought that you had provided an option, -mmc or similar, to use only the commands common to the standard. As people become more careful about security fewer systems will allow setuid root programs. Trying to clear drive status. This may be from a drive firmware bug or frim running hald (hald is non-cooperatively). Try to kill hald and retry cdrecord after correctly installing it suid root. Time to learn to use a scalpel instead of a chain saw... You don't just "kill hald" on most modern distributions, things stop working. And the problem is not in hald at all, it's in the rules given to hald for handling the drive, usually a 70_something rule, which you can edit or remove to prevent probing and automounting. This problem looks like firmware or bad media though. -- E. Robert Bogusta It seemed like a good idea at the time -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@other.debian.org
Re: cdrecord floating point exception
On Sa, 31 Jan 2009, Rob Bogus wrote: > Maybe you and Dr Norbert could take your pissing contest to email and > off this list. I don't discuss with Mr Schilling (and he not with me). I just want to get some things straight that are always reiterated here on a Debian list insulting Debian Developers and the Debian Project. Best wishes Norbert --- Dr. Norbert Preining Vienna University of Technology Debian Developer Debian TeX Group gpg DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094 --- MOLESBY (n.) The kind of family that drives to the seaside and then sits in the car with all the windows closed, reading the Sunday Express and wearing sidcups (q.v.) --- Douglas Adams, The Meaning of Liff -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@other.debian.org
Re: cdrecord floating point exception
Norbert Preining wrote: On Fr, 30 Jan 2009, Joerg Schilling wrote: that are responsible for introducing various bugs and license violations call themself "Debian packet maintainer". Stop talking nonsense and lies on a debian list, or I will try to get you banned from that list. What is it that you claim is a lie? 1 - that the changes from cdrecord to wodim were done by people called "Debian packet maintainer" 2 - that those changes don't introduce bugs (or the failures to work are somehow not bugs) 3 - that wodim is distributed under a different and conflicting license from the original cdrecord When you call someone a liar in a public forum, it's good to be able to back up your claim. Best wishes Norbert --- Dr. Norbert Preining Vienna University of Technology Debian Developer Debian TeX Group gpg DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094 --- EWELME (n.) The smile bestowed on you by an air hostess. --- Douglas Adams, The Meaning of Liff -- E. Robert Bogusta It seemed like a good idea at the time
Re: cdrecord floating point exception
Thomas Schmitt wrote: Hi, There always was only one cdrecord source code since it's creation in late 1995. The first DVD support code was added in February 1998 but could not be made OpenSource due to an NDA. Anyway, the DVD support in cdrecord code became OpenSource long before the fork "wodim" was created. Indeed the sequence was 1) End of ProDVD (May 2006) 2) Fork of cdrkit (Oct 2006) But the release of ProDVD functionality in cdrtools source tarballs marks exactly the point where the fork took off: http://lists.debian.org/cdwrite/2006/05/msg00021.html Here you announce cdrtools-2.01.01a09 and mention CDDL. The fork of cdrkit is based on cdrtools-2.01.01a08. http://en.wikipedia.org/wiki/Cdrkit So they probably did not take your DVD code because they assumed that it is not under GPL. But there were other programs capable of burning DVDs before that, based on hacked cdrecord code. They may not have been wodim, or were not called wodim, but they certainly existed. They even worked, if you found the right media for your burner. I don't miss SCSI burners a bit! -- E. Robert Bogusta It seemed like a good idea at the time -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@other.debian.org
Re: cdrecord floating point exception
Joerg Schilling wrote:
"Thomas Schmitt" wrote:
Hi,
The fork (when started in september 2006) removed the
original DVD code and replaced it by something that does not work. I have no
idea why the initiators of the fork replaced working code...
To my observation the timeline was:
- Fork of cdrkit ("cdrecord" became "wodim").
I think that's right, and by big complaint is that they called their
fork "cdrecord" because people didn't use "wodim."
- Introduction of DVD code into the fork
(from program dvdrecord ?).
- Soon later you released the cdrecord-ProDVD
functionality as cdrtools source tarball.
It looks as if you are a victim of the FUD spread by Debian :-(
There always was only one cdrecord source code since it's
creation in late 1995. The first DVD support code was added in
February 1998 but could not be made OpenSource due to an NDA.
Anyway, the DVD support in cdrecord code became OpenSource long
before the fork "wodim" was created.
Perhaps before the name was used, but there was a fork with DVD
capability before cdrecord got the ProDVD code. I used it because I had
too many problems with the licensing of ProDVD and couldn't get
permission to install it.
Why don't you inform yourself from the official cdrecord website?
Official how? It's your version of history, your memory, your inside
information. That doesn't make it right or wrong, but it's no more
official or authoritative than the Debian version or my own
recollection. We did burn DVDs with other software before cdrecord
included the code, if you believe it or not.
Maybe you and Dr Norbert could take your pissing contest to email and
off this list.
As i stated towards Parker Jones:
If growisofs cannot handle drive and media
then there is few hope that others can.
(I deem my programs not worse than growisofs
but they cannot claim to be better when it
comes to DVD writing.)
If you observe the net, you will see that there are many people
who report that they use cdrecord to write DVDs because growisofs
is not working for them..
Jörg
--
E. Robert Bogusta
It seemed like a good idea at the time
Re: cdrecord floating point exception
Friends, if we can't live together in harmony, lets just leave each other alone. Truly yours, M. On Sat, Jan 31, 2009 at 14:47, Norbert Preining wrote: > On Sa, 31 Jan 2009, Rob Bogus wrote: > > 1 - that the changes from cdrecord to wodim were done by people called > > "Debian packet maintainer" > > Debian Developers. > > > 2 - that those changes don't introduce bugs (or the failures to work are > > somehow not bugs) > > That they fixed some bugs, and some bugs are still open. Right. > > > 3 - that wodim is distributed under a different and conflicting license > > from the original cdrecord > > ?? You guess WHO changed the license of cdrecord and forced the fork? It > was no Debian Developer. > > The fork was made when the license was still GPL. And there has been > enough discussions on that, and both sides disagree on the validity of > their proper action. > > But it is ALWAY Mr. Schilling STARTING to tell lies about Debian, not > us. > > Best wishes > > Norbert > > > --- > Dr. Norbert Preining Vienna University of > Technology > Debian Developer Debian TeX > Group > gpg DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 > B094 > > --- > TORONTO (n.) Generic term for anything which comes out of a gush > despite all your careful efforts to let it out gently, e.g. flour into > a white sauce, tomato ketchup on to fried fish, sperm into a human > being, etc. > --- Douglas Adams, The Meaning of Liff > > > -- > To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org > with a subject of "unsubscribe". Trouble? Contact > listmas...@other.debian.org > >
Re: cdrecord floating point exception
On Sa, 31 Jan 2009, Rob Bogus wrote: > 1 - that the changes from cdrecord to wodim were done by people called > "Debian packet maintainer" Debian Developers. > 2 - that those changes don't introduce bugs (or the failures to work are > somehow not bugs) That they fixed some bugs, and some bugs are still open. Right. > 3 - that wodim is distributed under a different and conflicting license > from the original cdrecord ?? You guess WHO changed the license of cdrecord and forced the fork? It was no Debian Developer. The fork was made when the license was still GPL. And there has been enough discussions on that, and both sides disagree on the validity of their proper action. But it is ALWAY Mr. Schilling STARTING to tell lies about Debian, not us. Best wishes Norbert --- Dr. Norbert Preining Vienna University of Technology Debian Developer Debian TeX Group gpg DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094 --- TORONTO (n.) Generic term for anything which comes out of a gush despite all your careful efforts to let it out gently, e.g. flour into a white sauce, tomato ketchup on to fried fish, sperm into a human being, etc. --- Douglas Adams, The Meaning of Liff -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@other.debian.org
Re: cdrecord floating point exception
Parker Jones wrote: Hi Thomas, > It is advisable to use a different program > for DVD purposes. E.g: > growisofs, cdrecord, cdrskin, xorriso. > (I am author of the latter two.) > > DVD+RW should be simply writeable via their > device file. Try: > > dd if=newworld.iso bs=2048 of=/dev/dvd > > Maybe the kernel is smarter than the burn program. I tried this and here's the output: $ dd if=~/newworld.iso bs=2048 of=/dev/dvd dd: writing `/dev/dvd': No space left on device 2+0 records in 1+0 records out 2048 bytes (2.0 kB) copied, 0.080821 s, 25.3 kB/s I guessed this was because the media needed formatting which I did with dvd+rw-format /dev/dvd but the outcome was still the same. I tried cdrecord because growisofs didn't work (see thread about a fortnight ago). So this may not be software related. But it would still be nice to get a clear error message indicating what has gone wrong. I don't think you burner likes this media, but I would suggest formatting as a separate step, with cdrecord or dvd+rw-format, then leave off options like "-dao" and let the software pick a mode. I agree about the messages not be clear to a typical user, but your results with "dd" indicate issues other than the application. -- E. Robert Bogusta It seemed like a good idea at the time
Re: cdrecord floating point exception
On Sa, 31 Jan 2009, Thomas Schmitt wrote: > So they probably did not take your DVD code because they > assumed that it is not under GPL. And right it is. The fork was only done due to the licensing change. Best wishes Norbert --- Dr. Norbert Preining Vienna University of Technology Debian Developer Debian TeX Group gpg DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094 --- ARDCRONY (n.) A remote acquaintance passed off as 'a very good friend of mine' by someone trying to impress people. --- Douglas Adams, The Meaning of Liff -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@other.debian.org
Re: cdrecord floating point exception
Hi, > There always was only one cdrecord source code since it's > creation in late 1995. The first DVD support code was added in > February 1998 but could not be made OpenSource due to an NDA. > Anyway, the DVD support in cdrecord code became OpenSource long > before the fork "wodim" was created. Indeed the sequence was 1) End of ProDVD (May 2006) 2) Fork of cdrkit (Oct 2006) But the release of ProDVD functionality in cdrtools source tarballs marks exactly the point where the fork took off: http://lists.debian.org/cdwrite/2006/05/msg00021.html Here you announce cdrtools-2.01.01a09 and mention CDDL. The fork of cdrkit is based on cdrtools-2.01.01a08. http://en.wikipedia.org/wiki/Cdrkit So they probably did not take your DVD code because they assumed that it is not under GPL. Have a nice day :) Thomas -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@other.debian.org
Re: cdrecord floating point exception
Norbert Preining wrote: > On Fr, 30 Jan 2009, Joerg Schilling wrote: > > that are responsible for introducing various bugs and license violations > > call > > themself "Debian packet maintainer". > > Stop talking nonsense and lies on a debian list, or I will try to get > you banned from that list. You are well known for repeatedly spreading lies on this list. Please finally stop spreading your lies. Jörg -- EMail:jo...@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin j...@cs.tu-berlin.de(uni) joerg.schill...@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@other.debian.org
Re: cdrecord floating point exception
On Fr, 30 Jan 2009, Joerg Schilling wrote: > that are responsible for introducing various bugs and license violations call > themself "Debian packet maintainer". Stop talking nonsense and lies on a debian list, or I will try to get you banned from that list. Best wishes Norbert --- Dr. Norbert Preining Vienna University of Technology Debian Developer Debian TeX Group gpg DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094 --- EWELME (n.) The smile bestowed on you by an air hostess. --- Douglas Adams, The Meaning of Liff -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@other.debian.org
Re: cdrecord floating point exception
"Thomas Schmitt" wrote:
> Hi,
>
> > The fork (when started in september 2006) removed the
> > original DVD code and replaced it by something that does not work. I have no
> > idea why the initiators of the fork replaced working code...
>
> To my observation the timeline was:
>
> - Fork of cdrkit ("cdrecord" became "wodim").
>
> - Introduction of DVD code into the fork
> (from program dvdrecord ?).
>
> - Soon later you released the cdrecord-ProDVD
> functionality as cdrtools source tarball.
It looks as if you are a victim of the FUD spread by Debian :-(
There always was only one cdrecord source code since it's
creation in late 1995. The first DVD support code was added in
February 1998 but could not be made OpenSource due to an NDA.
Anyway, the DVD support in cdrecord code became OpenSource long
before the fork "wodim" was created.
Why don't you inform yourself from the official cdrecord website?
> As i stated towards Parker Jones:
> If growisofs cannot handle drive and media
> then there is few hope that others can.
> (I deem my programs not worse than growisofs
> but they cannot claim to be better when it
> comes to DVD writing.)
If you observe the net, you will see that there are many people
who report that they use cdrecord to write DVDs because growisofs
is not working for them..
Jörg
--
EMail:jo...@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin
j...@cs.tu-berlin.de(uni)
joerg.schill...@fokus.fraunhofer.de (work) Blog:
http://schily.blogspot.com/
URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily
--
To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@other.debian.org
Re: cdrecord floating point exception
Hi,
> The fork (when started in september 2006) removed the
> original DVD code and replaced it by something that does not work. I have no
> idea why the initiators of the fork replaced working code...
To my observation the timeline was:
- Fork of cdrkit ("cdrecord" became "wodim").
- Introduction of DVD code into the fork
(from program dvdrecord ?).
- Soon later you released the cdrecord-ProDVD
functionality as cdrtools source tarball.
Obviously the DVD code of wodim is still
much too near to the CD code. To send a CUE
sheet to a DVD+RW is quite a stubborn gesture.
wodim cannot do multi-session on DVD and it
cannot write data streams of unannounced length
to DVD. So it is really not first choice for
that kind of media.
As i stated towards Parker Jones:
If growisofs cannot handle drive and media
then there is few hope that others can.
(I deem my programs not worse than growisofs
but they cannot claim to be better when it
comes to DVD writing.)
Have a nice day :)
Thomas
--
To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@other.debian.org
Re: cdrecord floating point exception
Parker Jones wrote: > I tried cdrecord because growisofs didn't work (see thread about a fortnight > ago). So this may not be software related. But it would still be nice to > get a clear error message indicating what has gone wrong. Without knowing the media manufacturer, it is hard to tell what might have been wrong. GIGABYTE is a mainboard manufacturer and the drives they make are partially produced under license and partially self made. This is what I have been told from the company at a CeBIT visit. Anyway, you have a drive that is most likely produced in camparable low volumes. If a drive does not like a medium, cdrecord usually prints error messages that allow to make conclusions on the problem. You therefore should kill hald and retry and report the output from cdrecord -v -minfo Jörg -- EMail:jo...@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin j...@cs.tu-berlin.de(uni) joerg.schill...@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@other.debian.org
Re: cdrecord floating point exception
"Thomas Schmitt" wrote: > But your problem is quite consistent. > Drive and media do not work together. > You cannot format successfully, you cannot > write a single byte. The various programs > say that the media is unformatted after > any effort to format it (plus tray reload). It looks as if the drive has been formatted correclty (I cannot tell more as he did not use -v when running cdrecord). A call to "cdrecord -v -minfo" would give us information about the current media status and the media manufacturer. Jörg -- EMail:jo...@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin j...@cs.tu-berlin.de(uni) joerg.schill...@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@other.debian.org
Re: cdrecord floating point exception
>From zoubi...@hotmail.com Fri Jan 30 21:07:19 2009 >Joerg, Thanks for the explanation - it's all a bit over my head; I'm just >using what came with my distribution. >I have downloaded your cdrtools, built and tried again. Here is the result >(still no success). Does this help? > ./cdrecord -v -dao speed=1 dev=/dev/dvd ~/newworld.iso >Cdrecord-ProDVD-ProBD-Clone 2.01.01a57 (i686-pc-linux-gnu) Copyright (C) >1995-2009 J???rg Schilling >TOC Type: 1 = CD-ROM >./cdrecord: Operation not permitted. Warning: Cannot raise RLIMIT_MEMLOCK >limits. >./cdrecord: Cannot allocate memory. WARNING: Cannot do mlockall(2). >./cdrecord: WARNING: This causes a high risk for buffer underruns. >./cdrecord: Operation not permitted. WARNING: Cannot set RR-scheduler. >./cdrecord: Permission denied. WARNING: Cannot set priority using >setpriority(). >./cdrecord: WARNING: This causes a high risk for buffer underruns. You did not install cdrecord correctly as you see from this messages. Cdrecord needs to be installed suid root in order to be able to open all needed devices and in order to send all needed SCSI commands. >scsidev: '/dev/dvd' >devname: '/dev/dvd' >scsibus: -2 target: -2 lun: -2 >Warning: Open by 'devname' is unintentional and not supported. Your dev= parameter was invalid. If you only have one drive, just omit the dev= parameter. If you have more than drive, call cdrecord -scanbus to find the right dev= parameter. >Linux sg driver version: 3.5.27 >Using libscg version 'schily-0.9'. >SCSI buffer size: 64512 >atapi: 1 >Device type: Removable CD-ROM >Version: 5 <--- Cable problems or Firmware bug? >Response Format: 2 >Capabilities : >Vendor_info: 'GIGABYTE' >Identifikation : 'GO-W1608A ' >Revision : 'B8S2' >Device seems to be: Generic mmc2 DVD-R/DVD-RW/DVD-RAM. >Current: DVD+RW >Profile: DVD+R/DL >Profile: DVD+R >Profile: DVD+RW (current) >Profile: DVD-RW sequential recording >Profile: DVD-RW restricted overwrite >Profile: DVD-R sequential recording >Profile: DVD-ROM >Profile: CD-RW >Profile: CD-R >Profile: CD-ROM >Using generic SCSI-3/mmc-3 DVD+RW driver (mmc_dvdplusrw). >Driver flags : NO-CD DVD MMC-3 SWABAUDIO BURNFREE FORCESPEED >Supported modes: PACKET SAO >Drive buf size : 1602048 = 1564 KB >./cdrecord: Warning: The DMA speed test has been skipped. Did you enable DMA for the drive? >FIFO size : 4194304 = 4096 KB >Track 01: data 4391 MB >Total size: 4391 MB = 2248251 sectors >Current Secsize: 2048 >WARNING: Drive returns illegal Disk type CD-DA or CD-ROM. >Capacity Blklen/Sparesz. Format-type Type > 2295104 2048 0x00 Unformated or Blank Media > 22951040 0x26 Reserved (0) >Format was needed. >Starting to write CD/DVD/BD at speed 1 in real FORMAT mode for single session. >Last chance to quit, starting real write0 seconds. Operation starts. >Formatting media >Formatting time: 92.518s Auto-formatting was successful. >Trying to clear drive status. This may be from a drive firmware bug or frim running hald (hald is non-cooperatively). Try to kill hald and retry cdrecord after correctly installing it suid root. Jörg -- EMail:jo...@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin j...@cs.tu-berlin.de(uni) joerg.schill...@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@other.debian.org
Re: cdrecord floating point exception
"Thomas Schmitt" wrote: > > Sending CUE sheet... > > The program has few clue about DVD+RW. > You probably caused this by option -dao. > > > CDB: 2A 00 00 00 00 00 00 00 1F 00 > > status: 0x2 (CHECK CONDITION) > > Sense Bytes: 70 00 05 00 00 00 00 0A 00 00 00 00 30 10 00 00 > > Sense Key: 0x5 Illegal Request, Segment 0 > > Sense Code: 0x30 Qual 0x10 (medium not formatted) Fru 0x0 This program has no clue about DVD+, it would be most unlikely that a different "write mode" specified on the command line would change things. You cannot write to a DVD+RW without first formatting it and a program that doesn't know that is needs to auto-format the medium before starting to write just has no DVD+RW support. As I mentioned before, cdrecord has mature DVD support since 11 years and DVD+ support was added 6 years ago. The fork (when started in september 2006) removed the original DVD code and replaced it by something that does not work. I have no idea why the initiators of the fork replaced working code... maybe they like to disgust their users. Jörg -- EMail:jo...@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin j...@cs.tu-berlin.de(uni) joerg.schill...@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@other.debian.org
Re: cdrecord floating point exception
Hi, > I tried cdrecord because growisofs didn't work growisofs not working is a very bad sign for drive and/or media. > But it would still be nice to get a clear > error message indicating what has gone > wrong. We are restricted to what the drive tells our programs. We send SCSI commands and get status replies. In case of error this gives the three numbers SK, ASC, ASCQ which we can translate according to a list in the MMC specs. See e.g. http://fy.chalmers.se/~appro/linux/DVD+RW/keys.txt Nevertheless the drive manufacturers invent own error codes and sometimes the emitted codes hardly match the problem. But your problem is quite consistent. Drive and media do not work together. You cannot format successfully, you cannot write a single byte. The various programs say that the media is unformatted after any effort to format it (plus tray reload). You need to exchange some of the involved hardware. Drive or media. Have a nice day :) Thomas -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@other.debian.org
RE: cdrecord floating point exception
Hi Thomas, > It is advisable to use a different program > for DVD purposes. E.g: > growisofs, cdrecord, cdrskin, xorriso. > (I am author of the latter two.) > > DVD+RW should be simply writeable via their > device file. Try: > > dd if=newworld.iso bs=2048 of=/dev/dvd > > Maybe the kernel is smarter than the burn program. I tried this and here's the output: $ dd if=~/newworld.iso bs=2048 of=/dev/dvd dd: writing `/dev/dvd': No space left on device 2+0 records in 1+0 records out 2048 bytes (2.0 kB) copied, 0.080821 s, 25.3 kB/s I guessed this was because the media needed formatting which I did with dvd+rw-format /dev/dvd but the outcome was still the same. I tried cdrecord because growisofs didn't work (see thread about a fortnight ago). So this may not be software related. But it would still be nice to get a clear error message indicating what has gone wrong. Thanks for your help, Parker _ Got a 2008 financial hangover? Find a cure at MSN NZ Money http://money.msn.co.nz
Re: cdrecord floating point exception
Parker Jones wrote: > > Thanks for your reply Joerg. A defective and illegal fork from ubuntu core > developers? Well, you are suffing from one of many bugs in this fork. Your specific problem is caused by the fact that the mature DVD support from the original software has been replaced by something half baken in the fork. The person who started the fork you are using stopped working on the fork on May 6th 2007 and since then is advertizing for nerolinux. While "working" on the fork, he amongst others introduced modifications that are responsible for bringing it in conflict with both GPL and Copyright. BTW: AKAIK, nobody from ubuntu did make any modification on the fork. The people that are responsible for introducing various bugs and license violations call themself "Debian packet maintainer". Jörg -- EMail:jo...@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin j...@cs.tu-berlin.de(uni) joerg.schill...@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@other.debian.org
RE: cdrecord floating point exception
Joerg, Thanks for the explanation - it's all a bit over my head; I'm just using what came with my distribution. I have downloaded your cdrtools, built and tried again. Here is the result (still no success). Does this help? Parker ./cdrecord -v -dao speed=1 dev=/dev/dvd ~/newworld.iso Cdrecord-ProDVD-ProBD-Clone 2.01.01a57 (i686-pc-linux-gnu) Copyright (C) 1995-2009 J�rg Schilling TOC Type: 1 = CD-ROM ./cdrecord: Operation not permitted. Warning: Cannot raise RLIMIT_MEMLOCK limits. ./cdrecord: Cannot allocate memory. WARNING: Cannot do mlockall(2). ./cdrecord: WARNING: This causes a high risk for buffer underruns. ./cdrecord: Operation not permitted. WARNING: Cannot set RR-scheduler. ./cdrecord: Permission denied. WARNING: Cannot set priority using setpriority(). ./cdrecord: WARNING: This causes a high risk for buffer underruns. scsidev: '/dev/dvd' devname: '/dev/dvd' scsibus: -2 target: -2 lun: -2 Warning: Open by 'devname' is unintentional and not supported. Linux sg driver version: 3.5.27 Using libscg version 'schily-0.9'. SCSI buffer size: 64512 atapi: 1 Device type: Removable CD-ROM Version: 5 Response Format: 2 Capabilities : Vendor_info: 'GIGABYTE' Identifikation : 'GO-W1608A ' Revision : 'B8S2' Device seems to be: Generic mmc2 DVD-R/DVD-RW/DVD-RAM. Current: DVD+RW Profile: DVD+R/DL Profile: DVD+R Profile: DVD+RW (current) Profile: DVD-RW sequential recording Profile: DVD-RW restricted overwrite Profile: DVD-R sequential recording Profile: DVD-ROM Profile: CD-RW Profile: CD-R Profile: CD-ROM Using generic SCSI-3/mmc-3 DVD+RW driver (mmc_dvdplusrw). Driver flags : NO-CD DVD MMC-3 SWABAUDIO BURNFREE FORCESPEED Supported modes: PACKET SAO Drive buf size : 1602048 = 1564 KB ./cdrecord: Warning: The DMA speed test has been skipped. FIFO size : 4194304 = 4096 KB Track 01: data 4391 MB Total size: 4391 MB = 2248251 sectors Current Secsize: 2048 WARNING: Drive returns illegal Disk type CD-DA or CD-ROM. Capacity Blklen/Sparesz. Format-type Type 2295104 2048 0x00 Unformated or Blank Media 22951040 0x26 Reserved (0) Format was needed. Starting to write CD/DVD/BD at speed 1 in real FORMAT mode for single session. Last chance to quit, starting real write0 seconds. Operation starts. Formatting media Formatting time: 92.518s Trying to clear drive status. Forcespeed is OFF. ./cdrecord: Drive needs to reload the media to return to proper status. WARNING: Drive returns illegal Disk type CD-DA or CD-ROM. ./cdrecord: Data will not fit on any disk. ./cdrecord: Cannot write more than remaining DVD/BD capacity. _ Get inspired - dream, research, plan and book your next holiday online. MSN NZ Travel http://travel.msn.co.nz/
Re: cdrecord floating point exception
Hi, > I'm trying to burn a DVD+RW with cdrecord and get a floating point > exception. Can't make out what the error means. You are using wodim, not cdrecord. The floating point error is only a final glitch after writing already failed. > Sending CUE sheet... The program has few clue about DVD+RW. You probably caused this by option -dao. > CDB: 2A 00 00 00 00 00 00 00 1F 00 > status: 0x2 (CHECK CONDITION) > Sense Bytes: 70 00 05 00 00 00 00 0A 00 00 00 00 30 10 00 00 > Sense Key: 0x5 Illegal Request, Segment 0 > Sense Code: 0x30 Qual 0x10 (medium not formatted) Fru 0x0 That's the very first write attempt. Already failing. Looks like the program did not start background formatting on unformatted DVD+RW media before writing began. It is advisable to use a different program for DVD purposes. E.g: growisofs, cdrecord, cdrskin, xorriso. (I am author of the latter two.) DVD+RW should be simply writeable via their device file. Try: dd if=newworld.iso bs=2048 of=/dev/dvd Maybe the kernel is smarter than the burn program. Have a nice day :) Thomas -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@other.debian.org
RE: cdrecord floating point exception
Thanks for your reply Joerg. A defective and illegal fork from ubuntu core developers? $ dpkg-query -p wodim Package: wodim Priority: optional Section: otherosfs Installed-Size: 844 Maintainer: Ubuntu Core Developers Architecture: i386 Source: cdrkit Version: 9:1.1.6-1ubuntu6 Replaces: cdrecord, cdrtools-doc Provides: cdrecord Depends: libc6 (>= 2.7-1), libcap1 Recommends: genisoimage Suggests: cdrkit-doc Conflicts: xcdroast (<< 0.98+0alpha15-11) Size: 430966 Description: command line CD/DVD writing tool wodim allows you to create CDs or DVDs on a CD/DVD recorder. It supports writing data, audio, mixed, multi-session, and CD+ disc and DVD data and video disks on DVD capable devices, on just about every type of CD/DVD recorder out there. . Please install cdrkit-doc if you want most of the documentation and README files. Original-Maintainer: Joerg Jaspert > Date: Fri, 30 Jan 2009 18:48:06 +0100 > From: joerg.schill...@fokus.fraunhofer.de > To: zoubi...@hotmail.com; cdwrite@other.debian.org > Subject: Re: cdrecord floating point exception > > Parker Jones wrote: > > > I'm trying to burn a DVD+RW with cdrecord and get a floating point > > exception. Can't make out what the error means. > > > > Thanks for any suggestions. > > Parker > > > > > > Platform Ubuntu 8.10 i386 > > ii wodim 9:1.1.6-1ubuntu6 command line CD/DVD > > writing tool > > > > > > $ cdrecord -v -dao speed=1 dev=/dev/dvd newworld.iso > > TOC Type: 1 = CD-ROM > > wodim: Operation not permitted. Warning: Cannot raise RLIMIT_MEMLOCK > > limits.scsidev: '/dev/dvd' > > devname: '/dev/dvd' > > scsibus: -2 target: -2 lun: -2 > > Linux sg driver version: 3.5.27 > > Wodim version: 1.1.6 > > You are not using cdrecord but a defective and illegal fork. > > BTW: This fork does not support DVD writing correctly. > > Upgrade to recent original software from > > ftp://ftp.berlios.de/pub/cdrecord/alpha/ > > Jörg > > -- > EMail:jo...@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin >j...@cs.tu-berlin.de(uni) >joerg.schill...@fokus.fraunhofer.de (work) Blog: > http://schily.blogspot.com/ > URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily _ Enjoy the last moments of summer. Meet someone fun to play with at Match.com http://a.ninemsn.com.au/b.aspx?URL=http%3A%2F%2Fdating%2Enz%2Emsn%2Ecom%2Fchannel%2Findex%2Easpx%3Ftrackingid%3D1048628&_t=773568480&_r=nzWINDOWSliveMAILemailTAGLINES&_m=EXT
Re: cdrecord floating point exception
Parker Jones wrote: > I'm trying to burn a DVD+RW with cdrecord and get a floating point exception. > Can't make out what the error means. > > Thanks for any suggestions. > Parker > > > Platform Ubuntu 8.10 i386 > ii wodim 9:1.1.6-1ubuntu6 command line CD/DVD > writing tool > > > $ cdrecord -v -dao speed=1 dev=/dev/dvd newworld.iso > TOC Type: 1 = CD-ROM > wodim: Operation not permitted. Warning: Cannot raise RLIMIT_MEMLOCK > limits.scsidev: '/dev/dvd' > devname: '/dev/dvd' > scsibus: -2 target: -2 lun: -2 > Linux sg driver version: 3.5.27 > Wodim version: 1.1.6 You are not using cdrecord but a defective and illegal fork. BTW: This fork does not support DVD writing correctly. Upgrade to recent original software from ftp://ftp.berlios.de/pub/cdrecord/alpha/ Jörg -- EMail:jo...@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin j...@cs.tu-berlin.de(uni) joerg.schill...@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@other.debian.org
