While setting up my new developer VM I came to the point where I had to configure git again. As I keep on configuring git on several VMs and systems required for and provided by my clients, I thought it might be a good idea to create a small shell script which sets up my standard configuration.
Options I normally use are:
# Set username
git config user.name
# Set user email
git config user.email
# Set standard editor
git config core.editor
# Activate colors in output
git config color.ui true
# Some helpful aliases
git config alias.s status
git config alias.au '!git add -u && git status'
git config alias.spull 'svn rebase'
git config alias.spush 'svn dcommit'
Just experienced some weird behaviour on my fresh Oracle Enterprise Linux 6.5 installation. After installing a fresh VM I updated the system using system tools. Everything seemed fine until I rebooted the VM and started a new Gnome session. Unfortunately desktop icons were missing. The icons are normally provided by a nautilus process which starts on login. However, since the update nautilus kept being killed by signal 11 (SIGSEGV). Nevertheless, Gnome kept trying to open a new nautilus process which in ended up in a nautilus starting and killing spree 😉
In order to solve the problem I had a look at dmesg:
$ dmesg | tail
Within the output I found that not nautilus was the core problem but the librsvg library used by it. So I checked the software center application and found two versions:
After the first update process version 2.26.0-6.el6_5.2 was installed, so I tried 2.26.0-6.el6_5.3. Afterwards nautilus could start properly and the problem seems to be solved for the moment.
I just installed a fresh Oracle Linux 6.5. (64 Bit) development virtual machine for myself. One tool I learned to appreciate a lot is JD-GUI. Unfortunately, the binary provided does not run on a 64 Bit Linux (virtual) box as it was compiled for i686 architecture. However, in order to run it without any errors just install the following packages:
Due to my switch to Mac OS I started to use more and more virtual machines using VirtualBox. Recently I wanted to share some files between my host and Linux guest system. The route to take was VirtualBox’s shared folder feature. Setting up the shared folder was pretty easy, however when I wanted to access it I ran into some permission issues.
So I checked the folder permissions and found out that only root and the group vboxsf have access to this folder.
In order to solve my small access problem I just joint the vboxsf club 😉
Afterwards my access problems to the shared folder due to restrictive permissions were solved. You might have to logout and login again before the changes take effect.
In letzter Zeit störte mich häufig eine ärgerliche “System program problem detected” Nachricht. Diese kommt wohl von Crashreports die nicht korrekt gelöscht wurden. Daher versucht Ubuntu die Crashreports immer wieder zu senden. Folgender Befehl kann Abhilfe schaffen:
Ich habe kürzlich per Fernwartung das Distributionsupdate meines Servers mit do-release-upgrade durchführen wollen. Leider verlor ich natürlich die Netzwerkverbindung und war so aus dem Updatefenster rausgeworfen worden. Beim betrachten der aktiven Prozesse konnte ich jedoch sehen, dass es sehr wohl noch Updateprozesse und den Screen gab. Um den laufenden Screen wieder zu aktivieren, benutzte ich dann folgenden Befehl: