Joel Estes wrote:
> Bart Smaalders wrote:
You're not forced to use them for your own software;
put your libraries in /usr/local/lib or /opt/xxx and link
with that.
- Bart
I normaly do exactly that. But that still leaves the user with 481 MB of bloat
in /usr/sfw , most of which is not required by the core O/S. This does not
include the enormous bloat of Gnome, either. If OpenSSL is a requirement, the
suggestion was made to move it to /usr/lib, which is reasonable. Forcing the
user to install /usr/sfw with mysql, ImageMagick, and a host of other programs,
including a specific version of GCC and its libraries should _not_ be required
as part of the core O/S installation.
There's a super-barebones, core OS installation option that's fully
contained on "CD 1 of 4" called Reduced Network cluster (aka SUNWCrnet).
It installs a very minimal (less than 300 MB, I believe) set of packages
-- only one or two /usr/sfw packages gets installed, and zero X and
other GUI packages.
I played with SUNWCrnet a lot (coupled with the pkgsrc system) about a
year ago, and again just over the last few days. IMO, it holds a lot of
potential as a base for things like server appliance systems made from
self-compiled packages. Or, for the extremely adventurous, I discovered
that it's also feasible to use it as the base for a custom, personal
desktop implementation. In specific, start with SUNWCrnet, add to it by
hand the minimum required set of Sun's X Window packages to get a
barebones X platform, and then from that, marry it to a community
package repository and build up a lightweight (non-KDE/GNOME) "personal
desktop distro". I did a prototype using the pkg-get tool, the
CSW/Blastwave system, and the Xfce desktop environment with pretty good
results. I can write up what I did in more detail if anyone is
interested in trying it out.
Eric
_______________________________________________
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
