[src/trunk]: src/usr.sbin/traceroute with luck this is the last one

[dholland <dholland%NetBSD.org@localhost>]

details:   https://anonhg.NetBSD.org/src/rev/38dcd527c07e
branches:  trunk
changeset: 755261:38dcd527c07e
user:      dholland <dholland%NetBSD.org@localhost>
date:      Sun May 30 00:52:06 2010 +0000

description:
with luck this is the last one

diffstat:

 usr.sbin/traceroute/README |  30 ------------------------------
 1 files changed, 0 insertions(+), 30 deletions(-)

diffs (34 lines):

diff -r 242acecf2502 -r 38dcd527c07e usr.sbin/traceroute/README
--- a/usr.sbin/traceroute/README        Sun May 30 00:50:25 2010 +0000
+++ /dev/null   Thu Jan 01 00:00:00 1970 +0000
@@ -1,30 +0,0 @@
-$NetBSD: README,v 1.1.1.4 1997/10/03 22:25:20 christos Exp $
-@(#) Header: README,v 1.8 97/01/05 04:15:36 leres Exp  (LBL)
-
-TRACEROUTE 1.4
-Lawrence Berkeley National Laboratory
-Network Research Group
-traceroute%ee.lbl.gov@localhost
-ftp://ftp.ee.lbl.gov/traceroute.tar.Z
-
-Traceroute is a system administrators utility to trace the route
-ip packets from the current system take in getting to some
-destination system.  See the comments at the front of the
-program for a description of its use.
-
-This program uses raw ip sockets and must be run as root (or installed
-setuid to root).
-
-A couple of awk programs to massage the traceroute output are
-included.  "mean.awk" and "median.awk" compute the mean and median time
-to each hop, respectively.  I've found that something like
-
-    traceroute -q 7 foo.somewhere >t
-    awk -f median.awk t | xgraph
-
-can give you a quick picture of the bad spots on a long path (median is
-usually a better noise filter than mean).
-
-Problems, bugs, questions, desirable enhancements, source code
-contributions, etc., should be sent to the email address
-"traceroute%ee.lbl.gov@localhost".