[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
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 |
1408.0. "Config file differences for lsm_ted in nightly files" by AOSG::FILTER (Automatic Posting Software - mail to flume::puck) Tue Apr 18 1995 18:59
Date Of Receipt: 12-APR-1995 16:06:43.55
From: SMURF::WASTED::dbloemen "DALE BLOEMEN USG"
To: odehelp@DEC:.zko.wasted
CC: johnf@DEC:.zko.wasted (John Flanagan USG Test JOHNF Tools Group),
grist@DEC:.zko.wasted (Paul Grist OSG),
decwin::mccartney (Irene McCartney)
Subj: Config file differences for lsm_ted in nightly files
I've stumbled across some apparently nightly pool only configuration
file modifications for the lsm_ted device that nobody seems to know
how to handle. This affects the kernel/conf/alpha files. A
comparison between ptos/src/kernel/conf/alpha/SAS and ptos.nightly
src/kernel/conf/alpha/SAS gives the following:
6,9d5
< # Revision 1.2.139.7 1995/04/10 14:19:48 Harinder_Bhasin
< # Incorporated LSM TED, test suite, in the nightly build process.
< # [1995/04/07 19:17:47 Harinder_Bhasin]
< #
13c9
< #
---
> #
2242a2239
> pseudo-device lsm_ted 0
With the comment being in the ptos tree and the pseudo-device entry
being in the ptos.nightly tree. A diff of the files file in the same
sub-dir yields:
5,8d4
< # Revision 1.2.299.20 1995/04/10 14:20:08 Harinder_Bhasin
< # Incorporated LSM TED, test suite, in the nightly build process.
< # [1995/04/07 19:18:14 Harinder_Bhasin]
< #
12c8
< #
---
> #
2063a2060,2064
> #
> # LSM ted files
> #
> ted/ted.c optional lsm_ted Binary
> ted/tedSpace.c optional lsm_ted Binary
Again with the comment in the ptos tree and the files appearing in
the nightly tree.
I need to modify the GENERIC, SAS, PELICAN, FLAMINGO and files files
in the kernel/conf/alpha sub directory to defunct the PXG device. If
I check these files out of the ptos, which I've been doing, my build
against the nightly tree is broken. If I check them out of the nightly
tree, which has been suggested, then I face merge problems when I
submit to the ptos pool.
What is the "official" position on how to proceed?
Also, is there any chance that my srequests, ptos-107[23]-dbloemen
will be approved in time to make the pre-BL6 release?
Thank you,
Dale - [email protected] (603)881-1013
T.R | Title | User | Personal Name | Date | Lines |
---|
1408.1 | Re: Config file differences for lsm_ted in nightly files | AOSG::FILTER | Automatic Posting Software - mail to flume::puck | Tue Apr 18 1995 19:01 | 31 |
| Date Of Receipt: 12-APR-1995 16:34:56.94
From: SMURF::FLUME::johnf "John Flanagan USG Test Johnf Tools Group 12-Apr-1995 1633"
To: DALE BLOEMEN USG <dbloemen@DEC:.zko.flume>
CC: odehelp@DEC:.zko.flume,
johnf@DEC:.zko.flume (John Flanagan USG Test JOHNF Tools Group),
grist@DEC:.zko.flume (Paul Grist OSG),
decwin::mccartney (Irene McCartney)
Subj: Re: Config file differences for lsm_ted in nightly files
The files in the ptos submit tree [ptos] are the up to date files.
ptos.nightly
is now 2 days old due to bad builds. The latest bad build is reflected in
the tree called "ptos.nightly.standby".
I would make your changes in a pool backed by ptos, and do your builds in that
same sandbox.
John
______________________________________________________________________
John Flanagan enet: [email protected]
MS: ZKO3-3/W20 decnet: flambe::johnf
USG Release Engineering (603) 881-1719
110 Spitbrook Road (DTN) 381-1719
Nashua, NH
______________________________________________________________________
|