http://wiki.webos-internals.org/api.php?action=feedcontributions&user=Punzada&feedformat=atomWebOS Internals - User contributions [en]2024-03-29T13:04:29ZUser contributionsMediaWiki 1.35.1http://wiki.webos-internals.org/index.php?title=Linux_Tutorial_Irssi&diff=6546Linux Tutorial Irssi2009-10-17T02:51:00Z<p>Punzada: </p>
<hr />
<div>= Linux Tutorial - Irssi =<br />
<br />
=== Update 09/17/2009 === <br />
<br />
I have managed to get the [http://www.bitlbee.org/main.php/news.r.html BitlBee] service working with irssi for full AIM, MSN, Yahoo and Jabber support. I shall be doing my best to update this wiki with the best methods to get this working and configured easily and securely as soon as possible.<br />
<br />
=== This Document Assumes the following ===<br />
<br />
You have followed the procedure to Access Linux on the device and have enabled the Optware repositories and software [[Portal:Accessing_Linux]]<br />
<br />
You have installed the Terminal application [[Application:Terminal]]<br />
<br />
<br />
Once these procedures are done you should have access to:<br />
<br />
The Optware software repositories through ipkg-opt <br />
<br />
The Terminal Application through the WebOS (should load, be the root user, and function)<br />
<br />
<br />
<br />
== Installation ==<br />
<br />
Within the Terminal application use the following command:<br />
<br />
<pre><nowiki><br />
ipkg-opt install screen irssi perl<br />
</nowiki></pre><br />
<br />
This command will automatically download [http://www.gnu.org/software/screen/ GNU Screen] and [http://irssi.org/ irssi] as well as any necessary dependencies.<br />
<br />
Note: GNU Screen is *not* necessary for irssi to function, it only provides further functionality to be able to close the Terminal application if desired, keep irssi running in the background and reattach to it. Also, I have found that running irssi within a screen session gives irssi all its various colors while running natively within the terminal app leaves it mono-colored. <br />
<br />
<br />
== Usage ==<br />
<br />
In order to run irssi you simply need to type irssi into the Terminal application at the shell prompt and once hitting enter(return) it will load. <br />
<br />
However this is '''NOT RECOMMENDED''' as by default the Terminal Application is loaded as the root user and you should avoid using internet facing applications as the root user if it is not necessary (some IRC networks such as EFnet will go as far as to instantly disconnect you if it detects you are connecting to their servers as root). <br />
<br />
Once the Terminal Application is opened you may change to the user you set up when completing the steps to Access Linux via the su command<br />
<br />
example:<br />
<br />
<pre><nowiki><br />
root@castle:/var/home/root# su myuser<br />
myuser@castle:/var/home/root$<br />
</nowiki></pre><br />
<br />
from here you can simply enter irssi and hit return and it shall load.<br />
<br />
===Basic Commands===<br />
<br />
/connect ircserver<br />
<br />
This will connect you to an irc network ex: /connect irc.freenode.net will connect you to the freenode network.<br />
<br />
/join #channel<br />
<br />
This will join the requested channel, ex: /join #webos-internals<br />
<br />
Sym+n Will move to the 'next' window within the irssi interface<br />
Sym+p Will move you to the 'previous' window within the irssi interface<br />
<br />
You can directly jump to a window (numbered in irssi) by hitting Orange Key+Space+Number.<br />
<br />
===GNU Screen History & Basics===<br />
<br />
If you're like me and you want to always keep your irssi session active as well as have the colors available to you a good solution is to use GNU Screen.<br />
<br />
For those that don't know, screen acts as a window manager for terminal applications. Screen allows you to run multiple applications in a single terminal session, switch between the applications freely as well as being able to detach from it entirely, and reattach to it later while having those applications run in the background. Many consider screen to be one of the most important tools available for any type of command line work or administration - is is very powerful and very flexible, feel free to read up on it's customization and abilities to further enhance your experience with it.<br />
<br />
====Screen Usage====<br />
<br />
To start using screen it is very simple, follow the instructions above but before switching to your local user to run irssi, first type screen and hit enter<br />
<br />
You will be greeted with screen's opening text, letting you know that it is running, and the GPL license, simply press the space bar here and you will be taken back into the prompt and it will appear as if you're back to where you started.<br />
<br />
From this point on, follow the instructions above to change into your user that is not root, and open irssi like normal.<br />
<br />
You will see commands listed as such: Sym-A C <br />
<br />
This key combination is important because it means 'Press and hold Sym, then hit A, release both and hit C'<br />
<br />
This is how GNU Screen functions and is vital to it's usage, the example above creates a new window with a fresh terminal session.<br />
<br />
==== Attach / Detach ====<br />
<br />
In order to detach from your screen session use the command Sym-A D<br />
<br />
Once a session is detached you may close out of the terminal app and any applications running within your screen session will continue to run.<br />
<br />
In order to reattach to a session you left running, load the Terminal Application again and type the following at the command prompt and hit enter: screen -r<br />
<br />
<br />
==== Screen Commands To Know ====<br />
Sym-A C - Create a new window/terminal session<br />
<br />
Sym-A N - Change to next window/terminal session within the current screen session<br />
<br />
Sym-A P - Change to previous window/terminal session with the current screen session<br />
<br />
Sym-A D - Detach from current screen session<br />
<br />
== Bitlbee for Multi-IM ==<br />
<br />
[http://www.bitlbee.org/main.php/news.r.html BitlBee] is an IRC daemon that you can run to connect to basically all of the most popular IM protocols: XMPP/Jabber (including Google Talk), MSN Messenger, Yahoo! Messenger, AIM and ICQ.<br />
<br />
As of now we are able to install bitlbee on the linux subsystem, run it in daemon mode (I wasn't able to get it started with xinetd - will be investiating this further), launch it from a script when we wish to connect and set irssi to automatically connect, identify and load all of your IM accounts at once. <br />
<br />
'''The following procedure is how I have set mine up and there may be a sleeker/easier solution down the line. Try to think of this procedure as more "proof of concept" then "ready for the general public" '''<br />
<br />
<br />
<br />
first to install the necessary files (must be performed as root or privledged user with sudo from within the terminal application):<br />
<br />
<pre><nowiki><br />
ipkg-opt install screen irssi bitlbee perl<br />
</nowiki></pre><br />
<br />
=== Configure Bitlbee ===<br />
<br />
The only file that absolutely needs to be tweaked is located at /var/opt/etc/bitlbee/bitlbee.conf<br />
<br />
<pre><nowiki><br />
RunMode = Daemon<br />
<br />
User = myuser<br />
<br />
ConfigDir = /home/myuser/<br />
</nowiki></pre><br />
(note - replace myuser above with the user name set up when installing optware as shown above)<br />
edit the configuration file mentioned with your editor of choice as root (vi, nano, or copy it over and copy back with winscp - whatever works for you)<br />
make sure any of those values that are leading with a # have it removed otherwise the value will not be set and it will be seen as a comment.<br />
<br />
=== Startup Script ===<br />
<br />
This script will load the daemon on-demand (may even be better this way as using less resources when you don't want to IM) and will automatically put the shell to your username instead of root (so you can use irssi more securely off the bat)<br />
<br />
Create a file called "im" (without quotes) in your /var/home/root directory with the following:<br />
<br />
<pre><nowiki><br />
#!/bin/sh<br />
#load bitlbee daemon and automatically load screen with a regular user session<br />
/opt/sbin/bitlbee<br />
screen su myuser<br />
<br />
</nowiki></pre><br />
<br />
You may now run this script at any time by opening up the terminal app and typing ./im<br />
<br />
=== Configure Bitlbee for your IM clients ===<br />
<br />
Running the 'im' script that you have now made will bring you to a prompt featuring your username such as <br />
<pre><nowiki><br />
myuser@castle:/var/home/root$<br />
</nowiki></pre><br />
<br />
'''Important Note''' In order for these changes to take effect the filesystem must be mounted as writeable, to do that as root user (or through sudo) please use the following command<br />
<br />
<pre><nowiki><br />
mount -o remount,rw /<br />
</nowiki></pre><br />
<br />
and please remember to change it back to read-only when you're finished by doing<br />
<br />
<pre><nowiki><br />
mount -o remount,ro /<br />
</nowiki></pre> <br />
<br />
From your user shell, load up irssi.<br />
<br />
Once loaded you can connect to the bitlbee daemon by doing /connect localhost<br />
<br />
Move to the second window (sym+n or orange key+space+2) and you will be at the bitlbee control channel &bitlbee<br />
<br />
You can have a flushed out description (and possibly understanding) of the following procedure [http://princessleia.com/bitlbee.php Here] - I am simply going to sum up the commands quickly. Note ignore all < > 's within the commands fill this with the respective needed values.<br />
<br />
While on the bitlbee control channel:<br />
<br />
Global Registration Password (you will input this single password and bitlbee will automatically log in to any IM accounts you set up)<br />
<br />
<pre><nowiki><br />
register <password><br />
</nowiki></pre> <br />
<br />
Add an IM account to the service:<br />
<br />
<pre><nowiki><br />
account add <protocol> <username> <password> [<server>].<br />
</nowiki></pre> <br />
oscar is the protocol used by ICQ and AOL. For MSN use msn, for Yahoo use yahoo and for Jabber use jabber)<br />
<br />
For oscar, you need to specify the IM-server as a fourth argument (for msn and yahoo there is no fourth argument). <br />
<br />
For AOL Instant Messenger, the server name is login.oscar.aol.com. For ICQ, the server name is login.icq.com.<br />
<br />
Repeat this as many times as needed for any IM accounts.<br />
<br />
<br />
=== Configure irssi to automatically connect to Bitlbee ===<br />
<br />
'''Important Note''' Please make sure the above procedure to make the filesystem writable was done or these changes WILL NOT BE SAVED.<br />
<br />
Now that we have set up the start up script, configured bitlbee with our IM services of choice, now we will make it so that when irssi loads it will automatically connect to the bitlbee daemon and identify with it so you can immediately begin IM'ing.<br />
<br />
Perform the following commands while in irssi<br />
<br />
<pre><nowiki><br />
/NETWORK ADD -autosendcmd "/^msg &bitlbee identify password" Bitlbee<br />
</nowiki></pre><br />
(please replace password in the command above with the one you set for your global Bitlbee password)<br />
<br />
<pre><nowiki><br />
/SERVER ADD -auto -network Bitlbee localhost 6667<br />
</nowiki></pre><br />
<br />
=== Final Setup & Thoughts / Running ===<br />
<br />
At this point you should be entirely set up with bitlbee and irssi. Make sure you set your filesystem back to read-only (see above). A good test would be to restart your pre entirely after setup and perform the following procedure. <br />
<br />
To get to a fully functional irssi w/IM protocols through bitlbee is only a three step process:<br />
<br />
1. Load up terminal application<br />
<br />
2. at the prompt type<br />
<pre><nowiki><br />
./im<br />
</nowiki></pre><br />
<br />
3. at the user prompt that loads, type<br />
<pre><nowiki><br />
irssi<br />
</nowiki></pre><br />
<br />
and there you are, enjoy multiple IM protocol chats natively on your webos device.<br />
<br />
If you are a new user to screen it's easy to get lost in multiple embedded screen sessions and such, if you find yourself loading multiple copies of the bitlbee daemon and need them closed (or you're done with your IM sessions and want to conserve as much battery as possible) simply run the following command and it will kill the service:<br />
<br />
<pre><nowiki><br />
pkill bitlbee <br />
</nowiki></pre><br />
<br />
== Configuration/Tweaks ==<br />
<br />
Both irssi and GNU Screen are very rich applications with a plethora of scripts, customization and usage options that only a very small percentage of are covered in this document. If interested please search and find how you may be able to adjust them to fit your specific needs (and if you find anything worthwhile feel free to add it to this wiki!)<br />
<br />
For information on irssi please visit their startup documentation http://irssi.org/documentation/startup <br />
<br />
This site provides information that will help you in automating irssi to do tasks like autojoin set servers and channels and automatically identify your nickname with services. <br />
<br />
== Known Issues ==<br />
<br />
When first loaded irssi tends to not properly format to the whole screen and a simple rotation to let the terminal rotate to the side and back to standard typing position will fix it (you will see the characters slowly refresh during this process)<br />
<br />
Even with Screen running you can lose connection if the wifi radio turns off when the screen does, see http://www.webos-internals.org/wiki/Patch_webOS_Keep_Phone_Awake_While_in_Remote_Session<br />
<br />
[[Image:Terminal-irssi.jpg]]</div>Punzadahttp://wiki.webos-internals.org/index.php?title=Linux_Tutorial_Irssi&diff=6545Linux Tutorial Irssi2009-10-17T02:25:49Z<p>Punzada: </p>
<hr />
<div>= Linux Tutorial - Irssi =<br />
<br />
=== Update 09/17/2009 === <br />
<br />
I have managed to get the [http://www.bitlbee.org/main.php/news.r.html BitlBee] service working with irssi for full AIM, MSN, Yahoo and Jabber support. I shall be doing my best to update this wiki with the best methods to get this working and configured easily and securely as soon as possible.<br />
<br />
=== This Document Assumes the following ===<br />
<br />
You have followed the procedure to Access Linux on the device and have enabled the Optware repositories and software [[Portal:Accessing_Linux]]<br />
<br />
You have installed the Terminal application [[Application:Terminal]]<br />
<br />
<br />
Once these procedures are done you should have access to:<br />
<br />
The Optware software repositories through ipkg-opt <br />
<br />
The Terminal Application through the WebOS (should load, be the root user, and function)<br />
<br />
<br />
<br />
== Installation ==<br />
<br />
Within the Terminal application use the following command:<br />
<br />
<pre><nowiki><br />
ipkg-opt install -o /var screen irssi perl<br />
</nowiki></pre><br />
<br />
This command will automatically download [http://www.gnu.org/software/screen/ GNU Screen] and [http://irssi.org/ irssi] as well as any necessary dependencies.<br />
<br />
Note: GNU Screen is *not* necessary for irssi to function, it only provides further functionality to be able to close the Terminal application if desired, keep irssi running in the background and reattach to it. Also, I have found that running irssi within a screen session gives irssi all its various colors while running natively within the terminal app leaves it mono-colored. <br />
<br />
<br />
== Usage ==<br />
<br />
In order to run irssi you simply need to type irssi into the Terminal application at the shell prompt and once hitting enter(return) it will load. <br />
<br />
However this is '''NOT RECOMMENDED''' as by default the Terminal Application is loaded as the root user and you should avoid using internet facing applications as the root user if it is not necessary (some IRC networks such as EFnet will go as far as to instantly disconnect you if it detects you are connecting to their servers as root). <br />
<br />
Once the Terminal Application is opened you may change to the user you set up when completing the steps to Access Linux via the su command<br />
<br />
example:<br />
<br />
<pre><nowiki><br />
root@castle:/var/home/root# su myuser<br />
myuser@castle:/var/home/root$<br />
</nowiki></pre><br />
<br />
from here you can simply enter irssi and hit return and it shall load.<br />
<br />
===Basic Commands===<br />
<br />
/connect ircserver<br />
<br />
This will connect you to an irc network ex: /connect irc.freenode.net will connect you to the freenode network.<br />
<br />
/join #channel<br />
<br />
This will join the requested channel, ex: /join #webos-internals<br />
<br />
Sym+n Will move to the 'next' window within the irssi interface<br />
Sym+p Will move you to the 'previous' window within the irssi interface<br />
<br />
You can directly jump to a window (numbered in irssi) by hitting Orange Key+Space+Number.<br />
<br />
===GNU Screen History & Basics===<br />
<br />
If you're like me and you want to always keep your irssi session active as well as have the colors available to you a good solution is to use GNU Screen.<br />
<br />
For those that don't know, screen acts as a window manager for terminal applications. Screen allows you to run multiple applications in a single terminal session, switch between the applications freely as well as being able to detach from it entirely, and reattach to it later while having those applications run in the background. Many consider screen to be one of the most important tools available for any type of command line work or administration - is is very powerful and very flexible, feel free to read up on it's customization and abilities to further enhance your experience with it.<br />
<br />
====Screen Usage====<br />
<br />
To start using screen it is very simple, follow the instructions above but before switching to your local user to run irssi, first type screen and hit enter<br />
<br />
You will be greeted with screen's opening text, letting you know that it is running, and the GPL license, simply press the space bar here and you will be taken back into the prompt and it will appear as if you're back to where you started.<br />
<br />
From this point on, follow the instructions above to change into your user that is not root, and open irssi like normal.<br />
<br />
You will see commands listed as such: Sym-A C <br />
<br />
This key combination is important because it means 'Press and hold Sym, then hit A, release both and hit C'<br />
<br />
This is how GNU Screen functions and is vital to it's usage, the example above creates a new window with a fresh terminal session.<br />
<br />
==== Attach / Detach ====<br />
<br />
In order to detach from your screen session use the command Sym-A D<br />
<br />
Once a session is detached you may close out of the terminal app and any applications running within your screen session will continue to run.<br />
<br />
In order to reattach to a session you left running, load the Terminal Application again and type the following at the command prompt and hit enter: screen -r<br />
<br />
<br />
==== Screen Commands To Know ====<br />
Sym-A C - Create a new window/terminal session<br />
<br />
Sym-A N - Change to next window/terminal session within the current screen session<br />
<br />
Sym-A P - Change to previous window/terminal session with the current screen session<br />
<br />
Sym-A D - Detach from current screen session<br />
<br />
== Bitlbee for Multi-IM ==<br />
<br />
[http://www.bitlbee.org/main.php/news.r.html BitlBee] is an IRC daemon that you can run to connect to basically all of the most popular IM protocols: XMPP/Jabber (including Google Talk), MSN Messenger, Yahoo! Messenger, AIM and ICQ.<br />
<br />
As of now we are able to install bitlbee on the linux subsystem, run it in daemon mode (I wasn't able to get it started with xinetd - will be investiating this further), launch it from a script when we wish to connect and set irssi to automatically connect, identify and load all of your IM accounts at once. <br />
<br />
'''The following procedure is how I have set mine up and there may be a sleeker/easier solution down the line. Try to think of this procedure as more "proof of concept" then "ready for the general public" '''<br />
<br />
<br />
<br />
first to install the necessary files (must be performed as root or privledged user with sudo from within the terminal application):<br />
<br />
<pre><nowiki><br />
ipkg-opt install -o /var screen irssi bitlbee perl<br />
</nowiki></pre><br />
<br />
=== Configure Bitlbee ===<br />
<br />
The only file that absolutely needs to be tweaked is located at /var/opt/etc/bitlbee/bitlbee.conf<br />
<br />
<pre><nowiki><br />
RunMode = Daemon<br />
<br />
User = myuser<br />
<br />
ConfigDir = /home/myuser/<br />
</nowiki></pre><br />
(note - replace myuser above with the user name set up when installing optware as shown above)<br />
edit the configuration file mentioned with your editor of choice as root (vi, nano, or copy it over and copy back with winscp - whatever works for you)<br />
make sure any of those values that are leading with a # have it removed otherwise the value will not be set and it will be seen as a comment.<br />
<br />
=== Startup Script ===<br />
<br />
This script will load the daemon on-demand (may even be better this way as using less resources when you don't want to IM) and will automatically put the shell to your username instead of root (so you can use irssi more securely off the bat)<br />
<br />
Create a file called "im" (without quotes) in your /var/home/root directory with the following:<br />
<br />
<pre><nowiki><br />
#!/bin/sh<br />
#load bitlbee daemon and automatically load screen with a regular user session<br />
/var/opt/sbin/bitlbee<br />
screen su myuser<br />
<br />
</nowiki></pre><br />
<br />
You may now run this script at any time by opening up the terminal app and typing ./im<br />
<br />
=== Configure Bitlbee for your IM clients ===<br />
<br />
Running the 'im' script that you have now made will bring you to a prompt featuring your username such as <br />
<pre><nowiki><br />
myuser@castle:/var/home/root$<br />
</nowiki></pre><br />
<br />
'''Important Note''' In order for these changes to take effect the filesystem must be mounted as writeable, to do that as root user (or through sudo) please use the following command<br />
<br />
<pre><nowiki><br />
mount -o remount,rw /<br />
</nowiki></pre><br />
<br />
and please remember to change it back to read-only when you're finished by doing<br />
<br />
<pre><nowiki><br />
mount -o remount,ro /<br />
</nowiki></pre> <br />
<br />
From your user shell, load up irssi.<br />
<br />
Once loaded you can connect to the bitlbee daemon by doing /connect localhost<br />
<br />
Move to the second window (sym+n or orange key+space+2) and you will be at the bitlbee control channel &bitlbee<br />
<br />
You can have a flushed out description (and possibly understanding) of the following procedure [http://princessleia.com/bitlbee.php Here] - I am simply going to sum up the commands quickly. Note ignore all < > 's within the commands fill this with the respective needed values.<br />
<br />
While on the bitlbee control channel:<br />
<br />
Global Registration Password (you will input this single password and bitlbee will automatically log in to any IM accounts you set up)<br />
<br />
<pre><nowiki><br />
register <password><br />
</nowiki></pre> <br />
<br />
Add an IM account to the service:<br />
<br />
<pre><nowiki><br />
account add <protocol> <username> <password> [<server>].<br />
</nowiki></pre> <br />
oscar is the protocol used by ICQ and AOL. For MSN use msn, for Yahoo use yahoo and for Jabber use jabber)<br />
<br />
For oscar, you need to specify the IM-server as a fourth argument (for msn and yahoo there is no fourth argument). <br />
<br />
For AOL Instant Messenger, the server name is login.oscar.aol.com. For ICQ, the server name is login.icq.com.<br />
<br />
Repeat this as many times as needed for any IM accounts.<br />
<br />
<br />
=== Configure irssi to automatically connect to Bitlbee ===<br />
<br />
'''Important Note''' Please make sure the above procedure to make the filesystem writable was done or these changes WILL NOT BE SAVED.<br />
<br />
Now that we have set up the start up script, configured bitlbee with our IM services of choice, now we will make it so that when irssi loads it will automatically connect to the bitlbee daemon and identify with it so you can immediately begin IM'ing.<br />
<br />
Perform the following commands while in irssi<br />
<br />
<pre><nowiki><br />
/NETWORK ADD -autosendcmd "/^msg &bitlbee identify password" Bitlbee<br />
</nowiki></pre><br />
(please replace password in the command above with the one you set for your global Bitlbee password)<br />
<br />
<pre><nowiki><br />
/SERVER ADD -auto -network Bitlbee localhost 6667<br />
</nowiki></pre><br />
<br />
=== Final Setup & Thoughts / Running ===<br />
<br />
At this point you should be entirely set up with bitlbee and irssi. Make sure you set your filesystem back to read-only (see above). A good test would be to restart your pre entirely after setup and perform the following procedure. <br />
<br />
To get to a fully functional irssi w/IM protocols through bitlbee is only a three step process:<br />
<br />
1. Load up terminal application<br />
<br />
2. at the prompt type<br />
<pre><nowiki><br />
./im<br />
</nowiki></pre><br />
<br />
3. at the user prompt that loads, type<br />
<pre><nowiki><br />
irssi<br />
</nowiki></pre><br />
<br />
and there you are, enjoy multiple IM protocol chats natively on your webos device.<br />
<br />
If you are a new user to screen it's easy to get lost in multiple embedded screen sessions and such, if you find yourself loading multiple copies of the bitlbee daemon and need them closed (or you're done with your IM sessions and want to conserve as much battery as possible) simply run the following command and it will kill the service:<br />
<br />
<pre><nowiki><br />
pkill bitlbee <br />
</nowiki></pre><br />
<br />
== Configuration/Tweaks ==<br />
<br />
Both irssi and GNU Screen are very rich applications with a plethora of scripts, customization and usage options that only a very small percentage of are covered in this document. If interested please search and find how you may be able to adjust them to fit your specific needs (and if you find anything worthwhile feel free to add it to this wiki!)<br />
<br />
For information on irssi please visit their startup documentation http://irssi.org/documentation/startup <br />
<br />
This site provides information that will help you in automating irssi to do tasks like autojoin set servers and channels and automatically identify your nickname with services. <br />
<br />
== Known Issues ==<br />
<br />
When first loaded irssi tends to not properly format to the whole screen and a simple rotation to let the terminal rotate to the side and back to standard typing position will fix it (you will see the characters slowly refresh during this process)<br />
<br />
Even with Screen running you can lose connection if the wifi radio turns off when the screen does, see http://www.webos-internals.org/wiki/Patch_webOS_Keep_Phone_Awake_While_in_Remote_Session<br />
<br />
[[Image:Terminal-irssi.jpg]]</div>Punzadahttp://wiki.webos-internals.org/index.php?title=Portal:Linux_Applications&diff=6363Portal:Linux Applications2009-10-08T05:08:18Z<p>Punzada: </p>
<hr />
<div>__notoc__<br />
{{reorganize|This page needs to be reorganized still.}}<br />
{{portal-header<br />
|The Pre runs a very standard Linux on a commonly available processor. Very soon after access was achieved to the Linux, the Optware team made the entire catalog of Optware packages available on the pre. <br />
<br />
More about the Optware project here: [http://www.nslu2-linux.org/wiki/Optware/Packages Optware Packages].<br />
<br />
You can view a list of available packages here: [http://ipkg.nslu2-linux.org/feeds/optware/cs08q1armel/cross/unstable/ List of Packages].<br />
<br />
The community has been busy porting other applications to the Pre. Some of those are listed, and have pages for them below.<br />
}}<br />
{{portal-three-columns<br />
|column1=<br />
* [[Portal:Linux_Applications_All|All]]<br />
* [[Portal:Linux_Applications_Business|Business]]<br />
* [[Portal:Linux_Applications_Communications|Communications]]<br />
* [[Portal:Linux_Applications_Entertainment|Entertainment]]<br />
<br />
|column2=<br />
* [[Portal:Linux_Applications_Food|Food]]<br />
* [[Portal:Linux_Applications_Games|Games]]<br />
* [[Portal:Linux_Applications_Lifestyle|Lifestyle]]<br />
* [[Portal:Linux_Applications_News|News]]<br />
<br />
|column3=<br />
* [[Portal:Linux_Applications_Social Networking|Social Networking]]<br />
* [[Portal:Linux_Applications_Tutorial|Tutorial]]<br />
* [[Portal:Linux_Applications_Utilities|Utilities]]<br />
* [[Portal:Linux_Applications_Productivity|Productivity]]<br />
}}<br />
{{portal-two-columns<br />
|column1=<br />
== Application Tutorials ==<br />
<br />
'''[[Portal:Accessing Linux|Follow the Accessing Linux Article First]]'''<br />
* [[Ad-Hoc_Networking|Ad-Hoc Networking]]<br />
* [[Ajaxterm]]<br />
* [[Apache]]<br />
* [[Colorful_Bash_Prompt|Colorful Bash Prompt]]<br />
* [[Diff]]<br />
* [[Tutorials_Linux_DDNS_for_EVDO|Dynamic DNS for EVDO]]<br />
* [[DFBTerm DirectFB Terminal Emulator|DFBTerm DirectFB Terminal Emulator]] <br />
* [[Graphical Shell with WebShell|Graphical Shell with WebShell]] <br />
* [[GUI Text Editors|GUI Text Editors]] <br />
* [[HamachiVPN|HamachiVPN]] <br />
* [[How To Use "ls" In Color|How To Use "ls" In Color]] <br />
* [[Linux Tutorial Irssi|Linux Tutorial Irssi]]<br />
* [[Linux Tutorial Snownews|Linux Tutorial Snownews]]<br />
* [[Lighttpd|Lighttpd ]] <br />
* [[OpenVPN for Palm Pre|OpenVPN for Palm Pre]] <br />
* [[Tutorials_Linux_opt_on_loopback|/opt on loopback image on /media/internal]]<br />
* [[PalmVNC Terminal|PalmVNC Terminal]] <br />
* [[QEMU|QEMU]] <br />
* [[QEMU webOS Emulation|QEMU webOS Emulation]] <br />
* [[Running webOS in QEMU|Running webOS in QEMU]] <br />
* [[Replace "vi" with Fullscreen Text Editor "joe" or "nano"|Replace "vi" with Fullscreen Text Editor "joe" or "nano"]] <br />
* [[rTorrent]] <br />
* [[Setup Bash|Setup Bash]] <br />
* [[Samba Access|Samba Access]] <br />
* [[VNC (Virtual Network Computing)|VNC (Virtual Network Computing)]] <br />
* [[Vala Terminal|Vala Terminal]] <br />
* [[Wireless Music Sync with Amarok 1.4|Wireless Music Sync with Amarok 1.4]]<br />
<br />
== Want to write a tutorial and Add it? ==<br />
<br />
Just name the tutorial with<br />
<br />
"Tutorials Linux " + name<br />
<br />
Ex: Tutorials_Linux_Getting_Started<br /><br />
(spaces are the same thing as underscores)<br />
<br />
|column2=<br />
== Policies about adding Applications ==<br />
<br />
Your application can be any progress (Completed/Beta/Design Phase), just make sure you have a temporary name. For example if your application is called "Testing This":<br />
<br />
<source lang="text"><br />
{{portal-application-item<br />
|name=Asteroids<br />
|article=Asteroids<br />
|user=AWESOM-O<br />
|site=http://domain.com/asteroids/<br />
|description=This is a short description, leave screenshots<br />
and other details for the application page.<br />
<br />
}}<br />
</source><br />
<br />
<br />
Place this under the [[Portal:Linux Applications All|All Linux Application Portal]], and the category it goes under (for instance "Games" if it is a game). You can always change the applications name just make sure it is not taken and let us know on the [[Admin_Changes|Admin Changes]] page so we can delete the old application page (so others can use it).<br />
<br />
}}</div>Punzadahttp://wiki.webos-internals.org/index.php?title=Linux_Tutorial_Snownews&diff=6362Linux Tutorial Snownews2009-10-08T05:05:26Z<p>Punzada: New page: = Linux Tutorial - Snownews = [http://kiza.kcore.de/software/snownews/ Snownews] is a text mode RSS/RDF newsreader. It supports all versions of RSS natively and supports other formats vi...</p>
<hr />
<div>= Linux Tutorial - Snownews =<br />
<br />
<br />
[http://kiza.kcore.de/software/snownews/ Snownews] is a text mode RSS/RDF newsreader. It supports all versions of RSS natively and supports other formats via plugins.<br />
<br />
<br />
<br />
=== This Document Assumes the following ===<br />
<br />
You have followed the procedure to Access Linux on the device and have enabled the Optware repositories and software [[Portal:Accessing_Linux]]<br />
<br />
You have installed the Terminal application [[Application:Terminal]]<br />
<br />
<br />
Once these procedures are done you should have access to:<br />
<br />
The Optware software repositories through ipkg-opt <br />
<br />
The Terminal Application through the WebOS (should load, be the root user, and function)<br />
<br />
<br />
== Installation ==<br />
<br />
Within the terminal application, enter the following command for installation:<br />
<br />
<pre><nowiki><br />
ipkg-opt install -o /var snownews<br />
</nowiki></pre><br />
<br />
<br />
== Configuration ==<br />
<br />
This setting will make it so that feed items will load in the built-in webOS browser.<br />
<br />
Once loaded (simply type snownews within the terminal app), press B (shift+b) and place the following code into the box, and then hit enter.<br />
<pre><nowiki><br />
luna-send -n 1 palm://com.palm.applicationManager/launch {\"id\":\"com.palm.app.browser\",\"params\":{\"scene\":\"page\",\"target\":\"%s\"}}<br />
</nowiki></pre><br />
<br />
<br />
== Basic Commands ==<br />
<br />
a = add an rss feed<br />
<br />
B = change browser settings<br />
<br />
D (shift+d) = delete an rss feed<br />
<br />
Up/Down Arrow = highlight feed/story<br />
<br />
Enter = select feed/story<br />
<br />
m = mark all read (within a feed does all the items, at the main list does all the feeds)<br />
<br />
o = open site/feed item in browser<br />
<br />
<br />
== Known Issues ==<br />
<br />
Up/Down arrows are set by default within the Terminal App as:<br />
<br />
Up Gesture area - 2 <br />
<br />
Down Gesture area - 8<br />
<br />
which makes typical usage slightly clunky. I will look into setting different keybindings for either snownews or the terminal application itself to help correct this.</div>Punzadahttp://wiki.webos-internals.org/index.php?title=Linux_Tutorial_Irssi&diff=5889Linux Tutorial Irssi2009-09-24T07:49:50Z<p>Punzada: </p>
<hr />
<div>= Linux Tutorial - Irssi =<br />
<br />
=== Update 09/17/2009 === <br />
<br />
I have managed to get the [http://www.bitlbee.org/main.php/news.r.html BitlBee] service working with irssi for full AIM, MSN, Yahoo and Jabber support. I shall be doing my best to update this wiki with the best methods to get this working and configured easily and securely as soon as possible.<br />
<br />
=== This Document Assumes the following ===<br />
<br />
You have followed the procedure to Access Linux on the device and have enabled the Optware repositories and software [[Portal:Accessing_Linux]]<br />
<br />
You have installed the Terminal application [[Application:Terminal]]<br />
<br />
<br />
Once these procedures are done you should have access to:<br />
<br />
The Optware software repositories through ipkg-opt <br />
<br />
The Terminal Application through the WebOS (should load, be the root user, and function)<br />
<br />
<br />
<br />
== Installation ==<br />
<br />
Within the Terminal application use the following command:<br />
<br />
<pre><nowiki><br />
ipkg-opt install -o /var screen irssi perl<br />
</nowiki></pre><br />
<br />
This command will automatically download [http://www.gnu.org/software/screen/ GNU Screen] and [http://irssi.org/ irssi] as well as any necessary dependencies.<br />
<br />
Note: GNU Screen is *not* necessary for irssi to function, it only provides further functionality to be able to close the Terminal application if desired, keep irssi running in the background and reattach to it. Also, I have found that running irssi within a screen session gives irssi all its various colors while running natively within the terminal app leaves it mono-colored. <br />
<br />
<br />
== Usage ==<br />
<br />
In order to run irssi you simply need to type irssi into the Terminal application at the shell prompt and once hitting enter(return) it will load. <br />
<br />
However this is '''NOT RECOMMENDED''' as by default the Terminal Application is loaded as the root user and you should avoid using internet facing applications as the root user if it is not necessary (some IRC networks such as EFnet will go as far as to instantly disconnect you if it detects you are connecting to their servers as root). <br />
<br />
Once the Terminal Application is opened you may change to the user you set up when completing the steps to Access Linux via the su command<br />
<br />
example:<br />
<br />
<pre><nowiki><br />
root@castle:/var/home/root# su myuser<br />
myuser@castle:/var/home/root$<br />
</nowiki></pre><br />
<br />
from here you can simply enter irssi and hit return and it shall load.<br />
<br />
===Basic Commands===<br />
<br />
/connect ircserver<br />
<br />
This will connect you to an irc network ex: /connect irc.freenode.net will connect you to the freenode network.<br />
<br />
/join #channel<br />
<br />
This will join the requested channel, ex: /join #webos-internals<br />
<br />
Sym+n Will move to the 'next' window within the irssi interface<br />
Sym+p Will move you to the 'previous' window within the irssi interface<br />
<br />
You can directly jump to a window (numbered in irssi) by hitting Orange Key+Space+Number.<br />
<br />
===GNU Screen History & Basics===<br />
<br />
If you're like me and you want to always keep your irssi session active as well as have the colors available to you a good solution is to use GNU Screen.<br />
<br />
For those that don't know, screen acts as a window manager for terminal applications. Screen allows you to run multiple applications in a single terminal session, switch between the applications freely as well as being able to detach from it entirely, and reattach to it later while having those applications run in the background. Many consider screen to be one of the most important tools available for any type of command line work or administration - is is very powerful and very flexible, feel free to read up on it's customization and abilities to further enhance your experience with it.<br />
<br />
====Screen Usage====<br />
<br />
To start using screen it is very simple, follow the instructions above but before switching to your local user to run irssi, first type screen and hit enter<br />
<br />
You will be greeted with screen's opening text, letting you know that it is running, and the GPL license, simply press the space bar here and you will be taken back into the prompt and it will appear as if you're back to where you started.<br />
<br />
From this point on, follow the instructions above to change into your user that is not root, and open irssi like normal.<br />
<br />
You will see commands listed as such: Sym-A C <br />
<br />
This key combination is important because it means 'Press and hold Sym, then hit A, release both and hit C'<br />
<br />
This is how GNU Screen functions and is vital to it's usage, the example above creates a new window with a fresh terminal session.<br />
<br />
==== Attach / Detach ====<br />
<br />
In order to detach from your screen session use the command Sym-A D<br />
<br />
Once a session is detached you may close out of the terminal app and any applications running within your screen session will continue to run.<br />
<br />
In order to reattach to a session you left running, load the Terminal Application again and type the following at the command prompt and hit enter: screen -r<br />
<br />
<br />
==== Screen Commands To Know ====<br />
Sym-A C - Create a new window/terminal session<br />
<br />
Sym-A N - Change to next window/terminal session within the current screen session<br />
<br />
Sym-A P - Change to previous window/terminal session with the current screen session<br />
<br />
Sym-A D - Detach from current screen session<br />
<br />
== Bitlbee for Multi-IM ==<br />
<br />
[http://www.bitlbee.org/main.php/news.r.html BitlBee] is an IRC daemon that you can run to connect to basically all of the most popular IM protocols: XMPP/Jabber (including Google Talk), MSN Messenger, Yahoo! Messenger, AIM and ICQ.<br />
<br />
As of now we are able to install bitlbee on the linux subsystem, run it in daemon mode (I wasn't able to get it started with xinetd - will be investiating this further), launch it from a script when we wish to connect and set irssi to automatically connect, identify and load all of your IM accounts at once. <br />
<br />
'''The following procedure is how I have set mine up and there may be a sleeker/easier solution down the line. Try to think of this procedure as more "proof of concept" then "ready for the general public" '''<br />
<br />
<br />
<br />
first to install the necessary files (must be performed as root or privledged user with sudo from within the terminal application):<br />
<br />
<pre><nowiki><br />
ipkg-opt install -o /var screen irssi bitlbee perl<br />
</nowiki></pre><br />
<br />
=== Configure Bitlbee ===<br />
<br />
The only file that absolutely needs to be tweaked is located at /var/opt/etc/bitlbee/bitlbee.conf<br />
<br />
<pre><nowiki><br />
RunMode = Daemon<br />
<br />
User = myuser<br />
<br />
ConfigDir = /home/myuser/<br />
</nowiki></pre><br />
(note - replace myuser above with the user name set up when installing optware as shown above)<br />
edit the configuration file mentioned with your editor of choice as root (vi, nano, or copy it over and copy back with winscp - whatever works for you)<br />
make sure any of those values that are leading with a # have it removed otherwise the value will not be set and it will be seen as a comment.<br />
<br />
=== Startup Script ===<br />
<br />
This script will load the daemon on-demand (may even be better this way as using less resources when you don't want to IM) and will automatically put the shell to your username instead of root (so you can use irssi more securely off the bat)<br />
<br />
Create a file called "im" (without quotes) in your /var/home/root directory with the following:<br />
<br />
<pre><nowiki><br />
#!/bin/sh<br />
#load bitlbee daemon and automatically load screen with a regular user session<br />
/opt/sbin/bitlbee<br />
screen su myuser<br />
<br />
</nowiki></pre><br />
<br />
You may now run this script at any time by opening up the terminal app and typing ./im<br />
<br />
=== Configure Bitlbee for your IM clients ===<br />
<br />
Running the 'im' script that you have now made will bring you to a prompt featuring your username such as <br />
<pre><nowiki><br />
myuser@castle:/var/home/root$<br />
</nowiki></pre><br />
<br />
'''Important Note''' In order for these changes to take effect the filesystem must be mounted as writeable, to do that as root user (or through sudo) please use the following command<br />
<br />
<pre><nowiki><br />
mount -o remount,rw /<br />
</nowiki></pre><br />
<br />
and please remember to change it back to read-only when you're finished by doing<br />
<br />
<pre><nowiki><br />
mount -o remount,ro /<br />
</nowiki></pre> <br />
<br />
From your user shell, load up irssi.<br />
<br />
Once loaded you can connect to the bitlbee daemon by doing /connect localhost<br />
<br />
Move to the second window (sym+n or orange key+space+2) and you will be at the bitlbee control channel &bitlbee<br />
<br />
You can have a flushed out description (and possibly understanding) of the following procedure [http://princessleia.com/bitlbee.php Here] - I am simply going to sum up the commands quickly. Note ignore all < > 's within the commands fill this with the respective needed values.<br />
<br />
While on the bitlbee control channel:<br />
<br />
Global Registration Password (you will input this single password and bitlbee will automatically log in to any IM accounts you set up)<br />
<br />
<pre><nowiki><br />
register <password><br />
</nowiki></pre> <br />
<br />
Add an IM account to the service:<br />
<br />
<pre><nowiki><br />
account add <protocol> <username> <password> [<server>].<br />
</nowiki></pre> <br />
oscar is the protocol used by ICQ and AOL. For MSN use msn, for Yahoo use yahoo and for Jabber use jabber)<br />
<br />
For oscar, you need to specify the IM-server as a fourth argument (for msn and yahoo there is no fourth argument). <br />
<br />
For AOL Instant Messenger, the server name is login.oscar.aol.com. For ICQ, the server name is login.icq.com.<br />
<br />
Repeat this as many times as needed for any IM accounts.<br />
<br />
<br />
=== Configure irssi to automatically connect to Bitlbee ===<br />
<br />
'''Important Note''' Please make sure the above procedure to make the filesystem writable was done or these changes WILL NOT BE SAVED.<br />
<br />
Now that we have set up the start up script, configured bitlbee with our IM services of choice, now we will make it so that when irssi loads it will automatically connect to the bitlbee daemon and identify with it so you can immediately begin IM'ing.<br />
<br />
Perform the following commands while in irssi<br />
<br />
<pre><nowiki><br />
/NETWORK ADD -autosendcmd "/^msg &bitlbee identify password" Bitlbee<br />
</nowiki></pre><br />
(please replace password in the command above with the one you set for your global Bitlbee password)<br />
<br />
<pre><nowiki><br />
/SERVER ADD -auto -network Bitlbee localhost 6667<br />
</nowiki></pre><br />
<br />
=== Final Setup & Thoughts / Running ===<br />
<br />
At this point you should be entirely set up with bitlbee and irssi. Make sure you set your filesystem back to read-only (see above). A good test would be to restart your pre entirely after setup and perform the following procedure. <br />
<br />
To get to a fully functional irssi w/IM protocols through bitlbee is only a three step process:<br />
<br />
1. Load up terminal application<br />
<br />
2. at the prompt type<br />
<pre><nowiki><br />
./im<br />
</nowiki></pre><br />
<br />
3. at the user prompt that loads, type<br />
<pre><nowiki><br />
irssi<br />
</nowiki></pre><br />
<br />
and there you are, enjoy multiple IM protocol chats natively on your webos device.<br />
<br />
If you are a new user to screen it's easy to get lost in multiple embedded screen sessions and such, if you find yourself loading multiple copies of the bitlbee daemon and need them closed (or you're done with your IM sessions and want to conserve as much battery as possible) simply run the following command and it will kill the service:<br />
<br />
<pre><nowiki><br />
pkill bitlbee <br />
</nowiki></pre><br />
<br />
== Configuration/Tweaks ==<br />
<br />
Both irssi and GNU Screen are very rich applications with a plethora of scripts, customization and usage options that only a very small percentage of are covered in this document. If interested please search and find how you may be able to adjust them to fit your specific needs (and if you find anything worthwhile feel free to add it to this wiki!)<br />
<br />
For information on irssi please visit their startup documentation http://irssi.org/documentation/startup <br />
<br />
This site provides information that will help you in automating irssi to do tasks like autojoin set servers and channels and automatically identify your nickname with services. <br />
<br />
== Known Issues ==<br />
<br />
When first loaded irssi tends to not properly format to the whole screen and a simple rotation to let the terminal rotate to the side and back to standard typing position will fix it (you will see the characters slowly refresh during this process)<br />
<br />
Even with Screen running you can lose connection if the wifi radio turns off when the screen does, see http://www.webos-internals.org/wiki/Patch_webOS_Keep_Phone_Awake_While_in_Remote_Session<br />
<br />
[[Image:Terminal-irssi.jpg]]</div>Punzadahttp://wiki.webos-internals.org/index.php?title=Linux_Tutorial_Irssi&diff=5873Linux Tutorial Irssi2009-09-23T01:33:16Z<p>Punzada: </p>
<hr />
<div>= Linux Tutorial - Irssi =<br />
<br />
=== Update 09/17/2009 === <br />
<br />
I have managed to get the [http://www.bitlbee.org/main.php/news.r.html BitlBee] service working with irssi for full AIM, MSN, Yahoo and Jabber support. I shall be doing my best to update this wiki with the best methods to get this working and configured easily and securely as soon as possible.<br />
<br />
=== This Document Assumes the following ===<br />
<br />
You have followed the procedure to Access Linux on the device and have enabled the Optware repositories and software [[Portal:Accessing_Linux]]<br />
<br />
You have installed the Terminal application [[Application:Terminal]]<br />
<br />
<br />
Once these procedures are done you should have access to:<br />
<br />
The Optware software repositories through ipkg-opt <br />
<br />
The Terminal Application through the WebOS (should load, be the root user, and function)<br />
<br />
<br />
<br />
== Installation ==<br />
<br />
Within the Terminal application use the following command:<br />
<br />
<pre><nowiki><br />
ipkg-opt install -o /var screen irssi perl<br />
</nowiki></pre><br />
<br />
This command will automatically download [http://www.gnu.org/software/screen/ GNU Screen] and [http://irssi.org/ irssi] as well as any necessary dependencies.<br />
<br />
Note: GNU Screen is *not* necessary for irssi to function, it only provides further functionality to be able to close the Terminal application if desired, keep irssi running in the background and reattach to it. Also, I have found that running irssi within a screen session gives irssi all its various colors while running natively within the terminal app leaves it mono-colored. <br />
<br />
<br />
== Usage ==<br />
<br />
In order to run irssi you simply need to type irssi into the Terminal application at the shell prompt and once hitting enter(return) it will load. <br />
<br />
However this is '''NOT RECOMMENDED''' as by default the Terminal Application is loaded as the root user and you should avoid using internet facing applications as the root user if it is not necessary (some IRC networks such as EFnet will go as far as to instantly disconnect you if it detects you are connecting to their servers as root). <br />
<br />
Once the Terminal Application is opened you may change to the user you set up when completing the steps to Access Linux via the su command<br />
<br />
example:<br />
<br />
<pre><nowiki><br />
root@castle:/var/home/root# su myuser<br />
myuser@castle:/var/home/root$<br />
</nowiki></pre><br />
<br />
from here you can simply enter irssi and hit return and it shall load.<br />
<br />
===Basic Commands===<br />
<br />
/connect ircserver<br />
<br />
This will connect you to an irc network ex: /connect irc.freenode.net will connect you to the freenode network.<br />
<br />
/join #channel<br />
<br />
This will join the requested channel, ex: /join #webos-internals<br />
<br />
Sym+n Will move to the 'next' window within the irssi interface<br />
Sym+p Will move you to the 'previous' window within the irssi interface<br />
<br />
You can directly jump to a window (numbered in irssi) by hitting Orange Key+Space+Number.<br />
<br />
===GNU Screen History & Basics===<br />
<br />
If you're like me and you want to always keep your irssi session active as well as have the colors available to you a good solution is to use GNU Screen.<br />
<br />
For those that don't know, screen acts as a window manager for terminal applications. Screen allows you to run multiple applications in a single terminal session, switch between the applications freely as well as being able to detach from it entirely, and reattach to it later while having those applications run in the background. Many consider screen to be one of the most important tools available for any type of command line work or administration - is is very powerful and very flexible, feel free to read up on it's customization and abilities to further enhance your experience with it.<br />
<br />
====Screen Usage====<br />
<br />
To start using screen it is very simple, follow the instructions above but before switching to your local user to run irssi, first type screen and hit enter<br />
<br />
You will be greeted with screen's opening text, letting you know that it is running, and the GPL license, simply press the space bar here and you will be taken back into the prompt and it will appear as if you're back to where you started.<br />
<br />
From this point on, follow the instructions above to change into your user that is not root, and open irssi like normal.<br />
<br />
You will see commands listed as such: Sym-A C <br />
<br />
This key combination is important because it means 'Press and hold Sym, then hit A, release both and hit C'<br />
<br />
This is how GNU Screen functions and is vital to it's usage, the example above creates a new window with a fresh terminal session.<br />
<br />
==== Attach / Detach ====<br />
<br />
In order to detach from your screen session use the command Sym-A D<br />
<br />
Once a session is detached you may close out of the terminal app and any applications running within your screen session will continue to run.<br />
<br />
In order to reattach to a session you left running, load the Terminal Application again and type the following at the command prompt and hit enter: screen -r<br />
<br />
<br />
==== Screen Commands To Know ====<br />
Sym-A C - Create a new window/terminal session<br />
<br />
Sym-A N - Change to next window/terminal session within the current screen session<br />
<br />
Sym-A P - Change to previous window/terminal session with the current screen session<br />
<br />
Sym-A D - Detach from current screen session<br />
<br />
== Bitlbee for Multi-IM ==<br />
<br />
[http://www.bitlbee.org/main.php/news.r.html BitlBee] is an IRC daemon that you can run to connect to basically all of the most popular IM protocols: XMPP/Jabber (including Google Talk), MSN Messenger, Yahoo! Messenger, AIM and ICQ.<br />
<br />
As of now we are able to install bitlbee on the linux subsystem, run it in daemon mode (I wasn't able to get it started with xinetd - will be investiating this further), launch it from a script when we wish to connect and set irssi to automatically connect, identify and load all of your IM accounts at once. <br />
<br />
'''The following procedure is how I have set mine up and there may be a sleeker/easier solution down the line. Try to think of this procedure as more "proof of concept" then "ready for the general public" '''<br />
<br />
<br />
<br />
first to install the necessary files (must be performed as root or privledged user with sudo from within the terminal application):<br />
<br />
<pre><nowiki><br />
ipkg-opt install -o screen irssi bitlbee perl<br />
</nowiki></pre><br />
<br />
=== Configure Bitlbee ===<br />
<br />
The only file that absolutely needs to be tweaked is located at /var/opt/etc/bitlbee/bitlbee.conf<br />
<br />
<pre><nowiki><br />
RunMode = Daemon<br />
<br />
User = myuser<br />
<br />
ConfigDir = /home/myuser/<br />
</nowiki></pre><br />
(note - replace myuser above with the user name set up when installing optware as shown above)<br />
edit the configuration file mentioned with your editor of choice as root (vi, nano, or copy it over and copy back with winscp - whatever works for you)<br />
make sure any of those values that are leading with a # have it removed otherwise the value will not be set and it will be seen as a comment.<br />
<br />
=== Startup Script ===<br />
<br />
This script will load the daemon on-demand (may even be better this way as using less resources when you don't want to IM) and will automatically put the shell to your username instead of root (so you can use irssi more securely off the bat)<br />
<br />
Create a file called "im" (without quotes) in your /var/home/root directory with the following:<br />
<br />
<pre><nowiki><br />
#!/bin/sh<br />
#load bitlbee daemon and automatically load screen with a regular user session<br />
/opt/sbin/bitlbee<br />
screen su myuser<br />
<br />
</nowiki></pre><br />
<br />
You may now run this script at any time by opening up the terminal app and typing ./im<br />
<br />
=== Configure Bitlbee for your IM clients ===<br />
<br />
Running the 'im' script that you have now made will bring you to a prompt featuring your username such as <br />
<pre><nowiki><br />
myuser@castle:/var/home/root$<br />
</nowiki></pre><br />
<br />
'''Important Note''' In order for these changes to take effect the filesystem must be mounted as writeable, to do that as root user (or through sudo) please use the following command<br />
<br />
<pre><nowiki><br />
mount -o remount,rw /<br />
</nowiki></pre><br />
<br />
and please remember to change it back to read-only when you're finished by doing<br />
<br />
<pre><nowiki><br />
mount -o remount,ro /<br />
</nowiki></pre> <br />
<br />
From your user shell, load up irssi.<br />
<br />
Once loaded you can connect to the bitlbee daemon by doing /connect localhost<br />
<br />
Move to the second window (sym+n or orange key+space+2) and you will be at the bitlbee control channel &bitlbee<br />
<br />
You can have a flushed out description (and possibly understanding) of the following procedure [http://princessleia.com/bitlbee.php Here] - I am simply going to sum up the commands quickly. Note ignore all < > 's within the commands fill this with the respective needed values.<br />
<br />
While on the bitlbee control channel:<br />
<br />
Global Registration Password (you will input this single password and bitlbee will automatically log in to any IM accounts you set up)<br />
<br />
<pre><nowiki><br />
register <password><br />
</nowiki></pre> <br />
<br />
Add an IM account to the service:<br />
<br />
<pre><nowiki><br />
account add <protocol> <username> <password> [<server>].<br />
</nowiki></pre> <br />
oscar is the protocol used by ICQ and AOL. For MSN use msn, for Yahoo use yahoo and for Jabber use jabber)<br />
<br />
For oscar, you need to specify the IM-server as a fourth argument (for msn and yahoo there is no fourth argument). <br />
<br />
For AOL Instant Messenger, the server name is login.oscar.aol.com. For ICQ, the server name is login.icq.com.<br />
<br />
Repeat this as many times as needed for any IM accounts.<br />
<br />
<br />
=== Configure irssi to automatically connect to Bitlbee ===<br />
<br />
'''Important Note''' Please make sure the above procedure to make the filesystem writable was done or these changes WILL NOT BE SAVED.<br />
<br />
Now that we have set up the start up script, configured bitlbee with our IM services of choice, now we will make it so that when irssi loads it will automatically connect to the bitlbee daemon and identify with it so you can immediately begin IM'ing.<br />
<br />
Perform the following commands while in irssi<br />
<br />
<pre><nowiki><br />
/NETWORK ADD -autosendcmd "/^msg &bitlbee identify password" Bitlbee<br />
</nowiki></pre><br />
(please replace password in the command above with the one you set for your global Bitlbee password)<br />
<br />
<pre><nowiki><br />
/SERVER ADD -auto -network Bitlbee localhost 6667<br />
</nowiki></pre><br />
<br />
=== Final Setup & Thoughts / Running ===<br />
<br />
At this point you should be entirely set up with bitlbee and irssi. Make sure you set your filesystem back to read-only (see above). A good test would be to restart your pre entirely after setup and perform the following procedure. <br />
<br />
To get to a fully functional irssi w/IM protocols through bitlbee is only a three step process:<br />
<br />
1. Load up terminal application<br />
<br />
2. at the prompt type<br />
<pre><nowiki><br />
./im<br />
</nowiki></pre><br />
<br />
3. at the user prompt that loads, type<br />
<pre><nowiki><br />
irssi<br />
</nowiki></pre><br />
<br />
and there you are, enjoy multiple IM protocol chats natively on your webos device.<br />
<br />
If you are a new user to screen it's easy to get lost in multiple embedded screen sessions and such, if you find yourself loading multiple copies of the bitlbee daemon and need them closed (or you're done with your IM sessions and want to conserve as much battery as possible) simply run the following command and it will kill the service:<br />
<br />
<pre><nowiki><br />
pkill bitlbee <br />
</nowiki></pre><br />
<br />
== Configuration/Tweaks ==<br />
<br />
Both irssi and GNU Screen are very rich applications with a plethora of scripts, customization and usage options that only a very small percentage of are covered in this document. If interested please search and find how you may be able to adjust them to fit your specific needs (and if you find anything worthwhile feel free to add it to this wiki!)<br />
<br />
For information on irssi please visit their startup documentation http://irssi.org/documentation/startup <br />
<br />
This site provides information that will help you in automating irssi to do tasks like autojoin set servers and channels and automatically identify your nickname with services. <br />
<br />
== Known Issues ==<br />
<br />
When first loaded irssi tends to not properly format to the whole screen and a simple rotation to let the terminal rotate to the side and back to standard typing position will fix it (you will see the characters slowly refresh during this process)<br />
<br />
Even with Screen running you can lose connection if the wifi radio turns off when the screen does, see http://www.webos-internals.org/wiki/Patch_webOS_Keep_Phone_Awake_While_in_Remote_Session<br />
<br />
[[Image:Terminal-irssi.jpg]]</div>Punzadahttp://wiki.webos-internals.org/index.php?title=Linux_Tutorial_Irssi&diff=5872Linux Tutorial Irssi2009-09-23T01:22:53Z<p>Punzada: </p>
<hr />
<div>= Linux Tutorial - Irssi =<br />
<br />
=== Update 09/17/2009 === <br />
<br />
I have managed to get the [http://www.bitlbee.org/main.php/news.r.html BitlBee] service working with irssi for full AIM, MSN, Yahoo and Jabber support. I shall be doing my best to update this wiki with the best methods to get this working and configured easily and securely as soon as possible.<br />
<br />
=== This Document Assumes the following ===<br />
<br />
You have followed the procedure to Access Linux on the device and have enabled the Optware repositories and software [[Portal:Accessing_Linux]]<br />
<br />
You have installed the Terminal application [[Application:Terminal]]<br />
<br />
<br />
Once these procedures are done you should have access to:<br />
<br />
The Optware software repositories through ipkg-opt <br />
<br />
The Terminal Application through the WebOS (should load, be the root user, and function)<br />
<br />
<br />
<br />
== Installation ==<br />
<br />
Within the Terminal application use the following command:<br />
<br />
<pre><nowiki><br />
ipkg-opt install -o /var screen irssi perl<br />
</nowiki></pre><br />
<br />
This command will automatically download [http://www.gnu.org/software/screen/ GNU Screen] and [http://irssi.org/ irssi] as well as any necessary dependencies.<br />
<br />
Note: GNU Screen is *not* necessary for irssi to function, it only provides further functionality to be able to close the Terminal application if desired, keep irssi running in the background and reattach to it. Also, I have found that running irssi within a screen session gives irssi all its various colors while running natively within the terminal app leaves it mono-colored. <br />
<br />
<br />
== Usage ==<br />
<br />
In order to run irssi you simply need to type irssi into the Terminal application at the shell prompt and once hitting enter(return) it will load. <br />
<br />
However this is '''NOT RECOMMENDED''' as by default the Terminal Application is loaded as the root user and you should avoid using internet facing applications as the root user if it is not necessary (some IRC networks such as EFnet will go as far as to instantly disconnect you if it detects you are connecting to their servers as root). <br />
<br />
Once the Terminal Application is opened you may change to the user you set up when completing the steps to Access Linux via the su command<br />
<br />
example:<br />
<br />
<pre><nowiki><br />
root@castle:/var/home/root# su myuser<br />
myuser@castle:/var/home/root$<br />
</nowiki></pre><br />
<br />
from here you can simply enter irssi and hit return and it shall load.<br />
<br />
===Basic Commands===<br />
<br />
/connect ircserver<br />
<br />
This will connect you to an irc network ex: /connect irc.freenode.net will connect you to the freenode network.<br />
<br />
/join #channel<br />
<br />
This will join the requested channel, ex: /join #webos-internals<br />
<br />
Sym+n Will move to the 'next' window within the irssi interface<br />
Sym+p Will move you to the 'previous' window within the irssi interface<br />
<br />
You can directly jump to a window (numbered in irssi) by hitting Orange Key+Space+Number.<br />
<br />
===GNU Screen History & Basics===<br />
<br />
If you're like me and you want to always keep your irssi session active as well as have the colors available to you a good solution is to use GNU Screen.<br />
<br />
For those that don't know, screen acts as a window manager for terminal applications. Screen allows you to run multiple applications in a single terminal session, switch between the applications freely as well as being able to detach from it entirely, and reattach to it later while having those applications run in the background. Many consider screen to be one of the most important tools available for any type of command line work or administration - is is very powerful and very flexible, feel free to read up on it's customization and abilities to further enhance your experience with it.<br />
<br />
====Screen Usage====<br />
<br />
To start using screen it is very simple, follow the instructions above but before switching to your local user to run irssi, first type screen and hit enter<br />
<br />
You will be greeted with screen's opening text, letting you know that it is running, and the GPL license, simply press the space bar here and you will be taken back into the prompt and it will appear as if you're back to where you started.<br />
<br />
From this point on, follow the instructions above to change into your user that is not root, and open irssi like normal.<br />
<br />
You will see commands listed as such: Sym-A C <br />
<br />
This key combination is important because it means 'Press and hold Sym, then hit A, release both and hit C'<br />
<br />
This is how GNU Screen functions and is vital to it's usage, the example above creates a new window with a fresh terminal session.<br />
<br />
==== Attach / Detach ====<br />
<br />
In order to detach from your screen session use the command Sym-A D<br />
<br />
Once a session is detached you may close out of the terminal app and any applications running within your screen session will continue to run.<br />
<br />
In order to reattach to a session you left running, load the Terminal Application again and type the following at the command prompt and hit enter: screen -r<br />
<br />
<br />
==== Screen Commands To Know ====<br />
Sym-A C - Create a new window/terminal session<br />
<br />
Sym-A N - Change to next window/terminal session within the current screen session<br />
<br />
Sym-A P - Change to previous window/terminal session with the current screen session<br />
<br />
Sym-A D - Detach from current screen session<br />
<br />
== Bitlbee for Multi-IM ==<br />
<br />
[http://www.bitlbee.org/main.php/news.r.html BitlBee] is an IRC daemon that you can run to connect to basically all of the most popular IM protocols: XMPP/Jabber (including Google Talk), MSN Messenger, Yahoo! Messenger, AIM and ICQ.<br />
<br />
As of now we are able to install bitlbee on the linux subsystem, run it in daemon mode (I wasn't able to get it started with xinetd - will be investiating this further), launch it from a script when we wish to connect and set irssi to automatically connect, identify and load all of your IM accounts at once. <br />
<br />
'''The following procedure is how I have set mine up and there may be a sleeker/easier solution down the line. Try to think of this procedure as more "proof of concept" then "ready for the general public" '''<br />
<br />
<br />
<br />
first to install the necessary files (must be performed as root or privledged user with sudo from within the terminal application):<br />
<br />
<pre><nowiki><br />
ipkg-opt install -o screen irssi bitlbee perl<br />
</nowiki></pre><br />
<br />
=== Configure Bitlbee ===<br />
<br />
The only file that absolutely needs to be tweaked is located at /opt/etc/bitlbee/bitlbee.conf<br />
<br />
<pre><nowiki><br />
RunMode = Daemon<br />
<br />
User = myuser<br />
<br />
ConfigDir = /home/myuser/<br />
</nowiki></pre><br />
(note - replace myuser above with the user name set up when installing optware as shown above)<br />
edit the configuration file mentioned with your editor of choice as root (vi, nano, or copy it over and copy back with winscp - whatever works for you)<br />
make sure any of those values that are leading with a # have it removed otherwise the value will not be set and it will be seen as a comment.<br />
<br />
=== Startup Script ===<br />
<br />
This script will load the daemon on-demand (may even be better this way as using less resources when you don't want to IM) and will automatically put the shell to your username instead of root (so you can use irssi more securely off the bat)<br />
<br />
Create a file called "im" (without quotes) in your /var/home/root directory with the following:<br />
<br />
<pre><nowiki><br />
#!/bin/sh<br />
#load bitlbee daemon and automatically load screen with a regular user session<br />
/opt/sbin/bitlbee<br />
screen su myuser<br />
<br />
</nowiki></pre><br />
<br />
You may now run this script at any time by opening up the terminal app and typing ./im<br />
<br />
=== Configure Bitlbee for your IM clients ===<br />
<br />
Running the 'im' script that you have now made will bring you to a prompt featuring your username such as <br />
<pre><nowiki><br />
myuser@castle:/var/home/root$<br />
</nowiki></pre><br />
<br />
'''Important Note''' In order for these changes to take effect the filesystem must be mounted as writeable, to do that as root user (or through sudo) please use the following command<br />
<br />
<pre><nowiki><br />
mount -o remount,rw /<br />
</nowiki></pre><br />
<br />
and please remember to change it back to read-only when you're finished by doing<br />
<br />
<pre><nowiki><br />
mount -o remount,ro /<br />
</nowiki></pre> <br />
<br />
From your user shell, load up irssi.<br />
<br />
Once loaded you can connect to the bitlbee daemon by doing /connect localhost<br />
<br />
Move to the second window (sym+n or orange key+space+2) and you will be at the bitlbee control channel &bitlbee<br />
<br />
You can have a flushed out description (and possibly understanding) of the following procedure [http://princessleia.com/bitlbee.php Here] - I am simply going to sum up the commands quickly. Note ignore all < > 's within the commands fill this with the respective needed values.<br />
<br />
While on the bitlbee control channel:<br />
<br />
Global Registration Password (you will input this single password and bitlbee will automatically log in to any IM accounts you set up)<br />
<br />
<pre><nowiki><br />
register <password><br />
</nowiki></pre> <br />
<br />
Add an IM account to the service:<br />
<br />
<pre><nowiki><br />
account add <protocol> <username> <password> [<server>].<br />
</nowiki></pre> <br />
oscar is the protocol used by ICQ and AOL. For MSN use msn, for Yahoo use yahoo and for Jabber use jabber)<br />
<br />
For oscar, you need to specify the IM-server as a fourth argument (for msn and yahoo there is no fourth argument). <br />
<br />
For AOL Instant Messenger, the server name is login.oscar.aol.com. For ICQ, the server name is login.icq.com.<br />
<br />
Repeat this as many times as needed for any IM accounts.<br />
<br />
<br />
=== Configure irssi to automatically connect to Bitlbee ===<br />
<br />
'''Important Note''' Please make sure the above procedure to make the filesystem writable was done or these changes WILL NOT BE SAVED.<br />
<br />
Now that we have set up the start up script, configured bitlbee with our IM services of choice, now we will make it so that when irssi loads it will automatically connect to the bitlbee daemon and identify with it so you can immediately begin IM'ing.<br />
<br />
Perform the following commands while in irssi<br />
<br />
<pre><nowiki><br />
/NETWORK ADD -autosendcmd "/^msg &bitlbee identify password" Bitlbee<br />
</nowiki></pre><br />
(please replace password in the command above with the one you set for your global Bitlbee password)<br />
<br />
<pre><nowiki><br />
/SERVER ADD -auto -network Bitlbee localhost 6667<br />
</nowiki></pre><br />
<br />
=== Final Setup & Thoughts / Running ===<br />
<br />
At this point you should be entirely set up with bitlbee and irssi. Make sure you set your filesystem back to read-only (see above). A good test would be to restart your pre entirely after setup and perform the following procedure. <br />
<br />
To get to a fully functional irssi w/IM protocols through bitlbee is only a three step process:<br />
<br />
1. Load up terminal application<br />
<br />
2. at the prompt type<br />
<pre><nowiki><br />
./im<br />
</nowiki></pre><br />
<br />
3. at the user prompt that loads, type<br />
<pre><nowiki><br />
irssi<br />
</nowiki></pre><br />
<br />
and there you are, enjoy multiple IM protocol chats natively on your webos device.<br />
<br />
If you are a new user to screen it's easy to get lost in multiple embedded screen sessions and such, if you find yourself loading multiple copies of the bitlbee daemon and need them closed (or you're done with your IM sessions and want to conserve as much battery as possible) simply run the following command and it will kill the service:<br />
<br />
<pre><nowiki><br />
pkill bitlbee <br />
</nowiki></pre><br />
<br />
== Configuration/Tweaks ==<br />
<br />
Both irssi and GNU Screen are very rich applications with a plethora of scripts, customization and usage options that only a very small percentage of are covered in this document. If interested please search and find how you may be able to adjust them to fit your specific needs (and if you find anything worthwhile feel free to add it to this wiki!)<br />
<br />
For information on irssi please visit their startup documentation http://irssi.org/documentation/startup <br />
<br />
This site provides information that will help you in automating irssi to do tasks like autojoin set servers and channels and automatically identify your nickname with services. <br />
<br />
== Known Issues ==<br />
<br />
When first loaded irssi tends to not properly format to the whole screen and a simple rotation to let the terminal rotate to the side and back to standard typing position will fix it (you will see the characters slowly refresh during this process)<br />
<br />
Even with Screen running you can lose connection if the wifi radio turns off when the screen does, see http://www.webos-internals.org/wiki/Patch_webOS_Keep_Phone_Awake_While_in_Remote_Session<br />
<br />
[[Image:Terminal-irssi.jpg]]</div>Punzadahttp://wiki.webos-internals.org/index.php?title=Linux_Tutorial_Irssi&diff=5839Linux Tutorial Irssi2009-09-18T00:01:52Z<p>Punzada: </p>
<hr />
<div>= Linux Tutorial - Irssi =<br />
<br />
=== Update 09/17/2009 === <br />
<br />
I have managed to get the [http://www.bitlbee.org/main.php/news.r.html BitlBee] service working with irssi for full AIM, MSN, Yahoo and Jabber support. I shall be doing my best to update this wiki with the best methods to get this working and configured easily and securely as soon as possible.<br />
<br />
=== This Document Assumes the following ===<br />
<br />
You have followed the procedure to Access Linux on the device and have enabled the Optware repositories and software [[Portal:Accessing_Linux]]<br />
<br />
You have installed the Terminal application [[Application:Terminal]]<br />
<br />
<br />
Once these procedures are done you should have access to:<br />
<br />
The Optware software repositories through ipkg-opt <br />
<br />
The Terminal Application through the WebOS (should load, be the root user, and function)<br />
<br />
<br />
<br />
== Installation ==<br />
<br />
Within the Terminal application use the following command:<br />
<br />
<pre><nowiki><br />
ipkg-opt install -o /var screen irssi<br />
</nowiki></pre><br />
<br />
This command will automatically download [http://www.gnu.org/software/screen/ GNU Screen] and [http://irssi.org/ irssi] as well as any necessary dependencies.<br />
<br />
Note: GNU Screen is *not* necessary for irssi to function, it only provides further functionality to be able to close the Terminal application if desired, keep irssi running in the background and reattach to it. Also, I have found that running irssi within a screen session gives irssi all its various colors while running natively within the terminal app leaves it mono-colored. <br />
<br />
<br />
== Usage ==<br />
<br />
In order to run irssi you simply need to type irssi into the Terminal application at the shell prompt and once hitting enter(return) it will load. <br />
<br />
However this is '''NOT RECOMMENDED''' as by default the Terminal Application is loaded as the root user and you should avoid using internet facing applications as the root user if it is not necessary (some IRC networks such as EFnet will go as far as to instantly disconnect you if it detects you are connecting to their servers as root). <br />
<br />
Once the Terminal Application is opened you may change to the user you set up when completing the steps to Access Linux via the su command<br />
<br />
example:<br />
<br />
<pre><nowiki><br />
root@castle:/var/home/root# su myuser<br />
myuser@castle:/var/home/root$<br />
</nowiki></pre><br />
<br />
from here you can simply enter irssi and hit return and it shall load.<br />
<br />
===Basic Commands===<br />
<br />
/connect ircserver<br />
<br />
This will connect you to an irc network ex: /connect irc.freenode.net will connect you to the freenode network.<br />
<br />
/join #channel<br />
<br />
This will join the requested channel, ex: /join #webos-internals<br />
<br />
Sym+n Will move to the 'next' window within the irssi interface<br />
Sym+p Will move you to the 'previous' window within the irssi interface<br />
<br />
You can directly jump to a window (numbered in irssi) by hitting Orange Key+Space+Number.<br />
<br />
===GNU Screen History & Basics===<br />
<br />
If you're like me and you want to always keep your irssi session active as well as have the colors available to you a good solution is to use GNU Screen.<br />
<br />
For those that don't know, screen acts as a window manager for terminal applications. Screen allows you to run multiple applications in a single terminal session, switch between the applications freely as well as being able to detach from it entirely, and reattach to it later while having those applications run in the background. Many consider screen to be one of the most important tools available for any type of command line work or administration - is is very powerful and very flexible, feel free to read up on it's customization and abilities to further enhance your experience with it.<br />
<br />
====Screen Usage====<br />
<br />
To start using screen it is very simple, follow the instructions above but before switching to your local user to run irssi, first type screen and hit enter<br />
<br />
You will be greeted with screen's opening text, letting you know that it is running, and the GPL license, simply press the space bar here and you will be taken back into the prompt and it will appear as if you're back to where you started.<br />
<br />
From this point on, follow the instructions above to change into your user that is not root, and open irssi like normal.<br />
<br />
You will see commands listed as such: Sym-A C <br />
<br />
This key combination is important because it means 'Press and hold Sym, then hit A, release both and hit C'<br />
<br />
This is how GNU Screen functions and is vital to it's usage, the example above creates a new window with a fresh terminal session.<br />
<br />
==== Attach / Detach ====<br />
<br />
In order to detach from your screen session use the command Sym-A D<br />
<br />
Once a session is detached you may close out of the terminal app and any applications running within your screen session will continue to run.<br />
<br />
In order to reattach to a session you left running, load the Terminal Application again and type the following at the command prompt and hit enter: screen -r<br />
<br />
<br />
==== Screen Commands To Know ====<br />
Sym-A C - Create a new window/terminal session<br />
<br />
Sym-A N - Change to next window/terminal session within the current screen session<br />
<br />
Sym-A P - Change to previous window/terminal session with the current screen session<br />
<br />
Sym-A D - Detach from current screen session<br />
<br />
== Bitlbee for Multi-IM ==<br />
<br />
[http://www.bitlbee.org/main.php/news.r.html BitlBee] is an IRC daemon that you can run to connect to basically all of the most popular IM protocols: XMPP/Jabber (including Google Talk), MSN Messenger, Yahoo! Messenger, AIM and ICQ.<br />
<br />
As of now we are able to install bitlbee on the linux subsystem, run it in daemon mode (I wasn't able to get it started with xinetd - will be investiating this further), launch it from a script when we wish to connect and set irssi to automatically connect, identify and load all of your IM accounts at once. <br />
<br />
'''The following procedure is how I have set mine up and there may be a sleeker/easier solution down the line. Try to think of this procedure as more "proof of concept" then "ready for the general public" '''<br />
<br />
<br />
<br />
first to install the necessary files (must be performed as root or privledged user with sudo from within the terminal application):<br />
<br />
<pre><nowiki><br />
ipkg-opt install -o screen irssi bitlbee<br />
</nowiki></pre><br />
<br />
=== Configure Bitlbee ===<br />
<br />
The only file that absolutely needs to be tweaked is located at /opt/etc/bitlbee/bitlbee.conf<br />
<br />
<pre><nowiki><br />
RunMode = Daemon<br />
<br />
User = myuser<br />
<br />
ConfigDir = /home/myuser/<br />
</nowiki></pre><br />
(note - replace myuser above with the user name set up when installing optware as shown above)<br />
edit the configuration file mentioned with your editor of choice as root (vi, nano, or copy it over and copy back with winscp - whatever works for you)<br />
make sure any of those values that are leading with a # have it removed otherwise the value will not be set and it will be seen as a comment.<br />
<br />
=== Startup Script ===<br />
<br />
This script will load the daemon on-demand (may even be better this way as using less resources when you don't want to IM) and will automatically put the shell to your username instead of root (so you can use irssi more securely off the bat)<br />
<br />
Create a file called "im" (without quotes) in your /var/home/root directory with the following:<br />
<br />
<pre><nowiki><br />
#!/bin/sh<br />
#load bitlbee daemon and automatically load screen with a regular user session<br />
/opt/sbin/bitlbee<br />
screen su myuser<br />
<br />
</nowiki></pre><br />
<br />
You may now run this script at any time by opening up the terminal app and typing ./im<br />
<br />
=== Configure Bitlbee for your IM clients ===<br />
<br />
Running the 'im' script that you have now made will bring you to a prompt featuring your username such as <br />
<pre><nowiki><br />
myuser@castle:/var/home/root$<br />
</nowiki></pre><br />
<br />
'''Important Note''' In order for these changes to take effect the filesystem must be mounted as writeable, to do that as root user (or through sudo) please use the following command<br />
<br />
<pre><nowiki><br />
mount -o remount,rw /<br />
</nowiki></pre><br />
<br />
and please remember to change it back to read-only when you're finished by doing<br />
<br />
<pre><nowiki><br />
mount -o remount,ro /<br />
</nowiki></pre> <br />
<br />
From your user shell, load up irssi.<br />
<br />
Once loaded you can connect to the bitlbee daemon by doing /connect localhost<br />
<br />
Move to the second window (sym+n or orange key+space+2) and you will be at the bitlbee control channel &bitlbee<br />
<br />
You can have a flushed out description (and possibly understanding) of the following procedure [http://princessleia.com/bitlbee.php Here] - I am simply going to sum up the commands quickly. Note ignore all < > 's within the commands fill this with the respective needed values.<br />
<br />
While on the bitlbee control channel:<br />
<br />
Global Registration Password (you will input this single password and bitlbee will automatically log in to any IM accounts you set up)<br />
<br />
<pre><nowiki><br />
register <password><br />
</nowiki></pre> <br />
<br />
Add an IM account to the service:<br />
<br />
<pre><nowiki><br />
account add <protocol> <username> <password> [<server>].<br />
</nowiki></pre> <br />
oscar is the protocol used by ICQ and AOL. For MSN use msn, for Yahoo use yahoo and for Jabber use jabber)<br />
<br />
For oscar, you need to specify the IM-server as a fourth argument (for msn and yahoo there is no fourth argument). <br />
<br />
For AOL Instant Messenger, the server name is login.oscar.aol.com. For ICQ, the server name is login.icq.com.<br />
<br />
Repeat this as many times as needed for any IM accounts.<br />
<br />
<br />
=== Configure irssi to automatically connect to Bitlbee ===<br />
<br />
'''Important Note''' Please make sure the above procedure to make the filesystem writable was done or these changes WILL NOT BE SAVED.<br />
<br />
Now that we have set up the start up script, configured bitlbee with our IM services of choice, now we will make it so that when irssi loads it will automatically connect to the bitlbee daemon and identify with it so you can immediately begin IM'ing.<br />
<br />
Perform the following commands while in irssi<br />
<br />
<pre><nowiki><br />
/NETWORK ADD -autosendcmd "/^msg &bitlbee identify password" Bitlbee<br />
</nowiki></pre><br />
(please replace password in the command above with the one you set for your global Bitlbee password)<br />
<br />
<pre><nowiki><br />
/SERVER ADD -auto -network Bitlbee localhost 6667<br />
</nowiki></pre><br />
<br />
=== Final Setup & Thoughts / Running ===<br />
<br />
At this point you should be entirely set up with bitlbee and irssi. Make sure you set your filesystem back to read-only (see above). A good test would be to restart your pre entirely after setup and perform the following procedure. <br />
<br />
To get to a fully functional irssi w/IM protocols through bitlbee is only a three step process:<br />
<br />
1. Load up terminal application<br />
<br />
2. at the prompt type<br />
<pre><nowiki><br />
./im<br />
</nowiki></pre><br />
<br />
3. at the user prompt that loads, type<br />
<pre><nowiki><br />
irssi<br />
</nowiki></pre><br />
<br />
and there you are, enjoy multiple IM protocol chats natively on your webos device.<br />
<br />
If you are a new user to screen it's easy to get lost in multiple embedded screen sessions and such, if you find yourself loading multiple copies of the bitlbee daemon and need them closed (or you're done with your IM sessions and want to conserve as much battery as possible) simply run the following command and it will kill the service:<br />
<br />
<pre><nowiki><br />
pkill bitlbee <br />
</nowiki></pre><br />
<br />
== Configuration/Tweaks ==<br />
<br />
Both irssi and GNU Screen are very rich applications with a plethora of scripts, customization and usage options that only a very small percentage of are covered in this document. If interested please search and find how you may be able to adjust them to fit your specific needs (and if you find anything worthwhile feel free to add it to this wiki!)<br />
<br />
For information on irssi please visit their startup documentation http://irssi.org/documentation/startup <br />
<br />
This site provides information that will help you in automating irssi to do tasks like autojoin set servers and channels and automatically identify your nickname with services. <br />
<br />
== Known Issues ==<br />
<br />
When first loaded irssi tends to not properly format to the whole screen and a simple rotation to let the terminal rotate to the side and back to standard typing position will fix it (you will see the characters slowly refresh during this process)<br />
<br />
Even with Screen running you can lose connection if the wifi radio turns off when the screen does, see http://www.webos-internals.org/wiki/Patch_webOS_Keep_Phone_Awake_While_in_Remote_Session<br />
<br />
[[Image:Terminal-irssi.jpg]]</div>Punzadahttp://wiki.webos-internals.org/index.php?title=Linux_Tutorial_Irssi&diff=5838Linux Tutorial Irssi2009-09-17T23:38:20Z<p>Punzada: </p>
<hr />
<div>= Linux Tutorial - Irssi =<br />
<br />
=== Update 09/17/2009 === <br />
<br />
I have managed to get the [http://www.bitlbee.org/main.php/news.r.html BitlBee] service working with irssi for full AIM, MSN, Yahoo and Jabber support. I shall be doing my best to update this wiki with the best methods to get this working and configured easily and securely as soon as possible.<br />
<br />
=== This Document Assumes the following ===<br />
<br />
You have followed the procedure to Access Linux on the device and have enabled the Optware repositories and software [[Portal:Accessing_Linux]]<br />
<br />
You have installed the Terminal application [[Application:Terminal]]<br />
<br />
<br />
Once these procedures are done you should have access to:<br />
<br />
The Optware software repositories through ipkg-opt <br />
<br />
The Terminal Application through the WebOS (should load, be the root user, and function)<br />
<br />
<br />
<br />
== Installation ==<br />
<br />
Within the Terminal application use the following command:<br />
<br />
<pre><nowiki><br />
ipkg-opt install screen irssi<br />
</nowiki></pre><br />
<br />
This command will automatically download [http://www.gnu.org/software/screen/ GNU Screen] and [http://irssi.org/ irssi] as well as any necessary dependencies.<br />
<br />
Note: GNU Screen is *not* necessary for irssi to function, it only provides further functionality to be able to close the Terminal application if desired, keep irssi running in the background and reattach to it. Also, I have found that running irssi within a screen session gives irssi all its various colors while running natively within the terminal app leaves it mono-colored. <br />
<br />
<br />
== Usage ==<br />
<br />
In order to run irssi you simply need to type irssi into the Terminal application at the shell prompt and once hitting enter(return) it will load. <br />
<br />
However this is '''NOT RECOMMENDED''' as by default the Terminal Application is loaded as the root user and you should avoid using internet facing applications as the root user if it is not necessary (some IRC networks such as EFnet will go as far as to instantly disconnect you if it detects you are connecting to their servers as root). <br />
<br />
Once the Terminal Application is opened you may change to the user you set up when completing the steps to Access Linux via the su command<br />
<br />
example:<br />
<br />
<pre><nowiki><br />
root@castle:/var/home/root# su myuser<br />
myuser@castle:/var/home/root$<br />
</nowiki></pre><br />
<br />
from here you can simply enter irssi and hit return and it shall load.<br />
<br />
===Basic Commands===<br />
<br />
/connect ircserver<br />
<br />
This will connect you to an irc network ex: /connect irc.freenode.net will connect you to the freenode network.<br />
<br />
/join #channel<br />
<br />
This will join the requested channel, ex: /join #webos-internals<br />
<br />
Sym+n Will move to the 'next' window within the irssi interface<br />
Sym+p Will move you to the 'previous' window within the irssi interface<br />
<br />
You can directly jump to a window (numbered in irssi) by hitting Orange Key+Space+Number.<br />
<br />
===GNU Screen History & Basics===<br />
<br />
If you're like me and you want to always keep your irssi session active as well as have the colors available to you a good solution is to use GNU Screen.<br />
<br />
For those that don't know, screen acts as a window manager for terminal applications. Screen allows you to run multiple applications in a single terminal session, switch between the applications freely as well as being able to detach from it entirely, and reattach to it later while having those applications run in the background. Many consider screen to be one of the most important tools available for any type of command line work or administration - is is very powerful and very flexible, feel free to read up on it's customization and abilities to further enhance your experience with it.<br />
<br />
====Screen Usage====<br />
<br />
To start using screen it is very simple, follow the instructions above but before switching to your local user to run irssi, first type screen and hit enter<br />
<br />
You will be greeted with screen's opening text, letting you know that it is running, and the GPL license, simply press the space bar here and you will be taken back into the prompt and it will appear as if you're back to where you started.<br />
<br />
From this point on, follow the instructions above to change into your user that is not root, and open irssi like normal.<br />
<br />
You will see commands listed as such: Sym-A C <br />
<br />
This key combination is important because it means 'Press and hold Sym, then hit A, release both and hit C'<br />
<br />
This is how GNU Screen functions and is vital to it's usage, the example above creates a new window with a fresh terminal session.<br />
<br />
==== Attach / Detach ====<br />
<br />
In order to detach from your screen session use the command Sym-A D<br />
<br />
Once a session is detached you may close out of the terminal app and any applications running within your screen session will continue to run.<br />
<br />
In order to reattach to a session you left running, load the Terminal Application again and type the following at the command prompt and hit enter: screen -r<br />
<br />
<br />
==== Screen Commands To Know ====<br />
Sym-A C - Create a new window/terminal session<br />
<br />
Sym-A N - Change to next window/terminal session within the current screen session<br />
<br />
Sym-A P - Change to previous window/terminal session with the current screen session<br />
<br />
Sym-A D - Detach from current screen session<br />
<br />
== Bitlbee for Multi-IM ==<br />
<br />
[http://www.bitlbee.org/main.php/news.r.html BitlBee] is an IRC daemon that you can run to connect to basically all of the most popular IM protocols: XMPP/Jabber (including Google Talk), MSN Messenger, Yahoo! Messenger, AIM and ICQ.<br />
<br />
As of now we are able to install bitlbee on the linux subsystem, run it in daemon mode (I wasn't able to get it started with xinetd - will be investiating this further), launch it from a script when we wish to connect and set irssi to automatically connect, identify and load all of your IM accounts at once. <br />
<br />
'''The following procedure is how I have set mine up and there may be a sleeker/easier solution down the line. Try to think of this procedure as more "proof of concept" then "ready for the general public" '''<br />
<br />
<br />
<br />
first to install the necessary files (must be performed as root or privledged user with sudo from within the terminal application):<br />
<br />
<pre><nowiki><br />
ipkg-opt install screen irssi bitlbee<br />
</nowiki></pre><br />
<br />
=== Configure Bitlbee ===<br />
<br />
The only file that absolutely needs to be tweaked is located at /opt/etc/bitlbee/bitlbee.conf<br />
<br />
<pre><nowiki><br />
RunMode = Daemon<br />
<br />
User = myuser<br />
<br />
ConfigDir = /home/myuser/<br />
</nowiki></pre><br />
(note - replace myuser above with the user name set up when installing optware as shown above)<br />
edit the configuration file mentioned with your editor of choice as root (vi, nano, or copy it over and copy back with winscp - whatever works for you)<br />
make sure any of those values that are leading with a # have it removed otherwise the value will not be set and it will be seen as a comment.<br />
<br />
=== Startup Script ===<br />
<br />
This script will load the daemon on-demand (may even be better this way as using less resources when you don't want to IM) and will automatically put the shell to your username instead of root (so you can use irssi more securely off the bat)<br />
<br />
Create a file called "im" (without quotes) in your /var/home/root directory with the following:<br />
<br />
<pre><nowiki><br />
#!/bin/sh<br />
#load bitlbee daemon and automatically load screen with a regular user session<br />
/opt/sbin/bitlbee<br />
screen su myuser<br />
<br />
</nowiki></pre><br />
<br />
You may now run this script at any time by opening up the terminal app and typing ./im<br />
<br />
=== Configure Bitlbee for your IM clients ===<br />
<br />
Running the 'im' script that you have now made will bring you to a prompt featuring your username such as <br />
<pre><nowiki><br />
myuser@castle:/var/home/root$<br />
</nowiki></pre><br />
<br />
'''Important Note''' In order for these changes to take effect the filesystem must be mounted as writeable, to do that as root user (or through sudo) please use the following command<br />
<br />
<pre><nowiki><br />
mount -o remount,rw /<br />
</nowiki></pre><br />
<br />
and please remember to change it back to read-only when you're finished by doing<br />
<br />
<pre><nowiki><br />
mount -o remount,ro /<br />
</nowiki></pre> <br />
<br />
From your user shell, load up irssi.<br />
<br />
Once loaded you can connect to the bitlbee daemon by doing /connect localhost<br />
<br />
Move to the second window (sym+n or orange key+space+2) and you will be at the bitlbee control channel &bitlbee<br />
<br />
You can have a flushed out description (and possibly understanding) of the following procedure [http://princessleia.com/bitlbee.php Here] - I am simply going to sum up the commands quickly. Note ignore all < > 's within the commands fill this with the respective needed values.<br />
<br />
While on the bitlbee control channel:<br />
<br />
Global Registration Password (you will input this single password and bitlbee will automatically log in to any IM accounts you set up)<br />
<br />
<pre><nowiki><br />
register <password><br />
</nowiki></pre> <br />
<br />
Add an IM account to the service:<br />
<br />
<pre><nowiki><br />
account add <protocol> <username> <password> [<server>].<br />
</nowiki></pre> <br />
oscar is the protocol used by ICQ and AOL. For MSN use msn, for Yahoo use yahoo and for Jabber use jabber)<br />
<br />
For oscar, you need to specify the IM-server as a fourth argument (for msn and yahoo there is no fourth argument). <br />
<br />
For AOL Instant Messenger, the server name is login.oscar.aol.com. For ICQ, the server name is login.icq.com.<br />
<br />
Repeat this as many times as needed for any IM accounts.<br />
<br />
<br />
=== Configure irssi to automatically connect to Bitlbee ===<br />
<br />
'''Important Note''' Please make sure the above procedure to make the filesystem writable was done or these changes WILL NOT BE SAVED.<br />
<br />
Now that we have set up the start up script, configured bitlbee with our IM services of choice, now we will make it so that when irssi loads it will automatically connect to the bitlbee daemon and identify with it so you can immediately begin IM'ing.<br />
<br />
Perform the following commands while in irssi<br />
<br />
<pre><nowiki><br />
/NETWORK ADD -autosendcmd "/^msg &bitlbee identify password" Bitlbee<br />
</nowiki></pre><br />
(please replace password in the command above with the one you set for your global Bitlbee password)<br />
<br />
<pre><nowiki><br />
/SERVER ADD -auto -network Bitlbee localhost 6667<br />
</nowiki></pre><br />
<br />
=== Final Setup & Thoughts / Running ===<br />
<br />
At this point you should be entirely set up with bitlbee and irssi. Make sure you set your filesystem back to read-only (see above). A good test would be to restart your pre entirely after setup and perform the following procedure. <br />
<br />
To get to a fully functional irssi w/IM protocols through bitlbee is only a three step process:<br />
<br />
1. Load up terminal application<br />
<br />
2. at the prompt type<br />
<pre><nowiki><br />
./im<br />
</nowiki></pre><br />
<br />
3. at the user prompt that loads, type<br />
<pre><nowiki><br />
irssi<br />
</nowiki></pre><br />
<br />
and there you are, enjoy multiple IM protocol chats natively on your webos device.<br />
<br />
If you are a new user to screen it's easy to get lost in multiple embedded screen sessions and such, if you find yourself loading multiple copies of the bitlbee daemon and need them closed (or you're done with your IM sessions and want to conserve as much battery as possible) simply run the following command and it will kill the service:<br />
<br />
<pre><nowiki><br />
pkill bitlbee <br />
</nowiki></pre><br />
<br />
== Configuration/Tweaks ==<br />
<br />
Both irssi and GNU Screen are very rich applications with a plethora of scripts, customization and usage options that only a very small percentage of are covered in this document. If interested please search and find how you may be able to adjust them to fit your specific needs (and if you find anything worthwhile feel free to add it to this wiki!)<br />
<br />
For information on irssi please visit their startup documentation http://irssi.org/documentation/startup <br />
<br />
This site provides information that will help you in automating irssi to do tasks like autojoin set servers and channels and automatically identify your nickname with services. <br />
<br />
== Known Issues ==<br />
<br />
When first loaded irssi tends to not properly format to the whole screen and a simple rotation to let the terminal rotate to the side and back to standard typing position will fix it (you will see the characters slowly refresh during this process)<br />
<br />
Even with Screen running you can lose connection if the wifi radio turns off when the screen does, see http://www.webos-internals.org/wiki/Patch_webOS_Keep_Phone_Awake_While_in_Remote_Session<br />
<br />
[[Image:Terminal-irssi.jpg]]</div>Punzadahttp://wiki.webos-internals.org/index.php?title=Linux_Tutorial_Irssi&diff=5837Linux Tutorial Irssi2009-09-17T23:35:36Z<p>Punzada: </p>
<hr />
<div>= Linux Tutorial - Irssi =<br />
<br />
=== Update 09/17/2009 === <br />
<br />
I have managed to get the [http://www.bitlbee.org/main.php/news.r.html BitlBee] service working with irssi for full AIM, MSN, Yahoo and Jabber support. I shall be doing my best to update this wiki with the best methods to get this working and configured easily and securely as soon as possible.<br />
<br />
=== This Document Assumes the following ===<br />
<br />
You have followed the procedure to Access Linux on the device and have enabled the Optware repositories and software [[Portal:Accessing_Linux]]<br />
<br />
You have installed the Terminal application [[Application:Terminal]]<br />
<br />
<br />
Once these procedures are done you should have access to:<br />
<br />
The Optware software repositories through ipkg-opt <br />
<br />
The Terminal Application through the WebOS (should load, be the root user, and function)<br />
<br />
<br />
<br />
== Installation ==<br />
<br />
Within the Terminal application use the following command:<br />
<br />
<pre><nowiki><br />
ipkg-opt install screen irssi<br />
</nowiki></pre><br />
<br />
This command will automatically download [http://www.gnu.org/software/screen/ GNU Screen] and [http://irssi.org/ irssi] as well as any necessary dependencies.<br />
<br />
Note: GNU Screen is *not* necessary for irssi to function, it only provides further functionality to be able to close the Terminal application if desired, keep irssi running in the background and reattach to it. Also, I have found that running irssi within a screen session gives irssi all its various colors while running natively within the terminal app leaves it mono-colored. <br />
<br />
<br />
== Usage ==<br />
<br />
In order to run irssi you simply need to type irssi into the Terminal application at the shell prompt and once hitting enter(return) it will load. <br />
<br />
However this is '''NOT RECOMMENDED''' as by default the Terminal Application is loaded as the root user and you should avoid using internet facing applications as the root user if it is not necessary (some IRC networks such as EFnet will go as far as to instantly disconnect you if it detects you are connecting to their servers as root). <br />
<br />
Once the Terminal Application is opened you may change to the user you set up when completing the steps to Access Linux via the su command<br />
<br />
example:<br />
<br />
<pre><nowiki><br />
root@castle:/var/home/root# su myuser<br />
myuser@castle:/var/home/root$<br />
</nowiki></pre><br />
<br />
from here you can simply enter irssi and hit return and it shall load.<br />
<br />
===Basic Commands===<br />
<br />
/connect ircserver<br />
<br />
This will connect you to an irc network ex: /connect irc.freenode.net will connect you to the freenode network.<br />
<br />
/join #channel<br />
<br />
This will join the requested channel, ex: /join #webos-internals<br />
<br />
Sym+n Will move to the 'next' window within the irssi interface<br />
Sym+p Will move you to the 'previous' window within the irssi interface<br />
<br />
You can directly jump to a window (numbered in irssi) by hitting Orange Key+Space+Number.<br />
<br />
===GNU Screen History & Basics===<br />
<br />
If you're like me and you want to always keep your irssi session active as well as have the colors available to you a good solution is to use GNU Screen.<br />
<br />
For those that don't know, screen acts as a window manager for terminal applications. Screen allows you to run multiple applications in a single terminal session, switch between the applications freely as well as being able to detach from it entirely, and reattach to it later while having those applications run in the background. Many consider screen to be one of the most important tools available for any type of command line work or administration - is is very powerful and very flexible, feel free to read up on it's customization and abilities to further enhance your experience with it.<br />
<br />
====Screen Usage====<br />
<br />
To start using screen it is very simple, follow the instructions above but before switching to your local user to run irssi, first type screen and hit enter<br />
<br />
You will be greeted with screen's opening text, letting you know that it is running, and the GPL license, simply press the space bar here and you will be taken back into the prompt and it will appear as if you're back to where you started.<br />
<br />
From this point on, follow the instructions above to change into your user that is not root, and open irssi like normal.<br />
<br />
You will see commands listed as such: Sym-A C <br />
<br />
This key combination is important because it means 'Press and hold Sym, then hit A, release both and hit C'<br />
<br />
This is how GNU Screen functions and is vital to it's usage, the example above creates a new window with a fresh terminal session.<br />
<br />
==== Attach / Detach ====<br />
<br />
In order to detach from your screen session use the command Sym-A D<br />
<br />
Once a session is detached you may close out of the terminal app and any applications running within your screen session will continue to run.<br />
<br />
In order to reattach to a session you left running, load the Terminal Application again and type the following at the command prompt and hit enter: screen -r<br />
<br />
<br />
==== Screen Commands To Know ====<br />
Sym-A C - Create a new window/terminal session<br />
<br />
Sym-A N - Change to next window/terminal session within the current screen session<br />
<br />
Sym-A P - Change to previous window/terminal session with the current screen session<br />
<br />
Sym-A D - Detach from current screen session<br />
<br />
== Bitlbee for Multi-IM ==<br />
<br />
[http://www.bitlbee.org/main.php/news.r.html BitlBee] is an IRC daemon that you can run to connect to basically all of the most popular IM protocols: XMPP/Jabber (including Google Talk), MSN Messenger, Yahoo! Messenger, AIM and ICQ.<br />
<br />
As of now we are able to install bitlbee on the linux subsystem, run it in daemon mode (I wasn't able to get it started with xinetd - will be investiating this further), launch it from a script when we wish to connect and set irssi to automatically connect, identify and load all of your IM accounts at once. <br />
<br />
'''The following procedure is how I have set mine up and there may be a sleeker/easier solution down the line try to think of this procedure as more "proof of concept" then "ready for the general public" '''<br />
<br />
<br />
<br />
first to install the necessary files (must be performed as root or privledged user with sudo from within the terminal application):<br />
<br />
<pre><nowiki><br />
ipkg-opt install screen irssi bitlbee<br />
</nowiki></pre><br />
<br />
=== Configure Bitlbee ===<br />
<br />
The only file that absolutely needs to be tweaked is located at /opt/etc/bitlbee/bitlbee.conf<br />
<br />
<pre><nowiki><br />
RunMode = Daemon<br />
<br />
User = myuser<br />
<br />
ConfigDir = /home/myuser/<br />
</nowiki></pre><br />
(note - replace myuser above with the user name set up when installing optware as shown above)<br />
edit the configuration file mentioned with your editor of choice as root (vi, nano, or copy it over and copy back with winscp - whatever works for you)<br />
make sure any of those values that are leading with a # have it removed otherwise the value will not be set and it will be seen as a comment.<br />
<br />
=== Startup Script ===<br />
<br />
This script will load the daemon on-demand (may even be better this way as using less resources when you don't want to IM) and will automatically put the shell to your username instead of root (so you can use irssi more securely off the bat)<br />
<br />
Create a file called "im" (without quotes) in your /var/home/root directory with the following:<br />
<br />
<pre><nowiki><br />
#!/bin/sh<br />
#load bitlbee daemon and automatically load screen with a regular user session<br />
/opt/sbin/bitlbee<br />
screen su myuser<br />
<br />
</nowiki></pre><br />
<br />
You may now run this script at any time by opening up the terminal app and typing ./im<br />
<br />
=== Configure Bitlbee for your IM clients ===<br />
<br />
Running the 'im' script that you have now made will bring you to a prompt featuring your username such as <br />
<pre><nowiki><br />
myuser@castle:/var/home/root$<br />
</nowiki></pre><br />
<br />
'''Important Note''' In order for these changes to take effect the filesystem must be mounted as writeable, to do that as root user (or through sudo) please use the following command<br />
<br />
<pre><nowiki><br />
mount -o remount,rw /<br />
</nowiki></pre><br />
<br />
and please remember to change it back to read-only when you're finished by doing<br />
<br />
<pre><nowiki><br />
mount -o remount,ro /<br />
</nowiki></pre> <br />
<br />
From your user shell, load up irssi.<br />
<br />
Once loaded you can connect to the bitlbee daemon by doing /connect localhost<br />
<br />
Move to the second window (sym+n or orange key+space+2) and you will be at the bitlbee control channel &bitlbee<br />
<br />
You can have a flushed out description (and possibly understanding) of the following procedure [http://princessleia.com/bitlbee.php Here] - I am simply going to sum up the commands quickly. Note ignore all < > 's within the commands fill this with the respective needed values.<br />
<br />
While on the bitlbee control channel:<br />
<br />
Global Registration Password (you will input this single password and bitlbee will automatically log in to any IM accounts you set up)<br />
<br />
<pre><nowiki><br />
register <password><br />
</nowiki></pre> <br />
<br />
Add an IM account to the service:<br />
<br />
<pre><nowiki><br />
account add <protocol> <username> <password> [<server>].<br />
</nowiki></pre> <br />
oscar is the protocol used by ICQ and AOL. For MSN use msn, for Yahoo use yahoo and for Jabber use jabber)<br />
<br />
For oscar, you need to specify the IM-server as a fourth argument (for msn and yahoo there is no fourth argument). <br />
<br />
For AOL Instant Messenger, the server name is login.oscar.aol.com. For ICQ, the server name is login.icq.com.<br />
<br />
Repeat this as many times as needed for any IM accounts.<br />
<br />
<br />
=== Configure irssi to automatically connect to Bitlbee ===<br />
<br />
'''Important Note''' Please make sure the above procedure to make the filesystem writable was done or these changes WILL NOT BE SAVED.<br />
<br />
Now that we have set up the start up script, configured bitlbee with our IM services of choice, now we will make it so that when irssi loads it will automatically connect to the bitlbee daemon and identify with it so you can immediately begin IM'ing.<br />
<br />
Perform the following commands while in irssi<br />
<br />
<pre><nowiki><br />
/NETWORK ADD -autosendcmd "/^msg &bitlbee identify password" Bitlbee<br />
</nowiki></pre><br />
(please replace password in the command above with the one you set for your global Bitlbee password)<br />
<br />
<pre><nowiki><br />
/SERVER ADD -auto -network Bitlbee localhost 6667<br />
</nowiki></pre><br />
<br />
=== Final Setup & Thoughts / Running ===<br />
<br />
At this point you should be entirely set up with bitlbee and irssi. Make sure you set your filesystem back to read-only (see above). A good test would be to restart your pre entirely after setup and perform the following procedure. <br />
<br />
To get to a fully functional irssi w/IM protocols through bitlbee is only a three step process:<br />
<br />
1. Load up terminal application<br />
<br />
2. at the prompt type<br />
<pre><nowiki><br />
./im<br />
</nowiki></pre><br />
<br />
3. at the user prompt that loads, type<br />
<pre><nowiki><br />
irssi<br />
</nowiki></pre><br />
<br />
and there you are, enjoy multiple IM protocol chats natively on your webos device.<br />
<br />
If you are a new user to screen it's easy to get lost in multiple embedded screen sessions and such, if you find yourself loading multiple copies of the bitlbee daemon and need them closed (or you're done with your IM sessions and want to conserve as much battery as possible) simply run the following command and it will kill the service:<br />
<br />
<pre><nowiki><br />
pkill bitlbee <br />
</nowiki></pre><br />
<br />
== Configuration/Tweaks ==<br />
<br />
Both irssi and GNU Screen are very rich applications with a plethora of scripts, customization and usage options that only a very small percentage of are covered in this document. If interested please search and find how you may be able to adjust them to fit your specific needs (and if you find anything worthwhile feel free to add it to this wiki!)<br />
<br />
For information on irssi please visit their startup documentation http://irssi.org/documentation/startup <br />
<br />
This site provides information that will help you in automating irssi to do tasks like autojoin set servers and channels and automatically identify your nickname with services. <br />
<br />
== Known Issues ==<br />
<br />
When first loaded irssi tends to not properly format to the whole screen and a simple rotation to let the terminal rotate to the side and back to standard typing position will fix it (you will see the characters slowly refresh during this process)<br />
<br />
Even with Screen running you can lose connection if the wifi radio turns off when the screen does, see http://www.webos-internals.org/wiki/Patch_webOS_Keep_Phone_Awake_While_in_Remote_Session<br />
<br />
[[Image:Terminal-irssi.jpg]]</div>Punzadahttp://wiki.webos-internals.org/index.php?title=Linux_Tutorial_Irssi&diff=5836Linux Tutorial Irssi2009-09-17T23:34:15Z<p>Punzada: </p>
<hr />
<div>= Linux Tutorial - Irssi =<br />
<br />
=== Update 09/17/2009 === <br />
<br />
I have managed to get the [http://www.bitlbee.org/main.php/news.r.html BitlBee] service working with irssi for full AIM, MSN, Yahoo and Jabber support. I shall be doing my best to update this wiki with the best methods to get this working and configured easily and securely as soon as possible.<br />
<br />
=== This Document Assumes the following ===<br />
<br />
You have followed the procedure to Access Linux on the device and have enabled the Optware repositories and software [[Portal:Accessing_Linux]]<br />
<br />
You have installed the Terminal application [[Application:Terminal]]<br />
<br />
<br />
Once these procedures are done you should have access to:<br />
<br />
The Optware software repositories through ipkg-opt <br />
<br />
The Terminal Application through the WebOS (should load, be the root user, and function)<br />
<br />
<br />
<br />
== Installation ==<br />
<br />
Within the Terminal application use the following command:<br />
<br />
<pre><nowiki><br />
ipkg-opt install screen irssi<br />
</nowiki></pre><br />
<br />
This command will automatically download [http://www.gnu.org/software/screen/ GNU Screen] and [http://irssi.org/ irssi] as well as any necessary dependencies.<br />
<br />
Note: GNU Screen is *not* necessary for irssi to function, it only provides further functionality to be able to close the Terminal application if desired, keep irssi running in the background and reattach to it. Also, I have found that running irssi within a screen session gives irssi all its various colors while running natively within the terminal app leaves it mono-colored. <br />
<br />
<br />
== Usage ==<br />
<br />
In order to run irssi you simply need to type irssi into the Terminal application at the shell prompt and once hitting enter(return) it will load. <br />
<br />
However this is '''NOT RECOMMENDED''' as by default the Terminal Application is loaded as the root user and you should avoid using internet facing applications as the root user if it is not necessary (some IRC networks such as EFnet will go as far as to instantly disconnect you if it detects you are connecting to their servers as root). <br />
<br />
Once the Terminal Application is opened you may change to the user you set up when completing the steps to Access Linux via the su command<br />
<br />
example:<br />
<br />
<pre><nowiki><br />
root@castle:/var/home/root# su myuser<br />
myuser@castle:/var/home/root$<br />
</nowiki></pre><br />
<br />
from here you can simply enter irssi and hit return and it shall load.<br />
<br />
===Basic Commands===<br />
<br />
/connect ircserver<br />
<br />
This will connect you to an irc network ex: /connect irc.freenode.net will connect you to the freenode network.<br />
<br />
/join #channel<br />
<br />
This will join the requested channel, ex: /join #webos-internals<br />
<br />
Sym+n Will move to the 'next' window within the irssi interface<br />
Sym+p Will move you to the 'previous' window within the irssi interface<br />
<br />
You can directly jump to a window (numbered in irssi) by hitting Orange Key+Space+Number.<br />
<br />
===GNU Screen History & Basics===<br />
<br />
If you're like me and you want to always keep your irssi session active as well as have the colors available to you a good solution is to use GNU Screen.<br />
<br />
For those that don't know, screen acts as a window manager for terminal applications. Screen allows you to run multiple applications in a single terminal session, switch between the applications freely as well as being able to detach from it entirely, and reattach to it later while having those applications run in the background. Many consider screen to be one of the most important tools available for any type of command line work or administration - is is very powerful and very flexible, feel free to read up on it's customization and abilities to further enhance your experience with it.<br />
<br />
====Screen Usage====<br />
<br />
To start using screen it is very simple, follow the instructions above but before switching to your local user to run irssi, first type screen and hit enter<br />
<br />
You will be greeted with screen's opening text, letting you know that it is running, and the GPL license, simply press the space bar here and you will be taken back into the prompt and it will appear as if you're back to where you started.<br />
<br />
From this point on, follow the instructions above to change into your user that is not root, and open irssi like normal.<br />
<br />
You will see commands listed as such: Sym-A C <br />
<br />
This key combination is important because it means 'Press and hold Sym, then hit A, release both and hit C'<br />
<br />
This is how GNU Screen functions and is vital to it's usage, the example above creates a new window with a fresh terminal session.<br />
<br />
==== Attach / Detach ====<br />
<br />
In order to detach from your screen session use the command Sym-A D<br />
<br />
Once a session is detached you may close out of the terminal app and any applications running within your screen session will continue to run.<br />
<br />
In order to reattach to a session you left running, load the Terminal Application again and type the following at the command prompt and hit enter: screen -r<br />
<br />
<br />
==== Screen Commands To Know ====<br />
Sym-A C - Create a new window/terminal session<br />
<br />
Sym-A N - Change to next window/terminal session within the current screen session<br />
<br />
Sym-A P - Change to previous window/terminal session with the current screen session<br />
<br />
Sym-A D - Detach from current screen session<br />
<br />
== Bitlbee for Multi-IM ==<br />
<br />
[http://www.bitlbee.org/main.php/news.r.html BitlBee] is an IRC daemon that you can run to connect to basically all of the most popular IM protocols: XMPP/Jabber (including Google Talk), MSN Messenger, Yahoo! Messenger, AIM and ICQ.<br />
<br />
As of now we are able to install bitlbee on the linux subsystem, run it in daemon mode (I wasn't able to get it started with xinetd - will be investiating this further), launch it from a script when we wish to connect and set irssi to automatically connect, identify and load all of your IM accounts at once. <br />
<br />
<br />
<br />
'''The following procedure is how I have set mine up and there may be a sleeker/easier solution down the line''' try to think of this procedure as more 'proof of concept' then 'ready for the general public'<br />
<br />
first to install the necessary files (must be performed as root or privledged user with sudo from within the terminal application):<br />
<br />
<pre><nowiki><br />
ipkg-opt install screen irssi bitlbee<br />
</nowiki></pre><br />
<br />
=== Configure Bitlbee ===<br />
<br />
The only file that absolutely needs to be tweaked is located at /opt/etc/bitlbee/bitlbee.conf<br />
<br />
<pre><nowiki><br />
RunMode = Daemon<br />
<br />
User = myuser<br />
<br />
ConfigDir = /home/myuser/<br />
</nowiki></pre><br />
(note - replace myuser above with the user name set up when installing optware as shown above)<br />
edit the configuration file mentioned with your editor of choice as root (vi, nano, or copy it over and copy back with winscp - whatever works for you)<br />
make sure any of those values that are leading with a # have it removed otherwise the value will not be set and it will be seen as a comment.<br />
<br />
=== Startup Script ===<br />
<br />
This script will load the daemon on-demand (may even be better this way as using less resources when you don't want to IM) and will automatically put the shell to your username instead of root (so you can use irssi more securely off the bat)<br />
<br />
Create a file called "im" (without quotes) in your /var/home/root directory with the following:<br />
<br />
<pre><nowiki><br />
#!/bin/sh<br />
#load bitlbee daemon and automatically load screen with a regular user session<br />
/opt/sbin/bitlbee<br />
screen su myuser<br />
<br />
</nowiki></pre><br />
<br />
You may now run this script at any time by opening up the terminal app and typing ./im<br />
<br />
=== Configure Bitlbee for your IM clients ===<br />
<br />
Running the 'im' script that you have now made will bring you to a prompt featuring your username such as <br />
<pre><nowiki><br />
myuser@castle:/var/home/root$<br />
</nowiki></pre><br />
<br />
'''Important Note''' In order for these changes to take effect the filesystem must be mounted as writeable, to do that as root user (or through sudo) please use the following command<br />
<br />
<pre><nowiki><br />
mount -o remount,rw /<br />
</nowiki></pre><br />
<br />
and please remember to change it back to read-only when you're finished by doing<br />
<br />
<pre><nowiki><br />
mount -o remount,ro /<br />
</nowiki></pre> <br />
<br />
From your user shell, load up irssi.<br />
<br />
Once loaded you can connect to the bitlbee daemon by doing /connect localhost<br />
<br />
Move to the second window (sym+n or orange key+space+2) and you will be at the bitlbee control channel &bitlbee<br />
<br />
You can have a flushed out description (and possibly understanding) of the following procedure [http://princessleia.com/bitlbee.php Here] - I am simply going to sum up the commands quickly. Note ignore all < > 's within the commands fill this with the respective needed values.<br />
<br />
While on the bitlbee control channel:<br />
<br />
Global Registration Password (you will input this single password and bitlbee will automatically log in to any IM accounts you set up)<br />
<br />
<pre><nowiki><br />
register <password><br />
</nowiki></pre> <br />
<br />
Add an IM account to the service:<br />
<br />
<pre><nowiki><br />
account add <protocol> <username> <password> [<server>].<br />
</nowiki></pre> <br />
oscar is the protocol used by ICQ and AOL. For MSN use msn, for Yahoo use yahoo and for Jabber use jabber)<br />
<br />
For oscar, you need to specify the IM-server as a fourth argument (for msn and yahoo there is no fourth argument). <br />
<br />
For AOL Instant Messenger, the server name is login.oscar.aol.com. For ICQ, the server name is login.icq.com.<br />
<br />
Repeat this as many times as needed for any IM accounts.<br />
<br />
<br />
=== Configure irssi to automatically connect to Bitlbee ===<br />
<br />
'''Important Note''' Please make sure the above procedure to make the filesystem writable was done or these changes WILL NOT BE SAVED.<br />
<br />
Now that we have set up the start up script, configured bitlbee with our IM services of choice, now we will make it so that when irssi loads it will automatically connect to the bitlbee daemon and identify with it so you can immediately begin IM'ing.<br />
<br />
Perform the following commands while in irssi<br />
<br />
<pre><nowiki><br />
/NETWORK ADD -autosendcmd "/^msg &bitlbee identify password" Bitlbee<br />
</nowiki></pre><br />
(please replace password in the command above with the one you set for your global Bitlbee password)<br />
<br />
<pre><nowiki><br />
/SERVER ADD -auto -network Bitlbee localhost 6667<br />
</nowiki></pre><br />
<br />
=== Final Setup & Thoughts / Running ===<br />
<br />
At this point you should be entirely set up with bitlbee and irssi. Make sure you set your filesystem back to read-only (see above). A good test would be to restart your pre entirely after setup and perform the following procedure. <br />
<br />
To get to a fully functional irssi w/IM protocols through bitlbee is only a three step process:<br />
<br />
1. Load up terminal application<br />
<br />
2. at the prompt type<br />
<pre><nowiki><br />
./im<br />
</nowiki></pre><br />
<br />
3. at the user prompt that loads, type<br />
<pre><nowiki><br />
irssi<br />
</nowiki></pre><br />
<br />
and there you are, enjoy multiple IM protocol chats natively on your webos device.<br />
<br />
If you are a new user to screen it's easy to get lost in multiple embedded screen sessions and such, if you find yourself loading multiple copies of the bitlbee daemon and need them closed (or you're done with your IM sessions and want to conserve as much battery as possible) simply run the following command and it will kill the service:<br />
<br />
<pre><nowiki><br />
pkill bitlbee <br />
</nowiki></pre><br />
<br />
== Configuration/Tweaks ==<br />
<br />
Both irssi and GNU Screen are very rich applications with a plethora of scripts, customization and usage options that only a very small percentage of are covered in this document. If interested please search and find how you may be able to adjust them to fit your specific needs (and if you find anything worthwhile feel free to add it to this wiki!)<br />
<br />
For information on irssi please visit their startup documentation http://irssi.org/documentation/startup <br />
<br />
This site provides information that will help you in automating irssi to do tasks like autojoin set servers and channels and automatically identify your nickname with services. <br />
<br />
== Known Issues ==<br />
<br />
When first loaded irssi tends to not properly format to the whole screen and a simple rotation to let the terminal rotate to the side and back to standard typing position will fix it (you will see the characters slowly refresh during this process)<br />
<br />
Even with Screen running you can lose connection if the wifi radio turns off when the screen does, see http://www.webos-internals.org/wiki/Patch_webOS_Keep_Phone_Awake_While_in_Remote_Session<br />
<br />
[[Image:Terminal-irssi.jpg]]</div>Punzadahttp://wiki.webos-internals.org/index.php?title=Linux_Tutorial_Irssi&diff=5835Linux Tutorial Irssi2009-09-17T23:29:58Z<p>Punzada: </p>
<hr />
<div>= Linux Tutorial - Irssi =<br />
<br />
=== Update 09/17/2009 === <br />
<br />
I have managed to get the [http://www.bitlbee.org/main.php/news.r.html BitlBee] service working with irssi for full AIM, MSN, Yahoo and Jabber support. I shall be doing my best to update this wiki with the best methods to get this working and configured easily and securely as soon as possible.<br />
<br />
=== This Document Assumes the following ===<br />
<br />
You have followed the procedure to Access Linux on the device and have enabled the Optware repositories and software [[Portal:Accessing_Linux]]<br />
<br />
You have installed the Terminal application [[Application:Terminal]]<br />
<br />
<br />
Once these procedures are done you should have access to:<br />
<br />
The Optware software repositories through ipkg-opt <br />
<br />
The Terminal Application through the WebOS (should load, be the root user, and function)<br />
<br />
<br />
<br />
== Installation ==<br />
<br />
Within the Terminal application use the following command:<br />
<br />
<pre><nowiki><br />
ipkg-opt install screen irssi<br />
</nowiki></pre><br />
<br />
This command will automatically download [http://www.gnu.org/software/screen/ GNU Screen] and [http://irssi.org/ irssi] as well as any necessary dependencies.<br />
<br />
Note: GNU Screen is *not* necessary for irssi to function, it only provides further functionality to be able to close the Terminal application if desired, keep irssi running in the background and reattach to it. Also, I have found that running irssi within a screen session gives irssi all its various colors while running natively within the terminal app leaves it mono-colored. <br />
<br />
<br />
== Usage ==<br />
<br />
In order to run irssi you simply need to type irssi into the Terminal application at the shell prompt and once hitting enter(return) it will load. <br />
<br />
However this is '''NOT RECOMMENDED''' as by default the Terminal Application is loaded as the root user and you should avoid using internet facing applications as the root user if it is not necessary (some IRC networks such as EFnet will go as far as to instantly disconnect you if it detects you are connecting to their servers as root). <br />
<br />
Once the Terminal Application is opened you may change to the user you set up when completing the steps to Access Linux via the su command<br />
<br />
example:<br />
<br />
<pre><nowiki><br />
root@castle:/var/home/root# su myuser<br />
myuser@castle:/var/home/root$<br />
</nowiki></pre><br />
<br />
from here you can simply enter irssi and hit return and it shall load.<br />
<br />
===Basic Commands===<br />
<br />
/connect ircserver<br />
<br />
This will connect you to an irc network ex: /connect irc.freenode.net will connect you to the freenode network.<br />
<br />
/join #channel<br />
<br />
This will join the requested channel, ex: /join #webos-internals<br />
<br />
Sym+n Will move to the 'next' window within the irssi interface<br />
Sym+p Will move you to the 'previous' window within the irssi interface<br />
<br />
You can directly jump to a window (numbered in irssi) by hitting Orange Key+Space+Number.<br />
<br />
===GNU Screen History & Basics===<br />
<br />
If you're like me and you want to always keep your irssi session active as well as have the colors available to you a good solution is to use GNU Screen.<br />
<br />
For those that don't know, screen acts as a window manager for terminal applications. Screen allows you to run multiple applications in a single terminal session, switch between the applications freely as well as being able to detach from it entirely, and reattach to it later while having those applications run in the background. Many consider screen to be one of the most important tools available for any type of command line work or administration - is is very powerful and very flexible, feel free to read up on it's customization and abilities to further enhance your experience with it.<br />
<br />
====Screen Usage====<br />
<br />
To start using screen it is very simple, follow the instructions above but before switching to your local user to run irssi, first type screen and hit enter<br />
<br />
You will be greeted with screen's opening text, letting you know that it is running, and the GPL license, simply press the space bar here and you will be taken back into the prompt and it will appear as if you're back to where you started.<br />
<br />
From this point on, follow the instructions above to change into your user that is not root, and open irssi like normal.<br />
<br />
You will see commands listed as such: Sym-A C <br />
<br />
This key combination is important because it means 'Press and hold Sym, then hit A, release both and hit C'<br />
<br />
This is how GNU Screen functions and is vital to it's usage, the example above creates a new window with a fresh terminal session.<br />
<br />
==== Attach / Detach ====<br />
<br />
In order to detach from your screen session use the command Sym-A D<br />
<br />
Once a session is detached you may close out of the terminal app and any applications running within your screen session will continue to run.<br />
<br />
In order to reattach to a session you left running, load the Terminal Application again and type the following at the command prompt and hit enter: screen -r<br />
<br />
<br />
==== Screen Commands To Know ====<br />
Sym-A C - Create a new window/terminal session<br />
<br />
Sym-A N - Change to next window/terminal session within the current screen session<br />
<br />
Sym-A P - Change to previous window/terminal session with the current screen session<br />
<br />
Sym-A D - Detach from current screen session<br />
<br />
== Bitlbee for Multi-IM ==<br />
<br />
[http://www.bitlbee.org/main.php/news.r.html BitlBee] is an IRC daemon that you can run to connect to basically all of the most popular IM protocols: XMPP/Jabber (including Google Talk), MSN Messenger, Yahoo! Messenger, AIM and ICQ.<br />
<br />
As of now we are able to install bitlbee on the linux subsystem, run it in daemon mode (I wasn't able to get it started with xinetd - will be investiating this further), launch it from a script when we wish to connect and set irssi to automatically connect, identify and load all of your IM accounts at once. <br />
<br />
==== The following procedure is how I have set mine up and there may be a sleeker/easier solution down the line ====<br />
<br />
first to install the necessary files (must be performed as root or privledged user with sudo from within the terminal application):<br />
<br />
<pre><nowiki><br />
ipkg-opt install screen irssi bitlbee<br />
</nowiki></pre><br />
<br />
=== Configure Bitlbee ===<br />
<br />
The only file that absolutely needs to be tweaked is located at /opt/etc/bitlbee/bitlbee.conf<br />
<br />
<pre><nowiki><br />
RunMode = Daemon<br />
<br />
User = myuser<br />
<br />
ConfigDir = /home/myuser/<br />
</nowiki></pre><br />
(note - replace myuser above with the user name set up when installing optware as shown above)<br />
edit the configuration file mentioned with your editor of choice as root (vi, nano, or copy it over and copy back with winscp - whatever works for you)<br />
make sure any of those values that are leading with a # have it removed otherwise the value will not be set and it will be seen as a comment.<br />
<br />
=== Startup Script ===<br />
<br />
This script will load the daemon on-demand (may even be better this way as using less resources when you don't want to IM) and will automatically put the shell to your username instead of root (so you can use irssi more securely off the bat)<br />
<br />
Create a file called "im" (without quotes) in your /var/home/root directory with the following:<br />
<br />
<pre><nowiki><br />
#!/bin/sh<br />
#load bitlbee daemon and automatically load screen with a regular user session<br />
/opt/sbin/bitlbee<br />
screen su myuser<br />
<br />
</nowiki></pre><br />
<br />
You may now run this script at any time by opening up the terminal app and typing ./im<br />
<br />
=== Configure Bitlbee for your IM clients ===<br />
<br />
Running the 'im' script that you have now made will bring you to a prompt featuring your username such as <br />
<pre><nowiki><br />
myuser@castle:/var/home/root$<br />
</nowiki></pre><br />
<br />
'''Important Note''' In order for these changes to take effect the filesystem must be mounted as writeable, to do that as root user (or through sudo) please use the following command<br />
<br />
<pre><nowiki><br />
mount -o remount,rw /<br />
</nowiki></pre><br />
<br />
and please remember to change it back to read-only when you're finished by doing<br />
<br />
<pre><nowiki><br />
mount -o remount,ro /<br />
</nowiki></pre> <br />
<br />
From your user shell, load up irssi.<br />
<br />
Once loaded you can connect to the bitlbee daemon by doing /connect localhost<br />
<br />
Move to the second window (sym+n or orange key+space+2) and you will be at the bitlbee control channel &bitlbee<br />
<br />
You can have a flushed out description (and possibly understanding) of the following procedure [http://princessleia.com/bitlbee.php Here] - I am simply going to sum up the commands quickly. Note ignore all < > 's within the commands fill this with the respective needed values.<br />
<br />
While on the bitlbee control channel:<br />
<br />
Global Registration Password (you will input this single password and bitlbee will automatically log in to any IM accounts you set up)<br />
<br />
<pre><nowiki><br />
register <password><br />
</nowiki></pre> <br />
<br />
Add an IM account to the service:<br />
<br />
<pre><nowiki><br />
account add <protocol> <username> <password> [<server>].<br />
</nowiki></pre> <br />
oscar is the protocol used by ICQ and AOL. For MSN use msn, for Yahoo use yahoo and for Jabber use jabber)<br />
<br />
For oscar, you need to specify the IM-server as a fourth argument (for msn and yahoo there is no fourth argument). <br />
<br />
For AOL Instant Messenger, the server name is login.oscar.aol.com. For ICQ, the server name is login.icq.com.<br />
<br />
Repeat this as many times as needed for any IM accounts.<br />
<br />
<br />
=== Configure irssi to automatically connect to Bitlbee ===<br />
<br />
'''Important Note''' Please make sure the above procedure to make the filesystem writable was done or these changes WILL NOT BE SAVED.<br />
<br />
Now that we have set up the start up script, configured bitlbee with our IM services of choice, now we will make it so that when irssi loads it will automatically connect to the bitlbee daemon and identify with it so you can immediately begin IM'ing.<br />
<br />
Perform the following commands while in irssi<br />
<br />
<pre><nowiki><br />
/NETWORK ADD -autosendcmd "/^msg &bitlbee identify password" Bitlbee<br />
</nowiki></pre><br />
(please replace password in the command above with the one you set for your global Bitlbee password)<br />
<br />
<pre><nowiki><br />
/SERVER ADD -auto -network Bitlbee localhost 6667<br />
</nowiki></pre><br />
<br />
=== Final Setup & Thoughts / Running ===<br />
<br />
At this point you should be entirely set up with bitlbee and irssi. Make sure you set your filesystem back to read-only (see above). A good test would be to restart your pre entirely after setup and perform the following procedure. <br />
<br />
To get to a fully functional irssi w/IM protocols through bitlbee is only a three step process:<br />
<br />
1. Load up terminal application<br />
<br />
2. at the prompt type<br />
<pre><nowiki><br />
./im<br />
</nowiki></pre><br />
<br />
3. at the user prompt that loads, type<br />
<pre><nowiki><br />
irssi<br />
</nowiki></pre><br />
<br />
and there you are, enjoy multiple IM protocol chats natively on your webos device.<br />
<br />
If you are a new user to screen it's easy to get lost in multiple embedded screen sessions and such, if you find yourself loading multiple copies of the bitlbee daemon and need them closed (or you're done with your IM sessions and want to conserve as much battery as possible) simply run the following command and it will kill the service:<br />
<br />
<pre><nowiki><br />
pkill bitlbee <br />
</nowiki></pre><br />
<br />
== Configuration/Tweaks ==<br />
<br />
Both irssi and GNU Screen are very rich applications with a plethora of scripts, customization and usage options that only a very small percentage of are covered in this document. If interested please search and find how you may be able to adjust them to fit your specific needs (and if you find anything worthwhile feel free to add it to this wiki!)<br />
<br />
For information on irssi please visit their startup documentation http://irssi.org/documentation/startup <br />
<br />
This site provides information that will help you in automating irssi to do tasks like autojoin set servers and channels and automatically identify your nickname with services. <br />
<br />
== Known Issues ==<br />
<br />
When first loaded irssi tends to not properly format to the whole screen and a simple rotation to let the terminal rotate to the side and back to standard typing position will fix it (you will see the characters slowly refresh during this process)<br />
<br />
Even with Screen running you can lose connection if the wifi radio turns off when the screen does, see http://www.webos-internals.org/wiki/Patch_webOS_Keep_Phone_Awake_While_in_Remote_Session<br />
<br />
[[Image:Terminal-irssi.jpg]]</div>Punzadahttp://wiki.webos-internals.org/index.php?title=Linux_Tutorial_Irssi&diff=5834Linux Tutorial Irssi2009-09-17T23:17:24Z<p>Punzada: </p>
<hr />
<div>= Linux Tutorial - Irssi =<br />
<br />
=== Update 09/17/2009 === <br />
<br />
I have managed to get the [http://www.bitlbee.org/main.php/news.r.html BitlBee] service working with irssi for full AIM, MSN, Yahoo and Jabber support. I shall be doing my best to update this wiki with the best methods to get this working and configured easily and securely as soon as possible.<br />
<br />
=== This Document Assumes the following ===<br />
<br />
You have followed the procedure to Access Linux on the device and have enabled the Optware repositories and software [[Portal:Accessing_Linux]]<br />
<br />
You have installed the Terminal application [[Application:Terminal]]<br />
<br />
<br />
Once these procedures are done you should have access to:<br />
<br />
The Optware software repositories through ipkg-opt <br />
<br />
The Terminal Application through the WebOS (should load, be the root user, and function)<br />
<br />
<br />
<br />
== Installation ==<br />
<br />
Within the Terminal application use the following command:<br />
<br />
<pre><nowiki><br />
ipkg-opt install screen irssi<br />
</nowiki></pre><br />
<br />
This command will automatically download [http://www.gnu.org/software/screen/ GNU Screen] and [http://irssi.org/ irssi] as well as any necessary dependencies.<br />
<br />
Note: GNU Screen is *not* necessary for irssi to function, it only provides further functionality to be able to close the Terminal application if desired, keep irssi running in the background and reattach to it. Also, I have found that running irssi within a screen session gives irssi all its various colors while running natively within the terminal app leaves it mono-colored. <br />
<br />
<br />
== Usage ==<br />
<br />
In order to run irssi you simply need to type irssi into the Terminal application at the shell prompt and once hitting enter(return) it will load. <br />
<br />
However this is '''NOT RECOMMENDED''' as by default the Terminal Application is loaded as the root user and you should avoid using internet facing applications as the root user if it is not necessary (some IRC networks such as EFnet will go as far as to instantly disconnect you if it detects you are connecting to their servers as root). <br />
<br />
Once the Terminal Application is opened you may change to the user you set up when completing the steps to Access Linux via the su command<br />
<br />
example:<br />
<br />
<pre><nowiki><br />
root@castle:/var/home/root# su myuser<br />
myuser@castle:/var/home/root$<br />
</nowiki></pre><br />
<br />
from here you can simply enter irssi and hit return and it shall load.<br />
<br />
===Basic Commands===<br />
<br />
/connect ircserver<br />
<br />
This will connect you to an irc network ex: /connect irc.freenode.net will connect you to the freenode network.<br />
<br />
/join #channel<br />
<br />
This will join the requested channel, ex: /join #webos-internals<br />
<br />
Sym+n Will move to the 'next' window within the irssi interface<br />
Sym+p Will move you to the 'previous' window within the irssi interface<br />
<br />
You can directly jump to a window (numbered in irssi) by hitting Orange Key+Space+Number.<br />
<br />
===GNU Screen History & Basics===<br />
<br />
If you're like me and you want to always keep your irssi session active as well as have the colors available to you a good solution is to use GNU Screen.<br />
<br />
For those that don't know, screen acts as a window manager for terminal applications. Screen allows you to run multiple applications in a single terminal session, switch between the applications freely as well as being able to detach from it entirely, and reattach to it later while having those applications run in the background. Many consider screen to be one of the most important tools available for any type of command line work or administration - is is very powerful and very flexible, feel free to read up on it's customization and abilities to further enhance your experience with it.<br />
<br />
====Screen Usage====<br />
<br />
To start using screen it is very simple, follow the instructions above but before switching to your local user to run irssi, first type screen and hit enter<br />
<br />
You will be greeted with screen's opening text, letting you know that it is running, and the GPL license, simply press the space bar here and you will be taken back into the prompt and it will appear as if you're back to where you started.<br />
<br />
From this point on, follow the instructions above to change into your user that is not root, and open irssi like normal.<br />
<br />
You will see commands listed as such: Sym-A C <br />
<br />
This key combination is important because it means 'Press and hold Sym, then hit A, release both and hit C'<br />
<br />
This is how GNU Screen functions and is vital to it's usage, the example above creates a new window with a fresh terminal session.<br />
<br />
==== Attach / Detach ====<br />
<br />
In order to detach from your screen session use the command Sym-A D<br />
<br />
Once a session is detached you may close out of the terminal app and any applications running within your screen session will continue to run.<br />
<br />
In order to reattach to a session you left running, load the Terminal Application again and type the following at the command prompt and hit enter: screen -r<br />
<br />
<br />
==== Screen Commands To Know ====<br />
Sym-A C - Create a new window/terminal session<br />
<br />
Sym-A N - Change to next window/terminal session within the current screen session<br />
<br />
Sym-A P - Change to previous window/terminal session with the current screen session<br />
<br />
Sym-A D - Detach from current screen session<br />
<br />
== Bitlbee for Multi-IM ==<br />
<br />
[http://www.bitlbee.org/main.php/news.r.html BitlBee] is an IRC daemon that you can run to connect to basically all of the most popular IM protocols: XMPP/Jabber (including Google Talk), MSN Messenger, Yahoo! Messenger, AIM and ICQ.<br />
<br />
As of now we are able to install bitlbee on the linux subsystem, run it in daemon mode (I wasn't able to get it started with xinetd - will be investiating this further), launch it from a script when we wish to connect and set irssi to automatically connect, identify and load all of your IM accounts at once. <br />
<br />
==== The following procedure is how I have set mine up and there may be a sleeker/easier solution down the line ====<br />
<br />
first to install the necessary files (must be performed as root or privledged user with sudo from within the terminal application):<br />
<br />
<pre><nowiki><br />
ipkg-opt install screen irssi bitlbee<br />
</nowiki></pre><br />
<br />
=== Configure Bitlbee ===<br />
<br />
The only file that absolutely needs to be tweaked is located at /opt/etc/bitlbee/bitlbee.conf<br />
<br />
<pre><nowiki><br />
RunMode = Daemon<br />
<br />
User = myuser<br />
<br />
ConfigDir = /home/myuser/<br />
</nowiki></pre><br />
(note - replace myuser above with the user name set up when installing optware as shown above)<br />
edit the configuration file mentioned with your editor of choice as root (vi, nano, or copy it over and copy back with winscp - whatever works for you)<br />
make sure any of those values that are leading with a # have it removed otherwise the value will not be set and it will be seen as a comment.<br />
<br />
=== Startup Script ===<br />
<br />
This script will load the daemon on-demand (may even be better this way as using less resources when you don't want to IM) and will automatically put the shell to your username instead of root (so you can use irssi more securely off the bat)<br />
<br />
Create a file called "im" (without quotes) in your /var/home/root directory with the following:<br />
<br />
<pre><nowiki><br />
#!/bin/sh<br />
#load bitlbee daemon and automatically load screen with a regular user session<br />
/opt/sbin/bitlbee<br />
screen su myuser<br />
<br />
</nowiki></pre><br />
<br />
You may now run this script at any time by opening up the terminal app and typing ./im<br />
<br />
=== Configure Bitlbee for your IM clients ===<br />
<br />
Running the 'im' script that you have now made will bring you to a prompt featuring your username such as <br />
<pre><nowiki><br />
myuser@castle:/var/home/root$<br />
</nowiki></pre><br />
<br />
'''Important Note''' In order for these changes to take effect the filesystem must be mounted as writeable, to do that as root user (or through sudo) please use the following command<br />
<br />
<pre><nowiki><br />
mount -o remount,rw /<br />
</nowiki></pre><br />
<br />
and please remember to change it back to read-only when you're finished by doing<br />
<br />
<pre><nowiki><br />
mount -o remount,ro /<br />
</nowiki></pre> <br />
<br />
From your user shell, load up irssi.<br />
<br />
Once loaded you can connect to the bitlbee daemon by doing /connect localhost<br />
<br />
Move to the second window (sym+n or orange key+space+2) and you will be at the bitlbee control channel &bitlbee<br />
<br />
You can have a flushed out description (and possibly understanding) of the following procedure [http://princessleia.com/bitlbee.php Here] - I am simply going to sum up the commands quickly. Note ignore all < > 's within the commands fill this with the respective needed values.<br />
<br />
While on the bitlbee control channel:<br />
<br />
Global Registration Password (you will input this single password and bitlbee will automatically log in to any IM accounts you set up)<br />
<br />
<pre><nowiki><br />
register <password><br />
</nowiki></pre> <br />
<br />
Add an IM account to the service:<br />
<br />
<pre><nowiki><br />
account add <protocol> <username> <password> [<server>].<br />
</nowiki></pre> <br />
Oscar is the protocol used by ICQ and AOL. <br />
<br />
For oscar, you need to specify the IM-server as a fourth argument (for msn and yahoo there is no fourth argument). <br />
<br />
For AOL Instant Messenger, the server name is login.oscar.aol.com. For ICQ, the server name is login.icq.com.<br />
<br />
<br />
=== Configure irssi to automatically connect to Bitlbee ===<br />
<br />
'''Important Note''' Please make sure the above procedure to make the filesystem writable was done or these changes WILL NOT BE SAVED.<br />
<br />
Now that we have set up the start up script, configured bitlbee with our IM services of choice, now we will make it so that when irssi loads it will automatically connect to the bitlbee daemon and identify with it so you can immediately begin IM'ing.<br />
<br />
Perform the following commands while in irssi<br />
<br />
<pre><nowiki><br />
/NETWORK ADD -autosendcmd "/^msg &bitlbee identify password" Bitlbee<br />
</nowiki></pre><br />
(please replace password in the command above with the one you set for your global Bitlbee password)<br />
<br />
<pre><nowiki><br />
/SERVER ADD -auto -network Bitlbee localhost 6667<br />
</nowiki></pre><br />
<br />
<br />
== Configuration/Tweaks ==<br />
<br />
Both irssi and GNU Screen are very rich applications with a plethora of scripts, customization and usage options that only a very small percentage of are covered in this document. If interested please search and find how you may be able to adjust them to fit your specific needs (and if you find anything worthwhile feel free to add it to this wiki!)<br />
<br />
For information on irssi please visit their startup documentation http://irssi.org/documentation/startup <br />
<br />
This site provides information that will help you in automating irssi to do tasks like autojoin set servers and channels and automatically identify your nickname with services. <br />
<br />
== Known Issues ==<br />
<br />
When first loaded irssi tends to not properly format to the whole screen and a simple rotation to let the terminal rotate to the side and back to standard typing position will fix it (you will see the characters slowly refresh during this process)<br />
<br />
Even with Screen running you can lose connection if the wifi radio turns off when the screen does, see http://www.webos-internals.org/wiki/Patch_webOS_Keep_Phone_Awake_While_in_Remote_Session<br />
<br />
[[Image:Terminal-irssi.jpg]]</div>Punzadahttp://wiki.webos-internals.org/index.php?title=Linux_Tutorial_Irssi&diff=5833Linux Tutorial Irssi2009-09-17T23:10:12Z<p>Punzada: </p>
<hr />
<div>= Linux Tutorial - Irssi =<br />
<br />
=== Update 09/17/2009 === <br />
<br />
I have managed to get the [http://www.bitlbee.org/main.php/news.r.html BitlBee] service working with irssi for full AIM, MSN, Yahoo and Jabber support. I shall be doing my best to update this wiki with the best methods to get this working and configured easily and securely as soon as possible.<br />
<br />
=== This Document Assumes the following ===<br />
<br />
You have followed the procedure to Access Linux on the device and have enabled the Optware repositories and software [[Portal:Accessing_Linux]]<br />
<br />
You have installed the Terminal application [[Application:Terminal]]<br />
<br />
<br />
Once these procedures are done you should have access to:<br />
<br />
The Optware software repositories through ipkg-opt <br />
<br />
The Terminal Application through the WebOS (should load, be the root user, and function)<br />
<br />
<br />
<br />
== Installation ==<br />
<br />
Within the Terminal application use the following command:<br />
<br />
<pre><nowiki><br />
ipkg-opt install screen irssi<br />
</nowiki></pre><br />
<br />
This command will automatically download [http://www.gnu.org/software/screen/ GNU Screen] and [http://irssi.org/ irssi] as well as any necessary dependencies.<br />
<br />
Note: GNU Screen is *not* necessary for irssi to function, it only provides further functionality to be able to close the Terminal application if desired, keep irssi running in the background and reattach to it. Also, I have found that running irssi within a screen session gives irssi all its various colors while running natively within the terminal app leaves it mono-colored. <br />
<br />
<br />
== Usage ==<br />
<br />
In order to run irssi you simply need to type irssi into the Terminal application at the shell prompt and once hitting enter(return) it will load. <br />
<br />
However this is '''NOT RECOMMENDED''' as by default the Terminal Application is loaded as the root user and you should avoid using internet facing applications as the root user if it is not necessary (some IRC networks such as EFnet will go as far as to instantly disconnect you if it detects you are connecting to their servers as root). <br />
<br />
Once the Terminal Application is opened you may change to the user you set up when completing the steps to Access Linux via the su command<br />
<br />
example:<br />
<br />
<pre><nowiki><br />
root@castle:/var/home/root# su myuser<br />
myuser@castle:/var/home/root$<br />
</nowiki></pre><br />
<br />
from here you can simply enter irssi and hit return and it shall load.<br />
<br />
===Basic Commands===<br />
<br />
/connect ircserver<br />
<br />
This will connect you to an irc network ex: /connect irc.freenode.net will connect you to the freenode network.<br />
<br />
/join #channel<br />
<br />
This will join the requested channel, ex: /join #webos-internals<br />
<br />
Sym+n Will move to the 'next' window within the irssi interface<br />
Sym+p Will move you to the 'previous' window within the irssi interface<br />
<br />
You can directly jump to a window (numbered in irssi) by hitting Orange Key+Space+Number.<br />
<br />
===GNU Screen History & Basics===<br />
<br />
If you're like me and you want to always keep your irssi session active as well as have the colors available to you a good solution is to use GNU Screen.<br />
<br />
For those that don't know, screen acts as a window manager for terminal applications. Screen allows you to run multiple applications in a single terminal session, switch between the applications freely as well as being able to detach from it entirely, and reattach to it later while having those applications run in the background. Many consider screen to be one of the most important tools available for any type of command line work or administration - is is very powerful and very flexible, feel free to read up on it's customization and abilities to further enhance your experience with it.<br />
<br />
====Screen Usage====<br />
<br />
To start using screen it is very simple, follow the instructions above but before switching to your local user to run irssi, first type screen and hit enter<br />
<br />
You will be greeted with screen's opening text, letting you know that it is running, and the GPL license, simply press the space bar here and you will be taken back into the prompt and it will appear as if you're back to where you started.<br />
<br />
From this point on, follow the instructions above to change into your user that is not root, and open irssi like normal.<br />
<br />
You will see commands listed as such: Sym-A C <br />
<br />
This key combination is important because it means 'Press and hold Sym, then hit A, release both and hit C'<br />
<br />
This is how GNU Screen functions and is vital to it's usage, the example above creates a new window with a fresh terminal session.<br />
<br />
==== Attach / Detach ====<br />
<br />
In order to detach from your screen session use the command Sym-A D<br />
<br />
Once a session is detached you may close out of the terminal app and any applications running within your screen session will continue to run.<br />
<br />
In order to reattach to a session you left running, load the Terminal Application again and type the following at the command prompt and hit enter: screen -r<br />
<br />
<br />
==== Screen Commands To Know ====<br />
Sym-A C - Create a new window/terminal session<br />
<br />
Sym-A N - Change to next window/terminal session within the current screen session<br />
<br />
Sym-A P - Change to previous window/terminal session with the current screen session<br />
<br />
Sym-A D - Detach from current screen session<br />
<br />
== Bitlbee for Multi-IM ==<br />
<br />
[http://www.bitlbee.org/main.php/news.r.html BitlBee] is an IRC daemon that you can run to connect to basically all of the most popular IM protocols: XMPP/Jabber (including Google Talk), MSN Messenger, Yahoo! Messenger, AIM and ICQ.<br />
<br />
As of now we are able to install bitlbee on the linux subsystem, run it in daemon mode (I wasn't able to get it started with xinetd - will be investiating this further), launch it from a script when we wish to connect and set irssi to automatically connect, identify and load all of your IM accounts at once. <br />
<br />
==== The following procedure is how I have set mine up and there may be a sleeker/easier solution down the line ====<br />
<br />
first to install the necessary files (must be performed as root or privledged user with sudo from within the terminal application):<br />
<br />
<pre><nowiki><br />
ipkg-opt install screen irssi bitlbee<br />
</nowiki></pre><br />
<br />
=== Configure Bitlbee ===<br />
<br />
The only file that absolutely needs to be tweaked is located at /opt/etc/bitlbee/bitlbee.conf<br />
<br />
<pre><nowiki><br />
RunMode = Daemon<br />
<br />
User = myuser<br />
<br />
ConfigDir = /home/myuser/<br />
</nowiki></pre><br />
(note - replace myuser above with the user name set up when installing optware as shown above)<br />
edit the configuration file mentioned with your editor of choice as root (vi, nano, or copy it over and copy back with winscp - whatever works for you)<br />
make sure any of those values that are leading with a # have it removed otherwise the value will not be set and it will be seen as a comment.<br />
<br />
=== Startup Script ===<br />
<br />
This script will load the daemon on-demand (may even be better this way as using less resources when you don't want to IM) and will automatically put the shell to your username instead of root (so you can use irssi more securely off the bat)<br />
<br />
Create a file called "im" (without quotes) in your /var/home/root directory with the following:<br />
<br />
<pre><nowiki><br />
#!/bin/sh<br />
#load bitlbee daemon and automatically load screen with a regular user session<br />
/opt/sbin/bitlbee<br />
screen su myuser<br />
<br />
</nowiki></pre><br />
<br />
You may now run this script at any time by opening up the terminal app and typing ./im<br />
<br />
=== Configure Bitlbee for your IM clients ===<br />
<br />
Running the 'im' script that you have now made will bring you to a prompt featuring your username such as <br />
<pre><nowiki><br />
myuser@castle:/var/home/root$<br />
</nowiki></pre><br />
<br />
'''Important Note''' In order for these changes to take effect the filesystem must be mounted as writeable, to do that as root user (or through sudo) please use the following command<br />
<br />
<pre><nowiki><br />
mount -o remount,rw /<br />
</nowiki></pre><br />
<br />
and please remember to change it back to read-only when you're finished by doing<br />
<br />
<pre><nowiki><br />
mount -o remount,ro /<br />
</nowiki></pre> <br />
<br />
From your user shell, load up irssi.<br />
<br />
Once loaded you can connect to the bitlbee daemon by doing /connect localhost<br />
<br />
Move to the second window (sym+n or orange key+space+2) and you will be at the bitlbee control channel &bitlbee<br />
<br />
You can have a flushed out description (and possibly understanding) of the following procedure [http://princessleia.com/bitlbee.php Here] - I am simply going to sum up the commands quickly. Note ignore all < > 's within the commands fill this with the respective needed values.<br />
<br />
While on the bitlbee control channel:<br />
<br />
Global Registration Password (you will input this single password and bitlbee will automatically log in to any IM accounts you set up)<br />
<br />
<pre><nowiki><br />
register <password><br />
</nowiki></pre> <br />
<br />
Add an IM account to the service:<br />
<br />
<pre><nowiki><br />
account add <protocol> <username> <password> [<server>].<br />
</nowiki></pre> <br />
Oscar is the protocol used by ICQ and AOL. <br />
<br />
For oscar, you need to specify the IM-server as a fourth argument (for msn and yahoo there is no fourth argument). <br />
<br />
For AOL Instant Messenger, the server name is login.oscar.aol.com. For ICQ, the server name is login.icq.com.<br />
<br />
<br />
=== Configure irssi to automatically connect to Bitlbee ===<br />
<br />
== Configuration/Tweaks ==<br />
<br />
Both irssi and GNU Screen are very rich applications with a plethora of scripts, customization and usage options that only a very small percentage of are covered in this document. If interested please search and find how you may be able to adjust them to fit your specific needs (and if you find anything worthwhile feel free to add it to this wiki!)<br />
<br />
For information on irssi please visit their startup documentation http://irssi.org/documentation/startup <br />
<br />
This site provides information that will help you in automating irssi to do tasks like autojoin set servers and channels and automatically identify your nickname with services. <br />
<br />
== Known Issues ==<br />
<br />
When first loaded irssi tends to not properly format to the whole screen and a simple rotation to let the terminal rotate to the side and back to standard typing position will fix it (you will see the characters slowly refresh during this process)<br />
<br />
Even with Screen running you can lose connection if the wifi radio turns off when the screen does, see http://www.webos-internals.org/wiki/Patch_webOS_Keep_Phone_Awake_While_in_Remote_Session<br />
<br />
[[Image:Terminal-irssi.jpg]]</div>Punzadahttp://wiki.webos-internals.org/index.php?title=Linux_Tutorial_Irssi&diff=5832Linux Tutorial Irssi2009-09-17T22:52:51Z<p>Punzada: </p>
<hr />
<div>= Linux Tutorial - Irssi =<br />
<br />
=== Update 09/17/2009 === <br />
<br />
I have managed to get the [http://www.bitlbee.org/main.php/news.r.html BitlBee] service working with irssi for full AIM, MSN, Yahoo and Jabber support. I shall be doing my best to update this wiki with the best methods to get this working and configured easily and securely as soon as possible.<br />
<br />
=== This Document Assumes the following ===<br />
<br />
You have followed the procedure to Access Linux on the device and have enabled the Optware repositories and software [[Portal:Accessing_Linux]]<br />
<br />
You have installed the Terminal application [[Application:Terminal]]<br />
<br />
<br />
Once these procedures are done you should have access to:<br />
<br />
The Optware software repositories through ipkg-opt <br />
<br />
The Terminal Application through the WebOS (should load, be the root user, and function)<br />
<br />
<br />
<br />
== Installation ==<br />
<br />
Within the Terminal application use the following command:<br />
<br />
<pre><nowiki><br />
ipkg-opt install screen irssi<br />
</nowiki></pre><br />
<br />
This command will automatically download [http://www.gnu.org/software/screen/ GNU Screen] and [http://irssi.org/ irssi] as well as any necessary dependencies.<br />
<br />
Note: GNU Screen is *not* necessary for irssi to function, it only provides further functionality to be able to close the Terminal application if desired, keep irssi running in the background and reattach to it. Also, I have found that running irssi within a screen session gives irssi all its various colors while running natively within the terminal app leaves it mono-colored. <br />
<br />
<br />
== Usage ==<br />
<br />
In order to run irssi you simply need to type irssi into the Terminal application at the shell prompt and once hitting enter(return) it will load. <br />
<br />
However this is '''NOT RECOMMENDED''' as by default the Terminal Application is loaded as the root user and you should avoid using internet facing applications as the root user if it is not necessary (some IRC networks such as EFnet will go as far as to instantly disconnect you if it detects you are connecting to their servers as root). <br />
<br />
Once the Terminal Application is opened you may change to the user you set up when completing the steps to Access Linux via the su command<br />
<br />
example:<br />
<br />
<pre><nowiki><br />
root@castle:/var/home/root# su myuser<br />
myuser@castle:/var/home/root$<br />
</nowiki></pre><br />
<br />
from here you can simply enter irssi and hit return and it shall load.<br />
<br />
===Basic Commands===<br />
<br />
/connect ircserver<br />
<br />
This will connect you to an irc network ex: /connect irc.freenode.net will connect you to the freenode network.<br />
<br />
/join #channel<br />
<br />
This will join the requested channel, ex: /join #webos-internals<br />
<br />
Sym+n Will move to the 'next' window within the irssi interface<br />
Sym+p Will move you to the 'previous' window within the irssi interface<br />
<br />
You can directly jump to a window (numbered in irssi) by hitting Orange Key+Space+Number.<br />
<br />
===GNU Screen History & Basics===<br />
<br />
If you're like me and you want to always keep your irssi session active as well as have the colors available to you a good solution is to use GNU Screen.<br />
<br />
For those that don't know, screen acts as a window manager for terminal applications. Screen allows you to run multiple applications in a single terminal session, switch between the applications freely as well as being able to detach from it entirely, and reattach to it later while having those applications run in the background. Many consider screen to be one of the most important tools available for any type of command line work or administration - is is very powerful and very flexible, feel free to read up on it's customization and abilities to further enhance your experience with it.<br />
<br />
====Screen Usage====<br />
<br />
To start using screen it is very simple, follow the instructions above but before switching to your local user to run irssi, first type screen and hit enter<br />
<br />
You will be greeted with screen's opening text, letting you know that it is running, and the GPL license, simply press the space bar here and you will be taken back into the prompt and it will appear as if you're back to where you started.<br />
<br />
From this point on, follow the instructions above to change into your user that is not root, and open irssi like normal.<br />
<br />
You will see commands listed as such: Sym-A C <br />
<br />
This key combination is important because it means 'Press and hold Sym, then hit A, release both and hit C'<br />
<br />
This is how GNU Screen functions and is vital to it's usage, the example above creates a new window with a fresh terminal session.<br />
<br />
==== Attach / Detach ====<br />
<br />
In order to detach from your screen session use the command Sym-A D<br />
<br />
Once a session is detached you may close out of the terminal app and any applications running within your screen session will continue to run.<br />
<br />
In order to reattach to a session you left running, load the Terminal Application again and type the following at the command prompt and hit enter: screen -r<br />
<br />
<br />
==== Screen Commands To Know ====<br />
Sym-A C - Create a new window/terminal session<br />
<br />
Sym-A N - Change to next window/terminal session within the current screen session<br />
<br />
Sym-A P - Change to previous window/terminal session with the current screen session<br />
<br />
Sym-A D - Detach from current screen session<br />
<br />
== Bitlbee for Multi-IM ==<br />
<br />
[http://www.bitlbee.org/main.php/news.r.html BitlBee] for those that don't know is an IRC daemon that you can run to connect to basically all of the most popular IM protocols: XMPP/Jabber (including Google Talk), MSN Messenger, Yahoo! Messenger, AIM and ICQ.<br />
<br />
As of now we are able to install bitlbee on the linux subsystem, run it in daemon mode (I wasn't able to get it started with xinetd - will be investiating this further), launch it from a script when we wish to connect and set irssi to automatically connect, identify and load all of your IM accounts at once. <br />
<br />
==== The following procedure is how I have set mine up and there may be a sleeker/easier solution down the line ====<br />
<br />
first to install the necessary files (must be performed as root or privledged user with sudo from within the terminal application):<br />
<br />
<pre><nowiki><br />
ipkg-opt install screen irssi bitlbee<br />
</nowiki></pre><br />
<br />
=== Configure Bitlbee ===<br />
<br />
The only file that absolutely needs to be tweaked is located at /opt/etc/bitlbee/bitlbee.conf<br />
<br />
<pre><nowiki><br />
RunMode = Daemon<br />
<br />
User = myuser<br />
<br />
ConfigDir = /home/myuser/<br />
</nowiki></pre><br />
(note - replace myuser above with the user name set up when installing optware as shown above)<br />
edit the configuration file mentioned with your editor of choice (vi, nano, or copy it over and copy back with winscp whatever works for you)<br />
make sure any of those values that are leading with a # have it removed otherwise the value will not be set and it will be seen as a comment.<br />
<br />
=== Startup Script ===<br />
<br />
This script will load the daemon on-demand (may even be better this way as using less resources when you don't want to IM) and will automatically put the shell to your username instead of root (so you can use irssi more securely off the bat)<br />
<br />
Create a file called "im" (without quotes) in your /var/home/root directory with the following:<br />
<br />
<pre><nowiki><br />
#!/bin/sh<br />
#load bitlbee daemon and automatically load screen with a regular user session<br />
/opt/sbin/bitlbee<br />
screen su myuser<br />
<br />
</nowiki></pre><br />
<br />
You may now run this script at any time by opening up the terminal app and typing ./im<br />
<br />
=== Configure Bitlbee for your IM clients ===<br />
<br />
Running the 'im' script that you have now made will bring you to a prompt featuring your username such as <br />
<br />
'''Important Note''' In order for these changes to take effect the filesystem must be mounted as rw, to do that as root user (or through sudo) please use the following command<br />
<br />
<pre><nowiki><br />
mount -o remount,rw /<br />
</nowiki></pre><br />
<br />
=== Configure irssi to automatically connect to Bitlbee ===<br />
<br />
== Configuration/Tweaks ==<br />
<br />
Both irssi and GNU Screen are very rich applications with a plethora of scripts, customization and usage options that only a very small percentage of are covered in this document. If interested please search and find how you may be able to adjust them to fit your specific needs (and if you find anything worthwhile feel free to add it to this wiki!)<br />
<br />
For information on irssi please visit their startup documentation http://irssi.org/documentation/startup <br />
<br />
This site provides information that will help you in automating irssi to do tasks like autojoin set servers and channels and automatically identify your nickname with services. <br />
<br />
== Known Issues ==<br />
<br />
When first loaded irssi tends to not properly format to the whole screen and a simple rotation to let the terminal rotate to the side and back to standard typing position will fix it (you will see the characters slowly refresh during this process)<br />
<br />
Even with Screen running you can lose connection if the wifi radio turns off when the screen does, see http://www.webos-internals.org/wiki/Patch_webOS_Keep_Phone_Awake_While_in_Remote_Session<br />
<br />
[[Image:Terminal-irssi.jpg]]</div>Punzadahttp://wiki.webos-internals.org/index.php?title=Linux_Tutorial_Irssi&diff=5829Linux Tutorial Irssi2009-09-17T20:32:53Z<p>Punzada: </p>
<hr />
<div>= Linux Tutorial - Irssi =<br />
<br />
=== Update 09/17/2009 === <br />
<br />
I have managed to get the [http://www.bitlbee.org/main.php/news.r.html BitlBee] service working with irssi for full AIM, MSN, Yahoo and Jabber support. I shall be doing my best to update this wiki with the best methods to get this working and configured easily and securely as soon as possible.<br />
<br />
=== This Document Assumes the following ===<br />
<br />
You have followed the procedure to Access Linux on the device and have enabled the Optware repositories and software [[Portal:Accessing_Linux]]<br />
<br />
You have installed the Terminal application [[Application:Terminal]]<br />
<br />
<br />
Once these procedures are done you should have access to:<br />
<br />
The Optware software repositories through ipkg-opt <br />
<br />
The Terminal Application through the WebOS (should load, be the root user, and function)<br />
<br />
<br />
<br />
== Installation ==<br />
<br />
Within the Terminal application use the following command:<br />
<br />
<pre><nowiki><br />
ipkg-opt install screen irssi<br />
</nowiki></pre><br />
<br />
This command will automatically download [http://www.gnu.org/software/screen/ GNU Screen] and [http://irssi.org/ irssi] as well as any necessary dependencies.<br />
<br />
Note: GNU Screen is *not* necessary for irssi to function, it only provides further functionality to be able to close the Terminal application if desired, keep irssi running in the background and reattach to it. Also, I have found that running irssi within a screen session gives irssi all its various colors while running natively within the terminal app leaves it mono-colored. <br />
<br />
<br />
== Usage ==<br />
<br />
In order to run irssi you simply need to type irssi into the Terminal application at the shell prompt and once hitting enter(return) it will load. <br />
<br />
However this is '''NOT RECOMMENDED''' as by default the Terminal Application is loaded as the root user and you should avoid using internet facing applications as the root user if it is not necessary (some IRC networks such as EFnet will go as far as to instantly disconnect you if it detects you are connecting to their servers as root). <br />
<br />
Once the Terminal Application is opened you may change to the user you set up when completing the steps to Access Linux via the su command<br />
<br />
example:<br />
<br />
<pre><nowiki><br />
root@castle:/var/home/root# su myuser<br />
myuser@castle:/var/home/root$<br />
</nowiki></pre><br />
<br />
from here you can simply enter irssi and hit return and it shall load.<br />
<br />
===Basic Commands===<br />
<br />
/connect ircserver<br />
<br />
This will connect you to an irc network ex: /connect irc.freenode.net will connect you to the freenode network.<br />
<br />
/join #channel<br />
<br />
This will join the requested channel, ex: /join #webos-internals<br />
<br />
Sym+n Will move to the 'next' window within the irssi interface<br />
Sym+p Will move you to the 'previous' window within the irssi interface<br />
<br />
You can directly jump to a window (numbered in irssi) by hitting Orange Key+Space+Number.<br />
<br />
===GNU Screen History & Basics===<br />
<br />
If you're like me and you want to always keep your irssi session active as well as have the colors available to you a good solution is to use GNU Screen.<br />
<br />
For those that don't know, screen acts as a window manager for terminal applications. Screen allows you to run multiple applications in a single terminal session, switch between the applications freely as well as being able to detach from it entirely, and reattach to it later while having those applications run in the background. Many consider screen to be one of the most important tools available for any type of command line work or administration - is is very powerful and very flexible, feel free to read up on it's customization and abilities to further enhance your experience with it.<br />
<br />
====Screen Usage====<br />
<br />
To start using screen it is very simple, follow the instructions above but before switching to your local user to run irssi, first type screen and hit enter<br />
<br />
You will be greeted with screen's opening text, letting you know that it is running, and the GPL license, simply press the space bar here and you will be taken back into the prompt and it will appear as if you're back to where you started.<br />
<br />
From this point on, follow the instructions above to change into your user that is not root, and open irssi like normal.<br />
<br />
You will see commands listed as such: Sym-A C <br />
<br />
This key combination is important because it means 'Press and hold Sym, then hit A, release both and hit C'<br />
<br />
This is how GNU Screen functions and is vital to it's usage, the example above creates a new window with a fresh terminal session.<br />
<br />
==== Attach / Detach ====<br />
<br />
In order to detach from your screen session use the command Sym-A D<br />
<br />
Once a session is detached you may close out of the terminal app and any applications running within your screen session will continue to run.<br />
<br />
In order to reattach to a session you left running, load the Terminal Application again and type the following at the command prompt and hit enter: screen -r<br />
<br />
<br />
==== Screen Commands To Know ====<br />
Sym-A C - Create a new window/terminal session<br />
<br />
Sym-A N - Change to next window/terminal session within the current screen session<br />
<br />
Sym-A P - Change to previous window/terminal session with the current screen session<br />
<br />
Sym-A D - Detach from current screen session<br />
<br />
== Configuration/Tweaks ==<br />
<br />
Both irssi and GNU Screen are very rich applications with a plethora of scripts, customization and usage options that only a very small percentage of are covered in this document. If interested please search and find how you may be able to adjust them to fit your specific needs (and if you find anything worthwhile feel free to add it to this wiki!)<br />
<br />
For information on irssi please visit their startup documentation http://irssi.org/documentation/startup <br />
<br />
This site provides information that will help you in automating irssi to do tasks like autojoin set servers and channels and automatically identify your nickname with services. <br />
<br />
== Known Issues ==<br />
<br />
When first loaded irssi tends to not properly format to the whole screen and a simple rotation to let the terminal rotate to the side and back to standard typing position will fix it (you will see the characters slowly refresh during this process)<br />
<br />
Even with Screen running you can lose connection if the wifi radio turns off when the screen does, see http://www.webos-internals.org/wiki/Patch_webOS_Keep_Phone_Awake_While_in_Remote_Session<br />
<br />
[[Image:Terminal-irssi.jpg]]</div>Punzadahttp://wiki.webos-internals.org/index.php?title=Linux_Tutorial_Irssi&diff=5828Linux Tutorial Irssi2009-09-17T20:31:59Z<p>Punzada: </p>
<hr />
<div>= Linux Tutorial - Irssi =<br />
<br />
=== Update 09/17/2009 === <br />
<br />
I have managed to get the bitlbee service working with irssi for full AIM, MSN, Yahoo and Jabber support. I shall be doing my best to update this wiki with the best methods to get this working and configured easily and securely as soon as possible.<br />
<br />
=== This Document Assumes the following ===<br />
<br />
You have followed the procedure to Access Linux on the device and have enabled the Optware repositories and software [[Portal:Accessing_Linux]]<br />
<br />
You have installed the Terminal application [[Application:Terminal]]<br />
<br />
<br />
Once these procedures are done you should have access to:<br />
<br />
The Optware software repositories through ipkg-opt <br />
<br />
The Terminal Application through the WebOS (should load, be the root user, and function)<br />
<br />
<br />
<br />
== Installation ==<br />
<br />
Within the Terminal application use the following command:<br />
<br />
<pre><nowiki><br />
ipkg-opt install screen irssi<br />
</nowiki></pre><br />
<br />
This command will automatically download [http://www.gnu.org/software/screen/ GNU Screen] and [http://irssi.org/ irssi] as well as any necessary dependencies.<br />
<br />
Note: GNU Screen is *not* necessary for irssi to function, it only provides further functionality to be able to close the Terminal application if desired, keep irssi running in the background and reattach to it. Also, I have found that running irssi within a screen session gives irssi all its various colors while running natively within the terminal app leaves it mono-colored. <br />
<br />
<br />
== Usage ==<br />
<br />
In order to run irssi you simply need to type irssi into the Terminal application at the shell prompt and once hitting enter(return) it will load. <br />
<br />
However this is '''NOT RECOMMENDED''' as by default the Terminal Application is loaded as the root user and you should avoid using internet facing applications as the root user if it is not necessary (some IRC networks such as EFnet will go as far as to instantly disconnect you if it detects you are connecting to their servers as root). <br />
<br />
Once the Terminal Application is opened you may change to the user you set up when completing the steps to Access Linux via the su command<br />
<br />
example:<br />
<br />
<pre><nowiki><br />
root@castle:/var/home/root# su myuser<br />
myuser@castle:/var/home/root$<br />
</nowiki></pre><br />
<br />
from here you can simply enter irssi and hit return and it shall load.<br />
<br />
===Basic Commands===<br />
<br />
/connect ircserver<br />
<br />
This will connect you to an irc network ex: /connect irc.freenode.net will connect you to the freenode network.<br />
<br />
/join #channel<br />
<br />
This will join the requested channel, ex: /join #webos-internals<br />
<br />
Sym+n Will move to the 'next' window within the irssi interface<br />
Sym+p Will move you to the 'previous' window within the irssi interface<br />
<br />
You can directly jump to a window (numbered in irssi) by hitting Orange Key+Space+Number.<br />
<br />
===GNU Screen History & Basics===<br />
<br />
If you're like me and you want to always keep your irssi session active as well as have the colors available to you a good solution is to use GNU Screen.<br />
<br />
For those that don't know, screen acts as a window manager for terminal applications. Screen allows you to run multiple applications in a single terminal session, switch between the applications freely as well as being able to detach from it entirely, and reattach to it later while having those applications run in the background. Many consider screen to be one of the most important tools available for any type of command line work or administration - is is very powerful and very flexible, feel free to read up on it's customization and abilities to further enhance your experience with it.<br />
<br />
====Screen Usage====<br />
<br />
To start using screen it is very simple, follow the instructions above but before switching to your local user to run irssi, first type screen and hit enter<br />
<br />
You will be greeted with screen's opening text, letting you know that it is running, and the GPL license, simply press the space bar here and you will be taken back into the prompt and it will appear as if you're back to where you started.<br />
<br />
From this point on, follow the instructions above to change into your user that is not root, and open irssi like normal.<br />
<br />
You will see commands listed as such: Sym-A C <br />
<br />
This key combination is important because it means 'Press and hold Sym, then hit A, release both and hit C'<br />
<br />
This is how GNU Screen functions and is vital to it's usage, the example above creates a new window with a fresh terminal session.<br />
<br />
==== Attach / Detach ====<br />
<br />
In order to detach from your screen session use the command Sym-A D<br />
<br />
Once a session is detached you may close out of the terminal app and any applications running within your screen session will continue to run.<br />
<br />
In order to reattach to a session you left running, load the Terminal Application again and type the following at the command prompt and hit enter: screen -r<br />
<br />
<br />
==== Screen Commands To Know ====<br />
Sym-A C - Create a new window/terminal session<br />
<br />
Sym-A N - Change to next window/terminal session within the current screen session<br />
<br />
Sym-A P - Change to previous window/terminal session with the current screen session<br />
<br />
Sym-A D - Detach from current screen session<br />
<br />
== Configuration/Tweaks ==<br />
<br />
Both irssi and GNU Screen are very rich applications with a plethora of scripts, customization and usage options that only a very small percentage of are covered in this document. If interested please search and find how you may be able to adjust them to fit your specific needs (and if you find anything worthwhile feel free to add it to this wiki!)<br />
<br />
For information on irssi please visit their startup documentation http://irssi.org/documentation/startup <br />
<br />
This site provides information that will help you in automating irssi to do tasks like autojoin set servers and channels and automatically identify your nickname with services. <br />
<br />
== Known Issues ==<br />
<br />
When first loaded irssi tends to not properly format to the whole screen and a simple rotation to let the terminal rotate to the side and back to standard typing position will fix it (you will see the characters slowly refresh during this process)<br />
<br />
Even with Screen running you can lose connection if the wifi radio turns off when the screen does, see http://www.webos-internals.org/wiki/Patch_webOS_Keep_Phone_Awake_While_in_Remote_Session<br />
<br />
[[Image:Terminal-irssi.jpg]]</div>Punzadahttp://wiki.webos-internals.org/index.php?title=Linux_Tutorial_Irssi&diff=5809Linux Tutorial Irssi2009-09-17T03:26:35Z<p>Punzada: </p>
<hr />
<div>= Linux Tutorial - Irssi =<br />
<br />
<br />
<br />
=== This Document Assumes the following ===<br />
<br />
You have followed the procedure to Access Linux on the device and have enabled the Optware repositories and software [[Portal:Accessing_Linux]]<br />
<br />
You have installed the Terminal application [[Application:Terminal]]<br />
<br />
<br />
Once these procedures are done you should have access to:<br />
<br />
The Optware software repositories through ipkg-opt <br />
<br />
The Terminal Application through the WebOS (should load, be the root user, and function)<br />
<br />
<br />
<br />
== Installation ==<br />
<br />
Within the Terminal application use the following command:<br />
<br />
<pre><nowiki><br />
ipkg-opt install screen irssi<br />
</nowiki></pre><br />
<br />
This command will automatically download [http://www.gnu.org/software/screen/ GNU Screen] and [http://irssi.org/ irssi] as well as any necessary dependencies.<br />
<br />
Note: GNU Screen is *not* necessary for irssi to function, it only provides further functionality to be able to close the Terminal application if desired, keep irssi running in the background and reattach to it. Also, I have found that running irssi within a screen session gives irssi all its various colors while running natively within the terminal app leaves it mono-colored. <br />
<br />
<br />
== Usage ==<br />
<br />
In order to run irssi you simply need to type irssi into the Terminal application at the shell prompt and once hitting enter(return) it will load. <br />
<br />
However this is '''NOT RECOMMENDED''' as by default the Terminal Application is loaded as the root user and you should avoid using internet facing applications as the root user if it is not necessary (some IRC networks such as EFnet will go as far as to instantly disconnect you if it detects you are connecting to their servers as root). <br />
<br />
Once the Terminal Application is opened you may change to the user you set up when completing the steps to Access Linux via the su command<br />
<br />
example:<br />
<br />
<pre><nowiki><br />
root@castle:/var/home/root# su myuser<br />
myuser@castle:/var/home/root$<br />
</nowiki></pre><br />
<br />
from here you can simply enter irssi and hit return and it shall load.<br />
<br />
===Basic Commands===<br />
<br />
/connect ircserver<br />
<br />
This will connect you to an irc network ex: /connect irc.freenode.net will connect you to the freenode network.<br />
<br />
/join #channel<br />
<br />
This will join the requested channel, ex: /join #webos-internals<br />
<br />
Sym+n Will move to the 'next' window within the irssi interface<br />
Sym+p Will move you to the 'previous' window within the irssi interface<br />
<br />
You can directly jump to a window (numbered in irssi) by hitting Orange Key+Space+Number.<br />
<br />
===GNU Screen History & Basics===<br />
<br />
If you're like me and you want to always keep your irssi session active as well as have the colors available to you a good solution is to use GNU Screen.<br />
<br />
For those that don't know, screen acts as a window manager for terminal applications. Screen allows you to run multiple applications in a single terminal session, switch between the applications freely as well as being able to detach from it entirely, and reattach to it later while having those applications run in the background. Many consider screen to be one of the most important tools available for any type of command line work or administration - is is very powerful and very flexible, feel free to read up on it's customization and abilities to further enhance your experience with it.<br />
<br />
====Screen Usage====<br />
<br />
To start using screen it is very simple, follow the instructions above but before switching to your local user to run irssi, first type screen and hit enter<br />
<br />
You will be greeted with screen's opening text, letting you know that it is running, and the GPL license, simply press the space bar here and you will be taken back into the prompt and it will appear as if you're back to where you started.<br />
<br />
From this point on, follow the instructions above to change into your user that is not root, and open irssi like normal.<br />
<br />
You will see commands listed as such: Sym-A C <br />
<br />
This key combination is important because it means 'Press and hold Sym, then hit A, release both and hit C'<br />
<br />
This is how GNU Screen functions and is vital to it's usage, the example above creates a new window with a fresh terminal session.<br />
<br />
==== Attach / Detach ====<br />
<br />
In order to detach from your screen session use the command Sym-A D<br />
<br />
Once a session is detached you may close out of the terminal app and any applications running within your screen session will continue to run.<br />
<br />
In order to reattach to a session you left running, load the Terminal Application again and type the following at the command prompt and hit enter: screen -r<br />
<br />
<br />
==== Screen Commands To Know ====<br />
Sym-A C - Create a new window/terminal session<br />
<br />
Sym-A N - Change to next window/terminal session within the current screen session<br />
<br />
Sym-A P - Change to previous window/terminal session with the current screen session<br />
<br />
Sym-A D - Detach from current screen session<br />
<br />
== Configuration/Tweaks ==<br />
<br />
Both irssi and GNU Screen are very rich applications with a plethora of scripts, customization and usage options that only a very small percentage of are covered in this document. If interested please search and find how you may be able to adjust them to fit your specific needs (and if you find anything worthwhile feel free to add it to this wiki!)<br />
<br />
For information on irssi please visit their startup documentation http://irssi.org/documentation/startup <br />
<br />
This site provides information that will help you in automating irssi to do tasks like autojoin set servers and channels and automatically identify your nickname with services. <br />
<br />
== Known Issues ==<br />
<br />
When first loaded irssi tends to not properly format to the whole screen and a simple rotation to let the terminal rotate to the side and back to standard typing position will fix it (you will see the characters slowly refresh during this process)<br />
<br />
Even with Screen running you can lose connection if the wifi radio turns off when the screen does, see http://www.webos-internals.org/wiki/Patch_webOS_Keep_Phone_Awake_While_in_Remote_Session<br />
<br />
[[Image:Terminal-irssi.jpg]]</div>Punzadahttp://wiki.webos-internals.org/index.php?title=Linux_Tutorial_Irssi&diff=5806Linux Tutorial Irssi2009-09-17T03:20:09Z<p>Punzada: </p>
<hr />
<div>= Linux Tutorial - Irssi =<br />
<br />
<br />
<br />
=== This Document Assumes the following ===<br />
<br />
You have followed the procedure to Access Linux on the device and have enabled the Optware repositories and software [[Portal:Accessing_Linux]]<br />
<br />
You have installed the Terminal application [[Application:Terminal]]<br />
<br />
<br />
Once these procedures are done you should have access to:<br />
<br />
The Optware software repositories through ipkg-opt <br />
<br />
The Terminal Application through the WebOS (should load, be the root user, and function)<br />
<br />
<br />
<br />
== Installation ==<br />
<br />
Within the Terminal application use the following command:<br />
<br />
<pre><nowiki><br />
ipkg-opt install screen irssi<br />
</nowiki></pre><br />
<br />
This command will automatically download [http://www.gnu.org/software/screen/ GNU Screen] and [http://irssi.org/ irssi] as well as any necessary dependencies.<br />
<br />
Note: GNU Screen is *not* necessary for irssi to function, it only provides further functionality to be able to close the Terminal application if desired, keep irssi running in the background and reattach to it. Also, I have found that running irssi within a screen session gives irssi all its various colors while running natively within the terminal app leaves it mono-colored. <br />
<br />
<br />
== Usage ==<br />
<br />
In order to run irssi you simply need to type irssi into the Terminal application at the shell prompt and once hitting enter(return) it will load. <br />
<br />
However this is '''NOT RECOMMENDED''' as by default the Terminal Application is loaded as the root user and you should avoid using internet facing applications as the root user if it is not necessary (some IRC networks such as EFnet will go as far as to instantly disconnect you if it detects you are connecting to their servers as root). <br />
<br />
Once the Terminal Application is opened you may change to the user you set up when completing the steps to Access Linux via the su command<br />
<br />
example:<br />
<br />
<pre><nowiki><br />
root@castle:/var/home/root# su myuser<br />
myuser@castle:/var/home/root$<br />
</nowiki></pre><br />
<br />
from here you can simply enter irssi and hit return and it shall load.<br />
<br />
===Basic Commands===<br />
<br />
/connect ircserver<br />
<br />
This will connect you to an irc network ex: /connect irc.freenode.net will connect you to the freenode network.<br />
<br />
/join #channel<br />
<br />
This will join the requested channel, ex: /join #webos-internals<br />
<br />
Sym+n Will move to the 'next' window within the irssi interface<br />
Sym+p Will move you to the 'previous' window within the irssi interface<br />
<br />
You can directly jump to a window (numbered in irssi) by hitting Orange Key+Space+Number.<br />
<br />
===GNU Screen History & Basics===<br />
<br />
If you're like me and you want to always keep your irssi session active as well as have the colors available to you a good solution is to use GNU Screen.<br />
<br />
For those that don't know, screen acts as a window manager for terminal applications. Screen allows you to run multiple applications in a single terminal session, switch between the applications freely as well as being able to detach from it entirely, and reattach to it later while having those applications run in the background. Many consider screen to be one of the most important tools available for any type of command line work or administration - is is very powerful and very flexable, feel free to read up on it's customization and abilities to further enhance your experience with it.<br />
<br />
====Screen Usage====<br />
<br />
To start using screen it is very simple, follow the instructions above but before switching to your local user to run irssi, first type screen and hit enter<br />
<br />
You will be greeted with screen's opening text, letting you know that it is running, and the GPL license, simply press the space bar here and you will be taken back into the prompt and it will appear as if you're back to where you started.<br />
<br />
From this point on, follow the instructions above to change into your user that is not root, and open irssi like normal.<br />
<br />
You will see commands listed as such: Sym-A C <br />
<br />
This key combination is important because it means 'Press and hold Sym, then hit A, release both and hit C'<br />
<br />
This is how GNU Screen functions and is vital to it's usage, the example above creates a new window with a fresh terminal session.<br />
<br />
==== Attach / Detach ====<br />
<br />
In order to detach from your screen session use the command Sym-A D<br />
<br />
Once a session is detached you may close out of the terminal app and any applications running within your screen session will continue to run.<br />
<br />
In order to reattach to a session you left running, load the Terminal Application again and type the following at the command prompt and hit enter: screen -r<br />
<br />
<br />
==== Screen Commands To Know ====<br />
Sym-A C - Create a new window/terminal session<br />
<br />
Sym-A N - Change to next window/terminal session within the current screen session<br />
<br />
Sym-A P - Change to previous window/terminal session with the current screen session<br />
<br />
Sym-A D - Detach from current screen session<br />
<br />
== Configuration/Tweaks ==<br />
<br />
Both irssi and GNU Screen are very rich applications with a plethora of scripts, customization and usage options that only a very small percentage of are covered in this document. If interested please search and find how you may be able to adjust them to fit your specific needs (and if you find anything worthwhile feel free to add it to this wiki!)<br />
<br />
For information on irssi please visit their startup documentation http://irssi.org/documentation/startup <br />
<br />
This site provides information that will help you in automating irssi to do tasks like autojoin set servers and channels and automatically identify your nickname with services. <br />
<br />
== Known Issues ==<br />
<br />
When first loaded irssi tends to not properly format to the whole screen and a simple rotation to let the terminal rotate to the side and back to standard typing position will fix it (you will see the characters slowly refresh during this process)<br />
<br />
Even with Screen running you can lose connection if the wifi radio turns off when the screen does, see http://www.webos-internals.org/wiki/Patch_webOS_Keep_Phone_Awake_While_in_Remote_Session<br />
<br />
[[Image:Terminal-irssi.jpg]]</div>Punzadahttp://wiki.webos-internals.org/index.php?title=Linux_Tutorial_Irssi&diff=5805Linux Tutorial Irssi2009-09-17T03:17:56Z<p>Punzada: </p>
<hr />
<div>= Linux Tutorial - Irssi =<br />
<br />
<br />
<br />
=== This Document Assumes the following ===<br />
<br />
You have followed the procedure to Access Linux on the device and have enabled the Optware repositories and software [[Portal:Accessing_Linux]]<br />
<br />
You have installed the Terminal application [[Application:Terminal]]<br />
<br />
<br />
Once these procedures are done you should have access to:<br />
<br />
The Optware software repositories through ipkg-opt <br />
<br />
The Terminal Application through the WebOS (should load, be the root user, and function)<br />
<br />
<br />
<br />
== Installation ==<br />
<br />
Within the Terminal application use the following command:<br />
<br />
<pre><nowiki><br />
ipkg-opt install screen irssi<br />
</nowiki></pre><br />
<br />
This command will automatically download [http://www.gnu.org/software/screen/ GNU Screen] and [http://irssi.org/ irssi] as well as any necessary dependencies.<br />
<br />
Note: GNU Screen is *not* necessary for irssi to function, it only provides further functionality to be able to close the Terminal application if desired, keep irssi running in the background and reattach to it. Also, I have found that running irssi within a screen session gives irssi shows all its various colors while running natively within the terminal app leaves it mono-colored. <br />
<br />
<br />
== Usage ==<br />
<br />
In order to run irssi you simply need to type irssi into the Terminal application at the shell prompt and once hitting enter(return) it will load. <br />
<br />
However this is '''NOT RECOMMENDED''' as by default the Terminal Application is loaded as the root user and you should avoid using internet facing applications as the root user if it is not necessary (some IRC networks such as EFnet will go as far as to instantly disconnect you if it detects you are connecting to their servers as root). <br />
<br />
Once the Terminal Application is opened you may change to the user you set up when completing the steps to Access Linux via the su command<br />
<br />
example:<br />
<br />
<pre><nowiki><br />
root@castle:/var/home/root# su myuser<br />
myuser@castle:/var/home/root$<br />
</nowiki></pre><br />
<br />
from here you can simply enter irssi and hit return and it shall load.<br />
<br />
===Basic Commands===<br />
<br />
/connect ircserver<br />
<br />
This will connect you to an irc network ex: /connect irc.freenode.net will connect you to the freenode network.<br />
<br />
/join #channel<br />
<br />
This will join the requested channel, ex: /join #webos-internals<br />
<br />
Sym+n Will move to the 'next' window within the irssi interface<br />
Sym+p Will move you to the 'previous' window within the irssi interface<br />
<br />
You can directly jump to a window (numbered in irssi) by hitting Orange Key+Space+Number.<br />
<br />
===GNU Screen History & Basics===<br />
<br />
If you're like me and you want to always keep your irssi session active as well as have the colors available to you a good solution is to use GNU Screen.<br />
<br />
For those that don't know, screen acts as a window manager for terminal applications. Screen allows you to run multiple applications in a single terminal session, switch between the applications freely as well as being able to detach from it entirely, and reattach to it later while having those applications run in the background. Many consider screen to be one of the most important tools available for any type of command line work or administration - is is very powerful and very flexable, feel free to read up on it's customization and abilities to further enhance your experience with it.<br />
<br />
====Screen Usage====<br />
<br />
To start using screen it is very simple, follow the instructions above but before switching to your local user to run irssi, first type screen and hit enter<br />
<br />
You will be greeted with screen's opening text, letting you know that it is running, and the GPL license, simply press the space bar here and you will be taken back into the prompt and it will appear as if you're back to where you started.<br />
<br />
From this point on, follow the instructions above to change into your user that is not root, and open irssi like normal.<br />
<br />
You will see commands listed as such: Sym-A C <br />
<br />
This key combination is important because it means 'Press and hold Sym, then hit A, release both and hit C'<br />
<br />
This is how GNU Screen functions and is vital to it's usage, the example above creates a new window with a fresh terminal session.<br />
<br />
==== Attach / Detach ====<br />
<br />
In order to detach from your screen session use the command Sym-A D<br />
<br />
Once a session is detached you may close out of the terminal app and any applications running within your screen session will continue to run.<br />
<br />
In order to reattach to a session you left running, load the Terminal Application again and type the following at the command prompt and hit enter: screen -r<br />
<br />
<br />
==== Screen Commands To Know ====<br />
Sym-A C - Create a new window/terminal session<br />
<br />
Sym-A N - Change to next window/terminal session within the current screen session<br />
<br />
Sym-A P - Change to previous window/terminal session with the current screen session<br />
<br />
Sym-A D - Detach from current screen session<br />
<br />
== Configuration/Tweaks ==<br />
<br />
Both irssi and GNU Screen are very rich applications with a plethora of scripts, customization and usage options that only a very small percentage of are covered in this document. If interested please search and find how you may be able to adjust them to fit your specific needs (and if you find anything worthwhile feel free to add it to this wiki!)<br />
<br />
For information on irssi please visit their startup documentation http://irssi.org/documentation/startup <br />
<br />
this site provides information that will help you in automating irssi to do tasks like autojoin set servers and channels and automatically identify your nickname with services. <br />
<br />
== Known Issues ==<br />
<br />
When first loaded irssi tends to not properly format to the whole screen and a simple rotation to let the terminal rotate to the side and back to standard typing position will fix it (you will see the characters slowly refresh during this process)<br />
<br />
Even with Screen running you can lose connection if the wifi radio turns off when the screen does, see http://www.webos-internals.org/wiki/Patch_webOS_Keep_Phone_Awake_While_in_Remote_Session<br />
<br />
[[Image:Terminal-irssi.jpg]]</div>Punzadahttp://wiki.webos-internals.org/index.php?title=Linux_Tutorial_Irssi&diff=5797Linux Tutorial Irssi2009-09-16T21:19:56Z<p>Punzada: </p>
<hr />
<div>= Linux Tutorial - Irssi =<br />
<br />
<br />
<br />
=== This Documents Assumes the following ===<br />
<br />
You have followed the procedure to Access Linux on the device and have enabled the Optware repositories and software [[Portal:Accessing_Linux]]<br />
<br />
You have installed the Terminal application [[Application:Terminal]]<br />
<br />
<br />
Once these procedures are done you should have access to:<br />
<br />
The Optware software repositories through ipkg-opt <br />
<br />
The Terminal Application through the WebOS (should load, be the root user, and function)<br />
<br />
<br />
<br />
== Installation ==<br />
<br />
Within the Terminal application use the following command:<br />
<br />
<pre><nowiki><br />
ipkg-opt install screen irssi<br />
</nowiki></pre><br />
<br />
This command will automatically download [http://www.gnu.org/software/screen/ GNU Screen] and [http://irssi.org/ irssi] as well as any necessary dependencies.<br />
<br />
Note: GNU Screen is *not* necessary for irssi to function, it only provides further functionality to be able to close the Terminal application if desired, keep irssi running in the background and reattach to it. Also, I have found that running irssi within a screen session gives irssi shows all its various colors while running natively within the terminal app leaves it mono-colored. <br />
<br />
<br />
== Usage ==<br />
<br />
In order to run irssi you simply need to type irssi into the Terminal application at the shell prompt and once hitting enter(return) it will load. <br />
<br />
However this is '''NOT RECOMMENDED''' as by default the Terminal Application is loaded as the root user and you should avoid using internet facing applications as the root user if it is not necessary (some IRC networks such as EFnet will go as far as to instantly disconnect you if it detects you are connecting to their servers as root). <br />
<br />
Once the Terminal Application is opened you may change to the user you set up when completing the steps to Access Linux via the su command<br />
<br />
example:<br />
<br />
<pre><nowiki><br />
root@castle:/var/home/root# su myuser<br />
myuser@castle:/var/home/root$<br />
</nowiki></pre><br />
<br />
from here you can simply enter irssi and hit return and it shall load.<br />
<br />
===Basic Commands===<br />
<br />
/connect ircserver<br />
<br />
This will connect you to an irc network ex: /connect irc.freenode.net will connect you to the freenode network.<br />
<br />
/join #channel<br />
<br />
This will join the requested channel, ex: /join #webos-internals<br />
<br />
Sym+n Will move to the 'next' window within the irssi interface<br />
Sym+p Will move you to the 'previous' window within the irssi interface<br />
<br />
You can directly jump to a window (numbered in irssi) by hitting Orange Key+Space+Number.<br />
<br />
===GNU Screen History & Basics===<br />
<br />
If you're like me and you want to always keep your irssi session active as well as have the colors available to you a good solution is to use GNU Screen.<br />
<br />
For those that don't know, screen acts as a window manager for terminal applications. Screen allows you to run multiple applications in a single terminal session, switch between the applications freely as well as being able to detach from it entirely, and reattach to it later while having those applications run in the background. Many consider screen to be one of the most important tools available for any type of command line work or administration - is is very powerful and very flexable, feel free to read up on it's customization and abilities to further enhance your experience with it.<br />
<br />
====Screen Usage====<br />
<br />
To start using screen it is very simple, follow the instructions above but before switching to your local user to run irssi, first type screen and hit enter<br />
<br />
You will be greeted with screen's opening text, letting you know that it is running, and the GPL license, simply press the space bar here and you will be taken back into the prompt and it will appear as if you're back to where you started.<br />
<br />
From this point on, follow the instructions above to change into your user that is not root, and open irssi like normal.<br />
<br />
You will see commands listed as such: Sym-A C <br />
<br />
This key combination is important because it means 'Press and hold Sym, then hit A, release both and hit C'<br />
<br />
This is how GNU Screen functions and is vital to it's usage, the example above creates a new window with a fresh terminal session.<br />
<br />
==== Attach / Detach ====<br />
<br />
In order to detach from your screen session use the command Sym-A D<br />
<br />
Once a session is detached you may close out of the terminal app and any applications running within your screen session will continue to run.<br />
<br />
In order to reattach to a session you left running, load the Terminal Application again and type the following at the command prompt and hit enter: screen -r<br />
<br />
<br />
==== Screen Commands To Know ====<br />
Sym-A C - Create a new window/terminal session<br />
<br />
Sym-A N - Change to next window/terminal session within the current screen session<br />
<br />
Sym-A P - Change to previous window/terminal session with the current screen session<br />
<br />
Sym-A D - Detach from current screen session<br />
<br />
== Configuration/Tweaks ==<br />
<br />
Both irssi and GNU Screen are very rich applications with a plethora of scripts, customization and usage options that only a very small percentage of are covered in this document. If interested please search and find how you may be able to adjust them to fit your specific needs (and if you find anything worthwhile feel free to add it to this wiki!)<br />
<br />
For information on irssi please visit their startup documentation http://irssi.org/documentation/startup <br />
<br />
this site provides information that will help you in automating irssi to do tasks like autojoin set servers and channels and automatically identify your nickname with services. <br />
<br />
== Known Issues ==<br />
<br />
When first loaded irssi tends to not properly format to the whole screen and a simple rotation to let the terminal rotate to the side and back to standard typing position will fix it (you will see the characters slowly refresh during this process)<br />
<br />
Even with Screen running you can lose connection if the wifi radio turns off when the screen does, see http://www.webos-internals.org/wiki/Patch_webOS_Keep_Phone_Awake_While_in_Remote_Session<br />
<br />
[[Image:Terminal-irssi.jpg]]</div>Punzadahttp://wiki.webos-internals.org/index.php?title=Portal:Linux_Applications&diff=5796Portal:Linux Applications2009-09-16T21:04:10Z<p>Punzada: </p>
<hr />
<div>__notoc__<br />
{{reorganize|This page needs to be reorganized still.}}<br />
{{portal-header<br />
|The Pre runs a very standard Linux on a commonly available processor. Very soon after access was achieved to the Linux, the Optware team made the entire catalog of Optware packages available on the pre. <br />
<br />
More about the Optware project here: [http://www.nslu2-linux.org/wiki/Optware/Packages Optware Packages].<br />
<br />
You can view a list of available packages here: [http://ipkg.nslu2-linux.org/feeds/optware/cs08q1armel/cross/unstable/ List of Packages].<br />
<br />
The community has been busy porting other applications to the Pre. Some of those are listed, and have pages for them below.<br />
}}<br />
{{portal-three-columns<br />
|column1=<br />
* [[Portal:Linux_Applications_All|All]]<br />
* [[Portal:Linux_Applications_Business|Business]]<br />
* [[Portal:Linux_Applications_Communications|Communications]]<br />
* [[Portal:Linux_Applications_Entertainment|Entertainment]]<br />
<br />
|column2=<br />
* [[Portal:Linux_Applications_Food|Food]]<br />
* [[Portal:Linux_Applications_Games|Games]]<br />
* [[Portal:Linux_Applications_Lifestyle|Lifestyle]]<br />
* [[Portal:Linux_Applications_News|News]]<br />
<br />
|column3=<br />
* [[Portal:Linux_Applications_Social Networking|Social Networking]]<br />
* [[Portal:Linux_Applications_Tutorial|Tutorial]]<br />
* [[Portal:Linux_Applications_Utilities|Utilities]]<br />
* [[Portal:Linux_Applications_Productivity|Productivity]]<br />
}}<br />
{{portal-two-columns<br />
|column1=<br />
== Application Tutorials ==<br />
<br />
'''[[Portal:Accessing Linux|Follow the Accessing Linux Article First]]'''<br />
* [[Ad-Hoc_Networking|Ad-Hoc Networking]]<br />
* [[Ajaxterm]]<br />
* [[Apache]]<br />
* [[Colorful_Bash_Prompt|Colorful Bash Prompt]]<br />
* [[Diff]]<br />
* [[Tutorials_Linux_DDNS_for_EVDO|Dynamic DNS for EVDO]]<br />
* [[DFBTerm DirectFB Terminal Emulator|DFBTerm DirectFB Terminal Emulator]] <br />
* [[Graphical Shell with WebShell|Graphical Shell with WebShell]] <br />
* [[GUI Text Editors|GUI Text Editors]] <br />
* [[HamachiVPN|HamachiVPN]] <br />
* [[How To Use "ls" In Color|How To Use "ls" In Color]] <br />
* [[Linux Tutorial Irssi|Linux Tutorial Irssi]]<br />
* [[Lighttpd|Lighttpd ]] <br />
* [[OpenVPN for Palm Pre|OpenVPN for Palm Pre]] <br />
* [[Tutorials_Linux_opt_on_loopback|/opt on loopback image on /media/internal]]<br />
* [[PalmVNC Terminal|PalmVNC Terminal]] <br />
* [[QEMU|QEMU]] <br />
* [[QEMU webOS Emulation|QEMU webOS Emulation]] <br />
* [[Running webOS in QEMU|Running webOS in QEMU]] <br />
* [[Replace "vi" with Fullscreen Text Editor "joe" or "nano"|Replace "vi" with Fullscreen Text Editor "joe" or "nano"]] <br />
* [[rTorrent]] <br />
* [[Setup Bash|Setup Bash]] <br />
* [[Samba Access|Samba Access]] <br />
* [[VNC (Virtual Network Computing)|VNC (Virtual Network Computing)]] <br />
* [[Vala Terminal|Vala Terminal]] <br />
* [[Wireless Music Sync with Amarok 1.4|Wireless Music Sync with Amarok 1.4]]<br />
<br />
== Want to write a tutorial and Add it? ==<br />
<br />
Just name the tutorial with<br />
<br />
"Tutorials Linux " + name<br />
<br />
Ex: Tutorials_Linux_Getting_Started<br /><br />
(spaces are the same thing as underscores)<br />
<br />
|column2=<br />
== Policies about adding Applications ==<br />
<br />
Your application can be any progress (Completed/Beta/Design Phase), just make sure you have a temporary name. For example if your application is called "Testing This":<br />
<br />
<source lang="text"><br />
{{portal-application-item<br />
|name=Asteroids<br />
|article=Asteroids<br />
|user=AWESOM-O<br />
|site=http://domain.com/asteroids/<br />
|description=This is a short description, leave screenshots<br />
and other details for the application page.<br />
<br />
}}<br />
</source><br />
<br />
<br />
Place this under the [[Portal:Linux Applications All|All Linux Application Portal]], and the category it goes under (for instance "Games" if it is a game). You can always change the applications name just make sure it is not taken and let us know on the [[Admin_Changes|Admin Changes]] page so we can delete the old application page (so others can use it).<br />
<br />
}}</div>Punzadahttp://wiki.webos-internals.org/index.php?title=Linux_Tutorial_Irssi&diff=5795Linux Tutorial Irssi2009-09-16T21:02:35Z<p>Punzada: </p>
<hr />
<div>= Linux Tutorial - Irssi =<br />
<br />
<br />
<br />
=== This Documents Assumes the following ===<br />
<br />
You have followed the procedure to Access Linux on the device and have enabled the Optware repositories and software http://www.webos-internals.org/wiki/Portal:Accessing_Linux<br />
<br />
You have installed the Terminal application http://www.webos-internals.org/wiki/Application:Terminal<br />
<br />
<br />
Once these procedures are done you should have access to:<br />
<br />
The Optware software repositories through ipkg-opt <br />
<br />
The Terminal Application through the WebOS (should load, be the root user, and function)<br />
<br />
<br />
<br />
== Installation ==<br />
<br />
Within the Terminal application use the following command:<br />
<br />
<pre><nowiki><br />
ipkg-opt install screen irssi<br />
</nowiki></pre><br />
<br />
This command will automatically download [http://www.gnu.org/software/screen/ GNU Screen] and [http://irssi.org/ irssi] as well as any necessary dependencies.<br />
<br />
Note: GNU Screen is *not* necessary for irssi to function, it only provides further functionality to be able to close the Terminal application if desired, keep irssi running in the background and reattach to it. Also, I have found that running irssi within a screen session gives irssi shows all its various colors while running natively within the terminal app leaves it mono-colored. <br />
<br />
<br />
== Usage ==<br />
<br />
In order to run irssi you simply need to type irssi into the Terminal application at the shell prompt and once hitting enter(return) it will load. <br />
<br />
However this is '''NOT RECOMMENDED''' as by default the Terminal Application is loaded as the root user and you should avoid using internet facing applications as the root user if it is not necessary (some IRC networks such as EFnet will go as far as to instantly disconnect you if it detects you are connecting to their servers as root). <br />
<br />
Once the Terminal Application is opened you may change to the user you set up when completing the steps to Access Linux via the su command<br />
<br />
example:<br />
<br />
<pre><nowiki><br />
root@castle:/var/home/root# su myuser<br />
myuser@castle:/var/home/root$<br />
</nowiki></pre><br />
<br />
from here you can simply enter irssi and hit return and it shall load.<br />
<br />
===Basic Commands===<br />
<br />
/connect ircserver<br />
<br />
This will connect you to an irc network ex: /connect irc.freenode.net will connect you to the freenode network.<br />
<br />
/join #channel<br />
<br />
This will join the requested channel, ex: /join #webos-internals<br />
<br />
Sym+n Will move to the 'next' window within the irssi interface<br />
Sym+p Will move you to the 'previous' window within the irssi interface<br />
<br />
You can directly jump to a window (numbered in irssi) by hitting Orange Key+Space+Number.<br />
<br />
===GNU Screen History & Basics===<br />
<br />
If you're like me and you want to always keep your irssi session active as well as have the colors available to you a good solution is to use GNU Screen.<br />
<br />
For those that don't know, screen acts as a window manager for terminal applications. Screen allows you to run multiple applications in a single terminal session, switch between the applications freely as well as being able to detach from it entirely, and reattach to it later while having those applications run in the background. Many consider screen to be one of the most important tools available for any type of command line work or administration - is is very powerful and very flexable, feel free to read up on it's customization and abilities to further enhance your experience with it.<br />
<br />
====Screen Usage====<br />
<br />
To start using screen it is very simple, follow the instructions above but before switching to your local user to run irssi, first type screen and hit enter<br />
<br />
You will be greeted with screen's opening text, letting you know that it is running, and the GPL license, simply press the space bar here and you will be taken back into the prompt and it will appear as if you're back to where you started.<br />
<br />
From this point on, follow the instructions above to change into your user that is not root, and open irssi like normal.<br />
<br />
You will see commands listed as such: Sym-A C <br />
<br />
This key combination is important because it means 'Press and hold Sym, then hit A, release both and hit C'<br />
<br />
This is how GNU Screen functions and is vital to it's usage, the example above creates a new window with a fresh terminal session.<br />
<br />
==== Attach / Detach ====<br />
<br />
In order to detach from your screen session use the command Sym-A D<br />
<br />
Once a session is detached you may close out of the terminal app and any applications running within your screen session will continue to run.<br />
<br />
In order to reattach to a session you left running, load the Terminal Application again and type the following at the command prompt and hit enter: screen -r<br />
<br />
<br />
==== Screen Commands To Know ====<br />
Sym-A C - Create a new window/terminal session<br />
<br />
Sym-A N - Change to next window/terminal session within the current screen session<br />
<br />
Sym-A P - Change to previous window/terminal session with the current screen session<br />
<br />
Sym-A D - Detach from current screen session<br />
<br />
== Configuration/Tweaks ==<br />
<br />
Both irssi and GNU Screen are very rich applications with a plethora of scripts, customization and usage options that only a very small percentage of are covered in this document. If interested please search and find how you may be able to adjust them to fit your specific needs (and if you find anything worthwhile feel free to add it to this wiki!)<br />
<br />
For information on irssi please visit their startup documentation http://irssi.org/documentation/startup <br />
<br />
this site provides information that will help you in automating irssi to do tasks like autojoin set servers and channels and automatically identify your nickname with services. <br />
<br />
== Known Issues ==<br />
<br />
When first loaded irssi tends to not properly format to the whole screen and a simple rotation to let the terminal rotate to the side and back to standard typing position will fix it (you will see the characters slowly refresh during this process)<br />
<br />
Even with Screen running you can lose connection if the wifi radio turns off when the screen does, see http://www.webos-internals.org/wiki/Patch_webOS_Keep_Phone_Awake_While_in_Remote_Session<br />
<br />
[[Image:Terminal-irssi.jpg]]</div>Punzadahttp://wiki.webos-internals.org/index.php?title=File:Terminal-irssi.jpg&diff=5794File:Terminal-irssi.jpg2009-09-16T21:00:04Z<p>Punzada: </p>
<hr />
<div></div>Punzadahttp://wiki.webos-internals.org/index.php?title=Linux_Tutorial_Irssi&diff=5793Linux Tutorial Irssi2009-09-16T20:59:42Z<p>Punzada: </p>
<hr />
<div>= Linux Tutorial - Irssi =<br />
<br />
<br />
<br />
=== This Documents Assumes the following ===<br />
<br />
You have followed the procedure to Access Linux on the device and have enabled the Optware repositories and software http://www.webos-internals.org/wiki/Portal:Accessing_Linux<br />
<br />
You have installed the Terminal application http://www.webos-internals.org/wiki/Application:Terminal<br />
<br />
<br />
Once these procedures are done you should have access to:<br />
<br />
The Optware software repositories through ipkg-opt <br />
<br />
The Terminal Application through the WebOS (should load, be the root user, and function)<br />
<br />
<br />
<br />
== Installation ==<br />
<br />
Within the Terminal application use the following command:<br />
<br />
<pre><nowiki><br />
ipkg-opt install screen irssi<br />
</nowiki></pre><br />
<br />
This command will automatically download [http://www.gnu.org/software/screen/ GNU Screen] and [http://irssi.org/ irssi] as well as any necessary dependencies.<br />
<br />
Note: GNU Screen is *not* necessary for irssi to function, it only provides further functionality to be able to close the Terminal application if desired, keep irssi running in the background and reattach to it. Also, I have found that running irssi within a screen session gives irssi shows all its various colors while running natively within the terminal app leaves it mono-colored. <br />
<br />
<br />
== Usage ==<br />
<br />
In order to run irssi you simply need to type irssi into the Terminal application at the shell prompt and once hitting enter(return) it will load. <br />
<br />
However this is '''NOT RECOMMENDED''' as by default the Terminal Application is loaded as the root user and you should avoid using internet facing applications as the root user if it is not necessary (some IRC networks such as EFnet will go as far as to instantly disconnect you if it detects you are connecting to their servers as root). <br />
<br />
Once the Terminal Application is opened you may change to the user you set up when completing the steps to Access Linux via the su command<br />
<br />
example:<br />
<br />
<pre><nowiki><br />
root@castle:/var/home/root# su myuser<br />
myuser@castle:/var/home/root$<br />
</nowiki></pre><br />
<br />
from here you can simply enter irssi and hit return and it shall load.<br />
<br />
===Basic Commands===<br />
<br />
/connect ircserver<br />
<br />
This will connect you to an irc network ex: /connect irc.freenode.net will connect you to the freenode network.<br />
<br />
/join #channel<br />
<br />
This will join the requested channel, ex: /join #webos-internals<br />
<br />
Sym+n Will move to the 'next' window within the irssi interface<br />
Sym+p Will move you to the 'previous' window within the irssi interface<br />
<br />
You can directly jump to a window (numbered in irssi) by hitting Orange Key+Space+Number.<br />
<br />
===GNU Screen History & Basics===<br />
<br />
If you're like me and you want to always keep your irssi session active as well as have the colors available to you a good solution is to use GNU Screen.<br />
<br />
For those that don't know, screen acts as a window manager for terminal applications. Screen allows you to run multiple applications in a single terminal session, switch between the applications freely as well as being able to detach from it entirely, and reattach to it later while having those applications run in the background. Many consider screen to be one of the most important tools available for any type of command line work or administration - is is very powerful and very flexable, feel free to read up on it's customization and abilities to further enhance your experience with it.<br />
<br />
====Screen Usage====<br />
<br />
To start using screen it is very simple, follow the instructions above but before switching to your local user to run irssi, first type screen and hit enter<br />
<br />
You will be greeted with screen's opening text, letting you know that it is running, and the GPL license, simply press the space bar here and you will be taken back into the prompt and it will appear as if you're back to where you started.<br />
<br />
From this point on, follow the instructions above to change into your user that is not root, and open irssi like normal.<br />
<br />
You will see commands listed as such: Sym-A C <br />
<br />
This key combination is important because it means 'Press and hold Sym, then hit A, release both and hit C'<br />
<br />
This is how GNU Screen functions and is vital to it's usage, the example above creates a new window with a fresh terminal session.<br />
<br />
==== Attach / Detach ====<br />
<br />
In order to detach from your screen session use the command Sym-A D<br />
<br />
Once a session is detached you may close out of the terminal app and any applications running within your screen session will continue to run.<br />
<br />
In order to reattach to a session you left running, load the Terminal Application again and type the following at the command prompt and hit enter: screen -r<br />
<br />
<br />
==== Screen Commands To Know ====<br />
Sym-A C - Create a new window/terminal session<br />
<br />
Sym-A N - Change to next window/terminal session within the current screen session<br />
<br />
Sym-A P - Change to previous window/terminal session with the current screen session<br />
<br />
Sym-A D - Detach from current screen session<br />
<br />
== Configuration/Tweaks ==<br />
<br />
Both irssi and GNU Screen are very rich applications with a plethora of scripts, customization and usage options that only a very small percentage of are covered in this document. If interested please search and find how you may be able to adjust them to fit your specific needs (and if you find anything worthwhile feel free to add it to this wiki!)<br />
<br />
For information on irssi please visit their startup documentation http://irssi.org/documentation/startup <br />
<br />
this site provides information that will help you in automating irssi to do tasks like autojoin set servers and channels and automatically identify your nickname with services. <br />
<br />
== Known Issues ==<br />
<br />
When first loaded irssi tends to not properly format to the whole screen and a simple rotation to let the terminal rotate to the side and back to standard typing position will fix it (you will see the characters slowly refresh during this process)<br />
<br />
Even with Screen running you can lose connection if the wifi radio turns off when the screen does, see <link for fixing that><br />
<br />
[[Image:Terminal-irssi.jpg]]</div>Punzadahttp://wiki.webos-internals.org/index.php?title=Linux_Tutorial_Irssi&diff=5792Linux Tutorial Irssi2009-09-16T20:58:11Z<p>Punzada: </p>
<hr />
<div>= Linux Tutorial - Irssi =<br />
<br />
<br />
<br />
=== This Documents Assumes the following ===<br />
<br />
You have followed the procedure to Access Linux on the device and have enabled the Optware repositories and software http://www.webos-internals.org/wiki/Portal:Accessing_Linux<br />
<br />
You have installed the Terminal application http://www.webos-internals.org/wiki/Application:Terminal<br />
<br />
<br />
Once these procedures are done you should have access to:<br />
<br />
The Optware software repositories through ipkg-opt <br />
<br />
The Terminal Application through the WebOS (should load, be the root user, and function)<br />
<br />
<br />
<br />
== Installation ==<br />
<br />
Within the Terminal application use the following command:<br />
<br />
<pre><nowiki><br />
ipkg-opt install screen irssi<br />
</nowiki></pre><br />
<br />
This command will automatically download [http://www.gnu.org/software/screen/ GNU Screen] and [http://irssi.org/ irssi] as well as any necessary dependencies.<br />
<br />
Note: GNU Screen is *not* necessary for irssi to function, it only provides further functionality to be able to close the Terminal application if desired, keep irssi running in the background and reattach to it. Also, I have found that running irssi within a screen session gives irssi shows all its various colors while running natively within the terminal app leaves it mono-colored. <br />
<br />
<br />
== Usage ==<br />
<br />
In order to run irssi you simply need to type irssi into the Terminal application at the shell prompt and once hitting enter(return) it will load. <br />
<br />
However this is '''NOT RECOMMENDED''' as by default the Terminal Application is loaded as the root user and you should avoid using internet facing applications as the root user if it is not necessary (some IRC networks such as EFnet will go as far as to instantly disconnect you if it detects you are connecting to their servers as root). <br />
<br />
Once the Terminal Application is opened you may change to the user you set up when completing the steps to Access Linux via the su command<br />
<br />
example:<br />
<br />
<pre><nowiki><br />
root@castle:/var/home/root# su myuser<br />
myuser@castle:/var/home/root$<br />
</nowiki></pre><br />
<br />
from here you can simply enter irssi and hit return and it shall load.<br />
<br />
===Basic Commands===<br />
<br />
/connect ircserver<br />
<br />
This will connect you to an irc network ex: /connect irc.freenode.net will connect you to the freenode network.<br />
<br />
/join #channel<br />
<br />
This will join the requested channel, ex: /join #webos-internals<br />
<br />
Sym+n Will move to the 'next' window within the irssi interface<br />
Sym+p Will move you to the 'previous' window within the irssi interface<br />
<br />
You can directly jump to a window (numbered in irssi) by hitting Orange Key+Space+Number.<br />
<br />
===GNU Screen History & Basics===<br />
<br />
If you're like me and you want to always keep your irssi session active as well as have the colors available to you a good solution is to use GNU Screen.<br />
<br />
For those that don't know, screen acts as a window manager for terminal applications. Screen allows you to run multiple applications in a single terminal session, switch between the applications freely as well as being able to detach from it entirely, and reattach to it later while having those applications run in the background. Many consider screen to be one of the most important tools available for any type of command line work or administration - is is very powerful and very flexable, feel free to read up on it's customization and abilities to further enhance your experience with it.<br />
<br />
====Screen Usage====<br />
<br />
To start using screen it is very simple, follow the instructions above but before switching to your local user to run irssi, first type screen and hit enter<br />
<br />
You will be greeted with screen's opening text, letting you know that it is running, and the GPL license, simply press the space bar here and you will be taken back into the prompt and it will appear as if you're back to where you started.<br />
<br />
From this point on, follow the instructions above to change into your user that is not root, and open irssi like normal.<br />
<br />
You will see commands listed as such: Sym-A C <br />
<br />
This key combination is important because it means 'Press and hold Sym, then hit A, release both and hit C'<br />
<br />
This is how GNU Screen functions and is vital to it's usage, the example above creates a new window with a fresh terminal session.<br />
<br />
==== Attach / Detach ====<br />
<br />
In order to detach from your screen session use the command Sym-A D<br />
<br />
Once a session is detached you may close out of the terminal app and any applications running within your screen session will continue to run.<br />
<br />
In order to reattach to a session you left running, load the Terminal Application again and type the following at the command prompt and hit enter: screen -r<br />
<br />
<br />
==== Screen Commands To Know ====<br />
Sym-A C - Create a new window/terminal session<br />
<br />
Sym-A N - Change to next window/terminal session within the current screen session<br />
<br />
Sym-A P - Change to previous window/terminal session with the current screen session<br />
<br />
Sym-A D - Detach from current screen session<br />
<br />
== Configuration/Tweaks ==<br />
<br />
Both irssi and GNU Screen are very rich applications with a plethora of scripts, customization and usage options that only a very small percentage of are covered in this document. If interested please search and find how you may be able to adjust them to fit your specific needs (and if you find anything worthwhile feel free to add it to this wiki!)<br />
<br />
For information on irssi please visit their startup documentation http://irssi.org/documentation/startup <br />
<br />
this site provides information that will help you in automating irssi to do tasks like autojoin set servers and channels and automatically identify your nickname with services. <br />
<br />
== Known Issues ==<br />
<br />
When first loaded irssi tends to not properly format to the whole screen and a simple rotation to let the terminal rotate to the side and back to standard typing position will fix it (you will see the characters slowly refresh during this process)<br />
<br />
Even with Screen running you can lose connection if the wifi radio turns off when the screen does, see <link for fixing that><br />
<br />
[[Image:http://img11.imageshack.us/img11/4394/terminal20091609165433.jpg]]</div>Punzadahttp://wiki.webos-internals.org/index.php?title=Linux_Tutorial_Irssi&diff=5791Linux Tutorial Irssi2009-09-16T20:50:09Z<p>Punzada: </p>
<hr />
<div>= Linux Tutorial - Irssi =<br />
<br />
<br />
<br />
=== This Documents Assumes the following ===<br />
<br />
You have followed the procedure to Access Linux on the device and have enabled the Optware repositories and software http://www.webos-internals.org/wiki/Portal:Accessing_Linux<br />
<br />
You have installed the Terminal application http://www.webos-internals.org/wiki/Application:Terminal<br />
<br />
<br />
Once these procedures are done you should have access to:<br />
<br />
The Optware software repositories through ipkg-opt <br />
<br />
The Terminal Application through the WebOS (should load, be the root user, and function)<br />
<br />
<br />
<br />
== Installation ==<br />
<br />
Within the Terminal application use the following command:<br />
<br />
<pre><nowiki><br />
ipkg-opt install screen irssi<br />
</nowiki></pre><br />
<br />
This command will automatically download [http://www.gnu.org/software/screen/ GNU Screen] and [http://irssi.org/ irssi] as well as any necessary dependencies.<br />
<br />
Note: GNU Screen is *not* necessary for irssi to function, it only provides further functionality to be able to close the Terminal application if desired, keep irssi running in the background and reattach to it. Also, I have found that running irssi within a screen session gives irssi shows all its various colors while running natively within the terminal app leaves it mono-colored. <br />
<br />
<br />
== Usage ==<br />
<br />
In order to run irssi you simply need to type irssi into the Terminal application at the shell prompt and once hitting enter(return) it will load. <br />
<br />
However this is '''NOT RECOMMENDED''' as by default the Terminal Application is loaded as the root user and you should avoid using internet facing applications as the root user if it is not necessary (some IRC networks such as EFnet will go as far as to instantly disconnect you if it detects you are connecting to their servers as root). <br />
<br />
Once the Terminal Application is opened you may change to the user you set up when completing the steps to Access Linux via the su command<br />
<br />
example:<br />
<br />
<pre><nowiki><br />
root@castle:/var/home/root# su myuser<br />
myuser@castle:/var/home/root$<br />
</nowiki></pre><br />
<br />
from here you can simply enter irssi and hit return and it shall load.<br />
<br />
===Basic Commands===<br />
<br />
/connect ircserver<br />
<br />
This will connect you to an irc network ex: /connect irc.freenode.net will connect you to the freenode network.<br />
<br />
/join #channel<br />
<br />
This will join the requested channel, ex: /join #webos-internals<br />
<br />
Sym+n Will move to the 'next' window within the irssi interface<br />
Sym+p Will move you to the 'previous' window within the irssi interface<br />
<br />
You can directly jump to a window (numbered in irssi) by hitting Orange Key+Space+Number.<br />
<br />
===GNU Screen History & Basics===<br />
<br />
If you're like me and you want to always keep your irssi session active as well as have the colors available to you a good solution is to use GNU Screen.<br />
<br />
For those that don't know, screen acts as a window manager for terminal applications. Screen allows you to run multiple applications in a single terminal session, switch between the applications freely as well as being able to detach from it entirely, and reattach to it later while having those applications run in the background. Many consider screen to be one of the most important tools available for any type of command line work or administration - is is very powerful and very flexable, feel free to read up on it's customization and abilities to further enhance your experience with it.<br />
<br />
====Screen Usage====<br />
<br />
To start using screen it is very simple, follow the instructions above but before switching to your local user to run irssi, first type screen and hit enter<br />
<br />
You will be greeted with screen's opening text, letting you know that it is running, and the GPL license, simply press the space bar here and you will be taken back into the prompt and it will appear as if you're back to where you started.<br />
<br />
From this point on, follow the instructions above to change into your user that is not root, and open irssi like normal.<br />
<br />
You will see commands listed as such: Sym-A C <br />
<br />
This key combination is important because it means 'Press and hold Sym, then hit A, release both and hit C'<br />
<br />
This is how GNU Screen functions and is vital to it's usage, the example above creates a new window with a fresh terminal session.<br />
<br />
==== Attach / Detach ====<br />
<br />
In order to detach from your screen session use the command Sym-A D<br />
<br />
Once a session is detached you may close out of the terminal app and any applications running within your screen session will continue to run.<br />
<br />
In order to reattach to a session you left running, load the Terminal Application again and type the following at the command prompt and hit enter: screen -r<br />
<br />
<br />
==== Screen Commands To Know ====<br />
Sym-A C - Create a new window/terminal session<br />
<br />
Sym-A N - Change to next window/terminal session within the current screen session<br />
<br />
Sym-A P - Change to previous window/terminal session with the current screen session<br />
<br />
Sym-A D - Detach from current screen session<br />
<br />
== Configuration/Tweaks ==<br />
<br />
Both irssi and GNU Screen are very rich applications with a plethora of scripts, customization and usage options that only a very small percentage of are covered in this document. If interested please search and find how you may be able to adjust them to fit your specific needs (and if you find anything worthwhile feel free to add it to this wiki!)<br />
<br />
For information on irssi please visit their startup documentation http://irssi.org/documentation/startup <br />
<br />
this site provides information that will help you in automating irssi to do tasks like autojoin set servers and channels and automatically identify your nickname with services. <br />
<br />
== Known Issues ==<br />
<br />
When first loaded irssi tends to not properly format to the whole screen and a simple rotation to let the terminal rotate to the side and back to standard typing position will fix it (you will see the characters slowly refresh during this process)<br />
<br />
Even with Screen running you can lose connection if the wifi radio turns off when the screen does, see <link for fixing that></div>Punzadahttp://wiki.webos-internals.org/index.php?title=Linux_Tutorial_Irssi&diff=5790Linux Tutorial Irssi2009-09-16T20:47:14Z<p>Punzada: </p>
<hr />
<div>= Linux Tutorial - Irssi =<br />
<br />
<br />
<br />
=== This Documents Assumes the following ===<br />
<br />
You have followed the procedure to Access Linux on the device and have enabled the Optware repositories and software http://www.webos-internals.org/wiki/Portal:Accessing_Linux<br />
<br />
You have installed the Terminal application http://www.webos-internals.org/wiki/Application:Terminal<br />
<br />
<br />
Once these procedures are done you should have access to:<br />
<br />
The Optware software repositories through ipkg-opt <br />
<br />
The Terminal Application through the WebOS (should load, be the root user, and function)<br />
<br />
<br />
<br />
== Installation ==<br />
<br />
Within the Terminal application use the following command:<br />
<br />
<pre><nowiki><br />
ipkg-opt install screen irssi<br />
</nowiki></pre><br />
<br />
This command will automatically download [http://www.gnu.org/software/screen/ GNU Screen] and [http://irssi.org/ irssi] as well as any necessary dependencies.<br />
<br />
Note: GNU Screen is *not* necessary for irssi to function, it only provides further functionality to be able to close the Terminal application if desired, keep irssi running in the background and reattach to it. Also, I have found that running irssi within a screen session gives irssi shows all its various colors while running natively within the terminal app leaves it mono-colored. <br />
<br />
<br />
== Usage ==<br />
<br />
In order to run irssi you simply need to type irssi into the Terminal application at the shell prompt and once hitting enter(return) it will load. <br />
<br />
However this is '''NOT RECOMMENDED''' as by default the Terminal Application is loaded as the root user and you should avoid using internet facing applications as the root user if it is not necessary (some IRC networks such as EFnet will go as far as to instantly disconnect you if it detects you are connecting to their servers as root). <br />
<br />
Once the Terminal Application is opened you may change to the user you set up when completing the steps to Access Linux via the su command<br />
<br />
example:<br />
<br />
<pre><nowiki><br />
root@castle:/var/home/root# su myuser<br />
myuser@castle:/var/home/root$<br />
</nowiki></pre><br />
<br />
from here you can simply enter irssi and hit return and it shall load.<br />
<br />
===Basic Commands===<br />
<br />
/connect ircserver<br />
<br />
This will connect you to an irc network ex: /connect irc.freenode.net will connect you to the freenode network.<br />
<br />
/join #channel<br />
<br />
This will join the requested channel, ex: /join #webos-internals<br />
<br />
Sym+n Will move to the 'next' window within the irssi interface<br />
Sym+p Will move you to the 'previous' window within the irssi interface<br />
<br />
You can directly jump to a window (numbered in irssi) by hitting Orange Key+Space+Number.<br />
<br />
===GNU/Screen History & Basics===<br />
<br />
If you're like me and you want to always keep your irssi session active as well as have the colors available to you a good solution is to use GNU/Screen.<br />
<br />
For those that don't know, screen acts as a window manager for terminal applications. Screen allows you to run multiple applications in a single terminal session, switch between the applications freely as well as being able to detach from it entirely, and reattach to it later while having those applications run in the background. Many consider screen to be one of the most important tools available for any type of command line work or administration - is is very powerful and very flexable, feel free to read up on it's customization and abilities to further enhance your experience with it.<br />
<br />
====Screen Usage====<br />
<br />
To start using screen it is very simple, follow the instructions above but before switching to your local user to run irssi, first type screen and hit enter<br />
<br />
You will be greeted with screen's opening text, letting you know that it is running, and the GPL license, simply press the space bar here and you will be taken back into the prompt and it will appear as if you're back to where you started.<br />
<br />
From this point on, follow the instructions above to change into your user that is not root, and open irssi like normal.<br />
<br />
You will see commands listed as such: Sym-A C <br />
<br />
This key combination is important because it means 'Press and hold Sym, then hit A, release both and hit C'<br />
<br />
This is how GNU/Screen functions and is vital to it's usage, the example above creates a new window with a fresh terminal session.<br />
<br />
==== Attach / Detach ====<br />
<br />
In order to detach from your screen session use the command Sym-A D<br />
<br />
Once a session is detached you may close out of the terminal app and any applications running within your screen session will continue to run.<br />
<br />
In order to reattach to a session you left running, load the Terminal Application again and type the following at the command prompt and hit enter: screen -r<br />
<br />
<br />
==== Screen Commands To Know ====<br />
Sym-A C - Create a new window/terminal session<br />
<br />
Sym-A N - Change to next window/terminal session within the current screen session<br />
<br />
Sym-A P - Change to previous window/terminal session with the current screen session<br />
<br />
Sym-A D - Detach from current screen session<br />
<br />
== Configuration/Tweaks ==<br />
<br />
Both irssi and GNU/Screen are very rich applications with a plethora of scripts, customization and usage options that only a very small percentage of are covered in this document. If interested please search and find how you may be able to adjust them to fit your specific needs (and if you find anything worthwhile feel free to add it to this wiki!)<br />
<br />
For information on irssi please visit their startup documentation http://irssi.org/documentation/startup <br />
<br />
this site provides information that will help you in automating irssi to do tasks like autojoin set servers and channels and automatically identify your nickname with services. <br />
<br />
== Known Issues ==<br />
<br />
When first loaded irssi tends to not properly format to the whole screen and a simple rotation to let the terminal rotate to the side and back to standard typing position will fix it (you will see the characters slowly refresh during this process)<br />
<br />
Even with Screen running you can lose connection if the wifi radio turns off when the screen does, see <link for fixing that></div>Punzadahttp://wiki.webos-internals.org/index.php?title=Linux_Tutorial_Irssi&diff=5788Linux Tutorial Irssi2009-09-16T20:40:10Z<p>Punzada: </p>
<hr />
<div>= Linux Tutorial - Irssi =<br />
<br />
<br />
<br />
=== This Documents Assumes the following ===<br />
<br />
You have followed the procedure to Access Linux on the device and have enabled the Optware repositories and software http://www.webos-internals.org/wiki/Portal:Accessing_Linux<br />
<br />
You have installed the Terminal application http://www.webos-internals.org/wiki/Application:Terminal<br />
<br />
<br />
Once these procedures are done you should have access to:<br />
<br />
The Optware software repositories through ipkg-opt <br />
<br />
The Terminal Application through the WebOS (should load, be the root user, and function)<br />
<br />
<br />
<br />
== Installation ==<br />
<br />
Within the Terminal application use the following command:<br />
<br />
<pre><nowiki><br />
ipkg-opt install screen irssi<br />
</nowiki></pre><br />
<br />
This command will automatically download [http://www.gnu.org/software/screen/ GNU Screen] and [http://irssi.org/ irssi] as well as any necessary dependencies.<br />
<br />
Note: GNU Screen is *not* necessary for irssi to function, it only provides further functionality to be able to close the Terminal application if desired, keep irssi running in the background and reattach to it. Also, I have found that running irssi within a screen session gives irssi shows all its various colors while running natively within the terminal app leaves it mono-colored. <br />
<br />
<br />
== Usage ==<br />
<br />
In order to run irssi you simply need to type irssi into the Terminal application at the shell prompt and once hitting enter(return) it will load. <br />
<br />
However this is '''NOT RECOMMENDED''' as by default the Terminal Application is loaded as the root user and you should avoid using internet facing applications as the root user if it is not necessary (some IRC networks such as EFnet will go as far as to instantly disconnect you if it detects you are connecting to their servers as root). <br />
<br />
Once the Terminal Application is opened you may change to the user you set up when completing the steps to Access Linux via the su command<br />
<br />
example:<br />
<br />
<pre><nowiki><br />
root@castle:/var/home/root# su myuser<br />
myuser@castle:/var/home/root$<br />
</nowiki></pre><br />
<br />
from here you can simply enter irssi and hit return and it shall load.<br />
<br />
===Basic Commands===<br />
<br />
/connect ircserver<br />
<br />
This will connect you to an irc network ex: /connect irc.freenode.net will connect you to the freenode network.<br />
<br />
/join #channel<br />
<br />
This will join the requested channel, ex: /join #webos-internals<br />
<br />
Sym+n Will move to the 'next' window within the irssi interface<br />
Sym+p Will move you to the 'previous' window within the irssi interface<br />
<br />
You can directly jump to a window (numbered in irssi) by hitting Orange Key+Space+Number.<br />
<br />
===GNU/Screen History & Basics===<br />
<br />
If you're like me and you want to always keep your irssi session active as well as have the colors available to you a good solution is to use GNU/Screen.<br />
<br />
For those that don't know, screen acts as a window manager for terminal applications. Screen allows you to run multiple applications in a single terminal session, switch between the applications freely as well as being able to detach from it entirely, and reattach to it later while having those applications run in the background. Many consider screen to be one of the most important tools available for any type of command line work or administration - is is very powerful and very flexable, feel free to read up on it's customization and abilities to further enhance your experience with it.<br />
<br />
====Screen Usage====<br />
<br />
To start using screen it is very simple, follow the instructions above but before switching to your local user to run irssi, first run screen and hit enter<br />
<br />
You will be greeted with screen's opening text, letting you know that it is running, and the GPL license, simply press the space bar here and you will be taken back into the prompt and it will appear as if you're back to where you started.<br />
<br />
From this point on, follow the instructions above to change into your user that is not root, and open irssi like normal.<br />
<br />
You will see commands listed as such: Sym-A C <br />
<br />
This key combination is important because it means 'Press and hold Sym, then hit A, release both and hit C'<br />
<br />
This is how GNU/Screen functions and is vital to it's usage, the example above creates a new window with a fresh terminal session.<br />
<br />
==== Attach / Detach ====<br />
<br />
In order to detach from your screen session use the command Sym-A D<br />
<br />
Once a session is detached you may close out of the terminal app and any applications running within your screen session will continue to run.<br />
<br />
In order to reattach to a session you left running, load the Terminal Application again and type the following at the command prompt and hit enter: screen -r<br />
<br />
<br />
==== Screen Commands To Know ====<br />
Sym-A C - Create a new window/terminal session<br />
<br />
Sym-A N - Change to next window/terminal session within the current screen session<br />
<br />
Sym-A P - Change to previous window/terminal session with the current screen session<br />
<br />
Sym-A D - Detach from current screen session<br />
<br />
== Configuration/Tweaks ==<br />
<br />
<br />
<br />
== Known Issues ==<br />
<br />
When first loaded irssi tends to not properly format to the whole screen and a simple rotation to let the terminal rotate to the side and back to standard typing position will fix it (you will see the characters slowly refresh during this process)<br />
<br />
Even with Screen running you can lose connection if the wifi radio turns off when the screen does, see <link for fixing that></div>Punzadahttp://wiki.webos-internals.org/index.php?title=Linux_Tutorial_Irssi&diff=5787Linux Tutorial Irssi2009-09-16T20:37:34Z<p>Punzada: </p>
<hr />
<div>= Linux Tutorial - Irssi =<br />
<br />
<br />
<br />
=== This Documents Assumes the following ===<br />
<br />
You have followed the procedure to Access Linux on the device and have enabled the Optware repositories and software http://www.webos-internals.org/wiki/Portal:Accessing_Linux<br />
<br />
You have installed the Terminal application http://www.webos-internals.org/wiki/Application:Terminal<br />
<br />
<br />
Once these procedures are done you should have access to:<br />
<br />
The Optware software repositories through ipkg-opt <br />
<br />
The Terminal Application through the WebOS (should load, be the root user, and function)<br />
<br />
<br />
<br />
== Installation ==<br />
<br />
Within the Terminal application use the following command:<br />
<br />
<pre><nowiki><br />
ipkg-opt install screen irssi<br />
</nowiki></pre><br />
<br />
This command will automatically download [http://www.gnu.org/software/screen/ GNU Screen] and [http://irssi.org/ irssi] as well as any necessary dependencies.<br />
<br />
Note: GNU Screen is *not* necessary for irssi to function, it only provides further functionality to be able to close the Terminal application if desired, keep irssi running in the background and reattach to it. Also, I have found that running irssi within a screen session gives irssi shows all its various colors while running natively within the terminal app leaves it mono-colored. <br />
<br />
<br />
== Usage ==<br />
<br />
In order to run irssi you simply need to type irssi into the Terminal application at the shell prompt and once hitting enter(return) it will load. <br />
<br />
However this is '''NOT RECOMMENDED''' as by default the Terminal Application is loaded as the root user and you should avoid using internet facing applications as the root user if it is not necessary (some IRC networks such as EFnet will go as far as to instantly disconnect you if it detects you are connecting to their servers as root). <br />
<br />
Once the Terminal Application is opened you may change to the user you set up when completing the steps to Access Linux via the su command<br />
<br />
example:<br />
<br />
<pre><nowiki><br />
root@castle:/var/home/root# su myuser<br />
myuser@castle:/var/home/root$<br />
</nowiki></pre><br />
<br />
from here you can simply enter irssi and hit return and it shall load.<br />
<br />
===Basic Commands===<br />
<br />
/connect ircserver<br />
<br />
This will connect you to an irc network ex: /connect irc.freenode.net will connect you to the freenode network.<br />
<br />
/join #channel<br />
<br />
This will join the requested channel, ex: /join #webos-internals<br />
<br />
Sym+n Will move to the 'next' window within the irssi interface<br />
Sym+p Will move you to the 'previous' window within the irssi interface<br />
<br />
You can directly jump to a window (numbered in irssi) by hitting Orange Key+Space+Number.<br />
<br />
===GNU/Screen History & Basics===<br />
<br />
If you're like me and you want to always keep your irssi session active as well as have the colors available to you a good solution is to use GNU/Screen.<br />
<br />
For those that don't know, screen acts as a window manager for terminal applications. Screen allows you to run multiple applications in a single terminal session, switch between the applications freely as well as being able to detach from it entirely, and reattach to it later while having those applications run in the background. Many consider screen to be one of the most important tools available for any type of command line work or administration - is is very powerful and very flexable, feel free to read up on it's customization and abilities to further enhance your experience with it.<br />
<br />
====Screen Usage====<br />
<br />
To start using screen it is very simple, follow the instructions above but before switching to your local user to run irssi, first run screen and hit enter<br />
<br />
You will be greeted with screen's opening text, letting you know that it is running, and the GPL license, simply press the space bar here and you will be taken back into the prompt and it will appear as if you're back to where you started.<br />
<br />
From this point on, follow the instructions above to change into your user that is not root, and open irssi like normal.<br />
<br />
You will see commands listed as such: Sym-A C <br />
<br />
This key combination is important because it means 'Press and hold Sym, then hit A, release both and hit C'<br />
<br />
This is how GNU/Screen functions and is vital to it's usage, the example above creates a new window with a fresh terminal session.<br />
<br />
==== Attach / Detach ====<br />
<br />
In order to detach from your screen session use the command Sym-A D<br />
<br />
Once a session is detached you may close out of the terminal app and any applications running within your screen session will continue to run.<br />
<br />
In order to reattach to a session you left running, load the Terminal Application again and type the following at the command prompt and hit enter: screen -r<br />
<br />
<br />
==== Screen Commands To Know ====<br />
Sym-A C - Create a new window/terminal session<br />
Sym-A N - Change to next window/terminal session within the current screen session<br />
Sym-A P - Change to previous window/terminal session with the current screen session<br />
Sym-A D - Detach from current screen session<br />
<br />
== Configuration/Tweaks ==<br />
<br />
<br />
<br />
== Known Issues ==<br />
<br />
When first loaded irssi tends to not properly format to the whole screen and a simple rotation to let the terminal rotate to the side and back to standard typing position will fix it (you will see the characters slowly refresh during this process)<br />
<br />
Even with Screen running you can lose connection if the wifi radio turns off when the screen does, see <link for fixing that></div>Punzadahttp://wiki.webos-internals.org/index.php?title=Linux_Tutorial_Irssi&diff=5786Linux Tutorial Irssi2009-09-16T20:12:29Z<p>Punzada: </p>
<hr />
<div>= Linux Tutorial - Irssi =<br />
<br />
<br />
<br />
=== This Documents Assumes the following ===<br />
<br />
You have followed the procedure to Access Linux on the device and have enabled the Optware repositories and software http://www.webos-internals.org/wiki/Portal:Accessing_Linux<br />
<br />
You have installed the Terminal application http://www.webos-internals.org/wiki/Application:Terminal<br />
<br />
<br />
Once these procedures are done you should have access to:<br />
<br />
The Optware software repositories through ipkg-opt <br />
<br />
The Terminal Application through the WebOS (should load, be the root user, and function)<br />
<br />
<br />
<br />
== Installation ==<br />
<br />
Within the Terminal application use the following command:<br />
<br />
<pre><nowiki><br />
ipkg-opt install screen irssi<br />
</nowiki></pre><br />
<br />
This command will automatically download [http://www.gnu.org/software/screen/ GNU Screen] and [http://irssi.org/ irssi] as well as any necessary dependencies.<br />
<br />
Note: GNU Screen is *not* necessary for irssi to function, it only provides further functionality to be able to close the Terminal application if desired, keep irssi running in the background and reattach to it. Also, I have found that running irssi within a screen session gives irssi shows all its various colors while running natively within the terminal app leaves it mono-colored. <br />
<br />
<br />
== Usage ==<br />
<br />
In order to run irssi you simply need to type irssi into the Terminal application at the shell prompt and once hitting enter(return) it will load. <br />
<br />
However this is '''NOT RECOMMENDED''' as by default the Terminal Application is loaded as the root user and you should avoid using internet facing applications as the root user if it is not necessary (some IRC networks such as EFnet will go as far as to instantly disconnect you if it detects you are connecting to their servers as root). <br />
<br />
Once the Terminal Application is opened you may change to the user you set up when completing the steps to Access Linux via the su command<br />
<br />
example:<br />
<br />
<pre><nowiki><br />
root@castle:/var/home/root# su myuser<br />
myuser@castle:/var/home/root$<br />
</nowiki></pre><br />
<br />
from here you can simply enter irssi and hit return and it shall load.<br />
<br />
===Working with GNU/Screen===<br />
<br />
===Basic Commands===<br />
<br />
/connect ircserver<br />
<br />
This will connect you to an irc network ex: /connect irc.freenode.net will connect you to the freenode network.<br />
<br />
/join #channel<br />
<br />
This will join the requested channel, ex: /join #webos-internals<br />
<br />
Sym+n Will move to the 'next' window within the irssi interface<br />
Sym+p Will move you to the 'previous' window within the irssi interface<br />
<br />
You can directly jump to a window (numbered in irssi) by hitting Orange Key+Space+Number (or if you exceed 10 windows for 1-9 the next 10 windows are handled by the q through p keys)<br />
<br />
== Configuration/Tweaks ==<br />
<br />
<br />
<br />
== Known Issues ==<br />
<br />
Even with Screen running you can lose connection if the wifi radio turns off when the screen does, see <link for fixing that></div>Punzadahttp://wiki.webos-internals.org/index.php?title=Linux_Tutorial_Irssi&diff=5785Linux Tutorial Irssi2009-09-16T19:54:51Z<p>Punzada: </p>
<hr />
<div>= Linux Tutorial - Irssi =<br />
<br />
<br />
<br />
=== This Documents Assumes the following ===<br />
<br />
You have followed the procedure to Access Linux on the device and have enabled the Optware repositories and software http://www.webos-internals.org/wiki/Portal:Accessing_Linux<br />
<br />
You have installed the Terminal application http://www.webos-internals.org/wiki/Application:Terminal<br />
<br />
<br />
Once these procedures are done you should have access to:<br />
<br />
The Optware software repositories through ipkg-opt <br />
<br />
The Terminal Application through the WebOS (should load, be the root user, and function)<br />
<br />
<br />
<br />
== Installation ==<br />
<br />
Within the Terminal application use the following command:<br />
<br />
<pre><nowiki><br />
ipkg-opt install screen irssi<br />
</nowiki></pre><br />
<br />
This command will automatically download [http://www.gnu.org/software/screen/ GNU Screen] and [http://irssi.org/ irssi] as well as any necessary dependencies.<br />
<br />
Note: GNU Screen is *not* necessary for irssi to function, it only provides further functionality to be able to close the Terminal application if desired, keep irssi running in the background and reattach to it. Also, I have found that running irssi within a screen session gives irssi shows all its various colors while running natively within the terminal app leaves it mono-colored. <br />
<br />
<br />
== Configuration/Tweaks ==<br />
<br />
<br />
<br />
== Known Issues ==<br />
<br />
Even with Screen running you can lose connection if the wifi radio turns off when the screen does, see <link for fixing that></div>Punzadahttp://wiki.webos-internals.org/index.php?title=Linux_Tutorial_Irssi&diff=5784Linux Tutorial Irssi2009-09-16T19:45:31Z<p>Punzada: New page: = Linux Tutorial - Irssi = === This Documents Assumes the following === You have followed the procedure to Access Linux on the device and have enabled the Optware repositories and soft...</p>
<hr />
<div>= Linux Tutorial - Irssi =<br />
<br />
<br />
<br />
=== This Documents Assumes the following ===<br />
<br />
You have followed the procedure to Access Linux on the device and have enabled the Optware repositories and software http://www.webos-internals.org/wiki/Portal:Accessing_Linux<br />
<br />
You have installed the Terminal application http://www.webos-internals.org/wiki/Application:Terminal<br />
<br />
<br />
Once these procedures are done you should have access to:<br />
<br />
The Optware software repositories through ipkg-opt <br />
<br />
The Terminal Application through the WebOS (should load, be the root user, and function)<br />
<br />
<br />
<br />
== Installation ==<br />
<br />
Within the Terminal application use the following command:<br />
<br />
ipkg-opt install screen irssi<br />
<br />
This command will automatically download GNU Screen (link needed) and irssi (link needed) as well as any necessary dependencies.<br />
<br />
<br />
== Configuration/Tweaks ==<br />
<br />
<br />
<br />
== Known Issues ==<br />
<br />
Even with Screen running you can lose connection if the wifi radio turns off when the screen does, see <link for fixing that></div>Punzada