[4692] in Release_7.7_team
Re: Problem with 9.3 update
daemon@ATHENA.MIT.EDU (Jonathan R. Birge)
Wed Jul 14 16:50:19 2004
Date: Wed, 14 Jul 2004 16:50:15 -0400 (EDT)
From: "Jonathan R. Birge" <birge@MIT.EDU>
To: Greg Hudson <ghudson@MIT.EDU>
cc: release-team@MIT.EDU
In-Reply-To: <1089836783.13906.13.camel@equal-rites.mit.edu>
Message-ID: <Pine.LNX.4.58L.0407141639030.1491@birge.mit.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Greg:
You were right on with the grub intuition. You are clearly one of those
people who has a gift for solving problems. It didn't even occur to me to
think of the boot loader being the problem. My grub.conf file got screwed
up somehow during the upgrade. All the Athena entries had the 'single'
command added to them when the kernel entries were updated. I'm sure the
reason for this is related to the fact that I'd messed around with my
grub.conf file a bit, deleting the single-user option and adding other
entries for Windows XP and my diagnostics partition. Obviously the
installer wasn't happy with the fact that I'd edited out some of the
original Athena entries.
Anyway, I'm afraid I don't remember the errors I got during installation.
I'm also having problems with fonts changing after the update. For
example, some of the fonts in Gnome are now tiny. Changing the desktop
font to be larger then makes them normal, but now other fonts are huge.
Also, changing the window font results in really crazy fonts being used
(i.e. not the one you selected). Has this been experienced by others or
is this suggestive of my install having gone bad?
Thanks again,
Jonathan
______
Jonathan Birge, Research Assistant
Ultrafast Optics and Quantum Electronics Group
Research Laboratory of Electronics
Massachusetts Institute of Technology
77 Massachusetts Avenue
Cambridge, MA 02139
office: 36-397
e-mail: birge@mit.edu
phone: 617-253-4186
fax: 617-253-9611
web: www.rle.mit.edu/qoptics
web: web.mit.edu/birge
-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: 2.6.2
mQCNA0B8nAMAAAEEALcY7URlU+oDCO5Aj8zhf8QLu8Wd3mhHXH2gLyFzjiZNsi17
3fvsffrdvqftrLGqLtB7E0o+m9UtvokUW/cvUmDJ64U+tj10hWFJRQE7ie3a//Ps
PMiHcV6waz7PtYF+HEE7TCbcuBBPsPxnnEc0Y8j8Lw+UEFmdX8wBn8zA9HJlAAUR
tCFKb25hdGhhbiBSLiBCaXJnZSA8YmlyZ2VAbWl0LmVkdT4=
=bPLH
-----END PGP PUBLIC KEY BLOCK-----
On Wed, 14 Jul 2004, Greg Hudson wrote:
> On Wed, 2004-07-14 at 15:23, Jonathan R. Birge wrote:
> > I made a mistake when originally updating my personal Athena
> > workstation: I ran the update_ws program during an X session instead
> > of in a console window. At the end of the install, there was an error.
>
> I don't suppose you remember anything about the error? Normally,
> updating from an X session works fine, although it's not what we
> recommend.
>
> > I then shutdown X and reran the update from a console windows. This
> > succeeded, or at least that's what the update program said. However,
> > when I reboot, the startup process stops in the middle and throws me
> > into a shell. No error messages appear to be generated, it just stops
> > and I get a root prompt. However, if I do a 'telinit 5' then
> > everything continues and appears to work fine (I'm writing this from
> > the workstation, in fact). Do you know what happened?
>
> I don't know what happened. I can make two guesses:
>
> * Somehow, the default boot option became the option to boot
> single-user.
> * One of the init scripts is throwing you into a shell for some
> reason.
>
> If you send us your /boot/grub/grub.conf (or, if you don't have that
> file, /etc/lilo.conf), we can check out the first option. To check out
> the second one, run "ps auxw" from the shell prompt you get and look for
> a process like "/bin/sh /etc/rcN.d/SNNfoo start", and let us know what
> it is.
>
>
