Free kb software for linux

wmCalClockKbd is simple calendar clock with integrated keyboard group indicator (for XFree86 >= 4.3.0).
Usage
If you want to use the keyboard indicator, you really need to have XFree86 >= 4.3.0! If you use more keyboard maps, it should be set properly. There is example of my X86Config-4 InputDevice section:
Section "InputDevice"
Identifier "Keyboard1"
Driver "Keyboard"
Option "XkbModel" "pc102"
# you might use pc105, if you have Win keys on your keyboard
Option "XkbLayout" "us,cz_qwerty"
# most important! I have configured twokeyboard layouts (groups) - US/ASCII
# and Czech(qwerty), you can use up to 4 layouts
Option "XkbCompat" ""
Option "XkbOptions" "default,grp_led:scroll,grp:alt_shift_toggle,grp:switch"
# default - use some default options to avoid Mandrake bug
# grp_led:scroll - indicate alternative groups by switcing the scroll led
# grp:alt_shift_toogle - switch groups by pressing Alt+Shift (left)
# grp:switch - use right alt to set second group, while it is pressed down
EndSection
you can also use setxkbmap, if you dont want to edit you XF86Config-4:
setxkbmap -layout "us,cz_qwerty" -option "default,grp:alt_shift_toogle"
for example. Once, when you have configured your keyboard properly, you can run wmCalClockKbd with -kb option:
wmCalClockKbd -kb "us.xpm,cz.xpm"
which tells to wmCalClockKbd to use us.xpm file for first group and cz.xpm for the second group. Images are taken from the default location specified in PREFIX file.
You can use up to 4 images, but the number of images must be the same as number of configured layouts (groups), otherwise app disable keyboard indicator functions. Please make also sure, that there is your national image in pixmaps directory.
If not, you can make new one (dimension are 54x35 pixels, color depth depends on you system) and send it to me (I will add it to source files, but please dont break any Copyrights when making it).
There is another one new option -kbt, which sets how much will be the keyboard image transparent when merging with date sign (default options is 0.25, you can you any number from 0.0-1.0, but useful values are 0.1-0.5).
All wmCalClock options works like in the original version, you can read about them in olddoc/ dir of source codes or use -help switch.
Enhancements:
- added Russian and French flags

This are Hyriands UNOFFICIAL PySoulSeek patches.
PySoulSeek major features:
- Total queue size limiter
- Option to disable queue size limits for buddies
- Placeholder icons for tabs, so pyslsk doesnt ahve to re-layour (tnx hdhg)
- Faster connection to firewalled users if youre not firewalled yourself (enable "I can receive direct connections" in the server tab of the configuration screen)
- Run a command when a transfer or directory finishes (to auto-enqueue in xmms for example) (filename is properly escaped etc). Thanks Danial
- "Download to".. Select a download folder "on the fly"...
- Auto-reply when away.. Send a canned message to user that send you a private message when you are away..
- Incomplete dir. All incomplete files will be stored here and moved to the download directory when finished.
- Regexp filter in/out. This is an advanced option you should only use if you know what regexps are. You can enable it in the Misc tab of the settings screen.
- PM history (will show the last 15 lines of a conversation if loggin is enabled)
- Search filtering (see new help screen)
- Buttons on the user info are placed nicer
- Set the maximum number of upload slots to use
- Recursive directory downloading (thanks to geertk)
- Command aliasing.. Create your own / commands. See below for syntaxis
- GB/MB/KB filesizes in the transfers list
- Locale-independant decimal separators
- Configurable text colours for chats and search results
- Allow people on your user list to be scheduled for uploads ahead of regular users (see the transfers tab in the settings dialog)
Main features:
- Added features from Hyriands patch:
- Pyslsk will ping the server every 30 seconds (rewrote it to be gui-independent)
- Search history (remembers 10 last searches)
- Log window is now collapsable (state is remembered between sessions), rewrote it to look prettier than hyriands version
- Resizable panels arent deleted anymore when made really small
- Userinfo and browse tabs show user status
- /clear /c will clear a chat screen
- version in the window title
Enhancements:
- Code speedups, wxPython 2.6 fixes, and Unicode/character encoding fixes were made.
- Support for remotely-initiated uploads was added.
- An ignore button was added to searches.
- Graying out was re-enabled for users who left in the chat room.

WARNING:
This program is designed to heavily load CPU chips. Undercooled, overclocked or otherwise weak systems may fail causing data loss (filesystem corruption) and possibly permanent damage to electronic components. Nor will it catch all flaws.
USE AT YOUR OWN RISK

CPU testing utilities in optimized assembler for maximum loading P6 (Intel Pentium Pro/II/III and Celeron TM), AMD K7 (Athlon/Duron/Thunderbird TM) AMD K6, and Intel P5 Pentium chips. This is free software, copyright but freely licenced under the GNU Public Licence copyleft.

These programs are designed to load x86 CPUs as heavily as possible for the purposes of system testing. They have been optimized for different processors. FPU and ALU instructions are coded an assembler endless loop. They do not test every instruction. The goal has been to maximize heat production from the CPU, putting stress on the CPU itself, cooling system, motherboard (especially voltage regulators) and power supply
(likely cause of burnBX/MMX errors).

burnP5 is optimized for Intel Pentium w&w/o MMX processors
P6 is for Intel PentiumPro, PentiumII&III and Celeron CPUs
K6 is for AMD K6 processors
K7 is for AMD Athlon/Duron processors
MMX is to test cache/memory interfaces on all CPUs with MMX
BX is an alternate cache/memory test for Intel CPUs

TO USE: root priviliges are NOT required. It has been designed for ELF Linux, but also tested under FreeBSD. and a.out. Burn Testing is best done from a ramdisk distribution (tomsrtbt) or with filesystems unmounted or mounted read-only.

untar the source in a convenient directory:
`tar zxf cpuburn`

compile excutables
`make`

run desired program in background [ _repeat_ for SMP]:
`burnP6 || echo $? &`

Monitor progress of cpuburn by `ps`. When finished, `kill` the burn* process(es). If you have temperature probes (fingers) or the lm-sensors package, you can check your CPU temperature and/or system voltages.

If an error occurs in calculations, it will be preserved, and the program will terminate with error code 254 for an integer/memory error, and error code 255 for a FP/MMX error. Error checking happens every 10-40 sec for burnP6/K6/K7 and I havent seen any CPU errors in testing [lockups occur first]. burnBX and burnMMX check for error every 512 MB (4-10 sec), and error termination is frequently seen, lockups are rarer.

burnBX and burnMMX are essentially very intense RAM testers. They can also take an optional parameter indicating the RAM size to be tested:

A = 2 kB E = 32 kB I = 512 kB M = 8 MB
B = 4 F = 64 J = 1 MB N = 16
C = 8 G = 128 K = 2 O = 32
D = 16 H = 256 L = 4 P = 64

`burnBX L` (4 MB) and `burnMMX F` (64 kB) are the default sizes. A-E mostly test L1 cache, F-H test L2 cache, and H-P force their way to RAM. But even A-E will have some cacheline writeouts to RAM.

In spite of its name, burnBX can be run on any chipset [RAM controller] and tests alot more than the RAM controller. Unfortunately, burnBX is not optimal on AMD processors. burnMMX is preferable for any CPU that has an MMX unit.

burnBX/MMX needs about 72 MB of total RAM + swap to start (not necessarily free), but doesnt use this much unless you request it. They will throw a `Sig 11` if you dont have enough swap.

If you dont want to add more, you can adjust the .bss section downward as indicated in the source comments. They can also test swap, and at least on my system, I can run 2*`burnBX 8` with 128 MB SDRAM with some use of swap, but no excessive thrashing[seeks]. YMMV.

If sub-spec, your system may lock up after 2-10 minutes. It shouldnt. burn* are just an unpriviliged user processes. But it probably means your CPU is undercooled, most likely no thermal grease or other interface material between CPU & heatsink. Or some other deficiency. A power cycle should reset the system. But you should fix it.

The benchmark program takes less than 10 minutes to run (on most machines) and compares the system it is run on to two benchmark systems (a Dell Pentium 90 with 256 KB cache running MSDOS and an AMD K6/233 with 512 KB cache running Linux).

The archive contains the complete source, documentation, and a binary (Linux elf). The source has been successfully compiled on various operating systems, including SunOS, DEC Unix 4.0, DEC OSF1, HP-UX, DEC Ultrix, MS-DOS, and of course Linux.

This release is based on the Unix port of beta release 2 of BYTE Magazines BYTEmark benchmark program (previously known as BYTEs Native Mode Benchmarks). The port to Linux/Unix was done by Uwe F. Mayer.

Additional changes to the code were made to make the code work with egcs compiler and to make the software packagable. This is a CPU benchmark providing indexes for integer, floating, and memory performance. It is single-threaded and is not designed to measure the performance gain on multi-processor machines.

Running a "make" will create the binary if all goes well. It is called "nbench" and performs a suite of 10 tests and compares the results to a Dell Pentium 90 with 16 MB RAM and 256 KB L2 cache running MSDOS and compiling with the Watcom 10.0 C/C++ compiler.

If you define -DLINUX during compilation (the default) then you also get a comparison to an AMD K6/233 with 32 MB RAM and 512 KB L2-cache running Linux 2.0.32 and using a binary which was compiled with GNU gcc version 2.7.2.3 and GNU libc-5.4.38.

The algorithms were not changed from the source which was obtained from the BYTE web site at http://www.byte.com/bmark/bmark.htm on December 14, 1996. However, the source was modified to better work with 64-bit machines (in particular the random number generator was modified to always work with 32 bit, no matter what kind of hardware you run it on).

Furthermore, for some of the algorithms additional resettings of the data was added to increase the consistency across different hardware. Some extra debugging code was added, which has no impact on normal runs.

In case there is uneven system load due to other processes while this benchmark suite executes, it might take longer to run than on an unloaded system.

This is because the benchmark does some statistical analysis to make sure that the reported results are statistically significant, and an increased variation in individual runs requires more runs to achieve the required statistical confidence.

This is a single-threaded benchmark and is not designed to measure the performance gain on multi-processor machines.

Gtkedit1 is a notepad clone based on GTK+.
Gtkedit1 is a simple editor, written using the GTK+ 1.2 toolkit. It aims to be (in that order) light, useful and simple (source code-wise).
Main features:
- Binary weight less that 30 KB.
- Takes less than half a second to start in the development machine.
- Has nearly all the features of Windows 2000 Notepad (only printing and help are missing).
- The C source code is a single file, about 1400 lines long. No need to use a configure script or even a makefile.
What? another editor? Dont we have enough of them already?
Well, yes, indeed. There are quite a lot of different - and not so different - editors one can download from the Internet. Anyway...
1. I wanted a simple project to try GUI programming in Unix.
2. I have an old machine (Pentium 166 MHz, 32 MB RAM) with Slackware Linux 9.0. 3. This machine runs Xfce 3.8, based on GTK+ 1.2.
Theres no decent GUI editor for this machine. All are too slow, too bloated or too ugly.
OK, In fact I did found an editor that works fine. Its called gnotepad+, but it too takes too long to load (about 2 seconds) in this old machine. Theres plenty of room for improvements here, I thought.
And so gtkedit begun. I only wanted the most basic editing features: cut, copy, paste, basic undo/redo... nothing fancy. The obvious model to copy was, of course, Notepad.
Usage:
gtkedit is very simple to use. It understands the basic common shortcut keys, like < Ctrl >C for copy. You will find them listed next to each menu item.
Very basic undo/redo capabilities are provided, because the editor can only undo the very last text insertion or removal.
You can find and replace text, and there is a menu option that will allow you to quickly go to any particular line, which is handy if one is writting a program and wants locate an error line.
Finally, you can change the font used for text display, or toggle the wrapping of long lines. These settings are lost when the program closes, though.

kompact0r is a simple text based system monitor. It can do everything kompact does but kompact0r displays:

- Distro (not auto detected)
- Kernel, KDE & QT version
- CPU MHz, Temp and % load graph
- Ram & Swap use
- eth0 and/or eth1 IP address and KB/s in & out w/graphs
- Uptime
- Date & Calendar

Comes with:

- Chocie of 2 backgrounds
- Thorough documentation.txt nicely written by benny fletch.

Still available in the theme if you wish to do some editing:

- User & Host names
- Battery Status
- CPU Model
- Used space on the partitions
- Time

Brownstone is a KDE theme with a pale imitation of nature... Inspired by Green Leaf

http://www.kde-look.org/content/show.php/Green+Leaf?content=54875

The JPEGs I have posted doesnt really do justice..a decent png was >300 kb so couldnt upload it..

My part is basically a config file for domino made by me.. everything else is available in kde-look

I have found that most themes are usually leaning towards blue or a specific shade of a colour..so i have tried to make this as colour neutral theme as possible..

More specifically I have tried to get the effect of grey stone on brown earth with greenery after rainfall.. when the sun has come out.. since thats the most soothing image i can think of..and has lots of soft colours..

The other stuff u see are available in kde-look:

Style:

Domino
(I am using the kubuntu package)

Windec:

Crystal

Wallpaper:

Soft green
http://www.kde-look.org/content/show.php/More+green?content=41884

Colour:

Brown Terra
http://www.kde-look.org/content/show.php/Brown+Terra?content=53421

Iconset:

Ekisho_project
http://www.kde-look.org/content/show.php/Ekisho_Project?content=55588

I have made a small change to the icon set config after installation:
In file associations in control centre

goto inode>folder and change the icon to "folder_grey" in filesystems

because the default icon was too bright for this theme..the new icon is shown in the first screenshot

However for some reason the brighter icon appears in the Quick file menu..if someone can point me to the config where i can change that would appreciate it..

Not too sure about how much i have succeeded in getting the effect i wanted..but i hope you like it..feedback appreciated.