| Date Of Receipt: 27-JUL-1995 18:58:42.51
From: SMURF::FLUME::jmf "Joshua M. Friedman OSF/UNIX SDE 27-Jul-1995 1857"
To: kinstler@DEC:.zko.flume
CC: odehelp@DEC:.zko.flume
Subj: Re: Problems after moving sandbox
Bob, you can outdate anything you created.
If you moved your sandboxes entirely, and there was no corruption, you
can just continue on; to outdate work you've done, from within a workon,
do
bcs -u file file file
to unlock any files bco'd but not bci'd, and
bcs -o file file file
to outdate the branches. You can combine -u -o if you need to do both;
you can also use -all instead of file file file if you want to start over
for everything.
If your sandbox was corrupted and you're in a sandbox with another name
you can use the "-set <setname>" option in the bcs command, where the setname
is the original sandbox name if you haven't explicitly used any sets.
-josh
> Hi,
> I am in UNIX Support Engineering and am experiencing some
> trouble after moving my sandboxes to a new disk drive.
> Could you contact me about this? I would like to have
> some branches outdated so I can start over. This trouble
> involves v32supportos and perhaps v30supportos.
>
> Thanks.
>
> Bob Kinstler
|
| Date Of Receipt: 28-JUL-1995 13:54:34.98
From: SMURF::FLUME::jmf "Joshua M. Friedman OSF/UNIX SDE 28-Jul-1995 1353"
To: kinstler@DEC:.zko.flume
CC: odehelp@DEC:.zko.flume
Subj: Re: Problems after moving sandbox
Bob, I called and left you a brief voicemail.
All the files you "bci"d are safe and sound in rcs, you can check
out the state you last checked in, unlocked (read-only) using:
bco -u -rRobert_Kinstler_setname file file file
(setname == sandbox name if you don't explicitly use sets)
The only problem is that there are files in your sandbox which ODE needs
to track the state of these files, called
src/.BCSconfig
src/.BCSset-Robert_Kinstler_setname
These can be recreated if need be, the you should get assistance for that.
If you can't workon because of corruption, that's one thing, but you
may not be able to due to mount dependencies. Check your sandbox 'link'
to see what it points to, and make sure you have that mounted.
If it points to something which no longer exists, you can manually resb
your sandbox as follows; eg say you were backed to ptos.bl5, which has
been deleted, and you want to back to ptos.bl7
(as root) /usr/sde/odemount ptos.bl7
(now as you...)
cd <your sandbox>
ls -l link ... shows link -> /usr/sde/..../ptos.bl5
rm link
ln -s /usr/sde/osf1/build/ptos.bl7 link
workon -sb name
resb ptos.bl7 (will clean up a few things)
exit
workon -sb name
If that's not the issue, and you really want to start over, first try:
mksb -undo sandboxname
It will complain if that sandbox references files in the .BCS* files.
The easiest thing is to workon to that sandbox and outdate them; if need be
you can workon to another sandbox and outdate them using the -set option
I explained earlier (attached), then "rm" that sandbox's .BCS*
files, then do the mksb -undo.
Be aware that it's important to outdate the bci'd files if you really want
to start from scratch or they can interfere later, since they're still
under your private branches in rcs (do a blog [-r] on the file to see this).
Give me a call if you have more questions.
-josh
------
Josh-
Suppose my sandboxes are totally screwed up and I can't workon
any? I'd like to wipe the filesystem and my .sandboxrc and
start over. Can I recover the files I have checked out or
do I need an administrator to outdate them? Why don't we talk
on the phone? I'm at 1-6156.
Bob Kinstler
--------
To: kinstler
Cc: odehelp
Subject: Re: Problems after moving sandbox
Date: Thu, 27 Jul 95 18:57:18 -0400
From: "Joshua M. Friedman, OSF/UNIX SDE 381-1548" <jmf>
Bob, you can outdate anything you created.
If you moved your sandboxes entirely, and there was no corruption, you
can just continue on; to outdate work you've done, from within a workon,
do
bcs -u file file file
to unlock any files bco'd but not bci'd, and
bcs -o file file file
to outdate the branches. You can combine -u -o if you need to do both;
you can also use -all instead of file file file if you want to start over
for everything.
If your sandbox was corrupted and you're in a sandbox with another name
you can use the "-set <setname>" option in the bcs command, where the setname
is the original sandbox name if you haven't explicitly used any sets.
-josh
> Hi,
> I am in UNIX Support Engineering and am experiencing some
> trouble after moving my sandboxes to a new disk drive.
> Could you contact me about this? I would like to have
> some branches outdated so I can start over. This trouble
> involves v32supportos and perhaps v30supportos.
>
> Thanks.
>
> Bob Kinstler
|