[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: How to constrain the install through kickstart to one drive



Thanks for responding both Andrew and Maarten.

Ok then,  I was hoping that there was a way to say, regardless of what drives 
are installed in the pc, just load the drive that's hanging off Primary 
Master and leave the rest alone?  This is basically what I want to do.   I 
just didn't want to go through the pc's to find out exactly what type of 
drives are installed.  Not to start an OS flame war but I can do this in 
Solaris using the keyword "bootdisk" in the jumpstart profile.  Just 
wondering if there was something similar in ES4.

Thank you again, for your time...

Phil

On September 18, 2007 13:28:28 Andrew Bacchi wrote:
> You can't always use one size fits all.  We have many kickstart files
> for our many servers.  Each kickstart is tailored for a type of server
> and we use the type that best suits our needs.
>
> So, the ondisk=sda/hda problem is solved by using the appropriate
> kickstart file.  At the install screen we define which kickstart to use
> with "linux ks=kickstart_file_name".
>
> Phil Savoie wrote:
> > HI All,
> >
> > I have a number of machines I would like to install using kickstart. 
> > This isn't the problem as this I know how to do...but, some pc's have
> > more than one HD installed.  Some of the pc's have pata, sata or ide
> > drives; that is a mixture of all I have mentioned.  In order to combat
> > the problem of kickstart not working on all types of disks, I took out
> > the  ondisk=[s|h]da.  This works well on a pc with a single disk.  With
> > more than one disk, the second disk also get a filesystem.  I don't want
> > the second disk touched at all.  Is there a way to do this?
> >
> > Thanks in advance,
> >
> > Phil
>
> --
> veritatis simplex oratio est
> 		-Seneca
>
> Andrew Bacchi
> Systems Programmer
> Rensselaer Polytechnic Institute
> phone: 518.276.6415  fax: 518.276.2809
>
> http://www.rpi.edu/~bacchi/




[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]