restoring
Sponsored Links
Sponsored Links
Secleted [ 0 ] software to compare
Results 1 - 15 of about 285
Dump/Restore 0.4b41
Dump/Restore are utilities to dump and restore an ext2 partition. more>>
Dump/Restore project examines files in a filesystem, determines which ones need to be backed up, and copies those files to a specified disk, tape or other storage medium.
Subsequent incremental backups can then be layered on top of the full backup.
The restore command performs the inverse function of dump; it can restore a full backup of a filesystem.
Single files and directory subtrees may also be restored from full or partial backups in interractive mode.
Enhancements:
- This is a maintenance release, fixing a few bugs related to the restoration of ACLs and huge backups (symtab over 2GB in size).
- The directory hash indexing has been made optional since it may require too much memory when restoring huge backups.
<<lessSubsequent incremental backups can then be layered on top of the full backup.
The restore command performs the inverse function of dump; it can restore a full backup of a filesystem.
Single files and directory subtrees may also be restored from full or partial backups in interractive mode.
Enhancements:
- This is a maintenance release, fixing a few bugs related to the restoration of ACLs and huge backups (symtab over 2GB in size).
- The directory hash indexing has been made optional since it may require too much memory when restoring huge backups.
Download (0.28MB)
Added: 2006-01-02 License: BSD License Price:
1396 downloads
restore CD/DVD 1.06
restore CD/DVD allows you to create a CD or DVD that can be used to backup whole hard disk partitions from any OS. more>>
restore CD/DVD allows you to create a CD or DVD that can be used to backup whole hard disk partitions from any OS and restore them without user interaction.
restore CD/DVD can be used in a manner similar to vendor-provided rescue CDs included with new computers, but with all your own settings.
<<lessrestore CD/DVD can be used in a manner similar to vendor-provided rescue CDs included with new computers, but with all your own settings.
Download (13.3MB)
Added: 2006-01-04 License: GPL (GNU General Public License) Price:
1396 downloads
glucopy-glurestore 1.0
glucopy-glurestore is a set of scripts for copying and restoring a fully functional GNU/Linux (or other Unix-like) system. more>>
glucopy-glurestore is a set of scripts for copying and restoring a fully functional GNU/Linux (or other Unix-like) system.
The glucopy script will back up all system content (system and user files), while the glurestore script will partition and format an identical system, restore the system and user files, and make the system bootable.
glucopy-glurestore scripts are included in the HTML documentation.
The back-up should (ideally) be made while the system is not running, which usually means that you need to boot with a rescue system disk. A number of suitable floppy or CD-based system images can be downloaded from the net or, better, included in your distributions boot options. Make sure that this rescue system supports the type of disks in your target system (SATA/SCSI or IDE).
The following script will get partition information in a form that can be used to restore the system on new disks and will then collect the working system files in one (or more) compressed tar balls.
The sfdisk program is used for getting partition information (-d option). Take a look at sys_partitions.txt after the glucopy.sh script has finished.
In this application it is considered that all Master Boot Record (MBR) information will be overwritten by the partitioning and boot loader programs. If you need a copy of all or parts of the MBR, however, dd is your friend.
System directories that contain transient information (e.g. /proc, /sys) are not copied. Directories or individual files containing unwanted information can be excluded using tars –exclude=/directory/file option.
#!/bin/sh
###########################
# glucopy.sh
#
# Creates the /glucopy directory
# Copies partition information in sys_partitions.txt
# Optionally makes a copy of the MBR in mbr.bin
# Copies working GNU/Linux system to .tgz files
#
# USAGE:
# Boot system with a rescue CD or any bootable CD
# that supports your type of disks (SATA/SCSI or IDE).
# run the back-up script: ./glucopy.sh
#
# In this example the system is on /dev/sda
# /dev/sda1 is a small partition with HW manufacturer utilities
# /dev/sda2 has system root (/) -> mounted to /mnt
# /dev/sda3 is a spare (blank) partition
# /dev/sda4 has home (/home) and space to hold
# the information to be copied -> mounted to /mnt2
#
# 061116 jp/dm
###########################
# Change the following to reflect the place where your system root (/)
# and the home directories (/home/*) are mounted
mkdir /tmp/mnt1
mkdir /tmp/mnt2
mount /dev/sda2 /tmp/mnt1
mount /dev/sda4 /tmp/mnt2
# The directory to hold the system copy is placed on the larger partition
mkdir /tmp/mnt2/glucopy
# Change to the working directory
cd /tmp/mnt2/glucopy
# Optionally copy MBR information
#dd if=/dev/sda of=mbr.bin bs=512 count=1
# Copy partition information
/sbin/sfdisk -d /dev/sda > sys_partitions.txt
# Make tarballs
tar -C /tmp/mnt1 -cvzf syscopy.tgz boot bin etc lib media opt root sbin usr var dev
# Move up a level
cd ..
# here we are under the /home directory level
# notice that --exclude will exclude anything that matches a _pattern_
# the glucopy directory will still be created in the tarball
tar -cvzf ./glucopy/homecopy.tgz * --exclude=glucopy/*
# Copy the backup/restore scripts (here under root /), and the sfdisk program, as well
cp /glucopy.sh ./glucopy
cp /glurestore.sh ./glucopy
cp /sbin/sfdisk ./glucopy
# Notify user
echo -e “glucopy: finished a”
<<lessThe glucopy script will back up all system content (system and user files), while the glurestore script will partition and format an identical system, restore the system and user files, and make the system bootable.
glucopy-glurestore scripts are included in the HTML documentation.
The back-up should (ideally) be made while the system is not running, which usually means that you need to boot with a rescue system disk. A number of suitable floppy or CD-based system images can be downloaded from the net or, better, included in your distributions boot options. Make sure that this rescue system supports the type of disks in your target system (SATA/SCSI or IDE).
The following script will get partition information in a form that can be used to restore the system on new disks and will then collect the working system files in one (or more) compressed tar balls.
The sfdisk program is used for getting partition information (-d option). Take a look at sys_partitions.txt after the glucopy.sh script has finished.
In this application it is considered that all Master Boot Record (MBR) information will be overwritten by the partitioning and boot loader programs. If you need a copy of all or parts of the MBR, however, dd is your friend.
System directories that contain transient information (e.g. /proc, /sys) are not copied. Directories or individual files containing unwanted information can be excluded using tars –exclude=/directory/file option.
#!/bin/sh
###########################
# glucopy.sh
#
# Creates the /glucopy directory
# Copies partition information in sys_partitions.txt
# Optionally makes a copy of the MBR in mbr.bin
# Copies working GNU/Linux system to .tgz files
#
# USAGE:
# Boot system with a rescue CD or any bootable CD
# that supports your type of disks (SATA/SCSI or IDE).
# run the back-up script: ./glucopy.sh
#
# In this example the system is on /dev/sda
# /dev/sda1 is a small partition with HW manufacturer utilities
# /dev/sda2 has system root (/) -> mounted to /mnt
# /dev/sda3 is a spare (blank) partition
# /dev/sda4 has home (/home) and space to hold
# the information to be copied -> mounted to /mnt2
#
# 061116 jp/dm
###########################
# Change the following to reflect the place where your system root (/)
# and the home directories (/home/*) are mounted
mkdir /tmp/mnt1
mkdir /tmp/mnt2
mount /dev/sda2 /tmp/mnt1
mount /dev/sda4 /tmp/mnt2
# The directory to hold the system copy is placed on the larger partition
mkdir /tmp/mnt2/glucopy
# Change to the working directory
cd /tmp/mnt2/glucopy
# Optionally copy MBR information
#dd if=/dev/sda of=mbr.bin bs=512 count=1
# Copy partition information
/sbin/sfdisk -d /dev/sda > sys_partitions.txt
# Make tarballs
tar -C /tmp/mnt1 -cvzf syscopy.tgz boot bin etc lib media opt root sbin usr var dev
# Move up a level
cd ..
# here we are under the /home directory level
# notice that --exclude will exclude anything that matches a _pattern_
# the glucopy directory will still be created in the tarball
tar -cvzf ./glucopy/homecopy.tgz * --exclude=glucopy/*
# Copy the backup/restore scripts (here under root /), and the sfdisk program, as well
cp /glucopy.sh ./glucopy
cp /glurestore.sh ./glucopy
cp /sbin/sfdisk ./glucopy
# Notify user
echo -e “glucopy: finished a”
Download (0.14MB)
Added: 2006-12-07 License: (FDL) GNU Free Documentation License Price:
1051 downloads
Storable 2.16
Storable package contains persistence for Perl data structures. more>>
Storable package contains persistence for Perl data structures.
SYNOPSIS
use Storable;
store %table, file;
$hashref = retrieve(file);
use Storable qw(nstore store_fd nstore_fd freeze thaw dclone);
# Network order
nstore %table, file;
$hashref = retrieve(file); # There is NO nretrieve()
# Storing to and retrieving from an already opened file
store_fd @array, *STDOUT;
nstore_fd %table, *STDOUT;
$aryref = fd_retrieve(*SOCKET);
$hashref = fd_retrieve(*SOCKET);
# Serializing to memory
$serialized = freeze %table;
%table_clone = %{ thaw($serialized) };
# Deep (recursive) cloning
$cloneref = dclone($ref);
# Advisory locking
use Storable qw(lock_store lock_nstore lock_retrieve)
lock_store %table, file;
lock_nstore %table, file;
$hashref = lock_retrieve(file);
The Storable package brings persistence to your Perl data structures containing SCALAR, ARRAY, HASH or REF objects, i.e. anything that can be conveniently stored to disk and retrieved at a later time.
It can be used in the regular procedural way by calling store with a reference to the object to be stored, along with the file name where the image should be written.
The routine returns undef for I/O problems or other internal error, a true value otherwise. Serious errors are propagated as a die exception.
To retrieve data stored to disk, use retrieve with a file name. The objects stored into that file are recreated into memory for you, and a reference to the root object is returned. In case an I/O error occurs while reading, undef is returned instead. Other serious errors are propagated via die.
Since storage is performed recursively, you might want to stuff references to objects that share a lot of common data into a single array or hash table, and then store that object. That way, when you retrieve back the whole thing, the objects will continue to share what they originally shared.
At the cost of a slight header overhead, you may store to an already opened file descriptor using the store_fd routine, and retrieve from a file via fd_retrieve. Those names arent imported by default, so you will have to do that explicitly if you need those routines. The file descriptor you supply must be already opened, for read if youre going to retrieve and for write if you wish to store.
store_fd(%table, *STDOUT) || die "cant store to stdoutn";
$hashref = fd_retrieve(*STDIN);
You can also store data in network order to allow easy sharing across multiple platforms, or when storing on a socket known to be remotely connected. The routines to call have an initial n prefix for network, as in nstore and nstore_fd. At retrieval time, your data will be correctly restored so you dont have to know whether youre restoring from native or network ordered data. Double values are stored stringified to ensure portability as well, at the slight risk of loosing some precision in the last decimals.
When using fd_retrieve, objects are retrieved in sequence, one object (i.e. one recursive tree) per associated store_fd.
If youre more from the object-oriented camp, you can inherit from Storable and directly store your objects by invoking store as a method. The fact that the root of the to-be-stored tree is a blessed reference (i.e. an object) is special-cased so that the retrieve does not provide a reference to that object but rather the blessed object reference itself. (Otherwise, youd get a reference to that blessed object).
<<lessSYNOPSIS
use Storable;
store %table, file;
$hashref = retrieve(file);
use Storable qw(nstore store_fd nstore_fd freeze thaw dclone);
# Network order
nstore %table, file;
$hashref = retrieve(file); # There is NO nretrieve()
# Storing to and retrieving from an already opened file
store_fd @array, *STDOUT;
nstore_fd %table, *STDOUT;
$aryref = fd_retrieve(*SOCKET);
$hashref = fd_retrieve(*SOCKET);
# Serializing to memory
$serialized = freeze %table;
%table_clone = %{ thaw($serialized) };
# Deep (recursive) cloning
$cloneref = dclone($ref);
# Advisory locking
use Storable qw(lock_store lock_nstore lock_retrieve)
lock_store %table, file;
lock_nstore %table, file;
$hashref = lock_retrieve(file);
The Storable package brings persistence to your Perl data structures containing SCALAR, ARRAY, HASH or REF objects, i.e. anything that can be conveniently stored to disk and retrieved at a later time.
It can be used in the regular procedural way by calling store with a reference to the object to be stored, along with the file name where the image should be written.
The routine returns undef for I/O problems or other internal error, a true value otherwise. Serious errors are propagated as a die exception.
To retrieve data stored to disk, use retrieve with a file name. The objects stored into that file are recreated into memory for you, and a reference to the root object is returned. In case an I/O error occurs while reading, undef is returned instead. Other serious errors are propagated via die.
Since storage is performed recursively, you might want to stuff references to objects that share a lot of common data into a single array or hash table, and then store that object. That way, when you retrieve back the whole thing, the objects will continue to share what they originally shared.
At the cost of a slight header overhead, you may store to an already opened file descriptor using the store_fd routine, and retrieve from a file via fd_retrieve. Those names arent imported by default, so you will have to do that explicitly if you need those routines. The file descriptor you supply must be already opened, for read if youre going to retrieve and for write if you wish to store.
store_fd(%table, *STDOUT) || die "cant store to stdoutn";
$hashref = fd_retrieve(*STDIN);
You can also store data in network order to allow easy sharing across multiple platforms, or when storing on a socket known to be remotely connected. The routines to call have an initial n prefix for network, as in nstore and nstore_fd. At retrieval time, your data will be correctly restored so you dont have to know whether youre restoring from native or network ordered data. Double values are stored stringified to ensure portability as well, at the slight risk of loosing some precision in the last decimals.
When using fd_retrieve, objects are retrieved in sequence, one object (i.e. one recursive tree) per associated store_fd.
If youre more from the object-oriented camp, you can inherit from Storable and directly store your objects by invoking store as a method. The fact that the root of the to-be-stored tree is a blessed reference (i.e. an object) is special-cased so that the retrieve does not provide a reference to that object but rather the blessed object reference itself. (Otherwise, youd get a reference to that blessed object).
Download (0.17MB)
Added: 2007-05-22 License: Perl Artistic License Price:
885 downloads
KopeteNowListening 0.2.2
KopeteNowListening is an amarok script, a complete rewrite, but is based on many ideas from others. more>>
KopeteNowListening is an Amarok script, a complete rewrite, but is based on many ideas from others.
KopeteNowListening will update Kopete avatar, away message and away status based on the current playing song. The configurations are made via kdialog and its all written in bash script.
Feel free to send me ideas and opinions about this one.
Enhancements:
- Fix a bug that restore default [photo, nickname, away] msg even when configured to not use theses settings
<<lessKopeteNowListening will update Kopete avatar, away message and away status based on the current playing song. The configurations are made via kdialog and its all written in bash script.
Feel free to send me ideas and opinions about this one.
Enhancements:
- Fix a bug that restore default [photo, nickname, away] msg even when configured to not use theses settings
Download (0.020MB)
Added: 2006-12-22 License: GPL (GNU General Public License) Price:
1036 downloads
Firefox for Linux 2.0.0.6
Mozilla Firefox 2 for Linux version. more>> Mozilla Firefox is a fast, full-featured Web browser that makes browsing more efficient than ever before. Firefox includes pop-up blocking; a tab-browsing; integrated Google searching; simplified privacy controls that let you cover your tracks more effectively; a streamlined browser window that shows you more of the page than any other browser; and a number of additional features that work with you to help you get the most out of your time online.
Session Restore
Losing your place while youre doing things on the Web is a pain. Now, with Session Restore, if Firefox has to restart or closes when it comes back youll pick up exactly where you left off. The windows and tabs you were using, the text you typed into forms, and the in-progress downloads you had running will all be restored. You can even set Firefox 2 to always restore your previous session instead of loading a home page, so youll never lose your place again.
Web Feeds (RSS)
What do news headlines, indie rock podcasts, and pictures of kittens have in common? Theyre all things that you can subscribe to with Web feeds. Firefox 2 gives you full control over Web feeds, showing you a preview and letting you choose how you want to subscribe. You can use a Firefox Live Bookmark, or a feed reader that youve installed on your computer, or through a Web service such as My Yahoo!, Bloglines or Google Reader.
Firefox for Linux System Requirements
Please note that Linux distributors may provide packages for your distribution which have different requirements.
Linux kernel - 2.2.14 with the following libraries or packages minimums:
glibc 2.3.2
gtk+2.0
XFree86-3.3.6
fontconfig (also known as xft)
libstdc++5
Thunderbird has been tested on Linux Fedora Core 4<<less
Download (9.22MB)
Added: 2009-04-18 License: Freeware Price: Free
213 downloads
RetrospeKt 0.3
RetrospeKt is my attempt to make working with backups easier and more intuitive. more>>
RetrospeKt is my attempt to make working with backups easier and more intuitive. The project is inspired by Apples "Time machine" backup system and is based on rsnapshot backup script. With Retrospect you can easily browse your folders (in konqueror) as they were at any previous backup point. A simple konqueror service menu entries are also provided for:
- restoring files from backups
- comparing any two versions of a text file with the excellent Kompare (see exactly what you changed and possibly un-apply those changes)
- browsing all the versions of the selected file
- finding all the deleted files in the current directory
- listing all the changes made on the selected file/directory
NOTE: You have to have a working rsnapshot for this script to work.
Enhancements:
- name changed to RetrospeKt because, apparently, there already is a Retrospect backup software for MacOSX
- Cosmetic changes in the Journal
- installation script added
- RetrospeKt autoconfiguration
<<less- restoring files from backups
- comparing any two versions of a text file with the excellent Kompare (see exactly what you changed and possibly un-apply those changes)
- browsing all the versions of the selected file
- finding all the deleted files in the current directory
- listing all the changes made on the selected file/directory
NOTE: You have to have a working rsnapshot for this script to work.
Enhancements:
- name changed to RetrospeKt because, apparently, there already is a Retrospect backup software for MacOSX
- Cosmetic changes in the Journal
- installation script added
- RetrospeKt autoconfiguration
Download (0.017MB)
Added: 2007-05-10 License: GPL (GNU General Public License) Price:
897 downloads
confstore 0.5.4
Confstore is a configuration backup utility. more>>
Confstore is a configuration backup utility. Confstore scans your system for all recognised configuration files and then stores them in a archive. Confstore can also restore configuration from a previously created archive.
<<less Download (0.023MB)
Added: 2005-10-04 License: GPL (GNU General Public License) Price:
1480 downloads
Partition Image 0.6.6
Partition Image is a Linux/UNIX utility which saves partitions in many formats. more>>
Partition Image application is a Linux/UNIX utility which saves partitions in many formats (see below) to an image file.
The image file can be compressed in the GZIP/BZIP2 formats to save disk space, and split into multiple files to be copied on removable floppies (ZIP for example); partitions can be saved across the network since version 0.6.0.
Partition Image will only copy data from the used portions of the partition. For speed and efficiency, free blocks are not written to the image file.
This is unlike the dd command, which also copies empty blocks. Partition Image also works for large, very full partitions. For example, a full 1 GB partition can be compressed with gzip down to 400MB.
This is very useful to save partitions to an image in some cases:
- First you can restore your linux partition if there is a problem (virus, file system errors, manipulation error) . When you have a problem, you just have to restore the partition, and after 10 minutes, you have the original partition. You can write the image to a CD-R if you dont want the image to use hard-disk space.
- This utility can be used to install many identical PCs. For example, if you buy 50 PCs, with the same hardware, and you want to install the same linux systems on all 50 PCs, you will save a lot of time. Indeed, you just have to install on the first PC and create an image from it. For the 49 others, you can use the image file and Partition Images restore function.
<<lessThe image file can be compressed in the GZIP/BZIP2 formats to save disk space, and split into multiple files to be copied on removable floppies (ZIP for example); partitions can be saved across the network since version 0.6.0.
Partition Image will only copy data from the used portions of the partition. For speed and efficiency, free blocks are not written to the image file.
This is unlike the dd command, which also copies empty blocks. Partition Image also works for large, very full partitions. For example, a full 1 GB partition can be compressed with gzip down to 400MB.
This is very useful to save partitions to an image in some cases:
- First you can restore your linux partition if there is a problem (virus, file system errors, manipulation error) . When you have a problem, you just have to restore the partition, and after 10 minutes, you have the original partition. You can write the image to a CD-R if you dont want the image to use hard-disk space.
- This utility can be used to install many identical PCs. For example, if you buy 50 PCs, with the same hardware, and you want to install the same linux systems on all 50 PCs, you will save a lot of time. Indeed, you just have to install on the first PC and create an image from it. For the 49 others, you can use the image file and Partition Images restore function.
Download (0.52MB)
Added: 2007-08-11 License: GPL (GNU General Public License) Price:
815 downloads
StoreBackup 1.19
StoreBackup is a backup utility that stores files on other disks. more>>
StoreBackup is a backup utility that stores files on other disks.
It includes several optimizations that reduce the disk space needed and improve performance, and unifies the advantages of traditional full and incremental backups.
Depending on its contents, every file is stored only once on disk. It includes tools for analyzing backup data and restoring. Once archived, files are accessible by mounting filesystems (locally, or via Samba or NFS). It is easy to install and configure.
<<lessIt includes several optimizations that reduce the disk space needed and improve performance, and unifies the advantages of traditional full and incremental backups.
Depending on its contents, every file is stored only once on disk. It includes tools for analyzing backup data and restoring. Once archived, files are accessible by mounting filesystems (locally, or via Samba or NFS). It is easy to install and configure.
Download (0.096MB)
Added: 2005-09-26 License: GPL (GNU General Public License) Price:
1488 downloads
Collink 0.5
Collink is a link extractor/collector based on Qt library. more>>
Collink is a link extractor/collector based on Qt library. It saves list of links as plain text or better as a Downloader for X list giving different names for files to save.
You can filter links by filename extension and via a Qt regular expression. It is probably an unuseful utility if you do not manage your downloads with D4X, use it as a power user or if you know wget ;)
Enhancements:
- save / restore last filter
- 0.5 release
<<lessYou can filter links by filename extension and via a Qt regular expression. It is probably an unuseful utility if you do not manage your downloads with D4X, use it as a power user or if you know wget ;)
Enhancements:
- save / restore last filter
- 0.5 release
Download (0.52MB)
Added: 2006-07-05 License: GPL (GNU General Public License) Price:
1207 downloads
PApp::Storable 1.2
Storable module is a persistence for Perl data structures. more>>
Storable module is a persistence for Perl data structures.
SYNOPSIS
use Storable;
store %table, file;
$hashref = retrieve(file);
use Storable qw(nstore store_fd nstore_fd freeze thaw dclone);
# Network order
nstore %table, file;
$hashref = retrieve(file); # There is NO nretrieve()
# Storing to and retrieving from an already opened file
store_fd @array, *STDOUT;
nstore_fd %table, *STDOUT;
$aryref = fd_retrieve(*SOCKET);
$hashref = fd_retrieve(*SOCKET);
# Serializing to memory
$serialized = freeze %table;
%table_clone = %{ thaw($serialized) };
# Deep (recursive) cloning
$cloneref = dclone($ref);
# Advisory locking
use Storable qw(lock_store lock_nstore lock_retrieve)
lock_store %table, file;
lock_nstore %table, file;
$hashref = lock_retrieve(file);
The Storable package brings persistence to your Perl data structures containing SCALAR, ARRAY, HASH or REF objects, i.e. anything that can be conveniently stored to disk and retrieved at a later time.
It can be used in the regular procedural way by calling store with a reference to the object to be stored, along with the file name where the image should be written.
The routine returns undef for I/O problems or other internal error, a true value otherwise. Serious errors are propagated as a die exception.
To retrieve data stored to disk, use retrieve with a file name. The objects stored into that file are recreated into memory for you, and a reference to the root object is returned. In case an I/O error occurs while reading, undef is returned instead. Other serious errors are propagated via die.
Since storage is performed recursively, you might want to stuff references to objects that share a lot of common data into a single array or hash table, and then store that object. That way, when you retrieve back the whole thing, the objects will continue to share what they originally shared.
At the cost of a slight header overhead, you may store to an already opened file descriptor using the store_fd routine, and retrieve from a file via fd_retrieve. Those names arent imported by default, so you will have to do that explicitly if you need those routines. The file descriptor you supply must be already opened, for read if youre going to retrieve and for write if you wish to store.
store_fd(%table, *STDOUT) || die "cant store to stdoutn";
$hashref = fd_retrieve(*STDIN);
You can also store data in network order to allow easy sharing across multiple platforms, or when storing on a socket known to be remotely connected. The routines to call have an initial n prefix for network, as in nstore and nstore_fd. At retrieval time, your data will be correctly restored so you dont have to know whether youre restoring from native or network ordered data. Double values are stored stringified to ensure portability as well, at the slight risk of loosing some precision in the last decimals.
When using fd_retrieve, objects are retrieved in sequence, one object (i.e. one recursive tree) per associated store_fd.
If youre more from the object-oriented camp, you can inherit from Storable and directly store your objects by invoking store as a method. The fact that the root of the to-be-stored tree is a blessed reference (i.e. an object) is special-cased so that the retrieve does not provide a reference to that object but rather the blessed object reference itself. (Otherwise, youd get a reference to that blessed object).
<<lessSYNOPSIS
use Storable;
store %table, file;
$hashref = retrieve(file);
use Storable qw(nstore store_fd nstore_fd freeze thaw dclone);
# Network order
nstore %table, file;
$hashref = retrieve(file); # There is NO nretrieve()
# Storing to and retrieving from an already opened file
store_fd @array, *STDOUT;
nstore_fd %table, *STDOUT;
$aryref = fd_retrieve(*SOCKET);
$hashref = fd_retrieve(*SOCKET);
# Serializing to memory
$serialized = freeze %table;
%table_clone = %{ thaw($serialized) };
# Deep (recursive) cloning
$cloneref = dclone($ref);
# Advisory locking
use Storable qw(lock_store lock_nstore lock_retrieve)
lock_store %table, file;
lock_nstore %table, file;
$hashref = lock_retrieve(file);
The Storable package brings persistence to your Perl data structures containing SCALAR, ARRAY, HASH or REF objects, i.e. anything that can be conveniently stored to disk and retrieved at a later time.
It can be used in the regular procedural way by calling store with a reference to the object to be stored, along with the file name where the image should be written.
The routine returns undef for I/O problems or other internal error, a true value otherwise. Serious errors are propagated as a die exception.
To retrieve data stored to disk, use retrieve with a file name. The objects stored into that file are recreated into memory for you, and a reference to the root object is returned. In case an I/O error occurs while reading, undef is returned instead. Other serious errors are propagated via die.
Since storage is performed recursively, you might want to stuff references to objects that share a lot of common data into a single array or hash table, and then store that object. That way, when you retrieve back the whole thing, the objects will continue to share what they originally shared.
At the cost of a slight header overhead, you may store to an already opened file descriptor using the store_fd routine, and retrieve from a file via fd_retrieve. Those names arent imported by default, so you will have to do that explicitly if you need those routines. The file descriptor you supply must be already opened, for read if youre going to retrieve and for write if you wish to store.
store_fd(%table, *STDOUT) || die "cant store to stdoutn";
$hashref = fd_retrieve(*STDIN);
You can also store data in network order to allow easy sharing across multiple platforms, or when storing on a socket known to be remotely connected. The routines to call have an initial n prefix for network, as in nstore and nstore_fd. At retrieval time, your data will be correctly restored so you dont have to know whether youre restoring from native or network ordered data. Double values are stored stringified to ensure portability as well, at the slight risk of loosing some precision in the last decimals.
When using fd_retrieve, objects are retrieved in sequence, one object (i.e. one recursive tree) per associated store_fd.
If youre more from the object-oriented camp, you can inherit from Storable and directly store your objects by invoking store as a method. The fact that the root of the to-be-stored tree is a blessed reference (i.e. an object) is special-cased so that the retrieve does not provide a reference to that object but rather the blessed object reference itself. (Otherwise, youd get a reference to that blessed object).
Download (0.39MB)
Added: 2007-08-02 License: Perl Artistic License Price:
813 downloads
Magic Settings Wizard 0.1
Magic Settings Wizard is designed to quickly and easily restore or backup your favorite applications settings. more>>
Magic Settings Wizard is designed to quickly and easily restore or backup your favorite applications settings.
Magic Settings Wizard can backup/restore through an FTP location used as a storage medium.
Main features:
- backup or restore applications settings : select which ones from a list.
- personal home dir is automatically detected by default, but another directory can be specified.
- communicates with a FTP server specified by the user.
- FTP settings may be saved in a config file.
- a FTP directory may be created from the interface if needed.
- add your own applications settings definitions if yours dont exist in the database (edit settings_definitions.py).
<<lessMagic Settings Wizard can backup/restore through an FTP location used as a storage medium.
Main features:
- backup or restore applications settings : select which ones from a list.
- personal home dir is automatically detected by default, but another directory can be specified.
- communicates with a FTP server specified by the user.
- FTP settings may be saved in a config file.
- a FTP directory may be created from the interface if needed.
- add your own applications settings definitions if yours dont exist in the database (edit settings_definitions.py).
Download (0.015MB)
Added: 2006-01-24 License: GPL (GNU General Public License) Price:
1374 downloads
Etcsvn 0.2.1
Etcsvn is a command line program for managing system configurations in subversion. more>>
Etcsvn is a command line program for managing system configurations in subversion. Etcsvn doesnt make a working copy out of your /etc, but uses a temporary workspace. Etcsvn will preserve ownership/permissions of the files being tracked.
Suppose you want to keep track of important config files on a system in a subversion repository. There are a few problems with using svn directly. One problem is that you need to keep track of ownership and permission modes of files and directories that you are tracking. It is somewhat difficult to manage the repository without access to a working copy, but a working copy is twice as big as what it works on. Also there is the possibility that you want to track some files in /var or somewhere else.
Etcsvn tries to provide a simple command line interface to manage files on you system. What it does is make a temporary working copy on the system. Etcsvn must be run as root, and it sets a umask of 077 before creating any file or directory. This makes the working copy as secure as possible. This is also true when restoring files, as the ownership and permissions are set after the file is created.
I am trying to make etcsvn a bridge between your system and the working copy. The goal is to provide only what is necessary to aid a system admin in being able to edit system configuration files in a convenient manner with tools that may not be available on the system your configuring.
Version restrictions:
- I am currently working on getting etcsvn to handle symbolic links. I am also adding an option to track directories recursively.
- There is no revision support yet.
- There is should be a little work done on the repository layout. It should be possible to place many systems in one repository, or have separate repositories for clients, networks, etc.
- Etcsvn makes no attempt to authenticate to your repository. This will probably not change anytime soon, because I feel that it should be the job of the script or administrator to handle this.
- Currently there needs to be a ini style config file in the root of your repository named "etcsvn.conf". There is only one section used in this file currently, and it is called "main". In the "main" section there is only one option supported, and it is called "files". The "files" option is a list of absolute path files separated with newlines.
<<lessSuppose you want to keep track of important config files on a system in a subversion repository. There are a few problems with using svn directly. One problem is that you need to keep track of ownership and permission modes of files and directories that you are tracking. It is somewhat difficult to manage the repository without access to a working copy, but a working copy is twice as big as what it works on. Also there is the possibility that you want to track some files in /var or somewhere else.
Etcsvn tries to provide a simple command line interface to manage files on you system. What it does is make a temporary working copy on the system. Etcsvn must be run as root, and it sets a umask of 077 before creating any file or directory. This makes the working copy as secure as possible. This is also true when restoring files, as the ownership and permissions are set after the file is created.
I am trying to make etcsvn a bridge between your system and the working copy. The goal is to provide only what is necessary to aid a system admin in being able to edit system configuration files in a convenient manner with tools that may not be available on the system your configuring.
Version restrictions:
- I am currently working on getting etcsvn to handle symbolic links. I am also adding an option to track directories recursively.
- There is no revision support yet.
- There is should be a little work done on the repository layout. It should be possible to place many systems in one repository, or have separate repositories for clients, networks, etc.
- Etcsvn makes no attempt to authenticate to your repository. This will probably not change anytime soon, because I feel that it should be the job of the script or administrator to handle this.
- Currently there needs to be a ini style config file in the root of your repository named "etcsvn.conf". There is only one section used in this file currently, and it is called "main". In the "main" section there is only one option supported, and it is called "files". The "files" option is a list of absolute path files separated with newlines.
Download (0.007MB)
Added: 2005-09-28 License: GPL (GNU General Public License) Price:
1487 downloads
DHTML Windowing Toolkit 0.2
DHTML Windowing Toolkit is a cross-browser JavaScript library for the creation of inline DHTML windows to contain content. more>>
DHTML Windowing Toolkit is a cross-browser JavaScript library for the creation of inline DHTML windows to contain content; windows that can be opened, closed, moved, and resized much like native windows.
Enhancements:
- Window objects can be created with the following features: open, close, minimize, restore, move, and resize.
- The following browsers are supported: Microsoft Internet Explorer, Mozilla Firefox, Opera, and Konqueror.
<<lessEnhancements:
- Window objects can be created with the following features: open, close, minimize, restore, move, and resize.
- The following browsers are supported: Microsoft Internet Explorer, Mozilla Firefox, Opera, and Konqueror.
Download (0.064MB)
Added: 2006-08-22 License: GPL (GNU General Public License) Price:
1160 downloads
Secleted [ 0 ] software to compare
Copyright Notice:
Software piracy is theft, Using crack, password, serial numbers, registration codes, key generators is illegal and prevent future software development. The above restoring search only lists software in full, demo and trial versions for free download. Download links are directly from our mirror sites or publisher sites, torrent files or links from rapidshare.com, yousendit.com or megaupload.com are not allowed
