> > Or yet another config file...Actually, I see this as an extension of the > > package file list. There needs to be support for paritally backing up > > files, which means some rudimentary knowledge about which files are > > user-changeable, and which are not. > > Those in <pkg>.conf are user changeable; those not in <pkg>.conf are > not...
Sorry, but this is too simplistic...as an example, take sshd: You generate a host key for sshd to use, and put it in /etc/ssh, but it is NOT in the <pkg>.conf file of any sshd package I've used, since the <pkg>.conf file is not about user CHANGABLE files, but about user EDITABLE files (that show up in the package configuraition menu)...there's a difference. If you're always doing full package backups, you don't have to worry about the distinction...you just make sure the whole /etc/ssh directory is part of the package list, and you'll backup the host keys along with the config files. If, however, you want to intelligently backup just the local configuration of ssh, you need to know that there are more files than just the ones in sshd.conf to backup. Charles Steinkuehler http://lrp.steinkuehler.net http://c0wz.steinkuehler.net (lrp.c0wz.com mirror) _______________________________________________ Leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel