X-pop3-spooler: POP3MAIL 2.1.0 b 4 980420 -bs-
Date: Tue, 8 Sep 1998 02:55:56 -0700
From: david <david AT kalifornia DOT com>
Message-Id: <199809080955.CAA08373@Midnight>
To: radek DOT stachowiak AT alter DOT pl
Cc: beastium-list AT Desk DOT nl
Reply-To: david AT kalifornia DOT com
Subject: Re: Rebuild the kernel of Redhat5.1!
In-Reply-To: <19980908111110.B3904@blue.alter.pl>
X-Mailer: XCmail 0.99.6 - with PGP support, PGP engine version 0.5
X-Mailerorigin: http://www.fsai.fh-trier.de/~schmitzj/Xclasses/XCmail/
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 7bit
Sender: Marc Lehmann <pcg AT goof DOT com>
Status: RO
Content-Length: 949
Lines: 21

Reply to mail from Radoslaw Stachowiak about Rebuild the kernel of Redhat5.1!
-----------------
> Quoting Shawn Leas (sleas AT ixion DOT honeywell DOT com):
>> Could have sworn I saw it on the kernel list a few months back.  Wonder if
>> anybody could testify to 2.0.36's pgcc-ability from experience?
> cache in such situation (about x00kb, while machine has 64M). After that I
> have to reboot it and everything goes fine. I think that this problem is
> caused by compiling kernel with pgcc.

I must strongly disagree.  We use pgcc for everything.  Our entire server
farm has pgcc kernels and they range from a few months of uptime to
>10months of uptime.

They are all very stable and exhibit no anomalies.  This is of course
using only -O2.

-d
-- 
Look, look, see Windows 98.  Buy, lemmings, buy!   
(c) 1998 David Ford.  Redistribution via the Microsoft Network is prohibited.
 for linux-kernel: please read linux/Documentation/* before posting problems