>he lives in California. I was wondering, is there a way, like create a
>file, so when the installing process is going on, when RH ask you to
>choose which package to install, it can just read from the file
if youre willing to do some debugging, you can use the 'kickstart'
feature found in rh 5.x (at least for x>0, maybe x = 0 too). i warn
you that this is not a solution to ship off without thorough testing--
it took me about 10 hours of tweaking and debugging to get it working
well enough to do the install on our latest 64node cluster---but that
time was amortized considering that i didn't want to install 64 times
by hand and make sure i always got the same exact thing and didn't screw
up.
the docs on this functionality are really lean, but look for a file
README.ks
or maybe it was README.kickstart
somewhere in the redhat cd.
frankly, i'd suggest you just pick the subsets of the install that the
person should install (maybe everything, and then have him trim down
the docs after the install...you could mail him a shell script to
rpm -e the extra languages of docs that would be <200 characters in
case he had to type it in manually) and discourage them from trying
to pick individual packages at all (i know how easy it is to miss
something critical...i to this day forget bin86 frequently, without
which you can't generate a new kernel)
but, just to set the record straight, redhat *does* support a scriptable
install....
...at about the level solaris does, i think, which again is "use only in
case of dire need and many machines" imnsho.
i can give people a demo ks.cfg file (which you copy on to the boot floppy
and tweak some other stuff, to make it go), but the only one i can find
ATM is uncommented and thus near useless.
at any rate i've used this, and it's worked, so if you need help give me
a holler.
the README.ks file is IIRC a very well commented example cfg file.
---------------------------------------------------------------------------
Send administrative requests to [EMAIL PROTECTED]
