I was wondering if anyone could shed some light on the
philosophy behind duplicating Volume Descriptors on a
single CDROM ? (I refer to exact copies, not one or
more Supplementary Volume Descriptors that each provide
their own hierarchy with possibly different character
sets and possibly the same
I have a nominally ISO9660 CDROM that has a well-formed
SUSP System Use area associated with the first entry in
the Root Directory. System Use entries are:
SP
RR
PX
TF
CE
I find SP and CE in the SUSP Draft Standard Version 1.12.
I find PX and TF in the Rock Ridge Draft
[EMAIL PROTECTED] (Glenn Sieb) quoted and then wrote:
>On 01:01 AM 4/3/2002 +0200, Joerg Schilling wrote:
>>the current mkisofs & cdrecord-ProDVD should give you all you need for
>>Video DVDs. What is your problem?
>
>No no no :) Not his problem.. mine.. and it's not Video DVDs I'm having
>probl
[EMAIL PROTECTED] (James Pearson) quoted and then wrote:
>>>I believe RR was in early RRIP specs, but it was not mandatory and
>>>later dropped. Looking at the Linux source code, I think it's a bit
>>>flag that defines what other Rock Ridge fields are present.
>>
>>As with many CD related informa
[EMAIL PROTECTED] (James Pearson) quoted and then wrote:
>>>From searching the web, the most 'recent' version of the "Rock Ridge
>>>Interchange Protocol, version 1" is rev 1.12, however the 'RR' field
>>>was described in revisions up to 1.09 - see:
>>>
>>>http://groups.google.com/groups?hl=en&th=
[EMAIL PROTECTED] quoted and then wrote:
>>From: Matthias Schniedermeyer <[EMAIL PROTECTED]>
>>Yesterday i lost a 2,3 GB big file because mkisofs "silently" skipped it.
>
>>mkisofs ... $dir && rm -rf $dir
>
>>I had the luck that i can reget that file. But next time it's possibel
>>that i'm not s
[EMAIL PROTECTED] quoted and then wrote:
>>From: [EMAIL PROTECTED]
>
>>>mkisofs definitey does not skip those files silently!
>>>
>>>It prints: "File %s is too large - ignoring\n"
>>>
>>>It is not possible to put files > 2 GB into a ISO-9660 fs.
>
>>Presumably this is just a limit of the mkisofs
[EMAIL PROTECTED] quoted and then wrote:
>>From: [EMAIL PROTECTED]
>
>...
ISO 9660 : 1988 (E) 6.8.1 says that a Directory shall consist
of only one File Section. Given that limit of 4GB on the size
of any File Section (and thus a Directory) assuming a Directory
Record size of 64
[EMAIL PROTECTED] quoted and then wrote:
>From: [EMAIL PROTECTED] (Joerg Schilling)
>To:[EMAIL PROTECTED], [EMAIL PROTECTED]
>>From: [EMAIL PROTECTED]
>
>
>Looks like you like to make your own standard...
>>>
Sorry, I don't understand that comment.
>>>
If my understanding of ISO
[EMAIL PROTECTED] quoted and then wrote:
>I found a CD that looks a bit strange.
>
>Is there anybody who really knows Joliet and can help?
>
>The SVD of the CD contains escape sequences that I would call buggy:
>
>The first bytes are: 0: '%' 1: '/' 2: 'E' 3: ' '
I would say that %/E is correct f
[EMAIL PROTECTED] (James Pearson) quoted and then wrote:
>>I found a CD that looks a bit strange.
>>
>>Is there anybody who really knows Joliet and can help?
>>
>>The SVD of the CD contains escape sequences that I would call buggy:
>>
>>The first bytes are: 0: '%' 1: '/' 2: 'E' 3: ' '
>
>Certainl
So far as I know, the ISO 9660 Logical Sector Size
on CDROM is always 2048 bytes. While it would be
possible to comply with ISO 9660 using some larger
Logical Sector Size, it would require out-of-band
indications of this deviation from the norm. I had
guessed that the choice of 2048 for the Logic
[EMAIL PROTECTED] quoted and then wrote:
>From: [EMAIL PROTECTED] (Pierre Duhem)
>Reply-to: [EMAIL PROTECTED] (Pierre Duhem)
>To:[EMAIL PROTECTED], [EMAIL PROTECTED] (Mike Fox Morrey)
>Mike,
>
>MFM> Since DVD-Rs have UDF (extensions?|Along with ISO9660?) on them
>MFM> as well, I'm assumin
[EMAIL PROTECTED] (Chris Lawrence) quoted and then wrote:
>On Sep 19, James Pearson wrote:
>> However, there are probably limits in my code (and/or libhfs) that means
>> 2Gb is the maximum.
>
>Indeed; I encountered a similar problem building PowerPC DVDs and
>found that it misbehaved due to the 2
[EMAIL PROTECTED] (Meino Christian Cramer) quoted and then wrote:
> what I heard one time was, that if burnfree is triggered by a buffer
> underrun (which cause the laser beam to pause), a small (very small)
> gap is produced after the beam is switched on afterwards.
>
> A "master" produced that
[EMAIL PROTECTED] (Matthias Schniedermeyer) quoted and then wrote:
>From:
>To:[EMAIL PROTECTED] (Frank Hage)
>CC:[EMAIL PROTECTED]
>On Mon, Nov 04, 2002 at 11:49:47AM -0700, Frank Hage wrote:
>> On 2002.11.04, Joerg Schilling wrote:
>> :
>> :
>> : But DVD-* media is cheaper and I see n
[EMAIL PROTECTED] wrote:
>After the disk is written, I can mount the disk from Linux
>(2.2.25, glibc 2.2.5) in iso9660 mode. However, for files that
>originally have a Apple resource fork (from Netatalk), it seems
>that the resource fork instead of the data fork is visible to
>Linux. Stranger stil
[EMAIL PROTECTED] (Ambrose Li) quoted and then wrote:
>If I use the "unhide" mount option in /etc/fstab, Linux will pick up
>the resource forks (probably because they have the same filenames as
>the corresponding data forks) instead of the data forks, causing
>the corruption. The corruption st
[EMAIL PROTECTED] (Ambrose Li) quoted and then wrote:
>On Fri, Jun 27, 2003 at 11:40:59PM -0400, Rob Bogus wrote:
>
>> The user deliberately selected an option to make those forks
>> visible. Linux doesn't (deliberately) make things dificult,
>> it just makes the default safe in most cases, and a
[EMAIL PROTECTED] (Joerg Schilling) quoted and then wrote:
>>From: [EMAIL PROTECTED]
>>The ISO 9660 bit specifies that the very first extent is the
>>resource fork. The Linux option makes that first extent separately
>>visible. What effect does not Linux option have on the _other_
>>extents th
[EMAIL PROTECTED] (Andy Polyakov) quoted and then wrote:
>> >>When I invoked growisofs as follows: growisofs -Z /dev/cdrom -R -J
>> >>-dvd-compat and the overburn protection kicked in, it still wrote data
>> >>to the DVD+R.
>>
>> Here's what happens when I run it on the 4.3 GB file, which you cla
[EMAIL PROTECTED] (Andy Polyakov) quoted and then wrote:
>As for "...only if you need to have your files read on a Linux system."
>ISO9660 is about data interchange, isn't it? You don't know in advance
>where it will have to be read and therefore want your recordings to be
>normalized to some leas
At 1:53 PM -0400 8/20/03, Mike Fox Morrey wrote:
Can someone point me (or, if they're generous, give me a
quick explanation here..) to, specifically, filenames in ISO9660?
I noticed that if I do an "--iso-level 3" in my command line
(possibly others, but haven't checked.), my file
At 9:15 PM -0700 9/6/03, Thomas Zimmerman wrote:
>I've got an CDR that has gone bad (no superblock or too many filesystems
>mounted, when I try and mount it). I can always try and get a bit copy
>with dd, but wonder if there is a fsck.iso9660 about that might be able
>to save any files from the cdr
At 10:44 PM +0200 10/17/03, A.P.Munnikes wrote:
>1. Is it, or is is not, possibele to make a good/working/official image that is >
>4GB. (just with a lot of files with a size from 1 KB to a max. of 100MB, so not the
>problem about that the iso9660 can not contains a file > 2GB)
ISO9660 certainl
At 5:27 PM + 11/2/03, Gary Houston wrote:
>I have been using dvd+rw-tools (5.13.4.7.4) and mkisofs (cdrtools 1.11a29)
>to write backups to DVD. This generally works. However I encountered
>a problem when one of the files was 2351679431 bytes in size: the disk
>was written with no errors repor
At 8:48 PM +0100 11/2/03, Lourens Veen wrote:
>On Sun 2 November 2003 19:03, ljknews wrote:
>> At 5:27 PM + 11/2/03, Gary Houston wrote:
>> >I have been using dvd+rw-tools (5.13.4.7.4) and mkisofs
>> > (cdrtools 1.11a29) to write backups to DVD. This gener
At 1:50 PM +0100 11/3/03, Joerg Schilling wrote:
> >From: Volker Kuhlmann <[EMAIL PROTECTED]>
>
>>> But can a file span multiple extents? The way I read the comment
>>> Gary quoted, it's legal to have an image that is over 2GB in size,
>>> as long as each file inside that image is no larger than 2G
At 2:05 PM +0100 11/4/03, Joerg Schilling wrote:
> >From: ljknews <[EMAIL PROTECTED]>
>
>>>It is hard to implement things in mkisofs that cannot be tested.
>
>>Well such a resulting volume could certainly be tested, but I understand
>>that *IX develope
At 6:22 PM -0500 1/2/04, Bob Lockie wrote:
>I'm trying to backup stuff and I ran into this problem with mkisofs.
>
>$ mkisofs --version
>mkisofs 2.0.3 (i686-pc-linux-gnu)
>
>/opt/schily/bin/mkisofs: Directories too deep for
>'/home/rjl/20031231_d2/home/rjl/www_staging/lockieca_rjl/cars/Sentra/_vti_
At 11:36 PM + 1/2/04, Steve McIntyre wrote:
>On Fri, Jan 02, 2004 at 06:22:47PM -0500, Bob Lockie wrote:
>>I'm trying to backup stuff and I ran into this problem with mkisofs.
>>
>>$ mkisofs --version
>>mkisofs 2.0.3 (i686-pc-linux-gnu)
>>
>>/opt/schily/bin/mkisofs: Directories too deep for
>>'
At 10:06 PM +0530 10/20/04, _N4R3N_ wrote:
>hi
>
>
>I want to split a directory in to two sub directories
>
>If my home dir is 1000 Mb I can't write it completely on one cd
>
>So i want to split it in to two directories namely
>
>1)naren.bak.1
>2)naren.bak.2
>
>so that my /home/naren directory will
At 9:15 PM -0700 9/6/03, Thomas Zimmerman wrote:
>I've got an CDR that has gone bad (no superblock or too many filesystems
>mounted, when I try and mount it). I can always try and get a bit copy
>with dd, but wonder if there is a fsck.iso9660 about that might be able
>to save any files from the cdr
At 10:44 PM +0200 10/17/03, A.P.Munnikes wrote:
>1. Is it, or is is not, possibele to make a good/working/official image that
>is > 4GB. (just with a lot of files with a size from 1 KB to a max. of 100MB,
>so not the problem about that the iso9660 can not contains a file > 2GB)
ISO9660 certainl
At 5:27 PM + 11/2/03, Gary Houston wrote:
>I have been using dvd+rw-tools (5.13.4.7.4) and mkisofs (cdrtools 1.11a29)
>to write backups to DVD. This generally works. However I encountered
>a problem when one of the files was 2351679431 bytes in size: the disk
>was written with no errors repor
At 8:48 PM +0100 11/2/03, Lourens Veen wrote:
>On Sun 2 November 2003 19:03, ljknews wrote:
>> At 5:27 PM + 11/2/03, Gary Houston wrote:
>> >I have been using dvd+rw-tools (5.13.4.7.4) and mkisofs
>> > (cdrtools 1.11a29) to write backups to DVD. This gener
At 1:50 PM +0100 11/3/03, Joerg Schilling wrote:
> >From: Volker Kuhlmann <[EMAIL PROTECTED]>
>
>>> But can a file span multiple extents? The way I read the comment
>>> Gary quoted, it's legal to have an image that is over 2GB in size,
>>> as long as each file inside that image is no larger than 2G
At 2:05 PM +0100 11/4/03, Joerg Schilling wrote:
> >From: ljknews <[EMAIL PROTECTED]>
>
>>>It is hard to implement things in mkisofs that cannot be tested.
>
>>Well such a resulting volume could certainly be tested, but I understand
>>that *IX develope
At 6:22 PM -0500 1/2/04, Bob Lockie wrote:
>I'm trying to backup stuff and I ran into this problem with mkisofs.
>
>$ mkisofs --version
>mkisofs 2.0.3 (i686-pc-linux-gnu)
>
>/opt/schily/bin/mkisofs: Directories too deep for
>'/home/rjl/20031231_d2/home/rjl/www_staging/lockieca_rjl/cars/Sentra/_vti_
At 11:36 PM + 1/2/04, Steve McIntyre wrote:
>On Fri, Jan 02, 2004 at 06:22:47PM -0500, Bob Lockie wrote:
>>I'm trying to backup stuff and I ran into this problem with mkisofs.
>>
>>$ mkisofs --version
>>mkisofs 2.0.3 (i686-pc-linux-gnu)
>>
>>/opt/schily/bin/mkisofs: Directories too deep for
>>'
40 matches
Mail list logo
