Re: CD/DVD writing on IRIX6.5
I have a SGI IRIX 6.5 system with external DVD writer capable of burning DVD+RW and DVD-RW media. This device is connected as SCSI device through a SCSI HBA. ^^ Out of curiosity. You must be using some SCSI to IDE bridge. I wonder what kind and model? Just for reference:-) I would like to know what software is available if I want to :- 1. Write CD-R,DVD-R 2. Optionally also write DVD+R,DVD+RW, with incremental writes. I understand that there are tools available to do this on Linux but not so sure about IRIX 6.5. No, dvd+rw-tools don't support IRIX 6.5. But note that most of other dvd+rw-tools ports are contributed, so have you considered adding support for IRIX yourself? Alternatively I can throw in some initial code (I happened to have an IRIX machine) and you'll polish it in field... A. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: growisofs with ND-1300A problems: write failed:Input/output error
To my surprise I still had autofs in the service list but that gave only a short moment of hope. The fact that autofs appears in service list doesn't necessarily mean that it's the one which caused the trouble(*). It doesn't necessarily configured to control removable storage (at least it doesn't by default as far as I understand). In other words autofs is *one* of the culprits. (*) By trouble I mostly refer to write failed error, not unrecognized profile. After disabling autofs and checking for anything suspisious I made a new try! Still I get the following for both the +RW and the +R media: growisofs -speed=1 -Z /dev/dvd -dvd-video dvd :-( /dev/dvd: media is not recognized as recordable DVD: 10 This message normally means that *unit* failed to recognize media as recordable. The value you see is pulled from unit and is called profile. Profile value of 10 (it's in hex) means that unit has recognized media as DVD-ROM (0 in turn means that *unit* doesn't believe that there is any media in). What does dvd+rw-mediainfo return *right after* you run into this problem? You've posted dvd+rw-mediainfo output in first post. Can you confirm that that ouput was pulled *right after* growisofs has failed with not recognized as recordable? Point is that according to that dvd+rw-mediainfo output profile value is 1B. Provide dvd+rw-tools versioning information as well... And as before, both work flowlessly under XP/Nero. Is there anything more that could influence this?? There was one similar report and it turned out that user mixed different versions in same build directory (I don't know how it happened) and clean recompile solved the problem. It should be noted however that in that case profile values were obviously bogus, not as neat as 10 or 0. A. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Multi Volume CD/DVDs
Pardon my ignorance, but I would like to ask what is the commonly practiced method of creating multi-volume disks. You must be referring to Volume Sequence Number defined for ISO9660 data-set. I myself would first wonder how common is support for *accessing* of such multi-volume data-sets. Note that I'm not saying that I know answer to either question, but I won't be surprised if support for multi-volume *access* turns to be commonly poor. That is, for instance I need to burn a directory that has files whose combined size is, say 12 GB. How would one go about creating multiple ISO9660 images from it and then burning them on CD/DVDs. Is there a way that these images can themselves keep track of information like their position in the sequence, total number of images that constitute the complete dataset etc. Once again you probably should first wonder if and how target OS can use this multi-volume field, because if it doesn't treat it in the way you expect it to, then figuring out how to create multi-volume data-set won't solve the problem. Also, what if the things are complicated by the existence of one or more files of size 2GB. Is this a Linux only issue? Note that it's not an inherent Linux limitation, but Linux isofs implmentation issue. I mean you can access files larger than 2GB under Linux, but not those residing on ISO9660 volume. And the fact that Linux exhibits this deficiency doesn't mean that *all* other implementations are bug-free. I mean breaking 2GB limit is indeed a problem with Linux isofs implementation, but given this fact alone one can't tell that it's not a problem on some other given OS. Is this an issue on 64 bit SGI IRIX systems? I don't think anybody would be able to answer this question definitely. The only way is to try... Keep in mind that in Linux it's rather signed vs. unsigned than 32- vs. 64-bit issue. A. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: DVD writing, alpha architecture, recommendations wanted
Hi Andy! Thanks for your answer, here some comments: On Fre, 19 Mär 2004, Andy Polyakov wrote: As for dvd+rw-tools. There were couple of success reports from Alpha Linux users and I see no reason why it should be more buggy or less ok Good to hear. But the history of supporting stuff on alpha architecture wasn't that good, so I am careful. growisofs.c: In function `setup_fds': growisofs.c:503: warning: cast from pointer to integer of different size Note that those are not errors, but warnings. I can assure that they Yuo, I know this, I checked the code and didn't see anything which I would count as problem, so I didn't care. as intended. I can also add that warning will be eliminated in next update. Good to hear. ^^ Just pick brand-name unit and stick to brand name media. Ok. - Do you know a `good' backup program for DVD? Keep in mind that this is a *discussion* forum. Define backup program and then define 'good' backup program. Think about what's so special about DVD in context of these two definitions. Which backup programs did you use so far? Were they 'good'? Think about why can't you use then with DVD? A. We used self written scripts which in turn used dump for ext2 to tapes. Unfortunately our tapes are now too small for full backups, which makes it very cumbersome. We are in the process of switching to rsnapshots (rsnapshot.org) onto a remote computer with big hard disk (this is the alpha architecture). From their we want to make backups from time to time of the full system. Definition of `good' for me: It should run without more or less any user intervention, only for changing media. Reason for this: We are mathematicians working at the university and in fact don't want to spent a lot of time doing sysadm jobs. Our salary is already low enough ;-) Anyway, I already got some answers off list and will evaluate the options. Thanks for your input and all the best Norbert --- Norbert Preining preining AT logic DOT at Technische Universität Wien gpg DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094 --- BOOKThere is a theory which states that if ever anyone discovers exactly what the Universe is for and why it is here, it will instantly disappear and be replaced by something even more bizarrely inexeplicable. There is another theory which states that this has already happened. --- Introduction to Fit the Seventh. --- Douglas Adams, The Hitchhikers Guide to the Galaxy -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: DVD writing, alpha architecture, recommendations wanted
- Do you know a `good' backup program for DVD? Keep in mind that this is a *discussion* forum. Define backup program and then define 'good' backup program. Think about what's so special about DVD in context of these two definitions. Which backup programs did you use so far? Were they 'good'? Think about why can't you use then with DVD? Those were the questions you should rather have asked yourself in order to figure out what exactly is so special about DVD media, which makes you wonder this questions. My standpoint is that 1/2 of solution lies in posed question and good backup program for DVD is just too fuzzy. E.g.: We used self written scripts which in turn used dump for ext2 to tapes. You can use DVD as tape. Trouble is that if your average dataset is less than single media capacity, then special care has to be taken, as you probably don't want to waste one disc per set... Or you probably don't want to use it as tape and pack data? You might want to keep files accessible as single files for convenient restore... We are in the process of switching to rsnapshots (rsnapshot.org) onto a remote computer with big hard disk (this is the alpha architecture). From their we want to make backups from time to time of the full system. ... or maybe you on the contrary *want* to pack the data, so that it can be *compressed* prior recording. Then big in combination with full sounds like requirement for multi-volume. There was a post on the list how to burn arbitrary input stream to multiple volumes... Once again. Those are the question you should ask *yourself*. It's not my intention to find a solution that suits some particular need, but rather to make you and/or public to pose more tangible questions. ... some answers off list... Note to the public. Things discussed off-list tend to so to say disappear in vain. Open up and *share* your experience with public. Note to request originator. Consider posting summary. A. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Multi Volume CD/DVDs
... I would like to ask what is the commonly practiced method of creating multi-volume disks. That is, for instance I need to burn a directory that has files whose combined size is, say 12 GB. How would one go about creating multiple ISO9660 images from it and then burning them on CD/DVDs. A few years ago i was faced with the same problem and my solution is available as open source software : http://scdbackup.webframe.org/scdbackup-0.8.tar.gz see file README Homepage : http://scdbackup.webframe.org/main_eng.html In respect to other comments i have read so far : scdbackup does not use exotic ISO 9660 features. It produces plain independend ISO filesystems (+RockRidge) on several CDs. To Andy : Hi, scdbackup is one of the off-list answers sent to Norbert Preining about his request for a 'good' backup program. I was reluctant to advertise my stuff as such a thing. Ashish Rangole on the other hand asked for a central feature of scdbackup which i am proud to present. Worthless, of course, without mkisofs, afio, cdrecord or growisofs. (Taking a bow) Is there a way that these images can themselves keep track of information like their position in the sequence, total number of images that constitute the complete dataset etc. scdbackup-0.8 maintains a list of checksum records (MD5) which may be used to identify a volume of a multi volume backup. Those records tell date, total number of volumes and sequence number of the given volume. But this needs to read the whole media and will fail if the media is damaged. (It's actually intended for verifying write success.) So you will be better off with a leaflet of paper which holds the desired information in human readable form. Paint unique, permanent ID numbers on your media and refer to them on the leaflet. (Staedler Lumocolor pens seem to do no harm to the surface of a CD-RW. I never tested Edding pens.) Also, what if the things are complicated by the existence of one or more files of size 2GB. That depends wether the affected programs got compiled with Large File Support. I was told that mkisofs of cdrtools-2.01a19 has that feature (there are newer releases meanwhile). Is this a Linux only issue? Traditional functions and data structures of the file system interface used 32-bit signed integers (e.g. fseek got parameter long offset ). With Linux (and others) there are compile time macros which switch to more modern data types : _FILE_OFFSET_BITS=64 _LARGEFILE_SOURCE Is this an issue on 64 bit SGI IRIX systems? I suppose that SGI's own programs do support large files while possibly some third-party programs don't. scdbackup's programs get compiled with Large File Support. You will also need mkisofs with that feature (see above). Nevertheless, when creating ISO 9660 filesystems, scdbackup can not handle files which are larger than a single media. Therefore files 2GB can only be backuped on DVD (scdbackup uses growisofs to write the media) or in format afio (large file support since afio-2.4.7.9beta4). Have a nice day :) Thomas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Multi Volume CD/DVDs
To Andy : scdbackup is one of the off-list answers sent to Norbert Preining about his request for a 'good' backup program. Please note that I'm not blaming [nor in position to blame] anybody for choices they make. I merely *encoraged* public to open up, as it felt there is a need for that. My comment was *not* based solely on that particular remark, so don't take it personally. I was reluctant to advertise my stuff as such a thing. Modesty is of course valuable quality, but keep in mind that it's a *discussion* forum. Statement or proposed solution doesn't have to be 100% correct or perfectly suitable for some particular situation. That's why we *discuss* it, don't we? scdbackup-0.8 maintains a list of checksum records (MD5) which may be used to identify a volume of a multi volume backup. Great! Also, what if the things are complicated by the existence of one or more files of size 2GB. That depends wether the affected programs got compiled with Large File Support. I was told that mkisofs of cdrtools-2.01a19 has that feature (there are newer releases meanwhile). Is this a Linux only issue? Traditional functions and data structures of the file system interface used 32-bit signed integers (e.g. fseek got parameter long offset ). Once again. Keep in mind that Linux isofs implementation is deficient in such way which effectively limits maximum file size to 2G-1 byte. I mean even if kernel itself supports large files and all application programs are explicitly compiled with large file support, you still get into trouble [as long as we're talking about ISO9660 that is]. I assumed that Ashish was referring to this limitation, as it was discussed serveral times on this list. I might be wrong in my assumption (but that's OK as already established:-). Cheers. A. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Multi Volume CD/DVDs
On Fri, 19 Mar 2004 [EMAIL PROTECTED] wrote: On Fri, 19 Mar 2004, Andy Polyakov wrote: My comment was *not* based solely on that particular remark, so don't take it personally. No offense taken. And if ever ... your merits would outweight it. scdbackup-0.8 maintains a list of checksum records (MD5) which may be used to identify a volume of a multi volume backup. Great! ... and it got a bash script on each CD/DVD which tells you the volume number, the date and can tell you on which volume a file may be found. (Silly me, that would have been the better answer.) Once again. Keep in mind that Linux isofs implementation is deficient in such way which effectively limits maximum file size to 2G-1 byte. I was not aware of that. Still using CD-RW and only getting reports from my DVD users. At least one of them got happy with large files after pointing me to the lack of Large File Support in scdbackup-0.7 . Conclusion so far : For files larger than 2 GB i can only propose to use afio format rather than ISO. Again: get at least afio-2.4.7.9beta4 for that and make thorough tests including real restore experiments. Be aware that 4 GB might be another limit. Have a nice day :) Thomas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: permissions denied when using k3b
Joerg Schilling wrote: From: Geoffrey [EMAIL PROTECTED] I'm curious as to if anyone has found a reasonable solution to problems with the various gui interfaces running as a non-root user when cdrecord is the chosen tool? I've tried setting permissions on the device, setuid bit and sudo, to no avail. cdrecord always exists because of permissions. There is an official way to do this - see man cdrecord I tried this and it did not work. What does work is using sudo with the proper configuration (NOPASSWD for select users). -- Until later, Geoffrey Registered Linux User #108567 Building secure systems in spite of Microsoft -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Re: LF-D311 support?
Title: Re: Re: LF-D311 support? We are looking for a repair place that fixes these dvd ram drives? Also for the older style LF-D211V. Is there a place that does repair on panasonic dvd drives? Colette Dryden Voice Products, Inc. Assistant Operations Manager (316) 616- ext. 116
Re: CD/DVD writing on IRIX6.5
I have a SGI IRIX 6.5 system with external DVD writer capable of burning DVD+RW and DVD-RW media. This device is connected as SCSI device through a SCSI HBA. ^^ Out of curiosity. You must be using some SCSI to IDE bridge. I wonder what kind and model? Just for reference:-) I would like to know what software is available if I want to :- 1. Write CD-R,DVD-R 2. Optionally also write DVD+R,DVD+RW, with incremental writes. I understand that there are tools available to do this on Linux but not so sure about IRIX 6.5. No, dvd+rw-tools don't support IRIX 6.5. But note that most of other dvd+rw-tools ports are contributed, so have you considered adding support for IRIX yourself? Alternatively I can throw in some initial code (I happened to have an IRIX machine) and you'll polish it in field... A.
Re: growisofs with ND-1300A problems: write failed:Input/output error
To my surprise I still had autofs in the service list but that gave only a short moment of hope. The fact that autofs appears in service list doesn't necessarily mean that it's the one which caused the trouble(*). It doesn't necessarily configured to control removable storage (at least it doesn't by default as far as I understand). In other words autofs is *one* of the culprits. (*) By trouble I mostly refer to write failed error, not unrecognized profile. After disabling autofs and checking for anything suspisious I made a new try! Still I get the following for both the +RW and the +R media: growisofs -speed=1 -Z /dev/dvd -dvd-video dvd :-( /dev/dvd: media is not recognized as recordable DVD: 10 This message normally means that *unit* failed to recognize media as recordable. The value you see is pulled from unit and is called profile. Profile value of 10 (it's in hex) means that unit has recognized media as DVD-ROM (0 in turn means that *unit* doesn't believe that there is any media in). What does dvd+rw-mediainfo return *right after* you run into this problem? You've posted dvd+rw-mediainfo output in first post. Can you confirm that that ouput was pulled *right after* growisofs has failed with not recognized as recordable? Point is that according to that dvd+rw-mediainfo output profile value is 1B. Provide dvd+rw-tools versioning information as well... And as before, both work flowlessly under XP/Nero. Is there anything more that could influence this?? There was one similar report and it turned out that user mixed different versions in same build directory (I don't know how it happened) and clean recompile solved the problem. It should be noted however that in that case profile values were obviously bogus, not as neat as 10 or 0. A.
Re: DVD writing, alpha architecture, recommendations wanted
- Is writing of DVDs supported on alpha architecture, and if yes, is it still `buggy' or ok? As for dvd+rw-tools. There were couple of success reports from Alpha Linux users and I see no reason why it should be more buggy or less ok on Alpha Linux than on any other Linux (or other supported architecture for that matter). For cdrecord-prodvd I do not see alpha/linux architecture. For dvd+rw-tools I have built my own backport from the debian/sid package, but got the following errors compiling: growisofs.c: In function `setup_fds': growisofs.c:503: warning: cast from pointer to integer of different size Note that those are not errors, but warnings. I can assure that they don't affect functionality of dvd+rw-tools and the latter should perform as intended. I can also add that warning will be eliminated in next update. - Can I put the DVD writer on the Promise controller? I know that there are some controllers which do not accept CDROM drives (my HPT eg). I have no comment on this. - Finally, which DVD writer could you recommend? The market is not very mature and it's apparently possible to run into trouble with virtually any unit. By trouble I mean media problems, poorly supported media in firmware, which manifest themselves in most bizarre ways. Our main/only usage will be for backing up ^^ Just pick brand-name unit and stick to brand name media. - Do you know a `good' backup program for DVD? Keep in mind that this is a *discussion* forum. Define backup program and then define 'good' backup program. Think about what's so special about DVD in context of these two definitions. Which backup programs did you use so far? Were they 'good'? Think about why can't you use then with DVD? A.
Re: DVD writing, alpha architecture, recommendations wanted
Hi Andy! Thanks for your answer, here some comments: On Fre, 19 Mär 2004, Andy Polyakov wrote: As for dvd+rw-tools. There were couple of success reports from Alpha Linux users and I see no reason why it should be more buggy or less ok Good to hear. But the history of supporting stuff on alpha architecture wasn't that good, so I am careful. growisofs.c: In function `setup_fds': growisofs.c:503: warning: cast from pointer to integer of different size Note that those are not errors, but warnings. I can assure that they Yuo, I know this, I checked the code and didn't see anything which I would count as problem, so I didn't care. as intended. I can also add that warning will be eliminated in next update. Good to hear. ^^ Just pick brand-name unit and stick to brand name media. Ok. - Do you know a `good' backup program for DVD? Keep in mind that this is a *discussion* forum. Define backup program and then define 'good' backup program. Think about what's so special about DVD in context of these two definitions. Which backup programs did you use so far? Were they 'good'? Think about why can't you use then with DVD? A. We used self written scripts which in turn used dump for ext2 to tapes. Unfortunately our tapes are now too small for full backups, which makes it very cumbersome. We are in the process of switching to rsnapshots (rsnapshot.org) onto a remote computer with big hard disk (this is the alpha architecture). From their we want to make backups from time to time of the full system. Definition of `good' for me: It should run without more or less any user intervention, only for changing media. Reason for this: We are mathematicians working at the university and in fact don't want to spent a lot of time doing sysadm jobs. Our salary is already low enough ;-) Anyway, I already got some answers off list and will evaluate the options. Thanks for your input and all the best Norbert --- Norbert Preining preining AT logic DOT at Technische Universität Wien gpg DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094 --- BOOKThere is a theory which states that if ever anyone discovers exactly what the Universe is for and why it is here, it will instantly disappear and be replaced by something even more bizarrely inexeplicable. There is another theory which states that this has already happened. --- Introduction to Fit the Seventh. --- Douglas Adams, The Hitchhikers Guide to the Galaxy
Re: Multi Volume CD/DVDs
... I would like to ask what is the commonly practiced method of creating multi-volume disks. That is, for instance I need to burn a directory that has files whose combined size is, say 12 GB. How would one go about creating multiple ISO9660 images from it and then burning them on CD/DVDs. A few years ago i was faced with the same problem and my solution is available as open source software : http://scdbackup.webframe.org/scdbackup-0.8.tar.gz see file README Homepage : http://scdbackup.webframe.org/main_eng.html In respect to other comments i have read so far : scdbackup does not use exotic ISO 9660 features. It produces plain independend ISO filesystems (+RockRidge) on several CDs. To Andy : Hi, scdbackup is one of the off-list answers sent to Norbert Preining about his request for a 'good' backup program. I was reluctant to advertise my stuff as such a thing. Ashish Rangole on the other hand asked for a central feature of scdbackup which i am proud to present. Worthless, of course, without mkisofs, afio, cdrecord or growisofs. (Taking a bow) Is there a way that these images can themselves keep track of information like their position in the sequence, total number of images that constitute the complete dataset etc. scdbackup-0.8 maintains a list of checksum records (MD5) which may be used to identify a volume of a multi volume backup. Those records tell date, total number of volumes and sequence number of the given volume. But this needs to read the whole media and will fail if the media is damaged. (It's actually intended for verifying write success.) So you will be better off with a leaflet of paper which holds the desired information in human readable form. Paint unique, permanent ID numbers on your media and refer to them on the leaflet. (Staedler Lumocolor pens seem to do no harm to the surface of a CD-RW. I never tested Edding pens.) Also, what if the things are complicated by the existence of one or more files of size 2GB. That depends wether the affected programs got compiled with Large File Support. I was told that mkisofs of cdrtools-2.01a19 has that feature (there are newer releases meanwhile). Is this a Linux only issue? Traditional functions and data structures of the file system interface used 32-bit signed integers (e.g. fseek got parameter long offset ). With Linux (and others) there are compile time macros which switch to more modern data types : _FILE_OFFSET_BITS=64 _LARGEFILE_SOURCE Is this an issue on 64 bit SGI IRIX systems? I suppose that SGI's own programs do support large files while possibly some third-party programs don't. scdbackup's programs get compiled with Large File Support. You will also need mkisofs with that feature (see above). Nevertheless, when creating ISO 9660 filesystems, scdbackup can not handle files which are larger than a single media. Therefore files 2GB can only be backuped on DVD (scdbackup uses growisofs to write the media) or in format afio (large file support since afio-2.4.7.9beta4). Have a nice day :) Thomas
Re: Multi Volume CD/DVDs
To Andy : scdbackup is one of the off-list answers sent to Norbert Preining about his request for a 'good' backup program. Please note that I'm not blaming [nor in position to blame] anybody for choices they make. I merely *encoraged* public to open up, as it felt there is a need for that. My comment was *not* based solely on that particular remark, so don't take it personally. I was reluctant to advertise my stuff as such a thing. Modesty is of course valuable quality, but keep in mind that it's a *discussion* forum. Statement or proposed solution doesn't have to be 100% correct or perfectly suitable for some particular situation. That's why we *discuss* it, don't we? scdbackup-0.8 maintains a list of checksum records (MD5) which may be used to identify a volume of a multi volume backup. Great! Also, what if the things are complicated by the existence of one or more files of size 2GB. That depends wether the affected programs got compiled with Large File Support. I was told that mkisofs of cdrtools-2.01a19 has that feature (there are newer releases meanwhile). Is this a Linux only issue? Traditional functions and data structures of the file system interface used 32-bit signed integers (e.g. fseek got parameter long offset ). Once again. Keep in mind that Linux isofs implementation is deficient in such way which effectively limits maximum file size to 2G-1 byte. I mean even if kernel itself supports large files and all application programs are explicitly compiled with large file support, you still get into trouble [as long as we're talking about ISO9660 that is]. I assumed that Ashish was referring to this limitation, as it was discussed serveral times on this list. I might be wrong in my assumption (but that's OK as already established:-). Cheers. A.
Re: Multi Volume CD/DVDs
On Fri, 19 Mar 2004 [EMAIL PROTECTED] wrote: On Fri, 19 Mar 2004, Andy Polyakov wrote: My comment was *not* based solely on that particular remark, so don't take it personally. No offense taken. And if ever ... your merits would outweight it. scdbackup-0.8 maintains a list of checksum records (MD5) which may be used to identify a volume of a multi volume backup. Great! ... and it got a bash script on each CD/DVD which tells you the volume number, the date and can tell you on which volume a file may be found. (Silly me, that would have been the better answer.) Once again. Keep in mind that Linux isofs implementation is deficient in such way which effectively limits maximum file size to 2G-1 byte. I was not aware of that. Still using CD-RW and only getting reports from my DVD users. At least one of them got happy with large files after pointing me to the lack of Large File Support in scdbackup-0.7 . Conclusion so far : For files larger than 2 GB i can only propose to use afio format rather than ISO. Again: get at least afio-2.4.7.9beta4 for that and make thorough tests including real restore experiments. Be aware that 4 GB might be another limit. Have a nice day :) Thomas
Re: permissions denied when using k3b
Joerg Schilling wrote: From: Geoffrey [EMAIL PROTECTED] I'm curious as to if anyone has found a reasonable solution to problems with the various gui interfaces running as a non-root user when cdrecord is the chosen tool? I've tried setting permissions on the device, setuid bit and sudo, to no avail. cdrecord always exists because of permissions. There is an official way to do this - see man cdrecord I tried this and it did not work. What does work is using sudo with the proper configuration (NOPASSWD for select users). -- Until later, Geoffrey Registered Linux User #108567 Building secure systems in spite of Microsoft
