> I'm attaching the handly patch. > It works on snv_77 however I recommend you find > another applications based on gtk+-2.0 as putty > depends on XLFD based fonts with gtk+-1.2. > > putty-0.60/README: > - For the graphical utilities, Gtk+-1.2 is > required. Gtk+-2.0 is not > yet supported. > env LD_LIBRARY_PATH=/usr/lib/gtk-2.0/modules putty [...]
Thanks - that worked great on snv_66 also. Once the issues in getting putty to build on (Open)Solaris without patches are resolved, I hope it will be considered for inclusion in the appropriate consolidation, since I know there are people (not me!) who are familiar with it from Windows and would find some of its features convenient (even if not strictly necessary) on Solaris too. For instance, given a mixed implementation of console servers (serial multiport, dedicated boxes like Cyclades, SC or RSC, etc), one can set up stored sessions that preserve the knowledge of the possibly varying procedures (including double-hops) needed to get to servers one supports from one's desktop; the alternative being a hunt through indifferently maintained site documentation. There are of course other solutions for uniform console access, but they may imply a single point of control over the entire infrastructure, which isn't the case some places. This lets one express the details onself in a form that's later usable with point-and-drool, in case one is running on too much caffeine and too little of everything else. (It would be nice if putty had an option to "export" selected (or all) stored sessions in a form that could be "imported" across Windows and Unix/Linux ports, since I gather the Windows port saves its stored settings in the registry rather than in files in $HOME/.putty (as the Unix/Linux port does). That would allow the settings needed to access systems to be set up by one person and passed to others that needed the same access, rather than typed in by each person.) This message posted from opensolaris.org
