bug-inetutils
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: inetutils


From: Alain Magloire
Subject: Re: inetutils
Date: Sat, 2 Jun 2001 11:45:30 -0400 (EDT)

> 
> On Sat, Jun 02, 2001 at 05:20:08PM +0300, Sergey Poznyakoff wrote:
> > I've got some notices about talk/talkd in inetutils. Here they are:
> 
> Cool stuff!

Patches applied.

> > So how about your idea of breaking the stuff into libraries? Oh, by

Yes.

The idea is to be able to reuse those components.  Many times, I get friends
and co-worker that need it, to retreive quickly files from a server
whether FTP, TFTP etc ...  they hand up hacking quickly a short
lib for ftp or popen ("wget ftp://....";) etc ..
Also must of the utils comes BSD and some code look like it was written
by a high school student(Ok, I'm exagerating).  In any case since this
is after all free/hobby software.  Let's make it fun/good.

So the lets common out the the code so it can be usable
ftp --> libftp.a
tftp --> libtftp.a
rlogin/rsh/rexec --> librcmd.a
etc ....

#include <inetutils/ftp.h>

/* Higher level.  */
ftp_get ();
ftp_chdir ();

/* Protocol. */
ftp_user ();
ftp_pass ();
ftp_pasv ();
ftp_port ();
...

I don't know the API it is a suggestion.  But having reusable code
will certainly make me happy.
 
> > the way, what was the reason of including ifconfig in the package? The
> > stuff is heavily OS-dependent, it doesn't seem to belong here, does
> > it? Anyway, I am trying to make it compile and work on Solaris/x86
> > now...
> 
> I needed a place to put ifconfig for the GNU/Hurd system.  inetutils was
> just the best fit.  It is not finished, although it works as far as it is
> there, and we will see if and when we activate it for other systems beside
> the Hurd.  Patches are welcome, of course.  It should already be very
> compatible for the small set of features we support.  Note that the idea is:
> 
> To have a new set of (long) options which define the GNU ifconfig interface,
> common to all architectures.
> To remain backward compatible with the systems ifconfig on the command line
> for this architecture only.
> To be output compatible to the systems ifconfig by default (but the output
> format can be changed by the user with --format).
> 
> The more fancy features of the network interface configuration are of course
> quite different on different operating systems.  I am very unsure about how
> desireable it is to put these into this ifconfig.  The ifconfig in
> inetutils is modular to allow for system specific extensions, but we'll see
> how much interest there is in using it.  I'm satisfied with covering the more 
> or less
> common subset.

POSIX.1g at one point was suppose to come to the rescue in portability.
In theorie, I think ifconfig should compile on every platforms even
if all it does is return ENOSYS or ENOTSUP.

-- 
au revoir, alain
----
Aussi haut que l'on soit assis, on est toujours assis que sur son cul !!!




reply via email to

[Prev in Thread] Current Thread [Next in Thread]