What about the info file? I want to enforce the load structure, thus I have to have different CD's with different info files pointing to different xml files. i.e. one info file points to "laptop_developer.xml". Another points to "laptop_user.xml" etc. etc. Those xml files also have a lot of embedded scripts and config files to set up our krb5 authentication as well as the pam_mount login mounting system. I can't let user's do a "normal, choose what you want" install. For developers, I hand them the CD with the info file for developers. Users get the CD with the info file pointing to the regular user.xml. At least that's what I planned on doing. What I am hoping for is someone to tell me "edit these files ... put everything in from all 5 floppies into one subdirectory somewhere . . . now run mkisofs with these switches . . . burn the iso to CD." Or am I misunderstanding how this all works? (It wouldn't be the first time) --Jonathon -----Original Message----- From: Anas Nashif [mailto:nashif@suse.de] Sent: Wed 8/20/2003 12:11 PM To: Robison, Jonathon (M.) Cc: suse-autoinstall@lists.suse.com Subject: Re: [suse-autoinstall] Switching from floppies to disk Robison, Jonathon (M.) wrote:
I have created an install server, and the necessary floppies (1 boot, 4 module). The info file is working on the module1 floppy, and installing from the http server, as desired.
Can someone guide me on what I would need to do to combine all of these floppies into one image? I have some of those "Business Card" CD's, capable of holding 50M.
If you have this, then there is no need to create floppies at all, just create a bootable CD using the kernel and initrd available on the first CD in "boot/loader". Anas