Why remove such a useful tool - Doh!  I really don't want X or any of it's 
libraries near this particular machine.

What are the repercussions of running mkkickstart --force


Graham.


At 11:56 12/11/2001, you wrote:
>On 12 Nov 2001, Edward C. Bailey wrote:
>
> > >>>>> "Graham" == Graham Hemmings <[EMAIL PROTECTED]> writes:
> >
> > Graham> Upon running mkkickstart under RH7.2 it informs me that it is no
> > Graham> longer used under RH7.2 and that I should use ksconfig.
> >
> > Graham> Does anyone know where I can actually find ksconfig as it's not
> > Graham> installed on my system?
> >
> > $ rpm -qf /usr/sbin/ksconfig
> > ksconfig-1.9.8-4
> > $
>
>but mkkickstart and ksconfig are philosophically two different tools.
>mkkickstart (IIRC) would create a ks file to *duplicate* the machine
>you ran it on.  ksconfig is used to create a ks.cfg file according
>to your detailed specs.  so, technically, it's not a replacement.
>
>rday



_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list

Reply via email to