Path: utzoo!attcan!uunet!cs.utexas.edu!sdd.hp.com!hp-pcd!hpcvlx!ronv
From: ronv@hpcvlx.cv.hp.com (Ronald Voll)
Newsgroups: comp.sys.hp
Subject: Re: How to fix faulty VUE installations (was: problem with VUE)
Message-ID: <101950155@hpcvlx.cv.hp.com>
Date: 27 Oct 90 02:27:30 GMT
References: <1990Oct24.104320.3025@anduin.cs.liverpool.ac.uk>
Organization: Hewlett-Packard Co., Corvallis, OR, USA
Lines: 100


> The bug with the shipped VUE is that the file /usr/softbench/config/softinit
> is not shipped with read access for all (chmod +r fixes it).

THIS IS NOT A PROBLEM FOR MOST USERS.  IF YOU USE UPDATE TO INSTALL VUE
YOU SHOULD NOT RUN INTO THE ABOVE CONDITION.  

The file /usr/softbench/config/softinit is not "shipped" with VUE.  It is
created when the "/system/VUE_RUN/customize" script is run.  

If there is an existing "/usr/softbench/config/softinit" file, it is
overwritten but the permissions remain unchanged.  If your original
"softinit" file was not readable by "other" it will continue to be
unreadable by "other".  This does indeed cause a problem for non-root
users of VUE. 

Another way this problem can occur is if root's umask is something like
026 so that files created by root are not readable by "other".


In either case
	chmod +r /usr/softbench/config/softinit
will fix the problem.  It should not be necessary to reinstall VUE
at this point.  We will try to prevent this problem from occurring
in future releases.

> Here's how I installed and fixed VUE from scratch as root (and, yes, I had no
> documentation either and did it off my own cuff !)...

> Getting from tape (yes, you should run update, but this was a beta-test):

While the procedure which follows in the original basenote is essentially
correct, there is ample opportunity for error.  I strongly recommend that
you use "update" which will do much of the work for you as the writer
of the base note has indicated.

> /system/VUE_FONTS/customize update

the above line should read (on an s300 system):
	/system/VUE_FONTS/customize HP-MC68020

>cd /usr/bin/X11
>mv X X.old
>mv /tmp/X.703P X
>chown bin X
>chgrp bin X
>chmod 755 X

I don't know where /tmp/X.703P came from but it is not from the 
VUE installation.

>cd /usr/lib/X11/app-defaults
>mvcp XSession
>vi XSession
>(Changed XSession*CommandPath and XSession*TimeZone)

"/usr/lib/X11/app-defaults/Xsession" is not part of the VUE product.  I
believe it belongs to the XEnvironment Desktop 1.0 product.


>3. /system/VUE_RUN/customize replaces xload and hpterm !
>   Old copies are saved in a directory called /usr/bin/X11/HPUX7_00.

If you are on a 7.03 system the /system/VUE_RUN/customize script will
save the Old copies of xload and hpterm in "/usr/bin/X11/HPUX7_03".
The associated man pages and nls message catalog files are also replaced.

>4. 'No Windows' mode will not work unless you removed the 2 from the 'cons'
>   line in /etc/inittab.

This is only true if your console runs on the ITE (bitmapped display).
If you run your console to an ascii terminal you may safely leave the
"cons" line alone.

> and then reboot with shutdown -r 0. Do the reverse to enable VUE.

While it will work to reboot the system, it is not strictly necessary.
You can simply change run levels (as root) by using:
	/etc/telinit n  -- where n is the desired new run level.

>5. Errors for a particular user are stored in $HOME/.vue/errorlog.
>   This is a *very important* file - it gives invaluable information
>   that should have been displayed when the error occurred of course.

Errors which occur BEFORE a user logs in are stored in:
	"/usr/lib/X11/vue/Vuelogin/Xerrors
Note that ".../Vuelogin" is a CDF directory on clustered systems.

>I hope all this helps. If you've used update to install VUE, a lot of
>the stuff will have been done for you, but the chmod +r bug fix is
>probably still needed.

By all means use update and avoid the hassle.  You probably will not
run into the permission problem with "/usr/softbench/config/softinit" unless
root has a funny umask or the file is already read protected.

>Richard K. Lloyd,       *** This is a MicroVAX II running VAX/VMS V5.3-1 ***

	Ron Voll
	Hewlett-Packard, ITO