Free dvd2one 2.3.0 serial software for linux

Cons is a Software Construction System.

Cons is a system for constructing, primarily, software, but is quite different from previous software construction systems. Cons was designed from the ground up to deal easily with the construction of software spread over multiple source directories. Cons makes it easy to create build scripts that are simple, understandable and maintainable. Cons ensures that complex software is easily and accurately reproducible.

Cons uses a number of techniques to accomplish all of this. Construction scripts are just Perl scripts, making them both easy to comprehend and very flexible. Global scoping of variables is replaced with an import/export mechanism for sharing information between scripts, significantly improving the readability and maintainability of each script.

Construction environments are introduced: these are Perl objects that capture the information required for controlling the build process. Multiple environments are used when different semantics are required for generating products in the build tree. Cons implements automatic dependency analysis and uses this to globally sequence the entire build. Variant builds are easily produced from a single source tree. Intelligent build subsetting is possible, when working on localized changes. Overrides can be setup to easily override build instructions without modifying any scripts. MD5 cryptographic signatures are associated with derived files, and are used to accurately determine whether a given file needs to be rebuilt.

While offering all of the above, and more, Cons remains simple and easy to use. This will, hopefully, become clear as you read the remainder of this document.

Why Cons? Why not Make?

Cons is a make replacement. In the following paragraphs, we look at a few of the undesirable characteristics of make--and typical build environments based on make--that motivated the development of Cons.

Build complexity

Traditional make-based systems of any size tend to become quite complex. The original make utility and its derivatives have contributed to this tendency in a number of ways. Make is not good at dealing with systems that are spread over multiple directories. Various work-arounds are used to overcome this difficulty; the usual choice is for make to invoke itself recursively for each sub-directory of a build. This leads to complicated code, in which it is often unclear how a variable is set, or what effect the setting of a variable will have on the build as a whole. The make scripting language has gradually been extended to provide more possibilities, but these have largely served to clutter an already overextended language. Often, builds are done in multiple passes in order to provide appropriate products from one directory to another directory. This represents a further increase in build complexity.

Build reproducibility

The bane of all makes has always been the correct handling of dependencies. Most often, an attempt is made to do a reasonable job of dependencies within a single directory, but no serious attempt is made to do the job between directories. Even when dependencies are working correctly, makes reliance on a simple time stamp comparison to determine whether a file is out of date with respect to its dependents is not, in general, adequate for determining when a file should be rederived. If an external library, for example, is rebuilt and then ``snapped into place, the timestamps on its newly created files may well be earlier than the last local build, since it was built before it became visible.

Variant builds

Make provides only limited facilities for handling variant builds. With the proliferation of hardware platforms and the need for debuggable vs. optimized code, the ability to easily create these variants is essential. More importantly, if variants are created, it is important to either be able to separate the variants or to be able to reproduce the original or variant at will. With make it is very difficult to separate the builds into multiple build directories, separate from the source. And if this technique isnt used, its also virtually impossible to guarantee at any given time which variant is present in the tree, without resorting to a complete rebuild.

Repositories

Make provides only limited support for building software from code that exists in a central repository directory structure. The VPATH feature of GNU make (and some other make implementations) is intended to provide this, but doesnt work as expected: it changes the path of target file to the VPATH name too early in its analysis, and therefore searches for all dependencies in the VPATH directory. To ensure correct development builds, it is important to be able to create a file in a local build directory and have any files in a code repository (a VPATH directory, in make terms) that depend on the local file get rebuilt properly. This isnt possible with VPATH, without coding a lot of complex repository knowledge directly into the makefiles.

netshng project can be used in the development of applications which require direct communication (using the netsh protocol) with a Foxmoxie Networks STRATA-family router.

This program requires the use of libnetshclient. If in doubt, use the latest versions of both.

This application has been tested on the Linux platform only.

To compile, you must have:

GNU make 3.81+
GNUtls 1.4.4+
libnetshclient 2.2.0+

and of course, standard Posix and ANSI headers.

To build the binary, simply edit the Makefile and change the value of the variable named LIBNETSHCLIENT to the directory of your libnetshclient source and build.

Once done, type make.

There is presently no install mechanism, so this must be done manually.

stl2pov reads an STL (Standard Triangulation Language) file and outputs a POVray mesh.
stl2pov has been tested with STL files generated by Pro/Engineer.
BUILDING THE PROGRAM
For building on FreeBSD and other systems with the GNU toolset, see the instructions in the file INSTALL. After installation, a manual page for this program can be read with man stl2pov. Additional documentation is available in the documentation directory. See the Makefile.
I have set up a cross-compiler to produce a win32 binary. You can find it in the file stl2pov-2.3.0.zip on my website; http://www.xs4all.nl/~rsmith/software/
If anyone wants to donate makefiles or project files for other systems and compilers I will be happy to include them in the distribution.
Enhancements:
- Follow the new syntax for povray: use triangle instead of facet.

pngcheck verifies the integrity of PNG, JNG and MNG files (by checking the internal 32-bit CRCs [checksums] and decompressing the image data); pngcheck can optionally dump almost all of the chunk-level information in the image in human-readable form.
For example, it can be used to print the basic statistics about an image (dimensions, bit depth, etc.); to list the color and transparency info in its palette (assuming it has one); or to extract the embedded text annotations.
All PNG and JNG chunks are supported, plus almost all MNG chunks (everything but PAST, MAGN, DISC, DROP, DBYK, ORDR, and pHYg). This is a command-line program with batch capabilities (e.g., "pngcheck *.png").
Enhancements:
- This version adds an option to colorize the output (using ANSI colors), enhances the verbose output for interlaced images, and fixes three bugs that showed up in the most recent release of the brokensuite test images.

The ser2net daemon allows telnet and TCP sessions to be established with a units serial ports. Note that ser2net supports RFC 2217 (remote control of serial port parameters), but you must have a complient client. The only one I know it is kermit application (http://www.columbia.edu/kermit).
Enhancements:
- dataxfer.c, devcfg.c, devcfg.h, ser2net.conf, ser2net.8: Added a s banner token for printing out the serial parameters.
- ser2net.conf: Cleaned up the ugly banner3.
- Makefile.am: Add ser2net.init to EXTRA_DIST.
- configure.in: Move to version 2.3.

GKrellM application is a GTK-based stacked monitor program that charts SMP CPUs, disks, load, active net interfaces, and internet connections.
There are also builtin monitors for memory and swap, file systems with mount/umount feature, mailbox checking including POP3 and IMAP, clock/calendar, laptop battery, sensors (temperatures, voltages, and fans), and uptime.
It has LEDs for the net monitors and an on/off button and online timer for PPP. There is a GUI popup for configuration, plugin extensions can be installed, and many themes are available. It also features a client/server monitoring capability.
Main features:
- Hostname/systemname display.
- Clock/calendar.
- SMP CPU monitor that can chart individual CPUs and/or a composite CPU.
- Temperature, fan, and voltage sensor monitors if supported by the kernel and the mainboard hardware (Linux requires lm_sensors to be installed).
- Each sensor monitor has a configurable alarm and warning.
- Process monitor with a chart for load and forks and a display of number of current processes and users.
- Disk monitor that can chart individual disks or a composite disk.
- Internet monitor (http, ftp, ...) that displays current tcp port connections and charts historical port hits for over two days.
- Net interface monitors with charts for all routed net interfaces. Data rx/tx LEDs and a timer button that can be linked to a ppp or isdn net interface and displays on line time.
- Memory and swap space usage meters, and a swap page in/out chart.
- File system meters which show capacity/free space and can mount/umount.
- A mailbox monitor which can launch a mail reader, a mail fetch/check program, and a sound notify command. Builtin new mail message checking for mbox, maildir, MH, POP3, and IMAP mailboxes.
- APM laptop battery meter with a configurable alarm and warning for low battery time left.
- Uptime display.
- Multiple monitors managed by a single process to reduce system load.
- Charts have auto scaling or fixed scaling modes.
- Commands can be configured to run when monitor labels are clicked.
- gkrellm can run in client mode and collect data from a gkrellmd server running on a remote machine.
- Both gkrellm and the gkrellmd server are plugin capable so special interest monitors can be coded.

synctool is an administrative tool for working with clusters of computers.
synctool copies configuration files to groups of machines in your cluster based on what groups (or classes) they are in. By doing so, it keeps the configuration on that group of machines synchronized (or, "in sync").
If needed, synctool will restart or reload any daemons, as you wish. synctool can be easily extended to do other administrative tasks, such as checking daemons, checking free disk space, installing packages, etc. or any other task you want it to do.
synctool was developed by Walter de Jong from 2003 to 2006.
synctool simplyfies system administration by working with the following concepts:
- a host can be part of one or more groups, or classes
- files are designated a class by means of filename extension
- the overlay directory tree contains the files and directories that should be copied (or synced) to the target host
- when certain files are updated, you will want to execute a script (eg, /etc/init.d/daemon restart)
- simplicity. It uses the power of rsync and ssh to distribute the files.
- extendibility. Make synctool more powerful by writing plugin scripts.