Hi!  I just browsed the LFS documentation, and they install a bunch of
tools from Net-Tools:

http://www.linuxfromscratch.org/blfs/view/svn/basicnet/net-tools.html

I think we should offer some of these tools via InetUtils.  I already
have an arp implementation that I never seem to find time to finish, so
I thought about starting with something smaller like the dnsdomainname,
domainname, nisdomainname and ypdomainname tools.  Then I realized our
hostname tool already implement all of this stuff.  However I believe we
should provide the commands with 'make install'.  What do people think
about:

1) Write small compatibility shell scripts that invoke 'hostname' with
the right parameters.  For example, the 'dnsdomainname' script would
invoke 'hostname -d'.

2) Extend the 'hostname' tool to allow that argv[0] influence its mode
of operation.  This is how Net-Tools work today, they have only one
program but it is hardlinked to all these names.  Letting argv[0]
influence mode of operation is a bit ugly, but there are some precedent
for it even in well-maintained projects like CoreUtils.

3) Install separate tools that implement the operation.  This would
result in better documentation, better --help output, etc.  Technically
the tools could share most of the code and simply use some #define and
#include's for the gist of the operations.

Thoughts?

/Simon

Reply via email to