Prev: black screen
Next: Snow Leopard upgrade experience
From: Alex Miller on 8 Nov 2009 20:49
On Nov 7, 8:01 am, j...(a)cs.tu-berlin.de (Joerg Schilling) wrote:
> In article <eadaa1ce-191d-45ec-a48f-2e2b76d3f...(a)u25g2000prh.googlegroups..com>,
> Alex Miller  <alex.etc.mil...(a)gmail.com> wrote:
>
> >Debian 4 and OS X 10.6 indeed have problems reading those big files.
> >Debian sees about 300MB of it. However, Ubuntu 8.04 can read the file
> >fine, so it's definitely on the file system. The mkisofs used to
> >create the image was from Ubuntu 8.04 as well.
>
> With the command line you showed, it is impossible that you have the file
> on the medium (in a usable way) as the fork does not support files >= 4GB.
>
> BTW: Ubuntu has no mkisofs but the broken fork.
>
> Note that the fork does not include the whole file in a usable form.
> The option "-allow-limited-size" which is only in the defective fork
> is an option to allow broken data on the filesystem. The size you see
> in this case is typically the real file size modulo 2 GB or 4 GB.
>
> Also note that it is impossible to code a numer > 4 GB in 32 bits.
> To allow larger files, there needs to be more than one directory entry
> for the file and this is what the fork cannot do.
>
> A working mkisofs in part of the cdrtools package:
>
> ftp://ftp.berlios.de/pub/cdrecord/alpha/
>

All I can say is that I haven't noticed any breakage if the files are
read in Ubuntu, and I examined several of these cases. Are you sure
the Ubuntu fork didn't implement the functionality in some way?

If you'd like to reproduce the (surprising?) behavior, you may want to
install Ubuntu 8.04 with latest updates (easy in a VM), make an ISO
image from a 4.3GB file, following my recipe, and see if you get the
same file back after mounting the ISO.

Followup to a Linux group set (I don't read it, but we are getting OT
here).
First  |  Prev  | 
Pages: 1 2
Prev: black screen
Next: Snow Leopard upgrade experience