Free archivers roseville software for linux

User::Identity::Archive is a base class for archiving user information.

INHERITANCE

User::Identity::Archive
is a User::Identity::Item

User::Identity::Archive is extended by
User::Identity::Archive::Plain

SYNOPSIS

use User::Identity::Archive::Plain;
my $friends = User::Identity::Archive::Plain->new(friends);
$friends->from(*FH);
$friends->from(.friends);

An archive stores collections. It depends on the type of archive how and where that is done. Some archivers may limit the kinds of selections which can be stored.

hbuild53 (hastek build for FreeBSD 5.3 onward) is a script package to help build FreeBSD base systems. It makes sense if you have multiple systems to build.

hbuild53 will work on FreeBSD 4.x - however the base kernel configuration file will not - as of 5.2.1 the base kernel configuration file is too different.

hbuild53 provides automation for some of the things you might typically do after a base FreeBSD installation. This is relatively simple stuff but has saved me time when building/rebuilding/upgrading multiple systems.

This idea will probably make sense to those who build multiple machines, and will not make sense if you work with one or two systems only..

This package is intended to help start a server build (not to be installed over existing systems, though it probably wont hurt anything to do so), assuming you will be building
other applications later as you build your final platform.

This package is specific to FreeBSD 5.3-RELEASE onward. It will upgrade your ports tree, install ports, create some customizations, and provide some sysadmin packages, such as log archivers, a chrooted BIND builder, a heirarchichal unix platform backup system, shows how to set up serial console, a new kernel, and ipf for packet filtering.

Each hbuild subdirectory has bits you might be able to adapt into your own system administration.

You will need a reasonably fast internet connection for the ports. Why install ports rather than packages? You dont have to, but I always thought its better to build the software on the particular system, although it takes longer.

MixIt is a crypting program which makes given data unreadable using mixing, shifting, coding etc.

MixIt 1.2 offers you some features for an unbreakable communication via email using one time pads and password books.

To protect data, MixIt mixes a given input file with various mixing and shifting algorithms. To do so, MixIt needs a password and a level. To deprotect the mixed data, you must specify the password and level. This is like using WinZip or other archivers which can protect data too. This is made to protect data on your local disk.


To exchange such protected data MixIt offers password books which must be owned by both partners who want to exchange data. To exchange password books, MixIt offers file locking functions that can be used with the Diffie Hellman Box Model.

Like exchanging huge password books using one time pads, MixIt can create password books with random one time pads that one can lock data with these one time pads. You need the Diffie Hellman Box Model only to exchange these password books. The next messages can be simply send to your partner.

Conjury::C is a Perl Conjury with C/C++ compilers, linkers and archivers.

SYNOPSIS

c_object
Source => Isource-file>,
Directory => Idirectory>,
Includes => [ Idir1>, Idir2>, ... ],
Defines => { Ivar1> => Ival1>, Ivar2> => Ival2>, ... },
Compiler => I< compiler>,
Options => [ I< opt1>, I< opt2>, ... ],
Factors => [ I< factor1>, I< factor2>, ... ];

c_executable
Directory => I< directory>,
Name => I< output-filename>,
Order => [
Searches => [ I< dir1>, I< dir2>, ... ],
Objects => [ I< obj1>, I< obj2>, ... ],
Libraries => [ I< lib1>, I< lib2>, ...] ],
Linker => I< linker>,
Options => [ I< opt1>, I< opt2>, ... ],
Factors => [ I< factor1>, I< factors2>, ... ]

c_static_library
Directory => I< directory>,
Name => I< output-filename>,
Objects => [ I< obj1>, I< obj2>, ...],
Archiver => I< archiver>,
Options => [ I< opt1>, I< opt2>, ... ],
Factors => [ I< factor1>, I< factors2>, ... ]

c_compiler
Program => I< program>,
Options => [ I< opt1>, I< opt2>, ... ],
Journal => I< journal>,
Flag_Map => { I => I< include-flag>, D => I< define-flag>,
c => I< source-flag>, o => I< object-flag> },
Suffix_Rule => sub { my ($name) = @_; ... return $result },
Scanner => sub { my ($c_file, $args) = @_; ... return @result };

c_compiler Vendor => I< vendor>, ...

c_linker
Program => I< program>,
Options => [ I< opt1>, I< opt2>, ... ],
Journal => I< journal>,
Flag_Map => { l => I< link-flag>, L => I< search-flag>,
o => I< output-flag> },
Bind_Rule => sub { my ($lib, $bind) = @_;
... return @result },
Search_Rule => sub { my ($lib, $rule, $bind, @search) = @_;
... return @factors };

c_linker Vendor => I< vendor>, ...

c_archiver
Program => I< program>,
Options => [ I< opt1>, I< opt2>, ... ],
Journal => I< journal>,
Flag_Map => { r => I< replace-flag> };

c_archiver Vendor => I< vendor>, ...

Spells for compiling and linking C/C++ software are constructed using c_object, c_executable and c_static_library. The compiler, linker and archiver used in the resulting actions are the same compiler, linker and archiver that were used to build Perl itself, unless otherwise specified.

Specializations of the general classes of compiler, linker and archiver can be created using c_compiler, c_linker and c_archiver.