Subject: Re: sysinst maintainer?
To: Phil Nelson <phil@steelhead.cs.wwu.edu>
From: Tim Rightnour <root@garbled.net>
List: tech-install
Date: 08/18/1998 13:43:04
On 18-Aug-98 Phil Nelson spoke unto us all:
# I like your changes. We might add an additional fixed parameter that
# says to display the subwindow or don't display the sub window.
Thats not a bad idea at all.. I imagine a parameter like:
int show;
if show = 1; show stderr + stdout
if show = 2; show stderr
if show = 3; show stdout
if show = 4; dont even draw the subwindow.
Just for future flexibility.
# In
# both cases, we could log all interaction to a file so future questions
# of "sysinst blew up ...", we could ask for the log file.
Hell.. if it blew up.. we could have an option: format these logs into a PR.
and then tell the user to just email the output to gnats bugs.
# And that
# would be a good place build a script file to redo the install. I'm
# not sure, but I *think* all the install work is run through the sub-process
# commands. That is, if one reran all the same programs with the same
# parameters, one would get an identical installation. (The only things
# that might not be done this way are files that get written to /etc
# (/mnt/etc)
# and they could be added to the script file by approiate calls to echo.)
I was thinking along those lines.. hadn't thought of the /etc stuff.. You are
right.. we use fprintf's in there to do that.. I'll have to fiddle around in
my head for a way to do that without over-duplicating the code there.. the
best way is to probably add it to the script somehow with:
cat /etc/foo < EOX
stuff
EOX
Either way.. I'll get started this week on banging away at that stuff.. looks
like I need to either sacrifice a box for this.. or hack it to issue dummy
commands for everything.. (you don't happen to have patches for that do you,
just thought you might for development work)
---
Tim Rightnour - root@garbled.net
http://www.zynetwc.com/~garbled/garbled.html