On Tuesday 28 February 2006 21:21, Levi Bard wrote:
<snip>
> The package chooser was nearly as impressive as the disk utility.
> First and most annoying, the packages were listed in some arbitrary,
> non-alphabetical order, in order to offer installers the enjoyment of
> scrolling up and down the entire list to find, say, a C compiler.
> Second of all, most of the packages had very poor descriptions, along
> the lines of:
> * jwxSUNW46: binary files for jwxSUNW46
> * jwxSUNW46-lib-dev: lib-dev files for jwxSUNW46
> (nowhere an explanation of what jwxSUNW46 was, or why we
> would/wouldn't want it, or if anything depended on it, or even if it
> was recommended for installation)
Are you sure you didn't install Solaris 8 by mistake? Brings back memories...
<snip>
> We logged in, chose Sun Java Desktop(GNOME) as our desktop
> environment, and within a few seconds were sitting in front of what
> looked like a Windows 2000 desktop. One thing I noticed is that many
> of the standard applications' menu items had been renamed. For
> example, instead of "Mozilla" and "The Gimp," we had "Web Browser" and
> "Image Editor."
Even Linux distros tend to do that to the application names, so that part
shouldn't be a huge surprise at least.
<snip>
> Since we had a working C compiler, we decided to install Galeon,
> Tosha's browser of choice. This required us to get much newer
> versions of the GTK+ libraries than the ones that had been installed.
> After chasing down all the requisites (glib, atk, pango, ...), we
> began compiling them. Unfortunately, no matter what we did, we were
> unable to get the GTK+ configure script to see that pango was
> installed, even by passing it the path. While it was perhaps not
> Solaris's fault that we couldn't build GTK+, the fact that there was
> only a poor selection of ancient software available for install
> certainly was, and this was the last straw for us. For crying out
> loud, we could have installed Slackware 8 and had the same currency of
> software, except it would have worked out of the box without a lot of
> futzing. We never got around to actually looking at or building the
> actual OpenSolaris source, because we were hoping for a usable system
> first. If you've actually read down this far, go get yourself a
> cookie; you've earned it.
If you were using gcc to compile, you'll notice it'll link stuff that may not
be found at runtime. Solaris has a pretty basic list of runtime stuff
available. You might want to try `crle` (I think) and add stuff
like /usr/local/lib and maybe /opt/lib to your runtime linker path for stuff
installed from SFW. (Make sure you include /lib and /usr/lib first, as if
you don't include them in the list of paths you'll end up stuff not
finding /lib and /usr/lib...)
You've kind of dissuaded me from trying Open Solaris.
--Jason Boxman http://edseek.com/ - Linux and FOSS stuff
----------------------------------------------------------------------- This list is provided as an unmoderated internet service by Networked Knowledge Systems (NKS). Views and opinions expressed in messages posted are those of the author and do not necessarily reflect the official policy or position of NKS or any of its employees.
This archive was generated by hypermail 2.1.3 : Fri Aug 01 2014 - 19:02:34 EDT