2 questions for newbies

Hi I'm totally new to solaris 5.9

Two questions.

  1. What is the replacement for /proc/cpuinfo (isn't this part of POSIX). I heard it's psrinfo but it doesn't work.
  2. I use ssh - v -X with X tunelling from linux onto a solaris server, but xclock failed. it says won't open display. $DISPLAY is empty, what should I do? I've seen other people using nedit so it's not a problem with the server's permission.

Everything is different in solaris, even the version of 'top' used in solaris 5.9 was written in 1996!. I wonder if solaris would start borrowing gnu ware without violating GPL.

what distro os linux you use ???

Solaris 9 is quite old though.

/proc/cpuinfo is not part of POSIX, it is a Linux peculiarity.
Please clarify "psrinfo doesn't work" and tell what information you need.

If other people access the same server through ssh and have no problem tunneling X11, the problem is on your side, not on the server one. Double check how do they launch ssh and what DISPLAY variable they got (they might use unencrypted direct X11 protocol).

There was no version of top bundled with Solaris 9. The Solaris standard equivalent command is prstat. Someone installed it from some freeware repository.

What makes you think the GPL would be violated ? Many (most?) of the Gnu software was initially developed on Solaris (or previous SunOS releases) and current Solaris releases actually include a lot of GPL licensed software, not to mention Sun own or contributed software that is licensed under the GPL.

fedora core 3

in Solaris restart ssh

svcadm restart ssh 

why to you connect via terminal when you can easily connect via GUI

in fedora go to places and choose Connect to server

a new window will open -> choose under service type SSH -> under server name enter IP of Solaris

and new login screen will appear here enter your username and password -> clik on connect and a Solaris local disc will appear

..and all of that is easier than typing ssh -X hostname ?
Besides, if he can't connect via CL, chances are the GUI is not going to work either, so it is much better to troubleshoot in CL.

He is using Solaris 9 so that won't work. If I remember correctly restarting ssh can be done like that:

pkill -HUP sshd