All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Paul G. Allen" <pgallen@randomlogic.com>
To: Thomas Foerster <puckwork@madz.net>,
	"kplug-list@kernel-panic.org" <kplug-list@kernel-panic.org>,
	"kplug-lpsg@kernel-panic.org" <kplug-lpsg@kernel-panic.org>,
	"Linux kernel developer's mailing list" 
	<linux-kernel@vger.kernel.org>
Subject: Re: Linx Kernel Source tree and metrics
Date: Fri, 27 Jul 2001 02:25:16 -0700	[thread overview]
Message-ID: <3B61337C.D48F203A@randomlogic.com> (raw)
In-Reply-To: <200107270917.f6R9HUt19989@antimatter.net>

Thomas Foerster wrote:
> 
> Hi,
> 
> > For those interested, I have run the kernel (2.4.2-2) through a program
> > and generated extensive HTML reports including call trees, function and
> > data declarations, source code, and metrics. I plan to upgrade this to
> > the latest kernel and keep it up to date (as much as possible :), but I
> > am a) working with a kernel that I know currently runs on my dual
> > Athlon, and b) wanted to test this out and run it by the two lists
> > first.
> 
> > The URL is:
> 
> > http://24.5.14.144:3000/linux-kernel
> 
> [...]
> 
> It's forwarded to "127.0.0.1:3000", so no one can connect?! ;-)
> 

That figures. I'm about ready, to give this router back to my company -
I've had nothing but trouble since I got it. Things worked better when I
just used a Linux firewall/router to do all my routing and forwarding.
Arrgg!!

I'll see if I can make it listen to me and forward to the correct
internal IP and port. (that's the right port, but the wrong IP by far!
#8^)


PGA

-- 
Paul G. Allen
UNIX Admin II/Network Security
Akamai Technologies, Inc.
www.akamai.com

       reply	other threads:[~2001-07-27  9:31 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200107270917.f6R9HUt19989@antimatter.net>
2001-07-27  9:25 ` Paul G. Allen [this message]
2001-07-27  9:33   ` Linx Kernel Source tree and metrics Paul G. Allen
2001-07-27  9:53     ` Paul G. Allen
     [not found] <no.id>
2001-07-27 23:46 ` Alan Cox
2001-07-28  0:20   ` Paul G. Allen
2001-07-28  1:33     ` Paul G. Allen
2001-07-27  9:52 Thomas Foerster
2001-07-27 10:26 ` Paul G. Allen
2001-07-27 10:30 ` Neil Brown
2001-07-27 11:18   ` Jan-Benedict Glaw
2001-07-27 11:47     ` Paul G. Allen
  -- strict thread matches above, loose matches on Subject: below --
2001-07-27  8:58 Paul G. Allen
2001-07-27 12:52 ` Daniel Phillips
2001-07-27 13:08   ` Richard Gooch
2001-07-27 20:40     ` Paul G. Allen
2001-07-27 23:32       ` Paul G. Allen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3B61337C.D48F203A@randomlogic.com \
    --to=pgallen@randomlogic.com \
    --cc=kplug-list@kernel-panic.org \
    --cc=kplug-lpsg@kernel-panic.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=puckwork@madz.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.