stale
Sponsored Links
Sponsored Links
Secleted [ 0 ] software to compare
Results 1 - 15 of about 38
Install Kernel 0.9.3
Install Kernel is an advanced script which installs the kernel and sets up LILO or GRUB. more>>
Install Kernel interfaces with the Linux operating system by running a series of functions or groups of commands that automate the compiling or recompiling and installation process.
Install Kernel project consists of three groups of functions: building the kernel and moving files, checking dependencies, and editing the boot loader configuration file. Grouping all of the functions in these three groups makes maintaining and altering the script much easier.
Install Kernel can also be considered a program, because a program does checking and makes choices accordingly. A script is usually a file, which contains a certain number of commands with no logic in mind. Therefore, while ik is technically a script, it can also be called a program.
Dependency checks are to make sure the current system configuration and settings are properly setup before proceeding with the kernel build. There are seven dependency checks, they are: a root check, space check, link check, boot check, boot loader check, configuration check, and a module check.
First, the root check makes sure the user is a super user; which means they are capable of editing important system files only accessible to the root account. The space check makes sure there is at least 200 megabytes available.
The kernel source these days is around 150 megabytes just for the source code. When one compiles the kernel, it may increase the size to 50 megabytes or more. Therefore, ik
checks for at least 200MB available in order to successfully compile the kernel without running out of space. Next, it is not required, but it is standard to have a symbolic link of /usr/src/linux pointing to /usr/src/linux-x.y.z.
The fourth check makes sure the user has a /boot directory, this is where the Linux kernel files will be installed to. The fifth check determines the bootloader that will be used. There are two main boot loaders in Linux. LILO and GRUB are the two most popular for booting the operating system.
This check accurately finds whether the kernel was booted from either LILO or GRUB by checking which bootloader was used last. It then tells the rest of the script to edit the correct one accordingly. The sixth configuration check is to make sure users have created a proper kernel configuration file, which is used in the process of building the Linux kernel.
The final check is a module check, if modules are turned off, the script will determine this and alter the installation process to install with no module support. The main idea behind the depdency checks is to make sure the user cannot damage his or her system if they do not do something right.
The installation process also contains seven functions. The installation process is usually several commands. However, because of the differences that can occur in a users configuration file, each part of the building process must be checked and the building process may need to be altered.
The first function makes sure the dependencies are setup correctly for all files in the kernel source tree. The second function deletes stale object files and or old kernel files. Next, the third function is the kernel build function; this function runs a command to build the Linux kernel. Next, functions four and five make and install modules if the user had specified module support in his or her kernel configuration file.
The sixth function moves the Linux kernel and its System dependency map to the boot partition. The last function of the build process sets up module dependencies for the new kernel if modules were defined. The installation process also includes a small error check for each part of the kernel build process.
If any part of the kernel build process fails; the script will abort, not modifying any boot loader configuration files. This is important; because if it did not abort, it may alter the boot loader configuration files, thus rendering the system unbootable. It is important to support every Linux configuration possible because of the wide use of this script.
The boot loader configuration and setup process is probably the most important aspect of installing a new kernel. An improper boot loader configuration may leave one with system that does not boot; or simply does not boot the new kernel.
It is also important, as some systems may have two or more boot loaders installed. There are four functions defined for this process. The first function uses the boot loader, which was defined during the configuration checks. The second function defines where the LILO or GRUB configuration files are located.
Next, depending on which boot loader is found, either LILO or GRUB configuration files are edited automatically by sed. Sed is a stream editor, which edits a file with no user intervention. If user intervention were required, the user would have to be present between certain parts of the kernel installation. With ik, it makes efficient use of a users time because only one command needs to be entered to complete the entire installation and setup process.
Install Kernel is a useful tool for those who are new to Linux, rebuild their kernel often, or value their time. It reduces the commands for installing the kernel from about thirteen to one. Users new to Linux may find this attractive.
This is because the entire process is automated; and if something is not correct, in most cases ik will notify the user what is incorrect, and how to fix the error. On the other side, for experienced users who do not wish to spend valuable time installing a new kernel, this is also very handy. Install Kernel is efficient by requiring no user intervention and reducing time spent on kernel installs, and effective by giving new to Linux the option for an easy kernel upgrade.
Enhancements:
- Updated to work with the newer version of coreutils for head and tail.
- The MAKE_JOBS directive has been removed in favor of make -j2 to prevent make from spawning hundreds of jobs if /proc/cpuinfo did not exist.
<<lessInstall Kernel project consists of three groups of functions: building the kernel and moving files, checking dependencies, and editing the boot loader configuration file. Grouping all of the functions in these three groups makes maintaining and altering the script much easier.
Install Kernel can also be considered a program, because a program does checking and makes choices accordingly. A script is usually a file, which contains a certain number of commands with no logic in mind. Therefore, while ik is technically a script, it can also be called a program.
Dependency checks are to make sure the current system configuration and settings are properly setup before proceeding with the kernel build. There are seven dependency checks, they are: a root check, space check, link check, boot check, boot loader check, configuration check, and a module check.
First, the root check makes sure the user is a super user; which means they are capable of editing important system files only accessible to the root account. The space check makes sure there is at least 200 megabytes available.
The kernel source these days is around 150 megabytes just for the source code. When one compiles the kernel, it may increase the size to 50 megabytes or more. Therefore, ik
checks for at least 200MB available in order to successfully compile the kernel without running out of space. Next, it is not required, but it is standard to have a symbolic link of /usr/src/linux pointing to /usr/src/linux-x.y.z.
The fourth check makes sure the user has a /boot directory, this is where the Linux kernel files will be installed to. The fifth check determines the bootloader that will be used. There are two main boot loaders in Linux. LILO and GRUB are the two most popular for booting the operating system.
This check accurately finds whether the kernel was booted from either LILO or GRUB by checking which bootloader was used last. It then tells the rest of the script to edit the correct one accordingly. The sixth configuration check is to make sure users have created a proper kernel configuration file, which is used in the process of building the Linux kernel.
The final check is a module check, if modules are turned off, the script will determine this and alter the installation process to install with no module support. The main idea behind the depdency checks is to make sure the user cannot damage his or her system if they do not do something right.
The installation process also contains seven functions. The installation process is usually several commands. However, because of the differences that can occur in a users configuration file, each part of the building process must be checked and the building process may need to be altered.
The first function makes sure the dependencies are setup correctly for all files in the kernel source tree. The second function deletes stale object files and or old kernel files. Next, the third function is the kernel build function; this function runs a command to build the Linux kernel. Next, functions four and five make and install modules if the user had specified module support in his or her kernel configuration file.
The sixth function moves the Linux kernel and its System dependency map to the boot partition. The last function of the build process sets up module dependencies for the new kernel if modules were defined. The installation process also includes a small error check for each part of the kernel build process.
If any part of the kernel build process fails; the script will abort, not modifying any boot loader configuration files. This is important; because if it did not abort, it may alter the boot loader configuration files, thus rendering the system unbootable. It is important to support every Linux configuration possible because of the wide use of this script.
The boot loader configuration and setup process is probably the most important aspect of installing a new kernel. An improper boot loader configuration may leave one with system that does not boot; or simply does not boot the new kernel.
It is also important, as some systems may have two or more boot loaders installed. There are four functions defined for this process. The first function uses the boot loader, which was defined during the configuration checks. The second function defines where the LILO or GRUB configuration files are located.
Next, depending on which boot loader is found, either LILO or GRUB configuration files are edited automatically by sed. Sed is a stream editor, which edits a file with no user intervention. If user intervention were required, the user would have to be present between certain parts of the kernel installation. With ik, it makes efficient use of a users time because only one command needs to be entered to complete the entire installation and setup process.
Install Kernel is a useful tool for those who are new to Linux, rebuild their kernel often, or value their time. It reduces the commands for installing the kernel from about thirteen to one. Users new to Linux may find this attractive.
This is because the entire process is automated; and if something is not correct, in most cases ik will notify the user what is incorrect, and how to fix the error. On the other side, for experienced users who do not wish to spend valuable time installing a new kernel, this is also very handy. Install Kernel is efficient by requiring no user intervention and reducing time spent on kernel installs, and effective by giving new to Linux the option for an easy kernel upgrade.
Enhancements:
- Updated to work with the newer version of coreutils for head and tail.
- The MAKE_JOBS directive has been removed in favor of make -j2 to prevent make from spawning hundreds of jobs if /proc/cpuinfo did not exist.
Download (0.004MB)
Added: 2006-05-24 License: GPL (GNU General Public License) Price:
1249 downloads
nfsstats.pl 0.1
nfsstats.pl is a Net-SNMP sub-agent that parses. more>>
nfsstats.pl is a Net-SNMP sub-agent that parses /proc/net/rpc/nfs and /proc/net/rpc/nfsd to obtain NFS statistics (just like nfsstat), and reports these as SNMP values.
nfsstats.pl is useful for remotely monitoring NFS client or server usage via SNMP to utilities like MRTG, Cacti, or Ganglia.
Installation:
Installation instructsion are contained in the form of comments at the top of nfsstats.pl script. nfsstats.pl is only suitable for Linux. NFS version 3 statistics are made available.
Firstly, ensure you have a working Net-SNMP install. Secondly, ensure you have the Perl sub-components of Net-SNMP installed (in Fedora Core, do yum install net-snmp-perl). Thirdly, save nfsstats.pl to /var/net-snmp/. Add the following line to /etc/snmp/snmpd.conf: master agentx. Start nfsstats.pl in the way of your choice, logged to file of your choice (eg 2>/dev/null). Note that nfsstats.pl must be started as root.
If your snmpd is built with embedded Perl support (Fedora Core doesnt), then you can import the sub agent directly into the snmpd. See the script for more details.
Usage:
After you have successfully installed nfsstats.pl, you should be able to walk the provided OIDs: snmpwalk -v 2c -c public localhost enterprises.6789.6789 or snmpwalk -v 2c -c public localhost .1.3.6.1.4.1.6789.6789. As we have no MIB for nfsstats.pl yet, the numbers coming back wont make much sense. However, they should bear a striking resemblance to the output of /usr/sbin/nfsstat!
The list below is all the 114 statistics that nfsstats.pl can provide for SNMP values. The ones you should monitor (eg using MRTG) are entirely up to you.
enterprises.6789.6789.0.0.1 -> client.rpc.count.calls
enterprises.6789.6789.0.0.2 -> client.rpc.count.retrans
enterprises.6789.6789.0.0.3 -> client.rpc.count.authrefrsh
enterprises.6789.6789.0.3.0.0 -> client3.count.null
enterprises.6789.6789.0.3.0.1 -> client3.percent.null
enterprises.6789.6789.0.3.1.0 -> client3.count.getattr
enterprises.6789.6789.0.3.1.1 -> client3.percent.getattr
enterprises.6789.6789.0.3.2.0 -> client3.count.setattr
enterprises.6789.6789.0.3.2.1 -> client3.percent.setattr
enterprises.6789.6789.0.3.3.0 -> client3.count.lookup
enterprises.6789.6789.0.3.3.1 -> client3.percent.lookup
enterprises.6789.6789.0.3.4.0 -> client3.count.access
enterprises.6789.6789.0.3.4.1 -> client3.percent.access
enterprises.6789.6789.0.3.5.0 -> client3.count.readlink
enterprises.6789.6789.0.3.5.1 -> client3.percent.readlink
enterprises.6789.6789.0.3.6.0 -> client3.count.read
enterprises.6789.6789.0.3.6.1 -> client3.percent.read
enterprises.6789.6789.0.3.7.0 -> client3.count.write
enterprises.6789.6789.0.3.7.1 -> client3.percent.write
enterprises.6789.6789.0.3.8.0 -> client3.count.create
enterprises.6789.6789.0.3.8.1 -> client3.percent.create
enterprises.6789.6789.0.3.9.0 -> client3.count.mkdir
enterprises.6789.6789.0.3.9.1 -> client3.percent.mkdir
enterprises.6789.6789.0.3.10.0 -> client3.count.symlink
enterprises.6789.6789.0.3.10.1 -> client3.percent.symlink
enterprises.6789.6789.0.3.11.0 -> client3.count.mknod
enterprises.6789.6789.0.3.11.1 -> client3.percent.mknod
enterprises.6789.6789.0.3.12.0 -> client3.count.remove
enterprises.6789.6789.0.3.12.1 -> client3.percent.remove
enterprises.6789.6789.0.3.13.0 -> client3.count.rmdir
enterprises.6789.6789.0.3.13.1 -> client3.percent.rmdir
enterprises.6789.6789.0.3.14.0 -> client3.percent.rename
enterprises.6789.6789.0.3.15.0 -> client3.count.link
enterprises.6789.6789.0.3.15.1 -> client3.percent.link
enterprises.6789.6789.0.3.16.0 -> client3.count.readdir
enterprises.6789.6789.0.3.16.1 -> client3.percent.readdir
enterprises.6789.6789.0.3.17.0 -> client3.count.readdirplus
enterprises.6789.6789.0.3.17.1 -> client3.percent.readdirplus
enterprises.6789.6789.0.3.18.0 -> client3.count.fsstat
enterprises.6789.6789.0.3.18.1 -> client3.percent.fsstat
enterprises.6789.6789.0.3.19.0 -> client3.count.fsinfo
enterprises.6789.6789.0.3.19.1 -> client3.percent.fsinfo
enterprises.6789.6789.0.3.20.0 -> client3.count.pathconf
enterprises.6789.6789.0.3.20.1 -> client3.percent.pathconf
enterprises.6789.6789.0.3.21.0 -> client3.count.commit
enterprises.6789.6789.0.3.21.1 -> client3.percent.commit
enterprises.6789.6789.0.3.22.0 -> client3.count.total
enterprises.6789.6789.0.3.22.1 -> client3.percent.total
enterprises.6789.6789.1.0.0 -> server.rpc.count.calls
enterprises.6789.6789.1.0.1 -> server.rpc.count.retrans
enterprises.6789.6789.1.0.2 -> server.rpc.count.badcalls
enterprises.6789.6789.1.0.3 -> server.rpc.count.badauth
enterprises.6789.6789.1.0.4 -> server.rpc.count.badclnt
enterprises.6789.6789.1.0.5 -> server.rpc.count.xdrcall
enterprises.6789.6789.1.3.0.0 -> server3.count.null
enterprises.6789.6789.1.3.0.1 -> server3.percent.null
enterprises.6789.6789.1.3.1.0 -> server3.count.getattr
enterprises.6789.6789.1.3.1.1 -> server3.percent.getattr
enterprises.6789.6789.1.3.2.0 -> server3.count.setattr
enterprises.6789.6789.1.3.2.1 -> server3.percent.setattr
enterprises.6789.6789.1.3.3.0 -> server3.count.lookup
enterprises.6789.6789.1.3.3.1 -> server3.percent.lookup
enterprises.6789.6789.1.3.4.0 -> server3.count.access
enterprises.6789.6789.1.3.4.1 -> server3.percent.access
enterprises.6789.6789.1.3.5.0 -> server3.count.readlink
enterprises.6789.6789.1.3.5.1 -> server3.percent.readlink
enterprises.6789.6789.1.3.6.0 -> server3.count.read
enterprises.6789.6789.1.3.6.1 -> server3.percent.read
enterprises.6789.6789.1.3.7.0 -> server3.count.write
enterprises.6789.6789.1.3.7.1 -> server3.percent.write
enterprises.6789.6789.1.3.8.0 -> server3.count.create
enterprises.6789.6789.1.3.8.1 -> server3.percent.create
enterprises.6789.6789.1.3.9.0 -> server3.count.mkdir
enterprises.6789.6789.1.3.9.1 -> server3.percent.mkdir
enterprises.6789.6789.1.3.10.0 -> server3.count.symlink
enterprises.6789.6789.1.3.10.1 -> server3.percent.symlink
enterprises.6789.6789.1.3.11.0 -> server3.count.mknod
enterprises.6789.6789.1.3.11.1 -> server3.percent.mknod
enterprises.6789.6789.1.3.12.0 -> server3.count.remove
enterprises.6789.6789.1.3.12.1 -> server3.percent.remove
enterprises.6789.6789.1.3.13.0 -> server3.count.rmdir
enterprises.6789.6789.1.3.13.1 -> server3.percent.rmdir
enterprises.6789.6789.1.3.14.0 -> server3.count.rename
enterprises.6789.6789.1.3.14.1 -> server3.percent.rename
enterprises.6789.6789.1.3.15.0 -> server3.count.link
enterprises.6789.6789.1.3.15.1 -> server3.percent.link
enterprises.6789.6789.1.3.16.0 -> server3.count.readdir
enterprises.6789.6789.1.3.16.1 -> server3.percent.readdir
enterprises.6789.6789.1.3.17.0 -> server3.count.readdirplus
enterprises.6789.6789.1.3.17.1 -> server3.percent.readdirplus
enterprises.6789.6789.1.3.18.0 -> server3.count.fsstat
enterprises.6789.6789.1.3.18.1 -> server3.percent.fsstat
enterprises.6789.6789.1.3.19.0 -> server3.count.fsinfo
enterprises.6789.6789.1.3.19.1 -> server3.percent.fsinfo
enterprises.6789.6789.1.3.20.0 -> server3.count.pathconf
enterprises.6789.6789.1.3.20.1 -> server3.percent.pathconf
enterprises.6789.6789.1.3.21.0 -> server3.count.commit
enterprises.6789.6789.1.3.21.1 -> server3.percent.commit
enterprises.6789.6789.1.3.22.0 -> server3.count.total
enterprises.6789.6789.1.3.22.1 -> server3.percent.total
enterprises.6789.6789.1.6.0 -> server.replycache.count.hits
enterprises.6789.6789.1.6.1 -> server.replycache.count.misses
enterprises.6789.6789.1.6.2 -> server.replycache.count.nocache
enterprises.6789.6789.1.7.0 -> server.fhcache.count.lookups
enterprises.6789.6789.1.7.1 -> server.fhcache.count.anon
enterprises.6789.6789.1.7.2 -> server.fhcache.count.nocache_dir
enterprises.6789.6789.1.7.3 -> server.fhcache.count.nocache_nondir
enterprises.6789.6789.1.7.4 -> server.fhcache.count.stale
enterprises.6789.6789.1.8.0 -> server.threads.count
enterprises.6789.6789.1.8.1 -> server.threads.fullcount
enterprises.6789.6789.1.50 -> server.net.count.packets
enterprises.6789.6789.1.51 -> server.net.count.udp
enterprises.6789.6789.1.52 -> server.net.count.tcp
enterprises.6789.6789.1.53 -> server.net.count.tcpconn
<<lessnfsstats.pl is useful for remotely monitoring NFS client or server usage via SNMP to utilities like MRTG, Cacti, or Ganglia.
Installation:
Installation instructsion are contained in the form of comments at the top of nfsstats.pl script. nfsstats.pl is only suitable for Linux. NFS version 3 statistics are made available.
Firstly, ensure you have a working Net-SNMP install. Secondly, ensure you have the Perl sub-components of Net-SNMP installed (in Fedora Core, do yum install net-snmp-perl). Thirdly, save nfsstats.pl to /var/net-snmp/. Add the following line to /etc/snmp/snmpd.conf: master agentx. Start nfsstats.pl in the way of your choice, logged to file of your choice (eg 2>/dev/null). Note that nfsstats.pl must be started as root.
If your snmpd is built with embedded Perl support (Fedora Core doesnt), then you can import the sub agent directly into the snmpd. See the script for more details.
Usage:
After you have successfully installed nfsstats.pl, you should be able to walk the provided OIDs: snmpwalk -v 2c -c public localhost enterprises.6789.6789 or snmpwalk -v 2c -c public localhost .1.3.6.1.4.1.6789.6789. As we have no MIB for nfsstats.pl yet, the numbers coming back wont make much sense. However, they should bear a striking resemblance to the output of /usr/sbin/nfsstat!
The list below is all the 114 statistics that nfsstats.pl can provide for SNMP values. The ones you should monitor (eg using MRTG) are entirely up to you.
enterprises.6789.6789.0.0.1 -> client.rpc.count.calls
enterprises.6789.6789.0.0.2 -> client.rpc.count.retrans
enterprises.6789.6789.0.0.3 -> client.rpc.count.authrefrsh
enterprises.6789.6789.0.3.0.0 -> client3.count.null
enterprises.6789.6789.0.3.0.1 -> client3.percent.null
enterprises.6789.6789.0.3.1.0 -> client3.count.getattr
enterprises.6789.6789.0.3.1.1 -> client3.percent.getattr
enterprises.6789.6789.0.3.2.0 -> client3.count.setattr
enterprises.6789.6789.0.3.2.1 -> client3.percent.setattr
enterprises.6789.6789.0.3.3.0 -> client3.count.lookup
enterprises.6789.6789.0.3.3.1 -> client3.percent.lookup
enterprises.6789.6789.0.3.4.0 -> client3.count.access
enterprises.6789.6789.0.3.4.1 -> client3.percent.access
enterprises.6789.6789.0.3.5.0 -> client3.count.readlink
enterprises.6789.6789.0.3.5.1 -> client3.percent.readlink
enterprises.6789.6789.0.3.6.0 -> client3.count.read
enterprises.6789.6789.0.3.6.1 -> client3.percent.read
enterprises.6789.6789.0.3.7.0 -> client3.count.write
enterprises.6789.6789.0.3.7.1 -> client3.percent.write
enterprises.6789.6789.0.3.8.0 -> client3.count.create
enterprises.6789.6789.0.3.8.1 -> client3.percent.create
enterprises.6789.6789.0.3.9.0 -> client3.count.mkdir
enterprises.6789.6789.0.3.9.1 -> client3.percent.mkdir
enterprises.6789.6789.0.3.10.0 -> client3.count.symlink
enterprises.6789.6789.0.3.10.1 -> client3.percent.symlink
enterprises.6789.6789.0.3.11.0 -> client3.count.mknod
enterprises.6789.6789.0.3.11.1 -> client3.percent.mknod
enterprises.6789.6789.0.3.12.0 -> client3.count.remove
enterprises.6789.6789.0.3.12.1 -> client3.percent.remove
enterprises.6789.6789.0.3.13.0 -> client3.count.rmdir
enterprises.6789.6789.0.3.13.1 -> client3.percent.rmdir
enterprises.6789.6789.0.3.14.0 -> client3.percent.rename
enterprises.6789.6789.0.3.15.0 -> client3.count.link
enterprises.6789.6789.0.3.15.1 -> client3.percent.link
enterprises.6789.6789.0.3.16.0 -> client3.count.readdir
enterprises.6789.6789.0.3.16.1 -> client3.percent.readdir
enterprises.6789.6789.0.3.17.0 -> client3.count.readdirplus
enterprises.6789.6789.0.3.17.1 -> client3.percent.readdirplus
enterprises.6789.6789.0.3.18.0 -> client3.count.fsstat
enterprises.6789.6789.0.3.18.1 -> client3.percent.fsstat
enterprises.6789.6789.0.3.19.0 -> client3.count.fsinfo
enterprises.6789.6789.0.3.19.1 -> client3.percent.fsinfo
enterprises.6789.6789.0.3.20.0 -> client3.count.pathconf
enterprises.6789.6789.0.3.20.1 -> client3.percent.pathconf
enterprises.6789.6789.0.3.21.0 -> client3.count.commit
enterprises.6789.6789.0.3.21.1 -> client3.percent.commit
enterprises.6789.6789.0.3.22.0 -> client3.count.total
enterprises.6789.6789.0.3.22.1 -> client3.percent.total
enterprises.6789.6789.1.0.0 -> server.rpc.count.calls
enterprises.6789.6789.1.0.1 -> server.rpc.count.retrans
enterprises.6789.6789.1.0.2 -> server.rpc.count.badcalls
enterprises.6789.6789.1.0.3 -> server.rpc.count.badauth
enterprises.6789.6789.1.0.4 -> server.rpc.count.badclnt
enterprises.6789.6789.1.0.5 -> server.rpc.count.xdrcall
enterprises.6789.6789.1.3.0.0 -> server3.count.null
enterprises.6789.6789.1.3.0.1 -> server3.percent.null
enterprises.6789.6789.1.3.1.0 -> server3.count.getattr
enterprises.6789.6789.1.3.1.1 -> server3.percent.getattr
enterprises.6789.6789.1.3.2.0 -> server3.count.setattr
enterprises.6789.6789.1.3.2.1 -> server3.percent.setattr
enterprises.6789.6789.1.3.3.0 -> server3.count.lookup
enterprises.6789.6789.1.3.3.1 -> server3.percent.lookup
enterprises.6789.6789.1.3.4.0 -> server3.count.access
enterprises.6789.6789.1.3.4.1 -> server3.percent.access
enterprises.6789.6789.1.3.5.0 -> server3.count.readlink
enterprises.6789.6789.1.3.5.1 -> server3.percent.readlink
enterprises.6789.6789.1.3.6.0 -> server3.count.read
enterprises.6789.6789.1.3.6.1 -> server3.percent.read
enterprises.6789.6789.1.3.7.0 -> server3.count.write
enterprises.6789.6789.1.3.7.1 -> server3.percent.write
enterprises.6789.6789.1.3.8.0 -> server3.count.create
enterprises.6789.6789.1.3.8.1 -> server3.percent.create
enterprises.6789.6789.1.3.9.0 -> server3.count.mkdir
enterprises.6789.6789.1.3.9.1 -> server3.percent.mkdir
enterprises.6789.6789.1.3.10.0 -> server3.count.symlink
enterprises.6789.6789.1.3.10.1 -> server3.percent.symlink
enterprises.6789.6789.1.3.11.0 -> server3.count.mknod
enterprises.6789.6789.1.3.11.1 -> server3.percent.mknod
enterprises.6789.6789.1.3.12.0 -> server3.count.remove
enterprises.6789.6789.1.3.12.1 -> server3.percent.remove
enterprises.6789.6789.1.3.13.0 -> server3.count.rmdir
enterprises.6789.6789.1.3.13.1 -> server3.percent.rmdir
enterprises.6789.6789.1.3.14.0 -> server3.count.rename
enterprises.6789.6789.1.3.14.1 -> server3.percent.rename
enterprises.6789.6789.1.3.15.0 -> server3.count.link
enterprises.6789.6789.1.3.15.1 -> server3.percent.link
enterprises.6789.6789.1.3.16.0 -> server3.count.readdir
enterprises.6789.6789.1.3.16.1 -> server3.percent.readdir
enterprises.6789.6789.1.3.17.0 -> server3.count.readdirplus
enterprises.6789.6789.1.3.17.1 -> server3.percent.readdirplus
enterprises.6789.6789.1.3.18.0 -> server3.count.fsstat
enterprises.6789.6789.1.3.18.1 -> server3.percent.fsstat
enterprises.6789.6789.1.3.19.0 -> server3.count.fsinfo
enterprises.6789.6789.1.3.19.1 -> server3.percent.fsinfo
enterprises.6789.6789.1.3.20.0 -> server3.count.pathconf
enterprises.6789.6789.1.3.20.1 -> server3.percent.pathconf
enterprises.6789.6789.1.3.21.0 -> server3.count.commit
enterprises.6789.6789.1.3.21.1 -> server3.percent.commit
enterprises.6789.6789.1.3.22.0 -> server3.count.total
enterprises.6789.6789.1.3.22.1 -> server3.percent.total
enterprises.6789.6789.1.6.0 -> server.replycache.count.hits
enterprises.6789.6789.1.6.1 -> server.replycache.count.misses
enterprises.6789.6789.1.6.2 -> server.replycache.count.nocache
enterprises.6789.6789.1.7.0 -> server.fhcache.count.lookups
enterprises.6789.6789.1.7.1 -> server.fhcache.count.anon
enterprises.6789.6789.1.7.2 -> server.fhcache.count.nocache_dir
enterprises.6789.6789.1.7.3 -> server.fhcache.count.nocache_nondir
enterprises.6789.6789.1.7.4 -> server.fhcache.count.stale
enterprises.6789.6789.1.8.0 -> server.threads.count
enterprises.6789.6789.1.8.1 -> server.threads.fullcount
enterprises.6789.6789.1.50 -> server.net.count.packets
enterprises.6789.6789.1.51 -> server.net.count.udp
enterprises.6789.6789.1.52 -> server.net.count.tcp
enterprises.6789.6789.1.53 -> server.net.count.tcpconn
Download (0.005MB)
Added: 2006-07-19 License: GPL (GNU General Public License) Price:
1199 downloads
SpecialValue 0.5.0
SpecialValue is a C++ library that allows special numeric values to be represented accurately. more>>
SpecialValue is a C++ library that allows special numeric values to be represented accurately. This is useful for fractions that would normally be approximated as floating point, or numbers that are normally impossible to store, such as sqrt(-2).
Installation:
The `configure shell script attempts to guess correct values for various system-dependent variables used during compilation.
It uses those values to create a `Makefile in each directory of the package. It may also create one or more `.h files containing system-dependent definitions.
Finally, it creates a shell script `config.status that you can run in the future to recreate the current configuration, and a file `config.log containing compiler output (useful mainly for debugging `configure).
It can also use an optional file (typically called `config.cache and enabled with `--cache-file=config.cache or simply `-C) that saves the results of its tests to speed up reconfiguring. (Caching is disabled by default to prevent problems with accidental use of stale cache files.)
If you need to do unusual things to compile the package, please try to figure out how `configure could check whether to do them, and mail diffs or instructions to the address given in the `README so they can be considered for the next release.
If you are using the cache, and at some point `config.cache contains results you dont want to keep, you
may remove or edit it.
The file `configure.ac (or `configure.in) is used to create `configure by a program called `autoconf. You only need `configure.ac if you want to change it or regenerate `configure using a newer version of `autoconf.
The simplest way to compile this package is:
1. `cd to the directory containing the packages source code and type `./configure to configure the package for your system. If youre using `csh on an old version of System V, you might need to type `sh ./configure instead to prevent `csh from trying to execute
`configure itself.
Running `configure takes awhile. While running, it prints some messages telling which features it is checking for.
2. Type `make to compile the package.
3. Optionally, type `make check to run any self-tests that come with the package.
4. Type `make install to install the programs and any data files and documentation.
5. You can remove the program binaries and object files from the source code directory by typing `make clean.
To also remove the files that `configure created (so you can compile the package for a different kind of computer), type `make distclean. There is also a `make maintainer-clean target, but that is intended mainly for the packages developers.
If you use it, you may have to get all sorts of other programs in order to regenerate files that came with the distribution.
Enhancements:
- configure.ac: changed version nubmer
- doc/Makefile.am: added all those `svstruc images
- doc/SpecialValue.texi: updated documentation
<<lessInstallation:
The `configure shell script attempts to guess correct values for various system-dependent variables used during compilation.
It uses those values to create a `Makefile in each directory of the package. It may also create one or more `.h files containing system-dependent definitions.
Finally, it creates a shell script `config.status that you can run in the future to recreate the current configuration, and a file `config.log containing compiler output (useful mainly for debugging `configure).
It can also use an optional file (typically called `config.cache and enabled with `--cache-file=config.cache or simply `-C) that saves the results of its tests to speed up reconfiguring. (Caching is disabled by default to prevent problems with accidental use of stale cache files.)
If you need to do unusual things to compile the package, please try to figure out how `configure could check whether to do them, and mail diffs or instructions to the address given in the `README so they can be considered for the next release.
If you are using the cache, and at some point `config.cache contains results you dont want to keep, you
may remove or edit it.
The file `configure.ac (or `configure.in) is used to create `configure by a program called `autoconf. You only need `configure.ac if you want to change it or regenerate `configure using a newer version of `autoconf.
The simplest way to compile this package is:
1. `cd to the directory containing the packages source code and type `./configure to configure the package for your system. If youre using `csh on an old version of System V, you might need to type `sh ./configure instead to prevent `csh from trying to execute
`configure itself.
Running `configure takes awhile. While running, it prints some messages telling which features it is checking for.
2. Type `make to compile the package.
3. Optionally, type `make check to run any self-tests that come with the package.
4. Type `make install to install the programs and any data files and documentation.
5. You can remove the program binaries and object files from the source code directory by typing `make clean.
To also remove the files that `configure created (so you can compile the package for a different kind of computer), type `make distclean. There is also a `make maintainer-clean target, but that is intended mainly for the packages developers.
If you use it, you may have to get all sorts of other programs in order to regenerate files that came with the distribution.
Enhancements:
- configure.ac: changed version nubmer
- doc/Makefile.am: added all those `svstruc images
- doc/SpecialValue.texi: updated documentation
Download (0.48MB)
Added: 2005-09-28 License: LGPL (GNU Lesser General Public License) Price:
1486 downloads
libstree 0.4.2
libstree is a generic suffix tree implementation, written in C. more>>
libstree is a generic suffix tree implementation, written in C. libstree library can handle arbitrary data structures as elements of a string. Unlike most demo implementations, it is thus not limited to simple ASCII character strings.
Suffix tree generation in libstree is highly efficient and implemented using the algorithm by Ukkonen, which means that libstree builds suffix trees in time linear to the length of the strings (assuming that string element comparisons can be done in O(1)).
libstree can handle multiple strings per suffix tree, including dynamic insertion and removal of strings. It provides various means of obtaining information about nodes in the tree, such as depth-first and breadth-first iteration, leaves iteration, and bottom-up iteration.
libstree provides implementations of longest-common-substring and longest-repeated-substring algorithms, as examples of how to build complex algorithms using the suffix tree primitives.
Installation:
The `configure shell script attempts to guess correct values for various system-dependent variables used during compilation. It uses those values to create a `Makefile in each directory of the package.
It may also create one or more `.h files containing system-dependent definitions. Finally, it creates a shell script `config.status that you can run in the future to recreate the current configuration, and a file `config.log containing compiler output (useful mainly for debugging `configure).
It can also use an optional file (typically called `config.cache and enabled with `--cache-file=config.cache or simply `-C) that saves the results of its tests to speed up reconfiguring. (Caching is disabled by default to prevent problems with accidental use of stale cache files.)
If you need to do unusual things to compile the package, please try to figure out how `configure could check whether to do them, and mail diffs or instructions to the address given in the `README so they can be considered for the next release.
If you are using the cache, and at some point `config.cache contains results you dont want to keep, you may remove or edit it.
The file `configure.ac (or `configure.in) is used to create `configure by a program called `autoconf. You only need `configure.ac if you want to change it or regenerate `configure using a newer version of `autoconf.
The simplest way to compile this package is:
1. `cd to the directory containing the packages source code and type `./configure to configure the package for your system. If youre using `csh on an old version of System V, you might need to type `sh ./configure instead to prevent `csh from trying to execute
`configure itself.
Running `configure takes awhile. While running, it prints some messages telling which features it is checking for.
2. Type `make to compile the package.
3. Optionally, type `make check to run any self-tests that come with the package.
4. Type `make install to install the programs and any data files and documentation.
5. You can remove the program binaries and object files from the source code directory by typing `make clean. To also remove the files that `configure created (so you can compile the package for a different kind of computer), type `make distclean.
There is also a `make maintainer-clean target, but that is intended mainly for the packages developers. If you use it, you may have to get all sorts of other programs in order to regenerate files that came with the distribution.
Enhancements:
- LCS can now be run repeatedly on a single unmodified tree without problems.
- A memory leak in lst_stree_clear() has been fixed.
<<lessSuffix tree generation in libstree is highly efficient and implemented using the algorithm by Ukkonen, which means that libstree builds suffix trees in time linear to the length of the strings (assuming that string element comparisons can be done in O(1)).
libstree can handle multiple strings per suffix tree, including dynamic insertion and removal of strings. It provides various means of obtaining information about nodes in the tree, such as depth-first and breadth-first iteration, leaves iteration, and bottom-up iteration.
libstree provides implementations of longest-common-substring and longest-repeated-substring algorithms, as examples of how to build complex algorithms using the suffix tree primitives.
Installation:
The `configure shell script attempts to guess correct values for various system-dependent variables used during compilation. It uses those values to create a `Makefile in each directory of the package.
It may also create one or more `.h files containing system-dependent definitions. Finally, it creates a shell script `config.status that you can run in the future to recreate the current configuration, and a file `config.log containing compiler output (useful mainly for debugging `configure).
It can also use an optional file (typically called `config.cache and enabled with `--cache-file=config.cache or simply `-C) that saves the results of its tests to speed up reconfiguring. (Caching is disabled by default to prevent problems with accidental use of stale cache files.)
If you need to do unusual things to compile the package, please try to figure out how `configure could check whether to do them, and mail diffs or instructions to the address given in the `README so they can be considered for the next release.
If you are using the cache, and at some point `config.cache contains results you dont want to keep, you may remove or edit it.
The file `configure.ac (or `configure.in) is used to create `configure by a program called `autoconf. You only need `configure.ac if you want to change it or regenerate `configure using a newer version of `autoconf.
The simplest way to compile this package is:
1. `cd to the directory containing the packages source code and type `./configure to configure the package for your system. If youre using `csh on an old version of System V, you might need to type `sh ./configure instead to prevent `csh from trying to execute
`configure itself.
Running `configure takes awhile. While running, it prints some messages telling which features it is checking for.
2. Type `make to compile the package.
3. Optionally, type `make check to run any self-tests that come with the package.
4. Type `make install to install the programs and any data files and documentation.
5. You can remove the program binaries and object files from the source code directory by typing `make clean. To also remove the files that `configure created (so you can compile the package for a different kind of computer), type `make distclean.
There is also a `make maintainer-clean target, but that is intended mainly for the packages developers. If you use it, you may have to get all sorts of other programs in order to regenerate files that came with the distribution.
Enhancements:
- LCS can now be run repeatedly on a single unmodified tree without problems.
- A memory leak in lst_stree_clear() has been fixed.
Download (0.25MB)
Added: 2006-03-01 License: GPL (GNU General Public License) Price:
1334 downloads
SWFT 0.3
SWFT (Simple Web File Transfer) is a simple Web application designed as a more secure and modern replacement for FTP and SFTP. more>>
SWFT (pronounced Swift) is a simple web application designed as a more secure modern replacement for FTP and SFTP. SWFT allows for easy and secure upload and download of files through the HTTPS feature of any standard web browser. SWFT is written in php. SWFT stands for Simple Web File Transfer.
Each single file gets a unique Id and Password for download. Multiple file transfer requires multiple Ids or the use of ZIP files. Swft automatically remembers file names and extensions. Ids do not need to match the file name, so multiple files with the same name can be uploaded with different Ids. Password protection is enforced to reduce abuse.
The default swft configuration allows each file to be downloaded 5 times or to remain available for 24 hours, whichever comes first. Defaults can be changed by editing the simple configuration file, but will eventually be accessable through the administrators web interface. These auto housekeeping settings make for easy maintainance by removing stale uploads.
Upload can be done without ceasing administrative rights, and the confidentiality of data being guaranteed.
Swft is a php web application and therefore cross platform. It should work on any webserver with PHP 4 or newer. Limitations to file size are only controlled by the PHP configuration.
The interface is very plain, but easy to understand and will support easier website integration and CSS style sheets in future versions.
The documentation is incomplete, but Install and Howto are included with the download
Main features:
- Its freely licensed under the QPL.
- Since its written in php, it doesnt require you to recompile your web server (although you might want to make a few configuration adjustments).
- Since its written in php, its platform independent. It will run on any system that supports php4 or better, such as Windows, Linux, Macintosh, and BSD.
- Its specifically designed to be simple and secure.
- It doesnt require a big application framework or other complex install procedure.
- It works without cookies.
Enhancements:
- Windows doesnt have /dev/null, so that was not a good assumption to make if we want swft to be cross-platform
- Example config file had a bunch of typos in it
- $HTTP_SERVER_VAR is depreciated, using $_SERVER instead
<<lessEach single file gets a unique Id and Password for download. Multiple file transfer requires multiple Ids or the use of ZIP files. Swft automatically remembers file names and extensions. Ids do not need to match the file name, so multiple files with the same name can be uploaded with different Ids. Password protection is enforced to reduce abuse.
The default swft configuration allows each file to be downloaded 5 times or to remain available for 24 hours, whichever comes first. Defaults can be changed by editing the simple configuration file, but will eventually be accessable through the administrators web interface. These auto housekeeping settings make for easy maintainance by removing stale uploads.
Upload can be done without ceasing administrative rights, and the confidentiality of data being guaranteed.
Swft is a php web application and therefore cross platform. It should work on any webserver with PHP 4 or newer. Limitations to file size are only controlled by the PHP configuration.
The interface is very plain, but easy to understand and will support easier website integration and CSS style sheets in future versions.
The documentation is incomplete, but Install and Howto are included with the download
Main features:
- Its freely licensed under the QPL.
- Since its written in php, it doesnt require you to recompile your web server (although you might want to make a few configuration adjustments).
- Since its written in php, its platform independent. It will run on any system that supports php4 or better, such as Windows, Linux, Macintosh, and BSD.
- Its specifically designed to be simple and secure.
- It doesnt require a big application framework or other complex install procedure.
- It works without cookies.
Enhancements:
- Windows doesnt have /dev/null, so that was not a good assumption to make if we want swft to be cross-platform
- Example config file had a bunch of typos in it
- $HTTP_SERVER_VAR is depreciated, using $_SERVER instead
Download (0.013MB)
Added: 2006-06-20 License: GPL (GNU General Public License) Price:
1224 downloads
CMS Made Simple 0.10.1
CMS Made Simple is a simple and effective way of managing content of primarily static sites. more>>
The aim of CMS Made Simple is to supply a simple and effective way of managing content of primarily static sites. Before you can ask why you need a content management system for a site that doesnt change its content, let me tell you.
There are tons of content management systems out there but they are basically all the same. Other CMS systems are great if you have a lot of news or articles on your site, but what if your site content doesnt change a lot, or only small parts of it change? Doesnt make a lot of sense to create a new entry in your blog style site just for a simple update, and whats the point of having time stamped blog entries if you are constantly updating them? Voila, in comes CMS Made Simple.
CMS lets you update your pages and keep the content on a static page that will not become stale regardless of how much other content gets placed on your site, unlike a blog style site where entries get pushed off the page and your users have to check the archives or know an obscure link to get to the original story.
Main features:
- Easy user and group management
- Group-based permission system
- Intelligent caching mechanism to only get what is necessary from the database
- Full template support, for unlimted looks without changing a line of content
- Easy wizard based install and upgrade procedures
- Minimal requirements
- Admin panel with multiple language support
- Integrated, Optional WYSIWYG
- Content hierarchy with unlimited depth and size
- Optional self-generating menus
- Integrated file manager w/ upload capabilities
- Module API for unlimited expandability
- Integrated audit log
- Included News module
- Included RSS module
- Ability to program simple PHP coded plugins right inside the admin
- Friendly support in forums and irc
<<lessThere are tons of content management systems out there but they are basically all the same. Other CMS systems are great if you have a lot of news or articles on your site, but what if your site content doesnt change a lot, or only small parts of it change? Doesnt make a lot of sense to create a new entry in your blog style site just for a simple update, and whats the point of having time stamped blog entries if you are constantly updating them? Voila, in comes CMS Made Simple.
CMS lets you update your pages and keep the content on a static page that will not become stale regardless of how much other content gets placed on your site, unlike a blog style site where entries get pushed off the page and your users have to check the archives or know an obscure link to get to the original story.
Main features:
- Easy user and group management
- Group-based permission system
- Intelligent caching mechanism to only get what is necessary from the database
- Full template support, for unlimted looks without changing a line of content
- Easy wizard based install and upgrade procedures
- Minimal requirements
- Admin panel with multiple language support
- Integrated, Optional WYSIWYG
- Content hierarchy with unlimited depth and size
- Optional self-generating menus
- Integrated file manager w/ upload capabilities
- Module API for unlimited expandability
- Integrated audit log
- Included News module
- Included RSS module
- Ability to program simple PHP coded plugins right inside the admin
- Friendly support in forums and irc
Download (0.95MB)
Added: 2005-09-09 License: GPL (GNU General Public License) Price:
1507 downloads
PekSystray 0.4.0
PekSystray is a notification area (system tray) dockapp. more>>
PekSystray is a system tray dockapp similar to the GNOME notification area applet. But its designed for any window manager supporting.
Installation:
The `configure shell script attempts to guess correct values for various system-dependent variables used during compilation.
It uses those values to create a `Makefile in each directory of the package. It may also create one or more `.h files containing system-dependent definitions.
Finally, it creates a shell script `config.status that you can run in the future to recreate the current configuration, and a file `config.log containing compiler output (useful mainly for debugging `configure).
It can also use an optional file (typically called `config.cache and enabled with `--cache-file=config.cache or simply `-C) that saves the results of its tests to speed up reconfiguring. (Caching is disabled by default to prevent problems with accidental use of stale cache files.)
If you need to do unusual things to compile the package, please try to figure out how `configure could check whether to do them, and mail diffs or instructions to the address given in the `README so they can be considered for the next release.
If you are using the cache, and at some point `config.cache contains results you dont want to keep, you may remove or edit it.
The file `configure.ac (or `configure.in) is used to create `configure by a program called `autoconf. You only need `configure.ac if you want to change it or regenerate `configure using a newer version of `autoconf.
The simplest way to compile this package is:
1. `cd to the directory containing the packages source code and type `./configure to configure the package for your system.
If youre using `csh on an old version of System V, you might need to type `sh ./configure instead to prevent `csh from trying to execute `configure itself.
Running `configure takes awhile. While running, it prints some messages telling which features it is checking for.
2. Type `make to compile the package.
3. Optionally, type `make check to run any self-tests that come with the package.
4. Type `make install to install the programs and any data files and documentation.
5. You can remove the program binaries and object files from the source code directory by typing `make clean. To also remove the files that `configure created (so you can compile the package for a different kind of computer), type `make distclean.
There is also a `make maintainer-clean target, but that is intended mainly for the packages developers. If you use it, you may have to get all sorts of other programs in order to regenerate files that came with the distribution.
Enhancements:
- Complete reorganisation of the interface and code.
- Support for an unlimited number of icons.
- This release will only allocate necessary memory.
- It automatically creates another dock when the first one is full.
- --width and --height are available, superceding --vertical and --square.
- --multiple is the default now; it has been removed and --no-multiple added.
- A bug where some applications (grip, castpodder, etc.) had their icons at 0,0 has been fixed.
<<lessInstallation:
The `configure shell script attempts to guess correct values for various system-dependent variables used during compilation.
It uses those values to create a `Makefile in each directory of the package. It may also create one or more `.h files containing system-dependent definitions.
Finally, it creates a shell script `config.status that you can run in the future to recreate the current configuration, and a file `config.log containing compiler output (useful mainly for debugging `configure).
It can also use an optional file (typically called `config.cache and enabled with `--cache-file=config.cache or simply `-C) that saves the results of its tests to speed up reconfiguring. (Caching is disabled by default to prevent problems with accidental use of stale cache files.)
If you need to do unusual things to compile the package, please try to figure out how `configure could check whether to do them, and mail diffs or instructions to the address given in the `README so they can be considered for the next release.
If you are using the cache, and at some point `config.cache contains results you dont want to keep, you may remove or edit it.
The file `configure.ac (or `configure.in) is used to create `configure by a program called `autoconf. You only need `configure.ac if you want to change it or regenerate `configure using a newer version of `autoconf.
The simplest way to compile this package is:
1. `cd to the directory containing the packages source code and type `./configure to configure the package for your system.
If youre using `csh on an old version of System V, you might need to type `sh ./configure instead to prevent `csh from trying to execute `configure itself.
Running `configure takes awhile. While running, it prints some messages telling which features it is checking for.
2. Type `make to compile the package.
3. Optionally, type `make check to run any self-tests that come with the package.
4. Type `make install to install the programs and any data files and documentation.
5. You can remove the program binaries and object files from the source code directory by typing `make clean. To also remove the files that `configure created (so you can compile the package for a different kind of computer), type `make distclean.
There is also a `make maintainer-clean target, but that is intended mainly for the packages developers. If you use it, you may have to get all sorts of other programs in order to regenerate files that came with the distribution.
Enhancements:
- Complete reorganisation of the interface and code.
- Support for an unlimited number of icons.
- This release will only allocate necessary memory.
- It automatically creates another dock when the first one is full.
- --width and --height are available, superceding --vertical and --square.
- --multiple is the default now; it has been removed and --no-multiple added.
- A bug where some applications (grip, castpodder, etc.) had their icons at 0,0 has been fixed.
Download (0.069MB)
Added: 2007-01-09 License: GPL (GNU General Public License) Price:
1019 downloads
libRational 0.3.0
libRational is a C++ class library for rational arithmetic. more>>
libRational is a C++ class library for rational arithmetic.
Installation:
The `configure shell script attempts to guess correct values for various system-dependent variables used during compilation.
It uses those values to create a `Makefile in each directory of the package. It may also create one or more `.h files containing system-dependent definitions.
Finally, it creates a shell script `config.status that you can run in the future to recreate the current configuration, and a file `config.log containing compiler output (useful mainly for debugging `configure).
It can also use an optional file (typically called `config.cache and enabled with `--cache-file=config.cache or simply `-C) that saves the results of its tests to speed up reconfiguring. (Caching is disabled by default to prevent problems with accidental use of stale cache files.)
If you need to do unusual things to compile the package, please try to figure out how `configure could check whether to do them, and mail diffs or instructions to the address given in the `README so they can be considered for the next release.
If you are using the cache, and at some point `config.cache contains results you dont want to keep, you may remove or edit it.
The file `configure.ac (or `configure.in) is used to create `configure by a program called `autoconf. You only need `configure.ac if you want to change it or regenerate `configure using a newer version of `autoconf.
The simplest way to compile this package is:
1. `cd to the directory containing the packages source code and type `./configure to configure the package for your system.
If youre using `csh on an old version of System V, you might need to type `sh ./configure instead to prevent `csh from trying to execute `configure itself.
Running `configure takes awhile. While running, it prints some messages telling which features it is checking for.
2. Type `make to compile the package.
3. Optionally, type `make check to run any self-tests that come with the package.
4. Type `make install to install the programs and any data files and documentation.
5. You can remove the program binaries and object files from the source code directory by typing `make clean. To also remove the files that `configure created (so you can compile the package for a different kind of computer), type `make distclean.
There is also a `make maintainer-clean target, but that is intended mainly for the packages developers. If you use it, you may have to get all sorts of other programs in order to regenerate files that came with the distribution.
Enhancements:
- src/BigInt.hh: removed #ifdef structures
- src/BigInt.icc: assignation BigInt = MpIeee moved to source file
- src/TmpBigInt.hh: moved constructor from MpIeee to source file
- src/b_BigInt_MpIeee.cpp: moved constructor/assign MpIeee to this file
- src/r_toMpIeee.cpp: wrong FPParams constructor was called
<<lessInstallation:
The `configure shell script attempts to guess correct values for various system-dependent variables used during compilation.
It uses those values to create a `Makefile in each directory of the package. It may also create one or more `.h files containing system-dependent definitions.
Finally, it creates a shell script `config.status that you can run in the future to recreate the current configuration, and a file `config.log containing compiler output (useful mainly for debugging `configure).
It can also use an optional file (typically called `config.cache and enabled with `--cache-file=config.cache or simply `-C) that saves the results of its tests to speed up reconfiguring. (Caching is disabled by default to prevent problems with accidental use of stale cache files.)
If you need to do unusual things to compile the package, please try to figure out how `configure could check whether to do them, and mail diffs or instructions to the address given in the `README so they can be considered for the next release.
If you are using the cache, and at some point `config.cache contains results you dont want to keep, you may remove or edit it.
The file `configure.ac (or `configure.in) is used to create `configure by a program called `autoconf. You only need `configure.ac if you want to change it or regenerate `configure using a newer version of `autoconf.
The simplest way to compile this package is:
1. `cd to the directory containing the packages source code and type `./configure to configure the package for your system.
If youre using `csh on an old version of System V, you might need to type `sh ./configure instead to prevent `csh from trying to execute `configure itself.
Running `configure takes awhile. While running, it prints some messages telling which features it is checking for.
2. Type `make to compile the package.
3. Optionally, type `make check to run any self-tests that come with the package.
4. Type `make install to install the programs and any data files and documentation.
5. You can remove the program binaries and object files from the source code directory by typing `make clean. To also remove the files that `configure created (so you can compile the package for a different kind of computer), type `make distclean.
There is also a `make maintainer-clean target, but that is intended mainly for the packages developers. If you use it, you may have to get all sorts of other programs in order to regenerate files that came with the distribution.
Enhancements:
- src/BigInt.hh: removed #ifdef structures
- src/BigInt.icc: assignation BigInt = MpIeee moved to source file
- src/TmpBigInt.hh: moved constructor from MpIeee to source file
- src/b_BigInt_MpIeee.cpp: moved constructor/assign MpIeee to this file
- src/r_toMpIeee.cpp: wrong FPParams constructor was called
Download (0.41MB)
Added: 2005-10-05 License: GPL (GNU General Public License) Price:
1479 downloads
Rocks Cluster 4.3
Rocks Cluster Tool Kit is a Turnkey Linux COTS Clusters for x86 and IA64. more>>
Rocks Cluster is a complete "cluster on a CD" solution for x86 and IA64 Red Hat Linux COTS clusters.
Building a Rocks cluster does not require any experience in clustering, yet a cluster architect will find a flexible and programmatic way to redesign the entire software stack just below the surface (appropriately hidden from the majority of users).
Although Rocks includes the tools expected from any clustering software stack (PBS, Maui, GM support, Ganglia, etc), it is unique in its simplicity of installation.
From a hardware component and raw processing power perspective, commodity clusters are phenomenal price/performance compute engines. However, if a scalable ``cluster management strategy is not adopted, the favorable economics of clusters are offset by the additional on-going personnel costs involved to ``care and feed for the machine. The complexity of cluster management (e.g., determining if all nodes have a consistent set of software) often overwhelms part-time cluster administrators, who are usually domain application scientists. When this occurs, machine state is forced to either of two extremes: the cluster is not stable due to configuration problems, or software becomes stale, security holes abound, and known software bugs remain unpatched.
While earlier clustering toolkits expend a great deal of effort (i.e., software) to compare configurations of nodes, Rocks makes complete Operating System (OS) installation on a node the basic management tool. With attention to complete automation of this process, it becomes faster to reinstall all nodes to a known configuration than it is to determine if nodes were out of synchronization in the first place. Unlike a users desktop, the OS on a cluster node is considered to be soft state that can be changed and/or updated rapidly.
This is clearly more heavywieght than the philosophy of configuration management tools [Cfengine] that perform exhaustive examination and parity checking of an installed OS. At first glance, it seems wrong to reinstall the OS when a configuration parameter needs to be changed. Indeed, for a single node this might seem too severe. However, this approach scales exceptionally well, making it a preferred mode for even a modest-sized cluster. Because the OS can be installed from scratch in a short period of time, different (and perhaps incompatible) application-specific configurations can easily be installed on nodes. In addition, this structure insures any upgrade will not interfere with actively running jobs.
One of the key ingredients of Rocks is a robust mechanism to produce customized distributions (with security patches pre-applied) that define the complete set of software for a particular node. A cluster may require several node types including compute nodes, frontend nodes file servers, and monitoring nodes. Each of these roles requires a specialized software set. Within a distribution, different node types are defined with a machine specific Red Hat Kickstart file, made from a Rocks Kickstart Graph.
A Kickstart file is a text-based description of all the software packages and software configuration to be deployed on a node. The Rocks Kickstart Graph is an XML-based tree structure used to define RedHat Kickstart files. By using a graph, Rocks can efficiently define node types without duplicating shared components. Similiar to mammalian species sharing 80% of their genes, Rocks node types share much of their software set. The Rocks Kickstart Graph easily defines the differences between node types without duplicating the description of their similarities. See the Bibliography section for papers that describe the design of this structure in more depth.
By leveraging this installation technology, we can abstract out many of the hardware differences and allow the Kickstart process to autodetect the correct hardware modules to load (e.g., disk subsystem type: SCSI, IDE, integrated RAID adapter; Ethernet interfaces; and high-speed network interfaces). Further, we benefit from the robust and rich support that commercial Linux distributions must have to be viable in todays rapidly advancing marketplace.
Wherever possible, Rocks uses automatic methods to determine configuration differences. Yet, because clusters are unified machines, there are a few services that require ``global knowledge of the machine -- e.g., a listing of all compute nodes for the hosts database and queuing system. Rocks uses an SQL database to store the definitions of these global configurations and then generates database reports to create service-specific configuration files (e.g., DHCP configuration file, /etc/hosts, and PBS nodes file).
Enhancements:
- Rocks v4.3 is released for i386 and x86_64 CPU architectures. New features: Rocks command line - initial release of the Rocks command line which facilitates non-SQL administrative access to the database; PXE First - hosts can now be configured in BIOS with a boot order of CD, PXE, hard disk. Enhancements: based on CentOS 4.5 and all updates as of July 4, 2007; Anaconda installer updated to 10.1.1.63; performance improvement when building torrent files for the Avalanche Installer; database indirects, more flexibility with Rocks variables; Globus updated to gt4.0.4 with web services....
<<lessBuilding a Rocks cluster does not require any experience in clustering, yet a cluster architect will find a flexible and programmatic way to redesign the entire software stack just below the surface (appropriately hidden from the majority of users).
Although Rocks includes the tools expected from any clustering software stack (PBS, Maui, GM support, Ganglia, etc), it is unique in its simplicity of installation.
From a hardware component and raw processing power perspective, commodity clusters are phenomenal price/performance compute engines. However, if a scalable ``cluster management strategy is not adopted, the favorable economics of clusters are offset by the additional on-going personnel costs involved to ``care and feed for the machine. The complexity of cluster management (e.g., determining if all nodes have a consistent set of software) often overwhelms part-time cluster administrators, who are usually domain application scientists. When this occurs, machine state is forced to either of two extremes: the cluster is not stable due to configuration problems, or software becomes stale, security holes abound, and known software bugs remain unpatched.
While earlier clustering toolkits expend a great deal of effort (i.e., software) to compare configurations of nodes, Rocks makes complete Operating System (OS) installation on a node the basic management tool. With attention to complete automation of this process, it becomes faster to reinstall all nodes to a known configuration than it is to determine if nodes were out of synchronization in the first place. Unlike a users desktop, the OS on a cluster node is considered to be soft state that can be changed and/or updated rapidly.
This is clearly more heavywieght than the philosophy of configuration management tools [Cfengine] that perform exhaustive examination and parity checking of an installed OS. At first glance, it seems wrong to reinstall the OS when a configuration parameter needs to be changed. Indeed, for a single node this might seem too severe. However, this approach scales exceptionally well, making it a preferred mode for even a modest-sized cluster. Because the OS can be installed from scratch in a short period of time, different (and perhaps incompatible) application-specific configurations can easily be installed on nodes. In addition, this structure insures any upgrade will not interfere with actively running jobs.
One of the key ingredients of Rocks is a robust mechanism to produce customized distributions (with security patches pre-applied) that define the complete set of software for a particular node. A cluster may require several node types including compute nodes, frontend nodes file servers, and monitoring nodes. Each of these roles requires a specialized software set. Within a distribution, different node types are defined with a machine specific Red Hat Kickstart file, made from a Rocks Kickstart Graph.
A Kickstart file is a text-based description of all the software packages and software configuration to be deployed on a node. The Rocks Kickstart Graph is an XML-based tree structure used to define RedHat Kickstart files. By using a graph, Rocks can efficiently define node types without duplicating shared components. Similiar to mammalian species sharing 80% of their genes, Rocks node types share much of their software set. The Rocks Kickstart Graph easily defines the differences between node types without duplicating the description of their similarities. See the Bibliography section for papers that describe the design of this structure in more depth.
By leveraging this installation technology, we can abstract out many of the hardware differences and allow the Kickstart process to autodetect the correct hardware modules to load (e.g., disk subsystem type: SCSI, IDE, integrated RAID adapter; Ethernet interfaces; and high-speed network interfaces). Further, we benefit from the robust and rich support that commercial Linux distributions must have to be viable in todays rapidly advancing marketplace.
Wherever possible, Rocks uses automatic methods to determine configuration differences. Yet, because clusters are unified machines, there are a few services that require ``global knowledge of the machine -- e.g., a listing of all compute nodes for the hosts database and queuing system. Rocks uses an SQL database to store the definitions of these global configurations and then generates database reports to create service-specific configuration files (e.g., DHCP configuration file, /etc/hosts, and PBS nodes file).
Enhancements:
- Rocks v4.3 is released for i386 and x86_64 CPU architectures. New features: Rocks command line - initial release of the Rocks command line which facilitates non-SQL administrative access to the database; PXE First - hosts can now be configured in BIOS with a boot order of CD, PXE, hard disk. Enhancements: based on CentOS 4.5 and all updates as of July 4, 2007; Anaconda installer updated to 10.1.1.63; performance improvement when building torrent files for the Avalanche Installer; database indirects, more flexibility with Rocks variables; Globus updated to gt4.0.4 with web services....
Download (601MB)
Added: 2007-07-07 License: BSD License Price:
511 downloads
xrestop 0.4
xrestop is a utility to monitor the usage of resources within the X Server, and display them in a manner similar to top. more>>
xrestop project is a utility to monitor the usage of resources within the X Server, and display them in a manner similar to top.
Xrestop uses the X-Resource extension to provide top like statistics of each connected X11 clients server side resource usage. It is intended as a developer tool to aid more efficient server resource usage and debug server side leakage.
It should work with any server supporting the X-Resource extension, including the freedesktop.org server and XFree86 4.3+. "xdpyinfo | grep Resource" should tell you if your server supports this extension.
Installation:
The `configure shell script attempts to guess correct values for various system-dependent variables used during compilation. It uses those values to create a `Makefile in each directory of the package.
It may also create one or more `.h files containing system-dependent definitions. Finally, it creates a shell script `config.status that you can run in the future to recreate the current configuration, and a file `config.log containing compiler output (useful mainly for debugging `configure).
It can also use an optional file (typically called `config.cache and enabled with `--cache-file=config.cache or simply `-C) that saves the results of its tests to speed up reconfiguring. (Caching is disabled by default to prevent problems with accidental use of stale cache files.)
If you need to do unusual things to compile the package, please try to figure out how `configure could check whether to do them, and mail diffs or instructions to the address given in the `README so they can be considered for the next release.
If you are using the cache, and at some point `config.cache contains results you dont want to keep, you may remove or edit it.
The file `configure.ac (or `configure.in) is used to create `configure by a program called `autoconf. You only need `configure.ac if you want to change it or regenerate `configure using a newer version of `autoconf.
The simplest way to compile this package is:
1. `cd to the directory containing the packages source code and type `./configure to configure the package for your system.
If youre using `csh on an old version of System V, you might need to type `sh ./configure instead to prevent `csh from trying to execute
`configure itself.
Running `configure takes awhile. While running, it prints some messages telling which features it is checking for.
2. Type `make to compile the package.
3. Optionally, type `make check to run any self-tests that come with the package.
4. Type `make install to install the programs and any data files and documentation.
5. You can remove the program binaries and object files from the source code directory by typing `make clean. To also remove the files that `configure created (so you can compile the package for a different kind of computer), type `make distclean.
There is also a `make maintainer-clean target, but that is intended mainly for the packages developers. If you use it, you may have to get all sorts of other programs in order to regenerate files that came with the distribution.
<<lessXrestop uses the X-Resource extension to provide top like statistics of each connected X11 clients server side resource usage. It is intended as a developer tool to aid more efficient server resource usage and debug server side leakage.
It should work with any server supporting the X-Resource extension, including the freedesktop.org server and XFree86 4.3+. "xdpyinfo | grep Resource" should tell you if your server supports this extension.
Installation:
The `configure shell script attempts to guess correct values for various system-dependent variables used during compilation. It uses those values to create a `Makefile in each directory of the package.
It may also create one or more `.h files containing system-dependent definitions. Finally, it creates a shell script `config.status that you can run in the future to recreate the current configuration, and a file `config.log containing compiler output (useful mainly for debugging `configure).
It can also use an optional file (typically called `config.cache and enabled with `--cache-file=config.cache or simply `-C) that saves the results of its tests to speed up reconfiguring. (Caching is disabled by default to prevent problems with accidental use of stale cache files.)
If you need to do unusual things to compile the package, please try to figure out how `configure could check whether to do them, and mail diffs or instructions to the address given in the `README so they can be considered for the next release.
If you are using the cache, and at some point `config.cache contains results you dont want to keep, you may remove or edit it.
The file `configure.ac (or `configure.in) is used to create `configure by a program called `autoconf. You only need `configure.ac if you want to change it or regenerate `configure using a newer version of `autoconf.
The simplest way to compile this package is:
1. `cd to the directory containing the packages source code and type `./configure to configure the package for your system.
If youre using `csh on an old version of System V, you might need to type `sh ./configure instead to prevent `csh from trying to execute
`configure itself.
Running `configure takes awhile. While running, it prints some messages telling which features it is checking for.
2. Type `make to compile the package.
3. Optionally, type `make check to run any self-tests that come with the package.
4. Type `make install to install the programs and any data files and documentation.
5. You can remove the program binaries and object files from the source code directory by typing `make clean. To also remove the files that `configure created (so you can compile the package for a different kind of computer), type `make distclean.
There is also a `make maintainer-clean target, but that is intended mainly for the packages developers. If you use it, you may have to get all sorts of other programs in order to regenerate files that came with the distribution.
Download (0.087MB)
Added: 2006-03-10 License: GPL (GNU General Public License) Price:
1324 downloads
wmappl 0.71
wmappl is a simple scrolling application launcher for the WindowMaker dock. more>>
wmappl is a simple scrolling application launcher for the WindowMaker dock. It is loosely based off of WMButton by Edward Flora.
Given a list of programs and icons, wmappl displays up to six icons at a time. Scroll buttons or the mouse scroll wheel may be used to cycle through additional programs.
Installation:
The `configure shell script attempts to guess correct values for various system-dependent variables used during compilation.
It uses those values to create a `Makefile in each directory of the package. It may also create one or more `.h files containing system-dependent definitions.
Finally, it creates a shell script `config.status that you can run in the future to recreate the current configuration, and a file `config.log containing compiler output (useful mainly for debugging `configure).
It can also use an optional file (typically called `config.cache and enabled with `--cache-file=config.cache or simply `-C) that saves the results of its tests to speed up reconfiguring. (Caching is disabled by default to prevent problems with accidental use of stale cache files.)
If you need to do unusual things to compile the package, please try to figure out how `configure could check whether to do them, and mail diffs or instructions to the address given in the `README so they can be considered for the next release.
If you are using the cache, and at some point `config.cache contains results you dont want to keep, you may remove or edit it.
The file `configure.ac (or `configure.in) is used to create `configure by a program called `autoconf. You only need `configure.ac if you want to change it or regenerate `configure using a newer version of `autoconf.
The simplest way to compile this package is:
1. `cd to the directory containing the packages source code and type `./configure to configure the package for your system.
If youre using `csh on an old version of System V, you might need to type `sh ./configure instead to prevent `csh from trying to execute `configure itself.
Running `configure takes awhile. While running, it prints some messages telling which features it is checking for.
2. Type `make to compile the package.
3. Optionally, type `make check to run any self-tests that come with the package.
4. Type `make install to install the programs and any data files and documentation.
5. You can remove the program binaries and object files from the source code directory by typing `make clean. To also remove the files that `configure created (so you can compile the package for a different kind of computer), type `make distclean.
There is also a `make maintainer-clean target, but that is intended mainly for the packages developers. If you use it, you may have to get all sorts of other programs in order to regenerate files that came with the distribution.
Enhancements:
- man/wmapplrc.5: updated for tooltip_font option
<<lessGiven a list of programs and icons, wmappl displays up to six icons at a time. Scroll buttons or the mouse scroll wheel may be used to cycle through additional programs.
Installation:
The `configure shell script attempts to guess correct values for various system-dependent variables used during compilation.
It uses those values to create a `Makefile in each directory of the package. It may also create one or more `.h files containing system-dependent definitions.
Finally, it creates a shell script `config.status that you can run in the future to recreate the current configuration, and a file `config.log containing compiler output (useful mainly for debugging `configure).
It can also use an optional file (typically called `config.cache and enabled with `--cache-file=config.cache or simply `-C) that saves the results of its tests to speed up reconfiguring. (Caching is disabled by default to prevent problems with accidental use of stale cache files.)
If you need to do unusual things to compile the package, please try to figure out how `configure could check whether to do them, and mail diffs or instructions to the address given in the `README so they can be considered for the next release.
If you are using the cache, and at some point `config.cache contains results you dont want to keep, you may remove or edit it.
The file `configure.ac (or `configure.in) is used to create `configure by a program called `autoconf. You only need `configure.ac if you want to change it or regenerate `configure using a newer version of `autoconf.
The simplest way to compile this package is:
1. `cd to the directory containing the packages source code and type `./configure to configure the package for your system.
If youre using `csh on an old version of System V, you might need to type `sh ./configure instead to prevent `csh from trying to execute `configure itself.
Running `configure takes awhile. While running, it prints some messages telling which features it is checking for.
2. Type `make to compile the package.
3. Optionally, type `make check to run any self-tests that come with the package.
4. Type `make install to install the programs and any data files and documentation.
5. You can remove the program binaries and object files from the source code directory by typing `make clean. To also remove the files that `configure created (so you can compile the package for a different kind of computer), type `make distclean.
There is also a `make maintainer-clean target, but that is intended mainly for the packages developers. If you use it, you may have to get all sorts of other programs in order to regenerate files that came with the distribution.
Enhancements:
- man/wmapplrc.5: updated for tooltip_font option
Download (0.13MB)
Added: 2005-10-10 License: GPL (GNU General Public License) Price:
1474 downloads
Natural Language Toolkit 0.8
Natural Language Toolkit is a suite of Python libraries and programs for symbolic and statistical natural language processing. more>>
Natural Language Toolkit is a suite of Python libraries and programs for symbolic and statistical natural language processing. NLTK includes graphical demonstrations and sample data.
It is accompanied by extensive documentation, including tutorials that explain the underlying concepts behind the language processing tasks supported by the toolkit.
Documentation:
A substantial amount of documentation about how to use NLTK is available from the nltk home page:
< http://nltk.sourceforge.net >
In particular, the NLTK home page contains three types of documentation:
- Tutorials teach students how to use the toolkit, in the context of performing specific tasks. They are appropriate for anyone who wishes to learn how to use the toolkit.
< http://nltk.sourceforge.net/tutorial/ >
- The toolkits reference documentation describes every module, interface, class, method, function, and variable in the toolkit. This documentation should be useful to both users and developers.
< http://nltk.sourceforge.net/ref/nltk.html >
- A number of technical reports are available. These reports explain and justify the toolkits design and implementation. They are used by the developers of the toolkit to guide and document the toolkits construction. Students can consult these reports if they would like further information about how the toolkit is designed and why it is designed that way.
< http://nltk.sourceforge.net/tech/ >
Enhancements:
Code (major):
- changed package name to nltk
- import all top-level modules into nltk, reducing need for import statements
- reorganization of sub-package structures to simplify imports
- new featstruct module, unifying old featurelite and featurestructure modules
- FreqDist now inherits from dict, fd.count(sample) becomes fd[sample]
- FreqDist initializer permits: fd = FreqDist(len(token) for token in text)
- made numpy optional
Code (minor):
- changed GrammarFile initializer to accept filename
- consistent tree display format
- fixed loading process for WordNet and TIMIT that prevented code installation if data not installed
- taken more care with unicode types
- incorporated pcfg code into cfg module
- moved cfg, tree, featstruct to top level
- new filebroker module to make handling of example grammar files more transparent
- more corpus readers (webtext, abc)
- added cfg.covers() to check that a grammar covers a sentence
- simple text-based wordnet browser
- known bug: parse/featurechart.py uses incorrect apply() function
Corpora:
- csv data file to document NLTK corpora
Contrib:
- added Glue semantics code (contrib.glue, by Dan Garrette)
- Punkt sentence segmenter port (contrib.punkt, by Willy)
- added LPath interpreter (contrib.lpath, by Haejoong Lee)
- extensive work on classifiers (contrib.classifier*, Sumukh Ghodke)
Tutorials:
- polishing on parts I, II
- more illustrations, data plots, summaries, exercises
- continuing to make prose more accessible to non-linguistic audience
- new default import that all chapters presume: from nltk.book import *
Distributions:
- updated to latest version of numpy
- removed WordNet installation instructions as WordNet is now included in corpus distribution
- added pylab (matplotlib)
Enhancements:
Code:
- changed nltk.__init__ imports to explicitly import names from top-level modules
- changed corpus.util to use the rb flag for opening files, to fix problems reading corpora under MSWindows
- updated stale examples in engineering.txt
- extended feature stucture interface to permit chained features, e.g. fs[F,G]
- further misc improvements to test code plus some bugfixes
Tutorials:
- rewritten opening section of tagging chapter
- reorganized some exercises
<<lessIt is accompanied by extensive documentation, including tutorials that explain the underlying concepts behind the language processing tasks supported by the toolkit.
Documentation:
A substantial amount of documentation about how to use NLTK is available from the nltk home page:
< http://nltk.sourceforge.net >
In particular, the NLTK home page contains three types of documentation:
- Tutorials teach students how to use the toolkit, in the context of performing specific tasks. They are appropriate for anyone who wishes to learn how to use the toolkit.
< http://nltk.sourceforge.net/tutorial/ >
- The toolkits reference documentation describes every module, interface, class, method, function, and variable in the toolkit. This documentation should be useful to both users and developers.
< http://nltk.sourceforge.net/ref/nltk.html >
- A number of technical reports are available. These reports explain and justify the toolkits design and implementation. They are used by the developers of the toolkit to guide and document the toolkits construction. Students can consult these reports if they would like further information about how the toolkit is designed and why it is designed that way.
< http://nltk.sourceforge.net/tech/ >
Enhancements:
Code (major):
- changed package name to nltk
- import all top-level modules into nltk, reducing need for import statements
- reorganization of sub-package structures to simplify imports
- new featstruct module, unifying old featurelite and featurestructure modules
- FreqDist now inherits from dict, fd.count(sample) becomes fd[sample]
- FreqDist initializer permits: fd = FreqDist(len(token) for token in text)
- made numpy optional
Code (minor):
- changed GrammarFile initializer to accept filename
- consistent tree display format
- fixed loading process for WordNet and TIMIT that prevented code installation if data not installed
- taken more care with unicode types
- incorporated pcfg code into cfg module
- moved cfg, tree, featstruct to top level
- new filebroker module to make handling of example grammar files more transparent
- more corpus readers (webtext, abc)
- added cfg.covers() to check that a grammar covers a sentence
- simple text-based wordnet browser
- known bug: parse/featurechart.py uses incorrect apply() function
Corpora:
- csv data file to document NLTK corpora
Contrib:
- added Glue semantics code (contrib.glue, by Dan Garrette)
- Punkt sentence segmenter port (contrib.punkt, by Willy)
- added LPath interpreter (contrib.lpath, by Haejoong Lee)
- extensive work on classifiers (contrib.classifier*, Sumukh Ghodke)
Tutorials:
- polishing on parts I, II
- more illustrations, data plots, summaries, exercises
- continuing to make prose more accessible to non-linguistic audience
- new default import that all chapters presume: from nltk.book import *
Distributions:
- updated to latest version of numpy
- removed WordNet installation instructions as WordNet is now included in corpus distribution
- added pylab (matplotlib)
Enhancements:
Code:
- changed nltk.__init__ imports to explicitly import names from top-level modules
- changed corpus.util to use the rb flag for opening files, to fix problems reading corpora under MSWindows
- updated stale examples in engineering.txt
- extended feature stucture interface to permit chained features, e.g. fs[F,G]
- further misc improvements to test code plus some bugfixes
Tutorials:
- rewritten opening section of tagging chapter
- reorganized some exercises
Download (MB)
Added: 2007-07-03 License: GPL (GNU General Public License) Price:
850 downloads
libencio 0.1
libencio is a stdio-like symmetric key encryption library. more>>
libencio is a library providing stdio-like interface for reading and writing of encrypted files in MCrypt format. Additionally, through creation of an "index", libencio provices full support for fseek()-like random read access of encrypted data.
This allows one to operate on MCrypt-encrypted files as if they were ordinary, cleartext files.
Installation:
The `configure shell script attempts to guess correct values for various system-dependent variables used during compilation.
It uses those values to create a `Makefile in each directory of the package. It may also create one or more `.h files containing system-dependent definitions.
Finally, it creates a shell script `config.status that you can run in the future to recreate the current configuration, and a file `config.log containing compiler output (useful mainly for
debugging `configure).
It can also use an optional file (typically called `config.cache and enabled with `--cache-file=config.cache or simply `-C) that saves the results of its tests to speed up reconfiguring. (Caching is disabled by default to prevent problems with accidental use of stale cache files.)
If you need to do unusual things to compile the package, please try to figure out how `configure could check whether to do them, and mail diffs or instructions to the address given in the `README so they can be considered for the next release.
If you are using the cache, and at some point `config.cache contains results you dont want to keep, you may remove or edit it.
The file `configure.ac (or `configure.in) is used to create `configure by a program called `autoconf. You only need `configure.ac if you want to change it or regenerate `configure using a newer version of `autoconf.
The simplest way to compile this package is:
1. `cd to the directory containing the packages source code and type `./configure to configure the package for your system. If youre using `csh on an old version of System V, you might need to type `sh ./configure instead to prevent `csh from trying to execute
`configure itself.
Running `configure takes awhile. While running, it prints some messages telling which features it is checking for.
2. Type `make to compile the package.
3. Optionally, type `make check to run any self-tests that come with the package.
4. Type `make install to install the programs and any data files and documentation.
5. You can remove the program binaries and object files from the source code directory by typing `make clean. To also remove the files that `configure created (so you can compile the package for a different kind of computer), type `make distclean.
There is also a `make maintainer-clean target, but that is intended mainly for the packages developers. If you use it, you may have to get all sorts of other programs in order to regenerate files that came with the distribution.
<<lessThis allows one to operate on MCrypt-encrypted files as if they were ordinary, cleartext files.
Installation:
The `configure shell script attempts to guess correct values for various system-dependent variables used during compilation.
It uses those values to create a `Makefile in each directory of the package. It may also create one or more `.h files containing system-dependent definitions.
Finally, it creates a shell script `config.status that you can run in the future to recreate the current configuration, and a file `config.log containing compiler output (useful mainly for
debugging `configure).
It can also use an optional file (typically called `config.cache and enabled with `--cache-file=config.cache or simply `-C) that saves the results of its tests to speed up reconfiguring. (Caching is disabled by default to prevent problems with accidental use of stale cache files.)
If you need to do unusual things to compile the package, please try to figure out how `configure could check whether to do them, and mail diffs or instructions to the address given in the `README so they can be considered for the next release.
If you are using the cache, and at some point `config.cache contains results you dont want to keep, you may remove or edit it.
The file `configure.ac (or `configure.in) is used to create `configure by a program called `autoconf. You only need `configure.ac if you want to change it or regenerate `configure using a newer version of `autoconf.
The simplest way to compile this package is:
1. `cd to the directory containing the packages source code and type `./configure to configure the package for your system. If youre using `csh on an old version of System V, you might need to type `sh ./configure instead to prevent `csh from trying to execute
`configure itself.
Running `configure takes awhile. While running, it prints some messages telling which features it is checking for.
2. Type `make to compile the package.
3. Optionally, type `make check to run any self-tests that come with the package.
4. Type `make install to install the programs and any data files and documentation.
5. You can remove the program binaries and object files from the source code directory by typing `make clean. To also remove the files that `configure created (so you can compile the package for a different kind of computer), type `make distclean.
There is also a `make maintainer-clean target, but that is intended mainly for the packages developers. If you use it, you may have to get all sorts of other programs in order to regenerate files that came with the distribution.
Download (0.15MB)
Added: 2005-10-11 License: GPL (GNU General Public License) Price:
1473 downloads
StreamCruncher 2.1 RC
StreamCruncher is an Event Processor. more>>
StreamCruncher is an Event Processor. The project supports a language based on SQL which allows you to define Event Processing constructs like Sliding Windows, Time Based Windows, Partitions and Aggregates.
Queries can be written using this language, which are used to monitor streams of incoming Events. StreamCruncher is a multi-threaded Kernel that runs on Java.
Ever since RFID became commercially viable and companies started packaging their entire product line as Business Activity Monitoring Stacks, an old idea that has been around for almost a decade is now seeing the light of day. A handful of Startups have begun turning this Idea of Complex Event Processing (CEP) and Event Stream Processing (ESP) into Commercial grade software. Several people have contributed ideas to this field. The most frequently mentioned name would be Prof. Luckhams. Prof. Widoms contribution to the field is also noteworthy.
Those in a hurry can skip to this section.
Now, back to CEP and ESP. An over-simplified definition would probably look like this - Assume that a System produces "Events" that describe the state of that System at those instants. Slicing and Dicing the "live" Stream of Events (in near real-time) can reveal vital information. Since this information is available on the live data and not stale data, it can be used to look for Warning signs, implement JIT materials sourcing, Automated Trading and other highly nimble systems.
Events from multiple sources can be co-related to reveal information about their interactions and dependencies. CEP and ESP are not exactly the same, but well leave that to the Scholarly Papers to disambiguate. All this does not seem new at all to people whove been working on Control Systems. Data Warehouse specialists and Rule Engine experts might start mumbling something about "Old Wine..".
However, only lately are we seeing generic, off-the-shelf Software focusing on CEP and ESP. Each one of those Products or Projects distinguish themselves in Performance (Real-time, Soft Real-time), Ease of Integration (Features, Mild to Steep Learning Curves, Manageability), Speciality (Automated Trading Platforms) or General purpose stacks etc. Or, perhaps all of them, to varying degrees.
For a Program to continually Slice and Dice an Event Stream and thereby, discern/infer something useful about the state of the System before it goes stale, requires a variety of Technologies to converge. Weve been using SQL to handle Transactional Data stored in Databases, Data Warehouses to analyse Terrabytes of Offline data, Rule Engines to infer from a large collection of constantly changing Facts.
ESP and CEP Systems provide building blocks using which Users can build an intelligent System, with active feedback. All CEP and ESP Systems provide a mechanism by which Queries/Conditions/Criteria can be provided that are constantly evaluated against the Event Stream. Some systems provide drag-n-drop GUIs to specify such "Queries", while some have their own proprietary Query syntax. In essence, they provide a Domain Specific Language to encode such Queries/Rules, a facility to pump Events into the System and a way to channel the Output Stream to do something useful.
Enhancements:
- The pre-filter for input event streams now supports , !=, =, *, /, +, -, "in (..)", "not in (..)", "and", and "or".
- The "in" clause can refer to an SQL sub-query.
- Such sub-queries are cached by the kernel to improve performance.
- An additional property, cacherefresh.threads.num, can be configured to specify the number of sub-query cache processing threads to use.
- Two new test cases have been added to test the new features: H2StartupShutdown3Test and ThreeEventOrderTest.
<<lessQueries can be written using this language, which are used to monitor streams of incoming Events. StreamCruncher is a multi-threaded Kernel that runs on Java.
Ever since RFID became commercially viable and companies started packaging their entire product line as Business Activity Monitoring Stacks, an old idea that has been around for almost a decade is now seeing the light of day. A handful of Startups have begun turning this Idea of Complex Event Processing (CEP) and Event Stream Processing (ESP) into Commercial grade software. Several people have contributed ideas to this field. The most frequently mentioned name would be Prof. Luckhams. Prof. Widoms contribution to the field is also noteworthy.
Those in a hurry can skip to this section.
Now, back to CEP and ESP. An over-simplified definition would probably look like this - Assume that a System produces "Events" that describe the state of that System at those instants. Slicing and Dicing the "live" Stream of Events (in near real-time) can reveal vital information. Since this information is available on the live data and not stale data, it can be used to look for Warning signs, implement JIT materials sourcing, Automated Trading and other highly nimble systems.
Events from multiple sources can be co-related to reveal information about their interactions and dependencies. CEP and ESP are not exactly the same, but well leave that to the Scholarly Papers to disambiguate. All this does not seem new at all to people whove been working on Control Systems. Data Warehouse specialists and Rule Engine experts might start mumbling something about "Old Wine..".
However, only lately are we seeing generic, off-the-shelf Software focusing on CEP and ESP. Each one of those Products or Projects distinguish themselves in Performance (Real-time, Soft Real-time), Ease of Integration (Features, Mild to Steep Learning Curves, Manageability), Speciality (Automated Trading Platforms) or General purpose stacks etc. Or, perhaps all of them, to varying degrees.
For a Program to continually Slice and Dice an Event Stream and thereby, discern/infer something useful about the state of the System before it goes stale, requires a variety of Technologies to converge. Weve been using SQL to handle Transactional Data stored in Databases, Data Warehouses to analyse Terrabytes of Offline data, Rule Engines to infer from a large collection of constantly changing Facts.
ESP and CEP Systems provide building blocks using which Users can build an intelligent System, with active feedback. All CEP and ESP Systems provide a mechanism by which Queries/Conditions/Criteria can be provided that are constantly evaluated against the Event Stream. Some systems provide drag-n-drop GUIs to specify such "Queries", while some have their own proprietary Query syntax. In essence, they provide a Domain Specific Language to encode such Queries/Rules, a facility to pump Events into the System and a way to channel the Output Stream to do something useful.
Enhancements:
- The pre-filter for input event streams now supports , !=, =, *, /, +, -, "in (..)", "not in (..)", "and", and "or".
- The "in" clause can refer to an SQL sub-query.
- Such sub-queries are cached by the kernel to improve performance.
- An additional property, cacherefresh.threads.num, can be configured to specify the number of sub-query cache processing threads to use.
- Two new test cases have been added to test the new features: H2StartupShutdown3Test and ThreeEventOrderTest.
Download (3.9MB)
Added: 2007-07-19 License: Freeware Price:
828 downloads
libmoney 1.00
libmoney is a library written in C++ that allows a developer to build an application that keeps track of finances. more>>
libmoney is a library that allows a developer to build an application that keeps track of finances. It was originally developed to keep track of a budget, but can be expanded to keep track of all assets.
Installation:
The `configure shell script attempts to guess correct values for various system-dependent variables used during compilation.
It uses those values to create a `Makefile in each directory of the package. It may also create one or more `.h files containing system-dependent definitions.
Finally, it creates a shell script `config.status that you can run in the future to recreate the current configuration, and a file `config.log containing compiler output (useful mainly for
debugging `configure).
It can also use an optional file (typically called `config.cache and enabled with `--cache-file=config.cache or simply `-C) that saves the results of its tests to speed up reconfiguring. (Caching is disabled by default to prevent problems with accidental use of stale cache files.)
If you need to do unusual things to compile the package, please try to figure out how `configure could check whether to do them, and mail diffs or instructions to the address given in the `README so they can be considered for the next release.
If you are using the cache, and at some point `config.cache contains results you dont want to keep, you may remove or edit it.
The file `configure.ac (or `configure.in) is used to create `configure by a program called `autoconf. You only need `configure.ac if you want to change it or regenerate `configure using a newer version of `autoconf.
The simplest way to compile this package is:
1. `cd to the directory containing the packages source code and type `./configure to configure the package for your system.
If youre using `csh on an old version of System V, you might need to type `sh ./configure instead to prevent `csh from trying to execute `configure itself.
Running `configure takes awhile. While running, it prints some messages telling which features it is checking for.
2. Type `make to compile the package.
3. Optionally, type `make check to run any self-tests that come with the package.
4. Type `make install to install the programs and any data files and documentation.
5. You can remove the program binaries and object files from the source code directory by typing `make clean. To also remove the files that `configure created (so you can compile the package for a different kind of computer), type `make distclean.
There is also a `make maintainer-clean target, but that is intended mainly for the packages developers. If you use it, you may have to get all sorts of other programs in order to regenerate files that came with the distribution.
<<lessInstallation:
The `configure shell script attempts to guess correct values for various system-dependent variables used during compilation.
It uses those values to create a `Makefile in each directory of the package. It may also create one or more `.h files containing system-dependent definitions.
Finally, it creates a shell script `config.status that you can run in the future to recreate the current configuration, and a file `config.log containing compiler output (useful mainly for
debugging `configure).
It can also use an optional file (typically called `config.cache and enabled with `--cache-file=config.cache or simply `-C) that saves the results of its tests to speed up reconfiguring. (Caching is disabled by default to prevent problems with accidental use of stale cache files.)
If you need to do unusual things to compile the package, please try to figure out how `configure could check whether to do them, and mail diffs or instructions to the address given in the `README so they can be considered for the next release.
If you are using the cache, and at some point `config.cache contains results you dont want to keep, you may remove or edit it.
The file `configure.ac (or `configure.in) is used to create `configure by a program called `autoconf. You only need `configure.ac if you want to change it or regenerate `configure using a newer version of `autoconf.
The simplest way to compile this package is:
1. `cd to the directory containing the packages source code and type `./configure to configure the package for your system.
If youre using `csh on an old version of System V, you might need to type `sh ./configure instead to prevent `csh from trying to execute `configure itself.
Running `configure takes awhile. While running, it prints some messages telling which features it is checking for.
2. Type `make to compile the package.
3. Optionally, type `make check to run any self-tests that come with the package.
4. Type `make install to install the programs and any data files and documentation.
5. You can remove the program binaries and object files from the source code directory by typing `make clean. To also remove the files that `configure created (so you can compile the package for a different kind of computer), type `make distclean.
There is also a `make maintainer-clean target, but that is intended mainly for the packages developers. If you use it, you may have to get all sorts of other programs in order to regenerate files that came with the distribution.
Download (0.064MB)
Added: 2005-10-10 License: GPL (GNU General Public License) Price:
1474 downloads
Secleted [ 0 ] software to compare
Copyright Notice:
Software piracy is theft, Using crack, password, serial numbers, registration codes, key generators is illegal and prevent future software development. The above stale search only lists software in full, demo and trial versions for free download. Download links are directly from our mirror sites or publisher sites, torrent files or links from rapidshare.com, yousendit.com or megaupload.com are not allowed
