Free simplifying flexible isosurfaces using local geometric measures software for linux

MUNGE Uid N Gid Emporium is an authentication service for creating and validating credentials. It is designed to be highly scalable for use in an HPC cluster environment.
It allows a process to authenticate the UID and GID of another local or remote process within a group of hosts having common users and groups. These hosts form a security realm that is defined by a shared cryptographic key.
Clients within this security realm can create and validate credentials without the use of root privileges, reserved ports, or platform-specific methods.
Rationale
The need for MUNGE arose out of the HPC cluster environment. Consider the scenario in which a local daemon running on a login node receives a client request and forwards it on to remote daemons running on compute nodes within the cluster. Since the user has already logged on to the login node, the local daemon just needs a reliable means of ascertaining the UID and GID of the client process. Furthermore, the remote daemons need a mechanism to ensure the forwarded authentication data has not been subsequently altered.
A common solution to this problem is to use Unix domain sockets to determine the identity of the local client, and then forward this information on to remote hosts via trusted rsh connections. But this presents several new problems. First, there is no portable API for determining the identity of a client over a Unix domain socket. Second, rsh connections must originate from a reserved port; the limited number of reserved ports available on a given host directly limits scalability. Third, root privileges are required in order to bind to a reserved port. Finally, the remote daemons have no means of determining whether the client identity is authentic.
Overview
A process creates a credential by requesting one from the local MUNGE service. The encoded credential contains the UID and GID of the originating process. This process sends the credential to another process within the security realm as a means of proving its identity. The receiving process validates the credential with the use of its local MUNGE service. The decoded credential provides the receiving process with a reliable means of ascertaining the UID and GID of the originating process. This information can be used for accounting or access control decisions.
The contents of the credential (including any optional payload data) are encrypted with a key shared by all munged daemons within the security realm. The integrity of the credential is ensured by a message authentication code (MAC). The credential is valid for a limited time defined by its time-to-live (TTL). The daemon ensures unexpired credentials are not replayed on a particular host. Decoding of a credential can be restricted to a particular user and/or group ID. The payload data can be used for purposes such as embedding the destinations address to ensure the credential is only valid on a specific host. The internal format of the credential is encoded in a platform-independent manner. And the credential itself is base64 encoded to allow it to be transmitted over virtually any transport.
Enhancements:
- A bug was fixed that caused stack corruption on AMD-64 when using Libgcrypt.

PXES project is a micro Linux thin client distribution. PXES will boot a real thin client or will help to convert in minutes any compliant hardware (see list bellow) into a versatile thin client.
They will be capable of accessing any XDM server presenting the graphical login screen or any Microsoft Terminal Server through RDP protocol. The actual configuration of clients is made with an easy to use graphical configuration tool, allowing the specification of clients parameters or the server to access to.
You can recover hardware that is useless running current desktop OS or office package and give it a second chance. This thin client boots from the network with PXE (Intel Pre-Execution Environment specifications) so neither boot diskette nor boot eprom is needed.
The linux kernel and an initial root filesystem is transmitted over the network (the compressed size as of version 0.4 is about 4M).
Main features:
Supported servers and protocols
- Unix/Linux supporting XDM
- Microsoft Terminal Server using RDP
- Citrix using ICA
- VNC using TightVNC
- LOCAL local graphical session with simple desktop
- LTSP or K12LTSP
- IBM Host using 3270 or 5250 emulation (soon)
- Telnet emulating ANSI terminal
- SSH
- Tarantella using proprietary protocol
- NoMachine using NX
- Thinlinc
Boot methods
- PXE network card included in most modern PC hardware
- Etherboot to boot from diskette or EPROM
- CD-ROM
- Hard disk
- DOC DiskOnChip and DOM DiskOnModule
- USB Storage
- For Hard Disk, DOC, DOM or other flash memory installation you may also use PXES HD/DOM Installer (http://pxes.sourceforge.net/enterprise/install-dom.shtml) which is part of Enterprise Edition (http://pxes.sourceforge.net/enterprise/index.php).
- You can also see the detailed information about Boot Methods.
Hardware requirements
- Processor: x86 architecture (i486, i586, i686, VIA C3, Geode, Vortex86, Transmeta Crusoe, etc.)
- BUS: PCI recommended (although ISA works)
- RAM: 32 Mb recommended (16 Mb minimum)
- NIC: see supported network card list
- Video: see supported video card list
Local devices
- Diskette
- Hard disk
- CD-ROM
- Printers parallel, serial and USB
- Serial devices (bar code reader, etc.)
- Audio
- Flash memory / USB storage
Supported operating system
- Linux
- Solaris
- AIX
- SCO
- BSD
- HP-UX
- Microsoft Windows NT4
- Microsoft Windows 2000
- Microsoft Windows 2003
- Microsoft Windows XP
Enhancements:
- Support for different boot loaders was added.
- Support for GRUB on ISO images was added.
- A correction was made in the kernel and image path in isolinux.
- A message telling the user to run "pxesconfig --updatefstab" was added.
- updatefstab was added in post.
- Support for 2.4.32 and 2.6.15 kernels was added.
- Automated owner and permission changing on specific files was added, so now the whole pxes-base tree can be checked out as a normal user.

Text::NSP::Measures is a Perl module for computing association scores of Ngrams. This module provides the basic framework for these measures.

SYNOPSIS

Basic Usage

use Text::NSP::Measures::2D::MI::ll;

my $npp = 60; my $n1p = 20; my $np1 = 20; my $n11 = 10;

$ll_value = calculateStatistic( n11=>$n11,
n1p=>$n1p,
np1=>$np1,
npp=>$npp);

if( ($errorCode = getErrorCode()))
{
print STDERR $errorCode." - ".getErrorMessage()."n"";
}
else
{
print getStatisticName."value for bigram is ".$ll_value."n"";
}

isinglass-hzd is a firewall setup script designed to protect dial-up users.In normal configuration it is assumed that Ethernet interfaces belong to LAN and the user accesses Internet through some other interface (PPP etc).
Also only Indent requests are permitted by default, all other services on the machine are blocked. You may wish to change this, so take a look at /etc/isinglass.conf. After you think everything is ok, insert line "/usr/sbin/isinglass" into beginning of your /etc/ppp/ip-up.local script (assuming you use RedHat) and to /etc/rc.d/rc.local and you should be set.
Enhancements:
- Added ipchains support (firewalling used in 2.1 and beyond kernels)
- Added "isinglass.user" script which specifies user-defined rules ("isinglass.user" is run *AFTER* IsinGlass rules are set up)
- Now defaults to deny TCP connection attempts to ports above 1023 (Responses to outgoing packets are allowed by default)

Filesys::DiskFree is a Perl module to perform the Unix command df in a portable fashion.

SYNOPSIS

use Filesys::DiskFree;

$handle = new Filesys::DiskFree;
$handle->df();
print "The root device is ".$handle->device("/")."n";
print "It has ".$handle->avail("/")." bytes availablen";
print "It has ".$handle->total("/")." bytes totaln";
print "It has ".$handle->used("/")." bytes usedn";

Filesys::DiskFree does about what the unix command df(1) does, listing the mounted disks, and the amount of free space used & available.

Functions

Filesys::DiskFree->set(option => value)

Sets various options within the module.

The most common option to change is the mode, which can be either blocks or inodes. By default, blocks is used.

If reading a file from a foreign OS using the load() function, format may be used, which takes the name of an OS as set in the $^O variable.

Returns the previous values of the options.

Filesys::DiskFree->df()

Perfoms a df command, and stores the values for later use.

Filesys::DiskFree->command()

Returns the appropriate command to do a df command, for the current format. This is used when you wish to call a df on a remote system. Use the df() method for local dfs.

Returns undef if there isnt an appropriate command.

Filesys::DiskFree->load($line)

Reads in the output of a df, $line can be either a scalar or a filehandle. If $line is a filehandle, then the filehandle is read until EOF.

Returns undef on failure

Filesys::DiskFree->disks()

Returns all the disks known about

Filesys::DiskFree->device($id)

Returns the device for $id, which is a scalar containing the device name of a disk or a filename, in which case the disk that filename in stored upon is used. If a filename doesnt begin with /, then it is treated as if is /.

Filesys::DiskFree->mount($id)

Returns the mount point for $id, which is a scalar containing the device name of a disk or a filename, in which case the disk that filename in stored upon is used.

Filesys::DiskFree->avail($id)

Returns the amount of available space in bytes for $id, which is a scalar containing the device name of a disk or a filename, in which case the disk that filename in stored upon is used.

Filesys::DiskFree->total($id)

Returns the amount of total space in bytes for $id, which is a scalar containing the device name of a disk or a filename, in which case the disk that filename in stored upon is used.

Filesys::DiskFree->used($id)

Returns the amount of used space in bytes for $id, which is a scalar containing the device name of a disk or a filename, in which case the disk that filename in stored upon is used.

Inferno is a compact operating system designed for building distributed and networked systems on a wide variety of devices and platforms.
Inferno was originally developed at Bell Labs (the research division of Lucent Technologies).
Inferno Operating System is a well-designed, economical operating system particularly suitable for use in networked devices such as advanced telephones, hand-held devices, TV set-top boxes, and many other embedded applications.
Inferno can run in native mode on an embedded system or in emulation mode under many different operating systems. Inferno has many features in common with Plan 9.
Cross-Platform Portability
Inferno can run as a user application on top of an existing operating system or as a stand alone operating system. Most of the popular operating systems and processor architectures are supported:
Host Operating Systems:
- Windows NT/2000/XP
- Irix
- Linux
- MacOS X
- FreeBSD
- Solaris
- Plan 9
Supported Architectures:
- Intel x86 (386 & higher)
- Intel XScale
- IBM PowerPC
- ARM StrongARM (ARM & Thumb)
- Sun SPARC
Inferno also runs as a plug-in under Internet Explorer version 4 and higher. Each Inferno system presents an identical environment to the applications, irrespective of the underlying host OS or architecture, allowing the developer to work with a truly homogeneous environment across multiple different platforms.
Portable Applications
Inferno applications are written in Limbo, a modern, safe, modular, concurrent programming language with C-like syntax. It is more powerful than C but considerably easier to understand and debug than C++ or Java. Limbo code is compiled into architecture independent byte code which is then interpreted (or compiled on the fly) on the target processor. This means that any Inferno application will run identically on all Inferno platforms.
Transparent Resources
Inferno offers complete transparency of resources and data using a simple but powerful namespace system. By representing resources as files and having one standard communication protocol, resources such as data stores, services and external devices can easily be shared between Inferno systems. A resource interface may be imported to the local system and used by the applications without them knowing, or needing to know, whether it is local or remote.
Security
High level security is an important part of the Inferno system. By using one standard protocol for all network communication, security can be focused on one point and provided at a system level. Inferno offers full support for authenticated, encrypted connections using a certificate based user identification scheme and variety of algorithms including:
- IDEA, 56 bit DES, 40, 128 and 256 bit RC4 encryption algorithms
- MD4, MD5 and SHA secure hash algorithms
A Complete Solution
Inferno is not only an operating system, it is also a complete development environment, providing all the tools necessary for creating, testing and debugging the applications that run within it.
- Acme IDE: includes editor, shell, advanced pattern matching tools & more
- Fast Compiler: with full syntax and compile time type checking
- Graphical Debugger: with full stack trace for currently executing threads
- Powerful Shell: with sophisticated scripting capabilities
- UNIX like commands: including bind, grep, gzip, mount, ps, tar, yacc...
Enhancements:
- New licence terms (a `dual licence scheme allowing use as Free Software)
- Styx revision based on 9P2000, and consequent changes to Sys
- Authentication changes
- Improved colour graphics support, including compositing
- Scalable fonts using Freetype
- Revamped Tk implementation
- Window management moved out of Tk to a separate window manager in Limbo
- Limbo: exception handling and fixed-point
- Limbo: other possible changes
- Dis VM changes
- More commands and library modules
- Better network service configuration
- /net/dns served by host and native DNS resolver
- Hosted kernels configured from a parts list as for native kernels
- Signed modules
- Internet Explorer plug-in revised and in source form
- Expanded documentation

ln_local is a simple shell script for managing the installation of software packages (typically in /usr/local). Its a program between stow and lndir/cleanlinks.

The approach used by ln_local (based on Stow) is to install each package into its own tree, then use symbolic links to make it appear as though the files are installed in the common tree (see examples for more details).

Contrary to stow, ln_local create all subdirectory tree and then create all symbolic links (stow create simbolic links for subdirectories and normals files, so conflicts may appends when two programs share the same subdirectory).

Usage

Usage: ln_local [options] [do] Action

Action : create | delete | clean
create : create symlink and directory in /usr/local from current directory
delete : delete symlink and empty directory in /usr/local from current directory
clean : remove broken symlink and empty directory in /usr/local

If do is presents in the command line then changes are made,
else NO CHANGE ARE MADE

Options are :
-s, --source the source directory (default:current directory)
-t, --target the target directory (/usr/local)
-V, --version display version and exit
-u, --usage long help
-h, --help display this help

Example

Standard way to use ln_local:

* download source package (.tar.gz, tar.bz2 ...)

* extract the archive:
tar -xzvf archive-x.x.x.tar.gz
or tar -xjvf archive-x.x.x.tar.bz2

* go to archive directory:
cd archive-x.x.x

* configure the program compilation:
./configure --prefix="/usr/install/archive-x.x.x"

* build the program:
make

* install the program:
make install
or make install DESTDIR=/usr/install/archive-x.x.x if theres no ./configure in this last case, you may have to edit manually the Makefile.

* create symlinks in /usr/local:
cd /usr/install/archive-x.x.x
ln_local create do

* delete the source and archive
cd in the archive-x.x.x.tar.gz directory
rm -rf archive-x.x.x*

you can change the target directory (/usr/local) by editing the file /usr/local/bin/ln_local or use the --target option

To remove an existing program:
cd /usr/install/archive-x.x.x
ln_local delete do

To clean the /usr/local directory:
ln_local clean do

To remove definitively a program:
rm -rf /usr/install/archive-x.x.x
ln_local clean do

If you want to see what ln_local will do, remove the do in create, delete and clean action, so no action will be done