[3393] in SIPB_Linux_Development
Re: outstanding bugs
daemon@ATHENA.MIT.EDU (Angie Kelic)
Tue Mar 20 01:22:18 2001
Message-Id: <200103191229.HAA05142@tomcat.mit.edu>
To: Jonathon Weiss <jweiss@MIT.EDU>
cc: linux-dev@MIT.EDU
In-reply-to: Your message of "Mon, 19 Mar 2001 02:40:29 EST."
<200103190740.CAA06282@Bearing-An-Hourglass.mit.edu>
Date: Mon, 19 Mar 2001 07:29:15 -0500
From: Angie Kelic <sly@MIT.EDU>
krb5-configs does not (and should not) get installed by the
installer. None of my sipb installer installed machines have
the krb5-configs package. Some of my layered machines did, because
this package gets installed by redhat by default. Having this
package installed would cause updates to fail due to the
conflict. It is my belief that the user attempted to do something
clever and that the install doesn't install the krb5-configs
package. If anyone has had a different experience, please feel
free to comment.
>[2955]
>Somehow, my kerberos realm defaulted to "EXAMPLE.COM".
>This prevents athena users from logging in with xlogin.
>I'm not sure who owns the /etc/krb5.conf file:
> bash# rpm -qf /etc/krb5.conf
> athena-krb5-8.4-10
> krb5-configs-1.1.1-9
>We need to figure out if krb-configs is sometimes geting installed
>after athena-krb5 for some reason. There may have been discussion of
>doing an install and saving the install log and seeing whether there
>was anythign interesting in it, but no one ever dealt. Does this need
>to be requalified as mysterious lossage since it is working for other
>people?
This got fixed. We're installing 8.4.20 with current redhat
packages. I believe we verified this on the snork install.
(Though of course it can be verified again by a reinstall of
whacker or any other machine...)
>[3354]
>We're installing old versions of some RedHat packages. (I thought
>we'd fixed this, did I just miss the mail in my scan?)
I'm willing to believe the one below was just freakishness
on the part of writing the partition table and perhaps related
to lossage using the "back" button -- I have tried other installs
with custom partitioning that did the right thing.
>[3187] [3188] [3189] [3190] [3191]
>sly: 4g partition ended up with a 1g filesystem on it
Perhaps we should run an install before/during the meeting tonight
to verify some of the fixes that haven't been tested.
--Angie
