All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Paul G. Allen" <pgallen@randomlogic.com>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"kplug-list@kernel-panic.org" <kplug-list@kernel-panic.org>
Subject: Re: Kernel 2.4.7 Source Code Documentation
Date: Fri, 03 Aug 2001 20:17:08 -0700	[thread overview]
Message-ID: <3B6B6934.262D382A@randomlogic.com> (raw)
In-Reply-To: <3B6A2CC8.7D17F96F@randomlogic.com>

A slight change in plans:

www.randomlogic.com was out of disk space, so I now have a second site at http://www2.randomlogic.com. I am uploading the tar now and will uncompress the HTML
to:

http://www2.randomlogic.com/linuxkernel/

BIG NOTE READ THIS:


Anyone wishing to mirror this can download it from here:

http://www.randomlogic.com/files/linux-2.4.7_html.tar.gz

The file is in the neighborhood of 150MB and uncompressed is ~1GB. You have been forewarned. Please, no Wget on www2.randomlogic.com. :/

I'm still hoping for a better place to put it, but we'll see.

PGA

"Paul G. Allen" wrote:
> 
> I am attempting to get my slow UP PIII 800 here at work to parse the 2.4.7 source and annotate it so that I can put it up on my other web server. When it is
> done, I will upload it to the server and it should be available at this URL:
> 
> http://www.randomlogic.com/kernel/
> 
> This may or may not happen tonight since this machine is nowhere near as fast as my K7 at home and the K7 takes a few hours to do it all, but the U/L bandwidth
> is much better here (DS3 compared to cable). I do expect to have it up before the weekend.
> 
> (NOTE: I compared kernel compile times between the two, no official numbers, just compiling on both machines. I started the PIII 800 about 1 min before the K7
> Thunder. The K7 Thunder was done with make dep, bzImage, modules, and modules_install before the PIII was 50% complete with bzImage. The K7 was running 2
> SETI@Home sessions as well as compiling, the PIII was doing nothing else.)
> 
> I plan to update the documentation with every stable kernel release. (So please, don't crank them out too fast, I'd hate to spend my life U/L 1GB+ of HTML every
> other day!! ;-)
> 

-- 
Paul G. Allen
UNIX Admin II/Programmer
Akamai Technologies, Inc.
www.akamai.com
Work: (858)909-3630
Cell: (858)395-5043

  reply	other threads:[~2001-08-04  3:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-03  4:47 Kernel 2.4.7 Source Code Documentation Paul G. Allen
2001-08-04  3:17 ` Paul G. Allen [this message]
2001-08-04  3:36   ` Paul G. Allen
     [not found]     ` <3B6B6EEB.EAE86@Bellsouth.net>
     [not found]       ` <3B6B74EA.4648AAF2@randomlogic.com>
     [not found]         ` <3B6B76AA.A4526246@Bellsouth.net>
2001-08-04  4:52           ` Paul G. Allen
2001-08-04  5:28             ` Paul G. Allen
2001-08-06 21:37               ` Brent D. Norris
2001-08-08  3:50                 ` 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=3B6B6934.262D382A@randomlogic.com \
    --to=pgallen@randomlogic.com \
    --cc=kplug-list@kernel-panic.org \
    --cc=linux-kernel@vger.kernel.org \
    /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.