https://wiki.redbrick.dcu.ie/api.php?action=feedcontributions&feedformat=atom&user=CreadakRedbrick Wiki - User contributions [en]2026-05-21T23:05:50ZUser contributionsMediaWiki 1.39.8https://wiki.redbrick.dcu.ie/index.php?title=Weechat&diff=10694Weechat2015-07-23T14:34:59Z<p>Creadak: /* Conditions */</p>
<hr />
<div>Once upon a time there was BitchX. Then there was Irssi. Now there is Weechat. More and more people are switching over to Weechat from Irssi, probably coz the colours make IRC easier to read and follow. Problem is, for the Irssi user, Weechat may be a tad confusing.<br />
<br />
Weechat documentation can be tricky to follow, so this page is an attempt to make simple those bizarre and abstract commands.<br />
<br />
== Running Weechat ==<br />
<br />
Dregin is a big Weechat fanboi. And as such, he has his own special builds designed for Redbrick. Azazel is the current login machine, dregin has compiled a version of Weechat that runs on azazel:<br />
<br />
/home/associat/d/dregin/root_azazel/bin/weechat-curses<br />
<br />
Copy and paste that into your terminal command line, hit enter, and give yourself a pat on the back.<br />
<br />
== Compiling Weechat ==<br />
You can run <br />
~edu/compileweechat<br />
or <br />
git clone https://github.com/weechat/weechat<br />
cd weechat<br />
mkdir build<br />
cd build<br />
cmake .. -DCMAKE_INSTALL_PREFIX=$HOME -DENABLE_NLS=OFF<br />
make<br />
make install<br />
echo '*/upgrade ~/bin/weechat' > `find ~/.weechat -name "weechat_fifo_*"`<br />
rm -rf ~/weechat<br />
<br />
==Customising Weechat ==<br />
Weechat can be very basic when you first run it so here are some conf files to set it up with.<br />
cp ~edu/wcconf/* ~/.weechat/ <br />
you need to set your nick for the server<br />
vim ~/.weechat/irc.conf<br />
change “nicks” field to your username<br />
<br />
== Basic use ==<br />
<br />
=== Connecting to a server and channel ===<br />
<br />
When you hit 'chat' on Redbrick, you start Irssi, you're automatically connected to a server, then you're joined to Redbrick's #lobby. This all happens behind the scenes, and with Weechat, you need to do this manually. Fear not: it's easy.<br />
<br />
When you start Weechat, you won't get connected to a server or channel. To connect to Redbrick's IRC sever, type:<br />
<br />
/connect irc.redbrick.dcu.ie<br />
<br />
Then to join #lobby:<br />
<br />
/join #lobby<br />
<br />
As well as showing you how IRC clients (such as Weechat or Irssi or whatever) connect to stuff, this should also show you how to connect to other servers and channels outside of Redbrick.<br />
<br />
To connect to any server, simply enter /connect <server_address>. You will probably be greeted with various messages and such from that server. To join a channel on that server, just type /join <channel_name>.<br />
<br />
=== Navigation ===<br />
<br />
Like Irssi, you can move between windows/buffers using Alt+<num>. You can also type /buffer <num> (similar to /win <num> in Irssi).<br />
Unlike irssi you can do Alt+j then <num> to change to a number greather the 10 .<br />
<br />
F5 and F6 move to the predecessing and successing buffer, respectively.<br />
<br />
You can move buffers (chat windows) with /buffer move. In a channel, type:<br />
<br />
/buffer move <num><br />
<br />
(where <num> is any number you want). That channel is now accessible at Alt+<num><br />
<br />
=== Changing between servers ===<br />
<br />
Weechat will generally assume that whatever channel you're in, that's also the server you're operating on. So you can chat away as you wish and issue general commands.<br />
<br />
However, for some commands, you will need to let Weechat know what server you're on.<br />
<br />
Hit Alt+1. This will bring you to your status window. Along the bottom you will see the time, number of channels, the server you're connect to, as well as other channel stuff.<br />
<br />
Press Ctrl+x. If you're connected to multiple servers, the ''server'' section will change, telling you which server Weechat is connect to. So now you can issue commands to that server (such as /nick) without affecting other servers.<br />
<br />
For example, I am currently connected to irc.redbrick.dcu.ie and to irc.starchat.net. If I hit Ctrl-x I can switch to StarChat, and change my nickname there without it affecting Redbrick's IRC.<br />
<br />
== Mobile ==<br />
<br />
weechat has a mobile app you can get from the [https://play.google.com/store/apps/details?id=com.ubergeek42.WeechatAndroid google play store] or from the [https://github.com/ubergeek42/weechat-android github].<br />
Before we set up the app we need to go too weechat on the terminal and type in:<br />
/relay add weechat 1337<br />
then we need to set the password <br />
/set relay.network.password "your-secret-password"<br />
<br />
now on the Phone launch the app and in settings<br />
In connection settings <br />
Relay host: localhost<br />
Relay Port: 1337 (choose your own port) <br />
Relay password: your-secret-password<br />
Connect type: SSH tunnel<br />
then in SSH Tunnel settings<br />
SSH host: redbrick.dcu.ie<br />
SSH username: your username<br />
SSH port: 22<br />
if you have an ssh key add the route to the key on your phone in SSH Private key file and put the passphrase in the SSH password/key passphrase box, if you dont just put your password in there<br />
<br />
== Special commands ==<br />
<br />
=== Keybinds ===<br />
<br />
Keybinds are handy, especially if you have over 10 channels open. I use Alt+<num> to get to channels, but clearly this only works from 1 up to 0 (on a keyboard). So for channels in higher numbers, you can ''bind'' keys: i.e. Alt+q gets me to channel 11; Alt+y gets me to channel 16.<br />
<br />
/key bind meta-q /buffer 11<br />
<br />
"Key" and "bind" are self-explanatory. "Meta" is Weechat's word for Alt (so meta-q is the same as Alt+q). /buffer 11 is the command that's executed once meta-q (Alt-q) is typed.<br />
<br />
You can build up these to meta-w, meta-e, meta-r for buffer 2, buffer 3, buffer 4, etc etc.<br />
<br />
Of course, you can bind any key combo to any weechat command; it's not necessary to make them Alt+<num> commands.<br />
<br />
'''Note:''' Watch out for caps lock if you're keybinding. If you bind Alt+y to a command, Alt+Y won't work (unless you bind that separately). If you find your binds aren't working, check your caps.<br />
<br />
<br />
<br />
== Triggers ==<br />
<br />
Triggers are the swiss army knife of weechat. They can replace a '''lot''' of scripts, and we're still finding things to turn into trigger<br />
<br />
=== Turn any line with "nsfw" in it bright red ===<br />
/trigger addreplace nsfw modifier weechat_print "${tg_notify} && ${tg_message_nocolor} =~ .*nsfw.*" "/(.*)/${tg_prefix}\t${color:red}!NSFW! ${tg_message}"<br />
=== Make urls underlined and blue ===<br />
/trigger addreplace url_color modifier "weechat_print" "${tg_tags} !~ irc_quit" ";[a-z]+://\S+;${color:32}${color:underline}${re:0}${color:-underline}${color:reset};" ""<br />
===Strip items such as time from screen on smaller screens ===<br />
/trigger addreplace resize_small_timestamp signal signal_sigwinch "${info:term_width} < 200" "" "/set weechat.look.buffer_time_format \"\""<br />
===add items such as time from screen on bigger screens ===<br />
/trigger addreplace resize_big_timestamp signal signal_sigwinch "${info:term_width} >=200" "" "/set weechat.look.buffer_time_format %H:%M:%S "<br />
<br />
=== turn off nicklist on smaller screens ===<br />
/trigger addreplace resize_big signal signal_sigwinch "${info:term_width} >= 100" "" "/bar show nicklist"<br />
/trigger addreplace resize_small signal signal_sigwinch "${info:term_width} < 100" "" "/bar hide nicklist"<br />
=== turn off buffer list on small screens ===<br />
/trigger addreplace resize_small_buffer signal signal_sigwinch "${info:term_width} < 100" "" "/bar hide buffers"<br />
/trigger addreplace resize_big_buffer signal signal_sigwinch "${info:term_width} >= 100" "" "/bar show buffers"<br />
<br />
==Conditions==<br />
<br />
Conditions can be used to customize weechat depending on certain variables<br />
<br />
===Turn off nicklist on small windows===<br />
/set weechat.bar.nicklist.conditions "${nicklist} && (${window.win_width} > 100 || ${buffer.full_name} == irc.bitlbee.&bitlbee)"<br />
<br />
===Hide buffer list on small terminals===<br />
/set weechat.bar.buffers.conditions "${info:term_width > 100}"<br />
<br />
===Turn off status on nonactive windows ===<br />
/set weechat.bar.status.conditions "${active} && ${window}"<br />
<br />
== Spell Checker ==<br />
<br />
Weechat uses a handy aspell plugin to check your spelling. To enable it, either use iset or use<br />
/set aspell.check.enabled on<br />
<br />
Aspell has a few settings which you may find useful<br />
<br />
/set aspell.check.real_time on<br />
/set aspell.check.word_min_length 2<br />
/set aspell.check.default_dict "en"<br />
/set aspell.check.suggestions 3<br />
<br />
Or alternatively if you use iset, search for aspell<br />
<br />
The aspell plugin can also offer suggestions as of 0.4.0 and it can be added as an item to your status bar. The item should be added to weechat.bar.status.items. For instance:<br />
/set weechat.bar.status.items "time |,buffer_number+:buffer_name+(buffer_modes)+ |,buffer_nicklist_count |,hotlist |,[aspell_suggest]</div>Creadakhttps://wiki.redbrick.dcu.ie/index.php?title=Weechat&diff=10676Weechat2015-07-15T08:46:12Z<p>Creadak: </p>
<hr />
<div>Once upon a time there was BitchX. Then there was Irssi. Now there is Weechat. More and more people are switching over to Weechat from Irssi, probably coz the colours make IRC easier to read and follow. Problem is, for the Irssi user, Weechat may be a tad confusing.<br />
<br />
Weechat documentation can be tricky to follow, so this page is an attempt to make simple those bizarre and abstract commands.<br />
<br />
== Running Weechat ==<br />
<br />
Dregin is a big Weechat fanboi. And as such, he has his own special builds designed for Redbrick. Azazel is the current login machine, dregin has compiled a version of Weechat that runs on azazel:<br />
<br />
/home/associat/d/dregin/root_azazel/bin/weechat-curses<br />
<br />
Copy and paste that into your terminal command line, hit enter, and give yourself a pat on the back.<br />
<br />
== Compiling Weechat ==<br />
You can run <br />
~edu/compileweechat<br />
or <br />
git clone https://github.com/weechat/weechat<br />
cd weechat<br />
mkdir build<br />
cd build<br />
cmake .. -DCMAKE_INSTALL_PREFIX=$HOME -DENABLE_NLS=OFF<br />
make<br />
make install<br />
echo '*/upgrade ~/bin/weechat' > `find ~/.weechat -name "weechat_fifo_*"`<br />
rm -rf ~/weechat<br />
<br />
==Customising Weechat ==<br />
Weechat can be very basic when you first run it so here are some conf files to set it up with.<br />
cp ~edu/wcconf/* ~/.weechat/ <br />
you need to set your nick for the server<br />
vim ~/.weechat/irc.conf<br />
change “nicks” field to your username<br />
<br />
== Basic use ==<br />
<br />
=== Connecting to a server and channel ===<br />
<br />
When you hit 'chat' on Redbrick, you start Irssi, you're automatically connected to a server, then you're joined to Redbrick's #lobby. This all happens behind the scenes, and with Weechat, you need to do this manually. Fear not: it's easy.<br />
<br />
When you start Weechat, you won't get connected to a server or channel. To connect to Redbrick's IRC sever, type:<br />
<br />
/connect irc.redbrick.dcu.ie<br />
<br />
Then to join #lobby:<br />
<br />
/join #lobby<br />
<br />
As well as showing you how IRC clients (such as Weechat or Irssi or whatever) connect to stuff, this should also show you how to connect to other servers and channels outside of Redbrick.<br />
<br />
To connect to any server, simply enter /connect <server_address>. You will probably be greeted with various messages and such from that server. To join a channel on that server, just type /join <channel_name>.<br />
<br />
=== Navigation ===<br />
<br />
Like Irssi, you can move between windows/buffers using Alt+<num>. You can also type /buffer <num> (similar to /win <num> in Irssi).<br />
Unlike irssi you can do Alt+j then <num> to change to a number greather the 10 .<br />
<br />
F5 and F6 move to the predecessing and successing buffer, respectively.<br />
<br />
You can move buffers (chat windows) with /buffer move. In a channel, type:<br />
<br />
/buffer move <num><br />
<br />
(where <num> is any number you want). That channel is now accessible at Alt+<num><br />
<br />
=== Changing between servers ===<br />
<br />
Weechat will generally assume that whatever channel you're in, that's also the server you're operating on. So you can chat away as you wish and issue general commands.<br />
<br />
However, for some commands, you will need to let Weechat know what server you're on.<br />
<br />
Hit Alt+1. This will bring you to your status window. Along the bottom you will see the time, number of channels, the server you're connect to, as well as other channel stuff.<br />
<br />
Press Ctrl+x. If you're connected to multiple servers, the ''server'' section will change, telling you which server Weechat is connect to. So now you can issue commands to that server (such as /nick) without affecting other servers.<br />
<br />
For example, I am currently connected to irc.redbrick.dcu.ie and to irc.starchat.net. If I hit Ctrl-x I can switch to StarChat, and change my nickname there without it affecting Redbrick's IRC.<br />
<br />
== Mobile ==<br />
<br />
weechat has a mobile app you can get from the [https://play.google.com/store/apps/details?id=com.ubergeek42.WeechatAndroid google play store] or from the [https://github.com/ubergeek42/weechat-android github].<br />
Before we set up the app we need to go too weechat on the terminal and type in:<br />
/relay add weechat 1337<br />
then we need to set the password <br />
/set relay.network.password "your-secret-password"<br />
<br />
now on the Phone launch the app and in settings<br />
In connection settings <br />
Relay host: localhost<br />
Relay Port: 1337 (choose your own port) <br />
Relay password: your-secret-password<br />
Connect type: SSH tunnel<br />
then in SSH Tunnel settings<br />
SSH host: redbrick.dcu.ie<br />
SSH username: your username<br />
SSH port: 22<br />
if you have an ssh key add the route to the key on your phone in SSH Private key file and put the passphrase in the SSH password/key passphrase box, if you dont just put your password in there<br />
<br />
== Special commands ==<br />
<br />
=== Keybinds ===<br />
<br />
Keybinds are handy, especially if you have over 10 channels open. I use Alt+<num> to get to channels, but clearly this only works from 1 up to 0 (on a keyboard). So for channels in higher numbers, you can ''bind'' keys: i.e. Alt+q gets me to channel 11; Alt+y gets me to channel 16.<br />
<br />
/key bind meta-q /buffer 11<br />
<br />
"Key" and "bind" are self-explanatory. "Meta" is Weechat's word for Alt (so meta-q is the same as Alt+q). /buffer 11 is the command that's executed once meta-q (Alt-q) is typed.<br />
<br />
You can build up these to meta-w, meta-e, meta-r for buffer 2, buffer 3, buffer 4, etc etc.<br />
<br />
Of course, you can bind any key combo to any weechat command; it's not necessary to make them Alt+<num> commands.<br />
<br />
'''Note:''' Watch out for caps lock if you're keybinding. If you bind Alt+y to a command, Alt+Y won't work (unless you bind that separately). If you find your binds aren't working, check your caps.<br />
<br />
<br />
<br />
== Triggers ==<br />
<br />
Triggers are the swiss army knife of weechat. They can replace a '''lot''' of scripts, and we're still finding things to turn into trigger<br />
<br />
=== Turn any line with "nsfw" in it bright red ===<br />
/trigger addreplace nsfw modifier weechat_print "${tg_notify} && ${tg_message_nocolor} =~ .*nsfw.*" "/(.*)/${tg_prefix}\t${color:red}!NSFW! ${tg_message}"<br />
=== Make urls underlined and blue ===<br />
/trigger addreplace url_color modifier "weechat_print" "${tg_tags} !~ irc_quit" ";[a-z]+://\S+;${color:32}${color:underline}${re:0}${color:-underline}${color:reset};" ""<br />
=== Strip items such as buffer list and nick list from screen on smaller screens ===<br />
/trigger addreplace resize_small_timestamp signal signal_sigwinch "${info:term_width} < 200" "" "/set weechat.look.buffer_time_format """<br />
=== turn off nicklist on smaller screens ===<br />
/trigger addreplace resize_big signal signal_sigwinch "${info:term_width} >= 100" "" "/bar show nicklist"<br />
/trigger addreplace resize_small signal signal_sigwinch "${info:term_width} < 100" "" "/bar hide nicklist"<br />
=== turn off buffer list on small screens ===<br />
/trigger addreplace resize_small_buffer signal signal_sigwinch "${info:term_width} < 100" "" "/bar hide buffer"<br />
/trigger add replace resize_big_buffer signal signal_sigwinch "${info:term_width} >= 100" "" "/bar show buffer"<br />
<br />
== Spell Checker ==<br />
<br />
Weechat uses a handy aspell plugin to check your spelling. To enable it, either use iset or use<br />
/set aspell.check.enabled on<br />
<br />
Aspell has a few settings which you may find useful<br />
<br />
/set aspell.check.real_time on<br />
/set aspell.check.word_min_length 2<br />
/set aspell.check.default_dict "en"<br />
/set aspell.check.suggestions 3<br />
<br />
Or alternatively if you use iset, search for aspell<br />
<br />
The aspell plugin can also offer suggestions as of 0.4.0 and it can be added as an item to your status bar. The item should be added to weechat.bar.status.items. For instance:<br />
/set weechat.bar.status.items "time |,buffer_number+:buffer_name+(buffer_modes)+ |,buffer_nicklist_count |,hotlist |,[aspell_suggest]</div>Creadakhttps://wiki.redbrick.dcu.ie/index.php?title=Weechat&diff=10675Weechat2015-07-14T23:25:34Z<p>Creadak: /* Triggers */</p>
<hr />
<div>Once upon a time there was BitchX. Then there was Irssi. Now there is Weechat. More and more people are switching over to Weechat from Irssi, probably coz the colours make IRC easier to read and follow. Problem is, for the Irssi user, Weechat may be a tad confusing.<br />
<br />
Weechat documentation can be tricky to follow, so this page is an attempt to make simple those bizarre and abstract commands.<br />
<br />
== Running Weechat ==<br />
<br />
Dregin is a big Weechat fanboi. And as such, he has his own special builds designed for Redbrick. Azazel is the current login machine, dregin has compiled a version of Weechat that runs on azazel:<br />
<br />
/home/associat/d/dregin/root_azazel/bin/weechat-curses<br />
<br />
Copy and paste that into your terminal command line, hit enter, and give yourself a pat on the back.<br />
<br />
== Compiling Weechat ==<br />
You can run <br />
~edu/compileweechat<br />
or <br />
git clone https://github.com/weechat/weechat<br />
cd weechat<br />
mkdir build<br />
cd build<br />
cmake .. -DCMAKE_INSTALL_PREFIX=$HOME -DENABLE_NLS=OFF<br />
make<br />
make install<br />
echo '*/upgrade ~/bin/weechat' > `find ~/.weechat -name "weechat_fifo_*"`<br />
rm -rf ~/weechat<br />
<br />
==Customising Weechat ==<br />
Weechat can be very basic when you first run it so here are some conf files to set it up with.<br />
cp ~edu/wcconf/* ~/.weechat/ <br />
you need to set your nick for the server<br />
vim ~/.weechat/irc.conf<br />
change “nicks” field to your username<br />
<br />
== Basic use ==<br />
<br />
=== Connecting to a server and channel ===<br />
<br />
When you hit 'chat' on Redbrick, you start Irssi, you're automatically connected to a server, then you're joined to Redbrick's #lobby. This all happens behind the scenes, and with Weechat, you need to do this manually. Fear not: it's easy.<br />
<br />
When you start Weechat, you won't get connected to a server or channel. To connect to Redbrick's IRC sever, type:<br />
<br />
/connect irc.redbrick.dcu.ie<br />
<br />
Then to join #lobby:<br />
<br />
/join #lobby<br />
<br />
As well as showing you how IRC clients (such as Weechat or Irssi or whatever) connect to stuff, this should also show you how to connect to other servers and channels outside of Redbrick.<br />
<br />
To connect to any server, simply enter /connect <server_address>. You will probably be greeted with various messages and such from that server. To join a channel on that server, just type /join <channel_name>.<br />
<br />
=== Navigation ===<br />
<br />
Like Irssi, you can move between windows/buffers using Alt+<num>. You can also type /buffer <num> (similar to /win <num> in Irssi).<br />
Unlike irssi you can do Alt+j then <num> to change to a number greather the 10 .<br />
<br />
F5 and F6 move to the predecessing and successing buffer, respectively.<br />
<br />
You can move buffers (chat windows) with /buffer move. In a channel, type:<br />
<br />
/buffer move <num><br />
<br />
(where <num> is any number you want). That channel is now accessible at Alt+<num><br />
<br />
=== Changing between servers ===<br />
<br />
Weechat will generally assume that whatever channel you're in, that's also the server you're operating on. So you can chat away as you wish and issue general commands.<br />
<br />
However, for some commands, you will need to let Weechat know what server you're on.<br />
<br />
Hit Alt+1. This will bring you to your status window. Along the bottom you will see the time, number of channels, the server you're connect to, as well as other channel stuff.<br />
<br />
Press Ctrl+x. If you're connected to multiple servers, the ''server'' section will change, telling you which server Weechat is connect to. So now you can issue commands to that server (such as /nick) without affecting other servers.<br />
<br />
For example, I am currently connected to irc.redbrick.dcu.ie and to irc.starchat.net. If I hit Ctrl-x I can switch to StarChat, and change my nickname there without it affecting Redbrick's IRC.<br />
<br />
== Mobile ==<br />
<br />
weechat has a mobile app you can get from the [https://play.google.com/store/apps/details?id=com.ubergeek42.WeechatAndroid google play store] or from the [https://github.com/ubergeek42/weechat-android github].<br />
Before we set up the app we need to go too weechat on the terminal and type in:<br />
/relay add weechat 1337<br />
then we need to set the password <br />
/set relay.network.password "your-secret-password"<br />
<br />
now on the Phone launch the app and in settings<br />
In connection settings <br />
Relay host: localhost<br />
Relay Port: 1337 (choose your own port) <br />
Relay password: your-secret-password<br />
Connect type: SSH tunnel<br />
then in SSH Tunnel settings<br />
SSH host: redbrick.dcu.ie<br />
SSH username: your username<br />
SSH port: 22<br />
if you have an ssh key add the route to the key on your phone in SSH Private key file and put the passphrase in the SSH password/key passphrase box, if you dont just put your password in there<br />
<br />
== Special commands ==<br />
<br />
=== Keybinds ===<br />
<br />
Keybinds are handy, especially if you have over 10 channels open. I use Alt+<num> to get to channels, but clearly this only works from 1 up to 0 (on a keyboard). So for channels in higher numbers, you can ''bind'' keys: i.e. Alt+q gets me to channel 11; Alt+y gets me to channel 16.<br />
<br />
/key bind meta-q /buffer 11<br />
<br />
"Key" and "bind" are self-explanatory. "Meta" is Weechat's word for Alt (so meta-q is the same as Alt+q). /buffer 11 is the command that's executed once meta-q (Alt-q) is typed.<br />
<br />
You can build up these to meta-w, meta-e, meta-r for buffer 2, buffer 3, buffer 4, etc etc.<br />
<br />
Of course, you can bind any key combo to any weechat command; it's not necessary to make them Alt+<num> commands.<br />
<br />
'''Note:''' Watch out for caps lock if you're keybinding. If you bind Alt+y to a command, Alt+Y won't work (unless you bind that separately). If you find your binds aren't working, check your caps.<br />
<br />
== Cool Things ==<br />
<br />
=== Scripts ===<br />
<br />
If you're using creadak's weechat script you can use the /script command to view, add/remove, and update scripts that do really handy things, if you are using any version pre 0.3.9 you'll want to use the weeget script to manage your scripts. Some really handy scripts include buffers, iset, buffer_autoclose, cron, pybuffer, shell and screen_away.<br />
/script<br />
<br />
=== Spell Checker ===<br />
<br />
Weechat uses a handy aspell plugin to check your spelling. To enable it, either use iset or use<br />
/set aspell.check.enabled on<br />
<br />
Aspell has a few settings which you may find useful<br />
<br />
/set aspell.check.real_time on<br />
/set aspell.check.word_min_length 2<br />
/set aspell.check.default_dict "en"<br />
/set aspell.check.suggestions 3<br />
<br />
Or alternatively if you use iset, search for aspell<br />
<br />
The aspell plugin can also offer suggestions as of 0.4.0 and it can be added as an item to your status bar. The item should be added to weechat.bar.status.items. For instance:<br />
/set weechat.bar.status.items "time |,buffer_number+:buffer_name+(buffer_modes)+ |,buffer_nicklist_count |,hotlist |,[aspell_suggest]<br />
<br />
<br />
=== Triggers ===<br />
<br />
==== Turn any line with "nsfw" in it bright red ====<br />
/trigger addreplace nsfw modifier weechat_print "${tg_notify} && ${tg_message_nocolor} =~ .*nsfw.*" "/(.*)/${tg_prefix}\t${color:red}!NSFW! ${tg_message}"<br />
==== Make urls underlined and blue ====<br />
/trigger addreplace url_color modifier "weechat_print" "${tg_tags} !~ irc_quit" ";[a-z]+://\S+;${color:32}${color:underline}${re:0}${color:-underline}${color:reset};" ""<br />
==== Strip items such as buffer list and nick list from screen on smaller screens ====<br />
/trigger addreplace resize_small_timestamp signal signal_sigwinch "${info:term_width} < 200" "" "/set weechat.look.buffer_time_format """<br />
==== turn off nicklist on smaller screens ====<br />
/trigger addreplace resize_big signal signal_sigwinch "${info:term_width} >= 100" "" "/bar show nicklist"<br />
/trigger addreplace resize_small signal signal_sigwinch "${info:term_width} < 100" "" "/bar hide nicklist"<br />
==== turn off buffer list on small screens ====<br />
/trigger addreplace resize_small_buffer signal signal_sigwinch "${info:term_width} < 100" "" "/bar hide buffer"<br />
/trigger add replace resize_big_buffer signal signal_sigwinch "${info:term_width} >= 100" "" "/bar show buffer"</div>Creadakhttps://wiki.redbrick.dcu.ie/index.php?title=Weechat&diff=10471Weechat2013-03-29T16:02:11Z<p>Creadak: /* Spell Checker */</p>
<hr />
<div>Once upon a time there was BitchX. Then there was Irssi. Now there is Weechat. More and more people are switching over to Weechat from Irssi, probably coz the colours make IRC easier to read and follow. Problem is, for the Irssi user, Weechat may be a tad confusing.<br />
<br />
Weechat documentation can be tricky to follow, so this page is an attempt to make simple those bizarre and abstract commands.<br />
<br />
== Running Weechat ==<br />
<br />
Dregin is a big Weechat fanboi. And as such, he has his own special builds designed for Redbrick. Azazel is the current login machine, dregin has compiled a version of Weechat that runs on azazel:<br />
<br />
/home/associat/d/dregin/root_azazel/bin/weechat-curses<br />
<br />
Copy and paste that into your terminal command line, hit enter, and give yourself a pat on the back.<br />
<br />
== Compiling Weechat ==<br />
<br />
Weechat requires a bit of jiggery pokery before building on azazel using ''make && make install''. Here's how to do it:<br />
<br />
git clone git://git.sv.gnu.org/weechat.git<br />
cd weechat<br />
./autogen.sh<br />
./configure --prefix=$HOME<br />
for f in `ls po/*.po`<br />
do<br />
/usr/bin/msgmerge --update $f po/weechat.pot <br />
done;<br />
make<br />
make install<br />
<br />
Creadak has also written a script that will compile and install weechat to a local directory and then tell the currently running weechat to upgrade itself, so it's perfect for cronjobbing. The script is available from [http://creadak.tk/upgrade-weechat http://creadak.tk/upgrade-weechat] and instructions are at the top of the script.<br />
<br />
== Basic use ==<br />
<br />
=== Connecting to a server and channel ===<br />
<br />
When you hit 'chat' on Redbrick, you start Irssi, you're automatically connected to a server, then you're joined to Redbrick's #lobby. This all happens behind the scenes, and with Weechat, you need to do this manually. Fear not: it's easy.<br />
<br />
When you start Weechat, you won't get connected to a server or channel. To connect to Redbrick's IRC sever, type:<br />
<br />
/connect irc.redbrick.dcu.ie<br />
<br />
Then to join #lobby:<br />
<br />
/join #lobby<br />
<br />
As well as showing you how IRC clients (such as Weechat or Irssi or whatever) connect to stuff, this should also show you how to connect to other servers and channels outside of Redbrick.<br />
<br />
To connect to any server, simply enter /connect <server_address>. You will probably be greeted with various messages and such from that server. To join a channel on that server, just type /join <channel_name>.<br />
<br />
=== Navigation ===<br />
<br />
Like Irssi, you can move between windows/buffers using Alt+<num>. You can also type /buffer <num> (similar to /win <num> in Irssi).<br />
<br />
F5 and F6 move to the predecessing and successing buffer, respectively.<br />
<br />
You can move buffers (chat windows) with /buffer move. In a channel, type:<br />
<br />
/buffer move <num><br />
<br />
(where <num> is any number you want). That channel is now accessible at Alt+<num><br />
<br />
=== Changing between servers ===<br />
<br />
Weechat will generally assume that whatever channel you're in, that's also the server you're operating on. So you can chat away as you wish and issue general commands.<br />
<br />
However, for some commands, you will need to let Weechat know what server you're on.<br />
<br />
Hit Alt+1. This will bring you to your status window. Along the bottom you will see the time, number of channels, the server you're connect to, as well as other channel stuff.<br />
<br />
Press Ctrl+x. If you're connected to multiple servers, the ''server'' section will change, telling you which server Weechat is connect to. So now you can issue commands to that server (such as /nick) without affecting other servers.<br />
<br />
For example, I am currently connected to irc.redbrick.dcu.ie and to irc.starchat.net. If I hit Ctrl-x I can switch to StarChat, and change my nickname there without it affecting Redbrick's IRC.<br />
<br />
== Special commands ==<br />
<br />
=== Keybinds ===<br />
<br />
Keybinds are handy, especially if you have over 10 channels open. I use Alt+<num> to get to channels, but clearly this only works from 1 up to 0 (on a keyboard). So for channels in higher numbers, you can ''bind'' keys: i.e. Alt+q gets me to channel 11; Alt+y gets me to channel 16.<br />
<br />
/key bind meta-q /buffer 11<br />
<br />
"Key" and "bind" are self-explanatory. "Meta" is Weechat's word for Alt (so meta-q is the same as Alt+q). /buffer 11 is the command that's executed once meta-q (Alt-q) is typed.<br />
<br />
You can build up these to meta-w, meta-e, meta-r for buffer 2, buffer 3, buffer 4, etc etc.<br />
<br />
Of course, you can bind any key combo to any weechat command; it's not necessary to make them Alt+<num> commands.<br />
<br />
'''Note:''' Watch out for caps lock if you're keybinding. If you bind Alt+y to a command, Alt+Y won't work (unless you bind that separately). If you find your binds aren't working, check your caps.<br />
<br />
== Cool Things ==<br />
<br />
=== Scripts ===<br />
<br />
If you're using creadak's weechat script you can use the /script command to view, add/remove, and update scripts that do really handy things, if you are using any version pre 0.3.9 you'll want to use the weeget script to manage your scripts. Some really handy scripts include buffers, iset, buffer_autoclose, cron, pybuffer, shell and screen_away.<br />
<br />
=== Spell Checker ===<br />
<br />
Weechat uses a handy aspell plugin to check your spelling. To enable it, either use iset or use<br />
/set aspell.check.enabled on<br />
<br />
Aspell has a few settings which you may find useful<br />
<br />
aspell.check.real_time on<br />
aspell.check.word_min_length 2<br />
aspell.check.default_dict "en"<br />
<br />
Or alternatively if you use iset, search for aspell<br />
<br />
The aspell plugin can also offer suggestions as of 0.4.0 and it can be added as an item to your status bar. The item should be added to weechat.bar.status.items. For instance:<br />
/set weechat.bar.status.items "time |,buffer_number+:buffer_name+(buffer_modes)+ |,buffer_nicklist_count |,hotlist |,[aspell_suggest]<br />
<br />
You should then see something like [http://creadak.tk/scrn.png this]</div>Creadakhttps://wiki.redbrick.dcu.ie/index.php?title=Weechat&diff=10470Weechat2013-03-29T15:59:55Z<p>Creadak: </p>
<hr />
<div>Once upon a time there was BitchX. Then there was Irssi. Now there is Weechat. More and more people are switching over to Weechat from Irssi, probably coz the colours make IRC easier to read and follow. Problem is, for the Irssi user, Weechat may be a tad confusing.<br />
<br />
Weechat documentation can be tricky to follow, so this page is an attempt to make simple those bizarre and abstract commands.<br />
<br />
== Running Weechat ==<br />
<br />
Dregin is a big Weechat fanboi. And as such, he has his own special builds designed for Redbrick. Azazel is the current login machine, dregin has compiled a version of Weechat that runs on azazel:<br />
<br />
/home/associat/d/dregin/root_azazel/bin/weechat-curses<br />
<br />
Copy and paste that into your terminal command line, hit enter, and give yourself a pat on the back.<br />
<br />
== Compiling Weechat ==<br />
<br />
Weechat requires a bit of jiggery pokery before building on azazel using ''make && make install''. Here's how to do it:<br />
<br />
git clone git://git.sv.gnu.org/weechat.git<br />
cd weechat<br />
./autogen.sh<br />
./configure --prefix=$HOME<br />
for f in `ls po/*.po`<br />
do<br />
/usr/bin/msgmerge --update $f po/weechat.pot <br />
done;<br />
make<br />
make install<br />
<br />
Creadak has also written a script that will compile and install weechat to a local directory and then tell the currently running weechat to upgrade itself, so it's perfect for cronjobbing. The script is available from [http://creadak.tk/upgrade-weechat http://creadak.tk/upgrade-weechat] and instructions are at the top of the script.<br />
<br />
== Basic use ==<br />
<br />
=== Connecting to a server and channel ===<br />
<br />
When you hit 'chat' on Redbrick, you start Irssi, you're automatically connected to a server, then you're joined to Redbrick's #lobby. This all happens behind the scenes, and with Weechat, you need to do this manually. Fear not: it's easy.<br />
<br />
When you start Weechat, you won't get connected to a server or channel. To connect to Redbrick's IRC sever, type:<br />
<br />
/connect irc.redbrick.dcu.ie<br />
<br />
Then to join #lobby:<br />
<br />
/join #lobby<br />
<br />
As well as showing you how IRC clients (such as Weechat or Irssi or whatever) connect to stuff, this should also show you how to connect to other servers and channels outside of Redbrick.<br />
<br />
To connect to any server, simply enter /connect <server_address>. You will probably be greeted with various messages and such from that server. To join a channel on that server, just type /join <channel_name>.<br />
<br />
=== Navigation ===<br />
<br />
Like Irssi, you can move between windows/buffers using Alt+<num>. You can also type /buffer <num> (similar to /win <num> in Irssi).<br />
<br />
F5 and F6 move to the predecessing and successing buffer, respectively.<br />
<br />
You can move buffers (chat windows) with /buffer move. In a channel, type:<br />
<br />
/buffer move <num><br />
<br />
(where <num> is any number you want). That channel is now accessible at Alt+<num><br />
<br />
=== Changing between servers ===<br />
<br />
Weechat will generally assume that whatever channel you're in, that's also the server you're operating on. So you can chat away as you wish and issue general commands.<br />
<br />
However, for some commands, you will need to let Weechat know what server you're on.<br />
<br />
Hit Alt+1. This will bring you to your status window. Along the bottom you will see the time, number of channels, the server you're connect to, as well as other channel stuff.<br />
<br />
Press Ctrl+x. If you're connected to multiple servers, the ''server'' section will change, telling you which server Weechat is connect to. So now you can issue commands to that server (such as /nick) without affecting other servers.<br />
<br />
For example, I am currently connected to irc.redbrick.dcu.ie and to irc.starchat.net. If I hit Ctrl-x I can switch to StarChat, and change my nickname there without it affecting Redbrick's IRC.<br />
<br />
== Special commands ==<br />
<br />
=== Keybinds ===<br />
<br />
Keybinds are handy, especially if you have over 10 channels open. I use Alt+<num> to get to channels, but clearly this only works from 1 up to 0 (on a keyboard). So for channels in higher numbers, you can ''bind'' keys: i.e. Alt+q gets me to channel 11; Alt+y gets me to channel 16.<br />
<br />
/key bind meta-q /buffer 11<br />
<br />
"Key" and "bind" are self-explanatory. "Meta" is Weechat's word for Alt (so meta-q is the same as Alt+q). /buffer 11 is the command that's executed once meta-q (Alt-q) is typed.<br />
<br />
You can build up these to meta-w, meta-e, meta-r for buffer 2, buffer 3, buffer 4, etc etc.<br />
<br />
Of course, you can bind any key combo to any weechat command; it's not necessary to make them Alt+<num> commands.<br />
<br />
'''Note:''' Watch out for caps lock if you're keybinding. If you bind Alt+y to a command, Alt+Y won't work (unless you bind that separately). If you find your binds aren't working, check your caps.<br />
<br />
== Cool Things ==<br />
<br />
=== Scripts ===<br />
<br />
If you're using creadak's weechat script you can use the /script command to view, add/remove, and update scripts that do really handy things, if you are using any version pre 0.3.9 you'll want to use the weeget script to manage your scripts. Some really handy scripts include buffers, iset, buffer_autoclose, cron, pybuffer, shell and screen_away.<br />
<br />
=== Spell Checker ===<br />
<br />
Weechat uses a handy aspell plugin to check your spelling. To enable it, either use iset or use<br />
/set aspell.check enabled on<br />
<br />
Aspell has a few settings which you may find useful<br />
<br />
aspell.check.real_time on<br />
aspell.check.word_min_length 2<br />
aspell.check.default_dict "en"<br />
<br />
Or alternatively if you use iset, search for aspell<br />
<br />
The aspell plugin can also offer suggestions as of 0.4.0 and it can be added as an item to your status bar. The item should be added to weechat.bar.status.items. For instance:<br />
/set weechat.bar.status.items "time |,buffer_number+:buffer_name+(buffer_modes)+ |,buffer_nicklist_count |,hotlist |,[aspell_suggest]<br />
<br />
You should then see something like [http://creadak.tk/scrn.png this]</div>Creadakhttps://wiki.redbrick.dcu.ie/index.php?title=Weechat&diff=10469Weechat2013-03-29T13:57:54Z<p>Creadak: </p>
<hr />
<div>Once upon a time there was BitchX. Then there was Irssi. Now there is Weechat. More and more people are switching over to Weechat from Irssi, probably coz the colours make IRC easier to read and follow. Problem is, for the Irssi user, Weechat may be a tad confusing.<br />
<br />
Weechat documentation can be tricky to follow, so this page is an attempt to make simple those bizarre and abstract commands.<br />
<br />
== Running Weechat ==<br />
<br />
Dregin is a big Weechat fanboi. And as such, he has his own special builds designed for Redbrick. Azazel is the current login machine, dregin has compiled a version of Weechat that runs on azazel:<br />
<br />
/home/associat/d/dregin/root_azazel/bin/weechat-curses<br />
<br />
Copy and paste that into your terminal command line, hit enter, and give yourself a pat on the back.<br />
<br />
== Compiling Weechat ==<br />
<br />
Weechat requires a bit of jiggery pokery before building on azazel using ''make && make install''. Here's how to do it:<br />
<br />
git clone git://git.sv.gnu.org/weechat.git<br />
cd weechat<br />
./autogen.sh<br />
./configure --prefix=$HOME<br />
for f in `ls po/*.po`<br />
do<br />
/usr/bin/msgmerge --update $f po/weechat.pot <br />
done;<br />
make<br />
make install<br />
<br />
Creadak has also written a script that will compile and install weechat to a local directory and then tell the currently running weechat to upgrade itself, so it's perfect for cronjobbing. The script is available from [http://creadak.tk/upgrade-weechat http://creadak.tk/upgrade-weechat] and instructions are at the top of the script.<br />
<br />
== Basic use ==<br />
<br />
=== Connecting to a server and channel ===<br />
<br />
When you hit 'chat' on Redbrick, you start Irssi, you're automatically connected to a server, then you're joined to Redbrick's #lobby. This all happens behind the scenes, and with Weechat, you need to do this manually. Fear not: it's easy.<br />
<br />
When you start Weechat, you won't get connected to a server or channel. To connect to Redbrick's IRC sever, type:<br />
<br />
/connect irc.redbrick.dcu.ie<br />
<br />
Then to join #lobby:<br />
<br />
/join #lobby<br />
<br />
As well as showing you how IRC clients (such as Weechat or Irssi or whatever) connect to stuff, this should also show you how to connect to other servers and channels outside of Redbrick.<br />
<br />
To connect to any server, simply enter /connect <server_address>. You will probably be greeted with various messages and such from that server. To join a channel on that server, just type /join <channel_name>.<br />
<br />
=== Navigation ===<br />
<br />
Like Irssi, you can move between windows/buffers using Alt+<num>. You can also type /buffer <num> (similar to /win <num> in Irssi).<br />
<br />
F5 and F6 move to the predecessing and successing buffer, respectively.<br />
<br />
You can move buffers (chat windows) with /buffer move. In a channel, type:<br />
<br />
/buffer move <num><br />
<br />
(where <num> is any number you want). That channel is now accessible at Alt+<num><br />
<br />
=== Changing between servers ===<br />
<br />
Weechat will generally assume that whatever channel you're in, that's also the server you're operating on. So you can chat away as you wish and issue general commands.<br />
<br />
However, for some commands, you will need to let Weechat know what server you're on.<br />
<br />
Hit Alt+1. This will bring you to your status window. Along the bottom you will see the time, number of channels, the server you're connect to, as well as other channel stuff.<br />
<br />
Press Ctrl+x. If you're connected to multiple servers, the ''server'' section will change, telling you which server Weechat is connect to. So now you can issue commands to that server (such as /nick) without affecting other servers.<br />
<br />
For example, I am currently connected to irc.redbrick.dcu.ie and to irc.starchat.net. If I hit Ctrl-x I can switch to StarChat, and change my nickname there without it affecting Redbrick's IRC.<br />
<br />
== Special commands ==<br />
<br />
=== Keybinds ===<br />
<br />
Keybinds are handy, especially if you have over 10 channels open. I use Alt+<num> to get to channels, but clearly this only works from 1 up to 0 (on a keyboard). So for channels in higher numbers, you can ''bind'' keys: i.e. Alt+q gets me to channel 11; Alt+y gets me to channel 16.<br />
<br />
/key bind meta-q /buffer 11<br />
<br />
"Key" and "bind" are self-explanatory. "Meta" is Weechat's word for Alt (so meta-q is the same as Alt+q). /buffer 11 is the command that's executed once meta-q (Alt-q) is typed.<br />
<br />
You can build up these to meta-w, meta-e, meta-r for buffer 2, buffer 3, buffer 4, etc etc.<br />
<br />
Of course, you can bind any key combo to any weechat command; it's not necessary to make them Alt+<num> commands.<br />
<br />
'''Note:''' Watch out for caps lock if you're keybinding. If you bind Alt+y to a command, Alt+Y won't work (unless you bind that separately). If you find your binds aren't working, check your caps.</div>Creadakhttps://wiki.redbrick.dcu.ie/index.php?title=Weechat&diff=10224Weechat2012-04-18T12:39:38Z<p>Creadak: /* Compiling Weechat */</p>
<hr />
<div>Once upon a time there was BitchX. Then there was Irssi. Now there is Weechat. More and more people are switching over to Weechat from Irssi, probably coz the colours make IRC easier to read and follow. Problem is, for the Irssi user, Weechat may be a tad confusing.<br />
<br />
Weechat documentation can be tricky to follow, so this page is an attempt to make simple those bizarre and abstract commands.<br />
<br />
== Running Weechat ==<br />
<br />
Dregin is a big Weechat fanboi. And as such, he has his own special builds designed for Redbrick. Azazel is the current login machine, and like the hero that he is, dregin has compiled a version of Weechat that runs on azazel:<br />
<br />
/home/associat/d/dregin/root_azazel/bin/weechat-curses<br />
<br />
Copy and paste that into your terminal command line, hit enter, and give yourself a pat on the back.<br />
<br />
== Compiling Weechat ==<br />
<br />
Weechat requires a bit of jiggery pokery before building on azazel using ''make && make install''. Here's how to do it:<br />
<br />
git clone git://git.sv.gnu.org/weechat.git<br />
cd weechat<br />
./autogen.sh<br />
./configure --prefix=$HOME/bin --disable-ruby<br />
for f in `ls po/*.po`<br />
do<br />
/usr/bin/msgmerge --update $f po/weechat.pot <br />
done;<br />
make<br />
make install<br />
<br />
Creadak has also written a script that will upgrade weechat, install it to a local directory, and text you that it's upgraded, so it's perfect for cronjobbing. The script is available from [http://creadak.tk/upgrade-weechat http://creadak.tk/upgrade-weechat] and instructions are at the top of the script.<br />
<br />
== Basic use ==<br />
<br />
=== Connecting to a server and channel ===<br />
<br />
When you hit 'chat' on Redbrick, you start Irssi, you're automatically connected to a server, then you're joined to Redbrick's #lobby. This all happens behind the scenes, and with Weechat, you need to do this manually. Fear not: it's easy.<br />
<br />
When you start Weechat, you won't get connected to a server or channel. To connect to Redbrick's IRC sever, type:<br />
<br />
/connect irc.redbrick.dcu.ie<br />
<br />
Then to join #lobby:<br />
<br />
/join #lobby<br />
<br />
As well as showing you how IRC clients (such as Weechat or Irssi or whatever) connect to stuff, this should also show you how to connect to other servers and channels outside of Redbrick.<br />
<br />
To connect to any server, simply enter /connect <server_address>. You will probably be greeted with various messages and such from that server. To join a channel on that server, just type /join <channel_name>.<br />
<br />
=== Navigation ===<br />
<br />
Like Irssi, you can move between windows/buffers using Alt+<num>. You can also type /buffer <num> (similar to /win <num> in Irssi).<br />
<br />
F5 and F6 move to the predecessing and successing buffer, respectively.<br />
<br />
You can move buffers (chat windows) with /buffer move. In a channel, type:<br />
<br />
/buffer move <num><br />
<br />
(where <num> is any number you want). That channel is now accessible at Alt+<num><br />
<br />
=== Changing between servers ===<br />
<br />
Weechat will generally assume that whatever channel you're in, that's also the server you're operating on. So you can chat away as you wish and issue general commands.<br />
<br />
However, for some commands, you will need to let Weechat know what server you're on.<br />
<br />
Hit Alt+1. This will bring you to your status window. Along the bottom you will see the time, number of channels, the server you're connect to, as well as other channel stuff.<br />
<br />
Press Ctrl+x. If you're connected to multiple servers, the ''server'' section will change, telling you which server Weechat is connect to. So now you can issue commands to that server (such as /nick) without affecting other servers.<br />
<br />
For example, I am currently connected to irc.redbrick.dcu.ie and to irc.starchat.net. If I hit Ctrl-x I can switch to StarChat, and change my nickname there without it affecting Redbrick's IRC.<br />
<br />
== Special commands ==<br />
<br />
=== Keybinds ===<br />
<br />
Keybinds are handy, especially if you have over 10 channels open. I use Alt+<num> to get to channels, but clearly this only works from 1 up to 0 (on a keyboard). So for channels in higher numbers, you can ''bind'' keys: i.e. Alt+q gets me to channel 11; Alt+y gets me to channel 16.<br />
<br />
/key bind meta-q /buffer 11<br />
<br />
"Key" and "bind" are self-explanatory. "Meta" is Weechat's word for Alt (so meta-q is the same as Alt+q). /buffer 11 is the command that's executed once meta-q (Alt-q) is typed.<br />
<br />
You can build up these to meta-w, meta-e, meta-r for buffer 2, buffer 3, buffer 4, etc etc.<br />
<br />
Of course, you can bind any key combo to any weechat command; it's not necessary to make them Alt+<num> commands.<br />
<br />
'''Note:''' Watch out for caps lock if you're keybinding. If you bind Alt+y to a command, Alt+Y won't work (unless you bind that separately). If you find your binds aren't working, check your caps.</div>Creadakhttps://wiki.redbrick.dcu.ie/index.php?title=Weechat&diff=10223Weechat2012-04-18T12:18:55Z<p>Creadak: /* Compiling Weechat */</p>
<hr />
<div>Once upon a time there was BitchX. Then there was Irssi. Now there is Weechat. More and more people are switching over to Weechat from Irssi, probably coz the colours make IRC easier to read and follow. Problem is, for the Irssi user, Weechat may be a tad confusing.<br />
<br />
Weechat documentation can be tricky to follow, so this page is an attempt to make simple those bizarre and abstract commands.<br />
<br />
== Running Weechat ==<br />
<br />
Dregin is a big Weechat fanboi. And as such, he has his own special builds designed for Redbrick. Azazel is the current login machine, and like the hero that he is, dregin has compiled a version of Weechat that runs on azazel:<br />
<br />
/home/associat/d/dregin/root_azazel/bin/weechat-curses<br />
<br />
Copy and paste that into your terminal command line, hit enter, and give yourself a pat on the back.<br />
<br />
== Compiling Weechat ==<br />
<br />
Weechat requires a bit of jiggery pokery before building on azazel using ''make && make install''. Here's how to do it:<br />
<br />
git clone git://git.sv.gnu.org/weechat.git<br />
cd weechat<br />
./autogen.sh<br />
./configure --prefix=$HOME/bin --disable-ruby<br />
for f in `ls po/*.po`<br />
do<br />
/usr/bin/msgmerge --update $f po/weechat.pot <br />
done;<br />
make<br />
make install<br />
<br />
== Basic use ==<br />
<br />
=== Connecting to a server and channel ===<br />
<br />
When you hit 'chat' on Redbrick, you start Irssi, you're automatically connected to a server, then you're joined to Redbrick's #lobby. This all happens behind the scenes, and with Weechat, you need to do this manually. Fear not: it's easy.<br />
<br />
When you start Weechat, you won't get connected to a server or channel. To connect to Redbrick's IRC sever, type:<br />
<br />
/connect irc.redbrick.dcu.ie<br />
<br />
Then to join #lobby:<br />
<br />
/join #lobby<br />
<br />
As well as showing you how IRC clients (such as Weechat or Irssi or whatever) connect to stuff, this should also show you how to connect to other servers and channels outside of Redbrick.<br />
<br />
To connect to any server, simply enter /connect <server_address>. You will probably be greeted with various messages and such from that server. To join a channel on that server, just type /join <channel_name>.<br />
<br />
=== Navigation ===<br />
<br />
Like Irssi, you can move between windows/buffers using Alt+<num>. You can also type /buffer <num> (similar to /win <num> in Irssi).<br />
<br />
F5 and F6 move to the predecessing and successing buffer, respectively.<br />
<br />
You can move buffers (chat windows) with /buffer move. In a channel, type:<br />
<br />
/buffer move <num><br />
<br />
(where <num> is any number you want). That channel is now accessible at Alt+<num><br />
<br />
=== Changing between servers ===<br />
<br />
Weechat will generally assume that whatever channel you're in, that's also the server you're operating on. So you can chat away as you wish and issue general commands.<br />
<br />
However, for some commands, you will need to let Weechat know what server you're on.<br />
<br />
Hit Alt+1. This will bring you to your status window. Along the bottom you will see the time, number of channels, the server you're connect to, as well as other channel stuff.<br />
<br />
Press Ctrl+x. If you're connected to multiple servers, the ''server'' section will change, telling you which server Weechat is connect to. So now you can issue commands to that server (such as /nick) without affecting other servers.<br />
<br />
For example, I am currently connected to irc.redbrick.dcu.ie and to irc.starchat.net. If I hit Ctrl-x I can switch to StarChat, and change my nickname there without it affecting Redbrick's IRC.<br />
<br />
== Special commands ==<br />
<br />
=== Keybinds ===<br />
<br />
Keybinds are handy, especially if you have over 10 channels open. I use Alt+<num> to get to channels, but clearly this only works from 1 up to 0 (on a keyboard). So for channels in higher numbers, you can ''bind'' keys: i.e. Alt+q gets me to channel 11; Alt+y gets me to channel 16.<br />
<br />
/key bind meta-q /buffer 11<br />
<br />
"Key" and "bind" are self-explanatory. "Meta" is Weechat's word for Alt (so meta-q is the same as Alt+q). /buffer 11 is the command that's executed once meta-q (Alt-q) is typed.<br />
<br />
You can build up these to meta-w, meta-e, meta-r for buffer 2, buffer 3, buffer 4, etc etc.<br />
<br />
Of course, you can bind any key combo to any weechat command; it's not necessary to make them Alt+<num> commands.<br />
<br />
'''Note:''' Watch out for caps lock if you're keybinding. If you bind Alt+y to a command, Alt+Y won't work (unless you bind that separately). If you find your binds aren't working, check your caps.</div>Creadakhttps://wiki.redbrick.dcu.ie/index.php?title=Weechat&diff=10222Weechat2012-04-18T12:05:44Z<p>Creadak: /* Compiling Weechat */</p>
<hr />
<div>Once upon a time there was BitchX. Then there was Irssi. Now there is Weechat. More and more people are switching over to Weechat from Irssi, probably coz the colours make IRC easier to read and follow. Problem is, for the Irssi user, Weechat may be a tad confusing.<br />
<br />
Weechat documentation can be tricky to follow, so this page is an attempt to make simple those bizarre and abstract commands.<br />
<br />
== Running Weechat ==<br />
<br />
Dregin is a big Weechat fanboi. And as such, he has his own special builds designed for Redbrick. Azazel is the current login machine, and like the hero that he is, dregin has compiled a version of Weechat that runs on azazel:<br />
<br />
/home/associat/d/dregin/root_azazel/bin/weechat-curses<br />
<br />
Copy and paste that into your terminal command line, hit enter, and give yourself a pat on the back.<br />
<br />
== Compiling Weechat ==<br />
<br />
Weechat requires a bit of jiggery pokery before building on azazel using ''make && make install''. Here's how to do it:<br />
<br />
git clone git://git.sv.gnu.org/weechat.git<br />
cd weechat<br />
./autogen.sh<br />
./configure --prefix=$HOME/bin --disable-ruby<br />
for f in `ls po/*.po`<br />
do<br />
/usr/bin/msgmerge --update $f po/weechat.pot <br />
done;<br />
make<br />
make install<br />
<br />
<br />
Creadak has also written a script that will upgrade weechat, install it to a local directory, and text you that it's upgraded, so it's perfect for cronjobbing. The script is available from [http://creadak.tk/upgrade-weechat http://creadak.tk/upgrade-weechat] and instructions are at the top of the script<br />
<br />
== Basic use ==<br />
<br />
=== Connecting to a server and channel ===<br />
<br />
When you hit 'chat' on Redbrick, you start Irssi, you're automatically connected to a server, then you're joined to Redbrick's #lobby. This all happens behind the scenes, and with Weechat, you need to do this manually. Fear not: it's easy.<br />
<br />
When you start Weechat, you won't get connected to a server or channel. To connect to Redbrick's IRC sever, type:<br />
<br />
/connect irc.redbrick.dcu.ie<br />
<br />
Then to join #lobby:<br />
<br />
/join #lobby<br />
<br />
As well as showing you how IRC clients (such as Weechat or Irssi or whatever) connect to stuff, this should also show you how to connect to other servers and channels outside of Redbrick.<br />
<br />
To connect to any server, simply enter /connect <server_address>. You will probably be greeted with various messages and such from that server. To join a channel on that server, just type /join <channel_name>.<br />
<br />
=== Navigation ===<br />
<br />
Like Irssi, you can move between windows/buffers using Alt+<num>. You can also type /buffer <num> (similar to /win <num> in Irssi).<br />
<br />
F5 and F6 move to the predecessing and successing buffer, respectively.<br />
<br />
You can move buffers (chat windows) with /buffer move. In a channel, type:<br />
<br />
/buffer move <num><br />
<br />
(where <num> is any number you want). That channel is now accessible at Alt+<num><br />
<br />
=== Changing between servers ===<br />
<br />
Weechat will generally assume that whatever channel you're in, that's also the server you're operating on. So you can chat away as you wish and issue general commands.<br />
<br />
However, for some commands, you will need to let Weechat know what server you're on.<br />
<br />
Hit Alt+1. This will bring you to your status window. Along the bottom you will see the time, number of channels, the server you're connect to, as well as other channel stuff.<br />
<br />
Press Ctrl+x. If you're connected to multiple servers, the ''server'' section will change, telling you which server Weechat is connect to. So now you can issue commands to that server (such as /nick) without affecting other servers.<br />
<br />
For example, I am currently connected to irc.redbrick.dcu.ie and to irc.starchat.net. If I hit Ctrl-x I can switch to StarChat, and change my nickname there without it affecting Redbrick's IRC.<br />
<br />
== Special commands ==<br />
<br />
=== Keybinds ===<br />
<br />
Keybinds are handy, especially if you have over 10 channels open. I use Alt+<num> to get to channels, but clearly this only works from 1 up to 0 (on a keyboard). So for channels in higher numbers, you can ''bind'' keys: i.e. Alt+q gets me to channel 11; Alt+y gets me to channel 16.<br />
<br />
/key bind meta-q /buffer 11<br />
<br />
"Key" and "bind" are self-explanatory. "Meta" is Weechat's word for Alt (so meta-q is the same as Alt+q). /buffer 11 is the command that's executed once meta-q (Alt-q) is typed.<br />
<br />
You can build up these to meta-w, meta-e, meta-r for buffer 2, buffer 3, buffer 4, etc etc.<br />
<br />
Of course, you can bind any key combo to any weechat command; it's not necessary to make them Alt+<num> commands.<br />
<br />
'''Note:''' Watch out for caps lock if you're keybinding. If you bind Alt+y to a command, Alt+Y won't work (unless you bind that separately). If you find your binds aren't working, check your caps.</div>Creadakhttps://wiki.redbrick.dcu.ie/index.php?title=Screen&diff=10095Screen2011-10-21T18:25:20Z<p>Creadak: /* Reattaching Screen Automatically */ talked about ~/.zlogin and ~/.bash_login</p>
<hr />
<div>== Basics ==<br />
'''Screen''' usually does not exist; this <s>is the committee's</s> was a former committee's general position on screen due to the disastrous and/or hilarious situations which often result from new members' attempts to get it working. However, for the purpose of this tutorial, screen '''does''' exist, and this is how you use it. (Blame coconut for this defiance.)<br />
<br />
=== Omg, what's screen? ===<br />
<br />
Screen is most commonly known as "that thing that lets you stay logged in to chat when you log out of RedBrick". It's a terminal multiplexer, which allows you to log into multiple terminal sessions from one terminal window and keeps them open when you go away to bed or whatever it is you do with your time.<br />
<br />
=== Opening ===<br />
Type "screen" at the prompt like this:<br />
<br />
<br />
[[Image:screen1.jpg]]<br />
<br />
<br />
This will open a new screen session. First you'll see the screen startup message, which gives a little info on the program.<br />
<br />
<br />
[[Image:screen2.jpg]]<br />
<br />
<br />
Just hit space/return as it says and you'll be running screen. You won't notice anything immediately different once running screen, instead, you'll be back at the same old terminal. Now, however, you have access to a large variety of commands and features that you didn't before.<br />
<br />
== Screen commands ==<br />
=== Ctrl-a commands ===<br />
Nearly all of screen's commands are used via the ctrl-a key combination. First, you press the ctrl and a keys together, then release. Next, press the key you want to run a command. These commands can be a little awkward and difficult to remember at first, but you'll soon get the hang of it. In this tutorial, the commands will be shown as ctrl-a and then a letter, with the following letter being associated with a command.<br />
<br />
=== Creating a new window ===<br />
When you start screen, it presents you with the normal single window terminal you're used to. You can, however, create many more and run them all within the one screen session. The following command will create another window for you:<br />
ctrl-a c<br />
<br />
Just hit ctrl and a together, then release them and hit c. This keybinding will open a new window (window 2) inside screen. Now you'll have two windows to use, so you'll have to learn how to use the ctrl-a commands to switch between them.<br />
<br />
=== Switching windows===<br />
Once you have more than one window open, you can switch between them using some of the following commands:<br />
ctrl-a n<br />
This command will switch you over to the next window.<br />
<br />
ctrl-a p<br />
This one will bring you back to the previous window.<br />
<br />
ctrl-a a<br />
This will switch between the last two windows that you've been using.<br />
<br />
ctrl-a window_number<br />
Using this command, you can specify exactly which window you want to jump to by hitting ctrl and a, then the number on the keyboard of your desired window. This is pretty useful for when you have a lot of windows open in screen.<br />
<br />
=== Naming your windows ===<br />
You can give each of your windows its own name too for convenience by using this command:<br />
ctrl-a A<br />
<br />
This one might seem confusing first as the A is a capital letter in this case, but all you need to do is hit ctrl and a together and release as before, then hold shift and press a to get the capital. After you run it, you'll see a white bar appear at the bottom of your window, where you can change the name of your screen to whatever you like. In this case, the window has just been renamed to "chat".<br />
<br />
<br />
[[Image:screen3.jpg]]<br />
<br />
<br />
After you've named a few windows, you can try this command:<br />
ctrl-a "<br />
<br />
Yup, even quotation marks can be used in screen commands. So as before you do ctrl-a, then hold shift and hit the 2 key to get the " :) This will bring up a convenient list of all your windows with their names.<br />
<br />
<br />
[[Image:screen4.jpg]]<br />
<br />
<br />
From this window you can view and go to any of your windows. The flags on the right indicate whether your window is logged in or not with $ symbol.<br />
<br />
=== Detaching and reattaching screen ===<br />
<br />
One of the most popular features of screen is that it can keep you logged in even when you're offline. This means you can leave programs running or even stay on IRC even when you're not online. When you "minimise" screen or make it invisible, it is called detaching it.<br />
<br />
To do this, you just detach from screen instead of exiting it. To detach from screen without exiting, use the following command:<br />
ctrl-a d<br />
<br />
You'll then be returned to the prompt with a message telling you screen has been detached, like so:<br />
<br />
<br />
[[Image:screen5.jpg]]<br />
<br />
<br />
Later, you'll come back online and want to reattach to your screen session. When you "maximise" screen or bring it back onto your terminal, this is known as attaching. To reattach a detached screen, use this command at the prompt:<br />
screen -dr<br />
<br />
The -d will detach any attached screens and -r will reattach your screen.<br />
<br />
If you have more than one screen session available, you will need to specify the screen id you wish to open. You'll be given a list of the currently available screens, so then you type:<br />
<br />
screen -r<br />
<br />
followed by the id listed above of the screen you want to reattach to.<br />
<br />
=== Start and stop signals ===<br />
Quite often it happens someone may end up using the stop signal command in screen by mistake. This command is:<br />
<br />
ctrl-a s<br />
<br />
and you should probably avoid using it! But as the s key is beside the a key, people will occasionally run this command by accident without knowing it. As this is a stop signal, it has the unfortunate side effect of freezing up your window :( Worry not however, for to fix it, all you need to do is use the start signal again to bring it back from the dead:<br />
<br />
ctrl-a q<br />
<br />
This should have you back in action very shortly. However, if your screen is frozen and you can't figure out why, try asking a member of [[Helpdesk]] and they should know the answer :)<br />
<br />
=== Killing screen while attached ===<br />
Often enough new members (and often, experienced people) will make mistakes with screen that they can't fix. To kill screen altogether and start over, use:<br />
ctrl-a \<br />
<br />
Or, if you just want to kill a single window in screen, use:<br />
<br />
ctrl-a k<br />
<br />
or even just type "exit" at the prompt.<br />
<br />
=== Killing screen while detached ===<br />
<br />
'''Warning''': using the ''kill'' command to do anything can be very dangerous if you don't know what you're doing. If you're unsure, reattach the screen you want to kill and follow the instructions above.<br />
<br />
If you have more than one screen session and you want to kill one of them, type "screen -dr" to get a list of the available screens (from the terminal which appears when you first log in to RedBrick). Note the '''number''' (also known as a process id, or pid) at the beginning of each screen name. This is the process number. Ensure you know which screen session is which.<br />
<br />
To terminate a session, use this command (''pid'' is the number of the session you want to kill)<br />
<br />
kill ''pid''<br />
<br />
This will send the signal SIGTERM to the process, requesting its termination.<br />
<br />
If that fails and you want lil_cain to start complaining<br />
<br />
kill -9 ''pid''<br />
<br />
This will send the signal SIGKILL to the process, terminating it immediately and with lots of blood.<br />
<br />
Then, to then get rid of the dead screen session, type<br />
<br />
screen -wipe<br />
<br />
== Screen Configuration ==<br />
<br />
So after you've set up screen and have gotten used to it, you will probably want to configure it a little bit and the way to do this is by creating a ~/.screenrc<br />
<br />
To do this just<br />
nano ~/.screenrc<br />
<br />
Here's an example of a .screenrc that you may want to use:<br />
<br />
hardstatus alwayslastline<br />
hardstatus string '%{= kg}[ %{G}%H %{g}][%= %{= kw}%?%-Lw%?%{=b kR}(%{W}%n*%f %t%?(%u)%?%{=b kR})%{= kw}%?%+Lw%? %?%= %{g}][%{Y}%l%{g}]%{=b C}[ %d %M %c ]%{W}'<br />
deflogin off<br />
startup_message off<br />
screen -t irc 1 irssi<br />
screen -t Email/slrn 2 mutt -Z<br />
screen -t heys -L -l 3<br />
<br />
Basically this only really does two things, sets a hardstatus (basically a line that contains some information) and makes it display only on the bottom line and also creates a few new windows.<br />
<br />
The new windows created are given names and optionally a number or command (or both).<br />
<br />
screen -t irc q irssi<br />
<br />
This will create screen window 1, give it the title "irc" and then run irssi when you start screen.<br />
<br />
deflogin off<br />
<br />
This sets windows logged out by default, which means that you won't have to "mesg n" windows to not receive heys<br />
<br />
startup_message off<br />
<br />
This turns the startup message thats displayed when you start a new screen session off.<br />
<br />
screen -t heys -L -l 3<br />
<br />
Will create a logged in window specifically for heys. Handy.<br />
<br />
All this makes it very simple to restart all your processes if Redbrick ever crashes.<br />
<br />
With the above configuration file it will look something like this:<br />
<br />
[[Image:screenrc.jpg]]<br />
<br />
=== Reattaching Screen Automatically ===<br />
<br />
So, you've made your screen, configured it, and you happily type screen -dr '''every time''' you login to RedBrick. But wouldn't it be nice if whenever you login your screen would reattach '''itself'''??? It can be done :D<br />
<br />
Simply use your favorite text editor to edit your ~/.zlogin if you're using zsh (if you haven't changed your login shell, this is the one you're using) or ~/.bash_login if you're using bash and put the following in it<br />
<br />
screen -dr<br />
<br />
That should do the job. It'll try to reattach a screen whenever you login on any redbrick server<br />
<br />
* Please note, if this in fact, does not work, you can edit it out by using winSCP and editing the file using it.<br />
<br />
== Useful links ==<br />
If you'd like to learn more about the program, a long list of screen commands can be found here: http://www.linuxdevcenter.com/linux/cmd/cmd.csp?path=s/screen<br />
<br />
Help edited a screenrc: http://www.debian-administration.org/articles/560<br />
<br />
A starting guide to screen: http://magazine.redhat.com/2007/09/27/a-guide-to-gnu-screen/<br />
<br />
The Gentoo wiki article on screen (quite in depth) : http://www.gentoo-wiki.info/Screen<br />
<br />
[[Category:Helpdesk]]</div>Creadakhttps://wiki.redbrick.dcu.ie/index.php?title=Games&diff=10037Games2011-08-30T07:55:29Z<p>Creadak: </p>
<hr />
<div>Games available on RedBrick ([[minerva]]). These are all located in: /usr/games<br />
<br />
To see what a game is about, execute the "man" command followed by the game's name. For example: man nethack<br />
<br />
RedBrick also hosts other games on behalf of the DCU Games Society on their server [[blinky]].<br />
<br />
==abe==<br />
Does Not Work. ~ carri@minerva<br />
==adventure==<br />
I killed this. I got bored. <br />
==airstrike==<br />
Does Not Work. ~ carri@minerva<br />
==arithmetic==<br />
If I was 6 this would be awesome to practise maths. -_- It's addition and subtraction.<br />
==atc==<br />
Really easy to make the top players list.<br />
==backgammon==<br />
===teachgammon===<br />
Teaches you how to play backgammon. Useful, because I don't have a clue either.<br />
==banner==<br />
Makes things into a banner.. Like figlet but with... #<br />
==battlestar==<br />
Could do with a "how to guide" <br />
==bcd==<br />
"The bcd, ppt and morse commands read the given input and reformat it in the form of punched cards, paper tape or morse code respectively. Acceptable input are command line arguments or the standard input." Love the man page.<br />
==boggle==<br />
Boggle! <br />
==caesar==<br />
"The caesar utility attempts to decrypt caesar ciphers using English letter frequency statistics. caesar reads from the standard input and writes to the standard output."<br />
==canfield==<br />
The solitaire card game, canfield.<br />
===cfscores===<br />
Shows the database of high scores for canfield.<br />
==countmail==<br />
The countmail program counts your mail and tells you about it rather obnoxiously. If it doesn't work for you, e-mail admins@redbrick.dcu.ie and annoy them.<br />
==cribbage==<br />
Card game without cards. <br />
==dab==<br />
I like this. It's like a game called dots I used to play. The aim to fill in as many boxes you can with your name. You play against the computer.<br />
==dopewars==<br />
<br />
[[Image:400px-Stash3.jpg]]<br />
<br />
In this game, you play a drug dealer, travelling between New York's five boroughs. You make money by buying selling a plethora of mind-altering substances. <br />
It's all the fun of drug dealing '''without''' the legal repercussions!<br />
<br />
==eboard==<br />
===eboard-addtheme===<br />
==fortune==<br />
==gnuchess==<br />
===gnuchessx===<br />
Obsolete. Calls ''gnuchess xboard''<br />
<br />
==gnugo==<br />
==nethack==<br />
<br />
NetHack is an Advanced Dungeons and Dragons simulator. (Read: NetHack is a game for when you have so few friends that you can't even muster up four people to pretend to be elves in some stupid dungeon). I like it though. <br />
<br />
Players: <br />
* [[User:gw|gw]] <br />
* [[User:Bunbun|bunbun]]<br />
* [[User:fun|fun]]<br />
* [[User:creadak|creadak]]<br />
<br />
The version of Nethack on Redbrick is based on the Ubuntu version, which contains, among others, the [http://nethackwiki.com/wiki/Menucolors menucolors] and [http://nethackwiki.com/wiki/Hpmon hpmon] patches.<br />
We also patch it with the [http://bilious.homelinux.org/?40 dumplog] patch, which records a lot of info about the game when you die.<br />
<br />
A configuration file for the game (which takes advantage of hpmon and menucolors and makes it prettier with UTF-8 shit, among other things) is available [http://www.redbrick.dcu.ie/~bunbun/.nethackrc here], just put it in ~/.nethackrc.<br />
If you'd like to keep all of the dumpfiles created when you die, instead of just the most recent, add the following alias to your shell rc file (most likely ~/.zshrc)<br />
alias nethack="nethack; [ ! -e \"/var/games/nethack/save/$USERID$USERNAME.gz\" ] && cp /var/games/nethack/dumps/$USERNAME.lastgame.txt ~/dumps/\`date +%Y-%m-%d-%H:%M:%S\`.txt"<br />
Make sure to change $USERID and $USERNAME to your userid (gotten with the `id` command) and your username. This should save it each time you die to ~/dumps/YEAR-MM-DD-HH:MM:SS.txt, though in some cases it creates duplicates (If you quit before choosing your role/race/gender/alignment that I know of).<br />
<br />
==netris==<br />
<br />
Networked multiplayer version of tetris. You can play with anyone logged into RedBrick.<br />
<br />
Players: [[User:lil_cain|lil_cain]] [[User:phaxx|phaxx]] [[User:train|train]]<br />
<br />
===netris-sample-robot===<br />
<br />
==number==<br />
==worm==<br />
<br />
A clone of the game "Snake" which was created in the 1970s but popularised by the Nokia 3210 mobile phone (especially in Irish secondary schools!)<br />
<br />
==worms==<br />
==wtf==<br />
<br />
Not really a game per se. Decodes [[Acronyms|acronyms]].</div>Creadakhttps://wiki.redbrick.dcu.ie/index.php?title=Dropbox&diff=9991Dropbox2011-05-19T14:18:25Z<p>Creadak: </p>
<hr />
<div>== What is Dropbox? ==<br />
<br />
Dropbox is an web based file hosting service. It creates a folder in your home directory (usually ~/Dropbox) and monitors that folder and keeps it synced to the web and to other computers that you have installed Dropbox on. It's also a fairly handy way to upload files between your computer and RedBrick as it doesn't need your account details, it just requires that you link the client with your Dropbox account<br />
<br />
== Installing Dropbox on your RedBrick account ==<br />
<br />
Dropbox can't be installed on RedBrick in the traditional way as it is a plugin for nautilus which isn't going to be installed on RedBrick any time soon. Instead, we'll download the Command Line Interface version.<br />
<br />
=== Pre-installation ===<br />
<br />
Dropbox doesn't seem to run on [[minerva]], it works fine on [[morpheus]] and [[azazel]], [[carbon]] is untested. So ssh to one of these machines. Now, despite dropbox saying that the command line version uses the http_proxy variable, it actually uses the HTTP_PROXY variable, so lets set it correctly with:<br />
<br />
export HTTP_PROXY="http://proxy.dcu.ie:3128"<br />
<br />
And now you're ready to start.<br />
<br />
=== Installation === <br />
<br />
Grab the program from the dropbox website with:<br />
<br />
wget -O dropbox.tar.gz "http://www.dropbox.com/download/?plat=lnx.x86_64"<br />
<br />
Extract it to ~/.dropbox-dist with:<br />
<br />
tar -xvzf dropbox.tar.gz<br />
<br />
Next, create a folder in your home directory called bin:<br />
<br />
mkdir ~/bin<br />
<br />
There's something nice about this folder, if you type echo $PATH into your shell, you'll notice that that folder has been added to the start of your $PATH. Your $PATH is the list of folders that your shell looks through (in order) when it tries to execute a program. For example, if in your ~/bin you have a program called ls and try to execute ls, your shell will execute ~/bin/ls, as opposed to the systems ls. This is the folder where we will install the Dropbox CLI. Execute the following:<br />
<br />
wget -O ~/bin/dropbox "http://www.dropbox.com/download?dl=packages/dropbox.py"<br />
<br />
And make the program executable:<br />
<br />
chmod 700 ~/bin/dropbox<br />
<br />
Next, we'll start the dropbox daemon:<br />
<br />
~/.dropbox-dist/dropboxd<br />
<br />
This will give you output similar to the screen shot below. Follow the link and sign into your account to link your account to the client. <br />
<br />
[[Image:Dropboxd.png]]<br />
<br />
After you've done this, press ctrl+c to kill it, as we're going to use the dropbox program we downloaded earlier to interact with the daemon from now on. Notice how you have a shiny new ~/Dropbox folder? Dropbox is now ready to go.<br />
<br />
=== Using the dropbox script ===<br />
<br />
If you use a shell that autocorrects, you may want to turn it off in the config file, as when in your home directory, the Dropbox folder may confuse it, when you actually meant the dropbox program in your ~/bin. To do this in zsh put the following in your ~/.zshrc<br />
<br />
alias dropbox="nocorrect dropbox"<br />
<br />
and then reload your config<br />
<br />
source ~/.zshrc<br />
<br />
To start the dropbox daemon with the dropbox program type:<br />
<br />
dropbox start<br />
<br />
Notice how with this we get our terminal back? The dropbox script daemonises the dropbox daemon so that you can continue doing things while it runs in the background. Handy, no? Other useful dropbox commands are:<br />
<br />
dropbox status - See if the daemon is running or not<br />
dropbox stop - Stop the dropbox daemon<br />
dropbox autostart - Start the dropbox daemon as soon as you login.<br />
dropbox help - A list of all the commands<br />
<br />
== Extending Dropbox ==<br />
<br />
There are some pretty nice extensions for Dropbox, see http://wiki.dropbox.com/DropboxAddons?action=recall&rev=182 for a list of some of them. They all come with their own documentation, so it shouldn't be too hard to use them.<br />
<br />
== Your Dropbox and your RedBrick Quota ==<br />
<br />
Dropbox saves copies of your files to each copmuter it is linked to, so if you use your 2GB on dropbox you will need 2GB of space on your RedBrick account, if you need more space, contact the admins.</div>Creadakhttps://wiki.redbrick.dcu.ie/index.php?title=Mercurial&diff=9956Mercurial2011-04-12T17:32:55Z<p>Creadak: </p>
<hr />
<div>Mercurial is a version control system, like [[svn|subversion]] in that it manages changes in your code, but different in that it's designed to be distributed. Git and bazaar are also distributed version control systems. Mercurial is also written in python, which is [http://xkcd.com/353/ cool]. It's built in web interface is also excellent.<br />
<br />
==Setting Up On RedBrick ==<br />
<br />
All the setup needs to be done on murphy, since that's the webserver. After that, you can access your code from anywhere.<br />
<br />
First, we need to setup the repo that will contain the code <br />
receive@murphy (~) % hg init hgrepo<br />
<br />
Next, we setup the web access...<br />
<br />
=== Step 1 - Create the directory, and copy in the python cgi ===<br />
receive@murphy (~) % cd ~/public_html<br />
receive@murphy (~/public_html) % mkdir hg<br />
receive@murphy (~/public_html) % chmod 711 hg<br />
receive@murphy (~/public_html) % cd hg<br />
receive@murphy (~/public_html/hg) % cp /usr/share/doc/mercurial-common/examples/hgweb.cgi ./index.cgi<br />
receive@murphy (~/public_html/hg) % chmod 755 index.cgi<br />
<br />
=== Step 2 - Set the repo location ===<br />
<br />
Open the index.cgi in nano (or any other text editor) and on the second to last line replace /YOUR/HOME/DIR/YOUR/REPO with the location of the repo you created. For me, this is /home/member/r/receive/hgrepo - the location will depend on where your home directory is. Optionally, replace "repository name" with something cooler.<br />
<br />
=== Step 3 - Set Up htaccess ===<br />
<br />
receive@murphy (~/public_html/hg) % touch .htaccess<br />
receive@murphy (~/public_html/hg) % chmod 644 .htaccess<br />
<br />
Open the htaccess file in a text editor. <br />
<br />
<pre><br />
##################################<br />
# Force all access to over https #<br />
##################################<br />
<br />
RewriteCond %{SERVER_PORT} 80<br />
RewriteRule (.*) https://www.redbrick.dcu.ie/~receive/hg<br />
<br />
<br />
###################################<br />
# Options for rewriting hg access #<br />
###################################<br />
<br />
RewriteCond %{SERVER_PORT} 443<br />
#write base depending on where the base url lives<br />
RewriteBase /~receive/hg<br />
# Send requests for files that exist to those files.<br />
RewriteCond %{REQUEST_FILENAME} !-f<br />
# Send requests for directories that exist to those directories.<br />
RewriteCond %{REQUEST_FILENAME} !-d<br />
# Send requests to hgwebdir.cgi, appending the rest of url.<br />
RewriteRule (.*) index.cgi/$1 [QSA,L]<br />
<br />
################################<br />
# Options for password control #<br />
################################<br />
<br />
AuthType Basic<br />
AuthName "My Mercurial Repo"<br />
AuthUserFile /home/member/r/receive/.hgpasswd<br />
Require valid-user<br />
</pre><br />
<br />
You can use this htaccess file as a sample, but you'll need to make a few changes. The rewrite base should be set to the location on the webserver you created the hg directory. If you've been following the same example names I used it will be ~username/hg<br />
<br />
Also, you'll need to set the location you're going to use for your htpasswd file. <br />
<br />
=== Step 4: Create the password file ===<br />
<br />
receive@murphy (~/public_html/hg) % htpasswd -c /home/member/r/receive/.hgpasswd receive<br />
<br />
This will prompt you to enter your new password twice.<br />
<br />
receive@murphy (~/public_html/hg) % chmod 644 /home/member/r/receive/.hgpasswd<br />
<br />
<br />
== Using LDAP instead of the password file ==<br />
<br />
In the .htaccess you created earlier replace the Options for password control with the following:<br />
<br />
<pre><br />
################################<br />
# Options for password control #<br />
################################<br />
<br />
AuthType Basic<br />
AuthBasicProvider ldap<br />
AuthName "Some sort of name"<br />
AuthLDAPURL ldap://192.168.0.3:389/o=redbrick?uid?sub?objectClass=posixAccount<br />
AuthzLDAPAuthoritative Off<br />
Require valid-user<br />
</pre><br />
<br />
And hey presto, no need for a password file and you can log in with your redbrick details, of course so can anyone else so if you want to restrict access replace<br />
<br />
Require valid-user<br />
<br />
with<br />
<br />
Require user user1 user2 (Obviously replace user1 user2 with actual usernames etc)<br />
<br />
<br />
== Cloning the Repo ==<br />
<br />
Once all this is done you should be able to login at https://www.redbrick.dcu.ie/~username/hg - of course you won't see any code there yet.<br />
<br />
Go to whatever computer you want to start writing code on and clone a copy of the repo <br />
<br />
andrew@laptop:~ $ hg clone https://www.redbrick.dcu.ie/~receive/hg<br />
<br />
Now I have a copy of the repo on my laptop I can work on. You should [http://mercurial.selenic.com/guide/ read the guide] to see all the commands that are available, but the basics you'll need are hg add and hg commit. <br />
<br />
<br />
== Pushing ==<br />
<br />
After making changes you can push them back to your repo on RedBrick. <br />
<br />
andrew@laptop:~/hg $ hg push<br />
<br />
You can now look at the changes on the web interface :)</div>Creadakhttps://wiki.redbrick.dcu.ie/index.php?title=Mercurial&diff=9955Mercurial2011-04-12T17:24:13Z<p>Creadak: </p>
<hr />
<div>Mercurial is a version control system, like [[svn|subversion]] in that it manages changes in your code, but different in that it's designed to be distributed. Git and bazaar are also distributed version control systems. Mercurial is also written in python, which is [http://xkcd.com/353/ cool]. It's built in web interface is also excellent.<br />
<br />
==Setting Up On RedBrick ==<br />
<br />
All the setup needs to be done on murphy, since that's the webserver. After that, you can access your code from anywhere.<br />
<br />
First, we need to setup the repo that will contain the code <br />
receive@murphy (~) % hg init hgrepo<br />
<br />
Next, we setup the web access...<br />
<br />
=== Step 1 - Create the directory, and copy in the python cgi ===<br />
receive@murphy (~) % cd ~/public_html<br />
receive@murphy (~/public_html) % mkdir hg<br />
receive@murphy (~/public_html) % chmod 711 hg<br />
receive@murphy (~/public_html) % cd hg<br />
receive@murphy (~/public_html/hg) % cp /usr/share/doc/mercurial-common/examples/hgweb.cgi ./index.cgi<br />
receive@murphy (~/public_html/hg) % chmod 755 index.cgi<br />
<br />
=== Step 2 - Set the repo location ===<br />
<br />
Open the index.cgi in nano (or any other text editor) and on the second to last line replace /YOUR/HOME/DIR/YOUR/REPO with the location of the repo you created. For me, this is /home/member/r/receive/hgrepo - the location will depend on where your home directory is. Optionally, replace "repository name" with something cooler.<br />
<br />
=== Step 3 - Set Up htaccess ===<br />
<br />
receive@murphy (~/public_html/hg) % touch .htaccess<br />
receive@murphy (~/public_html/hg) % chmod 644 .htaccess<br />
<br />
Open the htaccess file in a text editor. <br />
<br />
<pre><br />
##################################<br />
# Force all access to over https #<br />
##################################<br />
<br />
RewriteCond %{SERVER_PORT} 80<br />
RewriteRule (.*) https://www.redbrick.dcu.ie/~receive/hg<br />
<br />
<br />
###################################<br />
# Options for rewriting hg access #<br />
###################################<br />
<br />
RewriteCond %{SERVER_PORT} 443<br />
#write base depending on where the base url lives<br />
RewriteBase /~receive/hg<br />
# Send requests for files that exist to those files.<br />
RewriteCond %{REQUEST_FILENAME} !-f<br />
# Send requests for directories that exist to those directories.<br />
RewriteCond %{REQUEST_FILENAME} !-d<br />
# Send requests to hgwebdir.cgi, appending the rest of url.<br />
RewriteRule (.*) hgweb.redbrick.cgi/$1 [QSA,L]<br />
<br />
################################<br />
# Options for password control #<br />
################################<br />
<br />
AuthType Basic<br />
AuthName "My Mercurial Repo"<br />
AuthUserFile /home/member/r/receive/.hgpasswd<br />
Require valid-user<br />
</pre><br />
<br />
You can use this htaccess file as a sample, but you'll need to make a few changes. The rewrite base should be set to the location on the webserver you created the hg directory. If you've been following the same example names I used it will be ~username/hg<br />
<br />
Also, you'll need to set the location you're going to use for your htpasswd file. <br />
<br />
=== Step 4: Create the password file ===<br />
<br />
receive@murphy (~/public_html/hg) % htpasswd -c /home/member/r/receive/.hgpasswd receive<br />
<br />
This will prompt you to enter your new password twice.<br />
<br />
receive@murphy (~/public_html/hg) % chmod 644 /home/member/r/receive/.hgpasswd<br />
<br />
<br />
== Cloning the Repo ==<br />
<br />
Once all this is done you should be able to login at https://www.redbrick.dcu.ie/~username/hg - of course you won't see any code there yet.<br />
<br />
Go to whatever computer you want to start writing code on and clone a copy of the repo <br />
<br />
andrew@laptop:~ $ hg clone https://www.redbrick.dcu.ie/~receive/hg<br />
<br />
Now I have a copy of the repo on my laptop I can work on. You should [http://mercurial.selenic.com/guide/ read the guide] to see all the commands that are available, but the basics you'll need are hg add and hg commit. <br />
<br />
<br />
== Pushing ==<br />
<br />
After making changes you can push them back to your repo on RedBrick. <br />
<br />
andrew@laptop:~/hg $ hg push<br />
<br />
You can now look at the changes on the web interface :)</div>Creadakhttps://wiki.redbrick.dcu.ie/index.php?title=Dropbox&diff=9861Dropbox2011-01-03T14:53:14Z<p>Creadak: </p>
<hr />
<div>== What is Dropbox? ==<br />
<br />
Dropbox is an web based file hosting service. It creates a folder in your home directory (usually ~/Dropbox) and monitors that folder and keeps it synced to the web and to other computers that you have installed Dropbox on. It's also a fairly handy way to upload files between your computer and RedBrick as it doesn't need your account details, it just requires that you link the client with your Dropbox account<br />
<br />
== Installing Dropbox on your RedBrick account ==<br />
<br />
Dropbox can't be installed on RedBrick in the traditional way as it is a plugin for nautilus which isn't going to be installed on RedBrick any time soon. Instead, we'll download the Command Line Interface version.<br />
<br />
=== Pre-installation ===<br />
<br />
First, you need to be on [[Morpheus]], as dropbox doesn't seem to work on [[Minerva]]. So, type: <br />
<br />
ssh morpheus <br />
<br />
to get to morpheus. Secondly, despite dropbox saying that the command line version uses the http_proxy variable, it actually uses the HTTP_PROXY variable, so lets set it correctly with:<br />
<br />
export HTTP_PROXY="http://proxy.dcu.ie:3128"<br />
<br />
And now you're ready to start.<br />
<br />
=== Installation === <br />
<br />
Grab the program from the dropbox website with:<br />
<br />
wget -O dropbox.tar.gz "http://www.dropbox.com/download/?plat=lnx.x86_64"<br />
<br />
Extract it to ~/.dropbox-dist with:<br />
<br />
tar -xvzf dropbox.tar.gz<br />
<br />
Next, create a folder in your home directory called bin:<br />
<br />
mkdir ~/bin<br />
<br />
There's something nice about this folder, if you type echo $PATH into your shell, you'll notice that that folder has been added to the start of your $PATH. Your $PATH is the list of folders that your shell looks through (in order) when it tries to execute a program. For example, if in your ~/bin you have a program called ls and try to execute ls, your shell will execute ~/bin/ls, as opposed to the systems ls. This is the folder where we will install the Dropbox CLI. Execute the following:<br />
<br />
wget -O ~/bin/dropbox "http://www.dropbox.com/download?dl=packages/dropbox.py"<br />
<br />
And make the program executable:<br />
<br />
chmod 700 ~/bin/dropbox<br />
<br />
Next, we'll start the dropbox daemon:<br />
<br />
~/.dropbox-dist/dropboxd<br />
<br />
This will give you output similar to the screen shot below. Follow the link and sign into your account to link your account to the client. <br />
<br />
[[Image:Dropboxd.png]]<br />
<br />
After you've done this, press ctrl+c to kill it, as we're going to use the dropbox program we downloaded earlier to interact with the daemon from now on. Notice how you have a shiny new ~/Dropbox folder? Dropbox is now ready to go.<br />
<br />
=== Using the dropbox script ===<br />
<br />
If you use a shell that autocorrects, you may want to turn it off in the config file, as when in your home directory, the Dropbox folder may confuse it, when you actually meant the dropbox program in your ~/bin. To do this in zsh put the following in your ~/.zshrc<br />
<br />
alias dropbox="nocorrect dropbox"<br />
<br />
and then reload your config<br />
<br />
source ~/.zshrc<br />
<br />
To start the dropbox daemon with the dropbox program type:<br />
<br />
dropbox start<br />
<br />
Notice how with this we get our terminal back? The dropbox script daemonises the dropbox daemon so that you can continue doing things while it runs in the background. Handy, no? Other useful dropbox commands are:<br />
<br />
dropbox status - See if the daemon is running or not<br />
dropbox stop - Stop the dropbox daemon<br />
dropbox autostart - Start the dropbox daemon as soon as you login.<br />
dropbox help - A list of all the commands<br />
<br />
== Extending Dropbox ==<br />
<br />
There are some pretty nice extensions for Dropbox, see http://wiki.dropbox.com/DropboxAddons?action=recall&rev=182 for a list of some of them. They all come with their own documentation, so it shouldn't be too hard to use them.<br />
<br />
== Your Dropbox and your RedBrick Quota ==<br />
<br />
Dropbox saves copies of your files to each copmuter it is linked to, so if you use your 2GB on dropbox you will need 2GB of space on your RedBrick account, if you need more space, contact the admins.</div>Creadakhttps://wiki.redbrick.dcu.ie/index.php?title=Dropbox&diff=9860Dropbox2011-01-02T20:55:56Z<p>Creadak: </p>
<hr />
<div>== What is Dropbox? ==<br />
<br />
Dropbox is an web based file hosting service. It creates a folder in your home directory (usually ~/Dropbox) and monitors that folder and keeps it synced to the web and to other computers that you have installed Dropbox on.<br />
<br />
== Installing Dropbox on your RedBrick account ==<br />
<br />
Dropbox can't be installed on RedBrick in the traditional way as it is a plugin for nautilus which isn't going to be installed on RedBrick any time soon. Instead, we'll download the Command Line Interface version.<br />
<br />
=== Pre-installation ===<br />
<br />
First, you need to be on [[Morpheus]], as dropbox doesn't seem to work on [[Minerva]]. So, type: <br />
<br />
ssh morpheus <br />
<br />
to get to morpheus. Secondly, despite dropbox saying that the command line version uses the http_proxy variable, it actually uses the HTTP_PROXY variable, so lets set it correctly with:<br />
<br />
export HTTP_PROXY="http://proxy.dcu.ie:3128"<br />
<br />
And now you're ready to start.<br />
<br />
=== Installation === <br />
<br />
Grab the program from the dropbox website with:<br />
<br />
wget -O dropbox.tar.gz "http://www.dropbox.com/download/?plat=lnx.x86_64"<br />
<br />
Extract it to ~/.dropbox-dist with:<br />
<br />
tar -xvzf dropbox.tar.gz<br />
<br />
Next, create a folder in your home directory called bin:<br />
<br />
mkdir ~/bin<br />
<br />
There's something nice about this folder, if you type echo $PATH into your shell, you'll notice that that folder has been added to the start of your $PATH. Your $PATH is the list of folders that your shell looks through (in order) when it tries to execute a program. For example, if in your ~/bin you have a program called ls and try to execute ls, your shell will execute ~/bin/ls, as opposed to the systems ls. This is the folder where we will install the Dropbox CLI. Execute the following:<br />
<br />
wget -O ~/bin/dropbox "http://www.dropbox.com/download?dl=packages/dropbox.py"<br />
<br />
And make the program executable:<br />
<br />
chmod 700 ~/bin/dropbox<br />
<br />
Next, we'll start the dropbox daemon:<br />
<br />
~/.dropbox-dist/dropboxd<br />
<br />
This will give you output similar to the screen shot below. Follow the link and sign into your account to link your account to the client. <br />
<br />
[[Image:Dropboxd.png]]<br />
<br />
After you've done this, press ctrl+c to kill it, as we're going to use the dropbox program we downloaded earlier to interact with the daemon from now on. Notice how you have a shiny new ~/Dropbox folder? Dropbox is now ready to go.<br />
<br />
=== Using the dropbox script ===<br />
<br />
If you use a shell that autocorrects, you may want to turn it off in the config file, as when in your home directory, the Dropbox folder may confuse it, when you actually meant the dropbox program in your ~/bin. To do this in zsh put the following in your ~/.zshrc<br />
<br />
alias dropbox="nocorrect dropbox"<br />
<br />
and then reload your config<br />
<br />
source ~/.zshrc<br />
<br />
To start the dropbox daemon with the dropbox program type:<br />
<br />
dropbox start<br />
<br />
Notice how with this we get our terminal back? The dropbox script daemonises the dropbox daemon so that you can continue doing things while it runs in the background. Handy, no? Other useful dropbox commands are:<br />
<br />
dropbox status - See if the daemon is running or not<br />
dropbox stop - Stop the dropbox daemon<br />
dropbox autostart - Start the dropbox daemon as soon as you login.<br />
dropbox help - A list of all the commands<br />
<br />
== Extending Dropbox ==<br />
<br />
There are some pretty nice extensions for Dropbox, see [[http://wiki.dropbox.com/DropboxAddons?action=recall&rev=182]] for a list of some of them. They all come with their own documentation, so it shouldn't be too hard to use them.<br />
<br />
== Your Dropbox and your RedBrick Quota ==<br />
<br />
Dropbox saves copies of your files to each copmuter it is linked to, so if you use your 2GB on dropbox you will need 2GB of space on your RedBrick account, if you need more space, contact the admins.</div>Creadakhttps://wiki.redbrick.dcu.ie/index.php?title=Dropbox&diff=9859Dropbox2011-01-02T20:53:47Z<p>Creadak: </p>
<hr />
<div>== What is Dropbox? ==<br />
<br />
Dropbox is an web based file hosting service. It creates a folder in your home directory (usually ~/Dropbox) and monitors that folder and keeps it synced to the web and to other computers that you have installed Dropbox on.<br />
<br />
== Installing Dropbox on your RedBrick account ==<br />
<br />
Dropbox can't be installed on RedBrick in the traditional way as it is a plugin for nautilus which isn't going to be installed on RedBrick any time soon. Instead, we'll download the Command Line Interface version.<br />
<br />
=== Pre-installation ===<br />
<br />
First, you need to be on [[Morpheus]], as dropbox doesn't seem to work on [[Minerva]]. So, type: <br />
<br />
ssh morpheus <br />
<br />
to get to morpheus. Secondly, despite dropbox saying that the command line version uses the http_proxy variable, it actually uses the HTTP_PROXY variable, so lets set it correctly with:<br />
<br />
export HTTP_PROXY="http://proxy.dcu.ie:3128"<br />
<br />
And now you're ready to start.<br />
<br />
=== Installation === <br />
<br />
Grab the program from the dropbox website with:<br />
<br />
wget -O dropbox.tar.gz "http://www.dropbox.com/download/?plat=lnx.x86_64"<br />
<br />
Extract it to ~/.dropbox-dist with:<br />
<br />
tar -xvzf dropbox.tar.gz<br />
<br />
Next, create a folder in your home directory called bin:<br />
<br />
mkdir ~/bin<br />
<br />
There's something nice about this folder, if you type echo $PATH into your shell, you'll notice that that folder has been added to the start of your $PATH. Your $PATH is the list of folders that your shell looks through (in order) when it tries to execute a program. For example, if in your ~/bin you have a program called ls and try to execute ls, your shell will execute ~/bin/ls, as opposed to the systems ls. This is the folder where we will install the Dropbox CLI. Execute the following:<br />
<br />
wget -O ~/bin/dropbox "http://www.dropbox.com/download?dl=packages/dropbox.py"<br />
<br />
And make the program executable:<br />
<br />
chmod 700 ~/bin/dropbox<br />
<br />
Next, we'll start the dropbox daemon:<br />
<br />
~/.dropbox-dist/dropboxd<br />
<br />
This will give you output similar to the screen shot below. Follow the link and sign into your account to link your account to the client. <br />
<br />
[[Image:Dropboxd.png]]<br />
<br />
After you've done this, press ctrl+c to kill it, as we're going to use the dropbox program we downloaded earlier to interact with the daemon from now on. Notice how you have a shiny new ~/Dropbox folder? Dropbox is now ready to go.<br />
<br />
=== Using the dropbox script ===<br />
<br />
If you use a shell that autocorrects, you may want to turn it off in the config file, as when in your home directory, the Dropbox folder may confuse it, when you actually meant the dropbox program in your ~/bin. To do this in zsh put the following in your ~/.zshrc<br />
<br />
alias dropbox="nocorrect dropbox"<br />
<br />
and then reload your config<br />
<br />
source ~/.zshrc<br />
<br />
To start the dropbox daemon with the dropbox program type:<br />
<br />
dropbox start<br />
<br />
Notice how with this we get our terminal back? The dropbox script daemonises the dropbox daemon so that you can continue doing things while it runs in the background. Handy, no? Other useful dropbox commands are:<br />
<br />
dropbox status - See if the daemon is running or not<br />
dropbox stop - Stop the dropbox daemon<br />
dropbox autostart - Start the dropbox daemon as soon as you login.<br />
dropbox help - A list of all the commands<br />
<br />
== Extending Dropbox ==<br />
<br />
There are some pretty nice extensions for Dropbox, see [[http://wiki.dropbox.com/DropboxAddons?action=recall&rev=182]] for a list of some of them. They all come with their own documentation, so it shouldn't be too hard to use them.<br />
<br />
== Dropbox ==<br />
<br />
Dropbox saves copies of your files to each copmuter it is linked to, so if you use your 2GB on dropbox you will need 2GB of space on your RedBrick account, if you need more space, contact the admins.</div>Creadakhttps://wiki.redbrick.dcu.ie/index.php?title=Dropbox&diff=9858Dropbox2011-01-02T20:51:21Z<p>Creadak: </p>
<hr />
<div>== What is Dropbox? ==<br />
<br />
Dropbox is an web based file hosting service. It creates a folder in your home directory (usually ~/Dropbox) and monitors that folder and keeps it synced to the web and to other computers that you have installed Dropbox on.<br />
<br />
== Installing Dropbox on your RedBrick account ==<br />
<br />
Dropbox can't be installed on RedBrick in the traditional way as it is a plugin for nautilus which isn't going to be installed on RedBrick any time soon. Instead, we'll download the Command Line Interface version.<br />
<br />
=== Pre-installation ===<br />
<br />
First, you need to be on [[Morpheus]], as dropbox doesn't seem to work on [[Minerva]]. So, type: <br />
<br />
ssh morpheus <br />
<br />
to get to morpheus. Secondly, despite dropbox saying that the command line version uses the http_proxy variable, it actually uses the HTTP_PROXY variable, so lets set it correctly with:<br />
<br />
export HTTP_PROXY="http://proxy.dcu.ie:3128"<br />
<br />
And now you're ready to start.<br />
<br />
=== Installation === <br />
<br />
Grab the program from the dropbox website with:<br />
<br />
wget -O dropbox.tar.gz "http://www.dropbox.com/download/?plat=lnx.x86_64"<br />
<br />
Extract it to ~/.dropbox-dist with:<br />
<br />
tar -xvzf dropbox.tar.gz<br />
<br />
Next, create a folder in your home directory called bin:<br />
<br />
mkdir ~/bin<br />
<br />
There's something nice about this folder, if you type echo $PATH into your shell, you'll notice that that folder has been added to the start of your $PATH. Your $PATH is the list of folders that your shell looks through (in order) when it tries to execute a program. For example, if in your ~/bin you have a program called ls and try to execute ls, your shell will execute ~/bin/ls, as opposed to the systems ls. This is the folder where we will install the Dropbox CLI. Execute the following:<br />
<br />
wget -O ~/bin/dropbox "http://www.dropbox.com/download?dl=packages/dropbox.py"<br />
<br />
And make the program executable:<br />
<br />
chmod 700 ~/bin/dropbox<br />
<br />
Next, we'll start the dropbox daemon:<br />
<br />
~/.dropbox-dist/dropboxd<br />
<br />
This will give you output similar to the screen shot below. Follow the link and sign into your account to link your account to the client. <br />
<br />
[[Image:Dropboxd.png]]<br />
<br />
After you've done this, press ctrl+c to kill it, as we're going to use the dropbox program we downloaded earlier to interact with the daemon from now on. Notice how you have a shiny new ~/Dropbox folder? Dropbox is now ready to go.<br />
<br />
=== Using the dropbox script ===<br />
<br />
If you use a shell that autocorrects, you may want to turn it off in the config file, as when in your home directory, the Dropbox folder may confuse it, when you actually meant the dropbox program in your ~/bin. To do this in zsh put the following in your ~/.zshrc<br />
<br />
alias dropbox="nocorrect dropbox"<br />
<br />
and then reload your config<br />
<br />
source ~/.zshrc<br />
<br />
To start the dropbox daemon with the dropbox program type:<br />
<br />
dropbox start<br />
<br />
Notice how with this we get our terminal back? The dropbox script daemonises the dropbox daemon so that you can continue doing things while it runs in the background. Handy, no? Other useful dropbox commands are:<br />
<br />
dropbox status - See if the daemon is running or not<br />
dropbox stop - Stop the dropbox daemon<br />
dropbox autostart - Start the dropbox daemon as soon as you login.<br />
dropbox help - A list of all the commands<br />
<br />
== Extending Dropbox ==<br />
<br />
There are some pretty nice extensions for Dropbox, see {{URL|http://wiki.dropbox.com/DropboxAddons?action=recall&rev=182}} for a list of some of them. They all come with their own documentation, so it shouldn't be too hard to use them.<br />
<br />
== Dropbox ==<br />
<br />
Dropbox saves copies of your files to each copmuter it is linked to, so if you use your 2GB on dropbox you will need 2GB of space on your RedBrick account, if you need more space, contact the admins.</div>Creadakhttps://wiki.redbrick.dcu.ie/index.php?title=Dropbox&diff=9857Dropbox2011-01-02T20:48:30Z<p>Creadak: </p>
<hr />
<div>== What is Dropbox? ==<br />
<br />
Dropbox is an web based file hosting service. It creates a folder in your home directory (usually ~/Dropbox) and monitors that folder and keeps it synced to the web and to other computers that you have installed Dropbox on.<br />
<br />
== Installing Dropbox on your RedBrick account ==<br />
<br />
Dropbox can't be installed on RedBrick in the traditional way as it is a plugin for nautilus which isn't going to be installed on RedBrick any time soon. Instead, we'll download the Command Line Interface version.<br />
<br />
=== Pre-installation ===<br />
<br />
First, you need to be on [[Morpheus]], as dropbox doesn't seem to work on [[Minerva]]. So, type: <br />
<br />
ssh morpheus <br />
<br />
to get to morpheus. Secondly, despite dropbox saying that the command line version uses the http_proxy variable, it actually uses the HTTP_PROXY variable, so lets set it correctly with:<br />
<br />
export HTTP_PROXY="http://proxy.dcu.ie:3128"<br />
<br />
And now you're ready to start.<br />
<br />
=== Installation === <br />
<br />
Grab the program from the dropbox website with:<br />
<br />
wget -O dropbox.tar.gz "http://www.dropbox.com/download/?plat=lnx.x86_64"<br />
<br />
Extract it to ~/.dropbox-dist with:<br />
<br />
tar -xvzf dropbox.tar.gz<br />
<br />
Next, create a folder in your home directory called bin:<br />
<br />
mkdir ~/bin<br />
<br />
There's something nice about this folder, if you type echo $PATH into your shell, you'll notice that that folder has been added to the start of your $PATH. Your $PATH is the list of folders that your shell looks through (in order) when it tries to execute a program. For example, if in your ~/bin you have a program called ls and try to execute ls, your shell will execute ~/bin/ls, as opposed to the systems ls. This is the folder where we will install the Dropbox CLI. Execute the following:<br />
<br />
wget -O ~/bin/dropbox "http://www.dropbox.com/download?dl=packages/dropbox.py"<br />
<br />
And make the program executable:<br />
<br />
chmod 700 ~/bin/dropbox<br />
<br />
Next, we'll start the dropbox daemon:<br />
<br />
~/.dropbox-dist/dropboxd<br />
<br />
This will give you output similar to the screen shot below. Follow the link and sign into your account to link your account to the client. <br />
<br />
[[Image:Dropboxd.png]]<br />
<br />
After you've done this, press ctrl+c to kill it, as we're going to use the dropbox program we downloaded earlier to interact with the daemon from now on. Notice how you have a shiny new ~/Dropbox folder? Dropbox is now ready to go.<br />
<br />
=== Using the dropbox script ===<br />
<br />
If you use a shell that autocorrects, you may want to turn it off in the config file, as when in your home directory, the Dropbox folder may confuse it, when you actually meant the dropbox program in your ~/bin. To do this in zsh put the following in your ~/.zshrc<br />
<br />
alias dropbox="nocorrect dropbox"<br />
<br />
and then reload your config<br />
<br />
source ~/.zshrc<br />
<br />
To start the dropbox daemon with the dropbox program type:<br />
<br />
dropbox start<br />
<br />
Notice how with this we get our terminal back? The dropbox script daemonises the dropbox daemon so that you can continue doing things while it runs in the background. Handy, no? Other useful dropbox commands are:<br />
<br />
dropbox status - See if the daemon is running or not<br />
dropbox stop - Stop the dropbox daemon<br />
dropbox autostart - Start the dropbox daemon as soon as you login.<br />
dropbox help - A list of all the commands<br />
<br />
== Extending Dropbox ==<br />
<br />
There are some pretty nice extensions for Dropbox, see [[here|http://wiki.dropbox.com/DropboxAddons?action=recall&rev=182]] for a list of some of them. They all come with their own documentation, so it shouldn't be too hard to use them.<br />
<br />
== Dropbox ==<br />
<br />
Dropbox saves copies of your files to each copmuter it is linked to, so if you use your 2GB on dropbox you will need 2GB of space on your RedBrick account, if you need more space, contact the admins.</div>Creadakhttps://wiki.redbrick.dcu.ie/index.php?title=Dropbox&diff=9856Dropbox2011-01-02T20:40:42Z<p>Creadak: Dropbox setup instructions</p>
<hr />
<div>== What is Dropbox? ==<br />
<br />
Dropbox is an web based file hosting service. It creates a folder in your home directory (usually ~/Dropbox) and monitors that folder and keeps it synced to the web and to other computers that you have installed Dropbox on.<br />
<br />
== Installing Dropbox on your RedBrick account ==<br />
<br />
Dropbox can't be installed on RedBrick in the traditional way as it is a plugin for nautilus which isn't going to be installed on RedBrick any time soon. Instead, we'll download the Command Line Interface version.<br />
<br />
=== Pre-installation ===<br />
<br />
First, you need to be on [[Morpheus]], as dropbox doesn't seem to work on [[Minerva]]. So, type: <br />
<br />
ssh morpheus <br />
<br />
to get to morpheus. Secondly, despite dropbox saying that the command line version uses the http_proxy variable, it actually uses the HTTP_PROXY variable, so lets set it correctly with:<br />
<br />
export HTTP_PROXY="http://proxy.dcu.ie:3128"<br />
<br />
And now you're ready to start.<br />
<br />
=== Installation === <br />
<br />
Grab the program from the dropbox website with:<br />
<br />
wget -O dropbox.tar.gz "http://www.dropbox.com/download/?plat=lnx.x86_64"<br />
<br />
Extract it to ~/.dropbox-dist with:<br />
<br />
tar -xvzf dropbox.tar.gz<br />
<br />
Next, create a folder in your home directory called bin:<br />
<br />
mkdir ~/bin<br />
<br />
There's something nice about this folder, if you type echo $PATH into your shell, you'll notice that that folder has been added to the start of your $PATH. Your $PATH is the list of folders that your shell looks through (in order) when it tries to execute a program. For example, if in your ~/bin you have a program called ls and try to execute ls, your shell will execute ~/bin/ls, as opposed to the systems ls. This is the folder where we will install the Dropbox CLI. Execute the following:<br />
<br />
wget -O ~/bin/dropbox "http://www.dropbox.com/download?dl=packages/dropbox.py"<br />
<br />
And make the program executable:<br />
<br />
chmod 700 ~/bin/dropbox<br />
<br />
Next, we'll start the dropbox daemon:<br />
<br />
~/.dropbox-dist/dropboxd<br />
<br />
This will give you output similar to the screen shot below. Follow the link and sign into your account to link your account to the client. <br />
<br />
[[Image:Dropboxd.png]]<br />
<br />
After you've done this, press ctrl+c to kill it, as we're going to use the dropbox program we downloaded earlier to interact with the daemon from now on. Notice how you have a shiny new ~/Dropbox folder? Dropbox is now ready to go.<br />
<br />
=== Using the dropbox script ===<br />
<br />
If you use a shell that autocorrects, you may want to turn it off in the config file, as when in your home directory, the Dropbox folder may confuse it, when you actually meant the dropbox program in your ~/bin. To do this in zsh put the following in your ~/.zshrc<br />
<br />
alias dropbox="nocorrect dropbox"<br />
<br />
and then reload your config<br />
<br />
source ~/.zshrc<br />
<br />
To start the dropbox daemon with the dropbox program type:<br />
<br />
dropbox start<br />
<br />
Notice how with this we get our terminal back? The dropbox script daemonises the dropbox daemon so that you can continue doing things while it runs in the background. Handy, no? Other useful dropbox commands are:<br />
<br />
dropbox status - See if the daemon is running or not<br />
dropbox stop - Stop the dropbox daemon<br />
dropbox autostart - Start the dropbox daemon as soon as you login.<br />
dropbox help - A list of all the commands<br />
<br />
== Extending Dropbox ==<br />
<br />
There are some pretty nice extensions for Dropbox, see [[http://wiki.dropbox.com/DropboxAddons?action=recall&rev=182]] for a list of some of them. They all come with their own documentation, so it shouldn't be too hard to use them.</div>Creadakhttps://wiki.redbrick.dcu.ie/index.php?title=File:Dropboxd.png&diff=9855File:Dropboxd.png2011-01-02T20:12:08Z<p>Creadak: Sample dropboxd output</p>
<hr />
<div>Sample dropboxd output</div>Creadakhttps://wiki.redbrick.dcu.ie/index.php?title=Lightning&diff=9725Lightning2010-08-27T06:36:08Z<p>Creadak: /* Description */</p>
<hr />
<div>{{Redbrick Hardware}}<br />
__NOTOC__<br />
'''Lightning ~ 136.206.15.6'''<br />
== Details ==<br />
<br />
<table><br />
<tr><td>Type: </td><td>Dell Dimension 2400 Desktop Computer</td></tr><br />
<tr><td>OS:</td><td><s>Xubuntu 6.06</s> Ubuntu 9.10</td></tr><br />
<tr><td>CPU:</td><td>Intel Pentium 4 2.4GHz</td></tr><br />
<tr><td>RAM:</td><td>500mb</td></tr><br />
<tr><td>Disks:</td><td>1x 10Gb IDE borrowed from old dell</td></tr><br />
<tr><td>Drives:</td><td>IDE DVD Reader</td></tr><br />
<tr><td>Network:</td><td>1x Onboard Ethernet</td></tr><br />
</table><br />
<br />
== Description ==<br />
<br />
In october 2008 it was decided that having an additional desktop machine in the room would be helpful, and an old G3 iMac with 32mb of ram was found from somewhere, and OpenBSD was installed. The machine was named lightning due to it's impressive speed.<br />
<br />
However, the iMac was a useless piece of shit, and it was decided we should replace it with a slightly less useless piece of shit. Andrew Harford (receive@rb) donated the new lightning, which was gathering dust in his apartment.<br />
<br />
In 2010 during the Server Room Move, Craig MacEntee (creadak@rb) took lightning home, as it was gathering dust in the server room. It now sits beside his bed, comfortably running ubuntu 9.10 though it seems to die from time to time, and isn't yet connected to the internet<br />
<br />
== Services ==<br />
<br />
* Firefox<br />
* Terminal<br />
<br />
[[Category:Hardware]]</div>Creadakhttps://wiki.redbrick.dcu.ie/index.php?title=Redbrick_Hardware&diff=9724Redbrick Hardware2010-08-27T06:35:17Z<p>Creadak: /* Former machines */</p>
<hr />
<div>This is a list of all hardware hosted or owned and run by RedBrick, renowned for its vast array of idiotic and/or meaningless names.<br />
<br />
NOTE: this inventory is always incomplete.<br />
<br />
<br />
== Main servers ==<br />
<br />
* [[Carbon]]<br />
* [[Deathray]]<br />
* [[Murphy]]<br />
* [[Minerva]]<br />
* [[Morpheus]]<br />
* [[Data]]<br />
<br />
== Storage ==<br />
* [[Worf]]<br />
<br />
== Backup/Management Servers ==<br />
<br />
* [[Severus]]<br />
* [[Thunder]]<br />
* [[Sprout]]<br />
* [[B4]]<br />
<br />
== VM Servers ==<br />
<br />
* [[Daniel]]<br />
<br />
== Games Soc ==<br />
<br />
* [[Blinky]]<br />
<br />
== Desktop Machines ==<br />
<br />
* [[Ceiling Cat]]<br />
* [[Coke (Computer)|Coke]]<br />
<br />
== Former machines ==<br />
<br />
* [[Asplodey]]<br />
* [[Lightning]]<br />
* [[Enigma]]<br />
* [[Fap]]<br />
* [[Laser]]<br />
* [[Nanny]]<br />
* [[Mother]]<br />
* [[Nurse]]<br />
* [[Obelisk]]<br />
* [[Prodigy]]<br />
* [[Playpen]]<br />
* [[Telstar]] (formerly Burner)<br />
* [[Tolka]]<br />
* [[Troublegum]]<br />
* [[Welmar]]<br />
* [[Cynic]]<br />
<br />
== Other Equipment ==<br />
<br />
* [[Hadron]]<br />
* [[Enzyme]]<br />
* [[The Monolith]] (retired)<br />
* [[The Docolith]] (retired)<br />
* [[The Dellith]] x3<br />
* [[APC UPS]]<br />
<br />
== Accessories ==<br />
<br />
Cables<br />
<br />
* 2 x Internal SCSI LVD multimode terminators [one used in enigma array]<br />
* 1 x Internal SCSI LVD cable; 8 connectors [used in enigma raid array]<br />
* 1 x Internal SCSI SE terminator<br />
* 2 x External SCSI VHCDI <-> HD68 cable [one used in enigma array]<br />
* 1 x External SCSI HD68 cable [used for DLT]<br />
* 1 x External SCSI HD68 terminator [used for DLT]<br />
* 1 x PS/2 splitter cable [primarily for shrapnel]<br />
* 1 x 4 metre SAS cable [used in PowerVault disk array]<br />
<br />
Adaptors<br />
<br />
* 1 x SCA <-> SCSI<br />
* 1 x External HD68 SCSI <-> Internal HD68 SCSI [used in enigma raid array]<br />
* 1 x 13W3 <-> VGA [plugged into nanny but unused]<br />
<br />
Tools<br />
<br />
* Set of screwdrivers<br />
* Leatherman kit<br />
* Electrostatic wrist strap<br />
<br />
== Stuff We Don't Have, But Would Like, Or Need to Buy More Of ==<br />
<br />
* A pony.<br />
<br />
[[Category:Hardware]]<br />
<br />
<br />
[[Category:Projects]]</div>Creadakhttps://wiki.redbrick.dcu.ie/index.php?title=Redbrick_Hardware&diff=9723Redbrick Hardware2010-08-27T06:34:53Z<p>Creadak: /* Desktop Machines */</p>
<hr />
<div>This is a list of all hardware hosted or owned and run by RedBrick, renowned for its vast array of idiotic and/or meaningless names.<br />
<br />
NOTE: this inventory is always incomplete.<br />
<br />
<br />
== Main servers ==<br />
<br />
* [[Carbon]]<br />
* [[Deathray]]<br />
* [[Murphy]]<br />
* [[Minerva]]<br />
* [[Morpheus]]<br />
* [[Data]]<br />
<br />
== Storage ==<br />
* [[Worf]]<br />
<br />
== Backup/Management Servers ==<br />
<br />
* [[Severus]]<br />
* [[Thunder]]<br />
* [[Sprout]]<br />
* [[B4]]<br />
<br />
== VM Servers ==<br />
<br />
* [[Daniel]]<br />
<br />
== Games Soc ==<br />
<br />
* [[Blinky]]<br />
<br />
== Desktop Machines ==<br />
<br />
* [[Ceiling Cat]]<br />
* [[Coke (Computer)|Coke]]<br />
<br />
== Former machines ==<br />
<br />
* [[Asplodey]]<br />
* [[Enigma]]<br />
* [[Fap]]<br />
* [[Laser]]<br />
* [[Nanny]]<br />
* [[Mother]]<br />
* [[Nurse]]<br />
* [[Obelisk]]<br />
* [[Prodigy]]<br />
* [[Playpen]]<br />
* [[Telstar]] (formerly Burner)<br />
* [[Tolka]]<br />
* [[Troublegum]]<br />
* [[Welmar]]<br />
* [[Cynic]]<br />
<br />
== Other Equipment ==<br />
<br />
* [[Hadron]]<br />
* [[Enzyme]]<br />
* [[The Monolith]] (retired)<br />
* [[The Docolith]] (retired)<br />
* [[The Dellith]] x3<br />
* [[APC UPS]]<br />
<br />
== Accessories ==<br />
<br />
Cables<br />
<br />
* 2 x Internal SCSI LVD multimode terminators [one used in enigma array]<br />
* 1 x Internal SCSI LVD cable; 8 connectors [used in enigma raid array]<br />
* 1 x Internal SCSI SE terminator<br />
* 2 x External SCSI VHCDI <-> HD68 cable [one used in enigma array]<br />
* 1 x External SCSI HD68 cable [used for DLT]<br />
* 1 x External SCSI HD68 terminator [used for DLT]<br />
* 1 x PS/2 splitter cable [primarily for shrapnel]<br />
* 1 x 4 metre SAS cable [used in PowerVault disk array]<br />
<br />
Adaptors<br />
<br />
* 1 x SCA <-> SCSI<br />
* 1 x External HD68 SCSI <-> Internal HD68 SCSI [used in enigma raid array]<br />
* 1 x 13W3 <-> VGA [plugged into nanny but unused]<br />
<br />
Tools<br />
<br />
* Set of screwdrivers<br />
* Leatherman kit<br />
* Electrostatic wrist strap<br />
<br />
== Stuff We Don't Have, But Would Like, Or Need to Buy More Of ==<br />
<br />
* A pony.<br />
<br />
[[Category:Hardware]]<br />
<br />
<br />
[[Category:Projects]]</div>Creadakhttps://wiki.redbrick.dcu.ie/index.php?title=Lightning&diff=9715Lightning2010-08-26T19:21:47Z<p>Creadak: </p>
<hr />
<div>{{Redbrick Hardware}}<br />
__NOTOC__<br />
'''Lightning ~ 136.206.15.6'''<br />
== Details ==<br />
<br />
<table><br />
<tr><td>Type: </td><td>Dell Dimension 2400 Desktop Computer</td></tr><br />
<tr><td>OS:</td><td><s>Xubuntu 6.06</s> Ubuntu 9.10</td></tr><br />
<tr><td>CPU:</td><td>Intel Pentium 4 2.4GHz</td></tr><br />
<tr><td>RAM:</td><td>500mb</td></tr><br />
<tr><td>Disks:</td><td>1x 10Gb IDE borrowed from old dell</td></tr><br />
<tr><td>Drives:</td><td>IDE DVD Reader</td></tr><br />
<tr><td>Network:</td><td>1x Onboard Ethernet</td></tr><br />
</table><br />
<br />
== Description ==<br />
<br />
In october 2008 it was decided that having an additional desktop machine in the room would be helpful, and an old G3 iMac with 32mb of ram was found from somewhere, and OpenBSD was installed. The machine was named lightning due to it's impressive speed.<br />
<br />
However, the iMac was a useless piece of shit, and it was decided we should replace it with a slightly less useless piece of shit. Andrew Harford (receive@rb) donated the new lightning, which was gathering dust in his apartment.<br />
<br />
In 2010 during the Server Room Move, Craig MacEntee (creadak@rb) took lightning home, as it was gathering dust in the server room. It now sits beside his bed, comfortably running ubuntu 9.10<br />
<br />
== Services ==<br />
<br />
* Firefox<br />
* Terminal<br />
<br />
[[Category:Hardware]]</div>Creadakhttps://wiki.redbrick.dcu.ie/index.php?title=Committee_Timeline&diff=9705Committee Timeline2010-07-03T12:53:19Z<p>Creadak: </p>
<hr />
<div>A visual overview of who did what, when.<br />
<br />
This gets less accurate the further back you go in time - I was working off the [[Committee]] page, making guesses at who resigned, when. 2006 onwards should be fairly accurate (working from memory). Feel free to make any corrections (it's a pig of a table, though, so you might want to work on it offline, and abuse the Show Preview function a bit).<br />
<br />
At the very least, it shows the sheer number of people (and man hours) who have been involved in running Redbrick at one point or another.<br />
<br />
(Idea stolen from [https://wiki.skynet.ie/Committee/CommitteeThroughThe_Ages Skynet]).<br />
<br />
{| border="1" cellspacing="0" cellpadding="5"<br />
! Semester !! Chairperson !! Secretary !! Treasurer !! Events Officer !! Public Relations Officer !! First Year Rep !! Helpdesk 1 !! Helpdesk 2 !! Helpdesk 3 !! Webmaster !! Admin 1 !! Admin 2 !! Admin 3<br />
|-<br />
| 1996 Q3<br />
|rowspan="4" style="background:greenyellow"|Sean Cullen ([[User:hyper|hyper]])<br />
|rowspan="4" style="background:orangered;color:white"|Dermot Hanley ([[User:wibble|<span style="color:white">wibble</span>]])<br />
|rowspan="4" style="background:darkslateblue;color:white"|Paraic O'Ceallaigh ([[User:swipe|<span style="color:white">swipe</span>]])<br />
|style="background:dimgray"|<br />
|rowspan="4" style="background:gold"|Micheal McHugh ([[User:sandman|sandman]])<br />
|style="background:dimgray"|<br />
|style="background:dimgray"|<br />
|style="background:dimgray"|<br />
|style="background:dimgray"|<br />
|style="background:dimgray"|<br />
|rowspan="8" style="background:red;color:white"|David Murphy ([[User:drjolt|<span style="color:white">drjolt</span>]])<br />
|rowspan="4" style="background:purple;color:white"|Fergus Donohue ([[User:fergus|<span style="color:white">fergus</span>]])<br />
|style="background:dimgray"|<br />
|-<br />
|1996 Q4<br />
|style="background:dimgray"|<br />
|style="background:dimgray"|<br />
|style="background:dimgray"|<br />
|style="background:dimgray"|<br />
|style="background:dimgray"|<br />
|style="background:dimgray"|<br />
|style="background:dimgray"|<br />
|-<br />
| 1997 Q1<br />
|style="background:dimgray"|<br />
|style="background:dimgray"|<br />
|style="background:dimgray"|<br />
|style="background:dimgray"|<br />
|style="background:dimgray"|<br />
|style="background:dimgray"|<br />
|style="background:dimgray"|<br />
|-<br />
|1997 Q2<br />
|style="background:dimgray"|<br />
|style="background:dimgray"|<br />
|style="background:dimgray"|<br />
|style="background:dimgray"|<br />
|style="background:dimgray"|<br />
|style="background:dimgray"|<br />
|style="background:dimgray"|<br />
|-<br />
| 1997 Q3<br />
|rowspan="2" style="background:plum"|Patrick Gannt ([[User:floppy|floppy]])<br />
|rowspan="8" style="background:skyblue"|Jonathan Lundberg ([[User:spock|spock]])<br />
|rowspan="4" style="background:lightcyan"|Aoife McGoveran ([[User:hms|hms]])<br />
|rowspan="4" style="background:brown;color:white"|Kevin O'Donovan ([[User:kod|<span style="color:white">kod</span>]])<br />
|rowspan="4" style="background:green;color:white"|Dave O'Flynn ([[User:firefly|<span style="color:white">firefly</span>]])<br />
|style="background:dimgray"|<br />
|rowspan="4" style="background:peachpuff"|Daire McKenna ([[User:fatwa|fatwa]])<br />
|rowspan="4" style="background:indigo;color:white"|Shane O'hUid ([[User:wishkah|<span style="color:white">wishkah</span>]])<br />
|rowspan="4" style="background:silver"|John Barker ([[User:barkerj|barkerj]])<br />
|rowspan="4" style="background:orange"|Andrew Lawless ([[User:andy|andy]])<br />
|rowspan="4" style="background:orangered;color:white"|Dermot Hanley ([[User:wibble|<span style="color:white">wibble</span>]])<br />
|rowspan="5" style="background:olive;color:white"|Ka Chun Leung ([[User:plop|<span style="color:white">plop</span>]])<br />
|-<br />
|1997 Q4<br />
|style="background:dimgray"|<br />
|-<br />
| 1998 Q1<br />
|rowspan="2" style="background:lightpink"|Mike Bennett ([[User:thalia|thalia]])<br />
|style="background:dimgray"|<br />
|-<br />
|1998 Q2<br />
|style="background:dimgray"|<br />
|-<br />
| 1998 Q3<br />
|rowspan="4" style="background:YellowGreen"| Justin Moran ([[User:cain|cain]])<br />
|rowspan="4" style="background:greenyellow"|Caroline Sheedy ([[Username:bootie|bootie]])<br />
|style="background:dimgray"|<br />
|rowspan="4" style="background:yellow"|Cecily Murray ([[Username:celery|celery]])<br />
|style="background:dimgray"|<br />
|rowspan="2" style="background:RoyalBlue;color:white"|Aoife Cahill ([[Username:ace|<span style="color:white">ace</span>]])<br />
|rowspan="8" style="background:blue;color:white"|Barry O'Neill ([[User:bubble|<span style="color:white">bubble</span>]])<br />
|rowspan="4" style="background:plum"|Sarvesh Singh ([[User:macbain|macbain]])<br />
|rowspan="2" style="background:red;color:white"|David Murphy ([[User:drjolt|<span style="color:white">drjolt</span>]])<br />
|rowspan="4" style="background:mediumspringgreen"|Cian Synnott ([[User:pooka|pooka]])<br />
|rowspan="2" style="background:khaki"|Colin Whittaker ([[User:grimnar|grimnar]])<br />
|-<br />
|1998 Q4<br />
|style="background:dimgray"|<br />
|style="background:dimgray"|<br />
|style="background:tomato"|John Bolger ([[Username:jbolger|jbolger]])<br />
|-<br />
|1999 Q1<br />
|style="background:dimgray"|<br />
|style="background:dimgray"|<br />
|rowspan="2" style="background:khaki"|Eoin McGrath ([[User:bob|bob]])<br />
|rowspan="2" style="background:LightSteelBlue"|Brian Scanlan ([[User:singer|singer]])<br />
|rowspan="6" style="background:Crimson;color:white"|Adam Kelly ([[User:cthulu|<span style="color:white">cthulu</span>]])<br />
|rowspan="6" style="background:peachpuff"|Hoi Chau Wong ([[User:whc|whc]])<br />
|-<br />
|1999 Q2<br />
|style="background:dimgray"|<br />
|style="background:dimgray"|<br />
|-<br />
|1999 Q3<br />
|rowspan="4" style="background:skyblue"|Jonathan Lundberg ([[User:spock|spock]])<br />
|rowspan="4" style="background:greenyellow"|Caroline Sheedy ([[User:bootie|bootie]])<br />
|rowspan="4" style="background:orangered;color:white"|Damien Martin ([[User:otto|<span style="color:white">otto</span>]])<br />
|rowspan="4" style="background:khaki"|Orla McGan ([[User:orly|orly]])<br />
|rowspan="4" style="background:lightpink"|Julie Kerin ([[User:julie|julie]])<br />
|style="background:dimgray"|<br />
|rowspan="8" style="background:gold"|Conor O'Kane ([[Username:cokane|cokane]])<br />
|rowspan="2" style="background:darkslateblue;color:white"|Nigel Parkes ([[Username:elmer|<span style="color:white">elmer</span>]])<br />
|rowspan="4" style="background:silver"|Karl Podesta ([[User:kpodesta|kpodesta]])<br />
|rowspan="8" style="background:YellowGreen"|Robert Crosbie ([[Username:bobb|bobb]])<br />
|-<br />
|1999 Q4<br />
|style="background:dimgray"|<br />
|-<br />
|2000 Q1<br />
|style="background:dimgray"|<br />
|rowspan="2" style="background:green;color:white"|Eileen Gavin ([[User:munchkin|<span style="color:white">munchkin</span>]])<br />
|-<br />
|2000 Q2<br />
|style="background:dimgray"|<br />
|-<br />
|2000 Q3<br />
|rowspan="4" style="background:silver"|Karl Podesta ([[User:kpodesta|kpodesta]])<br />
|rowspan="8" style="background:olive;color:white"|Brian Banbrick ([[User:moridin|<span style="color:white">moridin</span>]])<br />
|rowspan="4" style="background:skyblue"|Jonathan Lundberg ([[User:spock|spock]])<br />
|rowspan="4" style="background:LightSteelBlue"|John Canavan ([[User:tibor|tibor]])<br />
|rowspan="4" style="background:mediumspringgreen"|Kevin Cannon ([[User:p|p]])<br />
|style="background:dimgray"|<br />
|rowspan="4" style="color:white;background:brown"|Mark Campbell ([[User:mark|<span style="color:white">mark</span>]])<br />
|rowspan="4" style="background:lightcyan"|Donal Hunt ([[User:redgiant|redgiant]])<br />
|rowspan="4" style="background:blue;color:white"|Barry O'Neill ([[User:bubble|<span style="color:white">bubble</span>]])<br />
|rowspan="2" style="background:DarkRed;color:white"|Philip Reynolds ([[Username:phil|<span style="color:white">phil</span>]])<br />
|rowspan="2" style="background:plum"|Sarvesh Singh ([[Username:macbain|macbain]])<br />
|-<br />
|2000 Q4<br />
|style="background:dimgray"|<br />
|-<br />
|2001 Q1<br />
|style="background:dimgray"|<br />
|rowspan="2" style="background:purple;color:white"|Mark Dunne ([[User:pixies|<span style="color:white">pixies</span>]])<br />
|rowspan="2" style="background:greenyellow"|Noel Fitzpatrick ([[User:noelfitz|noelfitz]])<br />
|-<br />
|2001 Q2<br />
|style="background:dimgray"|<br />
|-<br />
|2001 Q3<br />
|rowspan="4" style="background:peachpuff"|Donal Mulligan ([[User:thor|thor]])<br />
|rowspan="4" style="background:LightSteelBlue"|John Canavan ([[User:tibor|tibor]])<br />
|rowspan="4" style="background:orange"|Micheal Glennon ([[User:magluby|magluby]])<br />
|rowspan="4" style="background:greenyellow"|Andrew MacCann ([[User:montoya|montoya]])<br />
|style="background:dimgray"|<br />
|rowspan="4" style="background:Crimson;color:white"|Kevin Dermody ([[User:esoteric|<span style="color:white">esoteric</span>]])<br />
|rowspan="4" style="background:lightpink"|Nikki Kenny ([[User:kamili|kamili]])<br />
|rowspan="4" style="background:RoyalBlue;color:white"|Neil Walsh ([[User:marvin|<span style="color:white">marvin</span>]])<br />
|rowspan="4" style="background:orangered;color:white"|Colm MacCarthaigh ([[User:colmmacc|<span style="color:white">colmmacc</span>]])<br />
|rowspan="4" style="background:DarkRed;color:white"|Philip Reynolds ([[Username:phil|<span style="color:white">phil</span>]])<br />
|rowspan="8" style="background:orange"|Cillian Sharkey ([[User:cns|cns]])<br />
|rowspan="4" style="color:white;background:brown"|Mark Campbell ([[User:mark|<span style="color:white">mark</span>]])<br />
|-<br />
|2001 Q4<br />
|style="background:dimgray"|<br />
|-<br />
|2002 Q1<br />
|style="background:dimgray"|<br />
|-<br />
|2002 Q2<br />
|style="background:dimgray"|<br />
|-<br />
|2002 Q3<br />
|rowspan="4" style="background:lightpink"|Nikky Kenny ([[User:kamili|kamili]])<br />
|rowspan="2" style="background:greenyellow"|Andrew MacCann ([[User:montoya|montoya]])<br />
|rowspan="2" style="background:RoyalBlue;color:white"|Neil Walsh ([[User:marvin|<span style="color:white">marvin</span>]])<br />
|rowspan="2" style="background:tomato"|Carla Coleman ([[User:angel|angel]])<br />
|rowspan="4" style="background:lightcyan"|Shane Tallon ([[User:del_boy|del_boy]])<br />
|style="background:dimgray"|<br />
|rowspan="8" style="background:aquamarine"|Eoin Campbell ([[User:cambo|cambo]])<br />
|rowspan="4" style="background:red;color:white"|Declan McMullen ([[User:skyhawk|<span style="color:white">skyhawk</span>]])<br />
|rowspan="2" style="color:white;background:brown"|Mark Campbell ([[User:mark|<span style="color:white">mark</span>]])<br />
|rowspan="4" style="background:olive;color:white"|David Johnston ([[User:emperor|<span style="color:white">emperor</span>]])<br />
|rowspan="8" style="background:darkslateblue;color:white"|Dermot Duffy ([[User:dizer|<span style="color:white">dizer</span>]])<br />
|rowspan="4" style="background:purple;color:white"|Mark Dunne ([[User:pixies|<span style="color:white">pixies</span>]])<br />
|-<br />
|2002 Q4<br />
|style="background:dimgray"|<br />
|-<br />
|2003 Q1<br />
|rowspan="2" style="background:Crimson;color:white"|Trevor Johnston ([[User:trevj|<span style="color:white">trevj</span>]])<br />
|rowspan="4" style="background:khaki"|Grainne Sheerin ([[User:dimples|dimples]])<br />
|rowspan="2" style="background:YellowGreen"|Elaine Bannon ([[User:purdy|purdy]])<br />
|style="background:dimgray"|<br />
|rowspan="2" style="background:green;color:white"|Declan O'Neill ([[User:dec|<span style="color:white">dec</span>]])<br />
|-<br />
|2003 Q2<br />
|style="background:dimgray"|<br />
|-<br />
| 2003 Q3<br />
|rowspan="4" style="background:olive;color:white"|David Johnston ([[User:emperor|<span style="color:white">emperor</span>]])<br />
|rowspan="4" style="background:orange"|Cillian Sharkey ([[User:cns|cns]])<br />
|rowspan="4" style="background:gold"|Martina Frain ([[User:dramaq|dramaq]])<br />
|rowspan="4" style="background:RoyalBlue;color:white"|Aisling Devlin ([[User:aeris|<span style="color:white">aeris</span>]])<br />
|style="background:dimgray"|<br />
|rowspan="4" style="background:skyblue"|Una Kehoe ([[User:keloe|keloe]])<br />
|rowspan="4" style="background:coral"|Sun Ning ([[User:sunshine|sunshine]])<br />
|rowspan="4" style="background:red;color:white"|Declan McMullen ([[User:skyhawk|<span style="color:white">skyhawk</span>]])<br />
|rowspan="4" style="background:LightSteelBlue"|Martin Clarke ([[User:prolix|prolix]])<br />
|rowspan="4" style="background:tomato"|Martin Harte ([[User:tuama|tuama]])<br />
|-<br />
|2003 Q4<br />
|style="background:dimgray"|<br />
|-<br />
| 2004 Q1<br />
|rowspan="2" style="background:silver"|Seamus O'Toole ([[User:mael|mael]])<br />
|style="background:dimgray"|<br />
|-<br />
|2004 Q2<br />
|style="background:dimgray"|<br />
|-<br />
| 2004 Q3<br />
|rowspan="8" style="background:orangered;color:white"|Michelle Graham ([[User:drusilla|<span style="color:white">drusilla</span>]])<br />
|rowspan="2" style="background:peachpuff"|Donal Mulligan ([[User:thor|thor]])<br />
|rowspan="4" style="background:DarkRed;color:white"|Charlene Barrett ([[User:charlene|<span style="color:white">charlene</span>]])<br />
|rowspan="4" style="background:green;color:white"|Mark Grenham ([[User:kyper|<span style="color:white">kyper</span>]])<br />
|rowspan="4" style="background:gold"|Martina Frain ([[User:dramaq|dramaq]])<br />
|style="background:dimgray"|<br />
<br />
|rowspan="8" style="background:blue;color:white"|Stephen Doyle ([[User:igy|<span style="color:white">igy</span>]])<br />
|rowspan="4" style="background:mediumspringgreen"|John Doyle ([[User:art_wolf|art_wolf]])<br />
|rowspan="4" style="background:indigo;color:white"|Eoghan Gaffney ([[User:atlas|<span style="color:white">atlas</span>]])<br />
|rowspan="4" style="background:tomato"|David Whelan ([[User:biteme|biteme]])<br />
|rowspan="8" style="background:plum"|Charlie Von Metzradt ([[User:phaxx|phaxx]])<br />
|rowspan="4" style="background:Crimson;color:white"|Michael Dowling ([[User:mickeyd|<span style="color:white">mickeyd</span>]])<br />
|rowspan="4" style="background:YellowGreen"|Padraic Hallinan ([[User:halenger|halenger]])<br />
|-<br />
|2004 Q4<br />
|style="background:dimgray"|<br />
|-<br />
| 2005 Q1<br />
|rowspan="2" style="background:RoyalBlue;color:white"|Aisling Devlin ([[User:aeris|<span style="color:white">aeris</span>]])<br />
|style="background:dimgray"|<br />
|-<br />
|2005 Q2<br />
|style="background:dimgray"|<br />
|-<br />
|2005 Q3<br />
|rowspan="4" style="background:yellow"|David Couse ([[User:phreak|phreak]])<br />
|rowspan="4" style="color:white;background:brown"|Kenneth Barrett ([[User:sionnach|<span style="color:white">sionnach</span>]])<br />
|rowspan="4" style="background:lightcyan"|Bernard McKeever ([[User:dregin|dregin]])<br />
|rowspan="4" style="background:lightpink"|Jessica Ní Chonchubair ([[User:jesjes|jesjes]])<br />
|style="background:dimgray"|<br />
|rowspan="8" style="background:darkslateblue;color:white"|Simon Kilroy ([[User:gizmo|<span style="color:white">gizmo</span>]])<br />
|rowspan="4" style="background:khaki"|Graham Bishop ([[User:winters|winters]])<br />
|rowspan="4" style="background:skyblue"|Una Kehoe ([[User:keloe|keloe]])<br />
|rowspan="8" style="background:indigo;color:white"|Eoghan Gaffney ([[User:atlas|<span style="color:white">atlas</span>]])<br />
|rowspan="4" style="background:DarkRed;color:white"|Stephen Ryan ([[User:ryaner|<span style="color:white">ryaner</span>]])<br />
|-<br />
|2005 Q4<br />
|style="background:dimgray"|<br />
|-<br />
|2006 Q1<br />
|style="background:dimgray"|<br />
|-<br />
|2006 Q2<br />
|style="background:dimgray"|<br />
|-<br />
|2006 Q3<br />
|rowspan="4" style="background:plum"|Charlie Von Metzradt ([[User:phaxx|phaxx]])<br />
|rowspan="4" style="background:lightpink"|Jessica Ni Chonchubhair ([[User:jesjes|jesjes]])<br />
|rowspan="4" style="background:red;color:white"|Andrew Harford ([[User:receive|<span style="color:white">receive</span>]])<br />
|rowspan="8" style="background:purple;color:white"|Kat Farrell ([[User:angelkat|<span style="color:white">angelkat</span>]])<br />
|rowspan="2" style="background:orange"|Padraig O'Connor ([[User:landa2|landa2]])<br />
|style="background:dimgray"|<br />
|rowspan="4" style="background:greenyellow"|Kevin Fox ([[User:undone|undone]])<br />
|rowspan="4" style="background:coral"|Diarmuid Bourke ([[User:drag0n|drag0n]])<br />
|rowspan="4" style="background:mediumspringgreen"|John Doyle ([[User:art_wolf]])<br />
|rowspan="4" style="background:RoyalBlue;color:white"|Sarunas Vancevicius ([[User:svan|<span style="color:white">svan</span>]])<br />
|style="background:dimgray"|<br />
|-<br />
| 2006 Q4<br />
|style="background:dimgray"|<br />
|rowspan="3" style="background:blue;color:white"|Stephen Doyle ([[User:igy|<span style="color:white">igy</span>]])<br />
|-<br />
| 2007 Q1<br />
|rowspan="6" style="background:olive;color:white"|Damien Rhatigan ([[User:dano|<span style="color:white">dano</span>]])<br />
|style="background:dimgray"|<br />
|-<br />
|2007 Q2<br />
|style="background:dimgray"|<br />
|-<br />
|2007 Q3<br />
|rowspan="4" style="background:red;color:white"|Andrew Harford ([[User:receive|<span style="color:white">receive</span>]])<br />
|rowspan="4" style="background:greenyellow"|Kevin Fox ([[User:undone|undone]])<br />
|style="background:peachpuff"|Ashley Samuel Dooley Martyn ([[User:mythe|mythe]])<br />
|style="background:dimgray"|<br />
|rowspan="2" style="background:lightcyan"|Matthew Barrington ([[User:moju|moju]])<br />
|rowspan="4" style="background:lightsalmon"|Eoghan Cotter ([[User:johan|johan]])<br />
|rowspan="2" style="background:YellowGreen"|Declan Whelan ([[User:castle|castle]])<br />
|rowspan="4" style="background:silver"|Richard Dalton ([[User:d_fens|d_fens]])<br />
|rowspan="4" style="background:gold"|Andrew Martin ([[User:werdz|werdz]])<br />
|style="background:coral"|Diarmuid Bourke ([[User:drag0n|drag0n]])<br />
|rowspan="8" style="background:skyblue"|Cian Brennan ([[User:lil_cain|lil_cain]])<br />
|-<br />
|2007 Q4<br />
|rowspan="3" style="background:aquamarine"|Amy Corrigan ([[User:corriga6|corriga6]])<br />
|style="background:dimgray"|<br />
|style="background:dimgray"|<br />
|-<br />
|2008 Q1<br />
|style="background:dimgray"|<br />
|rowspan="2" style="background:orange"|Padraig O'Connor ([[User:landa2|landa2]])<br />
|rowspan="2" style="background:green;color:white"|David Lynam ([[User:coconut|<span style="color:white">coconut</span>]])<br />
|style="background:dimgray"|<br />
|-<br />
|2008 Q2<br />
|style="background:dimgray"|<br />
|style="background:dimgray"|<br />
|-<br />
|2008 Q3<br />
|style="background:coral"|Robert O'Reilly ([[User:robby|robby]])<br />
|rowspan="4" style="background:olive;color:white"|Damien Rhatigan ([[User:dano|<span style="color:white">dano</span>]])<br />
|rowspan="4" style="background:plum"|Leah Doyle ([[User:bambi|bambi]])<br />
|rowspan="4" style="background:blue;color:white"|Lotta Mikkonen ([[User:attol|<span style="color:white">attol</span>]])<br />
|rowspan="2" style="background:RoyalBlue;color:white"|John Needham ([[User:colossus|<span style="color:white">colossus</span>]])<br />
|rowspan="4" style="background:yellow"|Emma Gallagher ([[User:emma|emma]])<br />
|rowspan="2" style="color:white;background:brown"|Sean Hand ([[User:revenant|<span style="color:white">revenant</span>]])<br />
|rowspan="4" style="background:orangered;color:white"|Séamus Ronan ([[User:train|<span style="color:white">train</span>]])<br />
|rowspan="2" style="background:peachpuff"|Gavin Tubritt ([[User:gamblitis|gamblitis]])<br />
|rowspan="4" style="background:gold"|Andrew Martin ([[User:werdz|werdz]])<br />
|rowspan="4" style="background:red;color:white"|Andrew Harford ([[User:receive|<span style="color:white">receive</span>]])<br />
|rowspan="8" style="background:lightsalmon"|Eoghan Cotter ([[User:johan|johan]])<br />
|-<br />
|2008 Q4<br />
|rowspan="3" style="background:purple;color:white"|Kat Farrell ([[User:angelkat|<span style="color:white">angelkat</span>]])<br />
|-<br />
|2009 Q1<br />
|rowspan="2" style="background:khaki"|Carri Fuery ([[User:carri|carri]])<br />
|style="background:dimgray"|<br />
|style="background:dimgray"|<br />
|-<br />
|2009 Q2<br />
|style="background:dimgray"|<br />
|style="background:dimgray"|<br />
|-<br />
|2009 Q3<br />
|rowspan="5" style="background:blue;color:white"|Lotta Mikkonen ([[User:attol|<span style="color:white">attol</span>]])<br />
|rowspan="4" style="background:yellow"|Emma Gallagher ([[User:emma|emma]])<br />
|rowspan="4" style="color:white;background:brown"|Sean Hand ([[User:revenant|<span style="color:white">revenant</span>]])<br />
|rowspan="2" style="background:khaki"|Carri Fuery ([[User:carri|carri]])<br />
|rowspan="4" style="background:silver"|Dan Fox ([[User:maiden|maiden]])<br />
|rowspan="4" style="background:greenyellow"|David Glennon ([[User:azrael|azrael]])<br />
|rowspan="2" style="background:lightpink"|Austin Halpin ([[User:haus|haus]])<br />
|rowspan="4" style="background:lightcyan"|Diarmaid McManus ([[User:elephant|elephant]])<br />
|rowspan="4" style="background:mediumspringgreen"|Gautam Wadhwa ([[User:gw|gw]])<br />
|rowspan="4" style="background:purple;color:white"|Kat Farrell ([[User:angelkat|<span style="color:white">angelkat</span>]])<br />
|style="background:green;color:white"|David Lynam ([[User:coconut|<span style="color:white">coconut</span>]])<br />
|rowspan="4" style="background:plum"|Alan Breathnach ([[User:sonic|sonic]])<br />
|-<br />
|2009 Q4<br />
|rowspan="3" style="background:gold"|Andrew Martin ([[User:werdz|werdz]])<br />
|-<br />
|2010 Q1<br />
|rowspan="2" style="background:coral"|Stephanie Coleman ([[User:steph|steph]])<br />
|rowspan="2" style="background:midnightblue;color:white"|Craig Gavagan MacEntee ([[User:credak|<span style="color:white">credak</span>]])<br />
|-<br />
|2010 Q2<br />
|-<br />
|2010 Q3<br />
|rowspan="1" style="background:chocolate"|Nina Hanzlikova ([[User:geekity|<span>geekity</span>]])<br />
|rowspan="1" style="background:dimgrey"|<br />
|rowspan="1" style="background:yellow"|Emma Gallagher ([[User:emma|<span>emma</span>]])<br />
|rowspan="1" style="background:khaki"|Carri Fuery ([[User:carri|<span>carri</span>]])<br />
|rowspan="1" style="background:dimgrey"|<br />
|rowspan="1" style="background:goldenrod"|Shane Stacey ([[User:isaac702|<span>isaac702</span>]])<br />
|rowspan="1" style="background:fuchsia"|Paul Bunbury ([[User:bunbun|<span>bunbun<span>]])<br />
|rowspan="1" style="background:dimgrey"|<br />
|rowspan="1" style="background:midnightblue;color:white"|Craig Gavagan MacEntee ([[User:creadak|<span style="color:white">creadak</span>]])<br />
|rowspan="1" style="background:seagreen"|James Reilly ([[User:fun|<span>fun</span>]])<br />
|rowspan="1" style="background:darkolivegreen"|Seamus Ronan ([[User:train|<span style=>train</span>]])<br />
|rowspan="1" style="background:dimgrey"|<br />
|}</div>Creadakhttps://wiki.redbrick.dcu.ie/index.php?title=OSs_used_by_Redbrickers&diff=9683OSs used by Redbrickers2010-05-29T22:50:48Z<p>Creadak: /* creadak */</p>
<hr />
<div>Below is a list of users and what Operating Systems they are competent with.<br />
<br />
Feel free to add an an entry about yourself below.<br />
<br />
<!-- Please follow the same format when adding your username --><br />
<br />
==[[User:redgiant|redgiant]]==<br />
<br />
Linux (redhat, debian), Solaris, Tru64<br />
<br />
==[[User:cammy|cammy]]==<br />
<br />
Windows (95, 98, NT, XP), Linux (redhat), VxWork, Solaris, OS20, OS21<br />
<br />
==[[User:drag0n|drag0n]]==<br />
<br />
Linux: Redhat 8,9, Fedora 3,4. Current: Ubuntu breezy.<br/><br />
Windows: 3.1 and 95. Current: 98se and XP home.<br />
<br />
==[[User:noelfitz|noelfitz]]==<br />
<br />
FreeBSD, Windows.<br />
<br />
<br />
==[[User:lil_cain|lil_cain]]==<br />
Linux(Ubuntu & debian) Windows (<3) and a bit of free-bsd. I also love solaris. It's the best OS ever.<br />
<br />
==[[User:svan|svan]]==<br />
<br />
DragonFlyBSD, FreeBSD, Linux, Windows.<br />
<br />
==[[User:gavin|gavin]]==<br />
<br />
PalmOS 5.<br />
<br />
==[[User:kyper|kyper]]== <br />
Mac OS X, Linux (Debian & Slackware), BeOS, FreeBSD, OpenBSD and Windows<br />
<br />
==[[User:pushpop|pushpop]]==<br />
<br />
Linux (SuSe), Windows, Mac OS X<br />
<br />
==[[User:werdz|werdz]]==<br />
<br />
Ubuntu 8.04 and OpenSuSE 11, and Windows XP.<br />
<br />
==[[User:receive|receive]]==<br />
<br />
Currently using Fedora 8. That is all.<br />
<br />
==[[User:d_fens|d_fens]]==<br />
<br />
Micrsoft Vista/XP/2k/ME/98SE, Ubuntu Fesity/Edgy/Dapper, DSLinux, FreeBSD<br />
<br />
==[[User:exzantia|exzantia]]==<br />
[[image:apple_logo.jpg]] [[image:ubuntu_logo.jpg]] [[image:windows_logo.jpg]]<br />
<br />
==[[User:revenant|revenant]]==<br />
Current: Windows Vista, XP Pro, Kubuntu, OSX Tiger<br />
<br />
Past: Windows 3.1, 95, 98SE<br />
<br />
==[[User:eondev|eondev]]==<br />
Ubuntu 8.04, OS J Alpha<br />
<br />
Past OSes: Windows XP, Windows Vista (/shudder), Windows 98, Sabayon, Fedora<br />
<br />
==[[User:ru|ru]]==<br />
Current: Windows Vista Home Premium, Vista Ultimate, XP MCE Edition<br />
<br />
Past: Ubuntu 7.10, Windows XP Pro, Windows XP Home, Windows 98, Windows 95, DOS 6, Some other early dos<br />
<br />
==[[User:undone|undone]]==<br />
Vista and nothing but!<br />
<br />
==[[User:gmblitis|gmblitis]]==<br />
OS X, Linux: Ubuntu, Windows XP<br />
<br />
==[[User:haus|haus]]==<br />
Linux: ubuntu 8.10. Windows: Vista.<br />
<br />
==[[User:creadak|creadak]]==<br />
Linux: Arch Linux, Linux from Scratch (still working on it)<br />
<br />
Windows: Windows 7<br />
[[Category:Community]]</div>Creadakhttps://wiki.redbrick.dcu.ie/index.php?title=Screen&diff=9682Screen2010-05-29T22:43:03Z<p>Creadak: /* Reattaching Screen Automatically */</p>
<hr />
<div>== Basics ==<br />
'''Screen''' usually does not exist; this <s>is the committee's</s> was a former committee's general position on screen due to the disastrous and/or hilarious situations which often result from new members' attempts to get it working. However, for the purpose of this tutorial, screen '''does''' exist, and this is how you use it. (Blame coconut for this defiance.)<br />
<br />
=== Omg, what's screen? ===<br />
<br />
Screen is most commonly known as "that thing that lets you stay logged in to chat when you log out of RedBrick". It's a terminal multiplexer, which allows you to log into multiple terminal sessions from one terminal window and keeps them open when you go away to bed or whatever it is you do with your time.<br />
<br />
=== Opening ===<br />
Type "screen" at the prompt like this:<br />
<br />
<br />
[[Image:screen1.jpg]]<br />
<br />
<br />
This will open a new screen session. First you'll see the screen startup message, which gives a little info on the program.<br />
<br />
<br />
[[Image:screen2.jpg]]<br />
<br />
<br />
Just hit space/return as it says and you'll be running screen. You won't notice anything immediately different once running screen, instead, you'll be back at the same old terminal. Now, however, you have access to a large variety of commands and features that you didn't before.<br />
<br />
== Screen commands ==<br />
=== Ctrl-a commands ===<br />
Nearly all of screen's commands are used via the ctrl-a key combination. First, you press the ctrl and a keys together, then release. Next, press the key you want to run a command. These commands can be a little awkward and difficult to remember at first, but you'll soon get the hang of it. In this tutorial, the commands will be shown as ctrl-a and then a letter, with the following letter being associated with a command.<br />
<br />
=== Creating a new window ===<br />
When you start screen, it presents you with the normal single window terminal you're used to. You can, however, create many more and run them all within the one screen session. The following command will create another window for you:<br />
ctrl-a c<br />
<br />
Just hit ctrl and a together, then release them and hit c. This keybinding will open a new window (window 2) inside screen. Now you'll have two windows to use, so you'll have to learn how to use the ctrl-a commands to switch between them.<br />
<br />
=== Switching windows===<br />
Once you have more than one window open, you can switch between them using some of the following commands:<br />
ctrl-a n<br />
This command will switch you over to the next window.<br />
<br />
ctrl-a p<br />
This one will bring you back to the previous window.<br />
<br />
ctrl-a a<br />
This will switch between the last two windows that you've been using.<br />
<br />
ctrl-a window_number<br />
Using this command, you can specify exactly which window you want to jump to by hitting ctrl and a, then the number on the keyboard of your desired window. This is pretty useful for when you have a lot of windows open in screen.<br />
<br />
=== Naming your windows ===<br />
You can give each of your windows its own name too for convenience by using this command:<br />
ctrl-a A<br />
<br />
This one might seem confusing first as the A is a capital letter in this case, but all you need to do is hit ctrl and a together and release as before, then hold shift and press a to get the capital. After you run it, you'll see a white bar appear at the bottom of your window, where you can change the name of your screen to whatever you like. In this case, the window has just been renamed to "chat".<br />
<br />
<br />
[[Image:screen3.jpg]]<br />
<br />
<br />
After you've named a few windows, you can try this command:<br />
ctrl-a "<br />
<br />
Yup, even quotation marks can be used in screen commands. So as before you do ctrl-a, then hold shift and hit the 2 key to get the " :) This will bring up a convenient list of all your windows with their names.<br />
<br />
<br />
[[Image:screen4.jpg]]<br />
<br />
<br />
From this window you can view and go to any of your windows. The flags on the right indicate whether your window is logged in or not with $ symbol.<br />
<br />
=== Detaching and reattaching screen ===<br />
<br />
One of the most popular features of screen is that it can keep you logged in even when you're offline. This means you can leave programs running or even stay on IRC even when you're not online. When you "minimise" screen or make it invisible, it is called detaching it.<br />
<br />
To do this, you just detach from screen instead of exiting it. To detach from screen without exiting, use the following command:<br />
ctrl-a d<br />
<br />
You'll then be returned to the prompt with a message telling you screen has been detached, like so:<br />
<br />
<br />
[[Image:screen5.jpg]]<br />
<br />
<br />
Later, you'll come back online and want to reattach to your screen session. When you "maximise" screen or bring it back onto your terminal, this is known as attaching. To reattach a detached screen, use this command at the prompt:<br />
screen -dr<br />
<br />
The -d will detach any attached screens and -r will reattach your screen.<br />
<br />
If you have more than one screen session available, you will need to specify the screen id you wish to open. You'll be given a list of the currently available screens, so then you type:<br />
<br />
screen -r<br />
<br />
followed by the id listed above of the screen you want to reattach to.<br />
<br />
=== Start and stop signals ===<br />
Quite often it happens someone may end up using the stop signal command in screen by mistake. This command is:<br />
<br />
ctrl-a s<br />
<br />
and you should probably avoid using it! But as the s key is beside the a key, people will occasionally run this command by accident without knowing it. As this is a stop signal, it has the unfortunate side effect of freezing up your window :( Worry not however, for to fix it, all you need to do is use the start signal again to bring it back from the dead:<br />
<br />
ctrl-a q<br />
<br />
This should have you back in action very shortly. However, if your screen is frozen and you can't figure out why, try asking a member of [[Helpdesk]] and they should know the answer :)<br />
<br />
=== Killing screen while attached ===<br />
Often enough new members (and often, experienced people) will make mistakes with screen that they can't fix. To kill screen altogether and start over, use:<br />
ctrl-a \<br />
<br />
Or, if you just want to kill a single window in screen, use:<br />
<br />
ctrl-a k<br />
<br />
or even just type "exit" at the prompt.<br />
<br />
=== Killing screen while detached ===<br />
<br />
'''Warning''': using the ''kill'' command to do anything can be very dangerous if you don't know what you're doing. If you're unsure, reattach the screen you want to kill and follow the instructions above.<br />
<br />
If you have more than one screen session and you want to kill one of them, type "screen -dr" to get a list of the available screens (from the terminal which appears when you first log in to RedBrick). Note the '''number''' (also known as a process id, or pid) at the beginning of each screen name. This is the process number. Ensure you know which screen session is which.<br />
<br />
To terminate a session, use this command (''pid'' is the number of the session you want to kill)<br />
<br />
kill ''pid''<br />
<br />
This will send the signal SIGTERM to the process, requesting its termination.<br />
<br />
If that fails and you want lil_cain to start complaining<br />
<br />
kill -9 ''pid''<br />
<br />
This will send the signal SIGKILL to the process, terminating it immediately and with lots of blood.<br />
<br />
Then, to then get rid of the dead screen session, type<br />
<br />
screen -wipe<br />
<br />
== Screen Configuration ==<br />
<br />
So after you've set up screen and have gotten used to it, you will probably want to configure it a little bit and the way to do this is by creating a ~/.screenrc<br />
<br />
To do this just<br />
nano ~/.screenrc<br />
<br />
Here's an example of a .screenrc that you may want to use:<br />
<br />
hardstatus alwayslastline<br />
hardstatus string '%{= kg}[ %{G}%H %{g}][%= %{= kw}%?%-Lw%?%{=b kR}(%{W}%n*%f %t%?(%u)%?%{=b kR})%{= kw}%?%+Lw%? %?%= %{g}][%{Y}%l%{g}]%{=b C}[ %d %M %c ]%{W}'<br />
deflogin off<br />
startup_message off<br />
screen -t irc 1 irssi<br />
screen -t Email/slrn 2 mutt -Z<br />
screen -t heys -L -l 3<br />
<br />
Basically this only really does two things, sets a hardstatus (basically a line that contains some information) and makes it display only on the bottom line and also creates a few new windows.<br />
<br />
The new windows created are given names and optionally a number or command (or both).<br />
<br />
screen -t irc q irssi<br />
<br />
This will create screen window 1, give it the title "irc" and then run irssi when you start screen.<br />
<br />
deflogin off<br />
<br />
This sets windows logged out by default, which means that you won't have to "mesg n" windows to not receive heys<br />
<br />
startup_message off<br />
<br />
This turns the startup message thats displayed when you start a new screen session off.<br />
<br />
screen -t heys -L -l 3<br />
<br />
Will create a logged in window specifically for heys. Handy.<br />
<br />
All this makes it very simple to restart all your processes if Redbrick ever crashes.<br />
<br />
With the above configuration file it will look something like this:<br />
<br />
[[Image:screenrc.jpg]]<br />
<br />
=== Reattaching Screen Automatically ===<br />
<br />
So, you've made your screen, configured it, and you happily type screen -dr '''every time''' you login to RedBrick. But wouldn't it be nice if whenever you login your screen would reattach '''itself'''??? It can be done :D<br />
<br />
Simply use your favorite text editor to edit your ~/.zshrc (or ~/.[name_of_shell]rc) and paste the following code into it.<br />
<br />
if [ -z "$STY" -a $TERM != "screen" ]<br />
then<br />
exec screen -dr<br />
fi<br />
<br />
That should do the job. However make sure to keep the spaces between the if statement, the brackets and the inside of the if statement (or it won't work).<br />
<br />
In particular<br />
<br />
$TERM != "screen"<br />
<br />
is very important for that code segment to work, otherwise when connecting to another server (Carbon for instance), your shell will try to attach a screen session, fail and disconnect leaving you on the server you tried to connect from (Really quite annoying).<br />
<br />
* Please note, if this in fact, does not work, you can edit it out by using winSCP and editing the file using it.<br />
<br />
== Useful links ==<br />
If you'd like to learn more about the program, a long list of screen commands can be found here: http://www.linuxdevcenter.com/linux/cmd/cmd.csp?path=s/screen<br />
<br />
Help edited a screenrc: http://www.debian-administration.org/articles/560<br />
<br />
A starting guide to screen: http://magazine.redhat.com/2007/09/27/a-guide-to-gnu-screen/<br />
<br />
The Gentoo wiki article on screen (quite in depth) : http://www.gentoo-wiki.info/Screen<br />
<br />
[[Category:Helpdesk]]</div>Creadakhttps://wiki.redbrick.dcu.ie/index.php?title=TimeLine2010&diff=9681TimeLine20102010-05-24T01:46:53Z<p>Creadak: /* April */</p>
<hr />
<div>==January==<br />
* 20th - New direct attached storage array arrives. Named [[Worf]], to get back at [[User:lil_cain|lil_cain]] for giving us 2 years of [[Minerva|terribly]] [[Sprout|named]] [[Daniel|machines]]. Since it doesn't actually have a hostname, this won't matter though.<br />
* 20th - [[B4]] is "modified" to take extra serial ports. Pictures to be posted to seeifixedit.com soon. Still in infinitely better condition then the machine it's replacing ([[Sprout|sprout]]).<br />
==February==<br />
* 1st - Redbrick Members go to England and find that everything is cheaper. (Case in point: Burger, chips and a Vodka + coke for £4.95)<br />
* 2nd - Travelling members go to Bletchley Park and are amazed by the whole place, also Craig Gavagan Mac Entee ( credak ) discovers that Alan Turing was Gay. credak is interested enough to investigate more. Later that night, Brickies congregate in Craig's room and make enough noise to annoy an uppity German across the hall, Chris gets his hair straightened and has make up put on him.<br />
* 3rd - Brickies return from England, flight is delayed by about a half hour due to delayed flight coming from Dublin.<br />
* 5th - Redbrick goes down in order to move user files to the new faster storage array ([[Worf]]), logins return around 9 while web server remains down for a bit longer. Users gain more space for <del>pronz</del> files<br />
* 16th - Lotta Mikkonnen ([[User:attol|Attol]]), David Glennon ([[User:azrael|Azrael]]) and Craig Gavagan Mac Entee ([[User:credak|Credak]]) man the Redbrick Refreshers Day table and attract ~6/7 new people. [[User:credak|Credak]] '''voluntarily''' spends most of the day in the infamous brick mascot.<br />
* 16th - Virtual machines are made available on a this-will-probably-asplode-at-any-moment-alpha basis. It rapidly begins [[RBVM_Bugs|asploding]], but it's a huge step in the right direction.<br />
* 20th - Linux is put back on [[Murphy]]. Redbrick is free from [[Rage|Solaris]] \o/<br />
*26th-28th - Redbrick visit Skynet to attend a series of talks. Speakers include Matt Zimmerman, David Coallier and Laura Czajkowski. Terran(Skynet) takes GW, Attol and Spanza on a tour of Limerick. Not much sleep is had on the nights due to partying and chatting. Tyrion(Skynet) abuses "Kevin". A random drunk dude who wandered into our booth in Costelloe's to have a nap. Maiden parties on down with Skynetters<br />
<br />
==March==<br />
* 2nd - Admin training for 2010 begins with a session on shell scripting presented by [[User:receive|Andrew Harford]].<br />
* 8th - Start of Tech Week 2010:<br />
Monday, 1PM - Hackerspaces, Jeffrey Roe<br />
Monday, 8PM - Launch party, Nubar<br />
Tuesday, 6PM - Game Programming, [[User:kineada|Tom Cashman]]<br />
Tuesday, 7PM - Django, [[User:atlas|Eoghan Gaffney]]<br />
Tuesday, 8PM - Film, Strange Things<br />
Wednesday, 2PM - Past Multimedia Projects, Declan Tuite<br />
Wednesday, 4PM - Build Your Own PC, [[User:revenant|Sean Hand]]<br />
Wednesday, 5PM - QZar<br />
Thursday, 6PM - Sustainable Computing, [[User:doc|Dave O'Connor]], Google<br />
Thursday, 7PM - Ubuntu Ireland Community, Laura Czjakowski<br />
Thursday, 8PM - Strange Things Quiz<br />
Saturday - [[Botwars NUIG|Robot Wars, NUIG]]<br />
<br />
* The Annual Redbrick Table Quiz was held, Prizes were 1st External Hard Drives, 2nd Sega Mega Drives, 3rd Nerf Guns, The raffle prize of a Dell Mini 10v was won by Andrew Harford. Debate Soc came first, again.<br />
<br />
==April==<br />
<br />
* 15th - Annual AGM is held in CG04 with an amazing turnout. Resolution to reduce Helpdesk from three people to two people passes by a clear majority. Elections were held and the new committee was chosen.<br />
<br />
Chairperson:<br />
Lotta Mikkonen (attol) was the only candidate and was elected by a show of hands<br />
<br />
Secretary:<br />
Nina Hanzlikova (geekity) was the only candidate and was elected by a show of hands<br />
<br />
Events Officer:<br />
Emma Gallagher (emma) was the only candidate and was elected by a show of hands<br />
<br />
PRO:<br />
Carri Fuery (carri) was the only candidate and was elected by a show of hands<br />
<br />
Admins:<br />
James Reilly (fun) and Seamus Ronan (train) ran, both were elected<br />
<br />
Webmaster:<br />
Craig Gavagan Mac Entee (creadak) was the only candidate and was elected by a show of hands<br />
<br />
Helpdesk:<br />
Paul Bunbury (bunbun) and Shane Stacey (isaac702) ran, both were elected.<br />
<br />
The First Year Rep, Treasurer and the Third Admin will be elected at an EGM in October.<br />
<br />
==May==<br />
==June==<br />
==July==<br />
==August==<br />
==September==<br />
==October==<br />
==November==<br />
==December==</div>Creadakhttps://wiki.redbrick.dcu.ie/index.php?title=TimeLine2010&diff=9680TimeLine20102010-05-24T01:46:23Z<p>Creadak: /* April */</p>
<hr />
<div>==January==<br />
* 20th - New direct attached storage array arrives. Named [[Worf]], to get back at [[User:lil_cain|lil_cain]] for giving us 2 years of [[Minerva|terribly]] [[Sprout|named]] [[Daniel|machines]]. Since it doesn't actually have a hostname, this won't matter though.<br />
* 20th - [[B4]] is "modified" to take extra serial ports. Pictures to be posted to seeifixedit.com soon. Still in infinitely better condition then the machine it's replacing ([[Sprout|sprout]]).<br />
==February==<br />
* 1st - Redbrick Members go to England and find that everything is cheaper. (Case in point: Burger, chips and a Vodka + coke for £4.95)<br />
* 2nd - Travelling members go to Bletchley Park and are amazed by the whole place, also Craig Gavagan Mac Entee ( credak ) discovers that Alan Turing was Gay. credak is interested enough to investigate more. Later that night, Brickies congregate in Craig's room and make enough noise to annoy an uppity German across the hall, Chris gets his hair straightened and has make up put on him.<br />
* 3rd - Brickies return from England, flight is delayed by about a half hour due to delayed flight coming from Dublin.<br />
* 5th - Redbrick goes down in order to move user files to the new faster storage array ([[Worf]]), logins return around 9 while web server remains down for a bit longer. Users gain more space for <del>pronz</del> files<br />
* 16th - Lotta Mikkonnen ([[User:attol|Attol]]), David Glennon ([[User:azrael|Azrael]]) and Craig Gavagan Mac Entee ([[User:credak|Credak]]) man the Redbrick Refreshers Day table and attract ~6/7 new people. [[User:credak|Credak]] '''voluntarily''' spends most of the day in the infamous brick mascot.<br />
* 16th - Virtual machines are made available on a this-will-probably-asplode-at-any-moment-alpha basis. It rapidly begins [[RBVM_Bugs|asploding]], but it's a huge step in the right direction.<br />
* 20th - Linux is put back on [[Murphy]]. Redbrick is free from [[Rage|Solaris]] \o/<br />
*26th-28th - Redbrick visit Skynet to attend a series of talks. Speakers include Matt Zimmerman, David Coallier and Laura Czajkowski. Terran(Skynet) takes GW, Attol and Spanza on a tour of Limerick. Not much sleep is had on the nights due to partying and chatting. Tyrion(Skynet) abuses "Kevin". A random drunk dude who wandered into our booth in Costelloe's to have a nap. Maiden parties on down with Skynetters<br />
<br />
==March==<br />
* 2nd - Admin training for 2010 begins with a session on shell scripting presented by [[User:receive|Andrew Harford]].<br />
* 8th - Start of Tech Week 2010:<br />
Monday, 1PM - Hackerspaces, Jeffrey Roe<br />
Monday, 8PM - Launch party, Nubar<br />
Tuesday, 6PM - Game Programming, [[User:kineada|Tom Cashman]]<br />
Tuesday, 7PM - Django, [[User:atlas|Eoghan Gaffney]]<br />
Tuesday, 8PM - Film, Strange Things<br />
Wednesday, 2PM - Past Multimedia Projects, Declan Tuite<br />
Wednesday, 4PM - Build Your Own PC, [[User:revenant|Sean Hand]]<br />
Wednesday, 5PM - QZar<br />
Thursday, 6PM - Sustainable Computing, [[User:doc|Dave O'Connor]], Google<br />
Thursday, 7PM - Ubuntu Ireland Community, Laura Czjakowski<br />
Thursday, 8PM - Strange Things Quiz<br />
Saturday - [[Botwars NUIG|Robot Wars, NUIG]]<br />
<br />
* The Annual Redbrick Table Quiz was held, Prizes were 1st External Hard Drives, 2nd Sega Mega Drives, 3rd Nerf Guns, The raffle prize of a Dell Mini 10v was won by Andrew Harford. Debate Soc came first, again.<br />
<br />
==April==<br />
<br />
* 15th - Annual AGM is held in CG04 with an amazing turnout. Resolution to reduce Helpdesk from three people to two people passes by a clear majority. Elections were held and the new committee was chosen.<br />
<br />
Chairperson:<br />
Lotta Mikkonen (attol) was the only candidate and was elected by a show of hands<br />
<br />
Secretary:<br />
Nina Hanzlikova (geekity) was the only candidate and was elected by a show of hands<br />
<br />
Events Officer:<br />
Emma Gallagher (emma) was the only candidate and was elected by a show of hands<br />
<br />
PRO:<br />
Carri Fuery (carri) was the only candidate and was elected by a show of hands<br />
<br />
Admins:<br />
James Reilly (fun) and Seamus Ronan ( train ) ran, both were elected<br />
<br />
Webmaster:<br />
Craig Gavagan Mac Entee (creadak) was the only candidate and was elected by a show of hands<br />
<br />
Helpdesk:<br />
Paul Bunbury (bunbun) and Shane Stacey (isaac702) ran, both were elected.<br />
<br />
The First Year Rep, Treasurer and the Third Admin will be elected at an EGM in October.<br />
<br />
==May==<br />
==June==<br />
==July==<br />
==August==<br />
==September==<br />
==October==<br />
==November==<br />
==December==</div>Creadakhttps://wiki.redbrick.dcu.ie/index.php?title=Coders_on_Redbrick&diff=9670Coders on Redbrick2010-05-06T23:26:55Z<p>Creadak: </p>
<hr />
<div>Below is a list of users and their relevant language competencies. Feel free to add an an entry about yourself.<br />
<br />
<!-- Please follow the same format when adding your username --><br />
<br />
==[[User:bilco|bilco]]==<br />
<br />
Java, PL/SQL, JSP<br />
<br />
==[[User:cammy|cammy]]==<br />
<br />
Java, C, Perl, C++, Javascript, PHP (and a sprinkling of Visual Basic, Visual C++ and Python)<br />
<br />
==[[User:cambo|cambo]]==<br />
<br />
C# 2.0, ASP.NET 2.0, AJAX.NET, MSSQL 2005. (XHTML, CSS, XML, Bit of Javascript, Bit of Desktop & Windows Service Dev)<br />
<br />
==[[User:calyx|calyx]]==<br />
<br />
Java, C, C++, PHP, HTML/CSS/XML (tiny amount of Perl and Python)<br />
<br />
==[[User:creadak|creadak]]==<br />
<br />
Python, Java X86 Assembly, Haskell, R, sprinkling of C, Shell Scripting, SQL HTML/CSS/XHTML/Django/PHP<br />
<br />
==[[User:drag0n|drag0n]]==<br />
<br />
Java, PHP, Prolog, Haskell and bits of C, C++ and JavaScript.<br />
<br />
==[[User:Eondev|EonDev]]==<br />
<br />
Java, C++, PHP, MySQL<br />
<br />
==[[User:halenger|halenger]]==<br />
<br />
Python, Java, some PHP/C/C++<br />
<br />
==[[User:jasper|jasper]]==<br />
<br />
VB6, VB.NET, Java, C++, C#, PHP, ASP, JSP, JS, XSLT<br />
<br />
==[[User:kyper|kyper]]==<br />
<br />
BASIC (QBasic, FreeBASIC, VB6 VB .NET), Java, C/C++/Obj-C, PHP and ASP<br />
<br />
==[[User:link|link]]==<br />
<br />
C, Java, Perl, Tcl<br />
<br />
==[[User:noelfitz|noelfitz]]==<br />
<br />
Java, C++.<br />
<br />
==[[User:phase|phase]]==<br />
<br />
VB6, C#/VB.NET, Coldfusion MX, MSSQL, ASP, MySQL<br />
<br />
==[[User:redgiant|redgiant]]==<br />
<br />
C, C++, perl, php, python, ASP<br />
<br />
==[[User:Taurus|Taurus]]==<br />
<br />
Usual web stuff (XHTML, CSS etc...), Javascript, PHP, C++, Java, SQL and PL/SQL<br />
<br />
==[[User:osama|osama]]==<br />
<br />
Java, JSP, XML, PHP, C#, Progress, C, Perl, PL/SQL<br />
<br />
==[[User:werdz|werdz]]==<br />
Python, C, C++, Perl, Java, Usual web stuff (PHP, JS, etc)<br />
<br />
==[[User:pushpop|pushpop]]==<br />
<br />
C/C++, Java, ASP, PHP, x86, MIPS, SQL<br />
<br />
[[Category:Community]]</div>Creadakhttps://wiki.redbrick.dcu.ie/index.php?title=OSs_used_by_Redbrickers&diff=9669OSs used by Redbrickers2010-05-06T23:16:12Z<p>Creadak: /* creadak */</p>
<hr />
<div>Below is a list of users and what Operating Systems they are competent with.<br />
<br />
Feel free to add an an entry about yourself below.<br />
<br />
<!-- Please follow the same format when adding your username --><br />
<br />
==[[User:redgiant|redgiant]]==<br />
<br />
Linux (redhat, debian), Solaris, Tru64<br />
<br />
==[[User:cammy|cammy]]==<br />
<br />
Windows (95, 98, NT, XP), Linux (redhat), VxWork, Solaris, OS20, OS21<br />
<br />
==[[User:drag0n|drag0n]]==<br />
<br />
Linux: Redhat 8,9, Fedora 3,4. Current: Ubuntu breezy.<br/><br />
Windows: 3.1 and 95. Current: 98se and XP home.<br />
<br />
==[[User:noelfitz|noelfitz]]==<br />
<br />
FreeBSD, Windows.<br />
<br />
<br />
==[[User:lil_cain|lil_cain]]==<br />
Linux(Ubuntu & debian) Windows (<3) and a bit of free-bsd. I also love solaris. It's the best OS ever.<br />
<br />
==[[User:svan|svan]]==<br />
<br />
DragonFlyBSD, FreeBSD, Linux, Windows.<br />
<br />
==[[User:gavin|gavin]]==<br />
<br />
PalmOS 5.<br />
<br />
==[[User:kyper|kyper]]== <br />
Mac OS X, Linux (Debian & Slackware), BeOS, FreeBSD, OpenBSD and Windows<br />
<br />
==[[User:pushpop|pushpop]]==<br />
<br />
Linux (SuSe), Windows, Mac OS X<br />
<br />
==[[User:werdz|werdz]]==<br />
<br />
Ubuntu 8.04 and OpenSuSE 11, and Windows XP.<br />
<br />
==[[User:receive|receive]]==<br />
<br />
Currently using Fedora 8. That is all.<br />
<br />
==[[User:d_fens|d_fens]]==<br />
<br />
Micrsoft Vista/XP/2k/ME/98SE, Ubuntu Fesity/Edgy/Dapper, DSLinux, FreeBSD<br />
<br />
==[[User:exzantia|exzantia]]==<br />
[[image:apple_logo.jpg]] [[image:ubuntu_logo.jpg]] [[image:windows_logo.jpg]]<br />
<br />
==[[User:revenant|revenant]]==<br />
Current: Windows Vista, XP Pro, Kubuntu, OSX Tiger<br />
<br />
Past: Windows 3.1, 95, 98SE<br />
<br />
==[[User:eondev|eondev]]==<br />
Ubuntu 8.04, OS J Alpha<br />
<br />
Past OSes: Windows XP, Windows Vista (/shudder), Windows 98, Sabayon, Fedora<br />
<br />
==[[User:ru|ru]]==<br />
Current: Windows Vista Home Premium, Vista Ultimate, XP MCE Edition<br />
<br />
Past: Ubuntu 7.10, Windows XP Pro, Windows XP Home, Windows 98, Windows 95, DOS 6, Some other early dos<br />
<br />
==[[User:undone|undone]]==<br />
Vista and nothing but!<br />
<br />
==[[User:gmblitis|gmblitis]]==<br />
OS X, Linux: Ubuntu, Windows XP<br />
<br />
==[[User:haus|haus]]==<br />
Linux: ubuntu 8.10. Windows: Vista.<br />
<br />
==[[User:creadak|creadak]]==<br />
Linux: Ubuntu 10.04, Debian 5, Fedora 13 beta, Arch Linux, Gentoo (building), Linux from Scratch (still working on it)<br />
<br />
Windows: Windows 7<br />
<br />
BSD: FreeBSD (in an RBVM)<br />
<br />
[[Category:Community]]</div>Creadakhttps://wiki.redbrick.dcu.ie/index.php?title=OSs_used_by_Redbrickers&diff=9668OSs used by Redbrickers2010-05-06T23:15:03Z<p>Creadak: </p>
<hr />
<div>Below is a list of users and what Operating Systems they are competent with.<br />
<br />
Feel free to add an an entry about yourself below.<br />
<br />
<!-- Please follow the same format when adding your username --><br />
<br />
==[[User:redgiant|redgiant]]==<br />
<br />
Linux (redhat, debian), Solaris, Tru64<br />
<br />
==[[User:cammy|cammy]]==<br />
<br />
Windows (95, 98, NT, XP), Linux (redhat), VxWork, Solaris, OS20, OS21<br />
<br />
==[[User:drag0n|drag0n]]==<br />
<br />
Linux: Redhat 8,9, Fedora 3,4. Current: Ubuntu breezy.<br/><br />
Windows: 3.1 and 95. Current: 98se and XP home.<br />
<br />
==[[User:noelfitz|noelfitz]]==<br />
<br />
FreeBSD, Windows.<br />
<br />
<br />
==[[User:lil_cain|lil_cain]]==<br />
Linux(Ubuntu & debian) Windows (<3) and a bit of free-bsd. I also love solaris. It's the best OS ever.<br />
<br />
==[[User:svan|svan]]==<br />
<br />
DragonFlyBSD, FreeBSD, Linux, Windows.<br />
<br />
==[[User:gavin|gavin]]==<br />
<br />
PalmOS 5.<br />
<br />
==[[User:kyper|kyper]]== <br />
Mac OS X, Linux (Debian & Slackware), BeOS, FreeBSD, OpenBSD and Windows<br />
<br />
==[[User:pushpop|pushpop]]==<br />
<br />
Linux (SuSe), Windows, Mac OS X<br />
<br />
==[[User:werdz|werdz]]==<br />
<br />
Ubuntu 8.04 and OpenSuSE 11, and Windows XP.<br />
<br />
==[[User:receive|receive]]==<br />
<br />
Currently using Fedora 8. That is all.<br />
<br />
==[[User:d_fens|d_fens]]==<br />
<br />
Micrsoft Vista/XP/2k/ME/98SE, Ubuntu Fesity/Edgy/Dapper, DSLinux, FreeBSD<br />
<br />
==[[User:exzantia|exzantia]]==<br />
[[image:apple_logo.jpg]] [[image:ubuntu_logo.jpg]] [[image:windows_logo.jpg]]<br />
<br />
==[[User:revenant|revenant]]==<br />
Current: Windows Vista, XP Pro, Kubuntu, OSX Tiger<br />
<br />
Past: Windows 3.1, 95, 98SE<br />
<br />
==[[User:eondev|eondev]]==<br />
Ubuntu 8.04, OS J Alpha<br />
<br />
Past OSes: Windows XP, Windows Vista (/shudder), Windows 98, Sabayon, Fedora<br />
<br />
==[[User:ru|ru]]==<br />
Current: Windows Vista Home Premium, Vista Ultimate, XP MCE Edition<br />
<br />
Past: Ubuntu 7.10, Windows XP Pro, Windows XP Home, Windows 98, Windows 95, DOS 6, Some other early dos<br />
<br />
==[[User:undone|undone]]==<br />
Vista and nothing but!<br />
<br />
==[[User:gmblitis|gmblitis]]==<br />
OS X, Linux: Ubuntu, Windows XP<br />
<br />
==[[User:haus|haus]]==<br />
Linux: ubuntu 8.10. Windows: Vista.<br />
<br />
==[[User:creadak|creadak]]==<br />
Linux: Ubuntu 10.04, Debian 5, Fedora 13 beta, Arch Linux, Gentoo (building), Linux from Scratch (still working on it)<br />
Windows: Windows 7<br />
BSD: FreeBSD (in an RBVM)<br />
<br />
[[Category:Community]]</div>Creadak