| > In low end systems running dropbear as a standalone service consumes | > memory. However dropbear supports running the service from inetd.conf so | > please offer installation choices like: | > | > 1) Run as service (at boot) | > 2) Run from inetd (uses less memory) | > | > The line to add to inetd.conf would be: | > | > ssh stream tcp nowait root /usr/sbin/tcpd /usr/sbin/dropbear -i | > | > This can be easily done during installation using: | > | > update-inetd --group RPC --add "ssh stream tcp nowait root /usr/sbin/tcpd /usr/sbin/dropbear -i" | | I don't want that. (1) I don't like debconf questions for package | configuration options; (2) I don't recommend running dropbear under | inetd, better use tcpsvd from ipsvd, if not standalone; (3) it's trivial | for an administrator to do manually.
I would consider using debconf as a service to the end users that install Debian packages. Dropbear does support inetd, so it should be irrelevant for the maintainer how the end user selects to install it. The comments could always be recorded to README.Debian if needed. Debian offers good tools to manage inet.conf, so it would enhance the dropbear package if it made use of them. Manual install is alwys more tedious than a good packaging in the long run. Not to mentioo package removals (how can one remember all manual tweakings?) Jari -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
