[Info-vax] Samba still troublesome

[Rich Jordan]

On Jan 25, 8:18 pm, Rich Jordan <jor... at ccs4vms.com> wrote:
> We're upgrading a system from 1.1 ECO 1 to current (1.2 ECO 1).
> Actually its an imaged copy of the production system.  Per the docs
> when doing an upgrade you shut down Samba, then PRODUCT INSTALL
> SAMBA.  You don't spec a destination.  You only need to do that if you
> are moving Samba (in which case you first back up the tree, then
> product remove, then product install with the new destination, then
> restore the tree).
>
> So I'm expecting product removed from DRIVE1:[000000.] and new product
> installed to the same.  Instead it installs to DISK$ALPHASYS:[VMS
> $COMMON.]
>
> The new samba tree is totally unconfigured.  No upgrade going to
> happen here; its a brand new install.
>
> I'd just like to express my dismay at this obvious dislocation between
> the docs and actual behavior.
>
> Good thing we have backups.  Bad thing, a couple more hours of time
> wasted loading from tape.

Restored backups and tried again specifying the product install /
destination qualifier.  It removed 1.1-1 and installed 1.2-1 t the
same correct location.  However running the samba$config did not 'act'
the way the docs stated it would if upgrading an existing
environment.

By chance has anyone done a Samba upgrade (not install) to 1.2 or
1.2-1 and had it work as documented?