Trackerinstallation auf Linux Voyage - Brauche Hilfe

    Servus,

    nachdem ich es nicht geschafft habe, meinen ALIX-PC mit WIndows XP zu vergewaltigen, habe ich jetzt das vom Hersteller empfohlene Linux Voyage installiert und siehe da, es läuft wunderbar und ich habe Zugriff per SSH. Ich benötige jetzt allerdings umfangreiche Hilfe, da ich bis auf ein paar Webserver-Geschichten keine Ahnung von Linux Betriebssysteme habe.

    1. Frage: Welchen Linuxtracker sollte ich nutzen?
    2. Wie installiere ich den auf dem Alix-Pc? Ich habe einen Kartenleser & ein mobiles CD-Laufwerk sowie entsprechend LAN-Zugriff. Die eingebaute WLAN Karte muss ich noch irgendwie aktivieren.

    Ich würde mich über Einstiegshilfe freuen :)

    Achso, bevor ich es vergesse: Schön wäre noch ein Crashkurs, wie ich den Pc absturzsicher mache. D.h. nach einem Stromausfall bootet er ja automatisch - aber das auch alle Programme wieder gestartet werden. Ist sicher ein kleiner Handgriff, wenn man weiß wie ;)

    Hello, Guido

    I take some looks into the doks around installing Voyage Linux...

    There is a readme text about it, from this seems me, this process is similar as some older processes, to install linux from a Live Linux CD.
    But If I know well, there are more "small" linux distribs, offer more simple and user friendly processes to installations, maybe on your board too.
    Here is a list of linuxes, running on your board:

    I red the instruction about the install of my favorite linux, centos, but it seems, it is not for beginners. The main problem is, you need a running linux machine to make the steps, need for this install... and it need some linux knowledge to relaize it.

    There are some nice, small linuxes, maybe runninig on your board, for example Slax, Puppy Linux, it seems, the more simple is the Gentoo, use a tool to mmake bootable cf card with the complete system:

    The Voyager linux solve the "first you need a running linux system", and you can install from it the new one-problem, that the install process can start from a Live linux, started from a CD.
    If you choose this Voyage linux, I propose for you, first download the Live CD image, burn it on a CD, and use your external CD drive, start it, and study it a little.
    I propose for you, if your seller has option to install this Voyage on your board, ask them to make it.
    And I propose, if you have friend with linux practices, ask him to help to install it on your board.
    Ofcourse we can help here for you, but this process has some critical steps, practically can make and control at the keyboard diretly. face-to-face with the installing system.

    best: t.janos

    Hey Janos,

    I think you misunderstood me. Linux voyage has already been installed and runs perfectly. Since I'm a greenhorn in linux systems I wanted to know how to install tracker software at linux and which one to choose (Nowadays there is more than 1 tracker avaiable, but which one is best?)

    Oh, sry, it seems to read the google translation, I misunderstand your core problem.
    I see, the CPU on the Alix board is AMD Geode, and 586 compatible. But I think there will be problem with the linux tracker to compiled on another x86 machine, because the different harware architecture, for example the serial port. You will need serial port support, it is shure.

    The path to make a ruuning version to install a development environment on your board, and make the compilation on it. I use the vers 23 on my system.
    If you want o check this problem personally, I send you my running version in personal mail. You can accees me on hg5apz at gmail.
    t.janos

    I didn't understand what's the real point. What I understood is that I will have to compile the software on my own at my alix board because the compiled software is not made for my architecture?

    Den Linux Tracker muss man selber kompilieren. Linux Voyage basiert ja scheinbar auf Debian, der ALIX-PC auf x86.

    Erstmal brauchst Du die benötigten Programme zum kompilieren. Alle Linux-Distributionen benutzen Paketmanager, mit denen man recht einfach Programme installieren und löschen kann. Unter Debian ist das APT. Folgendes Kommando sollte die benötigten Pakete fürs kompilieren installieren:

    Code
    apt-get install build-essential

    Dann den Tracker herunterladen und compilieren. Wie das geht steht ganz oben im Quelltext:

    Code
    g++ -Wall -lm -o tracker_Linux tracker_Linux.c

    Anschließend solltest Du eine Datei tracker_Linux im selben Verzeichnis erhalten, deren Hilfe Du dann so aufrufen kannst:

    Code
    ./tracker_Linux -h

    Die nötigen Parameter musst Du Dir selber zusammenbasteln.

    Um den Tracker beim Hochfahren Deiner Kiste zu starten, brauchst Du die Datei von hier. Diese dann entsprechend editieren und unter beliebigem Namen im Verzeichnis /etc/init.d/ abspeichern und ausführbahr machen. Wenn die Datei "blitzortung" heiß, geht das mit

    Code
    chmod +x /etc/init.d/blitzortung

    Mit diesem Befehl sollte der Tracker im Hintergrund gestartet werden.

    Code
    /etc/init.d/blitzortung start


    Ob er wirklich im Hintergrund läuft am besten über die Logfiles oder mit ps aux überprüfen.

    Zu guter letzt noch folgender Befehl, so dass der Tracker auch beim hochfahren gestartet wird.

    Code
    update-rc.d blitzortung defaults

    Ich hoffe das reicht Dir als Crashkurs.

    Hi Guido

    Tobias described the steps for the compiling the Linux Tracker on your new linux. I add small notes here, about my more simple practice.
    I dont run continuously the tracker, but I start it mainly manually, when I am at my computer. So, I dont use the "standard" linux init process to run at start up the tracker. (This coontains the commands in Tobias description installing the "standard init script" from Blitzortung Miscell page, and the next 3 steps.) Ofcourse, this is the more confortable method to run this "service".

    Instead of this I have a small "batch file" starting when I need it, my sensor station. This is a normal text file, containing the choosed parameters which are confortable for my practice.
    Here is my example, based on Linux Tracker, ver. 23 paramateres:
    ./tracker23 -vo -vi -vl SiRF 19200 /dev/ttyS0 JanosTol [passwd]
    (You can write here your password in "open" text form (we dont use encripted password in this communication)

    This means:
    tracker23 -- this is the name of the actual version on my computer the Linux_Tracker ver 23. After the compiling you will find it in the name of tracker_toa, based on Egon compiling instruction: g++ -Wall -lm -o tracker_toa tracker_toa.cc

    -vo : verbose mode, write board output to stdout
    alternative: --verbose_output
    -vl : verbose mode, write log messages to stdout
    alternative: --verbose_log
    -vi : verbose mode, write system information to stdout
    alternative: --verbose_info

    Ofcourse, you can choose another combinations, but this working well for me.
    You need to choose your gps type (My is SiRF compat) the speed of serial line (19200 in my example) the "linux name" of the serial port, in this example the first port, its name in Windors terminology COM1, here /dev/ttyS0
    and for the authentication at our server side your Username and Password.

    If you are on SSH connection to your machine, you need to choose a simple text editor for example the pico is a good chioce to make this small file.
    If you dont want to play with linux char-mode text editors, the most simpe way to use the echo commad to create this file:

    echo "./tracker_toa -vo -vi -vl SiRF 19200 /dev/ttyS0 [YOUR_USERNAME] {YOUR_PASSWD]" > start-tracker

    After this on the directory where you are, will be create the file start-tracker with the contains in "..."

    You need to give running permission to it, as you can see in Tobias description:
    chmod +x tracker_toa

    check this with the "long list" command:
    ls -l
    (personal lesson here: to read output of the "man ls")

    You need to start this "batch file" in this way:
    ./start-tracker
    but in the place, where your program (tracker_toa) it is....

    In the test period you will start more than one time this programs, you need to check the runing state of it, because it use (occupy) the serial line, and this is not a good idea to use this "resource" from more then one program.
    For this you can use this commands:
    To check the running processes with this command:
    ps -x

    You will see a short info line about your program similar as:
    3660 pts/3 S+ 0:00 ./tracker23 -vo -vi -vl SiRF 19200 /dev/ttyS0 JanosTol ....
    For manually killing the runnig program, you need the "process id", the first number in this line, in this example 3660

    To kill immediatly this process used this command:

    kill -9 3660
    -9 means, it must be kill it by the system immediatly.

    I hope this small simple command descriptions help for you to start your program.

    best:
    t.janos

    Yes... I made a small mistake:
    dont mixt the 2 different programs in this example, as I made:

    1. first is the comliled program, this is the Egon,s Linux Tracker, actually the vers. 23. Its name after the compiling
    tracker_toa, in my "local" vesion its name is tracker23
    2. the created, one-line batch file, which after the given running permision become a running program under linux system, its name in this example start-tracker
    Ofcourse both need "running permision" but in the previous text I cited only Tobias example:

    chmod +x tracker_toa

    After this you need to use this comand to give running permission to the batch file too:
    chmod +x start-tracker

    If you start this pogram, dont forget to use the ./ characters before its name. It means the system canot search in "known path" this command, instead can start it from the actual place.
    If you put your compiled program in a "standard" place, known by the system, you dont need to use this ./ characters, at the beginning of name. The good choice for "standard place" for this programs the /usr/sbin dir.

    t.janos

    The version number 23 of tracker_Linux.c on the page "Miscellaneous" / "Verschiedenes" is wrong. If you look in the code, you can see version 24. If you have Firmware 29, you should use that newer version. There's no more limit in maximum strikes per one second (for interference mode), as this is now implemented in the Firmware itself (at least I think so).

    Tobias, you are right!
    I cheched the source of the recently avaiable tracker_Linux.c on Misc page, and the text around it... I would like to note here, it is not the best practice to keep different versions on the same filename... Ok, in this case, the general instruction, how to compile it can keep in the original, simple form.
    Another part of my story, I dont want to update to the new firmware version, because it is questinable (for me), will it be running without problems on my very old board version. Consequently I am not up-to-date the availabality and the features of the latest version of the linux tracker too.
    Sometimes I "scan" the available versions on the Download page, but not regularly.

    best:
    t.janos

    So, vielen Dank, soweit scheint das erstmal alles zu funktionieren. WLAN habe ich auch hinbekommen.

    Ich muss jetzt nur noch diese S20-Datei bearbeiten, mein System verlangt nämlich LSB-Tags für Boot-Scripte.

    Code
    insserv: warning: script 'blitzortung' missing LSB tags and overrides
insserv: There is a loop between service nocatsplash and blitzortung if stopped
insserv:  loop involving service blitzortung at depth 2
insserv:  loop involving service nocatsplash at depth 1
insserv: Stopping blitzortung depends on nocatsplash and therefore on system facility `$all' which can not be true!
insserv: exiting now without changing boot order!

    Wer das Problem auch mal haben sollte, folgendes einfügen in der Init-Datei (diese sei "blitzortung" genannt)

    Code
    ### BEGIN INIT INFO
# Provides: blitzortung
# Required-Start: $remote_fs $syslog
# Required-Stop: $remote_fs $syslog
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
# Short-Description: Start blitzortung tracker
# Description: Start blitzortung.org Linux tracker as daemon
### END INIT INFO

    So, nach einigen Quälereien mit Linux klappt nun alles, soeben rauschte das erste Datenpaket ins System. Ab jetzt kann ich nachst beruhigt meinen Laptop herunterfahren und 24/7 Blitze orten. Danke für eure Hilfe :)