Re: Burning a single File
> >I have the following "Problem". I have a single file as the output of a > >pipe that i wan't to burn on a cdr. > > > >Is there a way to circumvent writting that file into a directory and then > >"mkisofs"ing that directory? > > > >A way of directly piping that file into mkisofs like > > > >mkisofs --one_file_from_stdin --filename=file --filesize=681574400 <...> > I assume the piped file is not an ISO9660 image already and what you > want is to create an ISO9660 image containing a single file? Right. > (your "example" above won't fit on a standard 650M CD ...) 73:5 You haven't done the math right? Currently i get 80Min CDRs for 0.80 DM (roughly 0.40$) per piece. So i could record 50MB more. But i have only 1.1 GB for 1.3(2x74Min)-1.4(2x80Min) so i haven't changed the script. :-) > It is possible to pipe any data to cdrecord - doesn't have to be an ISO9660 > image - the data could be a tar archive - of course, the CD will not > mountable as a file system, but you can use tar to extract data from > the raw device as you can with any other media. I know. And i pracitise that more or less often. But for THIS case that isn't an option. 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]
OT: Slowing down a (SCSI)-DVD-Drive
#Include Is it possibel to make such a drive spin slower? I've got 2 "Pioneer DVD-U04S" but they are MUCH to loud for watching movies. So i searched on freshmeat, but the 2 Programs i found don't work. :-(( (OS is Linux 2.2.17) 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: OT: Slowing down a (SCSI)-DVD-Drive
#include > > I've got 2 "Pioneer DVD-U04S" but they are MUCH to loud for watching > > movies. So i searched on freshmeat, but the 2 Programs i found don't > > work. :-(( > If it's MMC compliant plextor-tool will work (or at least should). If not Plextor-Tool checks for drive-name and only works with my (Plextor) PX32-TSi > it's only a matter to discover which SCSI commands are implemented. > Giuseppe Thats the big question. cdrom_speed, which issues an ioctl, doesn't work. cdctl doesn't get anything right. (It can't even eject a CD) 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: OT: Slowing down a (SCSI)-DVD-Drive
> > > > I've got 2 "Pioneer DVD-U04S" but they are MUCH to loud for watching > > > > movies. So i searched on freshmeat, but the 2 Programs i found don't > > > > work. :-(( > > > If it's MMC compliant plextor-tool will work (or at least should). If not > > > > Plextor-Tool checks for drive-name and only works with my (Plextor) > > PX32-TSi > AFAIK not true. I have 0.4.0 and can control my TEAC drive as well. I had the wrong one. Now everything EXCEPT setting speed works. (Setting idle-timeout e.x. works) > > > it's only a matter to discover which SCSI commands are implemented. > > > Giuseppe > > > > Thats the big question. > > > > cdrom_speed, which issues an ioctl, doesn't work. > What command? Ioctl or direct sg is only the "transport" layer. It issues the "Linux" ioctl 0x05 over /dev/sr 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]
Burning a single File
#Include I have the following "Problem". I have a single file as the output of a pipe that i wan't to burn on a cdr. Is there a way to circumvent writting that file into a directory and then "mkisofs"ing that directory? A way of directly piping that file into mkisofs like mkisofs --one_file_from_stdin --filename=file --filesize=681574400 <...> 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: Silly question - selecting all files to create an image
> I do apologize for sending a silly question to the list but I checked > cdrecord-mkisofs documentation and found nothing about it (There are loads of > files. Perhaps I miss the right one). > I need to pipe to an image created from all files in a dir (not > including the dirs within) to cdrecord. How can I do that? mkisofs -r * > doesn't work. I tried gcombust with its file manager but it didn't work > either. I am running 1.9a05. Write a script that (hard/sym)links all Files into an other. Then create an image from "the other" dir. 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]
Burning a single file, comming from a pipe, onto a CD-R
#incude Many, many, many month ago i asked how i could burn a single file, comming from a Pipe, onto a CD without writing it to disk first. Someone suggested to use a FIFO. Today i tried that. mkdir testdir mkfifo testdir/testfile dd if=/dev/zero of=testdir/testfile bs=1024 count=1024 mkisofs -r [-f] -o image1.raw testdir Output is this: (mkisofs from SuSE 7.1) Total translation table size: 0 Total rockridge attributes bytes: 266 Total directory bytes: 0 Path table size(bytes): 10 Max brk space used 3ba4 25 extents written (0 Mb) "ls -la" say this. -rw-r--r--1 root root51200 Mar 31 12:48 /roast/image1.raw Output is this: (Current mkisofs from 1.10a17) Total translation table size: 0 Total rockridge attributes bytes: 266 Total directory bytes: 0 Path table size(bytes): 10 Max brk space used 3404 48 extents written (0 Mb) "ls -la" say this. -rw-r--r--1 root root98304 Mar 31 12:59 /roast/image1.raw 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]
What does this message mean
#Include Just got "other" CDRs then "usual". And it's the first time this Message Disk sub type: Medium Type B, low Beta category (B-) (4) appeared. What does it mean? (Whole Message is this: ATIP info from disk: Indicated writing power: 5 Is not unrestricted Is not erasable Disk sub type: Medium Type B, low Beta category (B-) (4) ATIP start of lead in: -11767 (97:25/08) ATIP start of lead out: 359775 (79:59/00) Disk type:Short strategy type (Phthalocyanine or similar) Manuf. index: 64 Manufacturer: MPO Blocks total: 359775 Blocks current: 359775 Blocks remaining: 21830 ) 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]
2xTeac CD-R58S
#Include Ich habe 2x $subject Brenner. Kann ich die am gleichen Kabelstrang betreiben ohne das die sich gegenseitig "beeinflussen" (Wenn man z.B. das Brennen zu unterschiedlichen Zeitpunkten startet) (Vorerst werde ich die an unterschiedlichen SCSI-Adaptern betreiben.) 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]
Pioneer DVR-A03
#include
Re: Bill Davoidsen still has illegal mailer settings
> Sorry guys, > > this seems to be the only way to send Bill mail as he still refuses to make > hist mailer standard compliant! You aren't any better. Your MUA is "broken", "misconfigured" or (User is) "ignorand" Your MUA doesn't set the "In-Reply-to" and/or "references"-Headers Discussions with more than "a few" Mails (With a high percentage from you) are absolutly HARD to read because no thread-tree can be build. Sometimes there are Threads with >100 Mails in L.K.M.L., but nearly everybody has correctly configured MUAs (Even "pine" does it correctly) so you have a "perfect" thread-tree. (At least ALL regulars use "good" MUAs (Linus, Alan, Andre, Andrea, David ...) Sometimes this works so good that you can't see the thread "correctly" anymore, because the tree is so wide that it grew over the right border. 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: Bill Davoidsen still has illegal mailer settings
On Thu, 14 Jun 2001, Joerg Schilling wrote: > > >From: Matthias Schniedermeyer <[EMAIL PROTECTED]> > >> Sorry guys, > >> > >> this seems to be the only way to send Bill mail as he still refuses to make > >> hist mailer standard compliant! > > >You aren't any better. > > >Your MUA is "broken", "misconfigured" or (User is) "ignorand" > > >Your MUA doesn't set the "In-Reply-to" and/or "references"-Headers > > >Discussions with more than "a few" Mails (With a high percentage from you) > >are absolutly HARD to read because no thread-tree can be build. > > I am using the standard UNIX mail program and I see no reason why I should > change this. You want people to write emails to the gtar Authors to convince them to make gtar POSIX-compliant. Conclusion: YOU have to write a complain to the authors of that programm, so that they will make it "compliant" to RECENT Email-Standards. (Or patch it yourself, implementing this feature should be TRIVIAL) Btw. You know that RFC-822 is "deprecated", RFC-2822 is now THE Email-Standard. (I don't KNOW it, but i think those headers are defined in RFC-2822) Conclusion: EMail-Programm violating RFC-2822 have to be FIXED. Maybe i should fetch RFC-2822 and look if you HAVE TO fix you MUA. 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: Bill Davoidsen still has illegal mailer settings
On Thu, Jun 14, 2001 at 02:41:49AM +0200, Joerg Schilling wrote: > >From: Martin Lichtin <[EMAIL PROTECTED]> > > >> I am using the standard UNIX mail program > > >That a POSIX standard? > > The behavior of the program is covered by POSIX: > > http://www.opengroup.org/onlinepubs/7908799/xcu/mailx.html > > The mail data format is AFAIK not covered by POSIX. RFC-2822 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]
cdrecord "weakness"
#include cdrecord has a problem with SCSI-(RAID)-Controllers that don't allocate a ne scsibus for each Channels. Yesterday i got a 5 Channel FAST-SCSI RAID-Controller (ICP-Vortex) I have 4 CD-Rs and every one has a dedicated channel on the new Controller. First i had configured every CD-R to ID-0. But then cdrecord could only see the first one. Now i configured every drive with diffrent IDs (cdrecord -scanbus attached). But that's not "the(tm)" solution. AFAIK other OSses use "Adapter,Channel,ID,Lun" Adresses too. Why does cdrecord "only" use "scsibus,ID,Lun" (Hmmm. Do ANY cases exist where the LUNs are needed? (i only know 1 case, SCSI2SCSI-Bridges which map the ID from the "slave"-Channels to LUNs of the ID on the Main-Channel. But i think those bridges are "unusual") -- cdrecord -scanbus -- scsibus0: 0,0,0 0) * 0,1,0 1) * 0,2,0 2) * 0,3,0 3) * 0,4,0 4) * 0,5,0 5) * 0,6,0 6) 'IBM ' 'DDYS-T18350N' 'S93E' Disk 0,7,0 7) * scsibus1: 1,0,0 100) * 1,1,0 101) * 1,2,0 102) * 1,3,0 103) * cdrecord: Warning: controller returns wrong size for CD capabilities page. 1,4,0 104) 'PIONEER ' 'DVD-ROM DVD-303 ' '1.10' Removable CD-ROM 1,5,0 105) * 1,6,0 106) * 1,7,0 107) * scsibus3: 3,0,0 300) 'TEAC' 'CD-R58S ' '1.0H' Removable CD-ROM 3,1,0 301) 'TEAC' 'CD-R58S ' '1.0N' Removable CD-ROM 3,2,0 302) 'PIONEER ' 'DVD-ROM DVD-304 ' '1.03' Removable CD-ROM 3,3,0 303) 'PIONEER ' 'DVD-ROM DVD-304 ' '1.03' Removable CD-ROM 3,4,0 304) 'TEAC' 'CD-R58S ' '1.0K' Removable CD-ROM 3,5,0 305) * 3,6,0 306) 'TEAC' 'CD-R58S ' '1.0P' Removable CD-ROM 3,7,0 307) * -- end -- -- /proc/scsi/scsi -- Attached devices: Host: scsi0 Channel: 00 Id: 06 Lun: 00 Vendor: IBM Model: DDYS-T18350N Rev: S93E Type: Direct-AccessANSI SCSI revision: 03 Host: scsi1 Channel: 00 Id: 04 Lun: 00 Vendor: PIONEER Model: DVD-ROM DVD-303 Rev: 1.10 Type: CD-ROM ANSI SCSI revision: 02 Host: scsi3 Channel: 01 Id: 02 Lun: 00 Vendor: PIONEER Model: DVD-ROM DVD-304 Rev: 1.03 Type: CD-ROM ANSI SCSI revision: 02 Host: scsi3 Channel: 01 Id: 03 Lun: 00 Vendor: PIONEER Model: DVD-ROM DVD-304 Rev: 1.03 Type: CD-ROM ANSI SCSI revision: 02 Host: scsi3 Channel: 02 Id: 00 Lun: 00 Vendor: TEAC Model: CD-R58S Rev: 1.0H Type: CD-ROM ANSI SCSI revision: 02 Host: scsi3 Channel: 03 Id: 01 Lun: 00 Vendor: TEAC Model: CD-R58S Rev: 1.0N Type: CD-ROM ANSI SCSI revision: 02 Host: scsi3 Channel: 04 Id: 06 Lun: 00 Vendor: TEAC Model: CD-R58S Rev: 1.0P Type: CD-ROM ANSI SCSI revision: 02 Host: scsi3 Channel: 05 Id: 04 Lun: 00 Vendor: TEAC Model: CD-R58S Rev: 1.0K Type: CD-ROM ANSI SCSI revision: 02 -- end -- 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]
cdrecord "weakness" Part II
#include Now i tried to record something with my new RAID-Controller but i had no luck at all. # cdrecord -eject -dao speed=8 dev=3,0,0 fs=30m -v Cdrecord 1.10 (i686-pc-linux-gnu) Copyright (C) 1995-2001 Jörg Schilling TOC Type: 1 = CD-ROM scsidev: '3,0,0' scsibus: 3 target: 0 lun: 0 Linux sg driver version: 3.1.17 cdrecord: Warning Linux Bus mapping botch. Using libscg version 'schily-0.5' atapi: 0 Device type: Removable CD-ROM Version: 2 Response Format: 2 Capabilities : RELADR SYNC LINKED Vendor_info: 'TEAC' Identifikation : 'CD-R58S ' Revision : '1.0H' Device seems to be: Generic CD-ROM. cdrecord: Sorry, no CD/DVD-Recorder or unsupported CD/DVD-Recorder found on this target. # cdrecord -eject -dao driver=mmc_cdr speed=8 dev=3,0,0 fs=30m -v Cdrecord 1.10 (i686-pc-linux-gnu) Copyright (C) 1995-2001 Jörg Schilling TOC Type: 1 = CD-ROM scsidev: '3,0,0' scsibus: 3 target: 0 lun: 0 Linux sg driver version: 3.1.17 cdrecord: Warning Linux Bus mapping botch. Using libscg version 'schily-0.5' atapi: 0 Device type: Removable CD-ROM Version: 2 Response Format: 2 Capabilities : RELADR SYNC LINKED Vendor_info: 'TEAC' Identifikation : 'CD-R58S ' Revision : '1.0H' Device seems to be: Generic CD-ROM. cdrecord: WARNING: Trying to use other driver on known device. cdrecord: Cannot attach driver for CD/DVD-Recorder. (The "cdrecord: Warning Linux Bus mapping botch." message comes more often with the other CD-Rs (2x for 3,1,0. 3x for 3,6,0. 4x for 3,4,0)) 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]
BIG FAT BUG in cdrecord
#include When you abort cdrecord while the 10 second "last chance" then cdrecord exits with errorlevel "0". That destoy me an image because my burn-script does "if burning ok then delete image". (And i accedently called the false script, then i wanted to abort and use the correct one. I should have aborted at the "wrong" point, which gives an errorleven != 0) 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: BIG FAT BUG in cdrecord
> >When you abort cdrecord while the 10 second "last chance" then cdrecord > >exits with errorlevel "0". > > >That destoy me an image because my burn-script does "if burning ok then > >delete image". (And i accedently called the false script, then i wanted to > >abort and use the correct one. I should have aborted at the "wrong" point, > >which gives an errorleven != 0) > > I would not call that a big fat bug. The big fat bugs have never been found > be people outside It cost my CPU 1335m of "99,9%" running the "undelfs" from "Midnight Commander" (The only undelete-program i'm aware of) At least current "ETA" is at 1335m (8,42KB/s for a 660MB file (If i would to the same copy with "intact" file, that it takes <30 seconds). I still don't know if the file could be rescured. (98% done) > why does nobody find bugs in the RAW writing mode? Nobody knows you software as good as you. :-) Does the Teac CD-R58S support RAW writing? > But you are right, cdrecord better should do exit(2) in this case. :-))) I'm happy now. I don't know if it's the first time you say my opinion was right, but at least you share my opinion this time, so my burn script won't delete an image "in error" another time. :-))) 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: cdrecord "weakness"
> >cdrecord has a problem with SCSI-(RAID)-Controllers that don't allocate a > >ne scsibus for each Channels. > > > This is a problem with the Linux SCSI driver structure. > > > >Yesterday i got a 5 Channel FAST-SCSI RAID-Controller (ICP-Vortex) > > >I have 4 CD-Rs and every one has a dedicated channel on the new > >Controller. First i had configured every CD-R to ID-0. But then cdrecord > >could only see the first one. Now i configured every drive with diffrent > >IDs (cdrecord -scanbus attached). But that's not "the(tm)" solution. > > >AFAIK other OSses use "Adapter,Channel,ID,Lun" Adresses too. Why does > >cdrecord "only" use "scsibus,ID,Lun" (Hmmm. Do ANY cases exist where the > >LUNs are needed? (i only know 1 case, SCSI2SCSI-Bridges which map the ID > >from the "slave"-Channels to LUNs of the ID on the Main-Channel. But i > >think those bridges are "unusual") > > > Cdrecord uses what the standard addressing scheme with SCSI is. > > A SCSI Bus is an entity where the SCSI ANSI T10 adressing scheme is valid. > > T10 defines Target & Lun, the bus is the only layer above. > > If you read the Linux SCSI sources it is easy to find that Linux is wrong. > Linux calls a SCSI adapterCARD a Bus which has nothing to do with a SCSI bus. OK. "Fixed" with the newer driver-Version (cdrecord -scanbus looks "cool" with scsibus0 up to scsibus8) 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: How can I compile cdrecord for a i686?
> I have a computer with an amdk6-3d processor in it. since uname > doesn't detect the processor correctly, and compiles cdrecord for a > 586, which I don't have, I would like instructions on how to compile > cdrecord for my processor, or where to get binary versions compiled > for a amdk6 or a 686 or pentium. I think there is a kernel bug that > causes uname to return the wrong processor, because when it boots, it > gives me the correct processor. That 100% useless Burning 4 CDs in parallel(+X +mpg123 + ...) gives me a "phaenomeal" load of 0.07-0.14 (0.04-0.06 without the 4 cdrecords!) Each cdrecord has between <1% and 4% in Top Even mpg123 needs (much) more CPU-Power to play MP3! And cdrecord can get burn "faster" by optimized compiling! 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]
Teac CD-R58S doesn't work
Hi What does this error mean? -- schnipp -- Disk type:Long strategy type (Cyanine, AZO or similar) Manuf. index: 11 Manufacturer: Mitsubishi Chemical Corporation Blocks total: 359849 Blocks current: 359849 Blocks remaining: 232583 Starting to write CD/DVD at speed 8 in write mode for single session. Last chance to quit, starting real write in 0 seconds. Operation starts. Waiting for reader process to fill input buffer ... input buffer ready. Performing OPC... Starting new track at sector: -150 Track 01: 0 of 248 MB written.cdrecord: Input/output error. write_g1: scsi sendcmd: no error CDB: 2A 00 FF FF FF 6A 00 00 1F 00 status: 0x2 (CHECK CONDITION) Sense Bytes: 70 00 05 00 00 00 00 0A 00 00 00 16 21 00 00 00 Sense Key: 0x5 Illegal Request, Segment 0 Sense Code: 0x21 Qual 0x00 (logical block address out of range) Fru 0x0 Sense flags: Blk 0 (not valid) cmd finished after 0.249s timeout 40s write track data: error after 0 bytes Sense Bytes: 70 00 00 00 00 00 00 0A 00 00 00 00 00 00 00 00 00 00 Writing time: 21.905s Fixating... cdrecord: Input/output error. close track/session: scsi sendcmd: no error CDB: 5B 00 02 00 00 00 00 00 00 00 status: 0x2 (CHECK CONDITION) Sense Bytes: 70 00 05 00 00 00 00 0A 00 00 00 00 72 04 00 00 Sense Key: 0x5 Illegal Request, Segment 0 Sense Code: 0x72 Qual 0x04 (empty or partially written reserved track) Fru 0x0 Sense flags: Blk 0 (not valid) cmd finished after 0.008s timeout 480s cmd finished after 0.008s timeout 480s Fixating time:0.043s cdrecord: fifo had 479 puts and 1 gets. cdrecord: fifo was 0 times empty and 0 times full, min fill was 100%. -- schnapp -- 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]
Teac CD-R58S doesn't work Take II
Hi I have 4 of this CD-Writers and one produces this output. (The other 3 work flawlessly.) -- Output of "cdrecord speed=8 dev=6,0,0 -eject fs=30m -v " -- Cdrecord 1.10 (i686-pc-linux-gnu) Copyright (C) 1995-2001 Jörg Schilling TOC Type: 1 = CD-ROM scsidev: '6,0,0' scsibus: 6 target: 0 lun: 0 Linux sg driver version: 3.1.19 Using libscg version 'schily-0.5' atapi: 0 Device type: Removable CD-ROM Version: 2 Response Format: 2 Capabilities : RELADR SYNC LINKED Vendor_info: 'TEAC' Identifikation : 'CD-R58S ' Revision : '1.0H' Device seems to be: Generic mmc CD-R. Using generic SCSI-3/mmc CD-R driver (mmc_cdr). Driver flags : SWABAUDIO Drive buf size : 2732032 = 2668 KB FIFO size : 31457280 = 30720 KB Track 01: data 660 MB Total size: 758 MB (75:06.26) = 337970 sectors Lout start: 758 MB (75:08/20) = 337970 sectors Current Secsize: 2048 ATIP info from disk: Indicated writing power: 4 Is not unrestricted Is not erasable Disk sub type: Medium Type A, high Beta category (A+) (3) ATIP start of lead in: -11079 (97:34/21) ATIP start of lead out: 359849 (79:59/74) Disk type:Long strategy type (Cyanine, AZO or similar) Manuf. index: 11 Manufacturer: Mitsubishi Chemical Corporation Blocks total: 359849 Blocks current: 359849 Blocks remaining: 21879 Starting to write CD/DVD at speed 8 in write mode for single session. Last chance to quit, starting real write in 0 seconds. Operation starts. Waiting for reader process to fill input buffer ... input buffer ready. Performing OPC... Starting new track at sector: -150 Track 01: 0 of 660 MB written.cdrecord: Input/output error. write_g1: scsi sendcmd: no error CDB: 2A 00 FF FF FF 6A 00 00 1F 00 status: 0x2 (CHECK CONDITION) Sense Bytes: 70 00 05 00 00 00 00 0A 00 00 00 16 21 00 00 00 Sense Key: 0x5 Illegal Request, Segment 0 Sense Code: 0x21 Qual 0x00 (logical block address out of range) Fru 0x0 Sense flags: Blk 0 (not valid) cmd finished after 0.248s timeout 40s write track data: error after 0 bytes Sense Bytes: 70 00 00 00 00 00 00 0A 00 00 00 00 00 00 00 00 00 00 Writing time: 22.115s Fixating... cdrecord: Input/output error. close track/session: scsi sendcmd: no error CDB: 5B 00 02 00 00 00 00 00 00 00 status: 0x2 (CHECK CONDITION) Sense Bytes: 70 00 05 00 00 00 00 0A 00 00 00 00 72 04 00 00 Sense Key: 0x5 Illegal Request, Segment 0 Sense Code: 0x72 Qual 0x04 (empty or partially written reserved track) Fru 0x0 Sense flags: Blk 0 (not valid) cmd finished after 0.008s timeout 480s cmd finished after 0.008s timeout 480s Fixating time:0.038s cdrecord: fifo had 479 puts and 1 gets. cdrecord: fifo was 0 times empty and 0 times full, min fill was 100%. -- End -- I had a power outage a few days ago and since then the cdwriter "doesn't work" anymore. I think it's "Game over" for it. Am i right? System: Linux-Kernel 2.4.9 Dual PIII 933Mhz 3GB RAM ... With exactly this configuration this specific cdwriter (And the other 3) worked before the power outage. 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: yamaha 16x
On Sat, Sep 08, 2001 at 05:20:29PM +0200, feri wrote: > does anyone of u know if the yamaha 16x (ide) works with cdrecord ??? No problems. Even over Firewire 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: Pioneer S201 vs A03
> >> In addition, with ATAPI I don't know of anyway to get > >> the drive external from the actual PC. As I stated > >> earlier I have valid concerns about temperature and > >> vibration from the PC. > >> > >> Are those of you using the Pioneer A03 with IDE at > >> least happy with it? Does it seem like a solid drive? > > >Firewire is the best invention since chopped bread. > > >I have a Pioneer DVR-A03 build into a external 5,1/4" Firewire Case. > >Works flawlessly even with Linux. > > I just tested a SCSI adapter with the A03 but it unfortunately > does not disconnect/reconnect. > In general the quality of the adapters is bad. Maybe this > is the reason why Yamaha has special firmware in the adapter they > sell to limit use wo Yahama drives. Thats the reason why i prefer dedicated SCSI-Channels. e.g. I used a dedicated (5 Channel)-Fast-SCSI-RAID-Controller when i used 4 Teac-CDR-58S for burning CDRs. (In total Linux showed 10 SCSI-Channels) Then even Solaris should't have any problems with disconnect/reconnect incapable devices. > Solaris currently only supports video cameras over FireWire. You should urge the Solaris-Firewire-People to implement SBP-2. Then the whole range of Mass-Storage devices is suddenly usable, as all devices (i know) use SBP-2 (Serial BackPack Protocol 2 = SCSI over Firewire) 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: cdrecord via firewire
> i have a dvd recorder that uses a firewire (ieee 1394) port to communicate
> and was wondering if it is possible to get cdrecord to burn dvds via
> the firewire port. i know that to use ide there has to be a scsi
> emulation layer, and was wondering if the same thing is needed for
> firewire to work, if so can you offer any info or pointers about finding
> more about such emulators for this option. thank you. also please respond
> directly since i am not currently on the list.
if (DVR-D == "Pioneer DVR-A03" && system == "(more ore less current) linux (Kernel
2.4)") {
It works, if you know how.
Mine works (more or less) flawlessly.
Last coaster is more than 40 DVD-Rs away (Knocking on wood)
}
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: DVD-R scsi?
On Mon, Jan 14, 2002 at 11:51:26AM -0800, Dan Hollis wrote: > On Mon, 14 Jan 2002, Joerg Schilling wrote: > > >From [EMAIL PROTECTED] Mon Jan 14 13:03:37 2002 > > >On Mon, 14 Jan 2002, Joerg Schilling wrote: > > >> -Buy a Poineer A03 and add a ATAPI/SCSI Adaptor. > > >> Unfortunately most of these adaptors have severe bugs. > > >How about ATAPI->1394? > > It may work on Linux (there are known users) but it does not > > work on Solaris. > > I meant, do the 1394 bridges have severe bugs also? At least the one i use works perfectly. 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: DVD-R scsi?
On Mon, Jan 14, 2002 at 02:25:37PM -0800, Dan Hollis wrote: > On Mon, 14 Jan 2002, Matthias Schniedermeyer wrote: > > On Mon, Jan 14, 2002 at 11:51:26AM -0800, Dan Hollis wrote: > > > I meant, do the 1394 bridges have severe bugs also? > > At least the one i use works perfectly. > > And the make/model the one you use is ... ? "NoName" 5,25" Enclosure, maybe from MaPower. The Pioneer DVR-A03 is built into this one. And for HDDs i have a 2,5" and a 3,5" Enclosure each with an "Oxford 911" Chipset (Because of the performance, AFAIK this Chipset is still the fastest available IDE <-> Firewire "converter"-chipset. It can reach up to 33MB/s.). The 3,5" is called "IceCube" and IIRC the 2,5" is called "ClearView" (Both are from Mac-Shops in Mac-like designs" (Thats positive!)) 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: Greetings..
> the current mkisofs & cdrecord-ProDVD should give you all you need for > Video DVDs. What is your problem? If i take a non-CSSed DVD (*1) What do i have to burn a DVD(-R)-Video mkisofs -udf -o image1.raw and then just burn this image to a DVD-R? If thats what it needs to burn a DVD-Video. Then it sounds much to easy. :-) *1: AFAIK there is no tool available to create the data-files for a DVD-Video (*.ifo, *.vob ..) So i can just use the contents of another DVD-Video to get the necessary data-files. 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]
mkisofs should die with too big files
#include Yesterday i lost a 2,3 GB big file because mkisofs "silently" skipped it. mkisofs ... $dir && rm -rf $dir I had the luck that i can reget that file. But next time it's possibel that i'm not so lucky. So it would be best to "die" instead of a "silent" warning that a file was skipped. (At least as a commandline-option. Something like the "Make warnings to errors" from compilers (this can be especially usefull for scripts where the warnings aren't seen (Today i saw the warning because i was watching the process today)). Or a special option "die when files are too big") 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: mkisofs should die with too big files
On Mon, May 13, 2002 at 10:03:53PM +0200, Joerg Schilling wrote: > > >From: Matthias Schniedermeyer <[EMAIL PROTECTED]> > > > > >Yesterday i lost a 2,3 GB big file because mkisofs "silently" skipped it. > > >mkisofs ... $dir && rm -rf $dir > > >I had the luck that i can reget that file. But next time it's possibel > >that i'm not so lucky. So it would be best to "die" instead of a "silent" > >warning that a file was skipped. (At least as a commandline-option. > >Something like the "Make warnings to errors" from compilers (this can be > >especially usefull for scripts where the warnings aren't seen (Today i saw > >the warning because i was watching the process today)). Or a special > >option "die when files are too big") > > > mkisofs definitey does not skip those files silently! > > It prints: "File %s is too large - ignoring\n" > > It is not possible to put files > 2 GB into a ISO-9660 fs. Like i said. In a script that IS silent. start script, "(go/look) away", script done, source-dir deleted, image too small -> file lost. (Warning scrolled away. Yes i prefere the console) 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: mkisofs should die with too big files
On Mon, May 13, 2002 at 01:13:58PM -0700, Dan Hollis wrote: > On Mon, 13 May 2002, Joerg Schilling wrote: > > It prints: "File %s is too large - ignoring\n" > > It is not possible to put files > 2 GB into a ISO-9660 fs. > > What about UDF? Just curring symptoms. If UDF than NO ISO at all. But mkisofs can't switch of ISO. So i don't use UDF. 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: mkisofs should die with too big files
On Mon, May 13, 2002 at 10:36:01PM +0200, Joerg Schilling wrote: > >From [EMAIL PROTECTED] Mon May 13 22:18:40 2002 > > >On Mon, May 13, 2002 at 01:13:58PM -0700, Dan Hollis wrote: > >> On Mon, 13 May 2002, Joerg Schilling wrote: > >> > It prints: "File %s is too large - ignoring\n" > >> > It is not possible to put files > 2 GB into a ISO-9660 fs. > >> > >> What about UDF? > > >Just curring symptoms. If UDF than NO ISO at all. But mkisofs can't > >switch of ISO. So i don't use UDF. > > All UDF media should include ISO-9660. mkisofs is correct. "Should" is the jumping dot. All files names SHOULD not contain this or that characters. All file names should be 8.3 (or 20/32 Chars?). My filenames are too long. My filenames aren't Windows compatible. (Windows refuses to read the files. I had to use "isobuster" to copy a file off one of my DVD-Rs once) So why should i be so "compatible" to put an ISO onto the Disc? Some days ago i even thought about using romsfs, cramfs, FAT or something else. Linux can read everything. -> No problem for Linux means no problem for me. I even burned tar-files directly to CD-r in the past. All or nothing. UDF means that the ISO can have lesser files than the UDF part -> no ISO at all. A missing file isn't acceptable. 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: mkisofs should die with too big files
On Mon, May 13, 2002 at 10:36:01PM +0200, Joerg Schilling wrote: > >From [EMAIL PROTECTED] Mon May 13 22:18:40 2002 > > >On Mon, May 13, 2002 at 01:13:58PM -0700, Dan Hollis wrote: > >> On Mon, 13 May 2002, Joerg Schilling wrote: > >> > It prints: "File %s is too large - ignoring\n" > >> > It is not possible to put files > 2 GB into a ISO-9660 fs. > >> > >> What about UDF? > > >Just curring symptoms. If UDF than NO ISO at all. But mkisofs can't > >switch of ISO. So i don't use UDF. > > All UDF media should include ISO-9660. mkisofs is correct. You should make mkisofs more correct. It should refuse to make incompatible disc by default. Currently it says nothing when filenames aren't compatible and/or filenames are to long. (Or "-r" and/or "-J" switches that behaviour off. That are the only options i use) I grep for the "print" myself and put the "exit 1" behind it myself. But i would prefer to not do that with every release in the future. I'm OK with a commandline-option i can put into my image-creation script. (And i think my other would prefer such on option, or mkisofs to die when i skips files. I think most people didn't notice that behaviour because not so many use DVD-R currently. Like the "You have 10 seconds left" in cdrecord that did "exit 0" in the past, when you pressed "Control-C". Nobody noticed that, but my script just wippes the image when cdrecord does an "exit 0", so i lost an image (I had the luck that "Midnight Commander" could restore that file. But that took 24 hours) Same with my image-creation script. It BELIEVES mkisofs. When mkisofs says "everything OK", then everything is OK and the source-files can be wipped. This behaviour destroys that "trust" situation.) 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: mkisofs should die with too big files
> Yesterday i lost a 2,3 GB big file because mkisofs "silently" skipped it. > > mkisofs ... $dir && rm -rf $dir > > I had the luck that i can reget that file. But next time it's possibel > that i'm not so lucky. So it would be best to "die" instead of a "silent" > warning that a file was skipped. (At least as a commandline-option. > Something like the "Make warnings to errors" from compilers (this can be > especially usefull for scripts where the warnings aren't seen (Today i saw > the warning because i was watching the process today)). Or a special > option "die when files are too big") Now everything is right for my script. a "#include " at the top and a "_exit(1);" after the "errormessage" and everything works flawlessly now and the script doesn't wipe a directory from which a BROKEN image was created from. 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: mkisofs should die with too big files
> >If you make mkisofs completely "correct", it becomes rather useless.
>
> >The default behavior of mkisofs happens to also be the default behavior of
> >tar; that is, tar continues merrily on its way after an error (at least GNU
> >tar does).
>
> >There are good reasons to allow a process that takes a long time to complete,
> >such as mkisofs, to continue after an error is encountered rather than just
> >quit.
>
> Every tar that works as expected does this way.
>
> >From the 1979 tar.c:
>
> infile = open(shortname, 0);
> if (infile < 0) {
> fprintf(stderr, "tar: %s: cannot open file\n", longname);
> return;
> }
>
>
> Not even a notification to the caller is done. The message is all.
>
> 'Modern' tar implementations like star (1982-2002 ;-) print a problem
> sumary at the end
>
>
> All other people who create DVDs know that files > 2 GB are a problem and avoid
> them. Even the DVD video standard wants the video to be split into several ~ 1 GB
> files.
Then hardwire "exit 0" into mkisofs & cdrecord. No need to tell any
script (or other programs) that there has been an error. It's totaly
pointless to tell there there was an error. Everything in one go or
nothing at all, there is good chance that everything worked fine. I've
recorded around 200 DVD-Rs without problems. So the error percentage is
less then 1 percent. Why care for problems less then 1 percent.
No other program comes currently to my mind where i need output-parsing
to get the notice of a FATAL error. (You know that the "file too big"
means that at least half of the content (seen from the size point) is
missing from the image? And in my eyes thats a FATAL error. Maybe i
should do it the other way around and place a filesize checker into my
image-creation script, but why should i do that hassle when mkisofs
could just throw an error?)
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: mkisofs should die with too big files
Hi You are "strict" or you are not strict. If you are not strict that it is pointless to talk about being strict. Someone else would say that Joerg is just "inconsequent". "Silently" IGNORING a file can't be the behaviour of a program that is used in an automatic process. (And placing checks before or after image-creation can't be the job of my script. "mkisofs" is specialized in doing the job, so it should do it correct or die with an error(level)) On Mon, May 13, 2002 at 03:00:27PM -0700, Seth Kurtzberg wrote: > If you make mkisofs completely "correct", it becomes rather useless. > > The default behavior of mkisofs happens to also be the default behavior of > tar; that is, tar continues merrily on its way after an error (at least GNU > tar does). > > There are good reasons to allow a process that takes a long time to complete, > such as mkisofs, to continue after an error is encountered rather than just > quit. > > A command line argument to say "quit on error" would be fine, but my vote is > to keep the default behavior the way it is. > > On Monday 13 May 2002 02:24 pm, Matthias Schniedermeyer wrote: > > On Mon, May 13, 2002 at 10:36:01PM +0200, Joerg Schilling wrote: > > > >From [EMAIL PROTECTED] Mon May 13 22:18:40 2002 > > > > > > > >On Mon, May 13, 2002 at 01:13:58PM -0700, Dan Hollis wrote: > > > >> On Mon, 13 May 2002, Joerg Schilling wrote: > > > >> > It prints: "File %s is too large - ignoring\n" > > > >> > It is not possible to put files > 2 GB into a ISO-9660 fs. > > > >> > > > >> What about UDF? > > > > > > > >Just curring symptoms. If UDF than NO ISO at all. But mkisofs can't > > > >switch of ISO. So i don't use UDF. > > > > > > All UDF media should include ISO-9660. mkisofs is correct. > > > > You should make mkisofs more correct. It should refuse to make > > incompatible disc by default. Currently it says nothing when filenames > > aren't compatible and/or filenames are to long. (Or "-r" and/or "-J" > > switches that behaviour off. That are the only options i use) > > > > I grep for the "print" myself and put the "exit 1" behind it myself. But > > i would prefer to not do that with every release in the future. I'm OK > > with a commandline-option i can put into my image-creation script. (And > > i think my other would prefer such on option, or mkisofs to die when i > > skips files. I think most people didn't notice that behaviour because > > not so many use DVD-R currently. Like the "You have 10 seconds left" in > > cdrecord that did "exit 0" in the past, when you pressed "Control-C". > > Nobody noticed that, but my script just wippes the image when cdrecord > > does an "exit 0", so i lost an image (I had the luck that "Midnight > > Commander" could restore that file. But that took 24 hours) Same with my > > image-creation script. It BELIEVES mkisofs. When mkisofs says > > "everything OK", then everything is OK and the source-files can be > > wipped. This behaviour destroys that "trust" situation.) > > > > > > > > > > > > > > Bis denn > > -- > Seth Kurtzberg > MIS Corp. > Office: (480) 661-1849 > Fax: (480) 614-8909 > email: [EMAIL PROTECTED] > pager: 888-605-9296 or email [EMAIL PROTECTED] -- 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: License of cdrdao will be changed
On Mon, Sep 23, 2002 at 01:02:13PM +0200, Lourens Veen wrote: > On Monday 23 September 2002 12:03, Joerg Schilling wrote: > > Preface: I am sorry, but it seems that you don't know much about > > Copyright issues :-( Many of your statements are completely > > wrong and none of your mails from the last night has been > > helpful. > > > > For a decent discussion on this topic it is important that we use > > correct verbalizations. Unfortunately, the English language is > > not very precise here > > [...explanation of _German_ copyright system...] > > I believe we need to make a clear distinction between the German > copyright laws and the American copyright laws. Unfortunately, > there seem to be some major differences here, and given what you > wrote I'm not even sure if the GPL makes sense at all in the > context of German (and probably other European) copyright law. First: IANAL, AFAIK & AFAIR! The "biggest" difference is that in the US you can "give up" (e.g. sell) your authorship-rights (to use Joergs nomenclature) while in germany this is impossibel. Regarding GPL/PD/BSD/... this means that you (if you are german) "tolerate" violations of your rights. (You have the rights, but you don't use/enforce them.) e.g. It would be easy for a german to forbid another german to use his GPD/PD/BSD/... software. In the US this not be possibel, because you give up this/that right(s). In germany you can't give up that right, you just don't use it. AFAIR there has only been one case where a german has "missused" his german right(s) forbid another german to use his software. Unfortunatly i can't remember any details. 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: Write e2fs to CD
On Tue, Oct 08, 2002 at 09:49:53AM -0500, [EMAIL PROTECTED] wrote: > Folks, > > Is it possible to write a e2fs directory structure to CD? > Say I want to backup /www on my linux e2fs system. > Then later on, just mount the cd as you would any other e2fs partition. > I use cdrecord, slack linux 8, 2.2 kernel I believe. > > I've looked thru the FAQs. > > Any help appreciated. You can burn any filesystem that Linux can read onto a CD. Or no filesystem at all. e.g. you can burn a .tar(.gz) file directly onto a CD. 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: Write e2fs to CD
On Tue, Oct 08, 2002 at 10:37:32AM -0500, Korey O'Dell wrote: > Matthias Schniedermeyer wrote: > > > > On Tue, Oct 08, 2002 at 09:49:53AM -0500, [EMAIL PROTECTED] wrote: > > > Folks, > > > > > > Is it possible to write a e2fs directory structure to CD? > > > Say I want to backup /www on my linux e2fs system. > > > Then later on, just mount the cd as you would any other e2fs partition. > > > I use cdrecord, slack linux 8, 2.2 kernel I believe. > > > > > > I've looked thru the FAQs. > > > > > > Any help appreciated. > > > > > How? Specifically, if I wanted to burn my /www subdirectory and all > files and subdirs contained within to CD. I know I can mkisofs out of > it, but I dont want that. I just want a copy of my e2fs /www on CD. Want you want seems to be "packet-writing". With packet-writing you use the CD-R(W) in a HDD like way(*). AFAIK there is something like this for Linux, but can't say anything more. *: Strongly simplified. 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: Write e2fs to CD
On Wed, Oct 09, 2002 at 06:59:11AM +0200, Guido Hamacher wrote: > Am Dienstag 08 Oktober 2002 17:14 schrieb Matthias Schniedermeyer: > > On Tue, Oct 08, 2002 at 09:49:53AM -0500, [EMAIL PROTECTED] wrote: > > > Folks, > > > > > > Is it possible to write a e2fs directory structure to CD? > > > Say I want to backup /www on my linux e2fs system. > > > Then later on, just mount the cd as you would any other e2fs partition. > > > I use cdrecord, slack linux 8, 2.2 kernel I believe. > > > > > > I've looked thru the FAQs. > > > > > > Any help appreciated. > > > > You can burn any filesystem that Linux can read onto a CD. Or no > > filesystem at all. > > e.g. you can burn a .tar(.gz) file directly onto a CD. > > Fine idea -- but how do I read a tar-file from CD? SCSI: tar /dev/hdX In my case tar -zxvf /dev/sr2 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: CDRecord-ProDVD
On Fri, Oct 25, 2002 at 02:48:58PM +0200, Joerg Schilling wrote: > >From: Karl Bellve <[EMAIL PROTECTED]> > > >I am having trouble piping from mkisofs to cdrecord-ProDVD > > >I can write an iso with mkisofs, then use cdrecord-ProDVD without > >problems. > > >Inside a script, I have the following: > > >mkisofs -J -r -T "$@" | burndvd fs=16m -v speed=2 dev=0,0,0 - > > The man page and the README on ftp://ftp.fokus.gmd.de/pub/unix/cdrecord/ProDVD/ > describe why this cannot work. It would help if you read these documents. Maybe i'm stupid or blind (or both). Bt the README (in the dir) doesn't say a word about that and there is no man-page. Btw. You should update the Paragrah about the Free-License. (Last sentence.) - snip - As I am not sure if people will follow my licensing rules, so these keys are time limited and will expire on 2003 Jan 15 14:06:29. I will continue to make private/educational/research use free, but it may be that you need to request your private key for free after June 17th. - snip - 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: DVD+RW/+R for Linux update
On Mon, Nov 04, 2002 at 11:49:47AM -0700, Frank Hage wrote: > On 2002.11.04, Joerg Schilling wrote: > : > : > : But DVD-* media is cheaper and I see no advantage in using DVD+ media. > > Other advantages are the ability to completely fill the disks (> 4 GB > iso files are a problem on 32 bit systems) and not needing free space > for the disk images. "When you don't know what you are talking about. Shut up". :-) You can't make a single file bigger than 2 GB in an ISO-Filesystem, corect. But that is a limitation in of the ISO-Filesystem itself. With any other filesystem (or not filesystem at all), that is capable of having bigger files, you don't have that problems. When you have a problem creating the 4.5GB Image-File then your system isn't up to date. Update the system or use the split-option of mkisofs. I burn DVD-Rs for more than a year now and from day one on i had never problems with file-sizes (*1) (*2) *1: Except that i had to patch the ISO-driver in Linux (kernel 2.4.9) to recognize files bigger than 1 GB. But that patch made into "normal" Linux a few revisions later. *2: I don't count the 2GB Limitation of ISO-fs as a problem. As it is conceptual there is nothing you can do about it. 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: DVD+RW/+R for Linux update
On Wed, Nov 06, 2002 at 02:26:21PM +0100, Joerg Schilling wrote: > > >From: Matthias Schniedermeyer <[EMAIL PROTECTED]> > > >> : But DVD-* media is cheaper and I see no advantage in using DVD+ media. > >> > >> Other advantages are the ability to completely fill the disks (> 4 GB > >> iso files are a problem on 32 bit systems) and not needing free space > >> for the disk images. > > >"When you don't know what you are talking about. Shut up". :-) > > See above ;-).. I won't say what one of my teachers in school said about this topic. > >You can't make a single file bigger than 2 GB in an ISO-Filesystem, > >corect. But that is a limitation in of the ISO-Filesystem itself. > > The OP did not talk about single files _inside_ an ISO FS but about ISO-FILES > which usually is a file holding an ISO FS as content. As i said below. That problem doesn't exist (anymore). :-) The 2GB problem is the only size-problem i know. So i included the rant about that limitation to make a (more or less) technically correct statement. Point. > Future versions of mkisofs will allow you to use > 2 GB files in UDF > filesystems. You should rename the program. It doesn't "feel" correct anymore. OK currently you can't skip the ISO-FS. But AFAIR you once said that you will make it possibel to skip the ISO-FS from the image. mkufs mkimg mkhybrid :-) mk_image_suitable_for_burning_on_a_CD-R(W)_or_DVD(-/+)R(W)_(or_other_medium) 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: DVD+RW/+R for Linux update
On Wed, Nov 06, 2002 at 01:22:17PM -0700, Frank Hage wrote: > On 2002.11.06, Joerg Schilling wrote: > : > : > : >From: Matthias Schniedermeyer <[EMAIL PROTECTED]> > : > : >> : But DVD-* media is cheaper and I see no advantage in using DVD+ media. > : >> > : >> Other advantages are the ability to completely fill the disks (> 4 GB > : >> iso files are a problem on 32 bit systems) and not needing free space > : >> for the disk images. > : > : >"When you don't know what you are talking about. Shut up". :-) > : > : See above ;-).. > : > : >I burn DVD-Rs for more than a year now and from day one on i had never > : >problems with file-sizes (*1) (*2) > : > > I'm sorry. I forgot that DVD +/- geeks were having a religious war. ;-) You say it. There is only one god. :-) > Yes, you .de guys are right. Your Mileage Varies greatly from mine. A few month ago i even read an articel in our "Linux Magazin" about the "2GB Barrier" (The Topic was DVD-Recording). I felt like beeing warped back into the stoneage. :-) > However, perhaps you should look at it from my point of view. Often > "Confused and Ignorant", I go on trying to do my real job using computers > my institution provides and supports. Stability is a big issue in my work, > so we often run SEVERAL YEARS behind current releases on our computers. We > do this on purpose, because they need to collect and process data 24/7, > often for years at a time. I have limited options and little patience > for chasing development/alpha software. Yes, DVD- works great for you > after you patched, updated, split, etc... and then, what... diddled > Joerg for a cdrecord key? Perhaps I don't have that option. For burning i only had to recompile mkisofs because the version from my distribution wasn't compiled right, it couldn't create an image >2GB. But besides that i didn't had to change anything else in my system. So i've never splitted my images, since the 2GB Barrier was gone since 2.4pre and i used 2.4.4 or 2.4.9 the time i burned my first DVD-R. For reading files bigger 1GB the kernel had to be patched because otherwise the file would be shown as 16MB or something like that. No keys back then. The binary was the key, i got my "own" cdrecord. The keys came later. And another "thing" i never had problems with and where other people have a variing milage is firewire. Since day one i use the DVD-R connected via a IDE <-> Firewire enclosure. It took about 10 "try"s until i finally had my first DVD-R-coaster. :-) 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: DVD+RW/+R for Linux update
On Fri, Nov 08, 2002 at 03:53:16PM +0100, Andy Polyakov wrote: > > As already mentioned. DVD+RW supports write of randomly addressed 2KB > blocks even to *virgin* media (well, when you write 2KB, 32KB gets > naturally written/de-iced], and naturally rewrite in random order at > later occasion. Randomly written DVD+RW disc is *indistinguishable* from > one written progressively/streamed. DVD+R media can be written > progressively in 32KB ECC blocks, *but* uninterrupted streaming is not a > requirement [you can even eject media between writes]. DVD+R media > written progressively with interrupts is *indistinguishable* from one > written streamed/in one single take. All this thanks to "high [spatial] > frequency wobbled [pre-]groove with addressing information modulated > into it." Even if DVD+RW is "superior" to DVD-R. What does it REALLY buy you? Is there any REAL practical use for writing to the 4GB position on a virgin media? And personally i would NEVER use a rewritable medium that isn't build into a caddy. (Neither - or + fit this requirement. DVD-RAM would fit) As i "joke" i bought 2 DVD-RW media and used them to transport some data to a college of me, after 3 rounds the media weren't usable anymore, because of to many scratches. So the R(e)W(rite) is more theoretical then practical in my eyes. (OK there are "DVD+R" now) If i need TRUE "random" access, DVD-RAM is much better for the job. OK disadvantage is that nearly nobody has this (if you want to use such a media to transport data.) and even if DVD-RAMs were readable by a normal DVD drive the media wouldn't fit because i haven't see a DVD drive with a caddy latly. For transporting data to/from the place i work i use a 20GB 2,5" HDD build into a firewire-enclosure. With around 15MB/s this outperforms everything else on the portable market. (Excluding 3,5 HDD built into a firewire enclosure) 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: DVD+RW/+R for Linux update
On Sun, Nov 10, 2002 at 04:49:55PM +0100, Andy Polyakov wrote: > > > >The page in question was updated with following two paragraphs: > > Updated write-up is online and reads now as following: < Snip > Again. Even if DVD+RW is "superior". What does it REALLY buy you? Excluding the 0.01% of the person that can actually use some or all of the benefits. There are 99.99% of the people that don't care and/or don't need such benefits. To take myself. I burn for about 6 years now. I have NEVER used CD-RW (Actually the DVD-Burner is my first burner that supports CD-RW and i would NEVER use my DVD burner to burn CD-R(W)) and i have NEVER used multisession or things like that (This includes packetwriting which is only other way to gain the (same/similar) effect that you can get with multisession). And i don't know any person in my surrounding that uses/needs such a feature. To say it simple: The price-tag and/or the availability will settle the DVD(+/-)R(W) "war". (Or all manufractory will make drives like the announced drive from sony, that supports both formats. Then the price-tag of the media will settle the "war") 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: Condition to burn DVD in speed 2?
On Tue, Jan 07, 2003 at 09:10:09PM +0100, Gregoire Favre wrote: > Hello, > > since some time, I burn dvd using the great cdrecord-prodvd ;-) > > What shall I do to burn at speed two or four? a) Buy the correct DVD-Rs b) Buy the correct DVD-Rs c) Buy the correct DVD-Rs e.g. Verbatim is good. I've use them for nearly 1.5 years now and i had never problems with them. (I've never burned a DVD-R with 1x in my whole life (DVD-RW don't count!)) For 2x burning the firmware of the burner must know the write-strategy for the medium. -> Not all mediums are known to the Burner-Firmware -> Fallback to 1x. (*) For 4x you have to wait until they get available. AFAIK currently you can't buy 4x DVD-Rs. *: At least the article in c't says this. Current issue or one/two issues before. 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: Condition to burn DVD in speed 2?
On Tue, Jan 07, 2003 at 10:54:16PM +0100, Gregoire Favre wrote: > On Tue, Jan 07, 2003 at 10:46:43PM +0100, Matthias Schniedermeyer wrote: > > > a) Buy the correct DVD-Rs > > b) Buy the correct DVD-Rs > > c) Buy the correct DVD-Rs > > > > e.g. Verbatim is good. I've use them for nearly 1.5 years now and i had > > never problems with them. (I've never burned a DVD-R with 1x in my whole > > life (DVD-RW don't count!)) > > > > For 2x burning the firmware of the burner must know the write-strategy > > for the medium. -> Not all mediums are known to the Burner-Firmware -> > > Fallback to 1x. (*) > > > > For 4x you have to wait until they get available. AFAIK currently you > > can't buy 4x DVD-Rs. > > > > > > *: At least the article in c't says this. Current issue or one/two > > issues before. > > Well, > > great, I thought I should change the license of cdrecord-prodvd... > > Good new then (I have just updated my firmware to allow higher write > speed, but still no sucess) ;-) Ups. I forgot that totaly. As i've always had a license i forgot that you can't burn fast with the free license. When i read 'Burn faster' my first thought was that you have "cheap" medias that the firmware doesn't recognize. But you need both. Good media and a "better" license. 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: Condition to burn DVD in speed 2?
On Tue, Jan 07, 2003 at 11:03:12PM +0100, Gregoire Favre wrote: > On Tue, Jan 07, 2003 at 11:00:21PM +0100, Matthias Schniedermeyer wrote: > > > Ups. I forgot that totaly. As i've always had a license i forgot that > > you can't burn fast with the free license. > > > > When i read 'Burn faster' my first thought was that you have "cheap" > > medias that the firmware doesn't recognize. But you need both. Good > > media and a "better" license. > > Well, I thought that ;-) > > I didn't found the condition on the ftp site for Prodvd... > What is the price for a student and for a private use? I paid 100 EUR and AFAIK the price hasn't changed. But i don't know if Joerg charges less for students. You have to ask Joerg directly for more information. I've always used one of the email-adresses in the readme of cdrecord to mail Joerg. 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: Condition to burn DVD in speed 2?
On Wed, Jan 08, 2003 at 03:55:32PM +0100, Joerg Schilling wrote: > > >From: Matthias Schniedermeyer <[EMAIL PROTECTED]> > > >> great, I thought I should change the license of cdrecord-prodvd... > >> > >> Good new then (I have just updated my firmware to allow higher write > >> speed, but still no sucess) ;-) > > >Ups. I forgot that totaly. As i've always had a license i forgot that > >you can't burn fast with the free license. > > >When i read 'Burn faster' my first thought was that you have "cheap" > >medias that the firmware doesn't recognize. But you need both. Good > >media and a "better" license. > > Wrong: cdrecord-ProDVD never had a speed limitation for DVD media. > Old versions ignore speed and always write as maximum speed, newer versions > show actual speed and allow to change it if possible. OK. I take this point. But IMHO you should make the speed-limit-paragrah in the README at bit more understandable. At least that the speed-limit only hits the clone-feature isn't written 100% clearly in my eyes. 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: Condition to burn DVD in speed 2?
On Thu, Jan 09, 2003 at 09:25:47PM +0100, Joerg Schilling wrote: > >From: Matthias Riese <[EMAIL PROTECTED]> > > >> >> I would never recommend unmaintained software that is known not to > >> >> work correctly for many drives - see the mailing lists for this "project". > >> > >> >Wrong. > > >> -> The "project" you mention is definitely unmaintained The only changes are > >>related to useless changes in the nonstandard make system used by > >>this project. > > >Wrong. > > >1. The changes are not useless. > >2. You contradict yourself wrt to the state of maintenance. > > Wrong: > > The only thing Mr. Rosenkranzer did was to replace a make system that is known > to work by a broken make system and later start trying to fix his broken make > system. This cannot be called maintenance of the project (as it was not needed > at all) but hobbyists work... You mean: A make system that is know to work for THIS case with a make system that is know to work for nearly all other OSS-projects. I only say Tannenbaum 'Linux is obsolete'. 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: cdrecord-proDVD ,linux and IEEE1394
On Wed, Mar 19, 2003 at 09:58:51AM -0700, Ashish Rangole wrote: > All, > > I would like to know if anybody has tried burning > CD/DVD in linux on a drive with IEEE1394(firewire) > interface and if it has been tried with cdrecord-proDVD. > > I am thinking of using cdrecord-proDVD on Mandrake 9.0 > and the burner is a Pioneer DVD A-04 with IDE to IEEE1394 > convertor in front. I wish to know how IEEE1394 works on > linux in general and with CD/DVD writers having IEEE1394 > interface. > > Any response will be greatly appreciated. Thanks in advance. I've always burned (DVDs) via Firewire. Thats since >1,5 years. No problems. 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: extension of mkisofs for incremental backups
On Tue, Mar 25, 2003 at 08:38:05AM +0100, Patrick Ohly wrote: > > > However, accessing older versions of a file is > > > difficult: the CD filesystems must be able to select > > > arbitrary session and thus the old file. At least on > > > the Amiga this works, but I have doubts about Linux > > > > It's possible with 'mount -o session=N ...' under Linux. > > Ah, good to know. But mount would complain when > trying to mount the same device twice, wouldn't it? > So comparison of files would still be difficult. No. "Current" (>2.4.0) kernels have no problems mounting the same device multiple times. 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: howto burn a (data)dvd
On Tue, Mar 25, 2003 at 04:26:37PM +0100, Joerg Schilling wrote: > > >From [EMAIL PROTECTED] Mon Mar 24 20:14:22 2003 > > >On Mon, 24 Mar 2003, Joerg Schilling wrote: > >> There will be less and less people who may use it in future - there > >> is no support/development and the number of non Pioneer drives is increasing. > > >If someone submitted patches for cdrecord to support dvd drives, would you > >accept them? > > Looks like you also confuse dvdrecord with cdrecord. Cdrecord does support DVD > writing for more than 5 years. There is no need to include patches because the > functionality is already in. You confuse yourself. cdrecord-proDVD has it. cdrecord doesn't. cdrecord-proDVD != cdrecord (Per dictionary definition of "equal", "identical" ...!!) Or am i only to blind to see the (source-)parts in the cdrtools.tar.gz file? 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: how many cds...
On Wed, Apr 02, 2003 at 10:14:45PM -0300, Guilherme Miranda Martins wrote: > > Hi people, > > Please, i want to know how many image cds do I need to install Debian > Woody for i386. I have already downloaded 3 image files throught jigdo. > Can I install or have to get all the files ?? It depends. ;-) When you have a "good(tm)" connection the the internet you only need a very basic installation and the rest can be done over the internet. So you only need the first disc. Otherwise it depends on what software you want to install. 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: dvd+rw-tools update
> Public does not seem to share your viewpoint and does not experience > cdrecord and cdrecord-ProDVD as the same program. Neither do I... Same here. :-) 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: Dvdrecord problem
On Thu, Jun 19, 2003 at 01:14:34PM +0200, Joerg Schilling wrote: > > >From [EMAIL PROTECTED] Wed Jun 18 16:03:00 2003 > > >> Well, cdrecord-ProDVD definitely is free for private and research/educational > >> use. > > >s/free/libre/ > > Do you really belive that the context changes if you only translate from > english to french? As a german you should know that english doesn't differentiate "free". "Free as in beer" vs "Free as in speech" are both "free" in english. So the translation is a valid point. Guess why it is called "Open Source Software" and not "Free Software"! The proDVD version is ONLY as "free" as free beer . 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: two questions concerning fast burning and burn-free
On Wed, Jul 16, 2003 at 12:54:03AM +0200, Norbert Preining wrote: > Hello friends! > > I have two questions concerning burning with/without burn-free: > > The first: How fast is it theoretically possible with an UDMA100 > harddisk to burn *without* burnfree protection? If I burn with my > plextor premium at full speed I would always get buffer underruns. With the upcoming Linux-2.6 Kernel you will be able to burn with full speed because the 2.6-Kernel can talk to the burner in DMA mode. Current 2.4 Kernel isn't capable of doing this. Personaly i have my burner plugged into a Firewire-Enclosure, a good one talks with DMA to the burner. I have a 4x DVD-Burner (equals roughly 28/29x CD-Speed) and had never problems with burning. I never use burnfree. 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: two questions concerning fast burning and burn-free
On Wed, Jul 16, 2003 at 09:11:02AM +0200, Markus Plail wrote: > On Wed, 16 Jul 2003, Matthias Schniedermeyer wrote: > > >On Wed, Jul 16, 2003 at 12:54:03AM +0200, Norbert Preining wrote: > >> I have two questions concerning burning with/without burn-free: > >> > >> The first: How fast is it theoretically possible with an UDMA100 > >> harddisk to burn *without* burnfree protection? If I burn with my > >> plextor premium at full speed I would always get buffer underruns. > > > > With the upcoming Linux-2.6 Kernel you will be able to burn with full > > speed because the 2.6-Kernel can talk to the burner in DMA mode. > > Current 2.4 Kernel isn't capable of doing this. > > That's only true for non 2048 block sizes (audio, (S)VCD, RAW)). Ups. I have to admit that i never burned via IDE directly. I jumped directly from SCSI to Firewire because i hadn't had a free 5 1/4 slot in my case. Sorry for the confusion. 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: mkisofs questions
On Fri, Oct 17, 2003 at 10:44:58PM +0200, A.P.Munnikes wrote: > Hello, > > I have some questions about mkisofs (I'm using verion 4:2.0+a19-1, but > it is more about mkisofs in gereral) > > > 1. Is it, or is is not, possibele to make a good/working/official image > that is > 4GB. (just with a lot of files with a size from 1 KB to a max. > of 100MB, so not the problem about that the iso9660 can not contains a > file > 2GB) No Prob. I make/use >4GB images for more than 2 years now. As long as you have a current(tm) distribution and a >=2.4.0 kernel there is no problem. (And "current" here means that the distribtion compiled with a kernel >=2.4.0, so that LFS is enabled) 2 years ago i had to compile my own mkisofs, because "back then" the SuSE-mkisofs wasn't compiled correctly(tm). > (if yes: why is the Debian DVD image not > 4 GB ?) They don't need the size? They want downloaders to be able to download it with Windows 95/98? (AFAIK 4GB is the maximum filesize for FAT32) 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 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, 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
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 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
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: hidden file on an iso-image ?
On 21.10.2004 19:20, Helmut Jarausch wrote: > Hi, > > I have an ISO image of 300 Mb which is said to contain software for > Linux and for Windows. > When I burn it onto a CD and mount it or when I mount it directly as > loop device, > I can only see the Linux part ( du -sm shows 144 Mb only). > When I look at it under Windows I can only see the Windows part. > > Is there any means to access everything under Linux? > And how can I create such an image? > > Many thanks for a hint, man mount (Parameter: "unhide") - snip - unhide Also show hidden and associated files. (If the ordinary files and the associated or hidden files have the same filenames, this may make the ordinary files inaccessible.) - snip - a quick glanced shows that 'man mkisofs' also reveals a few "hide"-parameters 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: mkisofs questions
On Fri, Oct 17, 2003 at 10:44:58PM +0200, A.P.Munnikes wrote: > Hello, > > I have some questions about mkisofs (I'm using verion 4:2.0+a19-1, but > it is more about mkisofs in gereral) > > > 1. Is it, or is is not, possibele to make a good/working/official image > that is > 4GB. (just with a lot of files with a size from 1 KB to a max. > of 100MB, so not the problem about that the iso9660 can not contains a > file > 2GB) No Prob. I make/use >4GB images for more than 2 years now. As long as you have a current(tm) distribution and a >=2.4.0 kernel there is no problem. (And "current" here means that the distribtion compiled with a kernel >=2.4.0, so that LFS is enabled) 2 years ago i had to compile my own mkisofs, because "back then" the SuSE-mkisofs wasn't compiled correctly(tm). > (if yes: why is the Debian DVD image not > 4 GB ?) They don't need the size? They want downloaders to be able to download it with Windows 95/98? (AFAIK 4GB is the maximum filesize for FAT32) 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 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, 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 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: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
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: cdrecord on linux 2.6.x x > 2.6.8
Helmut Jarausch wrote: Hi, since Linus's changes to the 2.6.8.1 kernel cdrecord doesn't work anymore when used by a non-root user even if its permissions are set SUID root. Does anybody know about patches to cdrecord and/or the kernel source to make this possible again? I do need the recent kernel (currently 2.6.11). No. But "the other" solutions works flawlessly (for me). ssh [EMAIL PROTECTED] <...> (I haven't use sudo, so i don't know if it is also a solution) -- 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: cdrecord on linux 2.6.x x > 2.6.8
Helmut Jarausch wrote: On 4 Mar, Matthias Schniedermeyer wrote: Helmut Jarausch wrote: Hi, since Linus's changes to the 2.6.8.1 kernel cdrecord doesn't work anymore when used by a non-root user even if its permissions are set SUID root. Does anybody know about patches to cdrecord and/or the kernel source to make this possible again? I do need the recent kernel (currently 2.6.11). No. But "the other" solutions works flawlessly (for me). ssh [EMAIL PROTECTED] It works - BUT I've to tell the root password to all users! No. You can use RSA/DSA keys. And with keys you also have the possiblity to restrict the commands users can invoke at "login"-time, so you COULD e.x. restrict a login with key XY to only be able to call cdrecord. Keyword: command(="/usr/bin/cdrecord") in authorized_keys But i don't know how "good/secure" this is, never used it myself. -- 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]
