From: J Sloan <jjs@lexus.com>
To: Roy Sigurd Karlsbakk <roy@karlsbakk.net>
Cc: Arjan van de Ven <arjanv@redhat.com>,
linux-kernel@vger.kernel.org,
Tux mailing list <tux-list@redhat.com>
Subject: Re: TUX support?
Date: Tue, 22 Jan 2002 09:59:17 -0800 [thread overview]
Message-ID: <3C4DA875.6010403@lexus.com> (raw)
In-Reply-To: <Pine.LNX.4.30.0201221110030.5699-100000@mustard.heime.net>
My guess is Ingo is having lots of fun with
the O(1) scheduler and other kernel stuff
right now - I'd like to see a 2.5 branch of
tux myself, but things are probably moving
a bit quickly for that right now....
I'm sure tux is not going away, it was just
yesterday that Alex Kramarov submitted
a patch to provide expires support.
TuX is too good to go away!
jjs
Roy Sigurd Karlsbakk wrote:
>>>Does anyone know who's in charge of the Tux server now? I got excellent,
>>>responsive support and answers from Ingo in December, but now the mailing
>>>list and Ingo's updates seem to have died out...
>>>
>>If you demand answers you can always buy a support contract.... Red Hat
>>sells those for TUX you know...
>>
>
>I apologize...
>I don't demand answers. I just wondered if the mailing list and so is
>still online. I've submitted a couple of bug reports, and nothing's
>happened, so I wondered if Tux is being discontinued. In that case, I need
>to find something else ...
>
>--
>Roy Sigurd Karlsbakk, MCSE, MCNE, CLS, LCA
>
>Computers are like air conditioners.
>They stop working when you open Windows.
>
>-
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at http://www.tux.org/lkml/
>
prev parent reply other threads:[~2002-01-22 17:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-22 9:52 TUX support? Roy Sigurd Karlsbakk
2002-01-22 10:03 ` Arjan van de Ven
2002-01-22 10:12 ` Roy Sigurd Karlsbakk
2002-01-22 17:59 ` J Sloan [this message]
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=3C4DA875.6010403@lexus.com \
--to=jjs@lexus.com \
--cc=arjanv@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=roy@karlsbakk.net \
--cc=tux-list@redhat.com \
/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.