Free solaris sparc 10 software for linux

PkgTools are a set of utilities which are used to aid in the building of native Solaris packages. There are five separate utilities which are used to build packages, prepare a chroot() environment to install software into prior to building a package, copy package control scripts into place, a tool to aid in the starting of new projects, and a tool to check that packages are installed correctly.

Currently there are four tools in this set:

build-pkg
This is used to actually build the Solaris package, calling chroot-install if required.
chroot-install
A utility which creates an environment suitable for calling chroot() on and allowing the user to install software into it.
proj-template
A utility which asks the user questions and then copies files and directories from a specified template directory and performs macro expansion on them. This is designed to aid in the initial setup of the home directory of a new project.
simple-proj
A very similar utility to proj-template. However it does not ask questions and only deals with the setting up of a simple InstallPackage. This is useful when dealing with 3rd party software which just needs to have a number of package control scripts put into the package.
check-pkg
A utility which can be used to check to see if packages are installed correctly. It can also be given a pathname to check on which packages said pathname is a part of.

It should be noted that simple-proj is really proj-template wearing a different hat.

Sun::Solaris::Task is a Perl interface to Tasks.

SYNOPSIS

use Sun::Solaris::Task qw(:ALL);
my $taskid = gettaskid();

This module provides wrappers for the gettaskid(2) and settaskid(2) system calls.

Constants

TASK_NORMAL, TASK_FINAL.

Functions

settaskid($project, $flags)

The $project parameter must be a valid project ID and the $flags parameter must be TASK_NORMAL or TASK_FINAL. The parameters are passed through directly to the underlying settaskid() system call. The new task ID is returned if the call succeeds. On failure -1 is returned.

gettaskid()

This function returns the numeric task ID of the calling process, or undef if the underlying gettaskid() system call is unsuccessful.

Exports

By default nothing is exported from this module. The following tags can be used to selectively import constants and functions defined in this module:

:SYSCALLS settaskid() and gettaskid()

:CONSTANTS TASK_NORMAL and TASK_FINAL

:ALL :SYSCALLS and :CONSTANTS

Sun::Solaris::Privilege is a Perl interface to Privileges.

SYNOPSIS

use Sun::Solaris::Privilege qw(:ALL);

This module provides wrappers for the Privilege-related system and library calls. Also provided are constants from the various Privilege-related headers and dynamically generated constants for all the privileges and privilege sets.

Functions

getppriv($which)

This function returns the process privilege set specified by $which.

setppriv($op, $which, $set)

This function modified the privilege set specified by $which in the as specified by the $op and $set arguments. If $op is PRIV_ON the privileges in $set are added to the set specified; if $op is PRIV_OFF, the privileges in $set are removed from the set specified; if $op is PRIV_SET, the specified set is made equal to $set.

getpflags($flag)

Returns the value associated with process $flag or undef on error. Possible values for $flag are PRIV_AWARE and PRIV_DEBUG.

setppflags($flag, $val)

Sets the process flag $flag to $val.

priv_fillset()

This returns a new privilege set with all privileges set.

priv_emptyset()

This returns a new empty privilege set.

priv_isemptyset($set)

This function returns whether $set is empty or not.

priv_isfullset($set)

This function returns whether $set is full or not.

priv_isequalset($a, $b)

This function returns whether sets $a and $b are equal.

priv_issubset($a, $b)

This function returns whether set $a is a subset of $b.

priv_ismember($set, $priv)

This function returns whether $priv is a member of $set.

priv_ineffect($priv)

This function returned whether $priv is in the process effective set.

priv_intersect($a, $b)

This function returns a new privilege set which is the intersection of $a and $b

priv_union($a, $b)

This function returns a new privilege set which is the union of $a and $b

priv_inverse($a)

This function returns a new privilege set which is the inverse of $a.

priv_addset($set, $priv)

This functon adds the privilege $priv to $set.

priv_copyset($a)

This function returns a copy of the privilege set $a.

priv_delset($set, $priv)

This function remove the privilege $priv from $set.

LuBu OpenMagic is an enhancement of the Solaris OpenStep 1.1-sparc desktop enviroment.

It is not a rewrite, nor is it a re-release, but is a package that enhances and improves (and includes) Solaris OpenStep 1.1.

LuBu OpenMagic is only available for the SPARC architecture.

LuBu OpenMagic 1.0 is a heavily modified version of the Lighthouse OpenStep 1.1
release for the Sparc platform. It is not a theme, nor a reconfiguration, but
an almost pure rewrite of non-binary files (runtime configurations, application
definitions, enviroment variables, and many functions). In some parts entire functions
have been replaced features have been added. This applies primarily to the Wrapper
function which has been entirely rewritten to use the LuBu OpenMagic Alert System
(aka: LOAS). This is a completely new feature which among many other things also
produces error messages in human readable form, with the actual cause of the error.
This makes taking countermeasures and avoiding future errors easier. The default
application definitions provided with OpenStep 1.1 were the cause of countless bugs,
and I have spendt a great amount of time optimizing the default defs. There are still
a few bugs for which I have found no workaround, but non are critical.

OpenMagic 1.0 will only run on Sparc CPUs since it is based on Solaris OpenStep 1.1 for Sparc. There is not, nor will there ever be, a release for any other CPU. Since
LuBu OpenMagic 1.0 is based on the binary Solaris OpenStep release, it remains a
Solaris Sparc product. There are no known binaries for other CPUs or operating
systems. It does however fully integrate the Solaris Operating Enviroment, Common
Desktop Enviroment, and any other enviroments that run on Solaris Sparc. This makes it alot easier to integrate applications into the OpenStep enviroment without the need of porting.

LuBu OpenMagic 1.0 is packaged as a pure gzipped tar file, intended for unpacking
from the root directory (ie: / ). This means that the default installation directory for OpenStep should be /usr/openstep - it is importent that this rule is followed, else the installation will fail and the distribution will not function at all. It is however possible to extract to a different directory and create a symlink to /usr/openstep. Just remember to copy the etc/dt/config files to their desired location (/etc/dt/config). This is needed as there are some additional files included in order for LuBu OpenMagic 1.0 to function correctly:

1. A modified /etc/dt/config/Xservers file with -dpi 72
2. Configuration files for dtlogin (in /etc/dt/config/*.os|*.xpm)
3. Icons for /cdrom and /floppy (directories will be created if missing)

For an optimal installation:

$ su -
# cd /
# gtar zxvf /path/to/lubu_openwb-1.0-sparc.tgz

Make sure that all the files are extracted, and that existing files ARE overwritten! This will NOT reduce system security or in any other way reduce system performance.

Make sure all files in /usr/openstep are owned by bin:bin else you will loose alot of functionality! There is NO NEED for ANY of the files to be owned by root (other than possibly Preferences.app/set_password which is initially broken due to a missing library - see KNOWN_BUGS).

If you must chown /usr/openstep, then it is a good idea to cd to /usr before running chown -R in case you are using a non-standard chown. Worst case scenario is that a chown -R from / chowns your entire system bin:bin! Better safe than sorry.

# cd /usr
# chown -R bin:bin openstep/

If you extracted OpenStep to a different location, then cd to that location before running chown

# cd /path/to/your/installation
# chown -R bin:bin ../openstep (provided you actually are in the openstep directory)

Make sure the following line is present in /etc/dt/config/Xservers:
:0 Local local_uid@console root /usr/openwin/bin/Xsun :0 -nobanner -dpi 72
(this is however included in the distribution files and should be installed upon
extraction). For optimal performance it is best to run your display at -depth 24 -dpi 72

This file (Xservers) should be -rwx-xr-x otherwise run
# chmod 755 /etc/dt/config/Xservers

It is vital that dtlogin is restarted after installation. Exit your windowmanager, login as root to the system console, and run the following commands (as root):

# sh /etc/init.d/dtlogin stop
# sh /etc/init.d/dtlogin start

Now log out from the console and allow the dtlogin loginwindow to reappear.
Select "LuBu OpenMagic 1.0" from the session menu. Log in and enjoy!

It is however possible to run LuBu OpenMagic 1.0 without CDE installed, or without running it through dtlogin by simply starting the file /usr/openstep/bin/openstep:

$ sh /usr/openstep/bin/openstep

though you might loose some valuable configurations using this method.
It has not as of yet been tested thouroughly.

EasyBMP is a simple, cross-platform C++ library designed for easily reading, writing, and modifying Windows bitmap (BMP) image files. You can learn more about the history and goals of the project here.
The library is oriented towards the novice programmer with little formal experience, but it is sufficiently capable for anybody who desires to do I/O and pixel operations on 1-bit, 4-bit, 8-bit, 24-bit, or 32-bit BMP files.
EasyBMP is intended to be cross-platform on both little-endian (e.g., x86, x86-64) and big-endian (e.g., IBM PowerPC, Sun Sparc) architectures. So far, it has been tested on x86 with Linux (2.4.x, 2.6.x kernels and g++ and icc) and Windows (XP Pro, XP Home, and 2K Pro with MinGW/g++), as well as on a Sun Sparc 4 machine (Solaris 5.9 with g++). EasyBMP should be solid on little-endian architectures and experimental on big-endian architectures.
Enhancements:
- This bug focuses on minor bugfixes, particularly in the copy constructor.
- Numerous other small bugs have also been fixed.

Filaments is a library package that can be used to create architecture-independent parallel programs---that is, programs that are portable efficient across vastly different parallel machines. Filaments project virtualizes the underlying machine in terms of the number of processors and the interconnection.
This simplifies parallel program design in two ways. First, programs can be written (or generated) with the focus on the parallelism inherent in the application, not the architecture. Second, programs can be written that use familiar shared-variable communication.
Furthermore, Filaments uses a carefully designed API along with machine-specific runtime libraries and preprocessing that allow programs to run unchanged on both shared- and distributed-memory machines. Most importantly, applications programmed in Filaments run efficiently, achieving a speedup of over 4 on 8 processors or nodes in almost all tests that have been performed.
Platforms supported
Currently the following (homogeneous) architecture/OS combinations are supported:
- cluster of Sparc/Solaris
- cluster of X86/Solaris
- cluster of X86/Linux, kernel version 2.0.23 and above (older versions may work, but - have not been tested)
- multiprocessor SGI/Irix
- multiprocessor Sparc/Solaris
Note that Filaments does not run on heterogeneous platforms.