mkisofs
Joe Negron
can figure, the only options are to either specify a directory name
which it will recursively include in the .ISO image, or to specify
filenames on the command line. Regarding the latter, what if you want
to specify more files than will fit on the command line?
I want to include subsets of various directories on a DVD. The only way
I can determine to do this is to create a new directory, copy the files
from their various locations to it, then kill the directory when
finished. This seems pretty kludgy - there must be a more elegant way.
BTW, I tried this with a UDF formatted DVD, but no go. Copying to a UDF
formatted disc (DVD+RW) is painfully slow. But, the bigger problem is
that the Sony DVD player (attached to the TV, not PC) doesn't see more
than a certain number of files (sixty some-odd, IIRC). I don't know if
the Sony DVD Player or the UDF formatting is at fault.
--
------------------------------------------------------------------------
I would rather be able to appreciate things I cannot have than to have
things I am not able to appreciate.
--Elbert Hubbard
War is good for business - invest your son.
--antiwar bumper sticker from the 1960s
------------------------------------------------------------------------
Joe Negron from Bensonhurst, Brooklyn, NY, USA
Al Savage
> Does anyone know how to feed mkisofs a list of filenames?
I haven't tried it, but it seems as if you could create a list of
path/filenames, and use the "-path-list" option to feed it to mkisofs .
Reading below, it seems you could even pipe the list in.
http://linuxcommand.org/man_pages/mkisofs8.html
-path-list file
A file containing a list of pathspec directories and
filenames
to be added to the ISO9660 filesystem. This list of
pathspecs
are processed after any that appear on the command line.
If the
argument is -, then the list is read from the standard
input.
Joe Negron
>On Thu, 5 Mar 2009 22:03:43 UTC, Joe Negron <jne...@XsonicX.net> wrote:
>
>>Does anyone know how to feed mkisofs a list of filenames?
>
>I haven't tried it, but it seems as if you could create a list of
>path/filenames, and use the "-path-list" option to feed it to mkisofs .
>Reading below, it seems you could even pipe the list in.
Thanks Al! Don't know how I missed it.
--
------------------------------------------------------------------------
Genius without education is like silver in the mine.
--Benjamin Franklin
Joe Negron
>
>>Does anyone know how to feed mkisofs a list of filenames?
>
>I haven't tried it, but it seems as if you could create a list of
>path/filenames, and use the "-path-list" option to feed it to mkisofs .
>Reading below, it seems you could even pipe the list in.
Well, it worked - sorta. First, I fed it a list of filenames. What I
got on the DVD was pathspecs as part of the directory listing! For
example:
C:\>dir /b S:\
F:\Music\Classical\Baroque\Bach\Bach - Brandenburg Concerto #1, BWV 1046 {Richter}.mp3
F:\Music\Classical\Baroque\Bach\Bach - Brandenburg Concerto #2, BWV 1047 {Richter}.mp3
F:\Music\Classical\Baroque\Bach\Bach - Brandenburg Concerto #3, BWV 1048 {Richter}.mp3
F:\Music\Classical\Baroque\Bach\Bach - Brandenburg Concerto #4, BWV 1049 {Richter}.mp3
F:\Music\Classical\Baroque\Bach\Bach - Brandenburg Concerto #5, BWV 1050 {Richter}.mp3
F:\Music\Classical\Baroque\Bach\Bach - Brandenburg Concerto #6, BWV 1051 {Richter}.mp3
And, when I tried to access them, they seemed to point to the hard
drive!
The solution was to use "/" instead of "\" as the pathspec delimiter.
Would you happen to know how to tell mkisofs to put these files in
separate directories?
--
------------------------------------------------------------------------
Faith is much better than belief. Belief is when someone ELSE does the
thinking.
--R. Buckminster Fuller
Steven Levine
at 07:06 AM, Joe Negron <jne...@XsonicX.net> said:
Hi,
>Well, it worked - sorta. First, I fed it a list of filenames. What I
>got on the DVD was pathspecs as part of the directory listing! For
>example:
>C:\>dir /b S:\
>And, when I tried to access them, they seemed to point to the hard
>drive!
I doubt that, but...
>The solution was to use "/" instead of "\" as the pathspec delimiter.
Mkisfs and cdrecord are lightly ported. Always use unix style path
separators
>Would you happen to know how to tell mkisofs to put these files in
>separate directories?
Use the -graft-points option for this. Here's a snip from a typical
path-list file
usr/=d:/usr
vim/=d:/Util/vim
vim/=d:/cmd/vimenv.cmd
vim/=d:/cmd/vimx.cmd
vim/=d:/Home/.vimrc
WarpIn/=d:/Util/WarpIn
WPTools/=d:/Util/WPTools
Note that mkisofs handles files and directories somewhat differently.
Also, the trailing slash on the left-head path-spec is significant. If
you need wildcard expansion, you need to build the path-list dynamically.
Steven
--
--------------------------------------------------------------------------------------------
Steven Levine <ste...@earthlink.bogus.net>
eCS/Warp/DIY etc. www.scoug.com www.ecomstation.com
--------------------------------------------------------------------------------------------
Ilya Zakharevich
>>The solution was to use "/" instead of "\" as the pathspec delimiter.
>
> Mkisfs and cdrecord are lightly ported. Always use unix style path
> separators
I saw no problem with "\" (but I always have a drive letter prepended,
by ^F in FC).
>>Would you happen to know how to tell mkisofs to put these files in
>>separate directories?
>
> Use the -graft-points option for this. Here's a snip from a typical
> path-list file
>
> usr/=d:/usr
> vim/=d:/Util/vim
> vim/=d:/cmd/vimenv.cmd
> vim/=d:/cmd/vimx.cmd
> vim/=d:/Home/.vimrc
> WarpIn/=d:/Util/WarpIn
> WPTools/=d:/Util/WPTools
>
> Note that mkisofs handles files and directories somewhat differently.
> Also, the trailing slash on the left-head path-spec is significant.
I never used the trailing slash on the LHS. What does it mean?
(3 or 4 years ago I tried to understand trailing slashes business with
mkisofs, but experiments have shown that the docs are obviously wrong.
And I got a lot of crashes... I hope that now it is better...)
Yours,
Ilya
Steven Levine
at 08:37 PM, Ilya Zakharevich <nospam...@ilyaz.org> said:
Hi,
>I saw no problem with "\" (but I always have a drive letter prepended, by
>^F in FC).
I guess this is a YMMV thing. I've fixed other folks mkisofs failures by
using unix slashes.
What does ^F do in FC?
>> Also, the trailing slash on the left-head path-spec is significant.
>I never used the trailing slash on the LHS. What does it mean?
It ensures that the LHS is interpreted as a directory. It can probably be
omitted when the RHS is a directory. If the RHS is a file and the LHS
slash is omitted, the file is renamed.
Regards,
Ilya Zakharevich
>>I saw no problem with "\" (but I always have a drive letter prepended, by
>>^F in FC).
> I guess this is a YMMV thing. I've fixed other folks mkisofs failures by
> using unix slashes.
> What does ^F do in FC?
Pastes the full path of "the current file" into the command line...
Thanks,
Ilya