Menu with icons in Fedora 22/23

To enable menu icons in gnome-shell this command does the trick:

Tested under Fedora 22 and 23.

docker as normal user under Fedora 23

See https://docs.docker.com/v1.6/installation/fedora/

“The docker command line tool contacts the docker daemon process via a socket file /var/run/docker.sock owned by root:root. Though it’s recommended to use sudo for docker commands, if users wish to avoid it, an administrator can create a docker group, have it own /var/run/docker.sock, and add users to this group.”

Don’t forget to relogin to make this change take effect.

Install nvidia GTX980 driver in Fedora 23/22/21

I found a good and working tutorial unter http://www.if-not-true-then-false.com/2015/fedora-nvidia-guide/.

Here my notes for Fedora 23 and my GTX980:

 

Install Docker in Ubuntu 12.04 Precise

First make sure you have the latest version and an actual kernel running. Execute theses commands as root:

Then install docker with the following lines as root:

After this docker should be up and running. Rry using “docker ps” as root or with sudo.

docker on Linux Mint 17.2 Rafaela

There seem to be some missing dependencies in docker.io package. Here are the steps to get docker running in Linux Mint 17.2:

If you want to use docker as simple user you have to add this user to the docker group. Don’t forget to relogin if you add your actual user to a new group.

opensuse: nokogiri gem installation fails

Extracting libxml2-2.9.2.tar.gz into tmp/x86_64-suse-linux-gnu/ports/libxml2/2.9.2… OK
Running patch with /usr/lib64/ruby/gems/2.1.0/gems/nokogiri-1.6.6.2/ports/patches/libxml2/0001-Revert-Missing-initialization-for-the-catalog-module.patch…
Running ‘patch’ for libxml2 2.9.2… ERROR, review ‘/usr/lib64/ruby/gems/2.1.0/gems/nokogiri-1.6.6.2/ext/nokogiri/tmp/x86_64-suse-linux-gnu/ports/libxml2/2.9.2/patch.log’ to see what happened.
*** extconf.rb failed ***
Could not create Makefile due to some reason, probably lack of necessary
libraries and/or headers. Check the mkmf.log file for more details. You may
need configuration options.

The mentioned log tells us that patch executable is not installed. Fixed by:

 

How to access BeanManager in a JEE application

There are different ways to get a reference to javax.enterprise.inject.spi.BeanManager in an JEE application:

  • @Inject private BeanManager beanManager;
  • private BeanManager bm = javax.enterprise.inject.spi.CDI.current().getBeanManager();

Especially the second one can be very handy if you hit a part that doesn’t support CDI already.