powerpc instruction set
Sponsored Links
Sponsored Links
Secleted [ 0 ] software to compare
Results 1 - 15 of about 5238
Packet Construction Set 0.5 Beta
Packet Construction Set is a set of Python modules and objects that make building network protocol code easier. more>>
Packet Construction Set is a set of Python modules and objects that make building network protocol code easier for the protocol developer.
The core of the system is the pcs module itself which provides the necessary functionality to create classes that implement packets.
Installation Instructions for Packet Construction Set (PCS)
PCS follows the normal Python conventions for building and installing and there is very little, if any, magic. To install the library and the associated packet classes into your system do:
> python setup.py install < return >
To test your installation do:
> cd tests/ < return >
> python *.py
Some tests fail if you do not have enough privileges to work with the Berkeley Packet Filter. If you wish to run those tests run them using sudo.
To build the documentation you will need pdflatex and a BSD version of make installed. Go into the docs directory and build the documentation:
> cd docs/ < return >
> bsdmake all
you will see PDF versions of the docs.
Enhancements:
- Move my version of Doug Songs Python pcap library into the package.
- Update the Makefile to make sure that we install correctly no matter what target is selected.
<<lessThe core of the system is the pcs module itself which provides the necessary functionality to create classes that implement packets.
Installation Instructions for Packet Construction Set (PCS)
PCS follows the normal Python conventions for building and installing and there is very little, if any, magic. To install the library and the associated packet classes into your system do:
> python setup.py install < return >
To test your installation do:
> cd tests/ < return >
> python *.py
Some tests fail if you do not have enough privileges to work with the Berkeley Packet Filter. If you wish to run those tests run them using sudo.
To build the documentation you will need pdflatex and a BSD version of make installed. Go into the docs directory and build the documentation:
> cd docs/ < return >
> bsdmake all
you will see PDF versions of the docs.
Enhancements:
- Move my version of Doug Songs Python pcap library into the package.
- Update the Makefile to make sure that we install correctly no matter what target is selected.
Download (0.36MB)
Added: 2007-03-22 License: BSD License Price:
947 downloads
Folder Color Icon Set 1.0
Folder Color icon set is a must-have for any computer user who has lots of folders and would like to organize them for faster search and quick retrieval. These 36 color coded folder icons is the way to tackle the too-many-same-looking-folders problem. To change color of a folder: Right click the folder > select Properties > click Customize tab > click Change Icon... > select an icon from this icon set > click OK > click Apply > OK... more>> <<less
Download (446.2Kb)
Added: 2007-07-15 License: Free Price: Free
12 downloads
IA-32 Instructions Database 0.0.1
IA-32 Instructions Database is a description of all IA-32 instructions in the form of SQL source. more>>
IA-32 Instructions Database is a description of all IA-32 instructions in the form of SQL source, specifying operands, arguments, prefixes, encoding details, and description.
This database information initially came from XI (http://verb.org.ua/xi/) project, which was generated using information from (unfortunately outdated) IA-32 Intel(r) Architecture Software Developers Manual 2002.
Current release is alpha, so your feedback and bug reports are highly appreciable!
How to Build
Basically, there is no much need to build ia-32-instrdb, as it is just an sql file. However, you can type `make and if you have sqlite properly installed, you will get sqlites ia32instrs.db file shortly.
<<lessThis database information initially came from XI (http://verb.org.ua/xi/) project, which was generated using information from (unfortunately outdated) IA-32 Intel(r) Architecture Software Developers Manual 2002.
Current release is alpha, so your feedback and bug reports are highly appreciable!
How to Build
Basically, there is no much need to build ia-32-instrdb, as it is just an sql file. However, you can type `make and if you have sqlite properly installed, you will get sqlites ia32instrs.db file shortly.
Download (0.016MB)
Added: 2006-07-20 License: Freely Distributable Price:
1192 downloads
BitWise Routing Server 1.7
BitWise Routing Server allows multiple PCs behind a router to make direct connections. more>>
BitWise Routing Server allows multiple PCs behind a router to make direct connections.
The BitWise Routing Server allows you to accept BitWise connections to multiple computers behind a router. Typically, using a router, you would set up port forwarding on BitWises client port (4137), and specify a single destination IP. This is fine until multiple users behind a router all need to accept incoming connections.
As shown by the picture at right, the Routing Server allows individual users to register themselves with the Routing Server, and then the Routing Server accepts all incoming connections and directs those connections to the appropriate user.
The Routing Server requires that your physical router support port forwarding with a way to specify different external and internal ports (this is sometimes labeled "UPnP" by many common home routers).
The Routing Server has several options allowing you to customize the Routing Server for your environment. Many of the options are self-explanatory. The two that are not are Listen on Port and IP filtering. IP filtering is explained in the next section.
The BitWise Routing Server listens on a different port than the BitWise IM client. This allows the Routing Server and the IM client to be run on the same computer without causing conflicts. You will want to set up your router (more detail in a later step) to shift the port of the incoming connections from 4137 to another port. It doesnt particularly matter which port you want to use, as long as it is not a port used by another program. The default port is 4200.
Depending on the complexity of the network, it may be desirable to filter the IP addresses that are allowed to register with the Routing Server. This can be done in the preferences. One very likely scenario would be limiting registrations to the 192.168.1.x IP addresses (192.168 is reserved for local networks). When specifying an IP as the comparison address, you can use any valid IP numbers for wildcards.
In the case shown here, the Routing Server will limit connections to computers having IP addresses of 192.168.1.x. Any number, 0 through 255, could be placed for x in the Routing Server preferences.
If you are not familiar with IP address classes and IP filtering, it will usually be safe to leave Any selected.
Setting up the physical router
The picture at right was taken from a Linksys router, other routers will have a similar capability, although it may be layed out differently. On some routers, the advanced port forwarding options are mistakingly labeled UPnP.
The router setup shows that we are accepting connections on port 4137 and then sending them inside the network on port 4200 (the default port). Enter the IP address of the machine on the network running the Routing Server, and make sure that the rule is enabled. You will want to enter a rule for both TCP and UDP (UDP is used only for voice).
Please consult your router manual for more detailed instructions about how to set up port forwarding on your specific model.
Configuring BitWise to use the Routing Server
In order for you to enjoy the connectivity benefits of the Routing Server, you will need to register with the Routing Server when you log in to BitWise. Prior to logging in to BitWise, click the Setup button next to the Connect button to open the BitWise Setup. There is an area to enter an address for the Routing Server, and to specify what port to use. The port must be the same as the port used above (4200 is the default).
Upon connecting to BitWise, you will be registered with the Routing Server. If you could not be registered, an error message will be displayed. Double-check that the correct address was entered in the Setup.
Registration with the Routing Server
Upon successfully registering with the Routing Server, the Routing Server will display the user name and the IP address of the registration. If you want to unregister a user, click on the username, and then click Unregister. Incoming connections will no longer be forwarded to the specified computer.
It is worth pointing out two things here. First, if you later log in from a different computer, and that computer is also set to use the Routing Server, you will be re-registered with your new IP address. Second, if you are unregistered, or move to another computer but are not set up to use the Routing Server, you will not be able to benefit from the services of the Routing Server.
By default, the Routing Server saves the registered user list when it is closed down.
Using the Routing Server
Assuming that everything is set up correctly, everyone that registers with the Routing Server when they log in to BitWise will be able to enjoy significantly increased connectivity with other BitWise users. As incoming connections are established, you will see the connections listed in the right pane of the Routing Server window. The IP address and the time of the connection is also displayed, and the connection is later marked when it is disconnected.
The disconnected/closed connections may be cleaned from the list at any time using the Clean List button. Only active connections will be left displayed.
<<lessThe BitWise Routing Server allows you to accept BitWise connections to multiple computers behind a router. Typically, using a router, you would set up port forwarding on BitWises client port (4137), and specify a single destination IP. This is fine until multiple users behind a router all need to accept incoming connections.
As shown by the picture at right, the Routing Server allows individual users to register themselves with the Routing Server, and then the Routing Server accepts all incoming connections and directs those connections to the appropriate user.
The Routing Server requires that your physical router support port forwarding with a way to specify different external and internal ports (this is sometimes labeled "UPnP" by many common home routers).
The Routing Server has several options allowing you to customize the Routing Server for your environment. Many of the options are self-explanatory. The two that are not are Listen on Port and IP filtering. IP filtering is explained in the next section.
The BitWise Routing Server listens on a different port than the BitWise IM client. This allows the Routing Server and the IM client to be run on the same computer without causing conflicts. You will want to set up your router (more detail in a later step) to shift the port of the incoming connections from 4137 to another port. It doesnt particularly matter which port you want to use, as long as it is not a port used by another program. The default port is 4200.
Depending on the complexity of the network, it may be desirable to filter the IP addresses that are allowed to register with the Routing Server. This can be done in the preferences. One very likely scenario would be limiting registrations to the 192.168.1.x IP addresses (192.168 is reserved for local networks). When specifying an IP as the comparison address, you can use any valid IP numbers for wildcards.
In the case shown here, the Routing Server will limit connections to computers having IP addresses of 192.168.1.x. Any number, 0 through 255, could be placed for x in the Routing Server preferences.
If you are not familiar with IP address classes and IP filtering, it will usually be safe to leave Any selected.
Setting up the physical router
The picture at right was taken from a Linksys router, other routers will have a similar capability, although it may be layed out differently. On some routers, the advanced port forwarding options are mistakingly labeled UPnP.
The router setup shows that we are accepting connections on port 4137 and then sending them inside the network on port 4200 (the default port). Enter the IP address of the machine on the network running the Routing Server, and make sure that the rule is enabled. You will want to enter a rule for both TCP and UDP (UDP is used only for voice).
Please consult your router manual for more detailed instructions about how to set up port forwarding on your specific model.
Configuring BitWise to use the Routing Server
In order for you to enjoy the connectivity benefits of the Routing Server, you will need to register with the Routing Server when you log in to BitWise. Prior to logging in to BitWise, click the Setup button next to the Connect button to open the BitWise Setup. There is an area to enter an address for the Routing Server, and to specify what port to use. The port must be the same as the port used above (4200 is the default).
Upon connecting to BitWise, you will be registered with the Routing Server. If you could not be registered, an error message will be displayed. Double-check that the correct address was entered in the Setup.
Registration with the Routing Server
Upon successfully registering with the Routing Server, the Routing Server will display the user name and the IP address of the registration. If you want to unregister a user, click on the username, and then click Unregister. Incoming connections will no longer be forwarded to the specified computer.
It is worth pointing out two things here. First, if you later log in from a different computer, and that computer is also set to use the Routing Server, you will be re-registered with your new IP address. Second, if you are unregistered, or move to another computer but are not set up to use the Routing Server, you will not be able to benefit from the services of the Routing Server.
By default, the Routing Server saves the registered user list when it is closed down.
Using the Routing Server
Assuming that everything is set up correctly, everyone that registers with the Routing Server when they log in to BitWise will be able to enjoy significantly increased connectivity with other BitWise users. As incoming connections are established, you will see the connections listed in the right pane of the Routing Server window. The IP address and the time of the connection is also displayed, and the connection is later marked when it is disconnected.
The disconnected/closed connections may be cleaned from the list at any time using the Clean List button. Only active connections will be left displayed.
Download (1.0MB)
Added: 2006-03-02 License: Freeware Price:
1331 downloads
Set::Partition 0.03
Set::Partition is a Perl module that can enumerate all arrangements of a set in fixed subsets. more>>
Set::Partition is a Perl module that can enumerate all arrangements of a set in fixed subsets.
SYNOPSIS
use Set::Partition;
my $s = Set::Partition->new(
list => [qw(a b c d e)],
partition => [2, 3],
);
while (my $p = $s->next) {
print join( , map { "(@$_)" } @$p ), $/;
}
# produces
(a b) (c d e)
(a c) (b d e)
(a d) (b c e)
(a e) (b c d)
(b c) (a d e)
(b d) (a c e)
(b e) (a c d)
(c d) (a b e)
(c e) (a b d)
(d e) (a b c)
# or with a hash
my $s = Set::Partition->new(
list => { b => bat, c => cat, d => dog },
partition => [2, 1],
);
while (my $p = $s->next) {
...
}
Set::Partition takes a list or hash of elements and a list numbers that represent the sizes of the partitions into which the list of elements should be arranged.
The resulting object can then be used as an iterator which returns a reference to an array of lists, that represents the original list arranged according to the given partitioning. All possible arrangements are returned, and the object returns undef when the entire combination space has been exhausted.
<<lessSYNOPSIS
use Set::Partition;
my $s = Set::Partition->new(
list => [qw(a b c d e)],
partition => [2, 3],
);
while (my $p = $s->next) {
print join( , map { "(@$_)" } @$p ), $/;
}
# produces
(a b) (c d e)
(a c) (b d e)
(a d) (b c e)
(a e) (b c d)
(b c) (a d e)
(b d) (a c e)
(b e) (a c d)
(c d) (a b e)
(c e) (a b d)
(d e) (a b c)
# or with a hash
my $s = Set::Partition->new(
list => { b => bat, c => cat, d => dog },
partition => [2, 1],
);
while (my $p = $s->next) {
...
}
Set::Partition takes a list or hash of elements and a list numbers that represent the sizes of the partitions into which the list of elements should be arranged.
The resulting object can then be used as an iterator which returns a reference to an array of lists, that represents the original list arranged according to the given partitioning. All possible arrangements are returned, and the object returns undef when the entire combination space has been exhausted.
Download (0.007MB)
Added: 2007-07-04 License: Perl Artistic License Price:
842 downloads
Simple Machine Language interpreter
Simple Machine Language interpreter is a simple machine language interpreter. more>>
SML is a "toy" machine language intended to teach basic processor concepts. This website contains an explanation and definition of SML, as well as an interpreter and example SML programs. GPLd source code for the interpreter is available, as well as binaries for Windows and Linux.
A machine language defines a set of instructions that a CPU can execute to perform operations. In other words, a machine language defines what you can do with your computer. Modern processors have very complex instruction sets; however, the simple language described here can give you an understanding of what is happening "under the hood" with your computer.
Machine language is the actual data that is directly run by the processor. Writing a program in machine language can therefore be advantageous if you need to save space or highly optimize your code. However, machine language is also not portable and can be difficult to understand and maintain.
Therefore, almost all code is now written in a higher level language, such as C, C++, Java, or scripting languages such as shell or perl. These languages all have their advantages and disadvantages as well, such as varying levels of portability, maintainability, scalability, and execution speed.
One level higher than machine language is assembly language. Assembly language is basically readable machine language. Instead of writing out the code bit-by-bit, you write out the code as a sequence of human readable instructions, which are then compiled almost directly into machine language.
Assembly language is almost always used instead of machine language when such a direct level of control is needed. For example, some games implement part of their code in assembly in order to maximize execution speed. Assembly can be "inlined" into some higher level languages, like C. This means that the assembly is defined as a callable procedure from within the C code.
<<lessA machine language defines a set of instructions that a CPU can execute to perform operations. In other words, a machine language defines what you can do with your computer. Modern processors have very complex instruction sets; however, the simple language described here can give you an understanding of what is happening "under the hood" with your computer.
Machine language is the actual data that is directly run by the processor. Writing a program in machine language can therefore be advantageous if you need to save space or highly optimize your code. However, machine language is also not portable and can be difficult to understand and maintain.
Therefore, almost all code is now written in a higher level language, such as C, C++, Java, or scripting languages such as shell or perl. These languages all have their advantages and disadvantages as well, such as varying levels of portability, maintainability, scalability, and execution speed.
One level higher than machine language is assembly language. Assembly language is basically readable machine language. Instead of writing out the code bit-by-bit, you write out the code as a sequence of human readable instructions, which are then compiled almost directly into machine language.
Assembly language is almost always used instead of machine language when such a direct level of control is needed. For example, some games implement part of their code in assembly in order to maximize execution speed. Assembly can be "inlined" into some higher level languages, like C. This means that the assembly is defined as a callable procedure from within the C code.
Download (0.22MB)
Added: 2005-04-14 License: GPL (GNU General Public License) Price:
1668 downloads
Interactive Decompiler 0.2
Interactive Decompiler decompiles by the successive application of low-level refactorings, ultimately leading to high-level code more>>
Interactive Decompiler project is an interactive decompiler, where the user starts with an almost literal translation of Assembly code in C language, which he progressively decompiles by the successive application of low-level refactorings, ultimately leading to high-level C code.
Main features:
- Import Intel IA32 Assembly code, in the AT&T syntax -- the syntax normally generated by the gcc compiler for the Intel IA32 architecture.
- Visualize and export quasi-C language code.
- Provides a context-sensitive refactoring browser to a set of low-level refactorings.
- Visualize and manipulate the Control Flow Graph (CFG) and the Abstract Syntax Tree (AST).
- For developers:
- It has an extensible data type for program representation.
- It has an easily extensible architecture (new program metadata, new processors, new refactorings, or new visualizations can easily be added).
- It has an embedded language for describing refactorings and other transformation.
- It is possible to modify the refactorings while running the program.
Version restrictions:
- The IA32 instruction set is not yet fully supported, namely the floating-point and SIMD instructions are not yet translated.
- Not all refactoring are implemented, and some are only have a partial implementation.
- The data flow analysis performed in the refactorings focus only on register variables.
- The implementation of several of many necessary the refactorings is still missing due to lack of time.
<<lessMain features:
- Import Intel IA32 Assembly code, in the AT&T syntax -- the syntax normally generated by the gcc compiler for the Intel IA32 architecture.
- Visualize and export quasi-C language code.
- Provides a context-sensitive refactoring browser to a set of low-level refactorings.
- Visualize and manipulate the Control Flow Graph (CFG) and the Abstract Syntax Tree (AST).
- For developers:
- It has an extensible data type for program representation.
- It has an easily extensible architecture (new program metadata, new processors, new refactorings, or new visualizations can easily be added).
- It has an embedded language for describing refactorings and other transformation.
- It is possible to modify the refactorings while running the program.
Version restrictions:
- The IA32 instruction set is not yet fully supported, namely the floating-point and SIMD instructions are not yet translated.
- Not all refactoring are implemented, and some are only have a partial implementation.
- The data flow analysis performed in the refactorings focus only on register variables.
- The implementation of several of many necessary the refactorings is still missing due to lack of time.
Download (0.022MB)
Added: 2007-08-09 License: LGPL (GNU Lesser General Public License) Price:
857 downloads
Glass Icons Theme 0.2
Glass Icons Theme provides a full transparent set of icons. more>>
Glass Icons Theme provides a full transparent set of icons.
Full Transparent SVG Icons, are in beta-test.
This is the first public release.
<<lessFull Transparent SVG Icons, are in beta-test.
This is the first public release.
Download (MB)
Added: 2007-03-02 License: GPL (GNU General Public License) Price:
598 downloads
nwbintools 0.1.1
nwbintools is a machine code toolchain containing an assembler and various related development tools. more>>
nwbintools is a machine code toolchain containing an assembler and various related development tools. The project will thus be similar to GNU binutils, but no attempts are made to duplicate its functionality, interfaces, or organization.
nwbintools has been under development (on and off) since January 2007. It was written from scratch in C, and version 0.1.1 has just been released under the (revised) BSD license. Full source code is available from the download page.
At present, the tool collection only consists of the assembler - nwasm - and a simple program to dump some basic ELF object file information. However, in the future nwbintools is probably going to be extended with a new linker, disassembler, and other binary file analysis tools.
nwasm is currently x86-only, 32bit-only, and ELF-only. There are lots of other bugs and limitations as well. See the bugs page for details. The current goal is to get nwasm to work well with the code generated by the nwcc C compiler, which already works to a considerable extent because that code is very simple and doesnt use many obscure x86 features.
Hopefully future releases will support the complete x86 instruction set as well as multiple other architectures, and allow for seamless cross-assembling.
Enhancements:
- This release extends the assembler with support for most instructions from x87, MMX, SSE, SSE2, and SSE3.
- However, support for various system-level and post-486 instructions is still missing.
- Various critical bugs related to labels, relocations, and wrong section sizes were fixed.
- Performance has been doubled.
<<lessnwbintools has been under development (on and off) since January 2007. It was written from scratch in C, and version 0.1.1 has just been released under the (revised) BSD license. Full source code is available from the download page.
At present, the tool collection only consists of the assembler - nwasm - and a simple program to dump some basic ELF object file information. However, in the future nwbintools is probably going to be extended with a new linker, disassembler, and other binary file analysis tools.
nwasm is currently x86-only, 32bit-only, and ELF-only. There are lots of other bugs and limitations as well. See the bugs page for details. The current goal is to get nwasm to work well with the code generated by the nwcc C compiler, which already works to a considerable extent because that code is very simple and doesnt use many obscure x86 features.
Hopefully future releases will support the complete x86 instruction set as well as multiple other architectures, and allow for seamless cross-assembling.
Enhancements:
- This release extends the assembler with support for most instructions from x87, MMX, SSE, SSE2, and SSE3.
- However, support for various system-level and post-486 instructions is still missing.
- Various critical bugs related to labels, relocations, and wrong section sizes were fixed.
- Performance has been doubled.
Download (0.092MB)
Added: 2007-05-03 License: BSD License Price:
904 downloads
Nomad II Driver/Utilities 0.8
Nomad II supports the Creative Nomad II, IIc and II MG under Linux running USB for file transfers and other operations. more>>
Nomad II supports the Creative Nomad II, IIc and II MG under Linux running USB for file transfers and other operations.
By default, the ownership of the newly created device file for the Nomad II is owned by root, without group/other read+write permissions.
make nomadii setuid root; on startup, nomadii
detects it is running in this mode and changes the owner of the device file to the original user, and then immediately drops back to the user ID of the original user (in order to minimize the possibility of security issues). This can be made with a number of techniques:
use the devuid, devgid or devmode mount options for usbdevfs, either in your /etc/fstab file or located where the mount call for usbdevfs is made (/etc/rc.d/rc.sysinit on RedHat 7.x); for example use devmode=0666 to open full access to all USB devices (with the attendant insecureness this creates). In a multi-user machine, setting up a group for USB would be the more secure option using this method.
locate and install the usb_perms daemon
use the hotplug package; this subsystem has good support for USB devices with user-level drivers such as this one with its usb.usermap launch method. The module launched by hotplug can be used to set ownerships or permissions on the device file as soon as the Nomad II is connected, and then even launch an xterm running a nomadii session. This is the most delicate of these methods to set up - sample instructions are given in the HOTPLUG file that comes with the source distribution.
Enhancements:
- Rename of utility to nomadii
- Availablility of RPM
- Full support of the Nomad II, IIc and II MG with latest firmware
- Autocorrection of bad data when getting files from the Nomad
- Much improved error detection and reporting
- Split of code into text front end and library
- Better name handling and progress reporting
- Updated support for nomadii-driver
- Better USB device permission options
- Added send/get methods
- Added support for multiple send, get and delete
- Hotplug documentation and scripts
- Many major and minor bug fixes
<<lessBy default, the ownership of the newly created device file for the Nomad II is owned by root, without group/other read+write permissions.
make nomadii setuid root; on startup, nomadii
detects it is running in this mode and changes the owner of the device file to the original user, and then immediately drops back to the user ID of the original user (in order to minimize the possibility of security issues). This can be made with a number of techniques:
use the devuid, devgid or devmode mount options for usbdevfs, either in your /etc/fstab file or located where the mount call for usbdevfs is made (/etc/rc.d/rc.sysinit on RedHat 7.x); for example use devmode=0666 to open full access to all USB devices (with the attendant insecureness this creates). In a multi-user machine, setting up a group for USB would be the more secure option using this method.
locate and install the usb_perms daemon
use the hotplug package; this subsystem has good support for USB devices with user-level drivers such as this one with its usb.usermap launch method. The module launched by hotplug can be used to set ownerships or permissions on the device file as soon as the Nomad II is connected, and then even launch an xterm running a nomadii session. This is the most delicate of these methods to set up - sample instructions are given in the HOTPLUG file that comes with the source distribution.
Enhancements:
- Rename of utility to nomadii
- Availablility of RPM
- Full support of the Nomad II, IIc and II MG with latest firmware
- Autocorrection of bad data when getting files from the Nomad
- Much improved error detection and reporting
- Split of code into text front end and library
- Better name handling and progress reporting
- Updated support for nomadii-driver
- Better USB device permission options
- Added send/get methods
- Added support for multiple send, get and delete
- Hotplug documentation and scripts
- Many major and minor bug fixes
Download (0.044MB)
Added: 2006-07-21 License: GPL (GNU General Public License) Price:
1194 downloads
Software::Packager::Svr4 1.2
Software::Packager::Svr4 is the Software::Packager extension for System VR4 packages. more>>
Software::Packager::Svr4 is the Software::Packager extension for System VR4 packages.
SYNOPSIS
use Software::Packager;
my $packager = new Software::Packager(svr4);
This module is used to create software packages in a format suitable for installation with pkgadd.
FUNCTIONS
new()
This method creates and returns a new Software::Packager::SVR4 object.
add_item()
$packager->add_item(%object_data);
Adds a new object (file, link, etc) to the package.
package()
$packager->package();
Create the package.
info
This method returns a hash that is filled with the necessary information for a pkginfo file that conforms to the SYSV format.
package_name()
Define the package name.
program_name()
This is used to specify the full package name.
The program name must be less that 256 charaters.
For more details see the pkginfo(4) man page.
architecture()
The architecture must be a comma seperated list of alphanumeric tokens that indicate the architecture associated with the package.
The maximum length of a token is 16 charaters.
A token should be in the format "instruction set"."platform group" where:
instruction set is in the format of `uname -p`
platform group is in the format of `uname -m`
If the architecture is not set then the current instruction set is used.
For more details see the pkginfo(4) man page.
version()
This method is used to check the format of the version and return it in the format required for SVR4.
The version must be 256 charaters or less.
The first charater cannot be a left parenthesis.
The recommended format is an arbitrary string of numbers in Dewey-decimal format. For more datails see the pkginfo(4) man page.
install_dir()
$packager->install_dir(/usr/local);
my $base_dir = $packager->install_dir;
This method sets the base directory for the software to be installed. The installation directory must start with a "/".
compatible_version()
$packager->compatible_version(/some/path/file);
or
$packager->compatible_version($compver_stored_in_string);
my $compatible_version = $packager->compatible_version();
This method sets the compatible versions file for the software to be installed.
space()
$packager->space(/some/path/file);
or
$packager->space($space_data_stored_in_string);
my $space = $packager->space();
This method sets the space file for the software to be installed.
request_script()
$packager->request_script(/some/path/file);
or
$packager->request_script($request_script_stored_in_string);
my $request_script = $packager->request_script();
This method sets the space file for the software to be installed.
<<lessSYNOPSIS
use Software::Packager;
my $packager = new Software::Packager(svr4);
This module is used to create software packages in a format suitable for installation with pkgadd.
FUNCTIONS
new()
This method creates and returns a new Software::Packager::SVR4 object.
add_item()
$packager->add_item(%object_data);
Adds a new object (file, link, etc) to the package.
package()
$packager->package();
Create the package.
info
This method returns a hash that is filled with the necessary information for a pkginfo file that conforms to the SYSV format.
package_name()
Define the package name.
program_name()
This is used to specify the full package name.
The program name must be less that 256 charaters.
For more details see the pkginfo(4) man page.
architecture()
The architecture must be a comma seperated list of alphanumeric tokens that indicate the architecture associated with the package.
The maximum length of a token is 16 charaters.
A token should be in the format "instruction set"."platform group" where:
instruction set is in the format of `uname -p`
platform group is in the format of `uname -m`
If the architecture is not set then the current instruction set is used.
For more details see the pkginfo(4) man page.
version()
This method is used to check the format of the version and return it in the format required for SVR4.
The version must be 256 charaters or less.
The first charater cannot be a left parenthesis.
The recommended format is an arbitrary string of numbers in Dewey-decimal format. For more datails see the pkginfo(4) man page.
install_dir()
$packager->install_dir(/usr/local);
my $base_dir = $packager->install_dir;
This method sets the base directory for the software to be installed. The installation directory must start with a "/".
compatible_version()
$packager->compatible_version(/some/path/file);
or
$packager->compatible_version($compver_stored_in_string);
my $compatible_version = $packager->compatible_version();
This method sets the compatible versions file for the software to be installed.
space()
$packager->space(/some/path/file);
or
$packager->space($space_data_stored_in_string);
my $space = $packager->space();
This method sets the space file for the software to be installed.
request_script()
$packager->request_script(/some/path/file);
or
$packager->request_script($request_script_stored_in_string);
my $request_script = $packager->request_script();
This method sets the space file for the software to be installed.
Download (0.014MB)
Added: 2007-01-09 License: Perl Artistic License Price:
1021 downloads
ArchAddOn 1.0
ArchAddOn provides a straightforward toolbox of field types, widgets, and validators for Archetypes. more>>
ArchAddOn provides a straightforward toolbox of field types, widgets, and validators for Archetypes.
Instruction (only shows description on edit form, for adding sectional
help or other HTML markup to an edit form)
DynamicField. This is a textual field that can contain TALES
expressions which are evaluated. So you can add a "body" field to
a schema that is of this type, and have it be a mix of HTML content
and TALES expressions (just like in a ZPT).
SimpleDataGridField. A lines field with embedded vertical bars for fields. If the
columns property is set, the isValidGrid validator will ensure that
the entered text has exactly that number of columns for each row.
If strip_whitespace is True, the individual cells in the grid will
be stripped of leading and trailing whitespace (that is, whitespace
added around the delimiter).
If column_names is set to a tuple or list of strings, it gives the names
of columns in the grid. The getDataGridRow script and the getRow() method
will return a dict using these column names as keys rather than using the
column numbers (starting from zero).
Fields are just strings, with no internal validation, etc.
Enhancements:
- A long time resident of the collective, ArchAddOn makes its debut on plone.org.
<<lessInstruction (only shows description on edit form, for adding sectional
help or other HTML markup to an edit form)
DynamicField. This is a textual field that can contain TALES
expressions which are evaluated. So you can add a "body" field to
a schema that is of this type, and have it be a mix of HTML content
and TALES expressions (just like in a ZPT).
SimpleDataGridField. A lines field with embedded vertical bars for fields. If the
columns property is set, the isValidGrid validator will ensure that
the entered text has exactly that number of columns for each row.
If strip_whitespace is True, the individual cells in the grid will
be stripped of leading and trailing whitespace (that is, whitespace
added around the delimiter).
If column_names is set to a tuple or list of strings, it gives the names
of columns in the grid. The getDataGridRow script and the getRow() method
will return a dict using these column names as keys rather than using the
column numbers (starting from zero).
Fields are just strings, with no internal validation, etc.
Enhancements:
- A long time resident of the collective, ArchAddOn makes its debut on plone.org.
Download (0.012MB)
Added: 2007-04-14 License: GPL (GNU General Public License) Price:
923 downloads
Timos Rescue CD Set 0.9.12r2
Timos Rescue CD Set is a kit for creating bootable rescue CDs. more>>
Timos rescue CD set provides an easy way to generate bootable CDROMs with a ready-to-use rescue system on them. The system is designed to be fully customizable and easy to build.
The rescue system includes reiserfs, parted, partimage, nmap, w3m, bash, sshd, telnetd, ftpd, and nfsd. It is based on Debians "Sarge" release. LILO, syslinux, isolinux, and GRUB are supported.
The project is evolving more and more into a "Debian on CD" project, which means that its use is not limited to a rescue CD; it is also possible to install a whole Debian system on CD.
Enhancements:
- the cdrecord script was buggy - fixed
<<lessThe rescue system includes reiserfs, parted, partimage, nmap, w3m, bash, sshd, telnetd, ftpd, and nfsd. It is based on Debians "Sarge" release. LILO, syslinux, isolinux, and GRUB are supported.
The project is evolving more and more into a "Debian on CD" project, which means that its use is not limited to a rescue CD; it is also possible to install a whole Debian system on CD.
Enhancements:
- the cdrecord script was buggy - fixed
Download (80MB)
Added: 2005-04-11 License: GPL (GNU General Public License) Price:
1659 downloads
GNU Superoptimizer 2.5
GNU Superoptimizer is a project that uses an approach to finding the shortest instruction sequence for a given function. more>>
GNU Superoptimizer is a project that uses an approach to finding the shortest instruction sequence for a given function.
The superoptimizer is a function sequence generator that uses an exhaustive
generate-and-test approach to finding the shortest instruction sequence for
a given function. You have to tell the superoptimizer which function and
which CPU you want to generate code for, and how many instructions you can
accept.
The superoptimizer cant generate very long sequences, unless you have a
very fast computer or very much spare time. The time complexity of the used
algorithm is approximately
2n
O(m n )
where m is the number of available instructions on the architecture and n is
the shortest sequence for the goal function. The practical sequence length
limit depends on the target architecture and goal function arity; In most
cases it is about 5, but for a rich instruction set as the HPPA it is just
4. The longest sequence ever generated was for the MC68020 and 7
instructions long. It took several weeks to generate it...
The superoptimizer cant guarantee that it finds the best possible
instruction sequences for all possible goal functions. For example, it
doesnt even try to include immediate constants (other that -1, 0, +1, and
the smallest negative and biggest positive numbers) in the sequences.
Other reasons why not optimal sequences might be found is that not all
instructions are included, not even in their register-only form. Also, some
instructions included might not be correctly simulated. If you encounter
any of these problems, please report them to the address below.
WARNING! The generated sequences might be incorrect with a very small
probability. Always make sure a sequence is correct before using it. So
far, I have never encountered any incorrect sequences. If you find one,
please let me know about it!
Having said this, note that the superoptimizer practically always finds
optimal and correct sequences for functions that depend on registers only.
Enhancements:
- Delete unused variable tot_bits.
- Make state1 have char type.
- Use random() on alpha, since srand48 doesnt work there.
- Return small numbers with high probability.
<<lessThe superoptimizer is a function sequence generator that uses an exhaustive
generate-and-test approach to finding the shortest instruction sequence for
a given function. You have to tell the superoptimizer which function and
which CPU you want to generate code for, and how many instructions you can
accept.
The superoptimizer cant generate very long sequences, unless you have a
very fast computer or very much spare time. The time complexity of the used
algorithm is approximately
2n
O(m n )
where m is the number of available instructions on the architecture and n is
the shortest sequence for the goal function. The practical sequence length
limit depends on the target architecture and goal function arity; In most
cases it is about 5, but for a rich instruction set as the HPPA it is just
4. The longest sequence ever generated was for the MC68020 and 7
instructions long. It took several weeks to generate it...
The superoptimizer cant guarantee that it finds the best possible
instruction sequences for all possible goal functions. For example, it
doesnt even try to include immediate constants (other that -1, 0, +1, and
the smallest negative and biggest positive numbers) in the sequences.
Other reasons why not optimal sequences might be found is that not all
instructions are included, not even in their register-only form. Also, some
instructions included might not be correctly simulated. If you encounter
any of these problems, please report them to the address below.
WARNING! The generated sequences might be incorrect with a very small
probability. Always make sure a sequence is correct before using it. So
far, I have never encountered any incorrect sequences. If you find one,
please let me know about it!
Having said this, note that the superoptimizer practically always finds
optimal and correct sequences for functions that depend on registers only.
Enhancements:
- Delete unused variable tot_bits.
- Make state1 have char type.
- Use random() on alpha, since srand48 doesnt work there.
- Return small numbers with high probability.
Download (0.076MB)
Added: 2007-02-28 License: GPL (GNU General Public License) Price:
969 downloads
Software::Packager::Solaris 0.1
Software::Packager::Solaris is the Software::Packager extension for Solaris 2.5.1 and above. more>>
Software::Packager::Solaris is the Software::Packager extension for Solaris 2.5.1 and above.
SYNOPSIS
use Software::Packager;
my $packager = new Software::Packager(solaris);
This module is used to create software packages in a format suitable for installation with pkgadd. The process of creating packages is baised upon the document Application Packaging Developers Guide. Which can be found at http://docs.sun.com/ab2/@LegacyPageView?toc=SUNWab_42_2:/safedir/space3/coll1/SUNWasup/toc/PACKINSTALL:Contents;bt=Application+Packaging+Developer%27s+Guide;ps=ps/SUNWab_42_2/PACKINSTALL/Contents
FUNCTIONS
new()
This method creates and returns a new Software::Packager::Solaris object.
add_item()
$packager->add_item(%object_data);
This method overrides the add_item function in the Software::Packager module.
This method adds a new object to the package.
package()
$packager->packager(); This method overrides the base API in Software::Packager, it controls the process if package creation.
package_name()
This method is used to specify the abbreviated package name.
Sun say: (Application Packaging Developers Guide. Page 32) A valid package abbreviation must the criteria defined below:
It must start with a letter. Additional charaters may be alphanumeric and can be the two special charaters + and -.
It must be nine or fewer charaters.
Reserved names are install, new, and all.
For more details see the pkginfo(4) man page.
program_name()
This is used to specify the full package name.
The program name must be less that 256 charaters.
For more details see the pkginfo(4) man page.
architecture()
The architecture must be a comma seperated list of alphanumeric tokens that indicate the architecture associated with the package. The maximum length of a token is 16 charaters. A token should be in the format "instruction set"."platform group" where: instruction set is the output of `uname -p` platform group is the output of `uname -m`
If the architecture is not set then the current instruction set is used.
For more details see the pkginfo(4) man page.
version()
This method is used to check the format of the version and return it in the format required for Solaris.
The version must be 256 charaters or less.
The first charater cannot be a left parenthesis.
The recommended format isi an arbitrary string of numbers in Dewey-decimal format. For more datails see the pkginfo(4) man page.
install_dir()
$packager->install_dir(/usr/local);
my $base_dir = $packager->install_dir();
This method sets the base directory for the software to be installed. The installation directory must start with a "/".
compatible_version()
$packager->compatible_version(/some/path/file);
or
$packager->compatible_version($compver_stored_in_string);
my $compatible_version = $packager->compatible_version();
This method sets the compatible versions file for the software to be installed.
space()
$packager->space(/some/path/file);
or
$packager->space($space_data_stored_in_string);
my $space = $packager->space();
This method sets the space file for the software to be installed.
request_script()
$packager->request_script(/some/path/file);
or
$packager->request_script($request_script_stored_in_string);
my $request_script = $packager->request_script();
This method sets the space file for the software to be installed.
<<lessSYNOPSIS
use Software::Packager;
my $packager = new Software::Packager(solaris);
This module is used to create software packages in a format suitable for installation with pkgadd. The process of creating packages is baised upon the document Application Packaging Developers Guide. Which can be found at http://docs.sun.com/ab2/@LegacyPageView?toc=SUNWab_42_2:/safedir/space3/coll1/SUNWasup/toc/PACKINSTALL:Contents;bt=Application+Packaging+Developer%27s+Guide;ps=ps/SUNWab_42_2/PACKINSTALL/Contents
FUNCTIONS
new()
This method creates and returns a new Software::Packager::Solaris object.
add_item()
$packager->add_item(%object_data);
This method overrides the add_item function in the Software::Packager module.
This method adds a new object to the package.
package()
$packager->packager(); This method overrides the base API in Software::Packager, it controls the process if package creation.
package_name()
This method is used to specify the abbreviated package name.
Sun say: (Application Packaging Developers Guide. Page 32) A valid package abbreviation must the criteria defined below:
It must start with a letter. Additional charaters may be alphanumeric and can be the two special charaters + and -.
It must be nine or fewer charaters.
Reserved names are install, new, and all.
For more details see the pkginfo(4) man page.
program_name()
This is used to specify the full package name.
The program name must be less that 256 charaters.
For more details see the pkginfo(4) man page.
architecture()
The architecture must be a comma seperated list of alphanumeric tokens that indicate the architecture associated with the package. The maximum length of a token is 16 charaters. A token should be in the format "instruction set"."platform group" where: instruction set is the output of `uname -p` platform group is the output of `uname -m`
If the architecture is not set then the current instruction set is used.
For more details see the pkginfo(4) man page.
version()
This method is used to check the format of the version and return it in the format required for Solaris.
The version must be 256 charaters or less.
The first charater cannot be a left parenthesis.
The recommended format isi an arbitrary string of numbers in Dewey-decimal format. For more datails see the pkginfo(4) man page.
install_dir()
$packager->install_dir(/usr/local);
my $base_dir = $packager->install_dir();
This method sets the base directory for the software to be installed. The installation directory must start with a "/".
compatible_version()
$packager->compatible_version(/some/path/file);
or
$packager->compatible_version($compver_stored_in_string);
my $compatible_version = $packager->compatible_version();
This method sets the compatible versions file for the software to be installed.
space()
$packager->space(/some/path/file);
or
$packager->space($space_data_stored_in_string);
my $space = $packager->space();
This method sets the space file for the software to be installed.
request_script()
$packager->request_script(/some/path/file);
or
$packager->request_script($request_script_stored_in_string);
my $request_script = $packager->request_script();
This method sets the space file for the software to be installed.
Download (0.014MB)
Added: 2007-01-09 License: Perl Artistic License Price:
1018 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 powerpc instruction set 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
