From: David Weinehall <tao@acc.umu.se>
To: "Markus Hästbacka" <midian@ihme.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Uptime counter
Date: Sun, 1 Feb 2004 23:19:00 +0100 [thread overview]
Message-ID: <20040201221900.GE15492@khan.acc.umu.se> (raw)
In-Reply-To: <Pine.LNX.4.44.0402020006120.7215-100000@midi>
On Mon, Feb 02, 2004 at 12:07:40AM +0200, Markus Hästbacka wrote:
> On Sun, 1 Feb 2004, David Weinehall wrote:
> > On Sun, Feb 01, 2004 at 11:34:39PM +0200, Markus Hästbacka wrote:
> > > On Sun, 1 Feb 2004, David Weinehall wrote:
> > [snip]
> > > > Well, you're soon going to reboot to install the upcoming 2.0.40, right?
> > > > And I promise to release 2.0.41 before you've had 497 days of uptime
> > > > with that one... :-)
> > > >
> > > Of course :)
> > > But when you'll stop releasing stuff, then it's time to see that :)
> >
> > When I stop releasing stuff, it's time to upgrade to the 3.x kernel...
> >
> Never! This boxen is sticking with 2.0 :-)
> > [snip]
> >
> > > Btw, when is it coming? :-)
> >
> > When I've got enough feedback that 2.0.40-rc8 is working... Soon, very
> > soon. Unless, of course, you were talking about 2.0.41, which is quite
> > some time away... :-)
> >
> I see no problems with it, maybe I should do some tests or something? :)
Well, since most of the changes in the latest kernels involve
networking, trying it with various different network-adapters would be
interesting, and stress-testing the network-code in general.
If you have the hardware or a really good confidence, a recent
2.2-kernel to compare with and sufficient knowledge of C, have a look at
the network-drivers for a2065 and ariadne, both of which lack the
padding-fixes the other adapters have, since I didn't want to touch that
mess...
Regards: David Weinehall
--
/) David Weinehall <tao@acc.umu.se> /) Northern lights wander (\
// Maintainer of the v2.0 kernel // Dance across the winter sky //
\) http://www.acc.umu.se/~tao/ (/ Full colour fire (/
next prev parent reply other threads:[~2004-02-01 22:19 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-01 20:41 Markus Hästbacka
2004-02-01 20:51 ` Matti Aarnio
2004-02-01 22:07 ` Ludootje
2004-02-01 21:20 ` Matthew Reppert
2004-02-01 20:52 ` Måns Rullgård
2004-02-01 21:02 ` Christian Borntraeger
2004-02-01 21:16 ` Markus Hästbacka
2004-02-01 21:27 ` David Weinehall
2004-02-01 21:34 ` Markus Hästbacka
2004-02-01 21:44 ` David Weinehall
2004-02-01 22:07 ` Markus Hästbacka
2004-02-01 22:19 ` David Weinehall [this message]
2004-02-01 22:42 ` Markus Hästbacka
2004-02-01 21:56 ` Guillermo Menguez Alvarez
2004-02-01 22:36 ` Paul Jakma
2004-02-01 22:59 ` Markus Hästbacka
2004-02-01 23:04 ` David Weinehall
2004-02-02 7:20 ` Markus Hästbacka
2004-02-02 7:24 ` David Weinehall
2004-02-02 8:59 ` Markus Hästbacka
2004-02-01 23:47 ` Wakko Warner
2004-02-01 21:33 ` Tomasz Torcz
2004-02-01 22:10 ` Ludootje
2004-02-02 17:54 ` Valdis.Kletnieks
2004-02-02 18:37 ` Mike Fedyk
2004-02-04 16:24 ` Bill Davidsen
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=20040201221900.GE15492@khan.acc.umu.se \
--to=tao@acc.umu.se \
--cc=linux-kernel@vger.kernel.org \
--cc=midian@ihme.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®