[Olsr-dev] please revert " force copy the olsrd.conf file during install"

[L. Aaron Kaplan]

Hi Ferry,


I wouldn't recommend doing even that.

Why?
Due to the history of olsrd , there are a couple of networks out there which have very different olsrd.conf files.
Different metrics, etc.
So, overwriting - even by accidentally pressing "Y" - can ruin your network.
It is better to have the admin explicitly copy over and adapt the olsrd.conf file in my opinion.

This is based on my experience of maintaining nodes which are in the field and believe me, you don't want to go there every time you make an upgrade.
:))

Of course, I also understand the other side - at some point we need to have a newer olsrd.conf file.
Maybe we can adapt some experiences of debian apt-get ?
What do you think about this?


a.


On Jul 3, 2012, at 1:56 PM, Ferry Huberts wrote:

> 
> 
> On 03-07-12 13:49, Bastian Bittorf wrote:
>>> user will loose his olsrd.conf on make install
>> 
>> better would be something like:
>> 
>> if [ -e $CFGFILE ]; then
>>       cp -f $file $CFGFILE.maintainer
>> else
>>       cp -f $file $CFGFILE
>> fi
>> 
>>> moreover the OpenWRT patch do not hurt because it is not a patch
>>> that
>>> changes the olsrd binary
>> 
>> important point:
>> but if we can throw away the
>> patch its better for everybody.
>> 
>> bye, bastian
>> 
> 
> 
> how about this?
> 
>> http://olsr.org/git/?p=olsrd.git;a=commitdiff;h=000c9b85141e474ef4440ac62a1f8b0c71eeb8ef
> 
> 
> 
> -- 
> Ferry Huberts
> 
> 
> 
> -- 
> Olsr-dev mailing list
> (spam-protected)
> https://lists.olsr.org/mailman/listinfo/olsr-dev

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 203 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.olsr.org/pipermail/olsr-dev/attachments/20120703/60d5f4fb/attachment.sig>