On Thu, 2005-03-10 at 15:37 +0100, Maciej ?enczykowski wrote:
> Option (a) can be performed immediately by just adding a single line
> (dd if=/dev/zero bs=2048 count=150 >> file.iso) to the scripts used to
> create the iso/dvd images right after the anaconda implantation.
>
But this is a problem with cdrecord and not with iso generation. How
does this solution impact people who do not use cdrecord to make ISOs.
There are many people who burn the ISOs with other programs (growfs,
nero, roxio ezcd, and a dozen other windows or mac ISO recording
programs.)
I'm not sure that we should put the extra items on the end of the file
if it will adversely impact the other burning programs.
Any comments...
> Option (b) is nice and should probably be done anyway (making -pad
> cdrecord option the default) but will take ages to spread and in the
> meantime cd burning problems will continue to plague us.
>
This option only impacts the user that uses cdrecord and doesn't impact
other burning software.
> Option (c) is also nice and should possibly be done, once we figure out
> how to determine how much padding the file contains (or just assume it's
> always 300KB since that's how much mkisofs adds?)
>
> Still, option (a) is best for now at least and would solve this problem
> once and for all.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://lists.caosity.org/pipermail/centos/attachments/20050310/22e321d2/attachment-0001.bin
