Chris, That last comment from Moritz is how I did it -->
"Under Windows you can use WinIso or similar... it works! regards, Moritz" I just opened the linux boot iso with WinIso, extracted the cfg file, edited the parameters, and put it back. Relatively painless. I have a local install account and the unattended CD is the only 'one' that uses it to connect to the deployment server. Pretty much what you described and it may have taken 10 minutes including download time. I can see that you are frustrated and I agree with most of your points but it doesn't seem productive to get on the list and hammer the guys doing the work for their coding style. Anytime you go to another dev team they have their own way of doing things - you shouldn't barge in and tell them they are wrong. Before you get hotter ... I agree with most of your points and Pat has talked about some work on the file layout (there are a bunch of posts on the list about this) but it turns out that in most shops once you have a working setup you aren't given the time to fine-tune like we would all like. I have gained literally hundreds of hours by using this offering and I can say it took me a little while to get "my head around it" but it has been well worth it. If you want to talk to me, openly, about the problems and frustrations and perhaps get some insight into my use model I would be happy to give you a call. Just let me know. Don Morrison Technology Department Manager The National Judicial College [EMAIL PROTECTED] > 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
