-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 El 2009-03-30 a las 00:06 +0200, Camaleón escribió:
Son 4.2G, y lo máximo que admite un dvd ISO son 2 gigas por archivo.
tienes el mpgsplit que hace eso
Hum... me parece que el k3b permite usar las extensiones de nivel 3 del formato iso 9660 para archivos mayores de 4 GB, lo que ya no sé es la compatibilidad del dvd resultante con otros sistemas operativos :-?
Cierto, lo acabo de probar. De hecho, el k3b lo hace automáticamente, dice algo como que "activando extensiones udf", y advierte que necesitará un kernel con ese aditivo. Lo he podido montar sin problemas en suse, aparte de unos cuantos "chilllidos" en el log: kernel: cdrom: This disc doesn't have any tracks I recognize! kernel: hdc: UDMA/33 mode selected kernel: UDF-fs DEBUG fs/udf/lowlevel.c:43:udf_get_last_session: XA disk: no, vol_desc_start=0 kernel: UDF-fs DEBUG fs/udf/super.c:1920:udf_fill_super: Multi-session=0 kernel: UDF-fs DEBUG fs/udf/super.c:613:udf_vrs: Starting at sector 16 (2048 byte sectors) kernel: UDF-fs DEBUG fs/udf/super.c:637:udf_vrs: ISO9660 Primary Volume Descriptor found kernel: UDF-fs DEBUG fs/udf/super.c:641:udf_vrs: ISO9660 Supplementary Volume Descriptor found kernel: UDF-fs DEBUG fs/udf/super.c:649:udf_vrs: ISO9660 Volume Descriptor Set Terminator found kernel: UDF-fs DEBUG fs/udf/super.c:935:udf_load_pvoldesc: recording time 2009/03/29 18:05 (1078) kernel: UDF-fs DEBUG fs/udf/super.c:944:udf_load_pvoldesc: volIdent[] = 'La Milla Verde' kernel: UDF-fs DEBUG fs/udf/super.c:949:udf_load_pvoldesc: volSetIdent[] = '49CF9C2E00002710' kernel: UDF-fs DEBUG fs/udf/super.c:1481:udf_load_logicalvol: Partition (0:0) type 1 on volume 1 kernel: UDF-fs DEBUG fs/udf/super.c:1490:udf_load_logicalvol: FileSet found in LogicalVolDesc at block=0, partition=0 kernel: UDF-fs DEBUG fs/udf/super.c:1271:udf_load_partdesc: Searching map: (0 == 0) kernel: UDF-fs DEBUG fs/udf/super.c:1125:udf_fill_partdesc_info: Partition (0 type 1511) starts at physical 257, block length 2171120 kernel: UDF-fs DEBUG fs/udf/super.c:1745:udf_load_sequence: Using anchor in block 256 kernel: UDF-fs DEBUG fs/udf/super.c:1946:udf_fill_super: Lastblock=1151848 kernel: UDF-fs: Partition marked readonly; forcing readonly mount kernel: UDF-fs DEBUG fs/udf/super.c:903:udf_find_fileset: Fileset at block=0, partition=0 kernel: UDF-fs DEBUG fs/udf/super.c:1062:udf_load_fileset: Rootdir at block=2, partition=0 kernel: UDF-fs INFO UDF: Mounting volume 'La Milla Verde', timestamp 2009/03/29 17:05 (103c) kernel: UDF-fs DEBUG fs/udf/super.c:1271:udf_load_partdesc: Searching map: (0 == 0) kernel: UDF-fs DEBUG fs/udf/super.c:1125:udf_fill_partdesc_info: Partition (0 type 1511) starts at physical 257, block length 2171120 kernel: UDF-fs DEBUG fs/udf/super.c:1745:udf_load_sequence: Using anchor in block 256 kernel: UDF-fs DEBUG fs/udf/super.c:1946:udf_fill_super: Lastblock=1151848 kernel: UDF-fs: Partition marked readonly; forcing readonly mount kernel: UDF-fs DEBUG fs/udf/super.c:903:udf_find_fileset: Fileset at block=0, partition=0 kernel: UDF-fs DEBUG fs/udf/super.c:1062:udf_load_fileset: Rootdir at block=2, partition=0 kernel: UDF-fs INFO UDF: Mounting volume 'La Milla Verde', timestamp 2009/03/29 17:05 (103c) Ya probaré si el windows lo lee cuando venga algún amigo con un portatil con windows. De momento, me vale. Si puedo grabar los archivos enteros así, me ahorro tener que decirle al "xine" que cargue una colección de archivos, pero por otra parte, si sobra un trozo en el dvd, no lo puedo aprovechar con un trozo de otra peli. Pero como tengo una tarrina de dvds de segunda calidad (*), los aprovecharé. (*) Según http://www.digitalfaq.com/reviews/dvd-media.htm Ah, espera, ¿dices extensiones de nivel 3? Eso es otra cosa. Voy a mirar. [...] Vale, si activas esas extensiones, y desactivas las de udf, al crear la imagen vuelve a reactivar las extensiones udf de manera automática. No sirven, parece. A ver que dice la wikipedia... http://en.wikipedia.org/wiki/ISO_9660 # Level 3: Files are allowed to be non-contiguous (i.e., fragmented), principally to allow packet writing or incremental CD recording). ... The 4 GiB (or 2 GiB depending on implementation) file size limit All numbers in ISO 9660 file systems except the single byte value used for the GMT offset are unsigned numbers. As the length of a file's extent on disk is stored in a 32 bit value[3], it allows for a maximum length of 4 GiB. (Note: Some older operating systems may handle such values incorrectly (i.e., signed instead of unsigned), which would make it impossible to access files larger than 2 GiB in size.) Based on this, it is often assumed that a file on an ISO 9660 formatted disc cannot be larger than 232-1 in size, as the file's size is stored in an unsigned 32 bit value, for which 232-1 is the maximum. It is, however, possible to circumvent this limitation by using the multi-extent (fragmentation) feature of ISO 9660 Level 3. With this, files larger than 4 GiB can be split up into multiple extents (sequential series of sectors), each not exceeding the 4 GiB limit. For example, the free software such as infrarecorder and mkisofs as well as Roxio Toast are able to create ISO 9660 filesystems that use multi-extent files to store files larger than 4 GiB on appropriate media such as recordable DVDs. Empirical tests with a 4.2 GiB fragmented file on a DVD media have shown that Microsoft Windows XP supports this, while Mac OS X (as of 10.4.8) does not handle this case properly. In the case of Mac OS X, the driver appears not to support file fragmentation at all (i.e. it only supports ISO 9660 Level 2 but not Level 3). Linux supports multiple extents.[4] FreeBSD only shows and reads the last extent of a multi-extent file.[citation needed] Pues te dan la razón... pero no funciona. Habrá que investigarlo. - -- Saludos Carlos E.R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAknP/2IACgkQtTMYHG2NR9Ub2gCfU1Tk/nMraeCb8v65ZJ/LW45t B4MAn2EclHHlefHvD/httPDS5FsAExqT =MExZ -----END PGP SIGNATURE-----