On 09/10/11 05:47, Seth Goldberg wrote:
I guess I just don't know what caller would want to use some
non-standard path. DC doesn't care, it's just passing info to
mkisofs, so can we make them just do the right thing without DC in
the middle, where it can only screw things up?
The thinking was that the caller knows the disc's layout better than
pybootmgmt and so could choose a filename better, but using a default
filename is simple enough. (Though frankly, you could just use the
temporary filename, passing it to mkisofs).
I'd like to suggest a solution. I've noticed that the path supplied for
the bios eltorito image is binary identical to the file located at
/boot/grub/stage2_eltorito located under the pkg image area for the ISO.
So I'm assuming that pybootmgmt takes a copy of that and renames it
using the random name it provides to the install client ie. it does not
take the copy of stage2_eltorito from the running system.
In that case the temporary name is redundant since it's only purpose is
to be copied. All pybootmgmt needs to provide is the
path to the original stage2_eltorito above in the 'src' field and leave
the 'dst' field empty.
This means that the install client can locate the El Torito image to
pass on to mkisofs and not need to do anything further with it if 'dst'
and the
permission fields are none. It also eliminates the redundant copy of the
El Torito image being baked into the disk.
When situations arise where the file needs to be copied somewhere then
pybootmgmt can supply the appropriate 'dst' and permission values
Thanks,
Niall
Dave
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
