On Sun, Jul 15, 2007 at 02:25:39PM -0400, Roberto C. S?nchez wrote: > On Sun, Jul 15, 2007 at 07:36:06AM -0700, Tom Eastep wrote: > > > > Kenneth, > > > > The Debian maintainer thinks that things should be done the Debian way -- > > that's why he has the /etc/default/shorewall file with the 'startup' option. > > The rest of the world controls Shorewall startup using the STARTUP_ENABLED > > option in shorewall.conf. > > > As a Debian developer and user, I can certainly appreciate the > reasoning. But yes, having it in two places can be annoying. I imagine > that the "Debian way" is an outgrowth of multitudes of packages not > having a cimple way to control whether or not to start.
/etc/default controls init scripts, when they need to be controlled (yes, dumb name, historical). That's an area that has traditionally been left to the vendor - most packages don't even supply one, and it usually has to be rewritten when they do. It's an unfortunate concidence that shorewall has a feature that duplicates part of the behaviour of the init script. (This is all very clumsy, and that's mostly because sysvinit sucks - it just sucks less than every *other* way to do it) ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Shorewall-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-users
