Hi Anas, The answer to your question below is a little complicated but here goes: We have a custom selection of packages that we want to install and be able to maintain so we would like to keep them in a central repository rather than keep burning new CD's every time a package is updated. We want to use this installation all around the world (60+ locations, many with 256kbps WAN links or less)and keep it up-to-date so I wanted to create a boot CD (as small as possible) that I could distribute to people at each location who could use it to install this 'standard' build over the WAN (usually overnight). The problem is that the hardware the build is to be installed on is very varied and many have some "funnies" that cause the installation process to fail during probing etc. I wanted to get the root filesystem on the CD as troubleshooting the installation process when you have to wait 4hours to fetch the root filesystem via HTTP in order to test new settings is very hard work! If the root filesystem could be on the CD but the packages centrally, we can at least be sure the installation process is working OK, before leaving the machine overnight to (slowly) pull down all the current packages. I hope that makes some sort of sense, I'd be happy to consider any other suggestions as to how I might get around this problem... Thanks again, Nick. -----Original Message----- From: Anas Nashif [mailto:nashif@suse.de] Posted At: 02 February 2005 05:11 Posted To: Nick-Forbes.SPAM Conversation: [suse-autoinstall] Hybrid Auto Install (CD - FTP/HTTP) Subject: Re: [suse-autoinstall] Hybrid Auto Install (CD - FTP/HTTP) --snip--

Why exactly do you want to load the root file from the CD? any special reason?