Re: Problems running Tux w/ 2.4.19 generic

SuSE Linux 8.1 ships tux with it's 2.4.19 kernel -

Which come to think of it is basically 2.4.19-aa -

You may want to grab the -aa patches for your
2.4.19 base, that's probably the easiest way to
get 2.4.19 + tux -

Joe

[email protected] wrote:

>Thank you for responding,
>
>I am unaware of any patch that has been ported to 2.4.19.  Is there a ported patch available somewhere?
>
>Yes I had several hunks fail, but as this is not my area of expertise, I am unable to create a work around.
>
>Only Logging, and redirect_logging are enabled, from reading past archive messages I had thought that referer_logging was causing the errors.  Should I disable all logging?
>
>Thanks
>
>-----Original Message-----
>From: Shane Allen [mailto:[email protected]]
>Sent: Wednesday, January 08, 2003 9:10 PM
>To: [email protected]
>Subject: Re: Problems running Tux w/ 2.4.19 generic
>
>
>On Wed, Jan 08, 2003 at 05:57:48PM -0600, [email protected] wrote:
>  
>
>>Hello,
>>
>>I am currently trying to run Red Hat 8.0 with Tux compiled into a 2.4.19 generic kernel.  I have applied the tux2-full-2.4.18-final-A3 patch.  Under what I consider is very minor work loads Tux will, for apparently no reason, drop all of its threads and stop responding to requests.    I realize that the patch was not intended for this kernel version, but it is necessary in order for my SMP machine to work properly.
>>
>>My question is this.
>>   Has anyone attempted to do this, and if so did you see the same problems?  If you didn't see the same problems, am I missing something?  If you did see the same problems, did you ever find a work around for this issue?
>>
>>Thanks. Joshua  
>>    
>>
>
>Did you use a patch that had been ported to 2.4.19?
>
>When you patched, were there any error messages saying "Hunk #N Failed"
>where N is an integer?
>
>I've patched 2.4.21pre2 with tux, but I had to modify the patch in order
>to make the patching successful.
>
>Also, there have been numerous threads on-list regarding tux hanging
>with logging enabled. Check the archives for that info, and try
>disabling logging if you have it enabled.
>
>  
>