BlinkenSisters Jump'n'Run 0.5.3 (Default branch)

Tags

Special Forums News, Links, Events and Announcements Software Releases - RSS News BlinkenSisters Jump'n'Run 0.5.3 (Default branch)

12-07-2008

Registered User

26,240, 27

Join Date: Sep 2000

Last Activity: 1 August 2008, 3:09 PM EDT

Posts: 26,240

Thanks Given: 0

Thanked 27 Times in 26 Posts

BlinkenSisters Jump'n'Run 0.5.3 (Default branch)

Blinkensisters is a Parallax-style 2D scrolling gaming system for Windows, Mac OS X, Linux, and POSIX-compatible Unix systems (every platform that can run SDL). You can make your own levels with a simple text editor. The game also supports scripting. License: GNU General Public License (GPL) Changes:
This release adds a number of features like Color-3D (Anaglyph rendering), a Zoom-Mode that fixes some fullscreen issues, as well as major performance enhancements and a number of bugfixes. It is recommended that all users upgrade to this version.

More...

Linux Bot

View Public Profile for Linux Bot

Find all posts by Linux Bot

Previous Thread | Next Thread

3 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Notify when the script run(hourly)on my jump-box only when there is a failure on my remote-box

Team, Presently I have a script, which i have set up cron on one of my Jump-boxes,and gives me the output on every hourly basis,fetching the data from the remote machine.Basically it gives me the list of all active users logged and its count once we execute the script.Here the count is...

2. Shell Programming and Scripting

Jump to next element in a loop

Hi, i want the loop to move to 3rd item, when it encounters 2 while runing for i in 1 2 3 4 5 6 do if then #jump to element 3 else echo $i fi done o/p 1 3 4 5 6

3. Shell Programming and Scripting

how to jump a shell !!

Hi, can someone point out a solution to my problem below. Within a shell script TEST.ksh I have to run two commands CmdA & CmdB one after the other as below. ------------- TEST.ksh #!/usr/bin/ksh A B ------------- I am running this script from KSH with PID 12345 as below. ...

LEARN ABOUT DEBIAN

pi_stress

pi_stress(8)						Linux System Administrator's Manual					      pi_stress(8)

NAME

       pi_stress - a stress test for POSIX Priority Inheritance mutexes

SYNOPSIS

       pi_stress  [-i|--inversions  inversions]  [-t|--duration  seconds]  [-g|--groups groups [-d|--debug] [-v|--verbose] [-s|--signal] [-r|--rr]
       [-p|--prompt] [-m|--mlockall] [-u|--uniprocessor]
       pi_stress -h|--help

DESCRIPTION

       pi_stress is a program used to stress the priority-inheritance code paths for POSIX mutexes, in both the Linux kernel and the C library. It
       runs  as  a  realtime-priority task and launches inversion machine thread groups. Each inversion group causes a priorty inversion condition
       that will deadlock if priority inheritance doesn't work.

OPTIONS

       -i n|--inversions=n
	      Run for n number of inversion conditions. This is the total number of inversions for all inversion groups. Default is -1	for  infi-
	      nite.

       -t n|--duration=n
	      Run the test for n seconds and then terminate.

       -g n|--groups=n
	      The number of inversion groups to run. Defaults to 10.

       -d|--debug
	      Run in debug mode; lots of extra prints

       -v|--verbose
	      Run with verbose messages

       -s|--signal
	      Terminate on receipt of SIGTERM (Ctrl-C). Default is to terminate on any keypress.

       -r|--rr
	      Run inversion group threads as SCHED_RR (round-robin). The default is to run the inversion threads as SCHED_FIFO.

       -p|--prompt
	      Prompt before actually starting the stress test

       -u|--uniprocessor
	      Run  all threads on one processor. The default is to run all inversion group threads on one processor and the admin threads (report-
	      ing thread, keyboard reader, etc.) on a different processor.

       -m|--mlockall
	      Call mlockall to lock current and future memory allocations and prevent being paged out

       -h|--help
	      Display a short help message and options.

CAVEATS

       The pi_stress test threads run as SCHED_FIFO or SCHED_RR threads, which means that they can starve critical system threads. It is advisable
       to  change the scheduling policy of critical system threads to be SCHED_FIFO prior to running pi_stress and use a priority of 10 or higher,
       to prevent those threads from being starved by the stress test.

BUGS

       No documented bugs.

AUTHOR

       Clark Williams <williams@redhat.com>

								   Nov 27, 2006 						      pi_stress(8)

Software Releases - RSS News