transient
Sponsored Links
Sponsored Links
Secleted [ 0 ] software to compare
Results 1 - 15 of about 27
manix 0.5
manix is a window manager which aims to provide a full MacOS 8/9 interface, including an implementation of the Carbon API. more>>
manix is a window manager which aims to provide a full MacOS 8/9 interface, including an implementation of the Carbon API.
manix is using X11 as the graphical backend.
The window manager is not finished but should be useable. It will be part of the Manix Desktop which aims to implement the entire Mac OS 8/9 interface, without the hanging
and crashing of course.
Main features:
- Workspaces - currently fixed at 4, but will be settable in version 0.4
- Small and fast
Enhancements:
- Support for transient windows (modal dialogs), a new look for dialogs, and plain windows were added.
<<lessmanix is using X11 as the graphical backend.
The window manager is not finished but should be useable. It will be part of the Manix Desktop which aims to implement the entire Mac OS 8/9 interface, without the hanging
and crashing of course.
Main features:
- Workspaces - currently fixed at 4, but will be settable in version 0.4
- Small and fast
Enhancements:
- Support for transient windows (modal dialogs), a new look for dialogs, and plain windows were added.
Download (0.018MB)
Added: 2005-12-01 License: GPL (GNU General Public License) Price:
1423 downloads
Performance Co-Pilot 2.5.0
Performance Co-Pilot is a performance monitoring toolkit and API. more>>
Performance Co-Pilot (PCP) is a framework and services to support system-level performance monitoring and performance management.
The services offered by PCP are especially attractive for those tackling harder system-level performance problems. For example this may involve a transient performance degradation, or correlating end-user quality of service with platform activity, or diagnosing some complex interaction between resource demands on a single system, or management of performance on large systems with lots of "moving parts".
The distributed PCP architecture makes it especially useful for those seeking centralized monitoring of distributed processing (e.g. in a cluster or webserver farm environment), especially where a large number hosts are involved.
Main features:
- A single API for accessing the performance data that hides details of where the data comes from and how it was captured and imported into the PCP framework.
- A client-server architecture allows multiple clients to monitor the same host, and a single client to monitor multiple hosts (e.g. in a Beowulf cluster). This enables centralized monitoring of distributed processing.
- Integrated archive logging and replay so a client application can use the same API to process real-time data from a host or historical data from an archive.
- The framework supports APIs and configuration file formats that enable the scope of performance monitoring to be extended at all levels.
- An "plugin" framework (libraries, APIs, agents and daemon) to collect performance data from multiple sources on a single host, e.g. from the hardware, the kernel, the service layers, the application libraries, and the applications themselves.
- Libraries and sample implementations encourage the development of new "plugins" (or agents) to capture and export the performance data that matters in your application environment, along side the other generic performance data.
- An endian-safe transport layer for moving performance metrics between the collector and the monitoring applications over TCP/IP. This means an IRIX desktop with PCP can monitor one or more Linux systems with the Open Source release of PCP installed.
- A Linux agent that exports a broad range of performance data from most kernels circa 2.0.36 (RedHat 5.2) or later. This includes coverage of activity in the areas of: CPU, disk, memory, swapping, network, NFS, RPC, filesystems and all the per-process statistics.
- Other agents export performance data from:
- Web server activity logs
- arbitrary application-level tracing (via a PCP trace library)
- Cisco routers
- sendmail
- the mail queue
- the PCP infrastructure itself
- Assorted simple monitoring tools that use the PCP APIs to retrieve and display either arbitrary performance metrics, or specific groups of metrics (as in pmstat a cluster-aware vmstat lookalike).
- The PCP inference engine supports automated monitoring through a rule-based language and interpreter that performs user-defined actions when rule predicates are found to be true.
<<lessThe services offered by PCP are especially attractive for those tackling harder system-level performance problems. For example this may involve a transient performance degradation, or correlating end-user quality of service with platform activity, or diagnosing some complex interaction between resource demands on a single system, or management of performance on large systems with lots of "moving parts".
The distributed PCP architecture makes it especially useful for those seeking centralized monitoring of distributed processing (e.g. in a cluster or webserver farm environment), especially where a large number hosts are involved.
Main features:
- A single API for accessing the performance data that hides details of where the data comes from and how it was captured and imported into the PCP framework.
- A client-server architecture allows multiple clients to monitor the same host, and a single client to monitor multiple hosts (e.g. in a Beowulf cluster). This enables centralized monitoring of distributed processing.
- Integrated archive logging and replay so a client application can use the same API to process real-time data from a host or historical data from an archive.
- The framework supports APIs and configuration file formats that enable the scope of performance monitoring to be extended at all levels.
- An "plugin" framework (libraries, APIs, agents and daemon) to collect performance data from multiple sources on a single host, e.g. from the hardware, the kernel, the service layers, the application libraries, and the applications themselves.
- Libraries and sample implementations encourage the development of new "plugins" (or agents) to capture and export the performance data that matters in your application environment, along side the other generic performance data.
- An endian-safe transport layer for moving performance metrics between the collector and the monitoring applications over TCP/IP. This means an IRIX desktop with PCP can monitor one or more Linux systems with the Open Source release of PCP installed.
- A Linux agent that exports a broad range of performance data from most kernels circa 2.0.36 (RedHat 5.2) or later. This includes coverage of activity in the areas of: CPU, disk, memory, swapping, network, NFS, RPC, filesystems and all the per-process statistics.
- Other agents export performance data from:
- Web server activity logs
- arbitrary application-level tracing (via a PCP trace library)
- Cisco routers
- sendmail
- the mail queue
- the PCP infrastructure itself
- Assorted simple monitoring tools that use the PCP APIs to retrieve and display either arbitrary performance metrics, or specific groups of metrics (as in pmstat a cluster-aware vmstat lookalike).
- The PCP inference engine supports automated monitoring through a rule-based language and interpreter that performs user-defined actions when rule predicates are found to be true.
Download (1.3MB)
Added: 2006-10-25 License: LGPL (GNU Lesser General Public License) Price:
1094 downloads
Baudline 1.06
Baudline is a real-time signal analysis tool and an offline time-frequency browser. more>>
Baudline is a real-time signal analysis tool and an offline time-frequency browser. Baudline project has a built-in tone generation capability and it can play back audio files with a multitude of effects and filters.
Designed for environmental analysis missions that range from modulation parameter measurements to searching for transient signals that go bump in the night, baudline combines fast digital signal processing, versatile high-speed displays, and continuous capture tools for hunting down and studying elusive signal characteristics.
Main features:
- 192 kHz real-time bandwidth
- 96 dB dynamic range
- Real or Quadrature input
- Multiple sound card support
- Input Digital Down Converter (tuner)
- Configurable input channels that can perform various operations
- Channel Equalization
- Frequency, time, amplitude, and sample probability distribution analysis
- Drift Integration "de-chirping"
- High speed displays
- Test signal generation
Audio player
- looping
- speed control with multirate resampling
- pitch scaling
- heterodyning (frequency shifting)
- 2D matrix surround panning
- notch, high, and low pass filters
- digital gain boost
File loading
- file formats: .wav, .aiff, .au, .al, .snd, .voc, .rmd, .pvf, .mp3, ID3, .ogg, .gsm, .sah, .fna, raw, .avi, .mov
- channels: mono, stereo, ... up to 9 channels
- data formats: ASCII decimal, A-law, u-law, 1-bit (msb & lsb), 8-bit (signed & unsigned), 16/24/32-bit integer (little & big endian), float, double
- compression
- lossless suffixes: .gz, .bz2, .Z, .zip, .flac
- codecs: ADPCM, GSM, MPEG, Ogg Vorbis
Measurements
- peaks: primary, secondary, delta (Hz dB PSD)
- fundamental: (Hz dB PSD), auto drift rate, chromatic, periodicity, RPM
- distortion: SNR, THD, SINAD, ENOB, SFDR
- power: full, select, noise ratio (dB PSD)
- system: clips, delta selected, frequency range, cursor time, UTC time
<<lessDesigned for environmental analysis missions that range from modulation parameter measurements to searching for transient signals that go bump in the night, baudline combines fast digital signal processing, versatile high-speed displays, and continuous capture tools for hunting down and studying elusive signal characteristics.
Main features:
- 192 kHz real-time bandwidth
- 96 dB dynamic range
- Real or Quadrature input
- Multiple sound card support
- Input Digital Down Converter (tuner)
- Configurable input channels that can perform various operations
- Channel Equalization
- Frequency, time, amplitude, and sample probability distribution analysis
- Drift Integration "de-chirping"
- High speed displays
- Test signal generation
Audio player
- looping
- speed control with multirate resampling
- pitch scaling
- heterodyning (frequency shifting)
- 2D matrix surround panning
- notch, high, and low pass filters
- digital gain boost
File loading
- file formats: .wav, .aiff, .au, .al, .snd, .voc, .rmd, .pvf, .mp3, ID3, .ogg, .gsm, .sah, .fna, raw, .avi, .mov
- channels: mono, stereo, ... up to 9 channels
- data formats: ASCII decimal, A-law, u-law, 1-bit (msb & lsb), 8-bit (signed & unsigned), 16/24/32-bit integer (little & big endian), float, double
- compression
- lossless suffixes: .gz, .bz2, .Z, .zip, .flac
- codecs: ADPCM, GSM, MPEG, Ogg Vorbis
Measurements
- peaks: primary, secondary, delta (Hz dB PSD)
- fundamental: (Hz dB PSD), auto drift rate, chromatic, periodicity, RPM
- distortion: SNR, THD, SINAD, ENOB, SFDR
- power: full, select, noise ratio (dB PSD)
- system: clips, delta selected, frequency range, cursor time, UTC time
Download (1.7MB)
Added: 2007-07-16 License: Free To Use But Restricted Price:
838 downloads
Myco::Entity 1.22
Myco::Entity is a common base class for all Myco entity classes. more>>
Myco::Entity is a common base class for all Myco entity classes.
SYNOPSIS
### Entity class definition
package Myco::Foo;
use base qw(Myco::Entity);
# Start building metadata
my $metadata = Myco::Entity::Meta->new
( name => __PACKAGE__,
tangram => { table => Foo }
);
$metadata->add_attribute(name => attr1, type => string);
$metadata->add_attribute(name => attr2, type => string);
# class-specific methods defined ...
#
# Fill in $schema with all added_attributes and discover other metadata
$metadata->activate_class;
### Entity class usage
use Myco::Foo;
# Constructor
$obj = Myco::Foo->new;
$obj = Myco::Foo->new(attr1 => value, attr2 => value);
# Access class metadata (see Myco::Entity::Meta)
$meta = Myco::Foo->introspect;
$meta = $obj->introspect;
# Accessors
$obj->get_attr1; # get attribute value
$obj->set_attr1(value); # set attribute value
# Instance methods
$id = $obj->save; # update objects state in persistent
# storage, create new record if needed;
# returns objects Tangram id
$obj->destroy;
$obj->modify(attr1 => val, attr2 => val);
$object_id = $obj->id;
$obj->is_transient; # returns true if object is in Tangram
# transient storage
## object retrieval (see class Myco documentation
# for full detail)
$obj = Myco->load($object_id);
# fetch all objects of given type
@objects = Myco->select(ref $obj);
Provides, via inheritence, common interface in support of basic lifecycle needs for myco entity objects.
This is accomplished through the encapsulation of the CPAN module Class::Tangram which provides a basis for "in-memory" object behavior. Consult its documentation for details on schema definition syntax, getter/setter behavior, check functions, etc.
The common interface for object persistence behavior (referred within myco as "transaction" behavior) is provided through defintion of a handful of related instance methods. This is done with reliance on the services of the class Myco, which encapsulates the functionality of Tangram::Storage and provides system-wide connection handling.
<<lessSYNOPSIS
### Entity class definition
package Myco::Foo;
use base qw(Myco::Entity);
# Start building metadata
my $metadata = Myco::Entity::Meta->new
( name => __PACKAGE__,
tangram => { table => Foo }
);
$metadata->add_attribute(name => attr1, type => string);
$metadata->add_attribute(name => attr2, type => string);
# class-specific methods defined ...
#
# Fill in $schema with all added_attributes and discover other metadata
$metadata->activate_class;
### Entity class usage
use Myco::Foo;
# Constructor
$obj = Myco::Foo->new;
$obj = Myco::Foo->new(attr1 => value, attr2 => value);
# Access class metadata (see Myco::Entity::Meta)
$meta = Myco::Foo->introspect;
$meta = $obj->introspect;
# Accessors
$obj->get_attr1; # get attribute value
$obj->set_attr1(value); # set attribute value
# Instance methods
$id = $obj->save; # update objects state in persistent
# storage, create new record if needed;
# returns objects Tangram id
$obj->destroy;
$obj->modify(attr1 => val, attr2 => val);
$object_id = $obj->id;
$obj->is_transient; # returns true if object is in Tangram
# transient storage
## object retrieval (see class Myco documentation
# for full detail)
$obj = Myco->load($object_id);
# fetch all objects of given type
@objects = Myco->select(ref $obj);
Provides, via inheritence, common interface in support of basic lifecycle needs for myco entity objects.
This is accomplished through the encapsulation of the CPAN module Class::Tangram which provides a basis for "in-memory" object behavior. Consult its documentation for details on schema definition syntax, getter/setter behavior, check functions, etc.
The common interface for object persistence behavior (referred within myco as "transaction" behavior) is provided through defintion of a handful of related instance methods. This is done with reliance on the services of the class Myco, which encapsulates the functionality of Tangram::Storage and provides system-wide connection handling.
Download (0.10MB)
Added: 2006-10-20 License: Perl Artistic License Price:
639 downloads
DaVinci 1.0 Alpha
DaVinci is a comprehensive framework for model-driven Web Engineering. more>>
DaVinci is a comprehensive framework for model-driven Web Engineering.
DaVinci is designed as a complete toolkit which consists of three parts: the DaVinci Modeling Framework, the DaVinci Architecture Layer and the DaVinci Runtime Library.
Characteristics:
A fundamental difference to existing Web Engineering frameworks is the architectural concept of DaVinci which is specified in the DaVinci Architectural Layer. The architecture is based on the assumption that, for a Web application (by contrast to a more document-centric Web site) the hypermedia paradigm is more circumstance than useful.
A classical Web site is based on URLs, hyperlinks, and various kinds of resources which is the basic concept of hypermedia systems like the Web.
In the scope of DaVinci, a Web application is more like a traditional application running in the browser. Thus the bahavioural (or functional) aspect is much more important than pages. Pages are generated and transient. Therefore, the basic idea of DaVinci was to eleminate the classical hypermedia paradigm and to inject an additional layer between the Servlet Container and the application (see figure showing the DaVinci Stack).
The DaVinci Architectural Layer provides concepts which are missing in the Servlet API but essential for Web applications. While other projects (e.g. Java Server Faces or Struts) do not re-define the interaction process, DaVinci defines a dedicated GUI model as well as an interaction process.
These four important aspects outline the main characteristics of the DaVinci Web Engineering Framework:
A Web application is not just a set of Web pages, its rather a piece of software with application logic and business state. Thus, the notion of a user session is fundamental.
The view state is part of the session. It is based on a hierarchical view tree model with switchable sub-trees. This allows to change the GUI during the session, but always keeps the GUI in a certain, deterministic state.
Instead of refering to documents, URLs are refering to actions that can be invoked. When modeling an application with DaVinci, the GUI including all interaction spots (buttons, forms, etc.) is well defined allowing the incorporation of CASE tools.
Application logic is modeled using traditional methods and indepenently of the views.
The DaVinci Architectural Layer
The figure below shows the DaVinci Stack. Between the Servlet Container and a DaVinci Web Application there is the DaVinci Architectural Layer.
The DaVinci Modeling Framework
The DaVinci Modeling Framework is a UML-based toolkit for modeling DaVinci applications. It defines the modeling process starting with use cases and storyboarding, then defining the GUI (user-experience model), the database design and finally the application logic which can be done using UML thoroughly. The DaVinci Modeling Framework will provide a rich set of CASE tools which will facilitate and automate the modeling process.
There is already a simple View Stubs Generator which takes a view tree configuration file and generates all views (JSP files) based on configurable skeleton templates. The generator can be found in the package at.davinci.casetools.
The DaVinci Runtime Library
This is the JAVA library containing all required classes for running DaVinci applications. In other words, this is the implementation of the DaVinci Architectural Layer. Currently it also includes all development libraries and CASE tools. But these will be extracted and become part of the DaVinci Modeling Framework in future.
Generic client/server applications
The framework is designed in such a way as to enable the development of any client/server applications. This means, the DaVinci Architectural Layer can be decoupled from the Servlet Context/Web Server-bundle and run on-top of an autonomous DaVinci kernel module. Different FrontController implementations enable the integration of different client/server communication protocols (e.g. FTP, POP3, plain socket communication, etc.).
Thus its possible to use a POP3-FrontController, which will react on incoming e-mails. This can seamlessly migrate different communication channels within a business application and enable business workflows, that are not only based on HTTP, but also on E-Mail, FTP, etc. The framework can also be used for writing arbitrary socket-based server applications (for example a socket-based configuration utility running on an embedded device, etc.)
Currently there is a SocketController, which can be connected with an arbitrary telnet client, and a ConsoleRenderer which will render the state of the view tree into plain text.
<<lessDaVinci is designed as a complete toolkit which consists of three parts: the DaVinci Modeling Framework, the DaVinci Architecture Layer and the DaVinci Runtime Library.
Characteristics:
A fundamental difference to existing Web Engineering frameworks is the architectural concept of DaVinci which is specified in the DaVinci Architectural Layer. The architecture is based on the assumption that, for a Web application (by contrast to a more document-centric Web site) the hypermedia paradigm is more circumstance than useful.
A classical Web site is based on URLs, hyperlinks, and various kinds of resources which is the basic concept of hypermedia systems like the Web.
In the scope of DaVinci, a Web application is more like a traditional application running in the browser. Thus the bahavioural (or functional) aspect is much more important than pages. Pages are generated and transient. Therefore, the basic idea of DaVinci was to eleminate the classical hypermedia paradigm and to inject an additional layer between the Servlet Container and the application (see figure showing the DaVinci Stack).
The DaVinci Architectural Layer provides concepts which are missing in the Servlet API but essential for Web applications. While other projects (e.g. Java Server Faces or Struts) do not re-define the interaction process, DaVinci defines a dedicated GUI model as well as an interaction process.
These four important aspects outline the main characteristics of the DaVinci Web Engineering Framework:
A Web application is not just a set of Web pages, its rather a piece of software with application logic and business state. Thus, the notion of a user session is fundamental.
The view state is part of the session. It is based on a hierarchical view tree model with switchable sub-trees. This allows to change the GUI during the session, but always keeps the GUI in a certain, deterministic state.
Instead of refering to documents, URLs are refering to actions that can be invoked. When modeling an application with DaVinci, the GUI including all interaction spots (buttons, forms, etc.) is well defined allowing the incorporation of CASE tools.
Application logic is modeled using traditional methods and indepenently of the views.
The DaVinci Architectural Layer
The figure below shows the DaVinci Stack. Between the Servlet Container and a DaVinci Web Application there is the DaVinci Architectural Layer.
The DaVinci Modeling Framework
The DaVinci Modeling Framework is a UML-based toolkit for modeling DaVinci applications. It defines the modeling process starting with use cases and storyboarding, then defining the GUI (user-experience model), the database design and finally the application logic which can be done using UML thoroughly. The DaVinci Modeling Framework will provide a rich set of CASE tools which will facilitate and automate the modeling process.
There is already a simple View Stubs Generator which takes a view tree configuration file and generates all views (JSP files) based on configurable skeleton templates. The generator can be found in the package at.davinci.casetools.
The DaVinci Runtime Library
This is the JAVA library containing all required classes for running DaVinci applications. In other words, this is the implementation of the DaVinci Architectural Layer. Currently it also includes all development libraries and CASE tools. But these will be extracted and become part of the DaVinci Modeling Framework in future.
Generic client/server applications
The framework is designed in such a way as to enable the development of any client/server applications. This means, the DaVinci Architectural Layer can be decoupled from the Servlet Context/Web Server-bundle and run on-top of an autonomous DaVinci kernel module. Different FrontController implementations enable the integration of different client/server communication protocols (e.g. FTP, POP3, plain socket communication, etc.).
Thus its possible to use a POP3-FrontController, which will react on incoming e-mails. This can seamlessly migrate different communication channels within a business application and enable business workflows, that are not only based on HTTP, but also on E-Mail, FTP, etc. The framework can also be used for writing arbitrary socket-based server applications (for example a socket-based configuration utility running on an embedded device, etc.)
Currently there is a SocketController, which can be connected with an arbitrary telnet client, and a ConsoleRenderer which will render the state of the view tree into plain text.
Download (0.093MB)
Added: 2006-02-13 License: GPL (GNU General Public License) Price:
1596 downloads
OSSP lmtp2nntp 1.4.1
The OSSP lmtp2nntp program is an LMTP service. more>>
The OSSP lmtp2nntp program is an LMTP service for use in conjunction with a Mail Transfer Agent (MTA) like Sendmail or Postfix, providing a reliable real-time mail to news gateway.
Input messages get their headers slightly reformatted to match Usenet news article format. The article is then posted or feeded into a remote NNTP service (like INN). Delivery must take place immediately or the transaction fails.
OSSP lmtp2nntp relies on the queueing capabilities of the MTA in order to provide a fully reliable service. For this the program returns proper delivery status notification which indicates successful completed action, persistent transient failure or permanent failure.
<<lessInput messages get their headers slightly reformatted to match Usenet news article format. The article is then posted or feeded into a remote NNTP service (like INN). Delivery must take place immediately or the transaction fails.
OSSP lmtp2nntp relies on the queueing capabilities of the MTA in order to provide a fully reliable service. For this the program returns proper delivery status notification which indicates successful completed action, persistent transient failure or permanent failure.
Download (3.1MB)
Added: 2005-10-12 License: GPL (GNU General Public License) Price:
1472 downloads
CELT 0.6.0
CELT is an experimental audio codec for use in low-delay communication. more>>
CELT 0.6.0 is created to be an experimental audio codec for use in low-delay communication. CELT stands for "Code-Excited Lapped Transform". It applies some of the CELP principles, but does everything in the frequency domain, which removes some of the limitations of CELP.
Major Features:
- Ultra-low latency (typically from 3 to 9 ms)
- Full audio bandwidth (44.1 kHz and 48 kHz)
- Stereo support
- Packet loss concealment
- Constant bit-rates from 32 kbps to 128 kbps and above
- A fixed-point version of the encoder and decoder
- The CELT codec is meant to close the gap between Vorbis and Speex for applications where both high quality audio and low delay are desired.
Enhancements:
- Has just been released, with many quality improvements, including better stereo coupling, better handling of transients, and better handling of highly tonal signals.
- Packet loss robustness has been improved through the optional use of independent (intra) frames.
- Supports a larger dynamic range, suitable for encoding 24-bit audio (float version only).
- There is also a very early VBR implementation.
Added: 2009-07-07 License: BSD License Price: FREE
13 downloads
T-BEAR 1.5.1
T-BEAR is the Transient Bluetooth Environment security AuditoR. more>>
T-BEAR is the Transient Bluetooth Environment security AuditoR. It includes an ncurses-based BT scanner, a Bluetooth DoS proof-of-concept, and a "hidden" BDADDR hunter similar to Redfang 2.5.
Other tools based on gnuradio are being developed, including a BT "sniffer".
Enhancements:
- Minor feature enhancements
<<lessOther tools based on gnuradio are being developed, including a BT "sniffer".
Enhancements:
- Minor feature enhancements
Download (0.017MB)
Added: 2005-07-23 License: GPL (GNU General Public License) Price:
1565 downloads
ExodusII 4.46
ExodusII is a model developed to store and retrieve finite element geometry and topology. more>>
ExodusII is a model developed to store and retrieve finite element geometry, topology, and transient data for finite element analyses.
The project is used for preprocessing, postprocessing, as well as code to code data transfer. ExodusII is based on netcdf. It includes the nemesis parallel extension.
<<lessThe project is used for preprocessing, postprocessing, as well as code to code data transfer. ExodusII is based on netcdf. It includes the nemesis parallel extension.
Download (0.36MB)
Added: 2006-11-30 License: BSD License Price:
1061 downloads
glucopy-glurestore 1.0
glucopy-glurestore is a set of scripts for copying and restoring a fully functional GNU/Linux (or other Unix-like) system. more>>
glucopy-glurestore is a set of scripts for copying and restoring a fully functional GNU/Linux (or other Unix-like) system.
The glucopy script will back up all system content (system and user files), while the glurestore script will partition and format an identical system, restore the system and user files, and make the system bootable.
glucopy-glurestore scripts are included in the HTML documentation.
The back-up should (ideally) be made while the system is not running, which usually means that you need to boot with a rescue system disk. A number of suitable floppy or CD-based system images can be downloaded from the net or, better, included in your distributions boot options. Make sure that this rescue system supports the type of disks in your target system (SATA/SCSI or IDE).
The following script will get partition information in a form that can be used to restore the system on new disks and will then collect the working system files in one (or more) compressed tar balls.
The sfdisk program is used for getting partition information (-d option). Take a look at sys_partitions.txt after the glucopy.sh script has finished.
In this application it is considered that all Master Boot Record (MBR) information will be overwritten by the partitioning and boot loader programs. If you need a copy of all or parts of the MBR, however, dd is your friend.
System directories that contain transient information (e.g. /proc, /sys) are not copied. Directories or individual files containing unwanted information can be excluded using tars –exclude=/directory/file option.
#!/bin/sh
###########################
# glucopy.sh
#
# Creates the /glucopy directory
# Copies partition information in sys_partitions.txt
# Optionally makes a copy of the MBR in mbr.bin
# Copies working GNU/Linux system to .tgz files
#
# USAGE:
# Boot system with a rescue CD or any bootable CD
# that supports your type of disks (SATA/SCSI or IDE).
# run the back-up script: ./glucopy.sh
#
# In this example the system is on /dev/sda
# /dev/sda1 is a small partition with HW manufacturer utilities
# /dev/sda2 has system root (/) -> mounted to /mnt
# /dev/sda3 is a spare (blank) partition
# /dev/sda4 has home (/home) and space to hold
# the information to be copied -> mounted to /mnt2
#
# 061116 jp/dm
###########################
# Change the following to reflect the place where your system root (/)
# and the home directories (/home/*) are mounted
mkdir /tmp/mnt1
mkdir /tmp/mnt2
mount /dev/sda2 /tmp/mnt1
mount /dev/sda4 /tmp/mnt2
# The directory to hold the system copy is placed on the larger partition
mkdir /tmp/mnt2/glucopy
# Change to the working directory
cd /tmp/mnt2/glucopy
# Optionally copy MBR information
#dd if=/dev/sda of=mbr.bin bs=512 count=1
# Copy partition information
/sbin/sfdisk -d /dev/sda > sys_partitions.txt
# Make tarballs
tar -C /tmp/mnt1 -cvzf syscopy.tgz boot bin etc lib media opt root sbin usr var dev
# Move up a level
cd ..
# here we are under the /home directory level
# notice that --exclude will exclude anything that matches a _pattern_
# the glucopy directory will still be created in the tarball
tar -cvzf ./glucopy/homecopy.tgz * --exclude=glucopy/*
# Copy the backup/restore scripts (here under root /), and the sfdisk program, as well
cp /glucopy.sh ./glucopy
cp /glurestore.sh ./glucopy
cp /sbin/sfdisk ./glucopy
# Notify user
echo -e “glucopy: finished a”
<<lessThe glucopy script will back up all system content (system and user files), while the glurestore script will partition and format an identical system, restore the system and user files, and make the system bootable.
glucopy-glurestore scripts are included in the HTML documentation.
The back-up should (ideally) be made while the system is not running, which usually means that you need to boot with a rescue system disk. A number of suitable floppy or CD-based system images can be downloaded from the net or, better, included in your distributions boot options. Make sure that this rescue system supports the type of disks in your target system (SATA/SCSI or IDE).
The following script will get partition information in a form that can be used to restore the system on new disks and will then collect the working system files in one (or more) compressed tar balls.
The sfdisk program is used for getting partition information (-d option). Take a look at sys_partitions.txt after the glucopy.sh script has finished.
In this application it is considered that all Master Boot Record (MBR) information will be overwritten by the partitioning and boot loader programs. If you need a copy of all or parts of the MBR, however, dd is your friend.
System directories that contain transient information (e.g. /proc, /sys) are not copied. Directories or individual files containing unwanted information can be excluded using tars –exclude=/directory/file option.
#!/bin/sh
###########################
# glucopy.sh
#
# Creates the /glucopy directory
# Copies partition information in sys_partitions.txt
# Optionally makes a copy of the MBR in mbr.bin
# Copies working GNU/Linux system to .tgz files
#
# USAGE:
# Boot system with a rescue CD or any bootable CD
# that supports your type of disks (SATA/SCSI or IDE).
# run the back-up script: ./glucopy.sh
#
# In this example the system is on /dev/sda
# /dev/sda1 is a small partition with HW manufacturer utilities
# /dev/sda2 has system root (/) -> mounted to /mnt
# /dev/sda3 is a spare (blank) partition
# /dev/sda4 has home (/home) and space to hold
# the information to be copied -> mounted to /mnt2
#
# 061116 jp/dm
###########################
# Change the following to reflect the place where your system root (/)
# and the home directories (/home/*) are mounted
mkdir /tmp/mnt1
mkdir /tmp/mnt2
mount /dev/sda2 /tmp/mnt1
mount /dev/sda4 /tmp/mnt2
# The directory to hold the system copy is placed on the larger partition
mkdir /tmp/mnt2/glucopy
# Change to the working directory
cd /tmp/mnt2/glucopy
# Optionally copy MBR information
#dd if=/dev/sda of=mbr.bin bs=512 count=1
# Copy partition information
/sbin/sfdisk -d /dev/sda > sys_partitions.txt
# Make tarballs
tar -C /tmp/mnt1 -cvzf syscopy.tgz boot bin etc lib media opt root sbin usr var dev
# Move up a level
cd ..
# here we are under the /home directory level
# notice that --exclude will exclude anything that matches a _pattern_
# the glucopy directory will still be created in the tarball
tar -cvzf ./glucopy/homecopy.tgz * --exclude=glucopy/*
# Copy the backup/restore scripts (here under root /), and the sfdisk program, as well
cp /glucopy.sh ./glucopy
cp /glurestore.sh ./glucopy
cp /sbin/sfdisk ./glucopy
# Notify user
echo -e “glucopy: finished a”
Download (0.14MB)
Added: 2006-12-07 License: (FDL) GNU Free Documentation License Price:
1051 downloads
Sunifdef 3.1
Sunifdef is a command line tool for simplifying the preprocessor conditionals in C/C++ source code. more>>
Sunifdef is a command line tool for simplifying the preprocessor conditionals in C/C++ source code (#if and related directives) based on the the users chosen interpretation of the preprocessor symbols.
Sunifdef is a more powerful successor to the FreeBSD unifdef tool. Sunifdef is most useful to developers of constantly evolving products with large code bases, where preprocessor conditionals are used to configure the feature sets, APIs or implementations of different releases.
In these environments, the code base steadily accumulates #ifdef-pollution as transient configuration options become obselete. Sunifdef can largely automate the recurrent task of purging redundant #if-logic from the code.
Installation:
Download the tarball to a location under your home directory
Extract the directory sunifdef from the tarball. Do not rename it.
To install from source:
Open a command console and cd into the sunifdef directory
Run ./configure
If all is well, run make
If all is well, run su and enter the root password when prompted (to become root).
Run make install
To install the pre-built executable:
As root, copy built-bin/sunfidef from the sunifdef directory into /usr/local/bin.
Set permissions on /usr/local/bin/sunifdef to make it executable.
As root, copy man/sunifdef.1 from the sunifdef directory into /usr/local/man/man1
To test that Sunifdef is installed:
Run sunifdef -v, and expect output like:
sunifdef, version 0.1.3 (built Feb 22 2006, 19:47:48)
sunifdef: Completed, exit code 0x0000
Run man sunifdef, and expect to see the sunifdef man page.
Enhancements:
- The parser is strengthened to cope with contexts that were formerly skipped over as "obfuscated".
- The --obfusc option is thus redundant and is withdrawn.
- Six bugs are fixed.
- The demise of the Sourceforge compile farm means that many platforms can no longer be tested for this release.
<<lessSunifdef is a more powerful successor to the FreeBSD unifdef tool. Sunifdef is most useful to developers of constantly evolving products with large code bases, where preprocessor conditionals are used to configure the feature sets, APIs or implementations of different releases.
In these environments, the code base steadily accumulates #ifdef-pollution as transient configuration options become obselete. Sunifdef can largely automate the recurrent task of purging redundant #if-logic from the code.
Installation:
Download the tarball to a location under your home directory
Extract the directory sunifdef from the tarball. Do not rename it.
To install from source:
Open a command console and cd into the sunifdef directory
Run ./configure
If all is well, run make
If all is well, run su and enter the root password when prompted (to become root).
Run make install
To install the pre-built executable:
As root, copy built-bin/sunfidef from the sunifdef directory into /usr/local/bin.
Set permissions on /usr/local/bin/sunifdef to make it executable.
As root, copy man/sunifdef.1 from the sunifdef directory into /usr/local/man/man1
To test that Sunifdef is installed:
Run sunifdef -v, and expect output like:
sunifdef, version 0.1.3 (built Feb 22 2006, 19:47:48)
sunifdef: Completed, exit code 0x0000
Run man sunifdef, and expect to see the sunifdef man page.
Enhancements:
- The parser is strengthened to cope with contexts that were formerly skipped over as "obfuscated".
- The --obfusc option is thus redundant and is withdrawn.
- Six bugs are fixed.
- The demise of the Sourceforge compile farm means that many platforms can no longer be tested for this release.
Download (0.10MB)
Added: 2007-05-13 License: BSD License Price:
894 downloads
petardfs 0.0.2
petardfs is a FUSE filesystem designed to hoist your applications with errors. more>>
petardfs is a FUSE filesystem designed to hoist your applications with errors. With no configuration, petardfs takes a base filesystem and exposes it through FUSE.
An XML configuration file is used to tell petardfs which files to report errors for and what error code to use. For example, foo.txt can have an EIO error at bytes 34 to 37.
There is explicit support for errors such as EAGAIN and EINTR, where petardfs will only report such transient errors a nominated number of times. This is handy for testing applications that support such I/O conditions gracefully.
<<lessAn XML configuration file is used to tell petardfs which files to report errors for and what error code to use. For example, foo.txt can have an EIO error at bytes 34 to 37.
There is explicit support for errors such as EAGAIN and EINTR, where petardfs will only report such transient errors a nominated number of times. This is handy for testing applications that support such I/O conditions gracefully.
Download (0.28MB)
Added: 2007-03-20 License: GPL (GNU General Public License) Price:
948 downloads
Mail::RFC822::Address 0.3
Mail::RFC822::Address is a Perl extension for validating email addresses according to RFC822. more>>
Mail::RFC822::Address is a Perl extension for validating email addresses according to RFC822.
SYNOPSIS
use Mail::RFC822::Address qw(valid validlist);
if (valid("pdw@ex-parrot.com")) {
print "Thats a valid addressn";
}
if (validlist("pdw@ex-parrot.com, other@elsewhere.com")) {
print "Thats a valid list of addressesn";
}
Mail::RFC822::Address validates email addresses against the grammar described in RFC 822 using regular expressions. How to validate a user supplied email address is a FAQ (see perlfaq9): the only sure way to see if a supplied email address is genuine is to send an email to it and see if the user recieves it. The one useful check that can be performed on an address is to check that the email address is syntactically valid. That is what this module does.
This module is functionally equivalent to RFC::RFC822::Address, but uses regular expressions rather than the Parse::RecDescent parser. This means that startup time is greatly reduced making it suitable for use in transient scripts such as CGI scripts.
valid ( address )
Returns true or false to indicate if address is an RFC822 valid address.
validlist ( addresslist )
In scalar context, returns true if the parameter is an RFC822 valid list of addresses.
In list context, returns an empty list on failure (an invalid address was found); otherwise a list whose first element is the number of addresses found and whose remaining elements are the addresses. This is needed to disambiguate failure (invalid) from success with no addresses found, because an empty string is a valid list
<<lessSYNOPSIS
use Mail::RFC822::Address qw(valid validlist);
if (valid("pdw@ex-parrot.com")) {
print "Thats a valid addressn";
}
if (validlist("pdw@ex-parrot.com, other@elsewhere.com")) {
print "Thats a valid list of addressesn";
}
Mail::RFC822::Address validates email addresses against the grammar described in RFC 822 using regular expressions. How to validate a user supplied email address is a FAQ (see perlfaq9): the only sure way to see if a supplied email address is genuine is to send an email to it and see if the user recieves it. The one useful check that can be performed on an address is to check that the email address is syntactically valid. That is what this module does.
This module is functionally equivalent to RFC::RFC822::Address, but uses regular expressions rather than the Parse::RecDescent parser. This means that startup time is greatly reduced making it suitable for use in transient scripts such as CGI scripts.
valid ( address )
Returns true or false to indicate if address is an RFC822 valid address.
validlist ( addresslist )
In scalar context, returns true if the parameter is an RFC822 valid list of addresses.
In list context, returns an empty list on failure (an invalid address was found); otherwise a list whose first element is the number of addresses found and whose remaining elements are the addresses. This is needed to disambiguate failure (invalid) from success with no addresses found, because an empty string is a valid list
Download (0.005MB)
Added: 2007-02-14 License: Perl Artistic License Price:
985 downloads
AfterStep 2.2.6
AfterStep is a window manager for the Unix X Window System. more>>
AfterStep is a window manager for the Unix X Window System. Originally based on the look and feel of the NeXTStep interface, it provides end users with a consistent, clean, and elegant desktop.
AfterSteps goal is to provide for flexibility of desktop configuration, improving aestetics, and efficient use of system resources.
Whats New in This Release:
* fixed handling of AvoidCover on window move/resize
* changed default wharf geometry to go into upper left corner
* upgraded AS version in anticipation of release
* added ability to Wharf to kill swallowed apps by its PID. That
seems to have resolved a problem with trayer app
* fixed bug where if DesktopEntry was not found - there would still
be an emoty wharf button
* Fixed handling of ballons config parsing; Implemented support for
ShowHints in WinList allowing for Name, IconName, ResClass,
ResName
* made ShowHints more generic option allowing iut to be used in
other modules - started modifying WinList to make use of it
* Implemented NoModuleNameCollisions in base config to make AS kill
old instances of the module with same name
* fixed installation as an alternative to use proper link name
* cleanup of the stacking order code
* implemented IgnoreRestack to adde finer grain to IgnoreConfig -
IgnoreRestack will only ignore Raise/Lower requests from the
client
* fixed window list publishing to use new stacking_order vector
* minor optimization of the alpha-blending code
* added test container for mmx use
* fixed MMX usage - required _mm_empty() after each mmx intrinsics
use; Optimized window title change to not regenerate icon when
not in iconic mode
* Implemented support for root window having different color depth
- blacxk background on 16bpp screens should go away; temorarily
disabled mmx - it seems to ruin images sometimes
* fixed color printing on 64 bit system
* replaced mmx code to use gcc intinsics
* updated paths for Propaganda images.
* added folders in Menu Desktop/Pictures for Propaganda images.
* fixed parsing of ARGB icons supplied by applications
* fixed stacking order of mozilla dialogs - it creates group member
dialog that is not a transient, and then it creates a transient,
but transient for the main window - not the dialog, resulting in
this last transient to be under first dialog
* fixed handling of recursive transients, as is the case with
mozilla - it was crashing AS and messing up stacking order
<<lessAfterSteps goal is to provide for flexibility of desktop configuration, improving aestetics, and efficient use of system resources.
Whats New in This Release:
* fixed handling of AvoidCover on window move/resize
* changed default wharf geometry to go into upper left corner
* upgraded AS version in anticipation of release
* added ability to Wharf to kill swallowed apps by its PID. That
seems to have resolved a problem with trayer app
* fixed bug where if DesktopEntry was not found - there would still
be an emoty wharf button
* Fixed handling of ballons config parsing; Implemented support for
ShowHints in WinList allowing for Name, IconName, ResClass,
ResName
* made ShowHints more generic option allowing iut to be used in
other modules - started modifying WinList to make use of it
* Implemented NoModuleNameCollisions in base config to make AS kill
old instances of the module with same name
* fixed installation as an alternative to use proper link name
* cleanup of the stacking order code
* implemented IgnoreRestack to adde finer grain to IgnoreConfig -
IgnoreRestack will only ignore Raise/Lower requests from the
client
* fixed window list publishing to use new stacking_order vector
* minor optimization of the alpha-blending code
* added test container for mmx use
* fixed MMX usage - required _mm_empty() after each mmx intrinsics
use; Optimized window title change to not regenerate icon when
not in iconic mode
* Implemented support for root window having different color depth
- blacxk background on 16bpp screens should go away; temorarily
disabled mmx - it seems to ruin images sometimes
* fixed color printing on 64 bit system
* replaced mmx code to use gcc intinsics
* updated paths for Propaganda images.
* added folders in Menu Desktop/Pictures for Propaganda images.
* fixed parsing of ARGB icons supplied by applications
* fixed stacking order of mozilla dialogs - it creates group member
dialog that is not a transient, and then it creates a transient,
but transient for the main window - not the dialog, resulting in
this last transient to be under first dialog
* fixed handling of recursive transients, as is the case with
mozilla - it was crashing AS and messing up stacking order
Download (5.9MB)
Added: 2007-05-21 License: GPL (GNU General Public License) Price:
970 downloads
Bluewall GNU/Linux 1.2 Lite
Bluewall is a GNU/Linux distribution based on Debian and pkgsrc. more>>
Bluewall is a GNU/Linux distribution based on Debian and pkgsrc.
Bluewall GNU/Linux aims to create a complete pkgsrc-based GNU/Linux distribution.
Packages:
- debian
- pkgsrc
Enhancements:
- After some long time, a new bluewall has been released.
- This is a transient release, after the maintainer change this version tries to be a testing release, but feel free to report bugs!
- This new version updates the base debian to SID aka Debian unstable, also integrates the current CVS tree and some (541) i386-binary pkgsrc packages like Gnome, 2.12.2, Gimp 2.2.10, Xorg 6.8.1...
<<lessBluewall GNU/Linux aims to create a complete pkgsrc-based GNU/Linux distribution.
Packages:
- debian
- pkgsrc
Enhancements:
- After some long time, a new bluewall has been released.
- This is a transient release, after the maintainer change this version tries to be a testing release, but feel free to report bugs!
- This new version updates the base debian to SID aka Debian unstable, also integrates the current CVS tree and some (541) i386-binary pkgsrc packages like Gnome, 2.12.2, Gimp 2.2.10, Xorg 6.8.1...
Download (128MB)
Added: 2006-02-05 License: GPL (GNU General Public License) Price:
1359 downloads
Other version of Bluewall GNU/Linux
This is a transient release, after the maintainer change this version tries to be a testing release, but feel free to report bugs! - This new version updates the base debian to SID aka Debian unstableLicense:GPL (GNU General Public License)
Secleted [ 0 ] software to compare
- Page: 1 of 2
- 1
- 2
Copyright Notice:
Software piracy is theft, Using crack, password, serial numbers, registration codes, key generators is illegal and prevent future software development. The above transient 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
