Koozali.org: home of the SME Server

Legacy Forums => General Discussion (Legacy) => Topic started by: Adam Ghijben on June 13, 2000, 09:38:50 AM

Title: Kick Start
Post by: Adam Ghijben on June 13, 2000, 09:38:50 AM

Hi all,

Just wanting to know if anyone has got anywhere in adapting the ks.cfg (Kick Start) to automatically set up an e-smith machine immediately after install.

That is, to set custom settings to the machine, in place of the default ones.

I'd be interested to know how you did this, and a detailed answer would be nice, not merely, "I edited the file"....well DER! Perhaps post your own ks.cfg file?

Thanks a lot
Adam Ghijben

Title: RE: Kick Start
Post by: Gordon Rowell on June 13, 2000, 11:06:56 AM

Adam Ghijben wrote:

> Hi all,
>
> Just wanting to know if anyone has got anywhere in adapting
> the ks.cfg (Kick Start) to automatically set up an e-smith
> machine immediately after install.
> [...]

Absolutely - have a look at

http://e-smith.gormand.com.au/4.0-preview/ks.cfg-4.0-prototype

Be very careful with quoting - it's a Perl script embedded in
shell, and make sure that you save the file as a Unix (LF only)
file, not a DOS (CR/LF) file.

This is based on Charlie Brady's original file for 3.1 and may
need to change a bit before 4.0 is released as I may not have
all of the 4.0 variables set in the prototype file.

Gordon

Title: RE: Kick Start
Post by: Charlie Brady on June 19, 2000, 01:41:04 PM

Gordon Rowell wrote:

> Adam Ghijben wrote:
>
> > Hi all, > > Just wanting to know if anyone has got
> anywhere in adapting > the ks.cfg (Kick Start) to
> automatically set up an e-smith > machine immediately after
> install. > [...]
>
> Absolutely - have a look at
>
> http://e-smith.gormand.com.au/4.0-preview/ks.cfg-4.0-prototype
>
> Be very careful with quoting - it's a Perl script embedded in
> shell, and make sure that you save the file as a Unix (LF
> only) file, not a DOS (CR/LF) file.
>
> This is based on Charlie Brady's original file for 3.1 and may
> need to change a bit before 4.0 is released as I may not have
> all of the 4.0 variables set in the prototype file.

I'd do it a different way if I was doing it again. Instead of providing a replacement for the "reset-config" program, I'd just
do this after the reset-config call in ks.cfg:

/sbin/e-smith/config set Param1 'aaaaaa'
/sbin/e-smith/config set Param2 'bbbbbb'
/sbin/e-smith/config set Param3 'cccccc'
.....

for each param you wished to preconfigure. Then add:

/sbin/e-smith/signal-event console-save

regards

Charlie