On recent Fedora versions, it should works out of the box: you plug the phone, the system detects it and opens a file explorer allowing you to browse your device’s content. However, if for some reason you want to mount the phone using simple-mtpfs, you can proceed as follow. Install simple-mtpfs $ dnf install simple-mtpfs Note : you also need the packages fuse fuse-libs libmtp, but chances are that they are already installed on your system.
Article updated the 17th of August 2015, with the remarks of Giacomo Orlandi in the comments, who provided a cleaner way to update the systemd config, based on a discussion in this Docker’s Github issue. If you upgraded (or fresh-installed) your box to Ubuntu 15.04, you may have noticed that the Docker daemon is not using the configuration defined in /etc/default/docker anymore. That is due to the fact that Ubuntu is now using systemd instead of Upstart/SysV.
Prepare your docker host (with docker-machine) First step is to have a docker-ready server. We have several ways of doing that: we can install docker on our server by hand (from packages, from source, using docker.io neat curl|sh, …), we can use boot2docker, or we can user docker machine to directly provision a server for us. We’ll do the later as it’s reeeaallly easy, with Virtualbox as provider. You’ll need to have Virtualbox installed on your machine.
We saw earlier how to configure the proxy for docker on Ubuntu 14.04, let’s now see how to do that on CentOS 7. Edit /etc/sysconfig/docker and add the following lines: HTTP_PROXY='http://user:password@proxy-host:proxy-port' HTTPS_PROXY='http://user:password@proxy-host:proxy-port' For those settings to be taken into account, you’ll need to restart your docker daemon: # systemctl restart docker You may still need to declare the proxy in the Dockerfile too, as seen in the Ubuntu article.
If you’re behind a proxy, chances are that docker is failing to build your containers, as it is not able to pull base images, and commands in the Dockerfile that need to access the internet are failing. Let’s see how to fix that. Edit /etc/defaults/docker.io and add the following lines: export http_proxy='http://user:password@proxy-host:proxy-port' For those settings to be taken into account, you’ll have to restart your docker daemon: $ sudo service docker.io restart This should allow docker daemon to pull images from the central registry.
If you’re using a web based tool to manage your servers, chances are that this tool is providing ssh:// links to connect directly to those server with one click from your web browser. Let’s see how to setup Ubuntu 14.04 so it can handle this type of link. First we need a script which is able to process a string like “ssh://user@host:port”. Create a file named ssh-handler.sh somewhere in your home directory (ie.
When SSH’ing to old boxes within tmux, I sometimes get the following error: 'screen-256color': unknown terminal type, and a very ugly prompt. An easy way to fix this is to set a different value for the default-terminal setting in your tmux.conf. You only have to open your ~/.tmux.conf and add the following line: set -g default-terminal "xterm" However, note that this will affect all your sessions. If you don’t want to redefine your default-terminal value, you can fix this only when needed by setting a different value for the TERM variable when you ssh to those boxes.
Let’s assume you started a new project. You’re using Git for versionning, because it’s easy to set it up locally, and for a few hours/days/weeks you’re just happy with your local repository. However, now you need to go bigger and start sharing the code with your coworkers, or maybe want to setup a continuous integration system, or whatever else, and for that your need to create a remote repository which will act as reference for all the actors of your project.
If you need to access a git repository somewhere on the internet (let’s say on GihHub) from your workstation which is inside your corporate network, chances are that you’ll need to go through an HTTP proxy. Let’s see how we can configure that. Option 1 : Environment variables Git honor the environment variables http_proxy and https_proxy, so one way of solving our problem is setting those variables as follow: http_proxy='http://proxy_host:proxy_port' https_proxy=$http_proxy If your proxy requires authentication, you need to specify your user/password in the URL: http_proxy='http://username:password@proxy_host:proxy_port' If you need more info about setting proxy info in your environment, check that article I wrote about that a few month back.
Sometimes when you download a video on the internet, you get subtitles on a separate file (ie. from Open Subtitles, Subscene, addic7ed, etc…), and they are not always perfectly sync’ed. If you’re using Media Player Classic, you can fix that pretty easily with its “Sub resync” feature. Open your video with Media Player Classic and load your subtitles, then hit ctrl + 6 (or View -> Subresync) to open the sub-resync console.