Mark writes:
> Just a few suggestions/comments....
> 
> How about todo.pl logging errors instead of bailing on unexpected error
> conditions (unless it's fatal, of course). Maybe a switch to set it?

I prefer the default of halting.  This allows me to fix the problem, and
manually restart todo, to install the rest of the programs.  If the problem is
with the installation files, I can fix the installation, so it won't happen
again.  If it's just a network glitch I can get the installation going again.

If the installation just continues, and you install a lot of programs, there's
a good chance of dependency failures, meaning a total reinstall is necessary.
Also you HAVE to check the log after an install, or risk giving one of your
users an unworkable machine.


> Do we really need the Z:\ drive at all? Is there any reason we can't use
> a UNC path for everything?

Yes. There are programs that won't install from UNC drives.  Also
using z: allows you to have several different install servers, mapping to the
one with least load at boot time, or using a subst and installing off a DVD
drive instead.

Also, some of the install programs need to be told where you're installing
from.  This will also give you problems.


> What do you think about todo.pl being set up to take 2 additional
> variables (Package_Name, Package_Ver) and then adding those to a CSV
> file so we know what's on each PC? It could also be a first step towards
> a "post setup" program to parse and compare to a master CSV or database
> for automatic installs or upgrades (similar to the INI approach used by
> someone else earlier on the list). I'm currently doing it thru the
> install batch files, but it would probably be cleaner if it was done
> thru todo.pl.

Just having a log of all executed commands on the disk would be a good step
forwards.  What I'd really like is to generate a MD5sum of all files on the
local harddrive after the install.  I could then use this database to find
what applications were installed, wether any files were corrupt and also be
able to estimate the 'drift' of each PC as they are used, by regularly
recomputing the checksums.

-- 
Dag Nummedal ([EMAIL PROTECTED])


-------------------------------------------------------
This SF.net email is sponsored by:  Etnus, makers of TotalView, The best
thread debugger on the planet. Designed with thread debugging features
you've never dreamed of, try TotalView 6 free at www.etnus.com.
_______________________________________________
unattended-info mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/unattended-info

Reply via email to