From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Ralf Hildebrandt <Ralf.Hildebrandt@charite.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.10-ac11 announcement?
Date: Tue, 1 Feb 2005 00:02:49 +0100 [thread overview]
Message-ID: <200502010002.50734.rjw@sisk.pl> (raw)
In-Reply-To: <1107158722.14787.68.camel@localhost.localdomain>
Hi,
On Monday, 31 of January 2005 09:05, Alan Cox wrote:
> On Sad, 2005-01-29 at 19:12, Ralf Hildebrandt wrote:
> > Where is the 2.6.10-ac11 announcement?
>
> Good question
>
> Arjan van de Ven is now building RPMS of the kernel and those can be found
> in the RPM subdirectory and should be yum-able. Expect the RPMS to lag the
> diff a little as the RPM builds and tests do take time.
>
> Nothing terribly exciting here security wise but various bugs for problems
> people have been hitting that are now fixed upstream, and also the ULi
> tulip variant should now work. If you are running IPv6 you may well want
> the networking fixes.
Is there a broken-out version of the patch available? It reboots at startup
(before it mounts the root fs) on my dual-Opteron box (SuSE 9.2), but -ac10
works fine, evidently. I could check which changeset actually caused this to
happen, but I'd need to separate them.
Greets,
Rafael
--
- Would you tell me, please, which way I ought to go from here?
- That depends a good deal on where you want to get to.
-- Lewis Carroll "Alice's Adventures in Wonderland"
next prev parent reply other threads:[~2005-01-31 23:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-29 19:12 2.6.10-ac11 announcement? Ralf Hildebrandt
2005-01-31 8:05 ` Alan Cox
2005-01-31 23:02 ` Rafael J. Wysocki [this message]
2005-01-31 23:19 ` Dave Jones
2005-01-31 23:09 ` Alan Cox
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=200502010002.50734.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=Ralf.Hildebrandt@charite.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).