On Tue, 10 Apr 2001, Chris Petro wrote:
Go back and re-read what I wrote. That doesn't do it.
Using the comps file allows you to choose *different* packages for install,
but must be specified in the ks.config file. What I am going to acheive
is the ability to
On Mon, 9 Apr 2001, Chris Petro wrote:
Like many medium to large installations, we have some process in
place to "roll" (i.e. install and configure) machines in an
automatic or semi-automatic process. Currently we use a combination
of kickstart and "clustering" scripts
On Tue, Apr 10, 2001 at 09:18:57AM +0300, Pekka Savola wrote:
On Mon, 9 Apr 2001, Chris Petro wrote:
Like many medium to large installations, we have some process in
place to "roll" (i.e. install and configure) machines in an
automatic or semi-automatic process. Currently we
On Tue, 10 Apr 2001, Chris Petro wrote:
On Tue, Apr 10, 2001 at 09:18:57AM +0300, Pekka Savola wrote:
On Mon, 9 Apr 2001, Chris Petro wrote:
Like many medium to large installations, we have some process in
place to "roll" (i.e. install and configure) machines in an
automatic or
een hdlist and hdlist2.
Second, is there a possiblity of getting the programmers involved
in the production of the anaconda/kickstart system to document
what they are doing? Inline comments, beyond the stage of
"... linear search" (w
