Re: ISO9660 file naming (limits)
On Tue, 6 Jan 2004 11:17:43 -0500 Derrick 'dman' Hudson wrote: > On Tue, Jan 06, 2004 at 12:41:23PM +, Carlos Sousa wrote: > ... The only anomaly it produces is a visible (and -apparently- empty) > 'rr_moved' directory. > | > |mkisofs -r -D -L -l -graft-points -J -joliet-long -jcharset default ... > | The -D option will make that directory go away, as a side effect ;) -- Carlos Sousa http://vbc.dyndns.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: ISO9660 file naming (limits)
Incoming from Derrick 'dman' Hudson: > On Mon, Jan 05, 2004 at 09:32:21PM -0700, Paul E Condon wrote: > | > | Why don't you avoid problem by using tar on reasonably sized chunks of > | the file tree, and name the tar files concisely? > > I'd rather not have a cd full of tar files since I'm not cramped for > space. It is much more convenient to be able to put the cd in and Even if you have lots of disk, you may be cramped for getting all your data onto a CD. Then, if you've compressed your data into an archive and burned the archive to CD, you can get individual files/dirs out of the archive by just naming them: cd /lots_of_space tar xzf /cdrom/tararchive.tgz what_you_want_to_get_back -- Any technology distinguishable from magic is insufficiently advanced. (*) http://www.spots.ab.ca/~keeling - - -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: ISO9660 file naming (limits)
On Tue, Jan 06, 2004 at 12:41:23PM +, Carlos Sousa wrote:
| On Mon, 5 Jan 2004 23:12:16 -0500 Derrick 'dman' Hudson wrote:
| > I want to make a cd archive of my (past) school work and remove it
| > from my hard drive. The problem lies in name/path length limits for
| > ISO9660 filesystems. 'mkisofs -R -J' yields output such as
| > Using FINDR000.HH;1 for
./SE1-Software_Engineering.3010-361/src/FindRoomWindow.hh (FindRoomWindow_glade.hh)
| > Using FINDR000.CC;1 for
./SE1-Software_Engineering.3010-361/src/FindRoomWindow_glade.cc (FindRoomWindow.cc)
| > When I loopback mount the ISO to inspect it, the file apears normal
| > with the complete path and name.
| >
| > My question is, what does the output from mkisofs mean, and will the
| > CD have all of the files correctly named?
|
| I've had that problem, especially for files in Windows partitions.
| It probably means mkisofs is renaming the files to conform to specs,
| and building the necessary filename translation tables.
That's what I thought it might be too.
| As far as I can tell, the renaming won't be visible to the user and
| all files will be available to the system with their original names.
This is good. I wanted confirmation on that. The only anomaly it
produces is a visible (and -apparently- empty) 'rr_moved' directory.
I think that's where mkisofs maps the "sanitized" names to. One thing
I was afraid of was losing some filename information and needing to
manually work out the original names if I want to recover the data.
| The command I use is different, though:
|
|mkisofs -r -D -L -l -graft-points -J -joliet-long -jcharset default ...
|
| This makes it produce non-strictly-conforming CD images, but will handle
| much deeper directories and longer filenames. Both Linux and Windows seem
| to read such CDs correctly.
|
| I've been using that for my backups for years with no problems, all files
| are correctly shown both under Linux and Windows.
Ok. The -r option produces less of the "Using foo for bar" messages.
Probably because with 31 instead of 8.3 characters per name fewer
files need renaming. (Who ever thought 8.3 was a good limit for cds?
I can't fathom such shortsighted limits.)
Thanks,
-D
--
\begin{humor}
Disclaimer:
If I receive a message from you, you are agreeing that:
1. I am by definition, "the intended recipient"
2. All information in the email is mine to do with as I see fit and make
such financial profit, political mileage, or good joke as it lends
itself to. In particular, I may quote it on USENET or the WWW.
3. I may take the contents as representing the views of your company.
4. This overrides any disclaimer or statement of confidentiality that may
be included on your message
\end{humor}
www: http://dman13.dyndns.org/~dman/jabber: [EMAIL PROTECTED]
signature.asc
Description: Digital signature
Re: ISO9660 file naming (limits)
On Mon, Jan 05, 2004 at 09:32:21PM -0700, Paul E Condon wrote: | On Mon, Jan 05, 2004 at 11:12:16PM -0500, Derrick 'dman' Hudson wrote: | > I want to make a cd archive of my (past) school work and remove it | > from my hard drive. The problem lies in name/path length limits for | > ISO9660 filesystems. 'mkisofs -R -J' yields output such as | > Using FINDR000.HH;1 for ./SE1-Software_Engineering.3010-361/src/FindRoomWindow.hh (FindRoomWindow_glade.hh) | > Using FINDR000.CC;1 for ./SE1-Software_Engineering.3010-361/src/FindRoomWindow_glade.cc (FindRoomWindow.cc) | > When I loopback mount the ISO to inspect it, the file apears normal | > with the complete path and name. | > | > My question is, what does the output from mkisofs mean, and will the | > CD have all of the files correctly named? | | Why don't you avoid problem by using tar on reasonably sized chunks of | the file tree, and name the tar files concisely? I'd rather not have a cd full of tar files since I'm not cramped for space. It is much more convenient to be able to put the cd in and read over some code or some-such than it is to need extra disk space in which to untar the data, look at it, then delete it again. -D -- mailhost:/etc/mail# less sendmail.cf less: syntax of file "sendmail.cf" may induce nausea, show anyway? [n] www: http://dman13.dyndns.org/~dman/jabber: [EMAIL PROTECTED] signature.asc Description: Digital signature
Re: ISO9660 file naming (limits)
On Mon, 5 Jan 2004 23:12:16 -0500 Derrick 'dman' Hudson wrote: > I want to make a cd archive of my (past) school work and remove it > from my hard drive. The problem lies in name/path length limits for > ISO9660 filesystems. 'mkisofs -R -J' yields output such as > Using FINDR000.HH;1 for > ./SE1-Software_Engineering.3010-361/src/FindRoomWindow.hh (FindRoomWindow_glade.hh) > Using FINDR000.CC;1 for > ./SE1-Software_Engineering.3010-361/src/FindRoomWindow_glade.cc (FindRoomWindow.cc) > When I loopback mount the ISO to inspect it, the file apears normal > with the complete path and name. > > My question is, what does the output from mkisofs mean, and will the > CD have all of the files correctly named? I've had that problem, especially for files in Windows partitions. It probably means mkisofs is renaming the files to conform to specs, and building the necessary filename translation tables. As far as I can tell, the renaming won't be visible to the user and all files will be available to the system with their original names. The command I use is different, though: mkisofs -r -D -L -l -graft-points -J -joliet-long -jcharset default ... This makes it produce non-strictly-conforming CD images, but will handle much deeper directories and longer filenames. Both Linux and Windows seem to read such CDs correctly. I've been using that for my backups for years with no problems, all files are correctly shown both under Linux and Windows. HTH, -- Carlos Sousa http://vbc.dyndns.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: ISO9660 file naming (limits)
On Mon, Jan 05, 2004 at 11:12:16PM -0500, Derrick 'dman' Hudson wrote: > I want to make a cd archive of my (past) school work and remove it > from my hard drive. The problem lies in name/path length limits for > ISO9660 filesystems. 'mkisofs -R -J' yields output such as > Using FINDR000.HH;1 for > ./SE1-Software_Engineering.3010-361/src/FindRoomWindow.hh (FindRoomWindow_glade.hh) > Using FINDR000.CC;1 for > ./SE1-Software_Engineering.3010-361/src/FindRoomWindow_glade.cc (FindRoomWindow.cc) > When I loopback mount the ISO to inspect it, the file apears normal > with the complete path and name. > > My question is, what does the output from mkisofs mean, and will the > CD have all of the files correctly named? > Why don't you avoid problem by using tar on reasonably sized chunks of the file tree, and name the tar files concisely? -- Paul E Condon [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
ISO9660 file naming (limits)
I want to make a cd archive of my (past) school work and remove it from my hard drive. The problem lies in name/path length limits for ISO9660 filesystems. 'mkisofs -R -J' yields output such as Using FINDR000.HH;1 for ./SE1-Software_Engineering.3010-361/src/FindRoomWindow.hh (FindRoomWindow_glade.hh) Using FINDR000.CC;1 for ./SE1-Software_Engineering.3010-361/src/FindRoomWindow_glade.cc (FindRoomWindow.cc) When I loopback mount the ISO to inspect it, the file apears normal with the complete path and name. My question is, what does the output from mkisofs mean, and will the CD have all of the files correctly named? TIA, -D -- Folly delights a man who lacks judgement, but a man of understanding keeps a straight course. Proverbs 15:21 www: http://dman13.dyndns.org/~dman/jabber: [EMAIL PROTECTED] signature.asc Description: Digital signature
