TUX installation

[Prabha nair]

Sir
  thanx for your reply
  But do u actually mean that u agree with TUX or u dont agree with TUX.I
cant get it from your reply.
  If u know some more details please do infm me sir
  It will be great help for me
  Thanks in advance
  Regards
  Prabha

On Sat, Sep 19, 2009 at 9:39 AM, Kursad Keskinege <keskinege at gmail.com>wrote:

> I totally agree with TUX & nginx
> K
>
>
> On Fri, Sep 18, 2009 at 5:58 PM, Ryan Lynch <ryan.b.lynch at gmail.com>wrote:
>
>> TUX is dead.  There has not been any new development on TUX for about
>> 4 or 5 years, now.  Also, this mailing list is almost dead--I'm only
>> subscribed because I forgot about it.  Unless you want to write the
>> updates, y ourself, TUX will never work on a recent 2.6 Linux kernel.
>>
>> But TUX is also completely unnecessary, today--the 2.6 kernel can
>> provide nearly the same static file serving performance as an the 2.4
>> kernel did with TUX, and the stability is significantly better.  TUX
>> died because it no longer serves a purpose.
>>
>> If you want to serve static files very efficiently, and you want to
>> support large numbers of simultaneous HTTP sessions, then there are
>> some modern options.  Nginx is the current favorite, I think.
>>
>> Ryan B. Lynch
>> ryan.b.lynch at gmail.com
>>
>>
>>
>> On Fri, Sep 18, 2009 at 06:38, Prabha nair <shrudhavishal at gmail.com>
>> wrote:
>> > Hi,
>> >   I am trying to install TUX server for my project in Grid
>> >   I find that the patches are available for TUX only till 2.6.18.
>> >   I tried with the latest versions of kernel 2.6.29..but it didnt work
>> >   So I compiled the source of 2.6.18 version and patched the
>> TUX3-2.6.18-1
>> > and it got compiled
>> >   I got a TUX package tux-3.2.21.tar.gz for userspace utility.
>> >   But the problem is that when I try to do
>> >   # make
>> >    It leads to some many errors regarding the declaration
>> >   Can U please help me out to how to rectify this error
>> >   Thnx in advance
>> >
>> >   Error:
>> > ln -s tux3.h tux.h
>> > gcc -g -fomit-frame-pointer -O2 -Wall -I. -DINTERFACE_VERSION=3
>> > -D_LARGEFILE64_SOURCE  -I/usr/include/glib-2.0
>> -I/usr/lib/glib-2.0/include
>> > -c tux.c
>> > tux.c:51: error: expected declaration specifiers or ‘...’ before ‘tux’
>> > tux.c:51: error: expected declaration specifiers or ‘...’ before
>> ‘action’
>> > tux.c:51: error: expected declaration specifiers or ‘...’ before ‘req’
>> > tux.c:55: warning: return type defaults to ‘int’
>> > tux.c: In function ‘_syscall2’:
>> > tux.c:74: error: storage class specified for parameter ‘nr_threads’
>> > tux.c:75: error: storage class specified for parameter ‘shared_buf’
>> > tux.c:76: error: storage class specified for parameter ‘shared_idx’
>> > tux.c:76: error: parameter ‘shared_idx’ is initialized
>> > tux.c:78: error: storage class specified for parameter ‘max_module_idx’
>> > tux.c:78: error: parameter ‘max_module_idx’ is initialized
>> > tux.c:79: error: storage class specified for parameter
>> ‘handle_events_array’
>> > tux.c:82: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before
>> ‘{’
>> > token
>> > tux.c:91: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before
>> ‘{’
>> > token
>> > tux.c:107: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’
>> before
>> > ‘{’ token
>> > tux.c:117: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’
>> before
>> > ‘{’ token
>> > tux.c:126: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’
>> before
>> > ‘{’ token
>> > tux.c:131: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’
>> before
>> > ‘{’ token
>> > tux.c:159: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’
>> before
>> > ‘{’ token
>> > tux.c:260: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’
>> before
>> > ‘{’ token
>> > tux.c:265: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’
>> before
>> > ‘{’ token
>> > tux.c:274: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’
>> before
>> > ‘{’ token
>> > tux.c:324: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’
>> before
>> > ‘{’ token
>> > tux.c:341: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’
>> before
>> > ‘{’ token
>> > tux.c:358: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’
>> before
>> > ‘{’ token
>> > tux.c:363: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’
>> before
>> > ‘{’ token
>> > tux.c:376: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’
>> before
>> > ‘{’ token
>> > tux.c:623: error: old-style parameter declarations in prototyped
>> function
>> > definition
>> > tux.c:51: error: parameter name omitted
>> > tux.c:51: error: parameter name omitted
>> > tux.c:51: error: parameter name omitted
>> > tux.c:623: error: expected ‘{’ at end of input
>> > make: *** [tux.o] Error 1
>> >
>> >
>> >
>> >
>> > _______________________________________________
>> > tux-list mailing list
>> > tux-list at redhat.com
>> > https://www.redhat.com/mailman/listinfo/tux-list
>> >
>>
>> _______________________________________________
>> tux-list mailing list
>> tux-list at redhat.com
>> https://www.redhat.com/mailman/listinfo/tux-list
>>
>
>
> _______________________________________________
> tux-list mailing list
> tux-list at redhat.com
> https://www.redhat.com/mailman/listinfo/tux-list
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/tux-list/attachments/20090922/cd0443a3/attachment.htm>