Bug 2306 - Include a ThinLinc client for Solaris x86 in the product
Summary: Include a ThinLinc client for Solaris x86 in the product
Status: CLOSED WONTFIX
Alias: None
Product: ThinLinc
Classification: Unclassified
Component: Client platforms (show other bugs)
Version: trunk
Hardware: PC Solaris
: P2 Enhancement
Target Milestone: 4.5.0
Assignee: Peter Åstrand
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-01-05 13:30 CET by Peter Åstrand
Modified: 2015-08-14 09:22 CEST (History)
1 user (show)

See Also:
Acceptance Criteria:


Attachments

Comment 2 Marc 2014-02-14 04:38:32 CET
gentlemen,
I see that this was filed years ago and recently moved to a different group. Is there any work being done to support this? As you know, the sparc platform has been dying off for years and x86 is more substantially more dominant. Every SRS installation I have seen was on x86 so the sparc client for SRS support is virtually useless.
Comment 3 Peter Åstrand cendio 2014-02-17 08:17:01 CET
(In reply to comment #2)
> gentlemen,
> I see that this was filed years ago and recently moved to a different group. Is
> there any work being done to support this? As you know, the sparc platform has
> been dying off for years and x86 is more substantially more dominant. Every SRS
> installation I have seen was on x86 so the sparc client for SRS support is
> virtually useless.

No progress, unfortunately. Running the TL client on the SRS to provide access to ThinLinc from Sun Ray DTUs is also not an optimal solution. 

Anyhow, for an Solaris x86 TL client there are currently two options:

1) If you are willing to sign a NDA, you can get the TL client source code and try to build it yourself. 

2) We can also look at building the client for Solaris x86 as a consulting job, if you are interested.
Comment 4 Marc 2014-02-27 17:51:59 CET
Peter,
Thanks for the reply. Unfortunately I don't have to skills when it comes to the development side of the house so the source doesn't do me much good. I'm doing this for personal use at home, so consulting is also out of the question, heh. 

thanks for the response otherwise, i'm sure anyone else who is looking will find this useful.

Note You need to log in before you can comment on or make changes to this bug.