From: "Robert P. J. Day" <rpjday@mindspring.com>
To: Andrew Morton <akpm@digeo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5.66-bk12 causes "rpm" errors
Date: Sun, 6 Apr 2003 22:04:51 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.44.0304062200570.1604-100000@localhost.localdomain> (raw)
In-Reply-To: <20030406183234.1e8abd7f.akpm@digeo.com>
On Sun, 6 Apr 2003, Andrew Morton wrote:
> "Robert P. J. Day" <rpjday@mindspring.com> wrote:
> >
> >
> > got 2.5.66-bk12 to boot on my inspiron 8100, and ran
> > "rpm -q iptables", got the following:
> >
> > rpmdb: write: 0xbfffc2d0, 8192: Invalid argument
> > error: db4 error(22) from dbenv->open: Invalid argument
> > error: cannot open Packages index using db3 - Invalid argument (22)
> > error: cannot open Packages database in /var/lib/rpm
> > package iptables is not installed
> >
>
> Does it work OK with earlier 2.5 kernels?
sorry, i couldn't tell you about that.
> The only change which comes to mind is the below one. Could you do a
> patch -R of this and retest?
... patch deleted ...
that fixed it, but i only this second noticed the "-R" for reversing
the patch. i applied it normally against my 2.5.66-bk12 tree, and
it apparently applied cleanly.
wouldn't that suggest that that patch wasn't in my tree in the first
place? i'm sure i'm up to bk12 at this point.
rday
next prev parent reply other threads:[~2003-04-07 1:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-07 1:18 Robert P. J. Day
2003-04-07 1:32 ` Andrew Morton
2003-04-07 1:41 ` Robert Love
2003-04-07 1:47 ` Robert Love
2003-04-07 11:45 ` Alan Cox
2003-04-07 14:53 ` Robert Love
2003-04-07 14:17 ` Alan Cox
2003-04-07 1:49 ` Robert Love
2003-04-07 2:59 ` J Sloan
2003-04-07 12:07 ` Robert P. J. Day
2003-04-07 2:04 ` Robert P. J. Day [this message]
2003-04-07 1:28 ` Andrew Morton
2003-04-07 3:15 ` Robert Love
2003-04-07 3:19 ` Robert Love
2003-04-07 3:29 ` Andrew Morton
2003-04-07 3:35 ` Robert Love
2003-04-07 9:05 ` Felipe Alfaro Solana
2004-04-20 8:10 Fred Shaul
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=Pine.LNX.4.44.0304062200570.1604-100000@localhost.localdomain \
--to=rpjday@mindspring.com \
--cc=akpm@digeo.com \
--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
all inboxes | Powered by JetHome®