Re: problem integrating ks.cfg with RHEL WS 2.1 ISOs

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

 



Hello Philip,

Sincere thanks for your inputs.

I am aware of the interactive option but just missed
to try it and will give it a shot... However the
question is: why just the package selection screen is
skipped despite no %packages section specified (as I
have mentioned there is only %post section in my
ks.cfg).. Anyway this option definately needs an
attempt. Thanks.

"linux ks=cdrom:/ks.cfg" is a valid syntax. "file"
argument is used if ks.cfg is to be integrated with
initrd.img which is what I have done while creating
the first set.

Regards,
Ajay 



--- Philip Rowlands <phr@xxxxxxxxxxxx> wrote:
> On Fri, 18 Jun 2004, Ajay Mulwani wrote:
> 
> >1) The first set has integrated ks.cfg file within
> isolinux/initrd.img
> >and also updated isolinux/isolinux.cfg so that this
> ks.cfg is called by
> >default even if just the "Enter" key is pressed at
> the "boot:" prompt.
> >The ks.cfg file has ONLY the %post section which
> calls a script. With
> >this set the problem that I am facing is the linux
> installer does not
> >gives me an option to select packages and starts
> the "minimal"
> >installation always.
> 
> Sounds like you want the "interactive" option in the
> kickstart file:
> 
>  interactive (optional)
> 
>    Uses the information provided in the kickstart
> file during the
>    installation, but allow for inspection and
> modification of the
>    values given.  You will be presented with each
> screen of the
>    installation program with the values from the
> kickstart file.
>    Either accept the values by clicking Next or
> change the values
>    and click Next to continue. See also [50]the
> Section called
>    autostep.
> 
> >2) To avoid the situation in (1) I created the
> second set. Here, I
> >restored the original initrd.img and isolinux.cfg
> and now kept ks.cfg
> >at the top level and at isolinux directory. Now if
> at the "boot:"
> >prompt I give "linux ks=cdrom:/ks.cfg"
> 
> Is that a valid argument? command-line.txt has:
> 
> ks=cdrom:       Kickstart from CDROM
> ks=file:<path>  Kickstart from a file (path =
> 'fd0/ks.cfg')
> 
> (observe no file specified for cdrom, perhaps file
> would work)
> 
> 
> Cheers,
> Phil
> 
> 
> _______________________________________________
> Kickstart-list mailing list
> Kickstart-list@xxxxxxxxxx
>
https://www.redhat.com/mailman/listinfo/kickstart-list
> 


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 



[Index of Archives]     [Red Hat General]     [CentOS Users]     [Fedora Users]     [Fedora Maintainers]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [KDE Users]

  Powered by Linux