Search Results for "types"

DAR is a command-line backup and archiving tool that uses selective compression (not compressing already compressed files), strong encryption, may split an archive in different files of given size and provides on-fly hashing, supports differential backup with or without binary delta, ftp and sftp protocols to remote cloud storage Archive internal's catalog, allows very quick restoration even a single file from a huge, eventually sliced, compressed, encrypted archive eventually located on a remote cloud storage, by only reading/fetching the necessary data to perform the operation. Dar saves *all* UNIX inode types, takes care of hard links, sparse files as well as Extended Attributes (MacOS X file forks, Linux ACL, SELinux tags, user attributes) and some Filesystem Specific Attributes (Linux ext2/3/4, Mac OS X HFS+) more details at: http://dar.linux.free.fr/doc/Features.html

A file manager for the Unix terminal. Unlike most file managers out there, based on the TUI, CliFM is entirely based on command-line. It is also ultra-lightweight, lightning fast, extensible, and written in C.

pofig - portable shell script for probing base system properties: OS, OS version, kernel version, distro, distro version, architecture. It detects: 19 operating systems, 11 major linux distros, 13 CPU types. See wiki for more information and examples.

...The core set of daemons is written in C, however, any event (such as a light being turned on) can be handled by an external script or program. These programs can be written in any language, and the central daemon handles all the intercommunication. It is designed to be easily extensible for new device types and protocols. The core system is BSD Licensed (3-clause), however scripts or additional data collectors may be written under any acceptable lic. While the primary development environment for this is NetBSD, it can be used on other UNIX variants, such as Linux, or other BSD's.

CDs can be thought of as a mechanism to support fine-grained, hierarchical, application-directed, uncoordinated checkpoint and restore. Containment Domains (CDs) were created to allow an application to recover in the face of various types of component failures, including hard (e.g. persistent) and soft (e.g. transient) hardware failures, transient software failures, and complete node failures.