mkisofs behaviour with respect to parent directories

mkisofs behaviour with respect to parent directories

Post by Florian vo » Thu, 16 Oct 2003 20:03:52



Hello,

despite having read the manpage about ten times and having performed
numerous tests, I have been unable to understand how mksisofs exactly
interprets the 'pathspecs' it gets:

- if you specify a whole directory, it will write the whole directory
with its complete structure on the image, which is what I would
expect.

- if you, however, specify a file with a pathname like

foodir/bardir/foofoodir/file

it will put the file 'file' in the root directory of the iso image,
instead of creating the directory 'foodir' in the root directory,
creating 'bardir' in 'foodir', 'foofoodir' in 'bardir', and finally
putting the file 'file' in 'foofoodir'. At least in all my tests it
has behaved like that, regardless of whether the pathspec was given
on the commandline or in a -path-list file.

In other words: if you specify a single file, mkisofs will discard any
directory structure above it. Although a possible (and probably
sometimes wanted) way of interpreting that, it is not what I would
expect as default, since it will easily lead to name conflicts in the
root directory of the iso image.

Can anybody tell me whether mkisofs is capable of also creating the
parent directories of single files (similar to the "--parents" option
of cp?), and how it can be told to do so?

[ Two notes:

1. I could think of a workaround, i.e. using 'cp --parents' to create
a directory tree the top level directory of which can then be
passed to mkisofs as a single pathspec. That should do the trick,
but is quite a lot of overhead in terms of time and (temporarily)
disk space.

2. there's a note in the mkisofs README file about an ADD_FILES
compile option which was introduced in version 1.11 and removed in
version 1.12. It may have addressed that issue, but I'm not sure.]


There's a second question that also haunts me: is mkisofs capable of
ADDING files to an image in a second go (at all, I mean, irrespective
of the directories-in-its-path issue)?

--


Florian v. Savigny

If you are going to reply in private, please be patient, as I only
check for mail something like once a week. - Si vous allez rondre
personellement, patientez s.v.p., car je ne lis les courriels
qu'environ une fois par semaine.
 
 
 

mkisofs behaviour with respect to parent directories

Post by Edvard Rin » Fri, 17 Oct 2003 16:13:53


Check out http://www.yqcomputer.com/ #download and download the 1.3 beta 3
version. There you will find a tool called VisualISO.exe. It is used for
building the tree structure of an ISO image. Export your final design to a
file and you will see the correct notation for solving your problem. In
short, YES, mkisofs can create iso files with complete file path included.

Best of luck!

Ed

 
 
 

mkisofs behaviour with respect to parent directories

Post by news.werbu » Fri, 17 Oct 2003 20:01:33

Florian von Savigny wrote

[mkisofs pathspecs]



Yep.


Afaik there is no direct option.


Use -graft-points:

mkisofs -r -o dest.iso -graft-points \
/foodir/bardir/foofoodir/=/foodir/bardir/foofoodir/file


Yes, see readme.multi.

Udo
 
 
 

mkisofs behaviour with respect to parent directories

Post by Florian vo » Sat, 18 Oct 2003 03:55:54


"Edvard Ringen" < XXXX@XXXXX.COM > writes:



I'm sorry, I had not specified that I am running the stuff on Linux (I
had forgotten that Joerg Schilling's CDR tools are quite portable). So
please accept my apologies, and thanks for trying to help!


--


Florian v. Savigny

If you are going to reply in private, please be patient, as I only
check for mail something like once a week. - Si vous allez rondre
personellement, patientez s.v.p., car je ne lis les courriels
qu'environ une fois par semaine.