Wiimote This article will go through the basic steps required to have a working Wiimote in Linux for general use. It will not go into much detail for some steps as there are many guides already written for some parts already. Note: The approach shown on this page is based on software which is no longer developed upstream. There is a new effort on creating a Wii Remote driver based on the new Linux kernel Wii Remote driver. See XWiimote if you want to test the new Wii Remote software stack. Prerequisites Bluetooth cwiid Wiimote The most important piece required is Bluetooth, this must already be configured and running without the help of this guide. Connect the Wiimote First you need to make sure to load the uinput module: $ sudo modprobe uinput You should have a device in /dev/uinput now. Thanks to cwiid you can scan for your Wiimote now: (press the 1 and 2 buttons on your Wiimote) $ hcitool scan Scanning ... Input Device The Wiimote can act as a regular input device like a mouse using wminput. 1. 2.
CGI Tutorial: Forms Usually the information supplied by the QUERY_STRING variable should come from the user pressing buttons and entering text in the HTML document. It is this information we would like to package up and send to the CGI script. Each group of buttons and text boxes is called a form, and forms are enclosed between the HTML tags <form> ... </form>. <form action=" method="GET"> Some text in here. The action tag is the URL of the CGI script. Submit buttons A submit button is the input device that actually calls the URL. The result is a form which looks like this. If you click the submit button then the URL will be called. Checkboxes A checkbox is a simple on/off button. The result of this code is the following form Now if the submit button is clicked when the box is checked then the information lights=on is packaged into QUERY_STRING. Here is example HTML code for a form with two checkboxes and a message for each. Radio buttons Text boxes Exercise
Basic Linux Commands Basic Linux Commands mkdir - make directories Usage mkdir [OPTION] DIRECTORY Options Create the DIRECTORY(ies), if they do not already exist. Mandatory arguments to long options are mandatory for short options too. -m, mode=MODE set permission mode (as in chmod), not rwxrwxrwx - umask -p, parents no error if existing, make parent directories as needed -v, verbose print a message for each created directory -help display this help and exit -version output version information and exit cd - change directories Use cd to change directories. mv- change the name of a directory Type mv followed by the current name of a directory and the new name of the directory. Ex: mv testdir newnamedir pwd - print working directory will show you the full path to the directory you are currently in. rmdir - Remove an existing directory rm -r Removes directories and files within the directories recursively. chown - change file owner and group chown [OPTION] OWNER[:[GROUP]] FILE chown [OPTION] :GROUP FILE u - User who owns the file. bg
Mastering the VI editor Mastering the VI editor Mastering the VI editor (PDF format) Index Introduction The VI editor is a screen-based editor used by many Unix users. EX Commands Conventions In this tutorial, the following convention will be used: ^X denotes a control character. Before You Begin The VI editor uses the full screen, so it needs to know what kind of terminal you have. TERM = (vt100) If you know your terminal is a vt100 (or an emulator that can do vt100), just hit return for the terminal type when you log in. If you make an error when you log in and type the wrong terminal type, don't panic and log out. First, tell your shell what type of terminal you have. set term=vt100 For Bourne Shell (/bin/sh) or Korn Shell (/bin/ksh), the commands are the following: export TERM TERM=vt100 Next, reset your terminal with this command: tset Now that the terminal type is (hopefully) correctly set, you are ready to get started with VI. Starting the VI Editor The VI editor lets a user create new files or edit existing files. a h
Beat Detection Algorithms This document is to be distributed for free and without any modification from its original state. The author declines all responsibility in the damage this document or any of the things you will do with it might do to anyone or to anything. This document and any of its contents is not copyrighted and is free of all rights, you may thus use it, modify it or destroy it without breaking any international law. However according to the author's will, you may not use this document for commercial profit directly, but you may use indirectly its intellectual contents; in which case I would be pleased to receive a mail of notice or even thanks. This is my first tutorial and I am still a student, you must assume that this document is probably not free of small errors and bugs. In the same state of mind, those algorithms are not fully optimised, they are explained for pedagogical purposes and you may find some redundant computations or other voluntary clumsiness. 1 – Simple sound energy
CGI tutorial: Source files In case you are interested in how CGI scripts can be written, or if you want to compare your attempt at the exercises with mine, here are the Perl files used to generate them. Environment example: Generates an HTML document listing the values of (most of) the current environment variables. The endless document: Displays one of the many(!) pages of a document with infinitely many pages. It uses the QUERY_STRING environment variable to see what page it should generate and what the previous page was. The first page can be found at Linux Commands Cheat Sheet in Black & White Keep this linux cheat sheet on your desk printed, I am sure you will learn them quick and will be a linux expert very soon. We have added had both pdf and image (png) format of the cheat sheet. Please keep us posted if you need us to add more commands. Command are categorized 13 sections according its usage.We have designed the command in white color with black background as we often use on linux shell. We have added bit color for attraction :-). We have grouped commands in the below categories a) System b) Hardware c) Users d) File Commands e) Process Related f) File Permission g) Network h) Compression / Archives i) Install Packages j) Install Source k) Search l) Login m) File Transfer n) Directory Traverse Download linux cheat sheet in pdf format and refer each command in detail. Filed Under : LINUX COMMANDS
productivity - What is your most productive shortcut with Vim?