Free how to use winrar zip archive software for linux

Simple Page Archive is a mirror and archiving tool to copy Web pages you are interested in. The CGI script downloads all images and CSS files to preserve the mirrored Web page.
It works with the ZEUS (www.zeus.com) and Apache (www.apache.org) web servers. SPA is an simple CGI script which allows you to mirror a single web page. It stores all images and CSSs locally, so you are able to browse through the archive without the need of the original, images being availiable.
The script is dead simple to install!
1. First you need to download "Beatiful Soup" (BS) from http://www.crummy.com/software/BeautifulSoup/ which is a quite simple but very good HTML Parser (not like the one in the Python distro .. which is acutally broken). Please "install" the BS module in your site-packages directory of python.
2. Copy the "index.py" file to directory of your "web archive".
3. Edit the script and change wroot variable in Configuration section at the beginning of the script to the document root directory of your web archive (NOT the physical path on the disk!)
3.1 If you are behind a firewall and you need proxy support, add your proxy server in the Configuration section as well.
4. Make sure you have CGI support enabled in your web server.
5. Make sure index.py is being called as the default DirectoryIndex.
6. Make sure the permissions of the index.py file and the directory are set
correctly. The CGI process must be able to write to your archive directory.
7. Open a browser and try to mirror a page ;-)
Enhancements:
- Added filter support
- Output now sorted by date

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.

WormBase::Archive::Build can create archives of Wormbase releases.

SYNOPSIS

use Bio::GMOD::Admin::Archive;
my $archive = Bio::GMOD::Admin::Archive->new();

$archive->create_archive();

METHODS

Bio::GMOD::Admin::Archive->new(@options)
Create a new WormBase::Archive object for archiving WormBase releases.

The options consist largely of file system and remote paths. If none are provided, they will all be populated from the default file located on the primary WormBase server.

This is the recommended idiom as it insulates your programs from structural changes at WormBase. In this case, archives will be built in /pub/wormbase/RELEASE where RELEASE is a WSXXX release.

There are, however, at least two options that you will wish to provide:

--database_repository Full path where to store archives on your filesystem
--mysql_path Full path to the mysql data dir

See WormBase.pm for additional details on all system-dependent paths that can be overridden.

News::Archive is a Usenet news archiving package for downloading and later accessing news articles in bulk.

It can load articles laid out in INN format, retrieve them from a running news server, or just take articles one-by-one. News::Archive module is compatible with News::Web and Net::NNTP::Server, so the articles can be shared either via the Web or via NNTP.

SYNOPSIS

use News::Archive;
my $archive = new News::Archive
( basedir => /home/tskirvin/kiboze );

# Get a news article
my $article = News::Article->new(*STDIN);
my $msgid = article->header(message-id);

die "Already processed $msgidn"
if ($archive->article( $messageid ));

# Get the list of groups were supposed to be saving the article into
my @groups = split(s*,s*, $article->header(newsgroups) );
map { s/s+//g } @groups;

# Make sure were subscribed to these groups
foreach (@groups) { $archive->subscribe($_) }

# Actually save the article.
my $ret = $archive->save_article(
[ @{$article->rawheaders}, , @{$article->body} ], @groups );
$ret ? print "Accepted article $messageidn"
: print "Couldnt save article $messageidn";

News::Archive keeps several files to keep track of its archives:

active file

Keeps track of all newsgroups we are "subscribed" to and all of the information that changes regularly - the number of articles we have archived, the current first and last article numbers, etc.

Watched over with News::Active.

history database

A simple database keeping track of articles by Message-ID. Makes access by ID easy, and ensures that we dont save the same article twice. The database chosen to maintain these is user-determined.

newsgroup file

Keeps track of more static information about the newsgroups we are subscribed to - descriptions, creation dates, etc.

Watched over with News::GroupInfo.

archive directory

Directory structure of all articles, with each article saved as a single textfile within a directory structure laid out at one section of the group name per directory, such as "rec/games/mecha". Crossposts are hardlinked to other directory structures.

Articles are actually divided into sub-directories containing up to 500 articles, to avoid Unix directory size performance limitations. Individual files are thus stored in a file such as "rec/games/mecha/1.500/1".

Each newsgroup also contains overview information, watched over with
News::Overview. This overview file goes in the top of the structure,
such as "rec/games/mecha/.overview".

You may note that these files are very similar to how INN does its work. This is intentional - this package is meant to act in many ways like a lighter-weight INN.

Usage:

Global Variables

The following variables are set within News::Archive, and are global throughout all invocations.

$News::Active::DEBUG
Default value for "debug()" in new objects.

$News::Active::HOSTNAME
Default value for "hostname()" in new objects. Obtained using
"Sys::Hostname::hostname()".

$News::Active::HASH
The number of articles to keep in each directory. Default is 500;
change this at your own peril, since things may get screwed up later
if you change it after archiving any articles!

Archive::Rar is a interface with the rar command.

SYNOPSIS

use Archive::Rar;
my $rar =new Archive::Rar();
$rar->Add(
-size => $size_of_parts,
-archive => $archive_filename,
-files => @list_of_files,
);

This is a module for the handling of rar archives.

Locates the rar command (from PATH or from regedit for Win32) and encapsulate it to create, extract and list rar archives.

At the moment these methods are implemented:

new()

Returns a new Rar object. You can pass defaults options.

Add(%options)

Add file to an archive.

Extract(%options)

Extract the contains of an archive.

List(%options)

Fill the list variable of the object whith the index of an archive.

OPTIONS

-archive

Archive filename.

-files

List of files to add. You can use a scalar value or an array reference.

-quiet

No output for the rar command if True.

-sfx

Create self-extracting archive.

-size

Size of the parts in bytes.

-verbose

Level of verbosity.

Kenzip is a frontend for p7-zip.

You can create password protected 7z and zip archives with this python-qt3 utility

(Unfortunately ark does not support password protected archives.) KenZip has feasible dependency, you can install it to almost any existing distro.

It has been tested on OpenSuSE 10.2, Debian testing 2006.01. and Kanotix 2006-01-RC4 using the distros python qt3 package.

Do not forget to install python qt3 and p7-zip before! Prefer the distros package from repository for Debian based distributions, and the binary installer for other linux distros.

PloneFilesZip allows your visitor download the files and images from folders in a single ZIP file.
loneFilesZip provides a new document action in all folderish contents (ATFolder, ...) that let the user download files (and images) contained in the fields of any AT based content (ATContentTypes and others) in that folder.
PloneFilesZip works - out of the box - with any content type which schema has a FileField, an ImageField or any field that acts like a FileField, as the AttachmentField.
Customizing (site manager)
.Choose the content types that can profide files to the user among compatible types.
.Add Dublin Core information (RDF formatted) about the contents in the ZIP archive.
.Tweak the condition/permission to let the user download.
.Customizing (content type developers)
Some content types have schemas that do not "show" the compatible fields through the standard AT API. In order to let these content types provides files in a ZIP archive, developers can add type adapter classes in the PloneFilesZip types registry. An adapter for PloneArticle is less than 20 Python lines.
Some custom field types may provide files. In order to let the content types built with such fields provide files to a ZIP archive, developers can add field adapter classes in the PloneFilesZip fields registry.
Enhancements:
- Fix a bug in file retrieving. Append arg (full=True) while creating BaseUnit to make sure we get the entire file and not a chunk file
- Fix a bug on DeepZipStructurePolicy:getZipFilePath (add **kwargs on method)