said:
Steven
>> Um, well, I am not comprehending how the path list option works or
>>what it does. The documentation is not clear to me on that point.
>OK. From the docs
>
> -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. There must be at
> least one pathspec given on the command line as well.
>This says that the file contains a list of directories and filenames in
>pathspec format. The items are supplied one per line, which is pretty
>typical for this kind of input.
I am afraid that without an example, that does not say anything
meaningful to me. :^(
>A pathspec is defined as:
>
> pathspec is the path of the directory tree to be copied into
> the iso9660 filesystem. Multiple paths can be specified,
> and mkisofs will merge the files found in all of the speci-
> fied path components to form the cdrom image.
> If the option -graft-points has been specified, it is possi-
> ble to graft the paths at points other than the root direc-
> tory, and it is possible to graft files or directories onto
> the cdrom image with names different than what they have in
> the source filesystem. This is easiest to illustrate with a
> couple of examples. Let's start by assuming that a local
> file ../old.lis exists, and you wish to include it in the
> cdrom image.
>
>So, if you are not using graft-points, valid pathspecs are:
OK, what is a graft-point?
> /dirname
> /dirname/filename
>and so on.
>>mkisofs -v -o %H:\ISOIMAGES\ecs11cd1.iso% -r -J -m
>>-b M:\BOOTIMGS\cdloader.bin -c M:\BOOTIMGS\boot_cat.bin -no-emul-boot
>>-boot-load-size 4
>> > /H:\APPS\CDRECORD\makecs11cd1dow.log 2>&1
>>> mkisofs -v -o %ISOFILE% -r -J -graft-points -path-list=pathlist.in
>>>-exclude-list=pathlist.out
>Use forward slashes. Backslashes might work, but it's a crapshoot.
>Also, you have some basic syntax errors. Recall that % surrounds
>environment variables in scripts. :-)
A file name is an environment variable?
>Reread the docs for the -c option to understand why the path you supplied
>was wrong.
>You need to supply at least on source pathspec. I supply mine in the
>path-list file. You need to supply yours on the command line.
>Try:
> mkisofs -v -o H:/ISOIMAGES/ecs11cd1.iso -r -J -m
> -b M:/BOOTIMGS/cdloader.bin -c boot_cat.bin
> -no-emul-boot -boot-load-size 4 m:/
>after unwrapping, of course. This should either work, or be close.
I was trying to add a path and log file name to the
end of the command.
>Steven
Thanks
--
This message was sent to you by: Don(ald) O. Woodall
Shooting electrons at you from Grand Rapids, Michigan, USA
My e-Mail/News Reader is: MR/2 ICE version 2.40 S/N 393
The Operating System is: eComStation version 1.1
This OS/2 system uptime is 2 days 02:39 hours :^( (en).
-----------------------------------------------------------
"Don{ald} O. Woodall"
-----------------------------------------------------------
=====================================================
To unsubscribe from this list, send an email message
to "steward@scoug.com". In the body of the message,
put the command "unsubscribe scoug-help".
For problems, contact the list owner at
"rollin@scoug.com".
=====================================================
<< Previous Message <<
>> Next Message >>
Return to [ 28 |
August |
2004 ]
The Southern California OS/2 User Group
P.O. Box 26904
Santa Ana, CA 92799-6904, USA
Copyright 2001 the Southern California OS/2 User Group. ALL RIGHTS
RESERVED.
SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group.
OS/2, Workplace Shell, and IBM are registered trademarks of International
Business Machines Corporation.
All other trademarks remain the property of their respective owners.
