Big thanks to:
"Brehl, Blake" <Blake.Brehl_at_anritsu.com>
Horst Dieter Lenk <lenk_at_mpi-muelheim.mpg.de>
Parkin Frank - fparki <fparki_at_acxiom.co.uk>
"Dr. Thomas.Blinn_at_Compaq.com" <tpb_at_doctor.zk3.dec.com>
In brief, the problem was doconfig failing to build a kernel, the reason
was due to incorrect timestamps on files, fix is to 'touch' the affected
files to update the date then it works. Original question and responses
follow, thanks again to all who responded!
-=-=-=-=-=-=- Original message -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
I have recently upgraded two alpha servers (AS800 5/400 and AS1000A 5/400)
from DU4.0D to T64 5.1A via 4.0F, including updating the firmware from the
v6.0 firmware CD.
The AS800 was no problem, minimum amount of post-upgrade work needed,
applied the first patch, all went well. The AS1000A was a very different
story. Although the install seemed to go ok, there was a problem with CDE
logins and many of the file creation times are wrong, many are Jan 1st
1970. I installed the recent patch, and when it tried to rebuild the
kernel, it failed. I rebooted anyway, and as it came up, the system
started the same basic X session it uses for the 5.n install, then ran at
least some of the post-install 'configure' scripts, then booted ok. Now
CDE works again, but I still can't build a kernel:
8<---------------------------------------------------------------
cc -c -O2 -DLANGUAGE_C -std0 -g3 -I -I. -I.. -I../include -DIDENT=TERI
-DDEC1000A_5 -DUERF -DOSF -DCOMPAT_43 -DMACH -DUFS -DFFM_FS -DRT_SEM
-DKERNEL -D_KERNEL -D_BSD -D_USE_KERNEL_PROTOS -compress -MD -no_excpt
-nointrinsics -Wg,-unroll,1 -Wb,-static -Wco,-nofloat -msg_disable
ptrmismatch1 -msg_enable cvtdiftypes,warnimplfunc,
ptrmismatch,macroredef,lvaluecast,uselesstyped -msg_inform
cvtdiftypes,warnimplfunc,ptrmismatch,macroredef,lvaluecast,uselesstyped
-msg_enable uninit1,falloffend,intrinsicint,outtoomany,outtoofew,
questcompare,storclsdcl,tentredef -msg_warn
uninit1,falloffend,intrinsicint,outtoomany,outtoofew,questcompare,
storclsdcl,tentredef -msg_enable othermember -msg_error othermember
-Umips -UMIPS -U__intel__ -D__alpha -D__digital__ -D__arch64__
-no_warnprotos ../kern/lockinfo.c
Make: Don't know how to make data/steal_mem.c. Stop.
8<---------------------------------------------------------------
The file /usr/sys/data/steal_mem.c exists and is not empty (though it
doesn't contain much..)
I've tried using the old config file or using doconfig to create a new
one, and I tried removing the old /usr/sys/HOSTNAME directory, none of
these help.
Any ideas?
-=-=-=-=- Response 1 -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
From: "Brehl, Blake" <Blake.Brehl_at_anritsu.com>
Simon,
This may not be it, but I just experienced the same doconfig failure when
installing the security patch before installing the pre-requisite patch
kit
1 (the 73 Mbyte file). Uninstall the subsets 89 and 90 (at that point it
will successfully do a doconfig), install the (large) 90 subset pk1, and
follow with the security patch (the kernel build then goes fine).
-=-=-=-=- Response 2 -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
From: Horst Dieter Lenk <lenk_at_mpi-muelheim.mpg.de>
Hi,
I have the same problem during 5.1 -> 5.1A update.
All my files in /usr/sys have the wrong date (1-Jan-1970).
find /usr/sys -type f -exec touch {} \;
set a valid date.
Then the doconfig can build a new kernel.
-=-=-=-=-=- Response 3 -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
From: Parkin Frank - fparki <fparki_at_acxiom.co.uk>
Hi Simon,
Hopefully you will have received an answer by now ...
If you haven't ... you have spotted the problem already i.e. those 1970
dated files.
I believe this is a gotcha when upgrading to v5.1a from a O/S without the
latest patch kit.
I think it's in the technical notes amongst the Compaq v5.1a
documentations.
The fix is to find all the files which have old dates and touch them
(mainly
.c and .so files).
-=-=-=-=-=-=- Response 4 -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
From: "Dr. Thomas.Blinn_at_Compaq.com" <tpb_at_doctor.zk3.dec.com>
There was a critical patch for all the older releases that fixed what
as I recall was a "year 2001" bug. Files read from ISO-9660 CDROM
were getting READ with the wrong date, and this impacts the base OS
stuff on the install media. If you didn't patch your old system,
then as the files were updated from the CDROM (using "pax" to copy
them, preserving their dates), you got "zero" dates (the value of
the date number is zero, which is Jan 1 1970 in UNIX interpretation).
You need to find all the files on your system that have the wrong
dates and "touch" them to make them be dated around the time that
the media was created. Alternatively, if you re-do the installupdate
on top of itself, all the files will get re-copied from the media but
with the CORRECT time stamps (the correct time stamps are present on
the CDROM, it's the old kernel that was misinterpreting them during
the reading, your new genvmunix kernel gets it right). Or you can
use the flavor of "touch" that uses some file as a reference, walk
the CDROM media and find the equivalent files and touch them with
the date from the CDROM.
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Simon
--
Simon Greaves Voice: +679 212114
Systems & Networks Fax: +679 304089
ITS, USP, Suva Email: Simon.Greaves_at_usp.ac.fj
Fiji
Received on Wed Feb 06 2002 - 03:52:30 NZDT