September 2006 Archives by thread

• Messages sorted by: [ subject ] [ author ] [ date ]
• More info on this list...

Starting: Fri Sep 1 02:30:09 CST 2006
Ending: Sat Sep 30 10:51:48 CST 2006
Messages: 228

• [Libburn-tickets] Re: [libburn] #6: Wish: A write mode like cdrecord -tao   libburn
• [Libburn-tickets] Re: [libburn] #58: Progress always reports 0 as track number   libburn
• [Libburn-tickets] Re: [libburn] #46: API to exclude children files   libburn
• [Libburn-tickets] Re: [libburn] #48: API to add a directory or a file by their path on the disc   libburn
• [Libburn-tickets] Re: [libburn] #47: API to search for node by path   libburn
• [Libburn-tickets] Re: [libburn] #55: cdrskin beginns to burn without getting data   libburn
• [Libburn-tickets] [libburn] #60: My intentions and proposals about a new API documentation portal   libburn
  • [Libburn-tickets] Re: [libburn] #60: My intentions and proposals about a new API documentation portal   libburn
  • [Libburn-tickets] Re: [libburn] #60: My intentions and proposals about a new API documentation portal   libburn
  • [Libburn-tickets] Re: [libburn] #60: My intentions and proposals about a new API documentation portal   libburn
  • [Libburn-tickets] Re: [libburn] #60: My intentions and proposals about a new API documentation portal   libburn
  • [Libburn-tickets] Re: [libburn] #60: My intentions and proposals about a new API documentation portal   libburn
  • [Libburn-tickets] Re: [libburn] #60: My intentions and proposals about a new API documentation portal   libburn
  • [Libburn-tickets] Re: [libburn] #60: My intentions and proposals about a new API documentation portal   libburn
  • [Libburn-tickets] Re: [libburn] #60: My intentions and proposals about a new API documentation portal   libburn
  • [Libburn-tickets] Re: [libburn] #60: My intentions and proposals about a new API documentation portal   libburn
  • [Libburn-tickets] Re: [libburn] #60: My intentions and proposals about a new API documentation portal   libburn
  • [Libburn-tickets] Re: [libburn] #60: My intentions and proposals about a new API documentation portal   libburn
  • [Libburn-tickets] Re: [libburn] #60: My intentions and proposals about a new API documentation portal   libburn
  • [Libburn-tickets] Re: [libburn] #60: My intentions and proposals about a new API documentation portal   libburn
  • [Libburn-tickets] Re: [libburn] #60: My intentions and proposals about a new API documentation portal   libburn
  • [Libburn-tickets] Re: [libburn] #60: My intentions and proposals about a new API documentation portal   libburn
• [Libburn-tickets] Re: [libburn] #2: Disc Reading is Incorrect   libburn
• [Libburn-tickets] [libburn] #61: API improvements concerning specific usecases   libburn
  • [Libburn-tickets] Re: [libburn] #61: API improvements concerning specific usecases   libburn
  • [Libburn-tickets] Re: [libburn] #61: API improvements concerning specific usecases   libburn
  • [Libburn-tickets] Re: [libburn] #61: API improvements concerning specific usecases   libburn
  • [Libburn-tickets] Re: [libburn] #61: API improvements concerning specific usecases   libburn
  • [Libburn-tickets] Re: [libburn] #61: API improvements concerning specific usecases   libburn
  • [Libburn-tickets] Re: [libburn] #61: API improvements concerning specific usecases   libburn
  • [Libburn-tickets] Re: [libburn] #61: API improvements concerning specific usecases   libburn
• [Libburn-tickets] [libburn] #62: Scanning for new devices requires one to lose all the old ones.   libburn
  • [Libburn-tickets] Re: [libburn] #62: Scanning for new devices requires one to lose all the old ones.   libburn
  • [Libburn-tickets] Re: [libburn] #62: Scanning for new devices requires one to lose all the old ones.   libburn
  • [Libburn-tickets] Re: [libburn] #62: Scanning for new devices requires one to lose all the old ones.   libburn
  • [Libburn-tickets] Re: [libburn] #62: Scanning for new devices requires one to lose all the old ones.   libburn
  • [Libburn-tickets] Re: [libburn] #62: Scanning for new devices requires one to lose all the old ones.   libburn
  • [Libburn-tickets] Re: [libburn] #62: Scanning for new devices requires one to lose all the old ones.   libburn
  • [Libburn-tickets] Re: [libburn] #62: Scanning for new devices requires one to lose all the old ones.   libburn
  • [Libburn-tickets] Re: [libburn] #62: Scanning for new devices requires one to lose all the old ones.   libburn
  • [Libburn-tickets] Re: [libburn] #62: Scanning for new devices requires one to lose all the old ones.   libburn
  • [Libburn-tickets] Re: [libburn] #62: Scanning for new devices requires one to lose all the old ones.   libburn
  • [Libburn-tickets] Re: [libburn] #62: Scanning for new devices requires one to lose all the old ones.   libburn
  • [Libburn-tickets] Re: [libburn] #62: Scanning for new devices requires one to lose all the old ones.   libburn
  • [Libburn-tickets] Re: [libburn] #62: Scanning for new devices requires one to lose all the old ones.   libburn
  • [Libburn-tickets] Re: [libburn] #62: Scanning for new devices requires one to lose all the old ones.   libburn
  • [Libburn-tickets] Re: [libburn] #62: Scanning for new devices requires one to lose all the old ones.   libburn
  • [Libburn-tickets] Re: [libburn] #62: Scanning for new devices requires one to lose all the old ones.   libburn
  • [Libburn-tickets] Re: [libburn] #62: Scanning for new devices requires one to lose all the old ones.   libburn
  • [Libburn-tickets] Re: [libburn] #62: Scanning for new devices requires one to lose all the old ones.   libburn
  • [Libburn-tickets] Re: [libburn] #62: Scanning for new devices requires one to lose all the old ones.   libburn
  • [Libburn-tickets] Re: [libburn] #62: Scanning for new devices requires one to lose all the old ones.   libburn
  • [Libburn-tickets] Re: [libburn] #62: Scanning for new devices requires one to lose all the old ones.   libburn
  • [Libburn-tickets] Re: [libburn] #62: Scanning for new devices requires one to lose all the old ones.   libburn
  • [Libburn-tickets] Re: [libburn] #62: Scanning for new devices requires one to lose all the old ones.   libburn
  • [Libburn-tickets] Re: [libburn] #62: Scanning for new devices requires one to lose all the old ones.   libburn
  • [Libburn-tickets] Re: [libburn] #62: Scanning for new devices requires one to lose all the old ones.   libburn
  • [Libburn-tickets] Re: [libburn] #62: Scanning for new devices requires one to lose all the old ones.   libburn
  • [Libburn-tickets] Re: [libburn] #62: Scanning for new devices requires one to lose all the old ones.   libburn
  • [Libburn-tickets] Re: [libburn] #62: Scanning for new devices requires one to lose all the old ones.   libburn
  • [Libburn-tickets] Re: [libburn] #62: Scanning for new devices requires one to lose all the old ones.   libburn
  • [Libburn-tickets] Re: [libburn] #62: Scanning for new devices requires one to lose all the old ones.   libburn
  • [Libburn-tickets] Re: [libburn] #62: Scanning for new devices requires one to lose all the old ones.   libburn
  • [Libburn-tickets] Re: [libburn] #62: Scanning for new devices requires one to lose all the old ones.   libburn
  • [Libburn-tickets] Re: [libburn] #62: Scanning for new devices requires one to lose all the old ones.   libburn
  • [Libburn-tickets] Re: [libburn] #62: Scanning for new devices requires one to lose all the old ones.   libburn
  • [Libburn-tickets] Re: [libburn] #62: Scanning for new devices requires one to lose all the old ones.   libburn
  • [Libburn-tickets] Re: [libburn] #62: Scanning for new devices requires one to lose all the old ones.   libburn
  • [Libburn-tickets] Re: [libburn] #62: Scanning for new devices requires one to lose all the old ones.   libburn
  • [Libburn-tickets] Re: [libburn] #62: Scanning for new devices requires one to lose all the old ones.   libburn
  • [Libburn-tickets] Re: [libburn] #62: Scanning for new devices requires one to lose all the old ones.   libburn
  • [Libburn-tickets] Re: [libburn] #62: Scanning for new devices requires one to lose all the old ones.   libburn
  • [Libburn-tickets] Re: [libburn] #62: Scanning for new devices requires one to lose all the old ones.   libburn
  • [Libburn-tickets] Re: [libburn] #62: Scanning for new devices requires one to lose all the old ones.   libburn
• [Libburn-tickets] Re: [libburn] #35: How to reset browser+ticket system after "Mid Air Collision" ?   libburn
• [Libburn-tickets] Re: [libburn] #16: Subproject: Find out everything that cdrecord -v -atip can find out   libburn
• [Libburn-tickets] Re: [libburn] #16: Subproject: Find out everything that cdrecord -v -atip can find out   libburn
• [Libburn-tickets] Re: [libburn] #31: Beef up Doxygen example by a hint to click on #include <libburn/libburn.h> in example   libburn
• [Libburn-tickets] Re: [libburn] #39: Change sequence of API doxygen items   libburn
• [Libburn-tickets] Re: [libburn] #4: Better Error Handling   libburn
• [Libburn-tickets] Re: [libburn] #4: Better Error Handling   libburn
• [Libburn-tickets] [libburn] #63: What is cdrecord doing while "Fixating" ?   libburn
  • [Libburn-tickets] Re: [libburn] #63: What is cdrecord doing while "Fixating" ?   libburn
  • [Libburn-tickets] Re: [libburn] #63: What is cdrecord doing while "Fixating" ?   libburn
  • [Libburn-tickets] Re: [libburn] #63: What is cdrecord doing while "Fixating" ?   libburn
• [Libburn-tickets] [libburn] #64: tree corruption   libburn
  • [Libburn-tickets] Re: [libburn] #64: tree corruption   libburn
  • [Libburn-tickets] Re: [libburn] #64: tree corruption   libburn
  • [Libburn-tickets] Re: [libburn] #64: tree corruption   libburn
• [Libburn-tickets] [libburn] #65: Rock ridge names should not be formed after iso names   libburn
  • [Libburn-tickets] Re: [libburn] #65: Rock ridge names should not be formed after iso names   libburn
  • [Libburn-tickets] Re: [libburn] #65: Rock ridge names should not be formed after iso names   libburn
• [Libburn-tickets] Re: [libburn] #55: cdrskin beginns to burn without getting data   libburn
• [Libburn-tickets] [libburn] #66: Burnfree enabled by default   libburn
  • [Libburn-tickets] Re: [libburn] #66: Burnfree enabled by default   libburn
  • [Libburn-tickets] Re: [libburn] #66: Burnfree enabled by default   libburn
  • [Libburn-tickets] Re: [libburn] #66: Burnfree enabled by default   libburn
  • [Libburn-tickets] Re: [libburn] #66: Burnfree enabled by default   libburn
  • [Libburn-tickets] Re: [libburn] #66: Burnfree enabled by default   libburn
  • [Libburn-tickets] Re: [libburn] #66: Burnfree enabled by default   libburn
  • [Libburn-tickets] Re: [libburn] #66: Burnfree enabled by default   libburn
  • [Libburn-tickets] Re: [libburn] #66: Burnfree enabled by default   libburn
  • [Libburn-tickets] Re: [libburn] #66: Burnfree enabled by default   libburn
• [Libburn-tickets] Re: [libburn] #31: Beef up Doxygen example by a hint to click on #include <libburn/libburn.h> in example   libburn
• [Libburn-tickets] Re: [libburn] #39: Change sequence of API doxygen items   libburn
• [Libburn-tickets] Re: [libburn] #18: Please open the cd device using O_EXCL (forwarded from the debian bugtracker)   libburn
• [Libburn-tickets] Re: [libburn] #42: Blanking appendable discs isn't allowed, but works for me...   libburn
• [Libburn-tickets] Re: [libburn] #58: Progress always reports 0 as track number   libburn
• [Libburn-tickets] Re: [libburn] #9: struct burn_progress.track is always 0   libburn
• [Libburn-tickets] Re: [libburn] #2: Disc Reading is Incorrect   libburn
• [Libburn-tickets] Re: [libburn] #51: function to free struct iso_volset   libburn
• [Libburn-tickets] Re: [libburn] #51: function to free struct iso_volset   libburn
• [Libburn-tickets] Re: [libburn] #51: function to free struct iso_volset   libburn
• [Libburn-tickets] [libburn] #67: cflags in libburn-1.pc are wrong   libburn
  • [Libburn-tickets] Re: [libburn] #67: cflags in libburn-1.pc are wrong   libburn
• [Libburn-tickets] Re: [libburn] #8: False reports of drive and media status after load   libburn
• [Libburn-tickets] Re: [libburn] #8: False reports of drive and media status after load   libburn
• [Libburn-tickets] Re: [libburn] #51: function to free struct iso_volset   libburn
• [Libburn-tickets] Re: [libburn] #10: BURN_DRIVE_GRABBING cannot be aborted or canceled   libburn
• [Libburn-tickets] Re: [libburn] #23: Close device file descriptors as soon as possible.   libburn
• [Libburn-tickets] Re: [libburn] #23: Close device file descriptors as soon as possible.   libburn
• [Libburn-tickets] Re: [libburn] #44: Identify the reason for the high CPU load during libburn startup   libburn
• [Libburn-tickets] Re: [libburn] #52: Confusing, bad and redundant code   libburn
• [Libburn-tickets] Re: [libburn] #56: Separate eject function from burn_drive_release   libburn
• [Libburn-tickets] Re: [libburn] #56: Separate eject function from burn_drive_release   libburn
• [Libburn-tickets] Re: [libburn] #33: Follow symbolic links in /dev   libburn
• [Libburn-tickets] Re: [libburn] #41: Pulling from next track can leave drive unusable if no next track   libburn
• [Libburn-tickets] Re: [libburn] #34: Audio support within cdrskin and maybe some docs for other audio app developers on libburn   libburn
• [Libburn-tickets] Re: [libburn] #57: Read buffers show outdated content after write.   libburn
• [Libburn-tickets] Re: [libburn] #57: Read buffers show outdated content after write.   libburn
• [Libburn-tickets] [libburn] #68: hfs volume support   libburn
  • [Libburn-tickets] Re: [libburn] #68: hfs volume support   libburn
  • [Libburn-tickets] Re: [libburn] #68: hfs hybrid filesystem   libburn
  • [Libburn-tickets] Re: [libburn] #68: hfs hybrid filesystem   libburn
  • [Libburn-tickets] Re: [libburn] #68: hfs hybrid filesystem   libburn
• [Libburn-tickets] [libburn] #69: udf extension support   libburn
• [Libburn-tickets] [libburn] #70: CD-RW packet writing/formatting support   libburn
• [Libburn-tickets] [libburn] #71: HFS+ hybrid support   libburn
  • [Libburn-tickets] Re: [libburn] #71: HFS+ hybrid support   libburn
  • [Libburn-tickets] Re: [libburn] #71: HFS+ hybrid support   libburn
• [Libburn-tickets] [libburn] #72: burn_drive_scan returns no drives available when drive is mounted   libburn
  • [Libburn-tickets] Re: [libburn] #72: burn_drive_scan returns no drives available when drive is mounted   libburn
  • [Libburn-tickets] Re: [libburn] #72: burn_drive_scan returns no drives available when drive is mounted   libburn
  • [Libburn-tickets] Re: [libburn] #72: burn_drive_scan returns no drives available when drive is mounted   libburn
• [Libburn-tickets] Re: [libburn] #41: Pulling from next track can leave drive unusable if no next track   libburn
• [Libburn-tickets] Re: [libburn] #41: Pulling from next track can leave drive unusable if no next track   libburn
• [Libburn-tickets] Re: [libburn] #41: Pulling from next track can leave drive unusable if no next track   libburn
• [Libburn-tickets] Re: [libburn] #41: Pulling from next track leaves drive unusable if no next track   libburn
• [Libburn-tickets] Re: [libburn] #41: Pulling from next track leaves drive unusable if no next track   libburn
• [Libburn-tickets] Re: [libburn] #41: Pulling from next track leaves drive unusable if no next track   libburn
• [Libburn-tickets] Re: [libburn] #41: Pulling from next track leaves drive unusable if no next track   libburn
• [Libburn-tickets] Re: [libburn] #1: Change Lead-In Addressing   libburn
• [Libburn-tickets] Re: [libburn] #1: Change Lead-In Addressing   libburn
• [Libburn-tickets] Re: [libburn] #1: Change Lead-In Addressing   libburn
• [Libburn-tickets] Re: [libburn] #41: Pulling from next track leaves drive unusable if no next track   libburn
• [Libburn-tickets] Re: [libburn] #41: Pulling from next track leaves drive unusable if no next track   libburn
• [Libburn-tickets] Re: [libburn] #41: Pulling from next track leaves drive unusable if no next track   libburn
• [Libburn-tickets] Re: [libburn] #41: Pulling from next track leaves drive unusable if no next track   libburn
• [Libburn-tickets] [libburn] #73: Joliet without Rockridge creates unusable iso   libburn
  • [Libburn-tickets] Re: [libburn] #73: Joliet without Rockridge creates unusable iso   libburn
  • [Libburn-tickets] Re: [libburn] #73: Joliet without Rockridge creates unusable iso   libburn
  • [Libburn-tickets] Re: [libburn] #73: Joliet without Rockridge creates unusable iso   libburn
• [Libburn-tickets] [libburn] #74: close() is used without checking the return value, which is a "serious programming error" according to 'man close'.   libburn
  • [Libburn-tickets] Re: [libburn] #74: close() is used without checking the return value, which is a "serious programming error" according to 'man close'.   libburn
  • [Libburn-tickets] Re: [libburn] #74: close() is used without checking the return value, which is a "serious programming error" according to 'man close'.   libburn
  • [Libburn-tickets] Re: [libburn] #74: close() is used without checking the return value, which is a "serious programming error" according to 'man close'.   libburn
  • [Libburn-tickets] Re: [libburn] #74: close() is used without checking the return value, which is a "serious programming error" according to 'man close'.   libburn
  • [Libburn-tickets] Re: [libburn] #74: close() is used without checking the return value, which is a "serious programming error" according to 'man close'.   libburn
  • [Libburn-tickets] Re: [libburn] #74: close() is used without checking the return value, which is a "serious programming error" according to 'man close'.   libburn
  • [Libburn-tickets] Re: [libburn] #74: close() is used without checking the return value, which is a "serious programming error" according to 'man close'.   libburn
• [Libburn-tickets] Re: [libburn] #53: premature return of burn_disc_erase() on some drives   libburn
• [Libburn-tickets] Re: [libburn] #53: premature return of burn_disc_erase() on some drives   libburn
• [Libburn-tickets] Re: [libburn] #53: premature return of burn_disc_erase() on some drives   libburn
• [Libburn-tickets] Re: [libburn] #41: Pulling from next track leaves drive unusable if no next track   libburn
• [Libburn-tickets] Re: [libburn] #26: El-torito support   libburn
• [Libburn-tickets] Re: [libburn] #41: Pulling from next track leaves drive unusable if no next track   libburn
• [Libburn-tickets] Re: [libburn] #41: Pulling from next track leaves drive unusable if no next track   libburn
• [Libburn-tickets] Re: [libburn] #3: Fix Pre-Gaps   libburn
• [Libburn-tickets] Re: [libburn] #54: API to blank single sessions or tracks rather than entire disc   libburn
• [Libburn-tickets] Re: [libburn] #14: Wish: A way to query the drive's buffer fill   libburn
• [Libburn-tickets] Re: [libburn] #54: API to blank single sessions or tracks rather than entire disc   libburn
• [Libburn-tickets] Re: [libburn] #28: Post your unclear problem sightings here, for now   libburn
• [Libburn-tickets] Re: [libburn] #33: Follow symbolic links in /dev   libburn
• [Libburn-tickets] Re: [libburn] #33: Follow symbolic links in /dev   libburn
• [Libburn-tickets] Re: [libburn] #33: Follow symbolic links in /dev   libburn
• [Libburn-tickets] [libburn] #75: cdrskin does not work properly with address 1, 1, 0   libburn
  • [Libburn-tickets] Re: [libburn] #75: cdrskin does not work properly with address 1, 1, 0   libburn
  • [Libburn-tickets] Re: [libburn] #75: cdrskin does not work properly with address 1, 1, 0   libburn
  • [Libburn-tickets] Re: [libburn] #75: cdrskin does not work properly with address 1, 1, 0   libburn
  • [Libburn-tickets] Re: [libburn] #75: cdrskin does not work properly with address 1, 1, 0   libburn
• [Libburn-tickets] [libburn] #76: cdrskin compilation broken. I suspect a recent change of configure.ac.   libburn
  • [Libburn-tickets] Re: [libburn] #76: cdrskin compilation broken. I suspect a recent change of configure.ac.   libburn
  • [Libburn-tickets] Re: [libburn] #76: cdrskin compilation broken. I suspect a recent change of configure.ac.   libburn
  • [Libburn-tickets] Re: [libburn] #76: cdrskin compilation broken. I suspect a recent change of configure.ac.   libburn
  • [Libburn-tickets] Re: [libburn] #76: cdrskin compilation broken. I suspect a recent change of configure.ac.   libburn
  • [Libburn-tickets] Re: [libburn] #76: cdrskin compilation broken.   libburn
  • [Libburn-tickets] Re: [libburn] #76: cdrskin compilation broken.   libburn
  • [Libburn-tickets] Re: [libburn] #76: cdrskin compilation broken.   libburn
  • [Libburn-tickets] Re: [libburn] #76: cdrskin compilation broken.   libburn
• [Libburn-tickets] [libburn] #77: Is this Diva or libburn/cdrskin site?   libburn
  • [Libburn-tickets] Re: [libburn] #77: Is this Diva or libburn/cdrskin site?   libburn
• [Libburn-tickets] Re: [libburn] #33: Follow symbolic links in /dev   libburn
• [Libburn-tickets] Re: [libburn] #33: Follow symbolic links in /dev   libburn
• [Libburn-tickets] Re: [libburn] #33: Follow symbolic links in /dev   libburn
• [Libburn-tickets] Re: [libburn] #33: Follow symbolic links in /dev   libburn
• [Libburn-tickets] Re: [libburn] #33: Follow symbolic links in /dev   libburn
• [Libburn-tickets] Re: [libburn] #33: Follow symbolic links in /dev   libburn
• [Libburn-tickets] Re: [libburn] #11: Wish: A call to reset a drive   libburn
• [Libburn-tickets] Re: [libburn] #33: Follow symbolic links in /dev   libburn
• [Libburn-tickets] Re: [libburn] #4: Better Error Handling   libburn
• [Libburn-tickets] Re: [libburn] #33: Follow symbolic links in /dev   libburn
• [Libburn-tickets] Re: [libburn] #33: Follow symbolic links in /dev   libburn
• [Libburn-tickets] Re: [libburn] #33: Follow symbolic links in /dev   libburn
• [Libburn-tickets] Re: [libburn] #33: Follow symbolic links in /dev   libburn
• [Libburn-tickets] Re: [libburn] #33: Follow symbolic links in /dev   libburn
• [Libburn-tickets] Re: [libburn] #33: Follow symbolic links in /dev   libburn
• [Libburn-tickets] Re: [libburn] #33: Follow symbolic links in /dev   libburn
• [Libburn-tickets] Re: [libburn] #33: Follow symbolic links in /dev   libburn
• [Libburn-tickets] Re: [libburn] #33: Follow symbolic links in /dev   libburn
• [Libburn-tickets] Re: [libburn] #33: Follow symbolic links in /dev   libburn
• [Libburn-tickets] Re: [libburn] #33: Follow symbolic links in /dev   libburn
• [Libburn-tickets] Re: [libburn] #33: Follow symbolic links in /dev   libburn
• [Libburn-tickets] Re: [libburn] #33: Follow symbolic links in /dev   libburn
• [Libburn-tickets] Re: [libburn] #33: Follow symbolic links in /dev   libburn
• [Libburn-tickets] Re: [libburn] #1: Change Lead-In Addressing   libburn
• [Libburn-tickets] Re: [libburn] #26: El-torito support   libburn
• [Libburn-tickets] [libburn] #78: Protect dvd+rw-tools and libburn from spoiling each other on kernel 2.4   libburn
  • [Libburn-tickets] Re: [libburn] #78: Protect dvd+rw-tools and libburn from spoiling each other on kernel 2.4   libburn

Last message date: Sat Sep 30 10:51:48 CST 2006
Archived on: Sat Sep 30 10:51:50 CST 2006

• Messages sorted by: [ subject ] [ author ] [ date ]
• More info on this list...