Free thin file putter software for linux

Thin FTP Applet is a full featured File Transfer Program that can be easily integrated into your website or web application.
You can use it to carry out recursive folder uploads and downloads. Entire directory trees being transfered in single click. Interrupted transfers can be resumed.
Thats not all that the applet can do, it can be used to rename, delete and change permissions of file and folders and do almost anything that you can do with your favourite desktop FTP client.
Even though Thin FTP is a web client, its appearence is no different from the traditional 2-Table interface found on many desktop clients. Because Thin FTP is an applet, it does not need to refresh itself each time a file transfer or any other operation takes place.
The Profession Edition provides even tighter integration with existing web applications by allowing for automatic login.
Enhancements:
- Compatibility issues with OS X and Netware FTP servers and the pure-ftpd server on Linux have been addressed.

thin liquid film project is an application which allows linux users to quickly and easily convert video files into a format suitable for playing on the video capable ipods. I wrote this application, after purchasing a video ipod, and being frustrated that the only real option for converting video was either via command-line, or via a servicemenu with no ability to configure the resulting video file.
TLF uses the ffmpeg engine to do the encoding. It is written in pyqt, so it should work with a default kde installation, and is very easy to install.
features ...
Main features:
- Batch process any number of files;
- Display detailed information about source video files;
- Change output settings for one or many files;
- Save default settings for future sessions;
- Configure output quality settings;
- Choose between mpeg4 and h264 as output codec;
- Choose between 320 and 640 output video width, while maintaining aspect ratio;
- Choose between 1 or 2 pass encoding;
- Progress bar to show encoding progress;
- Uses ffmpeg as the encoding engine;
- Upload encoded files to your ipod directly;
- Set file information for upload to your ipod;
- Add files to existing or new video playlists on your ipod;
- Add files for encoding via the included servicemenu.

Thin FTP Upload project is an FTP upload applet designed for integration with Web applications.
Do you want to quickly add FTP file upload functionality to your website? Then Thin FTP Applet, a product that can be installed in less than 2 minutes is the product to choose.
To send files using the File Transfer Protocol, all your users have to do is to drag and drop them onto the designated area of the browser. Entire directory tree and a virtually unlimited number of files totalling several giga bytes can be transfered in this manner.
If your server is configued to allow annoymous transfers your users dont even have to login. Else they can login interactively by entering their username and password. Or else you can make it easier for them by using a single predefined username and password for each user so that multiple accounts do not have to be created.
Whats New in 1.02 Stable Release:
- The new version of the applet aims for improved compatibility with a wider range of FTP servers, epecially those servers deployed on Windows.
- The new version includes a subtle change in the way that the applet handles the trailing slash in the URL.
Whats New in 2.0 Development Release:
- Interrupted FTP uploads can now be resumed.
- A new progress monitor has been added.
- The applet loading mechanism has been changed, and the applet can now be configured using HTML parameters.

Thinstation is a thin client Linux distribution that makes a PC a full-featured thin client supporting all major connectivity protocols: Citrix ICA, No Machine NX, MS Windows terminal
services (RDP), Tarantella, X, telnet, tn5250, VMS term and SSH.

No special configuration of the application servers is needed to use Thinstation!

Thinstation can be booted from network (e.g. diskless) using Etherboot/PXE or from a local floppy/CD/HD/flash-disk. The thin client configuration can be centralized to simplify management.

Thinstation supports client-side storage (floppy/HD/CD/USB) and printers (LPT/USB). Prebuilt images and a Live CD are available too!

Mozilla Firefox and lighter browsers are supported as client-side browsers.

ThinTUX is a small Linux distribution for thin clients. It has support for all major remote access protocols like ICA, RDP, XDM, telnet, ssh, and more.
The distribution can be booted from the network using a network card with PXE-support or from standard media storage devices like floppy, CD, hard disk, or disk-on-chip.
The configuration is stored on a DHCP server to simplify terminal management.
Main features:
- Automatic hardware discovery and centralized configuration using DHCP
- Single point of administration
- Small footprint
- Fully self-contained
- No NFS mounted root filesystem
- Web based configuration tool
- One boot image fits all computers
- No previous Linux knowledge required
Enhancements:
- Reduced startup time.
- Reduced RAM footprint.
- Added support for glibc programs.
- Updated kernel
- Updated to rdesktop 1.4.1
- Updated the configuration tool(ThinTUX web tool).
- Renamed configuration variables

Pluto is the Reference Implementation of the Java Portlet Specfication. The current version of this specification is JSR 168.
Portlets are designed to run in the context of a portal. They are written to the Portlet API which are similar to the Servlet API.
In contrast to servlets, portlets may not do things like sending redirects or errors to browsers directly, forwarding requests or writing arbitrary markup to the output stream to assure that they don?t distract the portal web application which uses them.
Another difference compared to servlets is that portlets rely on portal specific infrastructure functions such as access to user profile information, standard interface for storing/retrieving persistent settings, getting client information, etc. Generally,
portlets are administrated more dynamically than servlets typically are.
A portlet container provides a runtime environment for portlets implemented according to the Portlet API. In this environment portlets can be instantiated, used and finally destroyed. The portlet container is not a stand-alone container like the servlet container; instead it is implemented as a thin layer on top of the servlet container and reuses the functionality provided by the servlet container.
Pluto serves as portlet container that implements the Portlet API and offers developers a working example platform from which they can test their portlets. However, its cumbersome to execute and test the portlet container without a driver, in this case, the portal.
Plutos simple portal component is built only on the portlet containers and the JSR 168s requirements. (In contrast, the more sophisticated, Jetspeed project concentrates on the portal itself rather than the portlet container, and considers requirements from other groups.)
Enhancements:
- Added Pluto 1.1 index page and basic documentation
- PLUTO 164: response contentType can change after getWriter()
- PLUTO 155: URL encoding in pluto 1.0.1-RC4 issue when using apache with jk2
- PLUTO 157: portlet.tld taglib is using jsp version 1.1. JSR168 spec requires JSP version 1.2
- PLUTO 152: Support maven deployment to a remote repository
- PLUTO 130: portlet:namespace fails inside JSTL c:set
- PLUTO-107: Admin portlet fails to add page. Hot deployment now supported.
- PLUTO-92: Deployer strips elements from web.xml (Deploy War Portlet)

BCCD - Bootable Cluster CD was created to facilitate instruction of parallel computing aspects and paradigms. Part of the difficulty instructors face is lack of dedicated resources to explore distributed computing aspects lack of time to preconfigure and test the supporting environment.

The BCCD image addresses this problem by providing a non-destructive overlay way to run a full-fledged parallel computing environment on just about any workstation-class system...Were happy to say that this now includes the MAC too!

The BCCD does share similarities with a few diskless solutions for clustering, such as the Warewulf project, the thin-OSCAR approach, Cluster Knoppix (only an openMosix system, no MPI/LAM/PVM build tools, ...), and so on. This is definitely the trend in HPC. But the main differences are that the BCCD will always fit in your pocket, be highly customizable for specific institutions needs, and will always be geared toward education and not dedicated clusters.

The "gar" build system also sets the BCCD apart from other projects. "gar" is a mix between BSDs "ports" system, Linux from scratch, and gentoo Linux. With gar, you can build an entire BCCD image from net-fetched sources in about two hours (assuming you have a primed ccache!).

The BCCD is also distinctly different from NPACI-Rocks, OSCAR, Cluster in a box or other type of mass-imaging clustering project for two reasons:

1. Its a non-destructive overlay on top of the current hardware. Once a system is rebooted, it reverts back to its original state. It is intended to be booted "over top" of a currently-configured Windows/Linux/BSD/etc. system.
2. Its focus in on educational aspects of High-Performance Computing (HPC) instead of the HPC core. Students will have a much better appreciation and understanding of how to tweak an MTU setting or wire the topology across a cluster if they understand how a distributed computation is laid out! Emphasis is placed upon building, configuring, and running distributed applications.

PXES project is a micro Linux thin client distribution. PXES will boot a real thin client or will help to convert in minutes any compliant hardware (see list bellow) into a versatile thin client.
They will be capable of accessing any XDM server presenting the graphical login screen or any Microsoft Terminal Server through RDP protocol. The actual configuration of clients is made with an easy to use graphical configuration tool, allowing the specification of clients parameters or the server to access to.
You can recover hardware that is useless running current desktop OS or office package and give it a second chance. This thin client boots from the network with PXE (Intel Pre-Execution Environment specifications) so neither boot diskette nor boot eprom is needed.
The linux kernel and an initial root filesystem is transmitted over the network (the compressed size as of version 0.4 is about 4M).
Main features:
Supported servers and protocols
- Unix/Linux supporting XDM
- Microsoft Terminal Server using RDP
- Citrix using ICA
- VNC using TightVNC
- LOCAL local graphical session with simple desktop
- LTSP or K12LTSP
- IBM Host using 3270 or 5250 emulation (soon)
- Telnet emulating ANSI terminal
- SSH
- Tarantella using proprietary protocol
- NoMachine using NX
- Thinlinc
Boot methods
- PXE network card included in most modern PC hardware
- Etherboot to boot from diskette or EPROM
- CD-ROM
- Hard disk
- DOC DiskOnChip and DOM DiskOnModule
- USB Storage
- For Hard Disk, DOC, DOM or other flash memory installation you may also use PXES HD/DOM Installer (http://pxes.sourceforge.net/enterprise/install-dom.shtml) which is part of Enterprise Edition (http://pxes.sourceforge.net/enterprise/index.php).
- You can also see the detailed information about Boot Methods.
Hardware requirements
- Processor: x86 architecture (i486, i586, i686, VIA C3, Geode, Vortex86, Transmeta Crusoe, etc.)
- BUS: PCI recommended (although ISA works)
- RAM: 32 Mb recommended (16 Mb minimum)
- NIC: see supported network card list
- Video: see supported video card list
Local devices
- Diskette
- Hard disk
- CD-ROM
- Printers parallel, serial and USB
- Serial devices (bar code reader, etc.)
- Audio
- Flash memory / USB storage
Supported operating system
- Linux
- Solaris
- AIX
- SCO
- BSD
- HP-UX
- Microsoft Windows NT4
- Microsoft Windows 2000
- Microsoft Windows 2003
- Microsoft Windows XP
Enhancements:
- Support for different boot loaders was added.
- Support for GRUB on ISO images was added.
- A correction was made in the kernel and image path in isolinux.
- A message telling the user to run "pxesconfig --updatefstab" was added.
- updatefstab was added in post.
- Support for 2.4.32 and 2.6.15 kernels was added.
- Automated owner and permission changing on specific files was added, so now the whole pxes-base tree can be checked out as a normal user.