[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 |
2722.0. "Re: steelos.shadow odemountable but not useable" by AOSG::FILTER (Automatic Posting Software - mail to flume::puck) Wed Dec 11 1996 15:09
Date Of Receipt: 11-DEC-1996 14:47:41.51
From: FLUME::jmf "Joshua M. Friedman Digital UNIX"
To: mjr@DEC:.zko.flume
CC: odehelp@DEC:.zko.flume
Subj: Re: steelos.shadow odemountable but not useable
Mike, edit your ~/.sandboxrc and remove the definition of a default
sandbox; ie. you can just have the following near the top of the file:
# default sandbox
default
This will also make "workon" require an -sb argument, a good safety measure.
Occasionally you'll get a warning that you have no default sandbox, this is ok.
-josh
----------------
To: [email protected]
Subject: steelos.shadow odemountable but not useable
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 11 Dec 96 13:46:21 -0500
From: mjr
X-Mts: smtp
Status: R
Why does 'mksb' need to have my main sandbox's link be correct?
Notice that when it can't read the link, it claims that steelos.shadow
is not a known backing tree. Why is steelos.shadow good when there
is a main/link but no good without it?
Is there some way to not have a main sandbox so that I don't
need to keep futzing with main/link to point to backing trees
I don't care about just to make the ODE tools succeed?
-mike
(mksb works first time--fails on 2nd sandbox creation):
# /usr/sde/odemount steelos.shadow
# schnausser.zk3> mksb -back steelos.shadow steel_shadow
creating new set: Mike_Rickabaugh_steel_shadow, setdir: .
creating lock file for new set.
[ creating /usr/staff/mjr/sand/steel_shadow/tmp ]
/usr/staff/mjr/sand/steel_shadow/tmp: created directory
drwxr-xr-- 2 mjr system 8192 Dec 11 13:39
/usr/staff/mjr/sand/steel_shadow/tmp
schnausser.zk3> mksb -undo steel_shadow
schnausser.zk3> ls main
main not found
schnausser.zk3> mv sand/main/link sand/main/link.was
schnausser.zk3> mksb -back steelos.shadow steel_shadow
cannot find include file ../link/rc_files/shared.sharedsandbox
>> FATAL ERROR in mksb:
>> No Access to Backing Tree Through link dir:/advfs0/mjr/sand/main/rc_f
iles/../link
Error parsing rc description file ./shared
>> WARNING in mksb:
>> unable to parse sandbox rcfile /usr/staff/mjr/sand/main/rc_files/loca
l.
cannot find include file ../link/rc_files/shared.sharedsandbox
>> FATAL ERROR in mksb:
>> No Access to Backing Tree Through link dir:/advfs0/mjr/sand/main/rc_f
iles/../link
Error parsing rc description file ./shared
>> WARNING in mksb:
>> steelos.shadow is not a known backing tree.
>> Will prompt for this information.
No known current backing trees to pick from.
Enter absolute path to backing tree:
T.R | Title | User | Personal Name | Date | Lines
|
---|