North American Network Operators Group

Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical

Re: ARIN Policy on IP-based Web Hosting

  • From: Sean Doran
  • Date: Thu Aug 31 14:52:12 2000

Hm, this is vaguely about the tension in how network-friendly
to make applications...

Jim Mercer writes:

| just think how crippled make(1) would be without extensions.

Hm, let's see, in NetBSD's make(1) regime, the current has
the declarations below.  What stops you from using a different
suffix convention than <foo>".c" and friends?  I see no reason why
make(1) couldn't be extended to deal with arbitrary prefix/infix/suffix 
identifiers, or even something complicated like a set of regexps. 


CXX?=           c++

OBJC?=          ${CC}


# C
        ${LINK.c} -o ${.TARGET} ${.IMPSRC} ${LDLIBS}
        ${COMPILE.c} ${.IMPSRC}
        ${COMPILE.c} ${.IMPSRC}
        ${AR} ${ARFLAGS} [email protected] $*.o
        rm -f $*.o
        ${LINT} ${LINTFLAGS} ${CPPFLAGS:M-[IDU]*} -i ${.IMPSRC}

# C++
.cc .cpp .cxx .C:
        ${} -o ${.TARGET} ${.IMPSRC} ${LDLIBS}
.cc.o .cpp.o .cxx.o .C.o:
        ${} ${.IMPSRC}


Finally, compared to the equivalents in, for example, the Common LISP
universe, make(1) *IS* crippled, suffix-convention or not.

The assumption many network people have that "everything is an X",
for varous values of X (endianness, VAXishness, Microsoftishness, UNIXish)
has always been a real problem, and has led to interesting problems
(e.g., taking a file froma TENEX machine, changing directories on
a VMS server).   HTTP for its sins does abstract away some of the
worst user-visible problems (e.g. do you need to care what platform
the web server is running on?)

The major problem I have with ftp, from the perspective of someone
trying to build networks, is that most clients generally do not
do passive-mode ftp by default, despite many years of harranguing
going waaaaay back to Vadim Antonov's argument for that here.

Another plug: NetBSD's ftp(1) man page says:

     epsv4       Toggle the use of the extended EPSV and EPRT commands on IPv4
                 connections; first try EPSV / EPRT, and then PASV / PORT.
                 This is enabled by default.  [with fallback to active on fail -smd]

This is, in my opinion, Doing The Right Thing.