Date: Mon, 13 Sep 2004 17:14:06 +0100 From: Matthew Seaman <m.seaman@infracaninophile.co.uk> To: Joshua Tinnin <krinklyfig@spymac.com> Cc: freebsd-questions@freebsd.org Subject: Re: Post Install Configuration Issues (ruby18 error) Message-ID: <20040913161406.GB83205@happy-idiot-talk.infracaninophile.co.uk> In-Reply-To: <200409122316.51822.krinklyfig@spymac.com> References: <5878D00B313A8D4E8D00B7E3082FC693067A1B@FF01.marsik.org> <413CA85B.9080500@makeworld.com> <200409122316.51822.krinklyfig@spymac.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--0eh6TmSyL6TZE2Uz
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Sun, Sep 12, 2004 at 11:16:51PM -0700, Joshua Tinnin wrote:
> On Monday 06 September 2004 11:11 am, Chris <racerx@makeworld.com>=20
> wrote:
>=20
> > Another way: - this changes the default database (btriev) to hash
> >
> > setenv PORTS_DBDRIVER bdb1_hash
> >
> > then run your portdb -u
> > In fact, I opted for this one. I now run my ports tree updating
> > scripts as I did BEFORE these issues.
>=20
> What sort of effect might this have elsewhere? I'm sure this fix works,=
=20
> but is there something else that could get borked by changing the=20
> default database?
The only two files this change might affect are /usr/ports/INDEX.db
and (possibly)[1] /var/db/pkg/pkgdb.db. In either case all it will cause
to happen is that the file will be replaced by a file using a
different on-disk data structure, but containing exactly the same
data. =20
As both of those .db files are created by the portupgrade(1) suite of
tools as a quick reference version of the data in
/usr/ports/INDEX{,-5} in one case, or /var/db/pkg in the other,
trashing the files is not the end of the world -- they can be rebuilt
fairly easily from scratch. Anyway it's only the portupgrade(1) tools
that are likely to be directly affected by that sort of corruption.
Cheers,
Matthew
[1] Actually, I think you'ld have to set PKG_DBDRIVER=3Dbdb1_hash to
affect /var/db/pkg/pkgdb.db similarly. However, the chances of that
file growing large enough to trigger the bdb1_btree bug are fairly
remote.
--=20
Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks
Savill Way
PGP: http://www.infracaninophile.co.uk/pgpkey Marlow
Tel: +44 1628 476614 Bucks., SL7 1TH UK
--0eh6TmSyL6TZE2Uz
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (FreeBSD)
iD8DBQFBRcdOiD657aJF7eIRAu/rAJ9k8AD7jz3xePKay43COaERIUiDnACdFhAs
X1lJEKEKDZnCYt1fjAoQWXs=
=biAI
-----END PGP SIGNATURE-----
--0eh6TmSyL6TZE2Uz--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040913161406.GB83205>