Yes, that's one way to do it.. another is to use a temp disk and avoid involvement of 'yet another' userid.. ;-) You're right - it doesn't require use of a r/w 191.. but a r/w address somewhere a long the way...
Scott Rohling On Wed, Oct 29, 2008 at 11:26 AM, Mark Post <[EMAIL PROTECTED]> wrote: > >>> On 10/29/2008 at 9:49 AM, Scott Rohling <[EMAIL PROTECTED]> > wrote: > -snip- > > True for cloning -- not true if you use the RedHat 'kickstart' method (or > > SuSE autoyast, which I haven't tried, personally). I've helped several > > clients implement an 'automated kickstart' - which involves creating the > > necessary config files on the 191 (or other addressed) disk, punching the > > install kernel to the reader and ipling the reader. The config file > points > > to a kickstart config on an install server -- and the automated install > > takes off. A new server is created this way rather than cloning.. > > Not to elongate this thread too much more, but none of that requires a > read-write 191 disk (or any other local disk). You can send the three files > (kernel/parmfile/initrd) from another userid and just IPL from the reader. > If that other userid has some automation built into it, you can do things > like select DASD devices and IP addresses from a predefined pool, craft a > custom parmfile and kickstart/AutoYaST file and away you go. > > > Mark Post >
