David Douthitt wrote: > Those in <pkg>.conf are user changeable; those not in <pkg>.conf are > not...
Charles Steinkuehler wrote: > Sorry, but this is too simplistic... It is? > 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. I would say then that the sshd package is broken. # echo /etc/ssh/host_key* >> /var/lib/lrpkg/sshd.conf > 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. I've been aiming to create the ability to use unmodified packages with a configuration file which configures the system. This means, then, that a user can set up a configuration file on the network somewhere, boot with a standard downloaded disk image, and use this image with perhaps a few configuration changes (for the config file) to run their firewall / router / whatever. This also means that a developer can configure their system so they can work on it, then a release comes down to: # mount /mnt/boot # cd /mnt/boot # rm config.lrp # cd / ; umount /mnt/boot ...and voila! Distributable image. SSH is a perfect example of why this is necessary. One doesn't want to give out your private keys, eh? > 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. Nahhh..... just fix sshd.conf.... _______________________________________________ Leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
