Free plans software for linux

Plan/B is a network aware file backup system specifically designed to make the backup of files from multiple machines to a variety of devices simple.
The system provides features such as comprehensive reporting, the ability to use CDROM (and soon DVD) drives across the network, as well as centralised management.
Plan/B can be deployed on Windows and Linux systems.
Main features:
General
- Backup anything, to anywhere: You can use any kind of device that plasticine knows about (currently CDROM, Local disk, Network share, FTP device) as either a source or destination. There is no limitation (as there is in DataArmour).
- Multiple sources, Multiple Destinations: A backup may source its files from multiple machines and devices. The destinations for a backup job can also be any number of machines or devices. Thus it is now easy to have a single set of files (documents, code or other important assets) copied to more than one location using a single job. No need to clone a job anymore!
- Multi-Platform: As the system is written in Java, it will work with any machine for which there is a VM (this is true for the backup server and agents). The administration console can be run on either a Linux or Windows machine (when SWT, the GUI framework used for the console matures on OsX, the console will be able to run on that OS as well)
- Volume spanning: If any removable destination is out of space, then it is possible to request the next volume during the backup process. A good example of this is backup to multiple CDs. Plasticine supports both the spanning of single files across multiple media, and also the saving of complete files across different media. In the first case, a large file can be split across two volumes. In the second case, only complete files are written to any volume (obviously, if the file is larger than the size of the volume, it will have to be split up).
- Flexible selection: A single job can backup whatever is deemed important to the user. The files to backup are specified by rules, which can be as simple as include everything, and complex as include all word documents, all excel spreadsheets under my docs directory, and everything NOT ending in .bak under the data directory
- Flexible scheduler: Jobs can be run whenever you like. The current scheduling implementation takes on a form very similar to Cron, but other implementations are easily added. The important point here is that the process of deciding when a backup should be run is completely separated from anything else about the backup job. This is a change from DataArmour, where the scheduling (specifically, the weekly incremental backup job scheduling) is fixed to run on a Monday, with a full backup occurring every week. In Plasticine, user defined schedules are possible.
- Statistics: The system emits various statistics while in operation, including current progress of various jobs, jobs in the run queue, current load, and recent logged events.
Enterprise
- Reliable:The remote agents are resilient to network failure. If a server cannot be contacted, they will move into a discovery mode until the server is back up. No configuration is required!
- Painless installation: The system is very easy to install - just run the included windows installer and tell it what kind of install you want. All services are configured automatically.
- Administration Console: The backup server is a separate process, which is administered via a GUI console. The console can be run from any machine, and can control and manage the settings for the backup server and any client. That means you can configure everything from one place.
Enhancements:
- This release added an option to specify that the destination location should be deleted prior to the backup occuring.
- It also added an option to copy full folders and specify whether or not to create an absolute or relative backup.
- Completion was sped up by detaching the email sending from the job completion process.
- Warnings are now used to log more in the reports for situations that are not necessarily fatal.
- When adding a source or destination, the file browser is now automatically opened for you.
- It is now possible to have multiple email recipients for a backup report.

Plan 9 from Bell Labs is a research system developed at Bell Labs starting in the late 1980s. Its original designers and authors were Ken Thompson, Rob Pike, Dave Presotto, and Phil Winterbottom. They were joined by many others as development continued throughout the 1990s to the present.
Plan 9 demonstrates a new and often cleaner way to solve most systems problems. The system as a whole is likely to feel tantalizingly familiar to Unix users but at the same time quite foreign.
In Plan 9, each process has its own mutable name space. A process may rearrange, add to, and remove from its own name space without affecting the name spaces of unrelated processes. Included in the name space mutations is the ability to mount a connection to a file server speaking 9P, a simple file protocol.
The connection may be a network connection, a pipe, or any other file descriptor open for reading and writing with a 9P server on the other end. Customized name spaces are used heavily throughout the system, to present new resources (e.g., the window system), to import resources from another machine (e.g., the network stack), or to browse backward in time (e.g., the dump file system).
Plan 9 is an operating system kernel but also a collection of accompanying software. The bulk of the software is predominantly new, written for Plan 9 rather than ported from Unix or other systems. The window system, compilers, file server, and network services are all freshly written for Plan 9. Although classic Unix programs like dc(1), ed(1), and even troff(1) have been brought along, they are often in an updated form. For example, troff accepts Unicode documents encoded in UTF-8, as does the rest of the system.
Enhancements:
- Some fixes for a time sync related problem and minor feature enhancements.

Plan-B is a bootable Linux environment without the need for a hard drive, it runs entirely in ram or from the cd, based on a basic, stripped installation of Red Hat Linux and the fundamental workings of the SuperRescue CD. A list of tools and utilities are also included for projects such as:

* Forensics/Data Recovery
* System/Network Analysis and Security Scanning
* Temporary Network Device/Server
* IDS / NIDS System
* Network Status Report Creation

My reason for its creation came about due to finding other similar projects (SuperRescue CD, Biatchux (F.I.R.E.), Trinux, Knoppix) to be geared toward only a single area of the broad spectrum I was looking for. The first of which (by H. Peter Anvin, the author of Syslinux, Isolinux, and zisofs) was the only one close to the concept I had in mind which is why I chose it as the foundation for this cd. After not finding what I was really looking for, the "All-in-One", I decided the only way to get it was to build one myself.

pam_sotp PAM module provides support for One Time Passwords (OTP) authentication. The "s" in "sotp" stands for "simple"; pam_sotp aims to be a simple, easy to configure, module.
pam_sotp is still under early stages of development. Although it seems to work pretty well be warned that this software could contain severe bugs that may put at risk the security of your system. Until a stable release is reached you are advised to not use pam_sotp on mission-critical systems or production servers.
Having said that, it seems that the software is reaching an stable stage. Ive received several reports about pam_sotp being used without problems in several configurations.
This project is way too small to have a serious roadmap, but anyways I guess that some of you would like to know what are my short/medium term plans for pam_sotp, so here they are:
Release pam_sotp 0.4.0, with some patches I received and other improvements I have in mind
Maintain the 0.4.x branch until it becomes stable
Release a couple of 1.0 release candidates and then finally pam_sotp 1.0
Maintain the 1.0 branch
Enhancements:
- Added disable and enable commands to otppasswd
- Bugfix: SGID shadow applications could not authenticate against pam_sotp (some SUID code somehow remained in pam_sotp)

Planner is a project managment tool for the Gnome desktop, for planning, scheduling and tracking projects.
Main features:
- Definition of tasks and subtasks, resources and resource groups
- Dependencies between tasks
- Display of the critical path
- Calendars with working/non-working time
- Gantt chart and resource usage overview
- HTML export of project plans
- Translated to nearly 20 languages, e.g. French, Spanish and Swedish
Enhancements:
- fix bug #353232 - patch to raise majic priority, fixing nautilus behavior when clicking on a planner file
- fix bug #368186 - patch to paint guide lines behind project start date rather than on top - contributed by Arthur Petitpierre
- added -Wno-return-type for compile with database enabled
- patch related to bug #353213 - added #ifdefs to allow compile with libgda 1 or 2, up to libgda-1.9.102
- Added Arabic - contributed by Djihed Afifi
- fix for bug 358415 crash in gantt view, contributed by Arthur Petitpierre and mdpoole trolius org.

YASTR is a simple string library that mainly consists of functionality that I require in my programs.

This entire library should be compatible with ANSI C89 && C99. To use, copy yastr.c, include "yastr.h" and go. No libraries to link, no special compilation flags, nada, zip zilch.

No initialization of the library is needed, but it is possible to configure the library to use custom functions to manage memory, as well as set the character used to escape and unescape strings.

Much of the library uses a yastr string, which is (currently) a rather simple structure, but please use yastr_len() and yastr_strptr() to extract the length and string pointer from a yastr struct. In future releases, the members of the structure may change as needed, but there are currently no plans to change yastr_len() or yastr_strptr().

To create a new yastr struct, try yastrnew() or yastrdup(). To destroy a string and free up memory, use yastrfree() on the string.

Most of the naming convention is ya[function], where [function] is the C function most similar to ya[function]. For example: yavsnprintf() -> vsnprintf()

Yastr also impliments a few non-traditional functions for manipulating string structures.

It is very similar to del.icio.us and in addition, it enables conversations around posts. To use the PostIt extension, you need to download and install the Indus Live SDK (available at http://www.aumeganetworks.com) which provides access to the P2P network and the PostIt application (available at http://www.aumeganetworks.com) which can be installed using the Indus Live toolbar.

PostIt currently features abilities to mark-and-post any web content, bookmark pages, add contacts, share and reply to posts, editing and organisation of posts. Indus Live has been designed to enable implementation and hosting of open source P2P services and developers are encouraged to improve PostIt (sources available from http://sourceforge.net/projects/indus) and add other P2P services. Current plans include adding tags, public posts and search, post to blogs, feeds of tagged posts and import/export of posts.