JMRI: 2.2 production version available


 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Software Releases - RSS News JMRI: 2.2 production version available
# 1  
Old 07-15-2008
JMRI: 2.2 production version available

Java interfaces and sample implementations for controlling a model railroad layout from a personal computer. JMRI is intended as a jumping-off point for hobbyists to build their own layout controls. Includes the DecoderPro and PanelPro applications.
Image
Image Image

More...
Login or Register to Ask a Question

Previous Thread | Next Thread

5 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Copy a file from directroy/ prior version to the directory/ new version

How to copy a file from directroy/ prior version to the directory/ new version automatically. (4 Replies)
Discussion started by: roy1912
4 Replies

2. IP Networking

Production to DR switch

Hi, I have application server on IP 10.10.220.42 (Prod). When the Production goes down I wish to switch over all my application server's configuration files onto IP 10.10.220.45 (DR). The client is exposed to proxy apache http webserver running @ IP 10.10.220.30 Can you please suggest... (4 Replies)
Discussion started by: mohtashims
4 Replies

3. BSD

Copying OpenBSD Kernel from a non production to production machine

Hi All, There are few OpenBSD 4.8 servers without compiler installed at my working place. However, sometimes there are some patches released for patching the kernel. My question is: Can I setup a non production OpenBSD 4.8 server as a test machine with compiler installed and use it to... (1 Reply)
Discussion started by: lcxpics
1 Replies

4. UNIX for Dummies Questions & Answers

need help.. ! Production Env.

Hi ! I want to delete a softlink... with a name.. " -> ALCATEL " FYI:- lrwxrwxrwx 1 infomcm develop 32 Dec 3 2007 COX -> /wlsuite/om/cm/build/sandbox/COX lrwxrwxrwx 1 infomcm develop 33 Jul 21 05:52 WL10 -> /wlsuite/om-cm/build/sandbox/WL10 lrwxrwxrwx 1... (2 Replies)
Discussion started by: dashok.83
2 Replies

5. UNIX for Dummies Questions & Answers

Most common version of UNIX on production systems

I am new to UNIX (about a year) and learning as fast as I can. I am an instructor teaching UNIX and have two labs with Ultra 10 333 MHz, Sun Blade 1000 1 GHz, Blade 100, and Two Enterprise 250 Servers. We are currently teaching our classes using the Solaris 2.10 OS, downloaded in May 2006, I am not... (7 Replies)
Discussion started by: dutchman
7 Replies
Login or Register to Ask a Question
SETXKBMAP(1)						      General Commands Manual						      SETXKBMAP(1)

NAME
setxkbmap - set the keyboard using the X Keyboard Extension SYNOPSIS
setxkbmap [ args ] [ layout [ variant [ option ... ] ] ] DESCRIPTION
The setxkbmap command maps the keyboard to use the layout determined by the options specified on the command line. An XKB keymap is constructed from a number of components which are compiled only as needed. The source for all of the components can be found in /usr/local/share/X11/xkb. OPTIONS
-help Prints a message describing the valid input to setxkbmap. -compat name Specifies the name of the compatibility map component used to construct a keyboard layout. -config file Specifies the name of an XKB configuration file which describes the keyboard to be used. -device device Specifies the numeric device id of the input device to be updated with the new keyboard layout. If not specified, the core keyboard device of the X server is updated. -display display Specifies the display to be updated with the new keyboard layout. -geometry name Specifies the name of the geometry component used to construct a keyboard layout. -I directory Adds a directory to the list of directories to be used to search for specified layout or rules files. -keycodes name Specifies the name of the keycodes component used to construct a keyboard layout. -keymap name Specifies the name of the keymap description used to construct a keyboard layout. -layout name Specifies the name of the layout used to determine the components which make up the keyboard description. Only one layout may be specified on the command line. -model name Specifies the name of the keyboard model used to determine the components which make up the keyboard description. Only one model may be specified on the command line. -option name Specifies the name of an option to determine the components which make up the keyboard description; multiple options may be speci- fied, one per -option flag. Note that setxkbmap adds options specified in the command line to the options that were set before (as saved in root window properties). If you want to replace all previously specified options, use the -option flag with an empty argu- ment first. -print With this option the setxkbmap just prints component names in a format acceptable by xkbcomp (an XKB keymap compiler) and exits. The option can be used for tests instead of a verbose option and in cases when one needs to run both the setxkbmap and the xkbcomp in chain (see below). -rules file Specifies the name of the rules file used to resolve the requested layout and model to a set of component names. -symbols name Specifies the name of the symbols component used to construct a keyboard layout. -synch Force synchronization for X requests. -types name Specifies the name of the types component used to construct a keyboard layout. -variant name Specifies which variant of the keyboard layout should be used to determine the components which make up the keyboard description. Only one variant may be specified on the command line. -verbose|-v [level] Specifies level of verbosity in output messages. Valid levels range from 0 (least verbose) to 10 (most verbose). The default ver- bosity level is 5. If no level is specified, each -v or -verbose flag raises the level by 1. USING WITH xkbcomp If you have an Xserver and a client shell running on different computers and XKB configuration files on those machines are different you can get problems specifying a keyboard map by model, layout, options names. This is because setxkbcomp converts these names to names of XKB configuration files according to files that are on the client side computer, then it sends the file names to the server where the xkb- comp has to compose a complete keyboard map using files which the server has. Thus if the sets of files differ significantly the names that the setxkbmap generates can be unacceptable on the server side. You can solve this problem by running the xkbcomp on the client side too. With the -print option setxkbmap just prints the file names in an appropriate format to its stdout and this output can be piped directly to the xkbcomp input. For example, the command setxkbmap us -print | xkbcomp - $DISPLAY makes both steps run on the same (client) machine and loads a keyboard map into the server. SEE ALSO
xkbcomp(1) FILES
/usr/local/share/X11/xkb X Version 11 setxkbmap 1.0.4 SETXKBMAP(1)