Firstly, nice job and great work to everyone working on this project. I have used the packages to build an intranet server, and it works extremely well. I'm really looking forward to the kolab and v2 release.
In my mind, one of the critical components of any standard enterprise server system is backup and restore capability. At my organization, we have been using amanda for this, fairly successfully. I noticed that there is no amanda openpkg package. I have previously rolled my own amanda rpms, and, despite being used as an example in the rpm book (http://rikers.org/rpmbook/node108.html), it is, IMO, notoriously difficuly to package well. I am willing to put some effort into creating an openpkg amanda rpm, but am looking for some advice. In particular:
1) (Sorry, first more of a user list question) Before I bother, is there a different strategy that people are using for backup that is already integrated within openpkg.
2) Amanda normally uses inetd/xinetd. This, of course, makes cross-platform packaging more difficult. I have not yet been able to find an example openpkg rpm that uses inetd/xinetd to see how that problem has been solved. Alternately, it would be possible to use a package like tcpserver to avoid using inetd. I am not sure which is the better approach, or if there is another better approach I haven't thought of.
3) It is normally sane to compile amanda with a restricted list of udp ports. This makes firewall configuration a bit simpler and somewhat more secure. However deciding which and how many ports depends on the installation. I could implement a with_restricted_ports build option, but are there other ways of solving this?
4) amanda includes client and server portions. Would it be best to have separate packages, or include a "with_client_only" mode?
Thanks much in advance,
Scott
______________________________________________________________________ The OpenPKG Project www.openpkg.org Developer Communication List [EMAIL PROTECTED]
