Free hex codes software for linux

check_iseries plugin for Nagios monitors the IBM iSeries (AS/400). It has been well tested under Linux and Windows.
check_iseries can monitor CPU usage and load, database capacity, the number of running jobs, outq/subsystem status, QSYSOPR messages, and disk status.
check_iseries invokes the following OS/400 (i5/OS) commands: WRKDSKSTS, DSPMSG, WRKOUTQ, WRKACTJOB, and WRKSYSSTS. Several extensions are available.
Enhancements:
- This release adds encrypted passwords (weak XOR, BASE64, or HEX).
- It fixes enterprise extensions configuration file support, do_sep_list for wrkdsksts, a wrkactjob problem with newer versions of i5/OS, and several other bugs.
- It adds -fulljob for SUBSYS.JOBNAME, more handler calls for extensions, reconnection on null-data, added onnomatch and nomatchtxt, and debugging on demand.

Unicode Utilities project are a set of programs for manipulating and analyzing Unicode text. uniname defaults to printing the character offset of each character, its byte offset, its hex code value, its encoding, the glyph itself, and its name. Command line options allow undesired information to be suppressed and the Unicode range to be added.
unidesc reports the character ranges to which different portions of the text belong. unihist generates a histogram of the characters in its input. ExplicateUTF8 is intended for debugging or for learning about Unicode. It determines and explains the validity of a sequence of bytes as a UTF-8 encoding. unirev reverses UTF-8 strings.
Enhancements:
- Adds to unidesc the option -r which causes it to list the ranges detected after reading all input rather than listing them as they are encountered, and adds to uniname the option -B which causes it to ignore characters within the Basic Multilingual Plane.

KPicoSim is an IDE for the picoblaze microcontroller.

KPicoSim is a development environment for the Xilinx PicoBlaze-3 soft-core processor for the KDE Desktop (Linux).

The environment has an editor with syntax highlighting (based on the popular katepart), compiler, simulator and an export functions to VHDL, HEX and MEM files.

KPicoSim provides more or less the same functionality as the Mediatronix pBlazeIDE (windows).

Installation:

You have to compile the program from source. First unpack the sources:

tar zxvf kpicosim-0.5.tar.gz

Then run configure

./configure

After that, compile the source:

make

And as last install the program (make sure you are root (su, type root password)):

make install

Now the program kpicosim is installed on your system. Just run kpicosim

Convert::BinHex can extract data from Macintosh BinHex files.

ALPHA WARNING: this code is currently in its Alpha release. Things may change drastically until the interface is hammered out: if you have suggestions or objections, please speak up now!

SYNOPSIS

Simple functions:

use Convert::BinHex qw(binhex_crc macbinary_crc);

# Compute HQX7-style CRC for data, pumping in old CRC if desired:
$crc = binhex_crc($data, $crc);

# Compute the MacBinary-II-style CRC for the data:
$crc = macbinary_crc($data, $crc);

Hex to bin, low-level interface. Conversion is actually done via an object ("Convert::BinHex::Hex2Bin") which keeps internal conversion state:
# Create and use a "translator" object:
my $H2B = Convert::BinHex->hex2bin; # get a converter object
while (< STDIN >) {
print $STDOUT $H2B->next($_); # convert some more input
}
print $STDOUT $H2B->done; # no more input: finish up

Hex to bin, OO interface. The following operations must be done in the order shown!
# Read data in piecemeal:
$HQX = Convert::BinHex->open(FH=>*STDIN) || die "open: $!";
$HQX->read_header; # read header info
@data = $HQX->read_data; # read in all the data
@rsrc = $HQX->read_resource; # read in all the resource

Bin to hex, low-level interface. Conversion is actually done via an object ("Convert::BinHex::Bin2Hex") which keeps internal conversion state:
# Create and use a "translator" object:
my $B2H = Convert::BinHex->bin2hex; # get a converter object
while (< STDIN >) {
print $STDOUT $B2H->next($_); # convert some more input
}
print $STDOUT $B2H->done; # no more input: finish up

Bin to hex, file interface. Yes, you can convert to BinHex as well as from it!
# Create new, empty object:
my $HQX = Convert::BinHex->new;

# Set header attributes:
$HQX->filename("logo.gif");
$HQX->type("GIFA");
$HQX->creator("CNVS");

# Give it the data and resource forks (either can be absent):
$HQX->data(Path => "/path/to/data"); # here, data is on disk
$HQX->resource(Data => $resourcefork); # here, resource is in core

# Output as a BinHex stream, complete with leading comment:
$HQX->encode(*STDOUT);

PLANNED!!!! Bin to hex, "CAP" interface. Thanks to Ken Lunde for suggesting this.
# Create new, empty object from CAP tree:
my $HQX = Convert::BinHex->from_cap("/path/to/root/file");
$HQX->encode(*STDOUT);

BinHex is a format used by Macintosh for transporting Mac files safely through electronic mail, as short-lined, 7-bit, semi-compressed data streams. Ths module provides a means of converting those data streams back into into binary data.

Sigma Consolefonts package contains a set of UTF-8 fonts which provide readability and wide coverage. Actually, it is only one font, in an 8x16 size but with a number of variations of what gets mapped into the (psfu) consolefont. If you arent using Linux and a UTF-8 locale, this probably will not have any relevance to you.

Still interested ? Ok, here is a less than wonderful photograph of what the sigma-general version of this font can do. Apologies for the poor quality of the photo, I hope you can get an idea of what this does - and if you are using the linux console without a graphical desktop, youll just have to download it to try it out.

I aim to let people see as many characters as possible on their console. I know that most people assume a graphical desktop is necessary to see a wide range of characters, but the standard console can display 512 characters if you do without the bold colours.

Traditional console fonts have often used separate glyphs for cyrillic and latin letters of the same shape, but desktop fonts normally render them identically (e.g. latin A and cyrillic А), and so do I - this helps make some space available. I have used Dmitry Bolkhovityanovs perl script to select which glyphs are used in a particular psfu font, and to map multiple codepoints to the same glyph. There are a limited range of line-drawing characters (enough to give a decent display in the linux kernels make menuconfig).
The main use of these fonts is when you dont have a graphical desktop but still want to be able to read text in many languages. So, perhaps they are most appropriate to people running servers. For myself, they let me read my mail over ssh when I am building the graphical desktop for a new system.

The font itself started out as etl16 from one of the debian console packages. I altered it to give more balanced letters - longer descenders at the expense of less space above the letters, and bringing the accents closer to the letter. The cell format of a capital letter is 3 rows above the letter, 10 rows for the letter, and another 3 rows for the descender. In hex, that is 3A3, hence the name (U+03A3 is Σ).

Unlike traditional vga fonts hard-coded into the machine, these fonts are much less bright - you may have to increase your screens brightness. This is because they are thin (normally only one pixel wide). The 8x16 size is very much "one size fits all" - adequate for most accented latin, and for cyrillic and current greek, but not ideal where there are multiple accents (livonian, vietnamese, polytonic greek).
Unlike most other console fonts, these come with the source (a bdf font) and a series of map files to decide what to include. So, if you really dislike the form of one of the letters you can alter it - the bdf is just 16 lines of hex codes, e.g. a capital U has nine lines of x42 (0100 0010) and a baseline of x3C (0011 1100).

If you want to change a map, either to add something else, or to remove something you dont use, they are simple to edit.
The linux console cannot accomodate CJK languages, so this font is for people who use alphabetic languages. The armenian and georgian glyphs should be identical to what is in etl16, also the arabic and hebrew (and I really dont know how useful those are on a left-to-right terminal). Everything else has been tweaked to provide what I think is a satisfactory result.

The tarball includes my attempt at listing the alphabets for the languages covered - to answer the question, which glyphs do you need for a particular language. These files may also be useful if you are using xorg and want to check whether your fonts provide adequate coverage.

For most people, I think the general version should work well (latin, greek and the main european cyrillic letters). Some people may prefer the cyrillic variant (all current cyrillic, greek, some latin letters. There is also a caucasian variant (latin, cyrillic, armenian, georgian) and some other example and proof-of-concept variants, e.g. african, polytonic, vietnamese. Ultimately, the african languages are limited by a lack of precomposed glyphs in unicode (AFAIK, there is a lack of terminals which support combining diacriticals), but some languages such as venda should work. Languages with multiple accents above the letter (livonian, polytonic greek, vietnamese) are not wonderful in the 8x16 size, but they might suffice.

Crossword allows you to try to solve crossword puzzles.
Crossword is a GNOME game that draws a crossword grid and clues for you to solve based on a configuration file.
It also has an editor to let you easily create puzzles.
Enhancements:
- Initial release! :)
- Currently can draw the board and the clues
- The interface needs a lot of work
- The editor has hardly been started, and is not usable
- The file format has been mostly finalized, so you can create files with a hex editor (not a text editor)

DCE::Status is a Perl interface of DCE status codes.

SYNOPSIS

use DCE::Status;

$errstr = error_inq_text($status);

tie $status => DCE::Status;

When a $scalar is tied to the DCE::Status class, it has a different value depending on the context it is evaluated in, similar to the magic $! variable. When evaluated in a numeric context, the numeric value is returns, otherwise, the string value obtained from dce_error_inq_text is returned.

EXPORTS

error_inq_text

Equivalent to the dce_error_inq_text function.

$errstr = error_inq_text($status);