ok, I'll try to sum up the thread and answers to the various point:<br><br><div><span class="gmail_quote">2005/10/24, Peter Selinger <<a href="mailto:selinger@mathstat.dal.ca">selinger@mathstat.dal.ca</a>>:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Arnaud Quette wrote:<br>...<br>> Any perl (or other well supported scripting) monger out there to take over<br>> that one?<br><br>Great idea. How about bash/sh? Still the most universally available<br>scripting language. I am including a script below that is called as
<br><br> updateconf.sh <configfile> <olddriver> <newdriver><br><br>It does the trick nicely. It would have to be integrated into the<br>install process.<br>...<br></blockquote></div><br>
- bash/sh are the standard on Linux/Unix, not on windows. Though the
support for this last is not a high priority, we should always keep it
in mind. However, if the auto conf update doesn't apply to it, it's not
a big problem as we only support the client part for the moment... So
bash'ing is ok for me, at least for the moment.<br><br>
- I would better see an autonomous script, which embed the data and the processing, whereas you only have the processing above.<br>
Having a table with "<old_drv> <new_drv>" format, with the
2nd field embedding params too (ie "powermust" "megatec -some_mode"
should be fine). But Carlos is also right telling that we do not
consider the driver options. So there should be some completion in the
new support. All options that are useful have to be supported by the
new driver. The remainder have to be discussed here. If these are
really anymore needed, we might have a 3rd field to tell this (ie
"mfr,test" will ask for the removal of "mfr=something" and
"test=something" params in ups.conf<br>
<br>
- if something fails for some reason, make a BIG and CLEAR warning to the user.<br>
<br>
- about the importance of such a task: don't just think about a
standalone box that have to migrate manually. Think about some Debian
infra, with thousand of hosts, upgraded automatically. What a nightmare
for the sysadmin if he has to edit all conf to update it, even in batch
mode!<br>
I can tell personnaly that 90 % of the user msg in my debs are there to
warn for conf changes. And that's really borrying (mix boring and
worrying) for things that could be automated, trust me. But it 's true
that we might (if possible) give the choice to users to auto or
manually migrate their conf!<br>
<br>
- keeping in mind nut-ng (what we have made since 2.0.1 is really
tiny), the conf will be hugely reworked. So this script might handle
this possible conversion too. But there, it's a matter of year(s)...<br>
<br clear="all">Arnaud<br>-- <br>Linux / Unix Expert - MGE UPS SYSTEMS - R&D Dpt<br>Network UPS Tools (NUT) Project Leader - <a href="http://www.networkupstools.org/">http://www.networkupstools.org/</a><br>Debian Developer -
<a href="http://people.debian.org/~aquette/">http://people.debian.org/~aquette/</a><br>OpenSource Developer - <a href="http://arnaud.quette.free.fr/">http://arnaud.quette.free.fr/</a>