Free turbo tax software for linux

FreeBSD is an advanced operating system for x86 compatible (including Pentium and Athlon), amd64 compatible (including Opteron, Athlon 64, and EM64T), IA-64, PC-98, Alpha/AXP and UltraSPARC architectures.
It is derived from BSD, the version of UNIX developed at the University of California, Berkeley. It is developed and maintained by a large team of individuals. Additional platforms are in various stages of development.
FreeBSD offers advanced networking, performance, security and compatibility features today which are still missing in other operating systems, even some of the best commercial ones.
FreeBSD makes an ideal Internet or Intranet server. It provides robust network services under the heaviest loads and uses memory efficiently to maintain good response times for thousands of simultaneous user processes.
The quality of FreeBSD combined with todays low-cost, high-speed PC hardware makes FreeBSD a very economical alternative to commercial UNIX workstations. It is well-suited for a great number of both desktop and server applications.
FreeBSD can be installed from a variety of media including CD-ROM, DVD-ROM, floppy disk, magnetic tape, an MS-DOS partition, or if you have a network connection, you can install it directly over anonymous FTP or NFS.
While you might expect an operating system with these features to sell for a high price, FreeBSD is available free of charge and comes with full source code.
It is easy to contribute to FreeBSD. All you need to do is find a part of FreeBSD which you think could be improved and make those changes (carefully and cleanly) and submit that back to the Project by means of send-pr or a committer, if you know one. This could be anything from documentation to artwork to source code.
Even if you are not a programmer, there are other ways to contribute to FreeBSD. The FreeBSD Foundation is a non-profit organization for which direct contributions are fully tax deductible.
Main features:
- A merged virtual memory and filesystem buffer cache continuously tunes the amount of memory used for programs and the disk cache. As a result, programs receive both excellent memory management and high performance disk access, and the system administrator is freed from the task of tuning cache sizes.
- Compatibility modules enable programs for other operating systems to run on FreeBSD, including programs for Linux, SCO UNIX, and System V Release 4.
- Soft Updates allows improved filesystem performance without sacrificing safety and reliability. It analyzes meta-data filesystem operations to avoid having to perform all of those operations synchronously. Instead, it maintains internal state about pending meta-data operations and uses this information to cache meta-data, rewrite meta-data operations to combine subsequent operations on the same files, and reorder meta-data operations so that they may be processed more efficiently. Features such as background filesystem checking and file system snapshots are built on the consistency and performance foundations of soft updates.
- File system snapshots, permitting administrators to take atomic file system snapshots for backup purposes using the free space in the file system, as well as facilitating background fsck, which allows the system to reach multiuser mode without waiting on file system cleanup operations following power outages.
- Support for IP Security (IPsec) allows improved security in networks, and support for the next-generation Internet Protocol, IPv6. The FreeBSD IPSEC implementation includes support for a broad range of accelerated crypto hardware.
- Out of the box support for IPv6 via the KAME IPv6 stack allows FreeBSD to be seamlessly integrated into next generation networking environments. FreeBSD even ships with many applications extended to support IPv6!
- Multi-threaded SMP architecture capable of executing the kernel in parallel on multiple processors, and with kernel preemption, allowing high priority kernel tasks to preempt other kernel activity, reducing latency. This includes a multi-threaded network stack and a multi-threaded virtual memory subsystem. With FreeBSD 6.x, support for a fully parallel VFS allows the UFS file system to run on multiple processors simultaneously, permitting load sharing of CPU-intensive I/O optimization.
- M:N application threading via pthreads permitting threads to execute on multiple CPUs in a scaleable manner, mapping many user threads onto a small number of Kernel Schedulable Entities. By adopting the Scheduler Activation model, the threading approach can be adapted to the specific requirements of a broad range of applications.
- Netgraph pluggable network stack allows developers to dynamically and easily extend the network stack through clean layered network abstractions. Netgraph nodes can implement a broad range of new network services, including encapsulation, tunneling, encryption, and performance adaptation. As a result, rapid prototyping and production deployment of enhanced network services can be performed far more easily and with fewer bugs.
- TrustedBSD MAC Framework extensible kernel security, which allows developers to customize the operating system security model for specific environments, from creating hardening policies to deploying mandatory labeled confidentiality of integrity policies. Sample seucrity policies include Multi-Level Security (MLS), and Biba Integrity Protection. Third party modules include SEBSD, a FLASK-based implementation of Type Enforcement.
- GEOM pluggable storage layer, which permits new storage services to be quickly developed and cleanly integrated into the FreeBSD storage subsystem. GEOM provides a consistent and coherrent model for discovering and layering storage services, making it possible to layer services such as RAID and volume management easily.
- FreeBSDs GEOM-Based Disk Encryption (GBDE), provides strong cryptographic protection using the GEOM Framework, and can protect file systems, swap devices, and other use of storage media.
- Kernel Queues allow programs to respond more efficiently to a variety of asynchronous events including file and socket IO, improving application and system performance.
- Accept Filters allow connection-intensive applications, such as web servers, to cleanly push part of their functionality into the operating system kernel, improving performance.

The Circle is an open source scalable decentralized peer to peer application. What does that mean? Well, theres no central authority running the show. No entry taxes either, no censorship, and (in theory) no weak point which can break the whole system. No one even owns the source code. There is a network, even if there are a few people which uses this program.

The Circle allows you to :

* Share files
* Send instant messages and chat IRC-style
* Put together your own personalized, trust based news service
* Proxy Debian package downloads

The Circle is written in Python. It runs on Linux and Windows. (in fact, there is very little operating system specific code, so it will most likely work on any system that supports Python).

At the core of the Circle is a decentralized hashtable, or "Chord". This table allows users to search for files in logarithmic time, based on keywords. This means that the Circle does not have the scalability problems of Gnutella style network (such as Kazaa, eDonkey), while also avoiding the need for a central server and therefore a single point of failure. Details of its operation are given in the "Technical Details" section below.

The Circle does have the ability to post fully anonymous news a la Freenet. However, the file-sharing protocol isnt entirely anonymous. People will be able to work out your IP address.

In order to protect user privacy, the Circle includes a Digital Rights Management system. Although everybody can search your files by their keywords, you may choose which users are authorized to download them. An unauthorized third party has access only to the names of your files, not to their content. Needless to say, we expect you to use this system in order to prevent copyright infringement, while allowing private copy.

Note: If we become aware that you are trying to share snuff or child pornography, we will be able to work out your IP and from that your location and identity, and report you to the police and/or your ISP. Snuff and child pornography are things we think any reasonable person considers to be evil (its an issue quite separate from the debate over copyright).

MGRX project is a 2D graphics library derived from the GRX library. GRX was originaly written by Csaba Biegl for DJ Delories DOS port of the GCC compiler. MGRX supports four platforms: DOS (DJGPPv2), Linux console, Linux X11 and Win32 (Mingw). On DOS it supports VGA and VESA compliant cards. On Linux console it uses the framebuffer. On X11 and Win32 it runs in a window.

Why MGRX

MGRX is a fork of GRX. Because I liked the GRX C API interface, I began to maintain GRX when it was orphaned at the end of 2000. But GRX has not only the C API, it has a Pascal API, a BGI compatibility API, support for Turbo C, Wattcom, MSC and some X11 implementations over mainframes. At the end it was not funny, to easy to break things I dont know (and dont want to know). So I stoped my job maintainig GRX at the end of 2003. At the time I write this, GRX is still orphaned.

But in the mean time I developed a fork for my own use, only the C API, no Pascal, no BGI, no Turbo C support, only the 4 platforms I can test. And a new (and better I think) input API. And now I have released it, only for fun.

Supported platforms:

Latest versions of OS, compiler, and key software tested:
Linux X11: linux 2.6.18, Xorg 7.2, gcc 4.1.2
Linux fb: linux 2.6.18, gcc 4.1.2
DJGPP: djdev 2.03, gcc 4.1.2
Win32: Windows XP, MinGW 3.1.0-1

libgeier is a library to send gathered tax declarations data to the German inland revenue offices (using the Elster2/Coala-approach).

It is capable of validating, encrypting, digitally signing, and sending the data, which has to be supplied as an XML tree. libgeier library can generate transmission protocols for you. A small command line client is included.

Apollo is an open-source developer test skeleton toolkit for Web Start. Apollo lets you turbo-charge Web Start apps without Web Start to speed up your compile/run/test/debug/goof-off cycle avoiding the hassle of stuffing, signing, uploading or downloading your jars every time you rearrange a comma in your source code.

Apollo is not a replacement for Web Start (OpenJNLP, NetX or any other app launcher). Apollo is more like a test emulator (such as POSE - Palm OS Emulator) helping you to speed up your development between full-blown, time-consuming, irreplaceable, real Web Start workouts.

Apollo cant fake every Web Start bell and whistle (e.g. download on demand) but outshines Suns Web Start dumb dev pack stubs that merely let you compile your source. Apollo lets you popup your household browser and more without calling in the Web Start machinery.

Apollo consists of a jar that you can use to replace Suns javax.jnlpx stubs residing in jnlp.jar that only allow you to compile your code and that ship with Suns Web Start dev pack.

Apollo is a thin wrapper around Suns javax.jnlpx services. If your app runs under Web Start Apollo will automatically detect it and pass all runtime service calls (such as poping up a browser window) on to the Web Start engine. If your app, however, runs without Web Start Apollo will kick in and mimick Web Starts runtime services.

To use Apollo replace all javax.jnlpx imports with apollo. Example:

import javax.jnlpx.*; // Web Start only
import apollo.*; // Web Start plus Apollo-propelled stand-alone launching

To spare you from learning yet another API set Apollo reuses all runtime service class and method names. The only exception is Apollos ServiceManager class that adds type-safe methods to lookup pre-defined runtime services (e.g. lookupBasicService()) avoiding unexpected runtime errors and reducing source code bloat. Example:

import javax.jnlp.*
...
BasicService bs = (BasicService) ServiceManager.lookup( "javax.jnlp.BasicService" );
bs.showDocument( new URL( "http://vamphq.com/times" ) );

becomes

import apollo.*;
...
BasicService bs = ServiceManager.lookupBasicService();
bs.showDocument( new URL( "http://vamphq.com/times" ) );

or

import apollo.*;
...
ServiceManager.lookupBasicService().showDocument( new URL( "http://vamphq.com/times" ) );

Apollo lets you configure the codebase or the online/offline status of your app if you want to run it without Web Start but still use BasicService.getCodeBase() or Basic.isOffline().

By default BasicService.isOffline() returns false (meaning your app is online). If you want to change the setting you can pass the property apollo.offline=true to your app. As an alternative you can also add apollo.properties to your classpath or bundle it with your apps jar in the root directory. Inside the apollo.properties file add the apollo.offline property to match your desired setting. Note, that all apollo properties only work if your app runs without Web Start.

By default BasicService.getCodeBase() uses the working directory returned by the system property user.dir. To use a different codebase pass the property apollo.codebase=your_url_here to your app. As an alternative you can also add the apollo.codebase property to the apollo.properties file in your apps root directory where Apollo picks it up if you run your app without Web Start.