From: Arnt Karlsen <arnt@c2i.net>
To: netfilter@lists.netfilter.org
Subject: Re: RedHat 8.0 upgrade problem 1.2.8
Date: Tue, 26 Aug 2003 15:47:32 +0200 [thread overview]
Message-ID: <20030826154732.3ce73dc3.arnt@c2i.net> (raw)
In-Reply-To: <04d101c36b8c$fedd3810$2288e7c0@promed.com.au>
On Tue, 26 Aug 2003 14:46:21 +1000,
"Stuart J. Browne" <stuart@promed.com.au> wrote in message
<04d101c36b8c$fedd3810$2288e7c0@promed.com.au>:
> >-----Original Message-----
> >From: netfilter-admin@lists.netfilter.org
> >[mailto:netfilter-admin@lists.netfilter.org] On Behalf Of
> >Jason S. Friedman
> >Sent: Tuesday, 26 August 2003 14:28
> >To: netfilter@lists.netfilter.org
> >Subject: RedHat 8.0 upgrade problem 1.2.8
> >
> >
> >I use RedHat and use the Redhat-provided RPMs for all my
> >server maintenance.
..this means you have _all_ erratas, no? I opened
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=89171
and it was closed with a fix in initscripts-7.26-1, can
anyone confirm this works?
> iptables 1.2.8 RPM's is listed as requring the newer kernel builds.
> They broke something, and sent out an erratta notification earlier (I
> got it this morning, but have not tried doing the updates yet).
>
> I'm picking the kernel modules in memory are from the olde version,
> thus requring you to reboot into a newer kernel, or continue using the
> older iptables for the moment.
>
--
..med vennlig hilsen = with Kind Regards from Arnt... ;-)
...with a number of polar bear hunters in his ancestry...
Scenarios always come in sets of three:
best case, worst case, and just in case.
next prev parent reply other threads:[~2003-08-26 13:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-26 4:28 RedHat 8.0 upgrade problem 1.2.8 Jason S. Friedman
2003-08-26 4:46 ` Stuart J. Browne
2003-08-26 13:47 ` Arnt Karlsen [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-08-26 13:07 Jason S. Friedman
2003-08-27 3:14 Jason S. Friedman
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=20030826154732.3ce73dc3.arnt@c2i.net \
--to=arnt@c2i.net \
--cc=netfilter@lists.netfilter.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