Free system software for linux

System monitor is a simple system monitor, used in this icons from Vista Inspirate and Metal Gold icon themes.

system-tools-backends is a package for GNOME.

to extract the configuracion

backend --get

to restore the configuration from XML

backend --set < file.xml

System.FilePath is a Haskell library from Yhc originally, now with added tweaks. Pure Haskell 98 (with Hierarchical libraries), no preprocessor. It has a nice interface for doing file manipulations, and works portably between Windows and Unix. [Not the same as http://darcs.haskell.org/~lemmih/FilePath/]

The interface is still changing, for that reason please use System.FilePath.Version_0_10 or System.FilePath.Version_0_11 which will be guaranteed to work unmodified in future releases.

I have written a System.FilePath module in part based on the one in
Yhc, and in part based on the one in Cabal (thanks to Lemmih). The aim
is to try and get this module into the base package, as FilePaths are
something many programs use, but its all too easy to hack up a little
function that gets it right most of the time on most platforms, and
there lies a source of bugs.

This module is Posix (Linux) and Windows capable - just import
System.FilePath and it will pick the right one. Of course, if you
demand Windows paths on all OSs, then System.FilePath.Windows will
give you that (same with Posix). Written in Haskell 98 + Heirarchical
Modules.

Haddock:
http://www-users.cs.york.ac.uk/~ndm/projects/filepath/System-FilePath.html
Darcs: darcs get http://www.cs.york.ac.uk/fp/darcs/filepath
Source: http://www.cs.york.ac.uk/fp/darcs/filepath/System/FilePath.hs
Homepage: http://www-users.cs.york.ac.uk/~ndm/projects/libraries.php

If you go to the haddock page there are a few little examples at the
top of the file.

Acknowledgements

Thanks to Marc Webber, shapr, David House, Lemmih, others...

Competitors

System.FilePath from Cabal, by Lemmih
FilePath.hs and NameManip.hs from MissingH

The one from Cabal and FilePath.hs in MissingH are both very similar, I
stole lots of good ideas from those two.

NameManip seems to be more unix specific, but all functions in that module
have equivalents in this new System.FilePath module.

Hopefully this new module can be used without noticing any lost functions,
and certainly adds new features/functions to the table.

Should FilePath by an abstract data type?

The answer for this library is no. This is a deliberate design decision.

In Haskell 98 the definition is type FilePath = String, and all functions
operating on FilePaths, i.e. readFile/writeFile etc take FilePaths. The
only way to introduce an abstract type is to provide wrappers for these
functions or casts between Strings and FilePathAbstracts.

There are also additional questions as to what constitutes a FilePath, and
what is just a pure String. For example, "/path/file.ext" is a FilePath. Is
"/" ? "/path" ? "path" ? "file.ext" ? ".ext" ? "file" ?

With that being accepted, it should be trivial to write
System.FilePath.ByteString which has the same interface as System.FilePath
yet operates on ByteStrings.

J Operating System is primarily intended for programmers.
Target Users:
- Hobbiests--You used to buy computers to do programming. They didnt do much else. Windows doesnt even come with a compiler, which is ironic since Bill Gates wrote BASIC. The "J" operating system is primarily intended for programmers. Ive attempted to lower the bar, so amateurs can contribute. I hope to recreate the dynamic environment that used to exist when the Commodore 64 was around and everyone was creating odd-ball software.
- Researchers--Im sure many lab researchers still use DOS because they have to interact with hardware, which is difficult with Windows.
Main features:
- No security! You can access all ports, memory and disk blocks to your hearts content. When youre working with your own computer, security just gets in the way and makes things slow--I hate anti-virus and anti-spyware because they just slow things down. When you know you dont have a risk, have no secrets and do regular back-ups, who needs security?
- Uniformity
- There is no virtual memory and everyone is on the same address-map. You can easily communicate between tasks, passing addresses. Addresses start at a base of zero and, essentually, segment registers are not used.
- There is basically one language to learn called "C+" which is a little more than "C", but less than "C++". You dont need to learn a scripting langauge because everything uses this syntax.
- There is an extension of ASCII called "J" rich text which allows colors, links, graphics and various widgets in your documents. This format is used in source code, documents, help, menus, etc.
- Support for compressed, encrypted and contiguous files.
- FAT32, FAT12 and ISO9660 filesystems.
- Blazing-fast compiler which can recompile everything in 5 seconds. It doesnt optimize.
- All source code is included and its still around a Meg.
Hardware:
- PS/2 mouse and keyboard
- VGA graphics
- Some hard drives. Must be on the primary or secondary IDE controller and support LBA28. Drives of 120Gig are the limit.
- Some CD-ROM/DVD drives, including burning.
- Some floppies. Just 1.44Meg and not all types.
- No USB support yet
- No network support yet
- ASCII printers on the parallel port are supported.

Asymptopia Flashcard System project is a LaTeX flash card system for student and professional education.

Asymptopia Flashcard System uses Motif and LaTeX to produce, manage, and use attractively formatted flashcards.

You load some or all of your "collections" and set the timer for pop-up frequency.

The GUI interface and "Collection Manager" make creating and modifying flashcards as simple as pushing a single button.

A knowledge of LaTeX is only required when entering special symbols.