Tom

At 03:04 14.04.2004, you wrote:
Erich Titl wrote:
..
My point is that /var/lib/lrpkg/shorwall.conf should not point to files that do not exist.

Oh.... sorry, this is for the configuration tool .... my fault :-(


Mhhh an egg and hen problem. If we include it in the initial distribution then an upgrade will overwrite it. IIRC LEAF does not have a postinstall function yet.



I think that Charles's suggestion about using two packages makes this a bit more friendly. The main problem that I see with that approach is that it doesn't allow any way for me to add a new config file in the future and have it reflected in the Shorewall configuration menu.

Well, I believe they are not necessarily mutually exclusive.
If we include let's say /etc/shorewalluser/* in /var/lib/lrpkg/shorewall.list and /etc/shorewalluser/shorewall.conf in the /var/lib/lrpkg/swconf.list then, if swconf.lrp _was_ installed, the user configuration would be saved to swconf.lrp, else it would be saved to shorewall.lrp. In any case you would not need to populate /etc/shorewalluser/shorewall.conf as the backup script would take care of user config data. This sounds complicated, but from a user's perspective would be almost invisible.

Well, it sounds complicated to me -- I'm lost :-)

Sorry, probably my fault being unclear :-(


I am referring to the lrcfg backup tool in LEAF.

The respective .list files in the directory /var/lib/lrpkg define what files are part of a .lrp package.

Files that are defined in multiple .list packages are not archived at all, but files implicitly included in a directory path in one file _and_ explicitly included in the other are backed up in the package which explicitly includes them.

If the /var/lib/lrpkg/shorwall.list file _and_ the /var/lib/lrpkg/swconf.list file both contain /etc/shorewalluser/shorewall.conf _and_ both packages are installed on a LEAF system then this file would never be backed up. This can be avoided by including /etc/shorewalluser to /var/lib/lrpkg/shorewall.list _and_ /etc/shorewalluser/shorewall.conf to /var/lib/lrpkg/swconf.list, e.g. naming the file explicitly in swconf.list.

If _both_ packages (shorewall.lrp and swconf.lrp) are installed then the /etc/shorewalluser/shorewall.conf will be saved to the swconf.lrp package.

If only shorewall.lrp is installed then the file will go to shorewall.lrp.

...
I assume that by "configuration file" you mean shorewall.conf (as opposed to shorwall.conf in /var/lib/lrpkg/).

yes.


cheers
Erich

THINK
Püntenstrasse 39
8143 Stallikon
mailto:[EMAIL PROTECTED]
PGP Fingerprint: BC9A 25BC 3954 3BC8 C024 8D8A B7D4 FF9D 05B8 0A16




------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id70&alloc_id638&op=click

_______________________________________________
leaf-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-devel

Reply via email to