> You're missing my point. > You don't need to reverse engineering or rebuild anything to > change the account/hostname info. Edit the config files in > the ISO using the _RIGHT_ tools and burn it to a CD.
Yes, Ryan, thank you, I do understand what mkisofs -quiet -o linuxboot.iso -b isolinux/isolinux.bin -c isolinux/boot.cat -no-emul-boot -boot-load-size 4 -boot-info-table iso does. I have hacked Dreamcast bin/cues before. My point is that hunting through z:\linuxboot\Makefile for the mkisofs parameters and obtaining a copy of mkisofs that works on XP and going through a *rebuild*[1] of the iso is more work than it should be in order to change three tiny yet critical parameter defaults that are extremely unlikely to be acceptable at a real Windows production site. But whatever. I'll concede that making the change to the Linux boot CD is unlikely to happen more than once for a production site, so this amount of work is negligible in the long run. Are you willing to concede the scripts are largely unintelligible as written? > The filesystem in the CD is not like your regular filesystem. > You can't just replace/edit the files in place and expect it > to still work. Funny. If I make a multi-session bootable Windows XP CD, I can rewrite \i386\winnt.sif to my heart's content. Chris Doherty Helpdesk Analyst Crompton Co./Cie a Chemtura Company Elmira: (519) 669-1671 x319 [1] What would you call creating a bootable ISO9660 image from source files, a second time? I call it a rebuild. ------------------------------------------------------- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42" plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php _______________________________________________ unattended-info mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/unattended-info
