You're going to have trouble with WS, it's not supported and is missing several packages that SRSS depends on.

Jim Kusznir wrote:
I'm installing on a RHEL WS4 (which is essentially identical to an AS4 build; we used WS4 as this is going to be replacing a bunch of workstations and we have all the software and build scripts developed for WS already.

So, I went to Sun's download page cited in another e-mail in this group and downloaded SRSS 3.1.1 for Linux. I moved it to /tmp and unzipped it, and tried to run the utinstall script. This failed with numerous directory errors, whcih after googling, I found the one-line add to make a 3rd directory in tmp. I rerean the script, it asked if it was OK to uninstall RedHat's GDM, I said yes. It then went to install GDM and the rest of the packages and errored out on GDM with "no such file or directory". When I took a look, the file was in fact not there....

I just re-extracted srss and found GDM is there now. Its the same version (3.1.1), but I think it was a copy I downloaded a few weeks ago rather than the one I just downloaded and used for my install attempt cited above.

Previous attempts were aborted with the utinstall script errors, or I tried to manually install the RPMs when the utinstall script didn't work. All these attempts failed miserably.

So now, after starting with a fresh extract of the tarball combined with the utinstall mod, the install actually worked. Now off to try and config it.

--Jim

On 3/16/07, *Craig Bender* <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> wrote:

    Jim,
    Are you using SRSS 3.1.1?  Which flavor of RHEL are you using (ES or
    AS)?  I've installed 3.1.1 many time on CentOS which as you know is
    identical to RH.  There are a couple of workarounds required, but
    nothing along the lines of the gdm not being present.  Can you walk us
    through utinstall from beginning to end?

    Regarding the second part, when you first described what you were trying
    to solve it sounded like CAM with SGD would meet you needs.  It sounded
    like you wanted users to be able to access different linux servers
    without having SRSS installed on those servers.  It can indeed do that.
      You can put the Sun Ray Server in kiosk mode and have it run the SGD
    client.  There would be no solaris login involved.  Users would
    authenticate to SGD and get a set of applications which could be full
    screen linux desktops offering Gnome, KDE, etc.



    Jim Kusznir wrote:
     > Hi all:
     >
     > I've posted in the past with a form of this problem.
     >
     > I have several sunrays that I would like to serve up a linux terminal
     > server (the main login will default to this system all the
    time...the
     > user just sits down, wiggles the mouse, and there presented with
    a login
     > screen to this linux box).  I've heard from many sources that this is
     > perfectly doable and is being done.  I've had people write bits and
     > pieces as to how its done.  Unfortunately after working on it on
    and off
     > for over a month now, I'm no closer to making it happen.
     >
     > Method 1: Install SRSS on the linux box (it is a RHEL4 system -- a
     > supported configuration)
     > Problems: numerous bugs in the installer.  The current "hard wall" is
     > that the archive downloaded from sun is missing the GDM rpm (the
     > directory structure is there, there's just no files in
    it).  Based on
     > the large number of major bugs in the installer I've had to work
    around
     > so far, and now this one, it appears Sun hardly even tests these
     > releases, if at all...  In any case, if anyone knows how to actually
     > install SRSS on RHEL4, I'd greatly appreciate knowing how and
    where to
     > get the working files.
     >
     > Method 2: Use some sort of desktop roming system such that the
    sunray's
     > boot from a SUN server (running Solaris 10) and display a different
     > (linux) box.  I've seen references to SGD and CAM, but the only
     > information I've found on these seem to have nothing to do with
     > accomplishing what I've said above: having the thin clients
    display as
     > their login this linux terminal ( i.e, it is NOT ok to require
    the users
     > to double-login or log into a sun server, then start a program that
     > opens a window into the other terminal server).  Its also NOT ok to
     > require the users to select "remote server" from the options popup on
     > the default solaris xdm, and then select the other systems.
     >
     > Either solution would be fine, but I'm rapidly running out of
    time, and
     > may have to ditch the sunray's all together if I can't make this work
     > very soon.
     >
     > Thanks!
     > --Jim
     >
     >
     >
    ------------------------------------------------------------------------

     >
     > _______________________________________________
     > SunRay-Users mailing list
     > [email protected] <mailto:[email protected]>
     > http://node1.filibeto.org/mailman/listinfo/sunray-users
    _______________________________________________
    SunRay-Users mailing list
    [email protected] <mailto:[email protected]>
    http://node1.filibeto.org/mailman/listinfo/sunray-users



------------------------------------------------------------------------

_______________________________________________
SunRay-Users mailing list
[email protected]
http://node1.filibeto.org/mailman/listinfo/sunray-users
_______________________________________________
SunRay-Users mailing list
[email protected]
http://node1.filibeto.org/mailman/listinfo/sunray-users

Reply via email to