Re: [osol-help] upgrade 78 to 81 with problems - help needed with Gnome startup

2008-02-05 Thread Uwe Dippel
Closed case. Though I had tried everything to get X back, finally needed to swap in Lars' /etc/passwd, for everything to came up. Now I swapped back in my old /etc/passwd, it reads as it always read: offers /root to 'root', and everything still works perfectly well. Somewhere on the way somethin

Re: [osol-help] upgrade 78 to 81 with problems - help needed with Gnome startup

2008-02-04 Thread Uwe Dippel
Hi, Lars, I might try tomorrow, though I seem to understand that you want to truss the X logon. It does work, and I guess it reads HOME from /etc/passwd. When I run an xterm, env is perfectly well and okay. But also, it is vastly different from real console. The problem of the strange HOME only

Re: [osol-help] upgrade 78 to 81 with problems - help needed with Gnome startup

2008-02-04 Thread Lars Tunkrans
Well it may work better but its not exactly solved, is it. What I would do is to truss(1M)a login session . Logon to the root account from another PC using SSH or telnet or whatever . Find the dtlogin deamon for the VGA screen, process 646 in the example below.

Re: [osol-help] upgrade 78 to 81 with problems - help needed with Gnome startup

2008-02-03 Thread Uwe Dippel
bash-3.2$ cat /etc/passwd root:x:0:0::/root:/usr/bin/bash If I remove the /root *only from /etc/passwd* but leave the /root directory, and make /etc/passwd: root:x:0:0:Super-User:/:/sbin/sh X starts properly. HOME for user anyuser is still at '/', but there are at least read permissions. No, on

Re: [osol-help] upgrade 78 to 81 with problems - help needed with Gnome startup

2008-02-03 Thread W. Wayne Liauh
> We have installed SX81 in a few additional machines. > I can confirm that the problem has nothing with > editing the passwd file. Rather, it was caused by > nautilus crash. After a couple of reboots, nautilus no longer crashes. Everything seems to be normal now. (Self-healing feature of Sol

Re: [osol-help] upgrade 78 to 81 with problems - help needed with Gnome startup

2008-02-02 Thread W. Wayne Liauh
We have installed SX81 in a few additional machines. I can confirm that the problem has nothing with editing the passwd file. Rather, it was caused by nautilus crash. In previous versions of SXCE, nautilus will be immediately restarted after a crash. This does not seem to be the case with 81

Re: [osol-help] upgrade 78 to 81 with problems - help needed with Gnome startup

2008-02-02 Thread Uwe Dippel
[i]I have had a look into the Solaris security toolkit , download link below. So what did you do exactly ? [/i] Full of confidence into a history of Unix, vi /etc/passwd [cf. OpenBSD] to change the parameters for root. That was all. [i]You had snv78 installed with some modifications . Did you do

Re: [osol-help] upgrade 78 to 81 with problems - help needed with Gnome startup

2008-02-02 Thread Lars Tunkrans
Yes I see the SPACE in my post . These seems to be artifacts of the web posting mechanism. The space is not there in the original file . I have had a look into the Solaris security toolkit , download link below. http://www.sun.com/download/products.xml?id=42e6becd after installtion,

Re: [osol-help] upgrade 78 to 81 with problems - help needed with Gnome startup

2008-02-02 Thread Uwe Dippel
Thanks, Lars, though curious, give me 1.5 days until I'm back at work. [No, I don't feel like updating my machine at home for the time being. It has the similar introduction of /root, though working properly in nv78: bash-3.2$ pwd /export/home/udippel bash-3.2$ whoami udippel bash-3.2$ cd bash-3

Re: [osol-help] upgrade 78 to 81 with problems - help needed with Gnome startup

2008-02-02 Thread Lars Tunkrans
Sorry there is an error introduced by the web posting mecahnism in my port of the passwd file the "daemon" and "bin" users should not be on the same line. lets try again : root:x:0:0:Super-User:/:/sbin/sh daemon:x:1:1::/: bin:x:2:2::/usr/bin: sys:x:3:3::/: adm:x:4:4:Admin:/var/adm: lp:x:71

Re: [osol-help] upgrade 78 to 81 with problems - help needed with Gnome startup

2008-02-02 Thread Lars Tunkrans
Hi, This is the default snv81 passwd file , If you change you passwd file manually be sure to run the pwconv(1M) utility afterwards. to SYNC the passwd and the shadow file. //Lars root:x:0:0:Super-User:/:/sbin/sh daemon:x:1:1::/: bin:x:2:2::/usr/bin: sys:x:3:3::/: adm:x:4:4:Admin:/v

Re: [osol-help] upgrade 78 to 81 with problems - help needed with Gnome startup

2008-02-01 Thread W. Wayne Liauh
In one of our machines (which has a nVidia 6150 GO chipset), SX81 "ate" the /export/home/$HOME directory. We couldn't run anything on the GNOME ("i/o error", /export/home/$HOME missing). This never happened before. We will file a bug report. Perhaps you should also do the same. This messa

Re: [osol-help] upgrade 78 to 81 with problems - help needed with Gnome startup

2008-02-01 Thread Uwe Dippel
I used the new installer ... Fine, let's assume nv81 doesn't like the reassignment of (root's) HOME. Do you mind posting your /etc/passwd, so that I can swap it in here, to exclude any other snag? (Everyone knows that there are no secrets any more in that file.) If I start to edit mine, I might

Re: [osol-help] upgrade 78 to 81 with problems - help needed with Gnome startup

2008-02-01 Thread Uwe Dippel
Sure, that is my 'invention', with /root for root. And I don't see anything wrong at that. Everything worked in nv70 and 78, as it is, (I only upgraded) and - yes - I have read passwd(4) and login(1) and now I hope for some way to go back to my desktop, because that's my desktop at work. [i]So

Re: [osol-help] upgrade 78 to 81 with problems - help needed with Gnome startup

2008-02-01 Thread Lars Tunkrans
I have installed B81 my self now as an Initial Install using the SXCE old installer: There is no /root directory not on the filesystem , not in /etc/passwd and the $HOME variable works as excpected. So Im afraid that whatever the problem is you have caused it yoursel

Re: [osol-help] upgrade 78 to 81 with problems - help needed with Gnome startup

2008-02-01 Thread Lars Tunkrans
There is a SPACE in the shell path for testo in the passwd file fragment you posted isten:x:37:4:Network Admin:/usr/net/nls: gdm:x:50:50:GDM Reserved UID:/: webservd:x:80:80:WebServer Reserved UID:/: postgres:x:90:90:PostgreSQL Reserved UID:/:/usr/bin/pfksh svctag:x:95:12:Service Tag UID:/:

Re: [osol-help] upgrade 78 to 81 with problems - help needed with Gnome startup

2008-02-01 Thread Lars Tunkrans
from the Bourne shell manual : HOME The default argument (home directory) for the cd command, set to the user's login directory by login(1) from the password file (see passwd(4)). Does Build 81 introduce the /root

Re: [osol-help] upgrade 78 to 81 with problems - help needed with Gnome startup

2008-02-01 Thread Uwe Dippel
Somewhat further: As to be expected, % env for each and any user returns HOME=/root. Meaning, I can export the correct directory, and then % cd works fine, bringing me back to each user's HOME under /export/home/. If I was still on Linux, I might have been able to start X with % startx or similar

Re: [osol-help] upgrade 78 to 81 with problems - help needed with Gnome startup

2008-02-01 Thread Uwe Dippel
not quite. But your hint was, I guess, good: Script started on Fri Feb 01 16:45:21 2008 bash: /root/.bashrc: Permission denied bash-3.2$ whoami testo bash-3.2$ pwd /export/home/testo bash-3.2$ ls -l total 168538 drwx-- 2 testostaff512 Feb 1 13:43 Mail -rw--- 1 testosta

Re: [osol-help] upgrade 78 to 81 with problems - help needed with Gnome startup

2008-01-31 Thread Lars Tunkrans
what you describe happens if the user is not the owner of the users home directory . or not the owner of all the dot-files . ( ie .gnome2 .gconfd ) //Lars This message posted from opensolaris.org ___ opensolaris-help mailing lis

[osol-help] upgrade 78 to 81 with problems - help needed with Gnome startup

2008-01-31 Thread Uwe Dippel
Made the straightforward upgrade from 78 to 81; after nobody yelling about problems with 81. I do have some; in short: Gnome seems to kill X and get me back to the login applet. Okay: upgrade went through without any warnings or errors. Reboot. kernel dumped and restarted; this time okay. Next