On 9/29/2014 11:35 AM, PGNd wrote: > That said, I'm all for as robust-as-possible upstream-only > host-specific process for those that prefer, either occasionally or > regularly, to stick as close to upstream as possible. (have Docker in my > eventual sights ...). > > EIther a mechanism to re-configure @ build46 exec, or > correct-as-possible host-specific defaults (hoping that, per-distro, > they're not changing frequently, if at all) are appreciated.
The current Shorewall version is usable back to at least RHEL 5, Debian 5, and OpenSuse 10. So per-distro defaults (as represented by the shorewallrc.* files) are not one-size-fits-all. For several years now, I've been tempted to drop rpms from the Shorewall distribution altogether: - I don't provide packages for the other major package systems. - I don't run any rpm-based systems myself (other than VMs for testing), and on those I either install from the tarballs or I use the distro's rpm. - One-size-fits-all rpms are not practical. - The Shorewall install system is capable of per-host/per-distro customization and can create tarballs suitable for input into the packaging systems. My $.02 -Tom -- Tom Eastep \ When I die, I want to go like my Grandfather who Shoreline, \ died peacefully in his sleep. Not screaming like Washington, USA \ all of the passengers in his car http://shorewall.net \________________________________________________
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ Slashdot TV. Videos for Nerds. Stuff that Matters. http://pubads.g.doubleclick.net/gampad/clk?id=160591471&iu=/4140/ostg.clktrk
_______________________________________________ Shorewall-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-users
