On Tue, 2008-07-01 at 18:57 -0700, Tom Eastep wrote: > > No, we aren't -- we are proposing to require that two fields (DUPLICATE and > COPY) be empty when the new behavior applies.
Ahhh. OK. I see. > Brian, we can't just remove > columns from configuration files between releases. Users often upgrade > Shorewall as part of a distribution upgrade where hundreds of packages are > changing. We can't make incompatible changes that result in their firewall > not starting after the upgrade. Yes, that's a very valid point. > I've thought of that approach (adding a provider option) You mean a new field/option to the provider table, yes? > but what happens if > part of the entries have the new option and part don't? s/part/some/ i.e. so some providers entries have the "override main routing" and some don't? I think that case is actually the more clear case. In that case, we can deduce that the user has actually chosen to use the new functionality. The more unclear case to me is that no provider entries have the new field selected. Is this because the user's preferences are that none of the providers override the main table or that they simply have not recognized the new feature and made adjustments to reflect it? I wonder if we could/should have a shorewall.conf feature (default to off of course) for this new behaviour. At least through a transition to a new major release that requires this new behaviour. Or do your release standards forbid any new release to require user intervention to adopt some new/changed functionality? That's fair enough if they do. I can certainly see a good point for that kind of policy. I'm just at the moment unclear if that's the case. b.
signature.asc
Description: This is a digitally signed message part
------------------------------------------------------------------------- Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________ Shorewall-users mailing list Shorewall-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/shorewall-users
