Free aws s3 software for linux

MythDora 3.0 is now using FC5 along with MythTV-0.20 all on DVD. This DVD will install on various PVR builds. A few changes have been made since the 2.32 version. Hopefully good ones. One big change is that version 3.0 now runs on an SMP kernel. Another big change is that MythDora-3.0 now uses KDE and goes onto a DVD rather than a CD. With change and additions, things just couldnt fit on a CD any longer. The ISO size isnt too much bigger, about 940mb total.
There will no longer be any need for a Unichrome version as the needed bits are now in the modular Xorg-7.0. What is now being used is a single Openchrome Via rpm from the Epia repository at washington.kelkoo.net. This should be enough to allow hardware acceleration for Epia mainboards and S3 video card users.
Please read the F.A.Q. if you have any initial questions. Also look over the README file thats located on your disk. This is where you will find instructions on certain parts of MythDora. There is also an Install Notes at the top of this page which gives you a general idea of how to set things up in mythtvsetup.
MythDora 3.0 uses an auto installer that allows your system to install only on the first hard drive and not on your remaining physical hard drives. The installer uses LVM which will allow you to add another HD to your volume group if you so choose.
For those of you new to MythDora, the easiest way to install would be to use the auto install feature. This will install every package on the disk, automatically format your disk(s), create a user mythtv, setup networking, setup MythTV etc., all on the fly. When mythtvsetup finishes, mythfilldatabase will automatically start but only if you have chosen an all-in-one setup and have a valid Data Direct subscription. XMLTV users will need to run mythfilldatabase --manual in the provided xterm screen if need be. After that a reboot will take place as this seems to install your tuner card(s) a little better.
Please be sure to make the appropriate changes in the frontend setup in order for things to work correctly. This may include sound working properly, bitrate adjustment, resolution or changing channels etc.
One thing you need to make sure of is when you install in either auto or custom, please make sure you disable selinux during install !!!
Its also recommended that you do not do an "apt-get dist-upgrade" , "apt-get upgrade" or "yum upgrade" as you run the risk of breaking something. You have been warned!!.
I really want to thank those of you who gave me feedback during the beta testing. This couldnt have been done without. I really appreciate it.
Also I want to thank one of our members here, inm8, for creating the kickass new logo for MythDora. He did an outstanding job and I dont think youll be disappointed. I also added in some more eye candy for your viewing pleasure.
Enhancements:
This is a second bugfix release to version 3.0. Hopefully the last. This is mainly to give Nvidia users the chance to install Legacy drivers for older video cards. I also included a new mythstreamtv rpm with corrected code that should allow you to kill the vlc stream now. Thanks to Jeffrey Kosowsky.
- Added older 8776 Nvidia drivers
- Corrected mythstreamtv
- Updated to latest stable kernel 2.6.18-1.2257.fc5smp
- Updated to MythTV 0.20-148
- Updated ivtv 0.8.2-123
- Added two new remotes (Nebula & Technisat)

S3cmd is a command line tool to upload, retrieve and manage data in Amazon S3. It is best suited for power users who dont fear command line. The project is also ideal for scripts, automated backups triggered from cron, etc.
Amazon S3 is a reasonably priced data storage service. Ideal for off-site backups, archiving and other data storage needs. Check out our pages about Amazon S3 to find out more.
Simple S3cmd HowTo
Register for Amazon AWS / S3
Go to Amazon S3 homepage, click on the "Sign up for web service" button in the right column and work through the registration. You will have to supply your Credit Card details in order to allow Amazon charge you for S3 usage. At the end you should posses your Access and Secret Keys
Run s3cmd --configure
You will be asked for the two keys - copy and paste them from your confirmation email or from your Amazon account page. Be careful when copying them! They are case sensitive and must be entered accurately or youll keep getting errors about invalid signatures or similar.
Run s3cmd ls to list all your buckets.
As you just started using S3 there are no buckets owned by you as of now. So the output will be empty.
Make a bucket with s3cmd mb s3://my-new-bucket-name
As mentioned above bucket names must be unique amongst _all_ users of S3. That means the simple names like "test" or "asdf" are already taken and you must make up something more original. I sometimes prefix my bucket names with my e-mail domain name (logix.cz) leading to a bucket name, for instance, logix.cz-test:
~$ s3cmd mb s3://logix.cz-test
Bucket logix.cz-test created
List your buckets again with s3cmd ls
Now you should see your freshly created bucket
~$ s3cmd ls
2007-01-19 01:41 s3://logix.cz-test
List the contents of the bucket
~$ s3cmd ls s3://logix.cz-test
Bucket logix.cz-test:
~$
Its empty, indeed.
Upload a file into the bucket
~$ s3cmd put addressbook.xml s3://logix.cz-test/addrbook.xml
File addressbook.xml stored as s3://logix.cz-test/addrbook.xml (123456 bytes)
Now we can list the bucket contents again
~$ s3cmd ls s3://logix.cz-test
Bucket logix.cz-test:
2007-01-19 01:46 120k s3://logix.cz-test/addrbook.xml
Retrieve the file back and verify that its hasnt been corrupted
~$ s3cmd get s3://logix.cz-test/addrbook.xml addressbook-2.xml
Object s3://logix.cz-test/addrbook.xml saved as addressbook-2.xml (123456 bytes)
~$ md5sum addressbook.xml addressbook-2.xml
39bcb6992e461b269b95b3bda303addf addressbook.xml
39bcb6992e461b269b95b3bda303addf addressbook-2.xml
Checksums of the original file matches the one of the retrieved one. Looks like it worked :-)
Clean up: delete the object and remove the bucket
~$ s3cmd rb s3://logix.cz-test
ERROR: S3 error: 409 (Conflict): BucketNotEmpty
Ouch, we can only remove empty buckets!
~$ s3cmd del s3://logix.cz-test/addrbook.xml
Object s3://logix.cz-test/addrbook.xml deleted
~$ s3cmd rb s3://logix.cz-test
Bucket logix.cz-test removed
Enhancements:
- Python 2.5 is not required anymore.
- Python 2.4 is now fully supported as well.

Net::Amazon::S3 is a simple, easy to use, pure Ruby implementation of the Amazon S3 REST API.

The project aims to provide a more Rubyish interface to the S3 API than other libraries and has no non-Ruby dependencies, so it’s completely platform-independent.

The easiest way to install Net::Amazon::S3 is via RubyGems:

gem install net-amazon-s3

S3OSCache project is an OSCache store implementation that uses Amazons Web Service S3 service to store the cached data. What this means is that if you are currently using oscache and storing cached objects on disk or in memory, you could easily configure this add-on to oscache and start storing your cached objects on S3.

Motivation

Youre probably asking why would you want to do this. Here is my situation... I have a website publishing system that dynamically resizes images for the user on demand. For example, it might create thumbnails or simply shrink a 2 megapixel photo to efficiently display that as a 400x300 pixel image.

Image resizing is a CPU intensive activity, especially with the Java Imaging API. From the start, I used OSCache to cache these smaller versions of the images on the app servers file system. The problem is that I can have anywhere between 2 and 7 app servers running at a time. This means that in the worst (and common) case, that image gets resized 7 times across my cluster.

I saw what could be done with OSCache storage API, so I took the Amazon S3 REST API and refactored it, since I needed to add HEAD method support and didnt need a lot else. I repackaged the REST API code so that it wont collide with the main Amazon S3 REST API jar if youre using that. The result is s3oscache

Duplicity backs directories by producing encrypted tar-format volumes and uploading them to a remote or local file server.
Because duplicity uses librsync, the incremental archives are space efficient and only record the parts of files that have changed since the last backup. Because duplicity uses GnuPG to encrypt and/or sign these archives, they will be safe from spying and/or modification by the server.
The duplicity package also includes the rdiffdir utility. Rdiffdir is an extension of librsyncs rdiff to directories---it can be used to produce signatures and deltas of directories as well as regular files. These signatures and deltas are in GNU tar format.
Main features:
Easy to use: Although duplicity is a command-line utility, the semantics are relative simply. To take a basic example, this command:
- duplicity /usr scp://host.net/target_dir
- backs up the /usr directory to the remost host host.net via scp.
Encrypted and signed archives: The archives that duplicity produces can be encrypted and signed using GnuPG, the standard for free software cryptology. The remote location will not be able to infer much about the backups other than their size and when they are uploaded. Also, if the archives are modified on the remote side, this will be detected when restoring.
Bandwidth and space efficient: Duplicity uses the rsync algorithm so only the changed parts of files are sent to the archive when doing an incremental backup. For instance, if a long log file increases by just a few lines of text, a small diff will be sent to and saved in the archive. Other backup programs may save a complete copy of the file.
Standard file format: Athough archive data will be encrypted, inside it is in standard GNU-tar format archives. A full backup contains normal tarballs, and incremental backups are tar archives of new files and the deltas from previous backups. The deltas are in the format produced by librsyncs command-line utility rdiff.
- Although you should never have to look at a duplicity archive manually, if the need should arise they can be produced and processed using GnuPG, rdiff, and tar.
Choice of remote protocol: Duplicity does not make many demands on its archive server. As long as files can be saved to, read from, listed, and deleted from a location, that location can be used as a duplicity backend. Besides increasing choice for the user, it can make a server more secure, as clients only require minimal access.
- Currently local file storage, scp/ssh, ftp, rsync, and Amazon S3 are supported, and others shouldnt be difficult to add.

Ruby/Amazon is a Ruby language library that allows programmatic access to the popular Amazon Web site via the REST (XML over HTTP) based Amazon Web Services. In addition to the original amazon.com site, the amazon.co.uk, amazon.de, amazon.fr, amazon.ca, and amazon.co.jp properties are also supported.

Ruby/Amazon library aims to wrap the grunt work of interacting with the Amazon API behind a high-level layer of Ruby, thereby making it easier to use.

Although the library is still in development, it already provides support for the vast majority of the AWS v3.1 API. For example, all forms of product search are implemented, along with the transaction details API and the remote shopping-cart API. Furthermore, advanced features such as threaded retrieval of multiple pages, object caching and determining a clients most appropriate AWS locale are all implemented. See the RDoc library documentation for more information, in particular the page about the top level Amazon module.

More features are planned for future versions, such as Amazon Web Services for Sellers.

POE::Component::Amazon::S3 is a Perl module to work with Amazon S3 using POE.

SYNOPSIS

use POE qw(Component::Amazon::S3);

POE::Component::Amazon::S3->spawn(
alias => s3,
aws_access_key_id => your S3 id,
aws_secret_access_key => your S3 key,
);

### Methods for working with buckets

# List buckets, posts back to buckets_done with the result
$kernel->post(
s3 => buckets, buckets_done,
);

# Add a bucket
$kernel->post(
s3 => add_bucket, add_bucket_done,
{
bucket => my-bucket,
}
);

# Delete a bucket, must be empty of all keys
$kernel->post(
s3 => delete_bucket, delete_bucket_done,
{
bucket => my-bucket,
}
);

# Set access control on a bucket, see below for more info about ACL
$kernel->post(
s3 => set_acl, set_acl_done,
{
bucket => my-bucket,
acl_short => public-read,
}
);

# Get the access control list for a bucket
$kernel->post(
s3 => get_acl, get_acl_done,
{
bucket => my-bucket,
}
);

### Methods for working with keys

# Add a key with inline data
$kernel->post(
s3 => add_key, add_key_done,
{
bucket => my-bucket,
key => my-inline-key,
data => testing 123,
}
);

# Add a key with data from a file
$kernel->post(
s3 => add_key, add_key_done,
{
bucket => my-bucket,
key => my-file-key,
file => /path/to/large_file,
}
);

# List some keys, used for pagination
$kernel->post(
s3 => list_bucket, list_bucket_done,
{
bucket => my-bucket,
max-keys => 10,
},
);

# List all keys, may make multiple calls internally to list_bucket
$kernel->post(
s3 => list_bucket_all, list_bucket_all_done,
{
bucket => my-bucket,
},
);

# Get a key, saving the contents in memory
$kernel->post(
s3 => get_key, get_key_done,
{
bucket => my-bucket
key => my-inline-key,
},
);

# Get a key, saving directly to a file
$kernel->post(
s3 => get_key, get_key_done,
{
bucket => my-bucket
key => my-file-key,
file => /tmp/my-file-key,
},
);

# Get only the headers for a key
$kernel->post(
s3 => head_key, head_key_done,
{
bucket => my-bucket,
key => my-inline-key,
},
);

# Delete a key
$kernel->post(
s3 => delete_key, delete_key_done,
{
bucket => my-bucket,
key => my-inline-key,
},
);

# Set access control on a key, see below for more info about ACL
$kernel->post(
s3 => set_acl, set_acl_done,
{
bucket => my-bucket,
key => my-inline-key,
acl_short => public-read,
}
);

# Get the access control list for a key
$kernel->post(
s3 => get_acl, get_acl_done,
{
bucket => my-bucket,
key => my-inline-key,
}
);

### Return values

# All methods post back to the given state with the same parameters,
# return and response. Example:

sub add_bucket_done {
my ( $kernel, $return, $response ) = @_[ KERNEL, ARG0, ARG1 ];

# $return contains only the results of the call
# $response contains the full HTTP::Response object from the call

# See individual method documentation below for details on $return
}