said:
> I am aware of 3 paths I am aware of:
> 1. the source path. M:/*.*
This is a pathspec, not a path. It will work, but it will not do what you
expect. It will ignore files and directories that do not have a dot in
the name.
> Where I want the ISO file written to:
>H:/ISOIMAGES/ecs11cd1.iso
Yes
> 3. the log file path.
> H:/APPS/CDRECORD/ecs11cd1.log
OK. However, this has nothing specific to do with mkisofs. The standard
method will work.
> Oops
> -b eltorito_boot-image
> Specifies the path and filename of the boot image to be
> used when making an "El Torito" bootable CD.
> 4. M:/BOOTIMAG/cdloader.bin
Right. You need to supply this.
> -e boot_catalog
> Specifies the path and filename of the boot catalog to be
> used when making an "El Torito" bootable CD.
> The pathname must be relative to the source path
> specified to MAKISOFS.
> I am afraid I never learn the significance of "relative."
> 5. M:/BOOTIMAG/boot_cat.bin
Relative means without drive or leading slash.
> -d
> Omit trailing period from files that do not have
> a period.
This is better for our uses.
> No where do I see a definition of what a graft point is and/or why
>one would use it. ???
It's in the docs and, hopefully, I given you sufficient alternative
explanations so that you now understand the docs.
> -l
> Allow full 31 character filenames.
> needed? I have some long file names.
Because it's implied for Joliett.
> The only
> -m
> I see is:
It was in your example. Drop it. Now that you mention it, I'm not sure
why you put it there.
> -m glob
> Exclude glob from being written to CDROM.
> What is a "glob" ???
A glob is similar to a wildcard. You can think of them as the same thing.
> -o filename
> is the name of the file to which the iso 9660 filesystem
> image should be written.
> Why isn't there any mention about a path???
There is. The ISO filename may be specified with a full pathname or
relative to the current directory. This is not different than how you
might specify any filename on your hard drive.
> ??? I am not aware that I want to add anything to the
> ISO9660 filesystem?
Everything you add is adding the the ISO9660 filesystem. That's what an
ISO is.
> My understanding is that everything
> that I want in the ISO9660 filesystem ISO image is in
> Drive M:\.
That's why I added m:/ to the command.
> -relaxed-filenames
> The option -RELAXED-FILENAMES allows ISO9660 filenames to
> include digits, uppercase characters and all other 7 bit
> ASCII characters...
> I think i need this. ???
No. Joliett implies this.
> And lets not forget
> -V volid
> Specifies the volume ID ...
> -V ECS_CDRUN
Sure.
Have fun.
Steven
--
----------------------------------------------------------------------
"Steven Levine" MR2/ICE 2.47 #10183 Warp4/FP15/14.093c_W4
www.scoug.com irc.fyrelizard.com #scoug (Wed 7pm PST)
----------------------------------------------------------------------
=====================================================
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.