So after a few dist-upgrades, docker is not running anymore in my debian Jessie. A quick run of sudo service docker status shows me: ● docker.service - Docker Application Container Engine Loaded: loaded (/lib/systemd/system/docker.service; disabled; vendor preset: enabled) Active: failed (Result: exit-code) since Wed 2015-09-02 00:03:18 CEST; 8min ago Docs: https://docs.docker.com Process: 22770 ExecStart=/usr/bin/docker -d -H fd:// $DOCKER_OPTS (code=exited, status=1/FAILURE) Main PID: 22770 (code=exited, status=1/FAILURE) Sep 02 00:03:18 rowanto-mdeb systemd[1]: Started Docker Application Container Engine.

I use Debian Jessie, and I am the type who do this command frequently: sudo apt-get update && sudo apt-get dist-upgrade Now I am suffering from the consequences. The desktop is completely broken. I googled around, and there was nothing. So I thought something in my laptop is broken at first. Well, if you are a long enough linux user, this kind of stuff is kind of normal. It always happens once in a blue moon.

This is the first time I’m deploying stuff to elasticbeanstalk, and when I’m trying to deploy my private project, I realized the eb cli I download is the version 2 and has different syntax. I installed the version 3, and it seems like it can only be installed using python package manager pip. After installing it, this is what I get: rowanto@Rowanto-Deb ~ $ eb Traceback (most recent call last): File "/usr/local/bin/eb", line 9, in <module> load_entry_point('awsebcli==3.

In case you recently tried to update your debian system, and got an error related to libgdbm3 like this: Preparing to unpack .../libgdbm3_1.8.3-13+b1_i386.deb ... Unpacking libgdbm3:i386 (1.8.3-13+b1) over (1.8.3-13) ... dpkg: error processing archive /var/cache/apt/archives/libgdbm3_1.8.3-13+b1_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libgdbm3/changelog.Debian.gz', which is different from other instances of package libgdbm3:i386 Errors were encountered while processing: /var/cache/apt/archives/libgdbm3_1.8.3-13+b1_i386.deb E: Sub-process /usr/bin/dpkg returned an error code (1) You can fix this easily by deleting the libdgbm3 changelog file.

What is actually CVE-2014-6271? Actually redhat did a very good job describing it: https://access.redhat.com/articles/1200223 From what I’ve understood, it’s basically a bug that allows you in bash to do some other command after the function declaration in a variable. Let’s change the example a little bit, so that it’s more easier to read: env your_function='() { echo "your function do something";}; echo "but I can still add other command after your function"' bash -c "echo this is a test" If you system is affected with the bug, if you run that command, you will see the text “but I can still add other command after your function”.

So I have an ATI HD5xxx graphic card in my desktop personal computer. It’s a nice and quite fast card. It also has three display adapters: HDMI, DVI, DisplayPort. On my desk, there are two monitors. One of them have a DVI and a VGA adapter. The other however, only have VGA adapter. Do you see the problem here? My graphic card has no VGA adapter, because of this, I need to use some adapter, and because I used an adapter, the resolution of the monitor is not detected properly.

So it was when I was trying to install Skype on my brand new Debian 7 (Wheezy) when I encountered this problem: package architecture (i386) does not match system (amd64) Actually I was a little shocked. I just downloaded the Skype package for Debian from the official website then tried to install it normally using “dpkg -i ”, and it used to always work (normally). Actually I came from the rpm world (Fedora and CentOS) and have been only using Windows 8 for the past few months for my thesis, so I am actually wondering whether I’m the one who is a little out of date, or this is just a deb thingie, or I’m just too thick and dumb.