Free amiga smart filesystem software for linux

SSH Filesystem is a filesystem client based on the SSH File Transfer Protocol. Since most SSH servers already support this protocol it is very easy to set up: i.e. on the server side theres nothing to do. On the client side mounting the filesystem is as easy as logging into the server with ssh.
The idea of sshfs was taken from the SSHFS filesystem distributed with LUFS, which I found very useful. There were some limitations of that codebase, so I rewrote it.
Main features:
- Based on FUSE (the best userspace filesystem framework for linux ;-)
- Multithreading: more than one request can be on its way to the server
- Allowing large reads (max 64k)
- Caching directory contents
Installing
First you need to download FUSE 2.2 or later from http://fuse.sourceforge.net/. You also need to install the devel package for glib2.0. After installing FUSE, compile sshfs the usual way:
./configure
make
make install (as root)
How to mount a filesystem
Once sshfs is installed (see next section) running it is very simple:
sshfs hostname: /mountpoint
Note, that its recommended to run it as user, not as root. For this to work the mountpoint must be owned by the user. If the username is different on the host you are connecting to, then use the "username@host:" form. If you need to enter a password sshfs will ask for it (actually it just runs ssh which ask for the password if needed). You can also specify a directory after the ":". The default is the home directory.
Enhancements:
- This release fixes a couple of rarely occurring crashes and some smaller bugs.

Amiga Research Operating System (AROS) is a portable and free desktop operating system aiming at being compatible with AmigaOS 3.1, while improving on it in many areas. The source code is available under an open source license, which allows anyone to freely improve upon it.

Goals

The goals of the AROS project is it to create an OS which:

1. Is as compatible as possible with AmigaOS 3.1.
2. Can be ported to different kinds of hardware architectures and processors, such as x86, PowerPC, Alpha, Sparc, HPPA and other.
3. Should be binary compatible on Amiga and source compatible on any other hardware.
4. Can run as a standalone version which boots directly from hard disk and as an emulation which opens a window on an existing OS to develop software and run Amiga and native applications at the same time.
5. Improves upon the functionality of AmigaOS.

To reach this goal, we use a number of techniques. First of all, we make heavy use of the Internet. You can participate in our project even if you can write only one single OS function. The most current version of the source is accessible 24 hours per day and patches can be merged into it at any time. A small database with open tasks makes sure work is not duplicated.

History

Some time back in the year 1993, the situation for the Amiga looked somewhat worse than usual and some Amiga fans got together and discussed what should be done to increase the acceptance of our beloved machine. Immediately the main reason for the missing success of the Amiga became clear: it was propagation, or rather the lack thereof. The Amiga should get a more widespread basis to make it more attractive for everyone to use and to develop for. So plans were made to reach this goal. One of the plans was to fix the bugs of the AmigaOS, another was to make it an modern operating system. The AOS project was born.

But exactly what was a bug? And how should the bugs be fixed? What are the features a so-called modern OS must have? And how should they be implemented into the AmigaOS?

Two years later, people were still arguing about this and not even one line of code had been written (or at least no one had ever seen that code). Discussions were still of the pattern where someone stated that "we must have ..." and someone answered "read the old mails" or "this is impossible to do, because ..." which was shortly followed by "youre wrong because ..." and so on.

In the winter of 1995, Aaron Digulla got fed up with this situation and posted an RFC (request for comments) to the AOS mailing list in which I asked what the minimal common ground might be. Several options were given and the conclusion was that almost everyone would like to see an open OS which is compatible to AmigaOS 3.1 (kickstart 40.68) on which further discussions could be based upon to see what is possible and what is not.

So the work began and AROS was born.

Intelligent Filesystem Guard is a tool that monitors information about changes in files and directories.

Intelligent Filesystem Guard can be used either for the detection of changes in important files (as an intrusion detection system guarding data against viruses and Trojan horses) or for guarding user data.

A large emphasis is put on monitoring files. One of the functions of this system is to tell what happened with the file according to a user query. The system is able to warn of any sort of change, such as modification, creation, erasure, or movement.

MP3::Find::Filesystem is a File::Find-based backend to MP3::Find.

SYNOPSIS

use MP3::Find::Filesystem;
my $finder = MP3::Find::Filesystem->new;

my @mp3s = $finder->find_mp3s(
dir => /home/peter/music,
query => {
artist => ilyaimy,
album => myxomatosis,
},
ignore_case => 1,
);

FileSystemStorage is a project that provides FileSystem storage for Archetypes.

FileSystemStorage is an Archetype storage for storing data on FileSystem This storage is used to avoid ZODB to grow quickly when using a lot of large files.

This extension library provides the filesystem primitives to your Lua scripts, which are missing from the core language. The exported primitives include mkdir, rmdir, stat, chown, chmod, and more.
Available filesystem primitives:
chdir()
chmod()
chown()
cwd()
is_dir()
is_file()
mkdir()
readdir()
rmdir()
stat()
This project was started when I was coding a simple Lua webserver and became frustrated at the lack of available filesystem primitives.
Enhancements:
- This is the first stable release of the software with complete documentation and a sufficiently useful set of exported primitives.

FUSE can implement a fully functional filesystem in a userspace program.
Main features:
- Simple library API
- Simple installation (no need to patch or recompile the kernel)
- Secure implementation
- Userspace - kernel interface is very efficient
- Usable by non privileged users
- Runs on Linux kernels 2.4.X and 2.6.X
- Has proven very stable over time
Installation
Some projects include the whole FUSE package (for simpler installation). In other cases or just to try out the examples FUSE must be installed first. The installation is simple, after unpacking enter:
./configure
make
make install
If this produces an error, please read on.
The configure script will try to guess the location of the kernel source. In case this fails, it may be specified using the --with-kernel parameter. Building the kernel module needs a configured kernel source tree matching the running kernel. If you build your own kernel this is no problem. On the other hand if a precompiled kernel is used, the kernel headers used by the FUSE build process must first be prepared. There are two possibilities:
1. A package containing the kernel headers for the kernel binary is available in the distribution (e.g. on Debian its the kernel-headers-X.Y.Z package for kernel-image-X.Y.Z)
2. The kernel source must be prepared:
- Extract the kernel source to some directory
- Copy the running kernels config (usually found in /boot/config-X.Y.Z) to .config at the top of the source tree
- Run make menuconfig, then make dep at the top of the source tree (only needed on 2.4 kernels)
If using the 2.6 kernel, then write access is needed to some files in the kernel source tree. Usually it is enough if you make .tmp_versions and .__modpost.cmd writable.
Enhancements:
- Stacking support for the high level API
- Add filename charset conversion module
- Improved mounting

Want to build your own community? Now youre limited only by your imagination. Not by software.
Dolphin Smart Community Builder is a Web community script that allows you to build any kind of online community you want.
With a huge variety of features and options, you can quickly develop your very unique and successful community site.
Dating Software Upgrade
Dolphin is so much more than a dating script. Dating software is now obsolete. Dolphin includes all features of dating scripts and adds more. It can be used as a reliable software platform for any online community you could imagine.
Freedom. Freedom. Freedom.
Dolphin gives complete freedom. In fact it gives at least three freedoms - its free in terms of price (you can download it for free); free in terms of licence (GPL) and free in terms of YOUR power to change, improve and expand your community site.
Experience and Innovation
Dolphin is a mature software with superior upgrade history; backed by a team with over 5 years of experience in dating and community software development. Dolphin is always in forward motion in terms of technology and research.
Main features:
- personal blogs
- user template switcher New!
- events by users
- speed dating & moderators
- drag&drop index compose
- media gallery
- mp3 upload
- multiple payment providers (PayPal, 2checkout, ccBill)
- multiple languages
- rate photos (hot or not)
- Gmail like mail history
- hot list & black list
- rate and comment profiles
- friends lists
- social network
- French, German, Russian, Dutch, Spanish Languages (for premiums) New!
- affiliate system, member as affiliate
- customizable profiles
- membership levels management
Enhancements:
- A WYSIWYG editor is available in member profiles.
- The design templates structure was improved.
- An integrated base configuration class was added.
- The system for uploading media files was improved.
- Integration with Ray 2.3 and Orca 1.1 was implemented.