--=-PO6znGijFrZ4iHxv3m88 Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Mon, 2002-06-17 at 12:42, Robert G. Brown wrote: > A suggestion: >=20 > Put a very simple yum.conf suitable for Duke in the man page OR comment > out the updates and finished sections in the distribution rpm. >=20 > Both the [updates] and [finished] sections will cause yum to fail even > if pointed at e.g. install.dulug.duke.edu/pub/linux/updates (a > reasonable guess). It is also hard to see what they are for from man > yum.conf, and whether or not yum will work without them. Might be nice > to add a comment or two regarding purpose, at least... >=20 > Empirically,=20 >=20 > [main] > cachedir=3D/var/cache/yum > debuglevel=3D2 > logfile=3D/var/log/yum.log >=20 > [server] > name=3D7.3 main > baseurl=3Dhttp://install.dulug.duke.edu/pub/linux/dulug-7.3/i386 >=20 > # [updates] > # name=3D7.3 updates > # baseurl=3Dhttp://install.dulug.duke.edu/pub/linux/updates/ >=20 > # [finished] > # name=3Ddulug finished rpms > # baseurl=3Dhttp://localhost/finished/ I was planning on adding a pointer to the man page in the conf file - sean's suggestion. =20 > seems to work locally. I'm trying a running update from 7.2 -> 7.3 as I > write this and it is telling me that it is getting a very long list of > .hdr files, so I presume that it is working. It'll take a while to know > for sure over a DSL line...;-) the stock distributed yum doesn't need a duke-specific conf file. The one in the dulug distro has a duke-specific conf file, though. Icon did a 7.1 -> 7.3 upgrade this weekend, and excluding a few hiccups had few problems. -sv --=-PO6znGijFrZ4iHxv3m88 Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQA9Dhbk1Aj3x2mIbMcRAvsaAJoD0K+0AmGiKt177b0jxHvrYP+eQgCgj7L7 5/60mopmgbWXYYx4Y4nyLQ8= =vRXE -----END PGP SIGNATURE----- --=-PO6znGijFrZ4iHxv3m88--
