Comments for cdrtools
[wish] support for large files
So far I can burn exactly 4GB file (one file = 4GB) on
DVD (using k3b as GUI frontend), however it would be
good to see support for larger files so I could fit one
file which would occupy the whole disc.
Any plans in supporting really :-) large files?
thank you for great tool!
Re: There is a better option these days.
Debian's software, like libburn, is under constant development. They're also truly Free software packages. Furthermore, they're not in Sun's pocket, so they actually work right under linux.
The parent post is typical Jörg FUD; prospective users, please try both and judge for yourself.
Re: There is a better option these days.
I recommend you to inform yourself before writing.
The software distributed by Debian is only
to fool users :-(
There is no development at the Debian variant
except for introducing new bugs. The original
software on the other side is constantly under developement.
Cdrtools is still the best solution and all
people who reported problems with debians
destroyed version were happy after the did
go back to the original.
Re: There is a better option these days.
And here's another alternative:
libburnia.pykix.org/
It works great and I had no probs with it.. It still lacks it's own iso genarting app but other than that should be good enough for day-to-day use...
There is a better option these days.
Oh, look. Jörg is calling linux "broken" again. Raise your hand if you're surprised.
For those of you who don't think one CD burning application is worth altering the entire linux drive addressing system, there is a better option. It's called "cdrkit" and it's a fork of cdrecord from before Jörg screwed the license up. It's being run by some debian devs, but I can attest it works on slackware too.
The freshmeat entry for cdrkit is here:
freshmeat.net/projects... (freshmeat.net/projects...)
and the project home page is
Re: More info about CDR99
> I wrote Jörg for more details about
> CDR99.
>
> He received samples a few weeks ago.
> They have an
> ATIP of:
>
>
> ATIP info from disk:
> Indicated writing power: 4
> Is not unrestricted
> Is not erasable
> ATIP start of lead in: -10981
> (97:35/44)
> ATIP start of lead out: 359849
> (79:59/74)
> Disk type: unknown
> Manuf. index: 0
> Manufacturer: Unknown old Manufacturer
> code
>
> The expected retail price will be below
> $2USD (4DM).
>
> He wasn't sure if they will be supported
> by most readers.
> They definately will require special
> writers because they
> are not Red Book Compliant.
>
> His plans:
> "I hope to be able to write a RAW
> mode CD with a self made TOC in a few
> days. I then will be able to do test
> with read compatibility.
>
> Write compatibility will take another
> set of tests...."
>
> Thanks Jörg!
>
> Evelyn
>
It's outdated now, but the project remains a mark.
Re: cdrecord: No target found.
Right you are. I've good luck with Nero as well.
Have a nice Time
Buring
A [relatively] recent feature in cdrtools (in mkisofs) enables it to detect file changes while burning 'on-the-fly' and quits the burn.
I.e. with a command such as:
mkisofs /files | cdrecord -options -
It errors with something like:
mkisofs: File '/so/and/so' did grow
I've looked at both manuals and couldn't find a way to turn this off.
Is there a hidden flag of some sort or some way to counter this?
Re: Never use this software directly but get a patched version from a major distribution
If you read these comments and don't know what the fuss is about you might want to read this article first (lwn.net/Articles/97469/). Tom (www.couol.com/)
Re: [wish] support for large files
You may have luck with genisoimage, see cdrkit package. The isofs representation remains broken (file size displayed is the modulo 4GB residual) but the UDF part should work well with large files.