[2898] in Release_7.7_team
Fwd: Problems with updating recently loaded machines
daemon@ATHENA.MIT.EDU (Bill Cattey)
Mon Aug 13 21:39:31 2001
Message-ID: <IvS85EJz0001ENHmNe@mit.edu>
Date: Tue, 14 Aug 2001 01:39:28 +0000 ()
From: Bill Cattey <wdc@MIT.EDU>
To: release-team@MIT.EDU
It is news to me that the 6.004 lab is trying to use Linux Athena.
This is an important beach head for further inroads into acceptance
of the Athena way in the EECS Dept.
I'm hesitant to provide the technical advice needed here for
fear I'd get it wrong. But it seems to me that:
1. The 6.004 machines SHOULD go to Athena 9.0.
2. The work-around is to remove ypbind temporararily, and restore it
after the update.
3. The SMP problem is being worked on. (Or does 9.0.14 have that fix in it?)
I notice that amb is not on linux-dev where this note originally went.
amb or ghudson: Could you sort this guy's problem out?
-wdc
---------- Forwarded message begins here ----------
Date: Mon, 13 Aug 2001 19:12:31 -0400
From: Chris Terman <cjt@lcs.mit.edu>
To: linux-dev@mit.edu
CC: Chris Terman <cjt@lcs.mit.edu>
Subject: Problems with updating recently loaded machines
[If there's a better place to send this info please let me
know -- Thanks.]
After loading several different machines in the 6.004 lab
last week using the SIPB-IS linux-boot-floppy, running
update_ws (either automatically or manually) to version
8.4.25 causes the kernel-smp package to be erased. This
seems to break detection of the eth0 interface on reboot and
subsequently the ifup script in sysconfig/network-scripts fails
since eth0 is not found by ifconfig. Both machines (an HP XU6/200
and a Dell Optiplex GX1) actually had dual-processor motherboards,
and the Dell had a second processor installed. However, the
vanilla 6.001 workstations seem have to suffered the same failure.
Attempts to run "update_ws 9.0" produces the following
conflict report:
Update would break dependencies:
yp-tools is needed by ypbind-1.7-0.6.x
*** The update has failed ***
Neither problem is crucial, but it would be nice to be able to
keep the 6.004 lab machines on autoupdate and to eventually
migrate to the 2.4 kernel, so any hints as to workarounds would
be helpful. Thanks.
- Chris
