Re: firmware or media problem or what???
> Now I have ruined a couple of DVD+R What does it mean exactly? As page requires, exact growisofs output and dvd+rw-mediainfo for resulting/ruined recording. > GET PERFORMANCE: > Speed Descriptor#0:00/2295104 [EMAIL PROTECTED] [EMAIL PROTECTED] > Speed Descriptor#1:00/2295104 [EMAIL PROTECTED] [EMAIL PROTECTED] It might pay off to decrease the recording velocity in order to succeed with this particular media brand with this particular firmware... Unfortunately 5.16 can't control speed in NEC, upcoming version will be able to do that... > :-[ READ DVD STRUCTURE#0 failed with SK=5h/ASC=24h/ACQ=00h]: Input/output > error This is perfectly OK for blank media. DVD STRUCTURE#0 is information from Lead-in and there is no lead-in yet. A.
firmware or media problem or what???
Hi folks I just got my first dvd writer and is struggling to get it working on my linux box. (My son tells me I should opt for plan b, and put it in his XP box.) I have successfully made a CDR, which should mean I'm pretty close. Now I have ruined a couple of DVD+R and seek your advice before I ruin myself. The box is a vanilla rh9 with all apt updates from freshrpms. dvd+rw-tools is installed as an rpm created directly from the tarball. I run dvd+rw-mediainfo and it says it fails, but I don't understand if that is important. Perhaps I'm doing something wrong and should RTFM, but It would be nice to _know_ if that is the case. The media is from a 25-pack marked PHILIPS DVD+R 1-4x. Great if someone could tell what these codes mean. Printout with a fresh disk follows... /Bengt [EMAIL PROTECTED] root]# rpm -q dvd+rw-tools dvd+rw-tools-5.16.4.8.5-1 [EMAIL PROTECTED] root]# dvd+rw-mediainfo /dev/cdrom INQUIRY:[_NEC][DVD_RW ND-1300A ][1.06] GET [CURRENT] CONFIGURATION: Mounted Media: 1Bh, DVD+R GET PERFORMANCE: Speed Descriptor#0:00/2295104 [EMAIL PROTECTED] [EMAIL PROTECTED] Speed Descriptor#1:00/2295104 [EMAIL PROTECTED] [EMAIL PROTECTED] :-[ READ DVD STRUCTURE#0 failed with SK=5h/ASC=24h/ACQ=00h]: Input/output error READ DISC INFORMATION: Disc status: blank Number of Sessions:1 State of Last Session: empty Number of Tracks: 1 READ TRACK INFORMATION[#1]: Track State: blank Track Start Address: 0*2KB Next Writable Address: 0*2KB Free Blocks: 2295104*2KB Track Size:2295104*2KB
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: growisofs for DVD-R -sort of problem
> ...using growisofs (5.16) with mkisofs 2.0 > > growisofs -Z /dev/scd0=xyz.isofine > growisofs -M /dev/scd0 abc/deffine - a few times > > - THEN did another growisofs - everything went fine but > attempts to access DVD give message 'no media mounted' ? > > --- > If relevant - none of the discs burned were mountable unless > the kernel was booted with ide-scsi enabled. > (dd -ing the contents of an ok dvd to hd and mounting it only > gives access to the initial 'Z' write session - presume normal?) Yes. > The full contents are accessible from XP - though the 'dead' disc > is not seen from XP either. Clarify this. You've burned serveral multi-session disks. Only one was rendered "dead," right? What about those "healthy" ones? Were they unmountable already after -Z without ide-scsi? Or did they become *unmountable* after first -M and you had to load ide-scsi? In which case how large were first sessions? > I note that the man-page comments that not all players can handle > multi-border playback - but this one seems to. In this case manual refers to *legacy DVD-ROM players*. You're referring to a recorder, right? Recorders are perfectly capable of multi-border playback. > - failure for 'various reasons' are also referred to. Presume I > am there - but can I do anything? "Various reasons" also refers to limitations of OS drivers, e.g. NetBSD reportedly fails to play multi-session DVD even if unit supports multi-sessioning... > --- > output of 'mediainfo' (straight + verbose) for the dead dvd simply > says - 'no media mounted' after the drive info... > and for a part burned - still ok disk is below. > (But I am nervous about doing any more 'grows' for fear of > losing the disc.) The media must have had a defect in lead-in. Media being rendered un-mountable as result of adding a session is not something which is meant to happen... I understand the hesitation, but the only way to figure this out is keep trying. > [EMAIL PROTECTED] nick]$ dvd+rw-mediainfo /dev/scd0 > INQUIRY:[TOSHIBA ][DVD-ROM SD-R6112][1031] > GET PERFORMANCE: > Speed Descriptor#0:00/2298495 [EMAIL PROTECTED] [EMAIL PROTECTED] Only one descriptor? No 1x? Strange... Point is that if it fails again, it would make sense to record at lower speed, but in order to switch the speed there have to be more descriptors... > READ TRACK INFORMATION[#1]: > Track Start Address: 0*2KB > Track Size:65264*2KB Even though it might appear tempting to add data in such small increments, I would recommend to grow in larger increments. You waste space on border-ins/-outs. > READ TRACK INFORMATION[#2]: > Track Start Address: 93952*2KB Follow Track Size values and Track Start Addresses. First session is 130MB and you wasted 60MB... Then number of amount of sessions is not unlimited. Well, DVD- allows for over 2000 sessions, so that this is not really relevant... > FABRICATED TOC: > Track#1 : [EMAIL PROTECTED] > Track#AA : [EMAIL PROTECTED] > Multi-session Info:[EMAIL PROTECTED] This is strange... Normally FABRICATED TOC for multi-session media consists of 3 tracks #1, #2 and #AA... A.
Re: firmware or media problem or what???
> Now I have ruined a couple of DVD+R What does it mean exactly? As page requires, exact growisofs output and dvd+rw-mediainfo for resulting/ruined recording. > GET PERFORMANCE: > Speed Descriptor#0:00/2295104 [EMAIL PROTECTED] [EMAIL PROTECTED] > Speed Descriptor#1:00/2295104 [EMAIL PROTECTED] [EMAIL PROTECTED] It might pay off to decrease the recording velocity in order to succeed with this particular media brand with this particular firmware... Unfortunately 5.16 can't control speed in NEC, upcoming version will be able to do that... > :-[ READ DVD STRUCTURE#0 failed with SK=5h/ASC=24h/ACQ=00h]: Input/output error This is perfectly OK for blank media. DVD STRUCTURE#0 is information from Lead-in and there is no lead-in yet. A. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
firmware or media problem or what???
Hi folks I just got my first dvd writer and is struggling to get it working on my linux box. (My son tells me I should opt for plan b, and put it in his XP box.) I have successfully made a CDR, which should mean I'm pretty close. Now I have ruined a couple of DVD+R and seek your advice before I ruin myself. The box is a vanilla rh9 with all apt updates from freshrpms. dvd+rw-tools is installed as an rpm created directly from the tarball. I run dvd+rw-mediainfo and it says it fails, but I don't understand if that is important. Perhaps I'm doing something wrong and should RTFM, but It would be nice to _know_ if that is the case. The media is from a 25-pack marked PHILIPS DVD+R 1-4x. Great if someone could tell what these codes mean. Printout with a fresh disk follows... /Bengt [EMAIL PROTECTED] root]# rpm -q dvd+rw-tools dvd+rw-tools-5.16.4.8.5-1 [EMAIL PROTECTED] root]# dvd+rw-mediainfo /dev/cdrom INQUIRY:[_NEC][DVD_RW ND-1300A ][1.06] GET [CURRENT] CONFIGURATION: Mounted Media: 1Bh, DVD+R GET PERFORMANCE: Speed Descriptor#0:00/2295104 [EMAIL PROTECTED] [EMAIL PROTECTED] Speed Descriptor#1:00/2295104 [EMAIL PROTECTED] [EMAIL PROTECTED] :-[ READ DVD STRUCTURE#0 failed with SK=5h/ASC=24h/ACQ=00h]: Input/output error READ DISC INFORMATION: Disc status: blank Number of Sessions:1 State of Last Session: empty Number of Tracks: 1 READ TRACK INFORMATION[#1]: Track State: blank Track Start Address: 0*2KB Next Writable Address: 0*2KB Free Blocks: 2295104*2KB Track Size:2295104*2KB -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: cdrtools-2.01a22 ready
On Thu, Jan 08, 2004 at 11:10:54AM -0800, Scott Bronson wrote: > Any chance this thread can be put to rest here? You could try invoking Godwin's Law
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: growisofs for DVD-R -sort of problem
> ...using growisofs (5.16) with mkisofs 2.0 > > growisofs -Z /dev/scd0=xyz.isofine > growisofs -M /dev/scd0 abc/deffine - a few times > > - THEN did another growisofs - everything went fine but > attempts to access DVD give message 'no media mounted' ? > > --- > If relevant - none of the discs burned were mountable unless > the kernel was booted with ide-scsi enabled. > (dd -ing the contents of an ok dvd to hd and mounting it only > gives access to the initial 'Z' write session - presume normal?) Yes. > The full contents are accessible from XP - though the 'dead' disc > is not seen from XP either. Clarify this. You've burned serveral multi-session disks. Only one was rendered "dead," right? What about those "healthy" ones? Were they unmountable already after -Z without ide-scsi? Or did they become *unmountable* after first -M and you had to load ide-scsi? In which case how large were first sessions? > I note that the man-page comments that not all players can handle > multi-border playback - but this one seems to. In this case manual refers to *legacy DVD-ROM players*. You're referring to a recorder, right? Recorders are perfectly capable of multi-border playback. > - failure for 'various reasons' are also referred to. Presume I > am there - but can I do anything? "Various reasons" also refers to limitations of OS drivers, e.g. NetBSD reportedly fails to play multi-session DVD even if unit supports multi-sessioning... > --- > output of 'mediainfo' (straight + verbose) for the dead dvd simply > says - 'no media mounted' after the drive info... > and for a part burned - still ok disk is below. > (But I am nervous about doing any more 'grows' for fear of > losing the disc.) The media must have had a defect in lead-in. Media being rendered un-mountable as result of adding a session is not something which is meant to happen... I understand the hesitation, but the only way to figure this out is keep trying. > [EMAIL PROTECTED] nick]$ dvd+rw-mediainfo /dev/scd0 > INQUIRY:[TOSHIBA ][DVD-ROM SD-R6112][1031] > GET PERFORMANCE: > Speed Descriptor#0:00/2298495 [EMAIL PROTECTED] [EMAIL PROTECTED] Only one descriptor? No 1x? Strange... Point is that if it fails again, it would make sense to record at lower speed, but in order to switch the speed there have to be more descriptors... > READ TRACK INFORMATION[#1]: > Track Start Address: 0*2KB > Track Size:65264*2KB Even though it might appear tempting to add data in such small increments, I would recommend to grow in larger increments. You waste space on border-ins/-outs. > READ TRACK INFORMATION[#2]: > Track Start Address: 93952*2KB Follow Track Size values and Track Start Addresses. First session is 130MB and you wasted 60MB... Then number of amount of sessions is not unlimited. Well, DVD- allows for over 2000 sessions, so that this is not really relevant... > FABRICATED TOC: > Track#1 : [EMAIL PROTECTED] > Track#AA : [EMAIL PROTECTED] > Multi-session Info:[EMAIL PROTECTED] This is strange... Normally FABRICATED TOC for multi-session media consists of 3 tracks #1, #2 and #AA... A. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: cdrtools-2.01a22 ready
On Thu, Jan 08, 2004 at 11:10:54AM -0800, Scott Bronson wrote: > Any chance this thread can be put to rest here? You could try invoking Godwin's Law -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: cdrtools-2.01a22 ready
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? Any chance this thread can be put to rest here? On Thu, 2004-01-08 at 05:47, Lourens Veen wrote: > 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 >
Re: cdrtools-2.01a22 ready
On Thu, Jan 08, 2004 at 07:02:57PM +0100, Joerg Schilling wrote: > > >From: Matthias Schniedermeyer <[EMAIL PROTECTED]> > > >Take this "as given". > > > > >Same as you can assume that the libc of Solaris 9 is compiled on Solaris > >9 and is forward compatible to Solaris 8. > > Libc from Solaris 2.6 definitely does not work on Solaris 2.5.1 > Libc from Solaris 7 definitely does not work on Solaris 2.6 > Libc from Solaris 10 definitely does not work on Solaris 9 I said FORWARD compatible. Which means: A program compiled on Solaris 8 works on Solaris 9. Which should be true for system independend programs in 99% of the cases. Bis denn -- Real Programmers consider "what you see is what you get" to be just as bad a concept in Text Editors as it is in women. No, the Real Programmer wants a "you asked for it, you got it" text editor -- complicated, cryptic, powerful, unforgiving, dangerous.
Re: cdrtools-2.01a22 ready
On Thu, Jan 08, 2004 at 07:17:16PM +0100, Lourens Veen wrote: > 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. Exactly. I would say: It is save to assume that a system independend program has a chance of 99% to work in the next Revision. Bis denn -- Real Programmers consider "what you see is what you get" to be just as bad a concept in Text Editors as it is in women. No, the Real Programmer wants a "you asked for it, you got it" text editor -- complicated, cryptic, powerful, unforgiving, dangerous.
Re: cdrtools-2.01a22 ready
>From: Matthias Schniedermeyer <[EMAIL PROTECTED]> >Take this "as given". >Same as you can assume that the libc of Solaris 9 is compiled on Solaris >9 and is forward compatible to Solaris 8. Libc from Solaris 2.6 definitely does not work on Solaris 2.5.1 Libc from Solaris 7 definitely does not work on Solaris 2.6 Libc from Solaris 10 definitely does not work on Solaris 9 For the other versions, I would need to spend too much time to check for differences Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) If you don't have iso-8859-1 [EMAIL PROTECTED](work) chars I am J"org Schilling URL: http://www.fokus.fraunhofer.de/usr/schilling ftp://ftp.berlios.de/pub/schily
Re: cdrtools-2.01a22 ready
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? Any chance this thread can be put to rest here? On Thu, 2004-01-08 at 05:47, Lourens Veen wrote: > 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: 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, Jan 08, 2004 at 05:11:36PM +0100, Joerg Schilling wrote: > > >From: Matthias Schniedermeyer <[EMAIL PROTECTED]> > > >> 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". > > >grep only uses libc-interface. As long as the program <-> libc interface > >is stable it will have no problem with the libc <-> site. > > >It is excatly THE job of libc to abstract away the "right" side. > >(Or the left when you assume hardware/kernel is leftmost) > > >Only "system dependend"(hardware, kernel interfaces, ..) software (e.g. > >cdrecord, star, ps, lspci, iptables) have this type of problem. > > Well of course libc too. This is something that people tend to forget. > > Who make sure that the libc that has been installed matched the current > kernel? Take this "as given". Same as you can assume that the libc of Solaris 9 is compiled on Solaris 9 and is forward compatible to Solaris 8. Bis denn -- Real Programmers consider "what you see is what you get" to be just as bad a concept in Text Editors as it is in women. No, the Real Programmer wants a "you asked for it, you got it" text editor -- complicated, cryptic, powerful, unforgiving, dangerous.
Re: cdrtools-2.01a22 ready
On Thu, Jan 08, 2004 at 07:02:57PM +0100, Joerg Schilling wrote: > > >From: Matthias Schniedermeyer <[EMAIL PROTECTED]> > > >Take this "as given". > > > > >Same as you can assume that the libc of Solaris 9 is compiled on Solaris > >9 and is forward compatible to Solaris 8. > > Libc from Solaris 2.6 definitely does not work on Solaris 2.5.1 > Libc from Solaris 7 definitely does not work on Solaris 2.6 > Libc from Solaris 10 definitely does not work on Solaris 9 I said FORWARD compatible. Which means: A program compiled on Solaris 8 works on Solaris 9. Which should be true for system independend programs in 99% of the cases. Bis denn -- Real Programmers consider "what you see is what you get" to be just as bad a concept in Text Editors as it is in women. No, the Real Programmer wants a "you asked for it, you got it" text editor -- complicated, cryptic, powerful, unforgiving, dangerous. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: cdrtools-2.01a22 ready
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. Bis denn -- Real Programmers consider "what you see is what you get" to be just as bad a concept in Text Editors as it is in women. No, the Real Programmer wants a "you asked for it, you got it" text editor -- complicated, cryptic, powerful, unforgiving, dangerous.
Re: cdrtools-2.01a22 ready
On Thu, Jan 08, 2004 at 07:17:16PM +0100, Lourens Veen wrote: > 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. Exactly. I would say: It is save to assume that a system independend program has a chance of 99% to work in the next Revision. Bis denn -- Real Programmers consider "what you see is what you get" to be just as bad a concept in Text Editors as it is in women. No, the Real Programmer wants a "you asked for it, you got it" text editor -- complicated, cryptic, powerful, unforgiving, dangerous. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: cdrtools-2.01a22 ready
>From: Matthias Schniedermeyer <[EMAIL PROTECTED]> >Take this "as given". >Same as you can assume that the libc of Solaris 9 is compiled on Solaris >9 and is forward compatible to Solaris 8. Libc from Solaris 2.6 definitely does not work on Solaris 2.5.1 Libc from Solaris 7 definitely does not work on Solaris 2.6 Libc from Solaris 10 definitely does not work on Solaris 9 For the other versions, I would need to spend too much time to check for differences Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) If you don't have iso-8859-1 [EMAIL PROTECTED](work) chars I am J"org Schilling URL: http://www.fokus.fraunhofer.de/usr/schilling ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: 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, Jan 08, 2004 at 05:11:36PM +0100, Joerg Schilling wrote: > > >From: Matthias Schniedermeyer <[EMAIL PROTECTED]> > > >> 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". > > >grep only uses libc-interface. As long as the program <-> libc interface > >is stable it will have no problem with the libc <-> site. > > >It is excatly THE job of libc to abstract away the "right" side. > >(Or the left when you assume hardware/kernel is leftmost) > > >Only "system dependend"(hardware, kernel interfaces, ..) software (e.g. > >cdrecord, star, ps, lspci, iptables) have this type of problem. > > Well of course libc too. This is something that people tend to forget. > > Who make sure that the libc that has been installed matched the current > kernel? Take this "as given". Same as you can assume that the libc of Solaris 9 is compiled on Solaris 9 and is forward compatible to Solaris 8. Bis denn -- Real Programmers consider "what you see is what you get" to be just as bad a concept in Text Editors as it is in women. No, the Real Programmer wants a "you asked for it, you got it" text editor -- complicated, cryptic, powerful, unforgiving, dangerous. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: cdrtools-2.01a22 ready
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. Bis denn -- Real Programmers consider "what you see is what you get" to be just as bad a concept in Text Editors as it is in women. No, the Real Programmer wants a "you asked for it, you got it" text editor -- complicated, cryptic, powerful, unforgiving, dangerous. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: cdrtools-2.01a22 ready
>From: Matthias Schniedermeyer <[EMAIL PROTECTED]> >> 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". >grep only uses libc-interface. As long as the program <-> libc interface >is stable it will have no problem with the libc <-> site. >It is excatly THE job of libc to abstract away the "right" side. >(Or the left when you assume hardware/kernel is leftmost) >Only "system dependend"(hardware, kernel interfaces, ..) software (e.g. >cdrecord, star, ps, lspci, iptables) have this type of problem. Well of course libc too. This is something that people tend to forget. Who make sure that the libc that has been installed matched the current kernel? Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) If you don't have iso-8859-1 [EMAIL PROTECTED](work) chars I am J"org Schilling URL: http://www.fokus.fraunhofer.de/usr/schilling ftp://ftp.berlios.de/pub/schily .,
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
Re: cdrtools-2.01a22 ready
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". grep only uses libc-interface. As long as the program <-> libc interface is stable it will have no problem with the libc <-> site. It is excatly THE job of libc to abstract away the "right" side. (Or the left when you assume hardware/kernel is leftmost) Only "system dependend"(hardware, kernel interfaces, ..) software (e.g. cdrecord, star, ps, lspci, iptables) have this type of problem. And btw. There is also a "binary" and "compile" compatiblity factor in this. e.g. libc6 aka glibc2 broke compatiblity with libc5 so A FEW programms needed patches to be COMPILABLE on new systems whereas (when the needed shared libraries where installed or the programm was static compiled) the libc5 binaries where still runable. Or in other words for >95% of all programms your statement is false! There is, always was and will ever be a small fraction of programs with this type of problem. The majority of software doesn't have this type of problem(s)! Or in other other words: It is wrong to assume that a random system dependend program compiled for OS revision A will run correctly on OS revision B for system. I have more other words: If Linux (for 2.8/3.0 whatever) would get incompatibel to every other Unix(type) OS AND to POSIX, BSD (and would need to drop glibc2). Then you can say what you have said. Bis denn -- Real Programmers consider "what you see is what you get" to be just as bad a concept in Text Editors as it is in women. No, the Real Programmer wants a "you asked for it, you got it" text editor -- complicated, cryptic, powerful, unforgiving, dangerous.
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
>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. 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 Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) If you don't have iso-8859-1 [EMAIL PROTECTED](work) chars I am J"org Schilling URL: http://www.fokus.fraunhofer.de/usr/schilling ftp://ftp.berlios.de/pub/schily
Re: DVD Media question
>From: Gregoire Favre <[EMAIL PROTECTED]> >Cdrecord-ProDVD-Clone 2.01a20 (i686-pc-linux-gnu) Copyright (C) >1995-2003 Jörg Schilling >Unlocked features: ProDVD Clone >Limited features: >This copy of cdrecord is licensed for: >private/research/educational_non-commercial_use >TOC Type: 1 = CD-ROM >scsidev: 'ATAPI:0,0,0' >devname: 'ATAPI' >scsibus: 0 target: 0 lun: 0 >Warning: Using ATA Packet interface. >Warning: The related libscg interface code is in pre alpha. >Warning: There may be fatal problems. >Using libscg version 'schily-0.7'. >SCSI buffer size: 64512 >atapi: 1 >Device type: Removable CD-ROM >Version: 0 >Response Format: 2 >Capabilities : >Vendor_info: 'SONY' >Identifikation : 'DVD RW DRU-500A ' >Revision : '2.0g' >Device seems to be: Generic mmc2 DVD-R/DVD-RW. >Current: none >Profile: DVD+R >Profile: DVD+RW >Profile: DVD-RW sequential overwrite >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 CD-R/CD-RW driver (mmc_cdr). >Driver flags : MMC-3 SWABAUDIO BURNFREE >Supported modes: TAO PACKET SAO SAO/R96R RAW/R96R >Drive buf size : 8112896 = 7922 KB >FIFO size : 67108864 = 65536 KB >Track 01: data 4481 MB >Total size: 5146 MB (509:52.64) = 2294448 sectors >Lout start: 5146 MB (509:54/48) = 2294448 sectors >cdrecord-prodvd: No disk / Wrong disk! I forgot to mention, that this is obviously a limitation of the drive or its firware. Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) If you don't have iso-8859-1 [EMAIL PROTECTED](work) chars I am J"org Schilling URL: http://www.fokus.fraunhofer.de/usr/schilling ftp://ftp.berlios.de/pub/schily
Re: cdrtools-2.01a22 ready
>From: Matthias Schniedermeyer <[EMAIL PROTECTED]> >> 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". >grep only uses libc-interface. As long as the program <-> libc interface >is stable it will have no problem with the libc <-> site. >It is excatly THE job of libc to abstract away the "right" side. >(Or the left when you assume hardware/kernel is leftmost) >Only "system dependend"(hardware, kernel interfaces, ..) software (e.g. >cdrecord, star, ps, lspci, iptables) have this type of problem. Well of course libc too. This is something that people tend to forget. Who make sure that the libc that has been installed matched the current kernel? Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) If you don't have iso-8859-1 [EMAIL PROTECTED](work) chars I am J"org Schilling URL: http://www.fokus.fraunhofer.de/usr/schilling ftp://ftp.berlios.de/pub/schily ., -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: DVD Media question
>From: Gregoire Favre <[EMAIL PROTECTED]> >I have some medi that gives me under linux: >And cdrecord-prodvd -v dev=ATAPI:0,0,0 -atip >Cdrecord-ProDVD-Clone 2.01a20 (i686-pc-linux-gnu) Copyright (C) >1995-2003 Jörg Schilling >Unlocked features: >Limited features: >TOC Type: 1 = CD-ROM >scsidev: 'ATAPI:0,0,0' >devname: 'ATAPI' >scsibus: 0 target: 0 lun: 0 >Warning: Using ATA Packet interface. >Warning: The related libscg interface code is in pre alpha. >Warning: There may be fatal problems. >Using libscg version 'schily-0.7'. >SCSI buffer size: 64512 >atapi: 1 >Device type: Removable CD-ROM >Version: 0 >Response Format: 2 >Capabilities : >Vendor_info: 'SONY' >Identifikation : 'DVD RW DRU-500A ' >Revision : '2.0g' >Device seems to be: Generic mmc2 DVD-R/DVD-RW. >Current: none >Profile: DVD+R >Profile: DVD+RW >Profile: DVD-RW sequential overwrite >Profile: DVD-RW restricted overwrite >Profile: DVD-R sequential recording >Profile: DVD-ROM >Profile: CD-RW >Profile: CD-R >Profile: CD-ROM >cdrecord-prodvd: This version of cdrecord limits DVD-R/DVD-RW support to >-dummy or 1 GB real. >cdrecord-prodvd: If you need full DVD-R/DVD-RW support, ask the Author >for cdrecord-ProDVD. >cdrecord-prodvd: Free test versions and free keys for personal use are >at ftp://ftp.berlios.de/pub/cdrecord/ProDVD/ >Using generic SCSI-3/mmc CD-R/CD-RW driver (mmc_cdr). >Driver flags : MMC-3 SWABAUDIO BURNFREE >Supported modes: TAO PACKET SAO SAO/R96R RAW/R96R >Drive buf size : 8112896 = 7922 KB >cdrecord-prodvd: No disk / Wrong disk! >But under OSX I can use the media and it tells me: >cdrecord-prodvd -v dev=IODVDServices -atip >Cdrecord-ProDVD-Clone 2.01a11 (powerpc-apple-macosx1.4) Copyright (C) >1995-2003 Jorg Schilling >Unlocked features: >Limited features: >TOC Type: 1 = CD-ROM >scsidev: 'IODVDServices' >devname: 'IODVDServices' >scsibus: -2 target: -2 lun: -2 >Using libscg version 'schily-0.7' >cdrecord-prodvd: Warning: using inofficial libscg transport code version >(csapuntz-scsi-mac-iokit.c-1.4 '@(#)scsi-mac-iokit.c 1.4 02/10/19 Copyright >1997,2001 J. Schilling'). >atapi: 0 >Device type: Removable CD-ROM >Version: 0 >Response Format: 2 >Capabilities : >Vendor_info: 'MATSHITA' >Identifikation : 'DVD-R UJ-816 ' >Revision : 'DXJ3' >Device seems to be: Generic mmc2 DVD-R/DVD-RW. >Profile: DVD-RW restricted overwrite >Profile: DVD-RW sequential overwrite >Profile: DVD-R sequential recording (current) >Profile: DVD-ROM >Profile: CD-RW >Profile: CD-R >Profile: CD-ROM >Profile: Removable Disk >cdrecord-prodvd: This version of cdrecord limits DVD-R/DVD-RW support to >-dummy or 1 GB real. >cdrecord-prodvd: If you need full DVD-R/DVD-RW support, ask the Author for >cdrecord-ProDVD. >Using generic SCSI-3/mmc-2 DVD-R/DVD-RW driver (mmc_dvd). >Driver flags : DVD MMC-3 SWABAUDIO BURNFREE >Supported modes: TAO PACKET SAO >Drive buf size : 1671168 = 1632 KB >Current Secsize: 2048 >book type: DVD-R, Version 5 (2.5) >disc size: 120mm (0) >minimum rate:Not specified (15) >number of layers:0 >track path: Parallel Track Path (0) >layer type: Rewritable Area (2) >linear density: 0.267 m/bit (0) >track density: 0.74 m/track (0) >phys start: 196608 >phys end:196608 >end layer 0: 0 >bca: 0 >phys size:...1 >copyr prot type: 0 >region mgt info: 0 >rzone number: 1 >border number: 1 >damage: 0 >reserved: 0 blank: 1 incremental: 0 >nwa valid: 1 >rzone start:0 >next wr addr: 0 >free blocks:2298496 >blocking factor:16 >rzone size: 2298496 >last recorded addr: 0 >WARNING: Phys disk size 1 differs from rzone size 2298496! Prerecorded disk? >WARNING: Phys start: 196608 Phys end 196608 >Is it possible to use those discs under linux? Of course: First mount the Matsushita drive into the Linux PC Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) If you don't have iso-8859-1 [EMAIL PROTECTED](work) chars I am J"org Schilling URL: http://www.fokus.fraunhofer.de/usr/schilling ftp://ftp.berlios.de/pub/schily
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: DVD Media question
On Thu, Jan 08, 2004 at 04:21:36PM +0100, Joerg Schilling wrote: > I forgot to mention, that this is obviously a limitation of the drive > or its firware. Thank, you answered my question before I sent it to you!!! Do you think it's worth writing to sony for an explanation of this limitation? Grégoire http://magma.epfl.ch/greg ICQ:16624071 mailto:[EMAIL PROTECTED]
Re: [Cdrecord-announces] cdrtools-2.01a24 ready
>From: Thomas Plank <[EMAIL PROTECTED]> >> ASPI was default for several years. You changed this behavior. >I'm not satisfied by changing this behavior too. >I namely do not have any problems with the SPTI method (perhaps because >I'm using NT 5.1) but what about all other users? First an important note: we need to test the code. It it is not the default, then it would remain untested. >Why isn't ASPI default and SPTI the new possible access version? Because otherwise, NT dumb users would not realize that it may work without now. >And I additionally have in mind all users of win95/98/ME, there's no >chance to get SPTI to work. It has been proved to work on win98 without problems using the same dev= strings as before. >I strongly stand up for making ASPI again the default method. It it blue screens Nt-4.0, then it makes sense to either find a workaround (other software seems to be able to do also) or introduce a hack that makes ASPI the default on NT-4.0 Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) If you don't have iso-8859-1 [EMAIL PROTECTED](work) chars I am J"org Schilling URL: http://www.fokus.fraunhofer.de/usr/schilling ftp://ftp.berlios.de/pub/schily
Re: DVD Media question
On Thu, Jan 08, 2004 at 04:14:24PM +0100, Joerg Schilling wrote: > Of course: > > First mount the Matsushita drive into the Linux PC ;-) OK, that THE solution, could I find somewhere an exlanation why it doesn't work with the Sony? Grégoire http://magma.epfl.ch/greg ICQ:16624071 mailto:[EMAIL PROTECTED]
Re: cdrtools-2.01a22 ready
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". grep only uses libc-interface. As long as the program <-> libc interface is stable it will have no problem with the libc <-> site. It is excatly THE job of libc to abstract away the "right" side. (Or the left when you assume hardware/kernel is leftmost) Only "system dependend"(hardware, kernel interfaces, ..) software (e.g. cdrecord, star, ps, lspci, iptables) have this type of problem. And btw. There is also a "binary" and "compile" compatiblity factor in this. e.g. libc6 aka glibc2 broke compatiblity with libc5 so A FEW programms needed patches to be COMPILABLE on new systems whereas (when the needed shared libraries where installed or the programm was static compiled) the libc5 binaries where still runable. Or in other words for >95% of all programms your statement is false! There is, always was and will ever be a small fraction of programs with this type of problem. The majority of software doesn't have this type of problem(s)! Or in other other words: It is wrong to assume that a random system dependend program compiled for OS revision A will run correctly on OS revision B for system. I have more other words: If Linux (for 2.8/3.0 whatever) would get incompatibel to every other Unix(type) OS AND to POSIX, BSD (and would need to drop glibc2). Then you can say what you have said. Bis denn -- Real Programmers consider "what you see is what you get" to be just as bad a concept in Text Editors as it is in women. No, the Real Programmer wants a "you asked for it, you got it" text editor -- complicated, cryptic, powerful, unforgiving, dangerous. -- 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
>From: Andy Polyakov <[EMAIL PROTECTED]> >> > star -tv < /tmp/cdev.tar.bz2 >> > ... >> > 255 7000 crw-r--r-- 1 root/other Jan 5 22:06 2004 cdev >> > >> > AS you see, this is a tar archive that includes a character >> > special with major 255 and minor 7000. >Postulate. Restoring of device entries from another architecture was >never guaranteed to provide meaningful results for following reasons: >- different platform allocate different amount of bits for major and >minor numbers, e.g. SVR3 specification reserves for 7 and 8 bits >respectively, SVR4 (e.g. Solaris and IRIX) - for 14/18, HP-UX - for >8/24, OSF - 12/20; >- restoring of devices from another platform can have undesirable effect >(imagine world writable /dev/null from another platform to coincide with >your system disk) and treated with special consideration or be avoided; Are you trying to open another unrelated thread or do you like to prove that you did not understand the current discusion? Nothing is wrong with calling: mknod cdev c 255 7000 on Linux-2.6 and for the same reason, it is completely legal to unpack the tar archive on Linux-2.6. How major()/minor() is handled is OS specific and the TAR archive does not contain any OS specifics. It does not make any sense to comment the rest of your text as it is completely unrelated to the problem. It seems that you just are unable or unwilling to admit that is is impossible to correctly use an star on Linux-2.6 if it has been compiled on Linux-2.4. Being able to use includes for me using all documented features and e.g. make backups and restores on the system. If you try to use an star compiled on 2.4 to make backups and restores on 2.6, then the device nodes may not be restored correctly, that's the problem! Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) If you don't have iso-8859-1 [EMAIL PROTECTED](work) chars I am J"org Schilling URL: http://www.fokus.fraunhofer.de/usr/schilling ftp://ftp.berlios.de/pub/schily
Re: cdrtools-2.01a22 ready
>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. 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 Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) If you don't have iso-8859-1 [EMAIL PROTECTED](work) chars I am J"org Schilling URL: http://www.fokus.fraunhofer.de/usr/schilling ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: DVD Media question
>From: Gregoire Favre <[EMAIL PROTECTED]> >Cdrecord-ProDVD-Clone 2.01a20 (i686-pc-linux-gnu) Copyright (C) >1995-2003 Jörg Schilling >Unlocked features: ProDVD Clone >Limited features: >This copy of cdrecord is licensed for: >private/research/educational_non-commercial_use >TOC Type: 1 = CD-ROM >scsidev: 'ATAPI:0,0,0' >devname: 'ATAPI' >scsibus: 0 target: 0 lun: 0 >Warning: Using ATA Packet interface. >Warning: The related libscg interface code is in pre alpha. >Warning: There may be fatal problems. >Using libscg version 'schily-0.7'. >SCSI buffer size: 64512 >atapi: 1 >Device type: Removable CD-ROM >Version: 0 >Response Format: 2 >Capabilities : >Vendor_info: 'SONY' >Identifikation : 'DVD RW DRU-500A ' >Revision : '2.0g' >Device seems to be: Generic mmc2 DVD-R/DVD-RW. >Current: none >Profile: DVD+R >Profile: DVD+RW >Profile: DVD-RW sequential overwrite >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 CD-R/CD-RW driver (mmc_cdr). >Driver flags : MMC-3 SWABAUDIO BURNFREE >Supported modes: TAO PACKET SAO SAO/R96R RAW/R96R >Drive buf size : 8112896 = 7922 KB >FIFO size : 67108864 = 65536 KB >Track 01: data 4481 MB >Total size: 5146 MB (509:52.64) = 2294448 sectors >Lout start: 5146 MB (509:54/48) = 2294448 sectors >cdrecord-prodvd: No disk / Wrong disk! I forgot to mention, that this is obviously a limitation of the drive or its firware. Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) If you don't have iso-8859-1 [EMAIL PROTECTED](work) chars I am J"org Schilling URL: http://www.fokus.fraunhofer.de/usr/schilling ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: DVD Media question
>From: Gregoire Favre <[EMAIL PROTECTED]> >I have some medi that gives me under linux: >And cdrecord-prodvd -v dev=ATAPI:0,0,0 -atip >Cdrecord-ProDVD-Clone 2.01a20 (i686-pc-linux-gnu) Copyright (C) >1995-2003 Jörg Schilling >Unlocked features: >Limited features: >TOC Type: 1 = CD-ROM >scsidev: 'ATAPI:0,0,0' >devname: 'ATAPI' >scsibus: 0 target: 0 lun: 0 >Warning: Using ATA Packet interface. >Warning: The related libscg interface code is in pre alpha. >Warning: There may be fatal problems. >Using libscg version 'schily-0.7'. >SCSI buffer size: 64512 >atapi: 1 >Device type: Removable CD-ROM >Version: 0 >Response Format: 2 >Capabilities : >Vendor_info: 'SONY' >Identifikation : 'DVD RW DRU-500A ' >Revision : '2.0g' >Device seems to be: Generic mmc2 DVD-R/DVD-RW. >Current: none >Profile: DVD+R >Profile: DVD+RW >Profile: DVD-RW sequential overwrite >Profile: DVD-RW restricted overwrite >Profile: DVD-R sequential recording >Profile: DVD-ROM >Profile: CD-RW >Profile: CD-R >Profile: CD-ROM >cdrecord-prodvd: This version of cdrecord limits DVD-R/DVD-RW support to >-dummy or 1 GB real. >cdrecord-prodvd: If you need full DVD-R/DVD-RW support, ask the Author >for cdrecord-ProDVD. >cdrecord-prodvd: Free test versions and free keys for personal use are >at ftp://ftp.berlios.de/pub/cdrecord/ProDVD/ >Using generic SCSI-3/mmc CD-R/CD-RW driver (mmc_cdr). >Driver flags : MMC-3 SWABAUDIO BURNFREE >Supported modes: TAO PACKET SAO SAO/R96R RAW/R96R >Drive buf size : 8112896 = 7922 KB >cdrecord-prodvd: No disk / Wrong disk! >But under OSX I can use the media and it tells me: >cdrecord-prodvd -v dev=IODVDServices -atip >Cdrecord-ProDVD-Clone 2.01a11 (powerpc-apple-macosx1.4) Copyright (C) 1995-2003 Jorg >Schilling >Unlocked features: >Limited features: >TOC Type: 1 = CD-ROM >scsidev: 'IODVDServices' >devname: 'IODVDServices' >scsibus: -2 target: -2 lun: -2 >Using libscg version 'schily-0.7' >cdrecord-prodvd: Warning: using inofficial libscg transport code version >(csapuntz-scsi-mac-iokit.c-1.4 '@(#)scsi-mac-iokit.c 1.4 02/10/19 Copyright >1997,2001 J. Schilling'). >atapi: 0 >Device type: Removable CD-ROM >Version: 0 >Response Format: 2 >Capabilities : >Vendor_info: 'MATSHITA' >Identifikation : 'DVD-R UJ-816 ' >Revision : 'DXJ3' >Device seems to be: Generic mmc2 DVD-R/DVD-RW. >Profile: DVD-RW restricted overwrite >Profile: DVD-RW sequential overwrite >Profile: DVD-R sequential recording (current) >Profile: DVD-ROM >Profile: CD-RW >Profile: CD-R >Profile: CD-ROM >Profile: Removable Disk >cdrecord-prodvd: This version of cdrecord limits DVD-R/DVD-RW support to -dummy or 1 >GB real. >cdrecord-prodvd: If you need full DVD-R/DVD-RW support, ask the Author for >cdrecord-ProDVD. >Using generic SCSI-3/mmc-2 DVD-R/DVD-RW driver (mmc_dvd). >Driver flags : DVD MMC-3 SWABAUDIO BURNFREE >Supported modes: TAO PACKET SAO >Drive buf size : 1671168 = 1632 KB >Current Secsize: 2048 >book type: DVD-R, Version 5 (2.5) >disc size: 120mm (0) >minimum rate:Not specified (15) >number of layers:0 >track path: Parallel Track Path (0) >layer type: Rewritable Area (2) >linear density: 0.267 m/bit (0) >track density: 0.74 m/track (0) >phys start: 196608 >phys end:196608 >end layer 0: 0 >bca: 0 >phys size:...1 >copyr prot type: 0 >region mgt info: 0 >rzone number: 1 >border number: 1 >damage: 0 >reserved: 0 blank: 1 incremental: 0 >nwa valid: 1 >rzone start:0 >next wr addr: 0 >free blocks:2298496 >blocking factor:16 >rzone size: 2298496 >last recorded addr: 0 >WARNING: Phys disk size 1 differs from rzone size 2298496! Prerecorded disk? >WARNING: Phys start: 196608 Phys end 196608 >Is it possible to use those discs under linux? Of course: First mount the Matsushita drive into the Linux PC Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) If you don't have iso-8859-1 [EMAIL PROTECTED](work) chars I am J"org Schilling URL: http://www.fokus.fraunhofer.de/usr/schilling ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: DVD Media question
On Thu, Jan 08, 2004 at 04:21:36PM +0100, Joerg Schilling wrote: > I forgot to mention, that this is obviously a limitation of the drive > or its firware. Thank, you answered my question before I sent it to you!!! Do you think it's worth writing to sony for an explanation of this limitation? Grégoire http://magma.epfl.ch/greg ICQ:16624071 mailto:[EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [Cdrecord-announces] cdrtools-2.01a24 ready
>From: Thomas Plank <[EMAIL PROTECTED]> >> ASPI was default for several years. You changed this behavior. >I'm not satisfied by changing this behavior too. >I namely do not have any problems with the SPTI method (perhaps because >I'm using NT 5.1) but what about all other users? First an important note: we need to test the code. It it is not the default, then it would remain untested. >Why isn't ASPI default and SPTI the new possible access version? Because otherwise, NT dumb users would not realize that it may work without now. >And I additionally have in mind all users of win95/98/ME, there's no >chance to get SPTI to work. It has been proved to work on win98 without problems using the same dev= strings as before. >I strongly stand up for making ASPI again the default method. It it blue screens Nt-4.0, then it makes sense to either find a workaround (other software seems to be able to do also) or introduce a hack that makes ASPI the default on NT-4.0 Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) If you don't have iso-8859-1 [EMAIL PROTECTED](work) chars I am J"org Schilling URL: http://www.fokus.fraunhofer.de/usr/schilling ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: DVD Media question
On Thu, Jan 08, 2004 at 04:14:24PM +0100, Joerg Schilling wrote: > Of course: > > First mount the Matsushita drive into the Linux PC ;-) OK, that THE solution, could I find somewhere an exlanation why it doesn't work with the Sony? Grégoire http://magma.epfl.ch/greg ICQ:16624071 mailto:[EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
growisofs for DVD-R -sort of problem
-many thanks for all the available stuff - very impressive playing with lots of things... but just wondering if I am missing something. specific problem burning DVD-R on my Laptop (Acer 290LMi intel pen cen - Linux 2.4.22) ...using growisofs (5.16) with mkisofs 2.0 growisofs -Z /dev/scd0=xyz.isofine growisofs -M /dev/scd0 abc/deffine - a few times - THEN did another growisofs - everything went fine but attempts to access DVD give message 'no media mounted' ? -which is a bit of a shame since it was doing so well. Had a couple of Gs on the disc after several sessions all nicely accessible but adding a bit more caused the failure - though disc still should have more than 1G space left - and can see from the 'burn'. All the burns proceeded without any startling remarks and completed apparently successfuly. --- If relevant - none of the discs burned were mountable unless the kernel was booted with ide-scsi enabled. (dd -ing the contents of an ok dvd to hd and mounting it only gives access to the initial 'Z' write session - presume normal?) The full contents are accessible from XP - though the 'dead' disc is not seen from XP either. --- I note that the man-page comments that not all players can handle multi-border playback - but this one seems to. - failure for 'various reasons' are also referred to. Presume I am there - but can I do anything? --- output of 'mediainfo' (straight + verbose) for the dead dvd simply says - 'no media mounted' after the drive info... and for a part burned - still ok disk is below. (But I am nervous about doing any more 'grows' for fear of losing the disc.) I hope this is not a major problem but just 'me' and apologies if this has been dealt with already - any help would be great. tks for all the fun - apologies if timewasting nick [EMAIL PROTECTED] nick]$ dvd+rw-mediainfo /dev/scd0 INQUIRY:[TOSHIBA ][DVD-ROM SD-R6112][1031] GET [CURRENT] CONFIGURATION: Mounted Media: 11h, DVD-R Sequential Media ID: MCC 00RG200 GET PERFORMANCE: Speed Descriptor#0:00/2298495 [EMAIL PROTECTED] [EMAIL PROTECTED] READ DVD STRUCTURE[#10h]: Media Book Type: 25h, DVD-R book [revision 5] Legacy lead-out at:2298496*2KB=4707319808 READ DVD STRUCTURE[#0h]: Media Book Type: 25h, DVD-R book [revision 5] Last border-out at:709136*2KB=1452310528 READ DISC INFORMATION: Disc status: appendable Number of Sessions:7 State of Last Session: empty "Next" Track: 7 Number of Tracks: 7 READ TRACK INFORMATION[#1]: Track State: complete incremental Track Start Address: 0*2KB Free Blocks: 0*2KB Track Size:65264*2KB Last Recorded Address: 10991*2KB READ TRACK INFORMATION[#2]: Track State: complete incremental Track Start Address: 93952*2KB Free Blocks: 0*2KB Track Size:54432*2KB Last Recorded Address: 148383*2KB READ TRACK INFORMATION[#3]: Track State: complete incremental Track Start Address: 154544*2KB Free Blocks: 0*2KB Track Size:18368*2KB Last Recorded Address: 172911*2KB READ TRACK INFORMATION[#4]: Track State: complete incremental Track Start Address: 179072*2KB Free Blocks: 0*2KB Track Size:14608*2KB Last Recorded Address: 193679*2KB READ TRACK INFORMATION[#5]: Track State: complete incremental Track Start Address: 199840*2KB Free Blocks: 0*2KB Track Size:447200*2KB Last Recorded Address: 647039*2KB READ TRACK INFORMATION[#6]: Track State: complete incremental Track Start Address: 654736*2KB Free Blocks: 0*2KB Track Size:54400*2KB Last Recorded Address: 709135*2KB READ TRACK INFORMATION[#7]: Track State: invisible incremental Track Start Address: 716832*2KB Next Writable Address: 716832*2KB Free Blocks: 1581056*2KB Track Size:1581056*2KB FABRICATED TOC: Track#1 : [EMAIL PROTECTED] Track#AA : [EMAIL PROTECTED] Multi-session Info:[EMAIL PROTECTED] -and verbose--- INQUIRY:[TOSHIBA ][DVD-ROM SD-R6112][1031] MODE SENSE[#3Fh]: 01:00 0a 00 00 00 00 00 00 00 00 05:40 c7 08 10 00 00 00 00 00 00 00 10 00 96 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 08:04 00 00 00 00 00 00 00 00 00 0D:00 09 00 3c 00 4b 0E:04 00 00 00 00 4b 01 ff 02 ff 00 00 00 00 1A:00 03 00 00 00 96 00 00 00 aa 1D:00 00 04 00 00 78 00 00 2A:3f 17 f1 77 29 23 10 8a 00 10 08 00 10 8a 00 18 0b 06 0b 06 00 01 00 00 00 00 0b 06 00 05 00 00 0b 06 00 00 08 45 00 00 06 e4 00 00 05 83 00 00 02 c2 MODE SENSE[#2A]: 2A:3f 17 f1 77 29 23 10 8a 00 10 08 00 10 8a 00 18 0b 06 0b 06 00 01 00 00 00 00 0b 06 00 05 00 00
Re: cdrtools-2.01a24 ready
>From [EMAIL PROTECTED] Wed Jan 7 23:39:56 2004
> > This allows to use cdrtools on NT without the need to install ASPI in
> > case you are administrator when yu run a program.
>I'm using NT4preSP7. Adaptec Aspi 4.60 is running. Normally I use
>Adaptec ASPI layer without administator rights to burn a CD.
If you call the last cdrecord with no admin rights, then it should
use ASPI because it is unable to open a SPTI file.
> > Please note that the use of SPTI is default.
>ASPI was default for several years. You changed this behavior.
ASPI was the only way to go before. If things work as expected, then
the change should not cause problems, but this is why there is a
test phase before a "final" release is published.
> > If you like to force using ASPI, use dev=ASPI:b,t,l or dev=ASPI
> > (in the -scanbus case).
>Now I'm using administrator rights and cygwin1.dll 1.5.5-cr-0x9b.
If you have administrator rights, then the code should first try SPTI.
>D:\>cdrecord -v dev=ASPI:1,1,0 blank=fast
>Ok, works.
>D:\>cdrecord dev=ASPI -scanbus
>Cdrecord-Clone 2.01a24 (i586-pc-cygwin) Copyright (C) 1995-2004 Jörg
>Schilling
>scsidev: 'ASPI'
>devname: 'ASPI'
>scsibus: -2 target: -2 lun: -2
>cdrecord: Invalid argument. Devname 'ASPI' unknown.. Cannot open SCSI
>driver.
>cdrecord: For possible targets try 'cdrecord -scanbus'. Make sure you
>are root.
>cdrecord: For possible transport specifiers try 'cdrecord dev=help'.
A bug, the code has not been completely written by me, I did only check for
the most obvious problems and reformatted acording to usual indentation
rules.
Did you try: cdrecord dev=ASPI: -scanbus
Please test the patch below
>D:\>cdrecord -scanbus
>Blue screen of death; well, broken OS. I got the same result on three
>different computers with NT4.
OK, you already mentioned it: if the OS dies, this is a OS bug.
But as other authors have been able to hack similar things, there should
be a way to prevent this from happening.
Anybody has an idea or can help?
>W2k with SPTI works without problems (cdrecord -scanbus and cd burning).
OK, thank you for the report.
I did check it on Win98 and it works out of fhe box with
cdrecord -scanbus
it prints an error message if you call: cdrecord -scanbus dev=SPTI
/*--*/
--- scsi-wnt.c ---
*** /tmp/sccs.TNaGVXDo Jan 8 15:01:43 2004
--- scsi-wnt.c Do Jan 8 15:01:29 2004
***
*** 688,700
return (-1);
}
! if ((device != NULL && *device != '\0' && strcmp(device, "SPTI") != 0
&& strcmp(device, "ASPI") != 0) || (busno == -2 && tgt == -2)) {
errno = EINVAL;
if (scgp->errstr)
js_snprintf(scgp->errstr, SCSI_ERRSTR_SIZE,
! "Devname '%s' unknown.", device);
return (-1);
}
if (AspiLoaded <= 0) { /* do not change access method on open driver */
bForceAccess = FALSE;
#ifdef PREFER_SPTI
--- 688,706
return (-1);
}
! if (device != NULL &&
! (strcmp(device, "SPTI") == 0 || strcmp(device, "ASPI") == 0) &&
! (busno < 0 && tgt < 0 && lun < 0))
! goto devok;
!
! if ((device != NULL && *device != '\0') || (busno == -2 && tgt == -2)) {
errno = EINVAL;
if (scgp->errstr)
js_snprintf(scgp->errstr, SCSI_ERRSTR_SIZE,
! "Open by 'devname' not supported on this OS");
return (-1);
}
+ devok:
if (AspiLoaded <= 0) { /* do not change access method on open driver */
bForceAccess = FALSE;
#ifdef PREFER_SPTI
Jörg
--
EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin
[EMAIL PROTECTED](uni) If you don't have iso-8859-1
[EMAIL PROTECTED](work) chars I am J"org Schilling
URL: http://www.fokus.fraunhofer.de/usr/schilling
ftp://ftp.berlios.de/pub/schily
Re: cdrtools-2.01a22 ready
>From: Andy Polyakov <[EMAIL PROTECTED]> >> > star -tv < /tmp/cdev.tar.bz2 >> > ... >> > 255 7000 crw-r--r-- 1 root/other Jan 5 22:06 2004 cdev >> > >> > AS you see, this is a tar archive that includes a character >> > special with major 255 and minor 7000. >Postulate. Restoring of device entries from another architecture was >never guaranteed to provide meaningful results for following reasons: >- different platform allocate different amount of bits for major and >minor numbers, e.g. SVR3 specification reserves for 7 and 8 bits >respectively, SVR4 (e.g. Solaris and IRIX) - for 14/18, HP-UX - for >8/24, OSF - 12/20; >- restoring of devices from another platform can have undesirable effect >(imagine world writable /dev/null from another platform to coincide with >your system disk) and treated with special consideration or be avoided; Are you trying to open another unrelated thread or do you like to prove that you did not understand the current discusion? Nothing is wrong with calling: mknod cdev c 255 7000 on Linux-2.6 and for the same reason, it is completely legal to unpack the tar archive on Linux-2.6. How major()/minor() is handled is OS specific and the TAR archive does not contain any OS specifics. It does not make any sense to comment the rest of your text as it is completely unrelated to the problem. It seems that you just are unable or unwilling to admit that is is impossible to correctly use an star on Linux-2.6 if it has been compiled on Linux-2.4. Being able to use includes for me using all documented features and e.g. make backups and restores on the system. If you try to use an star compiled on 2.4 to make backups and restores on 2.6, then the device nodes may not be restored correctly, that's the problem! Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) If you don't have iso-8859-1 [EMAIL PROTECTED](work) chars I am J"org Schilling URL: http://www.fokus.fraunhofer.de/usr/schilling ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: 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 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
Re: How to contact Jörg Schilling? - cdrecord.1 patch
>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. As your draft is only a skeleton, it currently cannot replace the old web page. Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) If you don't have iso-8859-1 [EMAIL PROTECTED](work) chars I am J"org Schilling URL: http://www.fokus.fraunhofer.de/usr/schilling ftp://ftp.berlios.de/pub/schily
growisofs for DVD-R -sort of problem
-many thanks for all the available stuff - very impressive playing with lots of things... but just wondering if I am missing something. specific problem burning DVD-R on my Laptop (Acer 290LMi intel pen cen - Linux 2.4.22) ...using growisofs (5.16) with mkisofs 2.0 growisofs -Z /dev/scd0=xyz.isofine growisofs -M /dev/scd0 abc/deffine - a few times - THEN did another growisofs - everything went fine but attempts to access DVD give message 'no media mounted' ? -which is a bit of a shame since it was doing so well. Had a couple of Gs on the disc after several sessions all nicely accessible but adding a bit more caused the failure - though disc still should have more than 1G space left - and can see from the 'burn'. All the burns proceeded without any startling remarks and completed apparently successfuly. --- If relevant - none of the discs burned were mountable unless the kernel was booted with ide-scsi enabled. (dd -ing the contents of an ok dvd to hd and mounting it only gives access to the initial 'Z' write session - presume normal?) The full contents are accessible from XP - though the 'dead' disc is not seen from XP either. --- I note that the man-page comments that not all players can handle multi-border playback - but this one seems to. - failure for 'various reasons' are also referred to. Presume I am there - but can I do anything? --- output of 'mediainfo' (straight + verbose) for the dead dvd simply says - 'no media mounted' after the drive info... and for a part burned - still ok disk is below. (But I am nervous about doing any more 'grows' for fear of losing the disc.) I hope this is not a major problem but just 'me' and apologies if this has been dealt with already - any help would be great. tks for all the fun - apologies if timewasting nick [EMAIL PROTECTED] nick]$ dvd+rw-mediainfo /dev/scd0 INQUIRY:[TOSHIBA ][DVD-ROM SD-R6112][1031] GET [CURRENT] CONFIGURATION: Mounted Media: 11h, DVD-R Sequential Media ID: MCC 00RG200 GET PERFORMANCE: Speed Descriptor#0:00/2298495 [EMAIL PROTECTED] [EMAIL PROTECTED] READ DVD STRUCTURE[#10h]: Media Book Type: 25h, DVD-R book [revision 5] Legacy lead-out at:2298496*2KB=4707319808 READ DVD STRUCTURE[#0h]: Media Book Type: 25h, DVD-R book [revision 5] Last border-out at:709136*2KB=1452310528 READ DISC INFORMATION: Disc status: appendable Number of Sessions:7 State of Last Session: empty "Next" Track: 7 Number of Tracks: 7 READ TRACK INFORMATION[#1]: Track State: complete incremental Track Start Address: 0*2KB Free Blocks: 0*2KB Track Size:65264*2KB Last Recorded Address: 10991*2KB READ TRACK INFORMATION[#2]: Track State: complete incremental Track Start Address: 93952*2KB Free Blocks: 0*2KB Track Size:54432*2KB Last Recorded Address: 148383*2KB READ TRACK INFORMATION[#3]: Track State: complete incremental Track Start Address: 154544*2KB Free Blocks: 0*2KB Track Size:18368*2KB Last Recorded Address: 172911*2KB READ TRACK INFORMATION[#4]: Track State: complete incremental Track Start Address: 179072*2KB Free Blocks: 0*2KB Track Size:14608*2KB Last Recorded Address: 193679*2KB READ TRACK INFORMATION[#5]: Track State: complete incremental Track Start Address: 199840*2KB Free Blocks: 0*2KB Track Size:447200*2KB Last Recorded Address: 647039*2KB READ TRACK INFORMATION[#6]: Track State: complete incremental Track Start Address: 654736*2KB Free Blocks: 0*2KB Track Size:54400*2KB Last Recorded Address: 709135*2KB READ TRACK INFORMATION[#7]: Track State: invisible incremental Track Start Address: 716832*2KB Next Writable Address: 716832*2KB Free Blocks: 1581056*2KB Track Size:1581056*2KB FABRICATED TOC: Track#1 : [EMAIL PROTECTED] Track#AA : [EMAIL PROTECTED] Multi-session Info:[EMAIL PROTECTED] -and verbose--- INQUIRY:[TOSHIBA ][DVD-ROM SD-R6112][1031] MODE SENSE[#3Fh]: 01:00 0a 00 00 00 00 00 00 00 00 05:40 c7 08 10 00 00 00 00 00 00 00 10 00 96 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 08:04 00 00 00 00 00 00 00 00 00 0D:00 09 00 3c 00 4b 0E:04 00 00 00 00 4b 01 ff 02 ff 00 00 00 00 1A:00 03 00 00 00 96 00 00 00 aa 1D:00 00 04 00 00 78 00 00 2A:3f 17 f1 77 29 23 10 8a 00 10 08 00 10 8a 00 18 0b 06 0b 06 00 01 00 00 00 00 0b 06 00 05 00 00 0b 06 00 00 08 45 00 00 06 e4 00 00 05 83 00 00 02 c2 MODE SENSE[#2A]: 2A:3f 17 f1 77 29 23 10 8a 00 10 08 00 10 8a 00 18 0b 06 0b 06 00 01 00 00 00 00 0b 06 00 05 00 00
Re: cdrtools-2.01a24 ready
>From [EMAIL PROTECTED] Wed Jan 7 23:39:56 2004
> > This allows to use cdrtools on NT without the need to install ASPI in
> > case you are administrator when yu run a program.
>I'm using NT4preSP7. Adaptec Aspi 4.60 is running. Normally I use
>Adaptec ASPI layer without administator rights to burn a CD.
If you call the last cdrecord with no admin rights, then it should
use ASPI because it is unable to open a SPTI file.
> > Please note that the use of SPTI is default.
>ASPI was default for several years. You changed this behavior.
ASPI was the only way to go before. If things work as expected, then
the change should not cause problems, but this is why there is a
test phase before a "final" release is published.
> > If you like to force using ASPI, use dev=ASPI:b,t,l or dev=ASPI
> > (in the -scanbus case).
>Now I'm using administrator rights and cygwin1.dll 1.5.5-cr-0x9b.
If you have administrator rights, then the code should first try SPTI.
>D:\>cdrecord -v dev=ASPI:1,1,0 blank=fast
>Ok, works.
>D:\>cdrecord dev=ASPI -scanbus
>Cdrecord-Clone 2.01a24 (i586-pc-cygwin) Copyright (C) 1995-2004 Jörg
>Schilling
>scsidev: 'ASPI'
>devname: 'ASPI'
>scsibus: -2 target: -2 lun: -2
>cdrecord: Invalid argument. Devname 'ASPI' unknown.. Cannot open SCSI
>driver.
>cdrecord: For possible targets try 'cdrecord -scanbus'. Make sure you
>are root.
>cdrecord: For possible transport specifiers try 'cdrecord dev=help'.
A bug, the code has not been completely written by me, I did only check for
the most obvious problems and reformatted acording to usual indentation
rules.
Did you try: cdrecord dev=ASPI: -scanbus
Please test the patch below
>D:\>cdrecord -scanbus
>Blue screen of death; well, broken OS. I got the same result on three
>different computers with NT4.
OK, you already mentioned it: if the OS dies, this is a OS bug.
But as other authors have been able to hack similar things, there should
be a way to prevent this from happening.
Anybody has an idea or can help?
>W2k with SPTI works without problems (cdrecord -scanbus and cd burning).
OK, thank you for the report.
I did check it on Win98 and it works out of fhe box with
cdrecord -scanbus
it prints an error message if you call: cdrecord -scanbus dev=SPTI
/*--*/
--- scsi-wnt.c ---
*** /tmp/sccs.TNaGVXDo Jan 8 15:01:43 2004
--- scsi-wnt.c Do Jan 8 15:01:29 2004
***
*** 688,700
return (-1);
}
! if ((device != NULL && *device != '\0' && strcmp(device, "SPTI") != 0
&& strcmp(device, "ASPI") != 0) || (busno == -2 && tgt == -2)) {
errno = EINVAL;
if (scgp->errstr)
js_snprintf(scgp->errstr, SCSI_ERRSTR_SIZE,
! "Devname '%s' unknown.", device);
return (-1);
}
if (AspiLoaded <= 0) { /* do not change access method on open driver */
bForceAccess = FALSE;
#ifdef PREFER_SPTI
--- 688,706
return (-1);
}
! if (device != NULL &&
! (strcmp(device, "SPTI") == 0 || strcmp(device, "ASPI") == 0) &&
! (busno < 0 && tgt < 0 && lun < 0))
! goto devok;
!
! if ((device != NULL && *device != '\0') || (busno == -2 && tgt == -2)) {
errno = EINVAL;
if (scgp->errstr)
js_snprintf(scgp->errstr, SCSI_ERRSTR_SIZE,
! "Open by 'devname' not supported on this OS");
return (-1);
}
+ devok:
if (AspiLoaded <= 0) { /* do not change access method on open driver */
bForceAccess = FALSE;
#ifdef PREFER_SPTI
Jörg
--
EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin
[EMAIL PROTECTED](uni) If you don't have iso-8859-1
[EMAIL PROTECTED](work) chars I am J"org Schilling
URL: http://www.fokus.fraunhofer.de/usr/schilling ftp://ftp.berlios.de/pub/schily
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: cdrtools-2.01a22 ready
>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.
>> 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.
Well, in Solaris this is true for at least 12 years:
#define OLDDEV 0/* old device format */
#define NEWDEV 1/* new device format */
#define makedev(maj, min) (__makedev(NEWDEV, maj, min))
#define major(dev) (__major(NEWDEV, dev))
#define minor(dev) (__minor(NEWDEV, dev))
...
>> 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
Do you _really_ know if the major()/minor()/makedev() change introduced
the _only_ incompatibility?
>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
>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.
There is a general rule that is many many years old:
If you like to run a binary on differen OS versions, compile on the oldest
and make decent tests to verify of there are problems.
As the program above calls ioctl() and other OS dependent interfaces,
you cannot grant that it will work.
>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.
Jörg
--
EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin
[EMAIL PROTECTED](uni) If you don't have iso-8859-1
[EMAIL PROTECTED](work) chars I am J"org Schilling
URL: http://www.fokus.fraunhofer.de/usr/schilling
ftp://ftp.berlios.de/pub/schily
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 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
>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. As your draft is only a skeleton, it currently cannot replace the old web page. Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) If you don't have iso-8859-1 [EMAIL PROTECTED](work) chars I am J"org Schilling URL: http://www.fokus.fraunhofer.de/usr/schilling ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: cdrtools-2.01a22 ready
>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.
>> 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.
Well, in Solaris this is true for at least 12 years:
#define OLDDEV 0/* old device format */
#define NEWDEV 1/* new device format */
#define makedev(maj, min) (__makedev(NEWDEV, maj, min))
#define major(dev) (__major(NEWDEV, dev))
#define minor(dev) (__minor(NEWDEV, dev))
...
>> 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
Do you _really_ know if the major()/minor()/makedev() change introduced
the _only_ incompatibility?
>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
>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.
There is a general rule that is many many years old:
If you like to run a binary on differen OS versions, compile on the oldest
and make decent tests to verify of there are problems.
As the program above calls ioctl() and other OS dependent interfaces,
you cannot grant that it will work.
>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.
Jörg
--
EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin
[EMAIL PROTECTED](uni) If you don't have iso-8859-1
[EMAIL PROTECTED](work) chars I am J"org Schilling
URL: http://www.fokus.fraunhofer.de/usr/schilling ftp://ftp.berlios.de/pub/schily
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
DVD Media question
Hello, I have some medi that gives me under linux: Cdrecord-ProDVD-Clone 2.01a20 (i686-pc-linux-gnu) Copyright (C) 1995-2003 Jörg Schilling Unlocked features: ProDVD Clone Limited features: This copy of cdrecord is licensed for: private/research/educational_non-commercial_use TOC Type: 1 = CD-ROM scsidev: 'ATAPI:0,0,0' devname: 'ATAPI' scsibus: 0 target: 0 lun: 0 Warning: Using ATA Packet interface. Warning: The related libscg interface code is in pre alpha. Warning: There may be fatal problems. Using libscg version 'schily-0.7'. SCSI buffer size: 64512 atapi: 1 Device type: Removable CD-ROM Version: 0 Response Format: 2 Capabilities : Vendor_info: 'SONY' Identifikation : 'DVD RW DRU-500A ' Revision : '2.0g' Device seems to be: Generic mmc2 DVD-R/DVD-RW. Current: none Profile: DVD+R Profile: DVD+RW Profile: DVD-RW sequential overwrite 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 CD-R/CD-RW driver (mmc_cdr). Driver flags : MMC-3 SWABAUDIO BURNFREE Supported modes: TAO PACKET SAO SAO/R96R RAW/R96R Drive buf size : 8112896 = 7922 KB FIFO size : 67108864 = 65536 KB Track 01: data 4481 MB Total size: 5146 MB (509:52.64) = 2294448 sectors Lout start: 5146 MB (509:54/48) = 2294448 sectors cdrecord-prodvd: No disk / Wrong disk! And cdrecord-prodvd -v dev=ATAPI:0,0,0 -atip Cdrecord-ProDVD-Clone 2.01a20 (i686-pc-linux-gnu) Copyright (C) 1995-2003 Jörg Schilling Unlocked features: Limited features: TOC Type: 1 = CD-ROM scsidev: 'ATAPI:0,0,0' devname: 'ATAPI' scsibus: 0 target: 0 lun: 0 Warning: Using ATA Packet interface. Warning: The related libscg interface code is in pre alpha. Warning: There may be fatal problems. Using libscg version 'schily-0.7'. SCSI buffer size: 64512 atapi: 1 Device type: Removable CD-ROM Version: 0 Response Format: 2 Capabilities : Vendor_info: 'SONY' Identifikation : 'DVD RW DRU-500A ' Revision : '2.0g' Device seems to be: Generic mmc2 DVD-R/DVD-RW. Current: none Profile: DVD+R Profile: DVD+RW Profile: DVD-RW sequential overwrite Profile: DVD-RW restricted overwrite Profile: DVD-R sequential recording Profile: DVD-ROM Profile: CD-RW Profile: CD-R Profile: CD-ROM cdrecord-prodvd: This version of cdrecord limits DVD-R/DVD-RW support to -dummy or 1 GB real. cdrecord-prodvd: If you need full DVD-R/DVD-RW support, ask the Author for cdrecord-ProDVD. cdrecord-prodvd: Free test versions and free keys for personal use are at ftp://ftp.berlios.de/pub/cdrecord/ProDVD/ Using generic SCSI-3/mmc CD-R/CD-RW driver (mmc_cdr). Driver flags : MMC-3 SWABAUDIO BURNFREE Supported modes: TAO PACKET SAO SAO/R96R RAW/R96R Drive buf size : 8112896 = 7922 KB cdrecord-prodvd: No disk / Wrong disk! But under OSX I can use the media and it tells me: cdrecord-prodvd -v dev=IODVDServices -atip Cdrecord-ProDVD-Clone 2.01a11 (powerpc-apple-macosx1.4) Copyright (C) 1995-2003 Jorg Schilling Unlocked features: Limited features: TOC Type: 1 = CD-ROM scsidev: 'IODVDServices' devname: 'IODVDServices' scsibus: -2 target: -2 lun: -2 Using libscg version 'schily-0.7' cdrecord-prodvd: Warning: using inofficial libscg transport code version (csapuntz-scsi-mac-iokit.c-1.4 '@(#)scsi-mac-iokit.c 1.4 02/10/19 Copyright 1997,2001 J. Schilling'). atapi: 0 Device type: Removable CD-ROM Version: 0 Response Format: 2 Capabilities : Vendor_info: 'MATSHITA' Identifikation : 'DVD-R UJ-816 ' Revision : 'DXJ3' Device seems to be: Generic mmc2 DVD-R/DVD-RW. Profile: DVD-RW restricted overwrite Profile: DVD-RW sequential overwrite Profile: DVD-R sequential recording (current) Profile: DVD-ROM Profile: CD-RW Profile: CD-R Profile: CD-ROM Profile: Removable Disk cdrecord-prodvd: This version of cdrecord limits DVD-R/DVD-RW support to -dummy or 1 GB real. cdrecord-prodvd: If you need full DVD-R/DVD-RW support, ask the Author for cdrecord-ProDVD. Using generic SCSI-3/mmc-2 DVD-R/DVD-RW driver (mmc_dvd). Driver flags : DVD MMC-3 SWABAUDIO BURNFREE Supported modes: TAO PACKET SAO Drive buf size : 1671168 = 1632 KB Current Secsize: 2048 book type: DVD-R, Version 5 (2.5) disc size: 120mm (0) minimum rate:Not specified (15) number of layers:0 track path: Parallel Track Path (0) layer type: Rewritable Area (2) linear density: 0.267 m/bit (0) track density: 0.74 m/track (0) phys start: 196608 phys end:196608 end layer 0: 0 bca: 0 phys size:...1 copyr prot type: 0 region mgt info: 0 rzone number: 1 border number: 1 damage: 0 reserved: 0 blank: 1 incremental: 0 nwa valid: 1 rzone start:0 next wr addr: 0 free blocks:2298496 blocking factor:16 rzone size: 2298496 last recorded addr: 0 WARNING: Phys disk size 1 differs from rzone size 2298496! Prerecor
DVD Media question
Hello, I have some medi that gives me under linux: Cdrecord-ProDVD-Clone 2.01a20 (i686-pc-linux-gnu) Copyright (C) 1995-2003 Jörg Schilling Unlocked features: ProDVD Clone Limited features: This copy of cdrecord is licensed for: private/research/educational_non-commercial_use TOC Type: 1 = CD-ROM scsidev: 'ATAPI:0,0,0' devname: 'ATAPI' scsibus: 0 target: 0 lun: 0 Warning: Using ATA Packet interface. Warning: The related libscg interface code is in pre alpha. Warning: There may be fatal problems. Using libscg version 'schily-0.7'. SCSI buffer size: 64512 atapi: 1 Device type: Removable CD-ROM Version: 0 Response Format: 2 Capabilities : Vendor_info: 'SONY' Identifikation : 'DVD RW DRU-500A ' Revision : '2.0g' Device seems to be: Generic mmc2 DVD-R/DVD-RW. Current: none Profile: DVD+R Profile: DVD+RW Profile: DVD-RW sequential overwrite 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 CD-R/CD-RW driver (mmc_cdr). Driver flags : MMC-3 SWABAUDIO BURNFREE Supported modes: TAO PACKET SAO SAO/R96R RAW/R96R Drive buf size : 8112896 = 7922 KB FIFO size : 67108864 = 65536 KB Track 01: data 4481 MB Total size: 5146 MB (509:52.64) = 2294448 sectors Lout start: 5146 MB (509:54/48) = 2294448 sectors cdrecord-prodvd: No disk / Wrong disk! And cdrecord-prodvd -v dev=ATAPI:0,0,0 -atip Cdrecord-ProDVD-Clone 2.01a20 (i686-pc-linux-gnu) Copyright (C) 1995-2003 Jörg Schilling Unlocked features: Limited features: TOC Type: 1 = CD-ROM scsidev: 'ATAPI:0,0,0' devname: 'ATAPI' scsibus: 0 target: 0 lun: 0 Warning: Using ATA Packet interface. Warning: The related libscg interface code is in pre alpha. Warning: There may be fatal problems. Using libscg version 'schily-0.7'. SCSI buffer size: 64512 atapi: 1 Device type: Removable CD-ROM Version: 0 Response Format: 2 Capabilities : Vendor_info: 'SONY' Identifikation : 'DVD RW DRU-500A ' Revision : '2.0g' Device seems to be: Generic mmc2 DVD-R/DVD-RW. Current: none Profile: DVD+R Profile: DVD+RW Profile: DVD-RW sequential overwrite Profile: DVD-RW restricted overwrite Profile: DVD-R sequential recording Profile: DVD-ROM Profile: CD-RW Profile: CD-R Profile: CD-ROM cdrecord-prodvd: This version of cdrecord limits DVD-R/DVD-RW support to -dummy or 1 GB real. cdrecord-prodvd: If you need full DVD-R/DVD-RW support, ask the Author for cdrecord-ProDVD. cdrecord-prodvd: Free test versions and free keys for personal use are at ftp://ftp.berlios.de/pub/cdrecord/ProDVD/ Using generic SCSI-3/mmc CD-R/CD-RW driver (mmc_cdr). Driver flags : MMC-3 SWABAUDIO BURNFREE Supported modes: TAO PACKET SAO SAO/R96R RAW/R96R Drive buf size : 8112896 = 7922 KB cdrecord-prodvd: No disk / Wrong disk! But under OSX I can use the media and it tells me: cdrecord-prodvd -v dev=IODVDServices -atip Cdrecord-ProDVD-Clone 2.01a11 (powerpc-apple-macosx1.4) Copyright (C) 1995-2003 Jorg Schilling Unlocked features: Limited features: TOC Type: 1 = CD-ROM scsidev: 'IODVDServices' devname: 'IODVDServices' scsibus: -2 target: -2 lun: -2 Using libscg version 'schily-0.7' cdrecord-prodvd: Warning: using inofficial libscg transport code version (csapuntz-scsi-mac-iokit.c-1.4 '@(#)scsi-mac-iokit.c 1.4 02/10/19 Copyright 1997,2001 J. Schilling'). atapi: 0 Device type: Removable CD-ROM Version: 0 Response Format: 2 Capabilities : Vendor_info: 'MATSHITA' Identifikation : 'DVD-R UJ-816 ' Revision : 'DXJ3' Device seems to be: Generic mmc2 DVD-R/DVD-RW. Profile: DVD-RW restricted overwrite Profile: DVD-RW sequential overwrite Profile: DVD-R sequential recording (current) Profile: DVD-ROM Profile: CD-RW Profile: CD-R Profile: CD-ROM Profile: Removable Disk cdrecord-prodvd: This version of cdrecord limits DVD-R/DVD-RW support to -dummy or 1 GB real. cdrecord-prodvd: If you need full DVD-R/DVD-RW support, ask the Author for cdrecord-ProDVD. Using generic SCSI-3/mmc-2 DVD-R/DVD-RW driver (mmc_dvd). Driver flags : DVD MMC-3 SWABAUDIO BURNFREE Supported modes: TAO PACKET SAO Drive buf size : 1671168 = 1632 KB Current Secsize: 2048 book type: DVD-R, Version 5 (2.5) disc size: 120mm (0) minimum rate:Not specified (15) number of layers:0 track path: Parallel Track Path (0) layer type: Rewritable Area (2) linear density: 0.267 m/bit (0) track density: 0.74 m/track (0) phys start: 196608 phys end:196608 end layer 0: 0 bca: 0 phys size:...1 copyr prot type: 0 region mgt info: 0 rzone number: 1 border number: 1 damage: 0 reserved: 0 blank: 1 incremental: 0 nwa valid: 1 rzone start:0 next wr addr: 0 free blocks:2298496 blocking factor:16 rzone size: 2298496 last recorded addr: 0 WARNING: Phys disk size 1 differs from rzone size 2298496! Prerecor
Re: [Cdrecord-announces] cdrtools-2.01a24 ready
Udo Buedel ([EMAIL PROTECTED]) wrote: >> Please note that the use of SPTI is default. > ASPI was default for several years. You changed this behavior. I'm not satisfied by changing this behavior too. I namely do not have any problems with the SPTI method (perhaps because I'm using NT 5.1) but what about all other users? Why isn't ASPI default and SPTI the new possible access version? > D:\>cdrecord -scanbus > Blue screen of death; well, broken OS. I got the same result on three > different computers with NT4. And I additionally have in mind all users of win95/98/ME, there's no chance to get SPTI to work. I strongly stand up for making ASPI again the default method. > W2k with SPTI works without problems (cdrecord -scanbus and cd burning). Win XP Prof. does the same here. -- mfg Thomas
Re: [Cdrecord-announces] cdrtools-2.01a24 ready
Udo Buedel ([EMAIL PROTECTED]) wrote: >> Please note that the use of SPTI is default. > ASPI was default for several years. You changed this behavior. I'm not satisfied by changing this behavior too. I namely do not have any problems with the SPTI method (perhaps because I'm using NT 5.1) but what about all other users? Why isn't ASPI default and SPTI the new possible access version? > D:\>cdrecord -scanbus > Blue screen of death; well, broken OS. I got the same result on three > different computers with NT4. And I additionally have in mind all users of win95/98/ME, there's no chance to get SPTI to work. I strongly stand up for making ASPI again the default method. > W2k with SPTI works without problems (cdrecord -scanbus and cd burning). Win XP Prof. does the same here. -- mfg Thomas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
