Firefox (v3 et précédentes) semble allergique aux liens irc chez moi. La modification de la page about:config ne fonctionne pas et le système introduit dans la version 3 n'apprécie pas l'ajout d'option.

Ma solution a été d'utiliser un petit script bash :

#!/bin/bash
xchat -e --url=$1

Il suffit de rendre le script exécutable puis de configurer Firefox pour qu'il l'utilise (irc dans l'onglet Applications)

Expressions avec yum

Je vois souvent sur les forums et les blogs des commandes du type :

yum install -y gstreamer*

où on utilise * pour installer plusieurs paquets en une seule commande. Au passage, cette méthode bien bourrin installera également les paquets de dévellopement et les paquets de debug (si le dépôt est activé).

En dehors de * (n'importe quels caractères), il y a également les accolades ({}) pour définir une liste, par exemple :

yum install gstreamer-plugins-{ugly,schroedinger,farsight,bad,bad-extras}
yum install nautilus-{image-converter,open-terminal}

On peut également définir des plages entre crochet. Exemple :

yum list [a-zA-Z]im

xguest

Tout vrai geek est parano (à un certain degré du moins), c'est pour cela qu'on ne laisse pas n'importe qui avoir accès n'importe comment à notre précieux ordinateur. Pour cela, il existe un paquet très pratique, xguest, qui crée un utilisateur nommé guest permettant à n'importe qui d'utiliser votre ordinateur entant qu'invité.

L'avantage de ce paquet par rapport à la création d'un utilisateur normal est que le guest est confiné grâce à SELinux (par exemple, guest ne peut pas utiliser su pour devenir root) et le home du guest est automatiquement nettoyer après déconnexion.

yum install -y xguest

I have the following line at the end of my .bashrc,
[source language='python']# Tracks next action reminders
~/bin/todo[/source]

and following script saved as ~/bin/todo:
[source language='python']#!/bin/bash

# Plain text feed URL
feed_url="https://tracks.tra.in/todos.txt?due=1&token=xxxxxxxxxxx-your-token-here-xxxxxxxxxxxx"

# Where to save the list locally
local_file="/home/user/.todo"

# How many minutes old before downloading the latest todo list
age_threshold=20

# ------------------------------------------------------------------------------

# Commandline arguments
mode="$1"

# Check for and create local_file
if [ ! -f $local_file ]; then
touch $local_file
mode="update"
fi

# Calculate how old the current todo list is
age_in_minutes=$(echo "(`date +%s` - `date -r $local_file +%s`) / 60" | bc)

# If it's been too long since the todo list was last updated,
if [ $age_in_minutes -gt $age_threshold ] || [ "$mode" = "update" ]; then

# Download the latest todo list
echo -n "${age_in_minutes} minutes since last update. Getting todo list... "
wget -q --timeout=4 -O $local_file $feed_url && echo "`color green`OK`color off`" || echo "`color red`Failed`color off`"

else

# Otherwise, just use the one we already have
echo "Updated ${age_in_minutes} minutes ago."

fi

# Print out the list
color ltblue && cat $local_file && color off[/source]

To force an update, $ ~/bin/todo update.

http://wifi.ham-radio-op.net/misc/compsci/

For those of you who don't know, ham-radio-op.net is run by dyndns.com, which probably means that the person running "wifi" has his own server. See the dyndns website if you have no clue what I'm talking about.

Updating my EBooks post...

Aqui les dejo este diagrama creado por Éric Lévénez, en el cual mediante informacion logro plasmar la historia de los lenguajes de programacion detalladamente y muy claro.

Download PDF

Mas Informacion

My rating: 4 of 5 Nerds =)

//cuidado com directorios que contenham espaços doens't work with spaces ;

find /home/ -uid 0 -exec ls -l \{\} \;

fgrep 'gold' /var/log/ -R | grep -i something

or regexp style search
egrep '(err|fail|warning)' /var/log/* > `date +%F`.txt

ls -l  | sed -e 's/andre/netcrash/gi'

#!/usr/bin/perl

print "hello\n";
$dir="/home/andre";
if ( (!(-d $dir."/Maildir")) ){
`/usr/bin/maildirmake.maildrop $dir"/Maildir"`;

}

bash
[03:42:08]andre@garden:~$ for i in `seq 10`; do echo $i ; done;

Haven't been using cut that mutch but, also a good weapon of choice.

Simple things that evolve to more complex tools :D

Motywacja

Alternatywą dla znanego wszystkim programu NapiProject pod linuksa (poza odpalaniem Napi przez Wine) jest programik napisany w pythonie autorstwa panów(tak mniemam): gim,krzynio,dosiu,hash.
Programik mimo, iż działa wzorowo nie ma opcji przeszukiwania rekurencyjnego katalogów, czyli w uproszczeniu: podaj_katalog -> znajdź_filmy -> znajdź_do_nich_napisy. W takim właśnie uproszczeniu i bez fajerwerków (sprawdzania np. czy katalog istnieje etc) działa poniższy skrypcik.

Skrypt wygląda następująco:

#!/bin/bash
#---------------------------------------#
#skrypt by spas (spassite.wordpress.com)#
#---------------------------------------#
dir="/katalog/z/filmami/"
ext=".avi"; #rozszerzenie do wyszukania
find $dir -name "*.avi" | while read file
do
name=`echo $file | sed 's/.avi//'`; #utnij rozszerzenie
file=`echo $file | sed 's/ /\ /'`;
if [ ! -e "${name}.txt" ]; then #czy napis jeszcze niepobrany?
echo "${name}.avi"
./napi.py "$file"; #wywolaj skrypt dla filmów bez napisów
fi
done

Aby uruchomić skrypt:

chmod +x plik_z_powyższym_skryptem.sh
./plik_z_powyższym_skryptem.sh

Do jego działania niezbędny jest napi.py w tym samym katalogu co skrypt, oraz paczka "p7zip-full" (sudo aptitude install p7zip-full), bez której napi.py nie będzie poprawnie pobierać napisów.

Lista życzeń (czyt. co zrobię jak będę miał chwilkę):

• sprawdzanie, czy katalog istnieje
• ścieżka do katalogu odczytywana ze zmiennych wywołania
• obsługa wielu rozszerzeń
• ...

Pliki do pobrania:

napi.py - program ściągający napisy do pobrania

1. Football Fans
2. Music Junkies
3. Bird Lovers
4. Eagle's Nest Members/attendees 

Ok, well sorry to disappoint any of the people in categories 1-3, but I'm not talking about Football, Music, or Birds. THESE THOUGHTS CAME TO ME WHILE CLEANING... First, I want to put out a disclaimer, that this specific blog post is not a bash on anyone, it is not written out of anger, and it is not intended for the purposes of de-facing the value of the history of Eagle's Nest.  

A little back story for my new/outside readers. I attend, and have attended Eagle's Nest Fellowship Church for a little under 11 years now, Have been very involved with many ministries and have even worked for the church some as well. Now there is a point to all of this and if you leave now you'll probably just think I'm another agree rebellious teenager (19)...but this blog is going to be pretty honest only for the sake of making a good point.

I'm afraid that it won't do the story justice, but I have to start somewhere, so i'll start with the fact that Eagle's Nest has many Eagle's and paintings of eagle's and are logo has an eagle on it...and rightfully so I might add, goes well with the name...  and so throughout the building you will find many. *(I think in one office I have counted somewhere around 20) Now, of-course some of us love to joke about it, and the truth is that Eagle's happen to be a large part of who we are. 

**So, I have a confession to make. I have been on a team (comprised of myself only) responsible for the slow removal of Eagle's from the viewable presence of people. Yes, this is true i started stashing them. Only I soon realized that soon there would be no decorations left, so I gave up. but if you read this and your favorite piece is missing, come find me on Sunday, I'll give it to you and you can take it home with you.**

I share this next true story from my perspective, and my perspective only. And I'm not using names for the sake of... well you get the picture. But one sunday, After the removal of a particular Eagle Painting I, along with a few other people where questioned about the disappearance of said eagle, (said eagle had been promptly replaced by a beautiful hand painting from another location.) If I believe correctly, we lied, and said we didn't know where it was and for that I am sorry. However, by the next week the Eagle was placed back and has remained there since. Apparently other church members had complained or otherwise asked about the painting not being there.

IF I'M LOOSING YOU... hang in there I'm getting to my point.

Wake up church, that is my message. That is my challenge to you!!!! Some people may argue and say that I'm just as wrong for wanting the Eagle to not be there. but I'm not saying that. I'm saying that Its NOT about what is hanging on our walls. AND WE HAVE MADE IT ABOUT THAT.  If we don't love people like we should then the stuff on our walls is POINTLESS. 

Community is not about some identity, (ours being the eagle) Its about fellowship. Where are all the pictures of ministry happening, and the art work of worshipers, where is the life and the joy that we are sharing?? Why don't we publish that to our people? why not leave our corporate Identity for the sake of our community?

This will be my final paragraph I promise I have written enough, and feel like i have explained nothing, but hopefully your hearing my heart here. Ok, so I'm going to leave you with these last thoughts. I go to college, and I spend time with people who are hurting, and seeking and NOT FINDING A PLACE. Where do these young people hang out? a lot of them, bars. what if our church looked like a bar? Ok, HEAR ME I'm not suggesting that we rip out everything and start serving beer. But I am asking you to consider WHAT ARE WE ABOUT? are we about our pictures of eagles? Are we about our favorite songs? are we about pretty colors? are we about fancy buildings or Amazing Graphics? OR are we about showing people the LIFE found in jesus? What if we stopped going to church on sunday for ourselves and started going for everyone else? Why wouldn't the church be the perfect place to display EVERYTHING going on in the community of the church itself?  And so I leave you with this question, and this challenge.

Ask yourself this question: WHAT IF CHURCH WAS BUILT FOR THEM AND NOT FOR ME.

thanks for enduring, if you have questions or you'd like to beat me up for my honesty please email me: takaminescx@gmail.com. I hope that you have heard my heart I strive to love you all with everything I have. And I want to be a piece of building something so much greater then anyone of us could be alone. 
In Christ's Service
Jeffery Peck

(www.myspace.com/no_your_other_left) 

*** if you email me comments, I may in-fact post them back on here to reply.***

Of course not all consoles are created equal. Some consoles are really just the equivalent of

while line=nextLine() ; do print line ; end

Typically this is reserved to crappy IDE's (yes, I know that's redundant, I'm making a hah-hah).

Some deluded souls think cygwin is a real console, only to discover half-way into trying to actually get something done that it ends up going nutso and spewing text in the most unlikely of locations. Infrequently this can lead to a series of awkward questions in the ER.

Gnome's terminal is pretty adequate, and of course you can't go wrong with xterm or a host of other well written, robust terminals that oddly enuff seem to show up only under flavors of UNIX (yes, netBSD... err.. Mac counts too).

Why is writing a solid console implementation so difficult?

Because a console is not about printing lines of text. A terminal is more like a pixel-based display where ever pixel is a character + presentation information.

It is a highly sophisticated user interface. Unlike the farktarded point-and-click UI's popular today for no good reason which use a maximum of say 8 buttons, a console typically has 108+ buttons.

Hah-hah, indeed. More importantly a console is really an interpreter.

No, I don't mean the shell, I mean the console is an interpreter. Just like with shells we have bash, tcsh and crapsh, terminals come in flavors like VT100, VT110, VT220, 3270, 5270 and plethora of others.

Since a terminals has to accept all sorts of input, the language for controlling the terminal is a done via "control codes." Typically a control code is just a string which is difficult to type.

For example: echo <ESC>[33mCheese<ESC>[0m

What is that <ESC>? Typically it is character 27. How do you type it? On a lot of consoles, you type it like this:

1. hold down the control key
2. press the 'v' key
3. let go of the control and 'v' key
4. press the escape key

Pretty neat, huh? That works for ANSI/VT100-based terminals. Not for all terminals. Luckily for us, that's just about all we really care about.

Of course a real console application (eg: vim) cares about all terminals and you start to move away from writing control codes directly and towards using terminal apis like curses/ncurses PDQ.

For hacking purposes, VT100 terminal codes will do just fine.

I know.. what a load of historic irrelevant blather and so what and quit wasting my time! What is it good for?!

When was the last time you looked at a log file? Let me put it a different way, when did you stop looking at log files? Chances are you are watching a log file right now! I know I am!

What percentage of log output do you care about for a given task? 10%? 2%? Isn't it a drag that it just blends in with the rest?

Of course you could grep it out, but then you lose the context... Or you might forget a term and have to reproduce the problem again (again [again]).

IMHO, a kick-aspirin use for VT100 color codes is for log highlighting, and it is some simple, it can be easily scripting into a general use script.

Here is the kind of usage I would like:

usage: cat foo | line_lite.sh ( pattern highlighting )+

pattern         is a ala grep
highlighting    is a colon separated list of colors

the colors are 

    reset        bright      dim         underline    blink
    reverse      hidden      black       red          green
    yellow       blue        magenta     cyan         white
    black_bg     red_bg      green_bg    yellow_bg    blue_bg
    magenta_bg   cyan_bg     white_bg

That way I can use it like: tail -f some.log | line_lite.sh Exception red "some other text" green:underline

In order to make this happen, I need to convert that red, green:underline crap to the appropriate VT100 code.

Natually, I do this with sed:

_line_lite_color_to_code() {
    echo ${*} | sed "s,reset,0,g;s,bright,1,g;s,dim,2,g;s,underline,4,g;s,blink,5,g;s,reverse,7,g;s,hidden,8,g;s,black,30,g;s,red,31,g;s,green,32,g;s,yellow,33,g;s,blue,34,g;s,magenta,35,g;s,cyan,36,g;s,white,37,g;s,black_bg,40,g;s,red_bg,41,g;s,green_bg,42,g;s,yellow_bg,43,g;s,blue_bg,44,g;s,magenta_bg,45,g;s,cyan_bg,46,g;s,white_bg,47,g;s,:,;,g"
}

_line_lite_code() {
    _line_lite_color_to_code ${*} | sed 's,.*,ESC[&m,'
}

This will convert "green:underline" to [32;4m

Now we just need some way to do our matching and add the color code. Once again, it's sed time.

For each pair of pattern/color, we create a sed expression like: s!.*.*!&!g;

% jar_minder_javap sun.security.provider.PolicyFile | line_lite.sh 'static'  red:bright
Compiled from "PolicyFile.java"
public class sun.security.provider.PolicyFile extends java.security.Policy{
    public sun.security.provider.PolicyFile();
    public sun.security.provider.PolicyFile(boolean);
    public void refresh();
    public boolean implies(java.security.ProtectionDomain, java.security.Permission);
    public java.security.PermissionCollection getPermissions(java.security.ProtectionDomain);
    public java.security.PermissionCollection getPermissions(java.security.CodeSource);
    protected java.security.cert.Certificate[] getSignerCertificates(java.security.CodeSource);
    static boolean access$002(sun.security.provider.PolicyFile, boolean);
    static boolean access$102(sun.security.provider.PolicyFile, boolean);
    static boolean access$202(sun.security.provider.PolicyFile, boolean);
    static boolean access$302(sun.security.provider.PolicyFile, boolean);
    static boolean access$200(sun.security.provider.PolicyFile);
    static sun.security.util.Debug access$400();
    static boolean access$500(sun.security.provider.PolicyFile, java.net.URL, sun.security.provider.PolicyInfo);
    static java.security.CodeSource access$600(sun.security.provider.PolicyFile, java.security.CodeSource, boolean);
    static java.lang.String access$700(sun.security.provider.PolicyFile, java.security.ProtectionDomain);
    static java.security.IdentityScope access$800();
    static {};
}

_line_lite_usage() {
cat << EOM

usage: cat foo | line_lite.sh ( pattern highlighting )+

pattern         is a ala grep
highlighting    is a colon separated list of colors

the colors are 

    reset        bright      dim         underline    blink
    reverse      hidden      black       red          green
    yellow       blue        magenta     cyan         white
    black_bg     red_bg      green_bg    yellow_bg    blue_bg
    magenta_bg   cyan_bg     white_bg    

EOM
}

_line_lite_color_to_code() {
        echo ${*} | sed "s,reset,0,g;s,bright,1,g;s,dim,2,g;s,underline,4,g;s,blink,5,g;s,reverse,7,g;s,hidden,8,g;s,black,30,g;s,red,31,g;s,green,32,g;s,yellow,33,g;s,blue,34,g;s,magenta,35,g;s,cyan,36,g;s,white,37,g;s,black_bg,40,g;s,red_bg,41,g;s,green_bg,42,g;s,yellow_bg,43,g;s,blue_bg,44,g;s,magenta_bg,45,g;s,cyan_bg,46,g;s,white_bg,47,g;s,:,;,g"
}

_line_lite_code() {
        _line_lite_color_to_code ${*} | sed 's,.*,ESC[&m,'
}

_line_lite_expr() {
        local pattern="${1}"
        local lite=$( _line_lite_code ${2})
        echo "s!.*${pattern}.*!${lite}&ESC[0m!g;"
}

_line_lite_it_up() {
        local expression=${1}
        if [ "" == "${expression}" ] ; then
                _line_lite_usage
        else
                sed "${expression}"
        fi
}

#####################
# normally I would put this in a function, but it hoses up the args

_line_lite_it_up_expression=""
while [ 2 -le ${#} ] ; do
        _line_lite_it_up_expression="${_line_lite_it_up_expression}$( _line_lite_expr "${1}" "${2}" )"
        shift 2
done

_line_lite_it_up "${_line_lite_it_up_expression}"