[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference smurf::buildhelp

Title:USG buildhelp questions/answers
Moderator:SMURF::FILTER
Created:Mon Apr 26 1993
Last Modified:Mon Jan 20 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:2763
Total number of notes:5802

1803.0. "BL8 kernel build" by AOSG::FILTER (Automatic Posting Software - mail to flume::puck) Mon Sep 11 1995 18:49

Date Of Receipt: 	11-SEP-1995 13:53:41.09
From: 	SMURF::ALPHA::"marier@zso.dec.com"
To: 	buildhelp@zk3.de.com
CC: 	odehelp@zk3.dec.com, mwarren@zk3.dec.com, daddamio@rust.zk3.dec.com,
	marier@rust.zk3.dec.com
Subj: 	BL8 kernel build

Mark Warren (mwarren@zk3.dec.com) recommended I ask you for help.

On Thursday (Sept 7th) I created a new sandbox to build a kernel
in.  This was backed to slugbt:/alpha_platinum/ptos, I then did
a mklinks -copy kernel as I needed a sandbox which would not change
out from under me.

After the kernel was built I booted it and now uname is reporting the
following

uname -a
OSF1 babylon5 X4.0 138 alpha
                   ^^^

Next I looketd at /etc/motd

Digital UNIX X4.0C-6  (Rev. 138); Fri Sep  8 17:05:51 PDT 1995 
                 ^^^^^^^^^^^^^^^
                                
As you can see it lists the kernel as C-6 and Rev 138.  The problem
is we should be on 4.0-8 (Rev 239) over a 100 revision different.

I've checked with other engineers which are backed to the same tree
and they are getting the same results.

HELP!!!!

T.RTitleUserPersonal
Name
DateLines
1803.1BL8 kernel buildAOSG::FILTERAutomatic Posting Software - mail to flume::puckMon Sep 11 1995 18:5544
Date Of Receipt: 	11-SEP-1995 14:19:02.73
From: 	SMURF::ALPHA::"marier@zso.dec.com"
To: 	buildhelp@zk3.dec.com
CC: 	
Subj: 	BL8 kernel build

------------- Begin Forwarded Message -------------

From marier Mon Sep 11 10:52:05 1995
To: buildhelp@zk3.de.com
Subject: BL8 kernel build
Cc: odehelp@zk3.dec.com, mwarren@zk3.dec.com, daddamio@rust.zso.dec.com,
        marier@rust.zso.dec.com

Mark Warren (mwarren@zk3.dec.com) recommended I ask you for help.

On Thursday (Sept 7th) I created a new sandbox to build a kernel
in.  This was backed to slugbt:/alpha_platinum/ptos, I then did
a mklinks -copy kernel as I needed a sandbox which would not change
out from under me.

After the kernel was built I booted it and now uname is reporting the
following

uname -a
OSF1 babylon5 X4.0 138 alpha
                   ^^^

Next I looketd at /etc/motd

Digital UNIX X4.0C-6  (Rev. 138); Fri Sep  8 17:05:51 PDT 1995 
                 ^^^^^^^^^^^^^^^
                                
As you can see it lists the kernel as C-6 and Rev 138.  The problem
is we should be on 4.0-8 (Rev 239) over a 100 revision different.

I've checked with other engineers which are backed to the same tree
and they are getting the same results.

HELP!!!!

------------- End Forwarded Message -------------


1803.2Re: BL8 kernel buildAOSG::FILTERAutomatic Posting Software - mail to flume::puckMon Sep 11 1995 20:0430
Date Of Receipt: 	11-SEP-1995 15:45:36.12
From: 	SMURF::FLUME::johnf "John Flanagan USG Test Johnf Tools Group  11-Sep-1995 1543"
To: 	Shawn Marier <marier@zso.dec.com>
CC: 	buildhelp@zk3.dec.com, johnf@DEC:.zko.flume
Subj: 	Re: BL8 kernel build

It appears that you were trying to build a kernel backed by the submit
tree.  The submit tree is not set up to support a legal kernel build. The
kernel config files for managing the namespace [i.e. X4.0-6 rev whatever]
are maintained in the build area and propogated only to the nightly and 
baselevel trees.  We suggest that you do your kernel builds backed by
either a nightly tree or a baselevel tree.  The kernel you ended up with,
though, should be functionally correct.  The datafiles for managing the 
namespace should be the only things out of rev.

John


 ______________________________________________________________________

 John Flanagan	 		enet:    johnf@zk3.dec.com	
 MS: ZKO3-3/W20			decnet:  flume::johnf
 USG Release Engineering		 (603) 881-1719
 110 Spitbrook Road 			 (DTN) 381-1719
 Nashua, NH  
 ______________________________________________________________________