A quick view at Electroneum binaries and how to use them

November 1, 2017 Leave a comment

As there are some uncertainties about how to use the Electroneum binaries for Linux, here is a quick view how they should look like:

electroneum-blockchain-export
electroneum-blockchain-import
electroneumd
electroneum-wallet-cli
electroneum-wallet-rpc

If you want to run these binaries, I suggest that you ALWAYS run in through a terminal. To start the binaries, change to the directory, where the files reside and run them with the command:
./FILENAME (where filename is for instance electroneumd or electroneum-wallet-cli)

There are two important binaries you have to run and use, first of all you have to run the electroneum daemon – named electroneumd.
You can set the log_level to 1 or even 2 which shows you a more detailed view what is going on.
set_log 1
This will update your blockchain (stored in /home/user/.electroneum

The second important file that you should run AFTER the blockchain is up to date (by running electroneumd) is electroneum-wallet-cli

By starting it the first time it will allow you to create a wallet. The wallet files will be stored in your current directory, handle them with care and backup them and do NOT forget your password.
Some commands which are interesting:
address (show your current adress)
balance (your current balance)
start_miner x (this starts the miner and the number of threads X - which is normally on a quadcore 1 to 4. 4 means, that all 4 cores of your CPU will be fully used)

Advertisements
Categories: Uncategorized

Build electroneum binaries from source

November 1, 2017 7 comments

In case your distribution will not run the electroneum binaries (0.11.0.0) – in my case it refused to download the blockchain, here a quick and dirty howto to build it on your distribution. First of all start electroneumd and type in: set_log 1 and watch if it downloads the blockchain or just refuses to do so.
If it does not download the blockchain, read on.

Only tested with Debian Stretch, should also work with all other Debian based distributions as Ubuntu.
I am not quite sure if all the dependencies have to be installed, but with these it built successfully.

1) Download the latest github .zip file and unzip it in a working directory
https://github.com/electroneum/electroneum

2) Open a terminal in the unzipped directory

3) Type in:
sudo apt-get update
sudo apt-get install build-essential cmake pkg-config libboost-all-dev libunbound-dev libminiupnpc-dev libunwind8-dev libldns-dev libexpat1-dev libgtest-dev doxygen graphviz

4) Run cmake:
cmake .

Watch closely if all the dependencies are met or if it informs you about missing dependencies – this is crucial. The error message about readline can be safely ignored.

5) Run make:
make

All the neccessary binaries will be in the /bin directory of the source-tree, you can simply copy them out in a desired directory, or do a make install. Electroneum binaries will create a directory named .electroneum in your home directory.

This is a quick and dirty post and will not be complete and might work in your case. Use this at your own risk.

Categories: Uncategorized

Ubuntu 11.10 Nautilus: Parent arrow gone – unfamiliar look.

October 16, 2011 3 comments

Yes, another thing I don´t like aobut 11.10. Nautilus look+feel has changed too. I was quite familiar with the old Nautilus way and could work very fast the way it was. Maybe I am just too lazy to learn these new “features” and user experience simplicity as they might call it. Again, I am looking for a way back to revert these changes.

First of all, it´s not possible to copy all of the old Nautilus behavior – the Parent folder arrow is still missing on the main screen. You can press ALT+UP Key to go to the parent folder – but what the heck is the reason to always get your fingers off the mouse and finger around on your keyboard ?

So, what is it I don´t like ?
1) The Tree view
2) The missing UP ARROW
3) The missing Folder view in the adress bar

So, this is the way it is out of the box in 11.10:
Old Nautilus look

And this is the result after a few modifications:
New old Nautilus

And here are the changes:

gsettings set org.gnome.nautilus.preferences always-use-location-entry false

This will change to folder view instead of folder adress.

Then View –> Side Panel –> Location
(not sure if this is location, if have another locale – just other than tree)

If you still have a tree view in the main window, then change to “symbols” in the main view Menu.

UPDATE:
Maybe take a look at pcmanfm (apt-get install pcmanfm) as an alternative to Nautilus as it looks very similiar to old Nautilus

Categories: Ubuntu Tags:

Classic Look on Ubuntu 11.10 – aka I want my Gnome classic back !

October 15, 2011 23 comments

I am not pleased at all with the new Unity and Gnome 3 look+feel Ubuntu has recently published when upgrading/installing Ubuntu 11.10. I find it uncomfortable, not intuitive and I generally don´t like the Look+Feel if you were used to Gnome2 without Unity. (which I disabled as soon as I got it running in 11.04)

Good news, there is a way back:

sudo apt-get install gnome-session-fallback

Logout, and choose Gnome Classic in the Login Screen.

The most noticable change is when you try to change the panel contents. Right clicking on the panel isn´t working anymore – but don´t panic. Just use ALT+Right Mouse and you can add/remove panel or content to the panel you were used to.

If I wouldn´t have noticed the way back to classic gnome look, I would have really considered leaving Ubuntu at all, though I was a very early user of Ubuntu – since it was released. If I would want a Smartphone Look+Feel on my desktop, I would buy one of those giant XXXL+ Android phones or tablets.

Update:
Well, I finally took the decision to bust Ubuntu. The Gnome 3 thing wasn´t the only reason, but my installed version was always an update from release to release – so it was pretty slow already. I switched to Linux Mint 11 and I will stay with this version for now, because Mint 12 will have gnome 3 too.
For all of those who especially don´t like Nautilus (see my other post on this blog) I found pcmanfm as an alternative – no clue if it works in Gnome 11.10 too. But it looks pretty similiar to Nautilus of gnome 2.x

Z68 Chipsatz Lan Probleme unter Ubuntu Linux 11.04 und Fedora

September 7, 2011 Leave a comment

Kürzlich habe ich festgestellt, dass ich extrem viele Packet-Drops bei der LAN-Verbindung meines PCs ins Internet habe, selbst die direkte Verbindung zum Router war kaum mehr möglich. Da diese Probleme nicht unter Windows aufgetreten sind, war mir klar, dass es ein Linux Problem ist.

Das Problem scheint darin zu bestehen, dass der Kernel irrtümlich den r8169 Treiber (also den Realtek Netzwerktreiber) anstatt des r8168B Treibers verwendet.
Barry Mavin hat hier eine Lösung erarbeitet, um den richtigen (r8168B) Treiber zu verwenden:

Original-Post:
http://www.foxhop.net/realtek-dropping-packets-on-linux-ubuntu-and-fedora

  • Überprüfen, ob wirklich der falsche Treiber geladen wurde:

    lsmod | grep r8169
    sollte in etwa zu dem Ergebnis führen:
    r8169 182616 0
    Dann ist das Problem in der Tat der falsche Treiber !

  • Den R8168B Linux Treiber downloaden und entpacken:

    wget http://www.foxhop.net/attachment/r8168-8.023.00.tar.bz2
    tar vjxf r8168-8.023.00.tar.bz2

  • Den Treiber unloaden:

    sudo rmmod r8169

  • Den Treiber selbst installieren:

    cd r8168-8.023.00
    sudo ./autorun.sh

  • Nun müßte ein:

    lsmod | grep r8168 so etwas darstellen:
    r8168 182616 0

  • Nun sollte man die Verbindung neu herstellen, falls dies manuell geschieht, aber OHNE den PC neuzustarten. Hat das Compilen des neuen Moduls funktioniert, das Surfen bzw. ping zeigt keine Packet-Losses mehr, dann, auch nur dann den übernächsten Schritt vollziehen, ansonsten den Treiber:

    cd /lib/modules/2.6.x-x-x/kernel/drivers/net/
    sudo mv r8169.bak r8169.ko

    wieder in den Originalzustand versetzen, um das anderweitige Problem festzustellen.

  • Abschließend noch den falschen Treiber daran hindern , wieder geladen zu werden:
    (wenn das Compilieren ohne Fehlermeldung funktioniert hat bzw. die Verbindung jetzt stabil ist – ansonsten SIEHE OBEN!!!!!)


    sudo su
    echo "blacklist r8169" >> /etc/modprobe.d/blacklist.conf
    exit

Die Verbindung ist jetzt absolut stabil und das Problem mit den Packet-Losses ist Gschichte !

Update: Seit dem Update auf kernel 3.x.x funktioniert der Treiber nicht mehr richtig. Um das zu berichtigen, die Datei src/Makefile im Editor öffnen und die Zeile:


KEXT := $(shell echo $(KVER) | sed -ne 's/^2\.[567]\..*/k/p')o

mittels # am Anfang auskommentieren, und darunter diese Zeile hinzufügen:

KEXT := $(shell echo $(KVER) | sed -ne 's/^[23]\.[0123456789]\..*/k/p')o

Somit sollte auch das Compilieren mit dem Kernel 3.x.x funkionieren!

Categories: Ubuntu

Ubuntu Taschenrechner – Komma funktioniert nicht

June 10, 2011 3 comments

Beim gcalculator (dem systemeigenen Taschenrechner von Gnome) in Ubuntu 11.04 habe ich kürzlich entdeckt, dass er keine Kommas über das Numpad akzeptiert, sondern nur umständlich über die “Punkt” Taste.

Dieser Bug ist nicht neu und laut bugreports hängt er mit der deutschen locale zusammen. Obwohl der Eintrag schon aus 2009 war und als gelöst markiert wurde, tritt er scheinbar wieder bzw. sporadisch auf.

Dazu ein einfacher Workaround:
Menü —> Einstellungen –> Tastatur

Im Belegungen-Reiter auf Optionen —> Belegungsauswahl des Nummernblocks —> Veraltet

Damit sollte das Komma wieder wie gewohnt funktionieren.

Categories: Good to know, Ubuntu

Convert Videos for the Nokia 5230 (and Nokia 5800)

March 16, 2010 3 comments

I recently purchased a Nokia 5230 and looked for a way to convert videos using Ubuntu.

There are plenty of free and unfree solutions in Windows for conversion (which didn´t work very well for me). So, there is an easy way in Ubuntu 9.10 which produces vids with nice quality both in video and sound in full resolution, which is 640x360px for the Nokia 5230.

I am using ffmpeg via console – it´s fast, very flexible and exactly does what it should do.

The command goes like this:

ffmpeg -i SOURCEFILE -f mp4 -vcodec libxvid -s 640x360 -b 768kb -r 25 -aspect 16:9 -acodec libfaac -ab 96kb -ar 44100 -ac 2 DESTINATIONFILE

That´s it. SOURCEFILE is the name of the video you are planning to encode, DESTINATIONFILE is the name of the vid you are expecting.

I put this command in a very simple (and primimtive) bash script:

Read more…