Just a quick question, and i'm not a scripter so I won't say its obvious, but couldn't the script ask (in the beginning) for user names and passwords. That way it is customized without the generics.
I'm not sure how hard interactivity for that is. Thanks for the work, btw! It really is awesome all that you have done. Kermit On Thu, Feb 21, 2008 at 11:33 AM, John Schmidt <[EMAIL PROTECTED]> wrote: > Hi, > > After much delay, I finally updated my install scripts to use the latest > version of Evergreen 1.2.1.3 that should work on Debian Etch or Lenny. > For > those that are unaware of what they are. It is just one big shell script > which automates the wiki instructions that Dan and others have assembled. > Even if you just use the wiki to install Evergreen, you can look at the > beginning of the evergreen.sh and get a little feel for what accounts are > set > up and why. > > There are many dependencies required to get Evergreen up and running. One > miscue in one place has ramifications in non-obvious places. In my > opinion, > installing the software is not hard, it is configuring the various config > files that are apt to trip up the person installing Evergreen for the > first > time. My script automates the config file generation. I have chosen > default > account names and passwords that are quite similar to what the wiki uses. > > The purpose for writing these scripts was I thought I would probably be > installing Evergreen on multiple machines in time, and wanted an automatic > way of doing it. In addition, I want Evergreen to be adopted and the > first > step is to make it easy to set up. And this is my attempt. I welcome any > and all feedback. > > I am attaching 3 files, Readme.txt, evergreen.sh, and evergreen_chroot.sh. > If > you have any questions please don't hesitate to email me. I will be happy > to > call you and walk through the installation if you would like. > > Thanks, > > John Schmidt > [EMAIL PROTECTED] > > > >
