Did you know, that you can be connected to the internet with a cable and still be in the wrong subnet? That’s what happened to me. I plugged in the cable and the internet worked. Or so I thought. Then I needed to download a file from a company internal location and the server was unreachable. But for my colleague it worked without problems. Mhm. Typo? My colleague sent me a link – no luck. DNS? I tried the IP directly – no luck. Restart? Advice from IT – but no luck.
After involving two more colleagues, we figured it out: There is a thing called 802.1x Security Authentication. Basically, after connecting to the internet, you still need to enter your user credentials to be allowed into the internal parts of the network. In my company’s case, they use PEAP. Apparently, Windows and Mac usually ask for the authentication automatically when connecting to a network that offers this method. Hence the advice by IT to restart. Well, Linux doesn’t ask. You need to know how to answer! When you know it, it’s easy: In Gnome activate the method under “Network Settings” – “Security”. You may need a certificate – ask your admins!
I learned something new today.
I use Linux in a corporate environment where Microsoft Office 365 is the toolchain of choice. One of the first things I needed to do my job was Microsoft Teams. Here are two things that worked for me.
The first (obvious) idea is to use the web UI. Messaging works out of the box with Chromium or Google Chrome. Getting audio and video calls to work is not obvious anymore. Basically, you need to pretend that you are on a Windows machine. This can be done by setting the “User Agent” to “Edge – Windows” with in the developer tools – see Christian Hujer’s blog post on the topic. Unfortunately, this hack breaks the message history. And there seems to be no way to get screen sharing to work. So while this solution is very easy, it is not optimal.
The second thing I tried and which works fine for me, is the unofficial MS Teams client by Ismael Martinez. I have it running on Ubuntu 18.04. As far as I have seen, everything works. Thank you!
If you want to give away a computer and you want to really delete the data on the hard drive, you can use
dd under Linux. Start a live linux from a USB drive (for example Ubuntu) on the computer where you want to erase the disk.
First, find out which partitions you have. A basic way of doing this is by using
sudo fdisk -l
Most distributions will have a graphical editor which makes it easier to see what is going on. In gnome this will be
gparted, in KDE
KDE partition manager. There are surely other tools around. But it does not really matter, all you need is to know the name of the partition which you want to erase. In my case it is
Now we will use
dd (“disk dump”) to write random information to this partition on top of the existing information. This is the command:
sudo dd if=/dev/urandom of=/dev/sda4 bs=65536 status=progress
of (“output file”) is the hard disk partition we want to write to. You do not want to mess up and take the wrong partition. The is no “undo”. Check this parameter twenty times. The parameter
if (“input file”) is used to set the data which should be written. In our case, we use
/dev/urandom which is a generator for random numbers.
status=progress will enable some output on the command line which tells us what is happening. If you forget this parameter, there will be no output and you will have no idea if 1 byte has been written in the last hour or 200 GB. Setting the block size (
bs) to something larger than the default 512 bytes is also very highly recommended. The difference in the time the command needs to run may be huge. I use 64k in the example which worked fine for me. If you want to determine the optimal block size for your system, I suggest this article: Tuning dd block size by Danny Guinther.
I just started my computer. Plasma did not start. I only saw the message “Could not start D-bus. Can you call qdbus-qt5?”. No. I cannot call this! I don’t have a working desktop!
What I managed to do was start a session with a different desktop environment and then search the internet for a solution. Will the error message, you will quickly find that “Anaconda update breaks KDE if it’s added to PATH”. Yes! I installed Anaconda the last time I used this computer! So I removed the lines it had added to my
.bashrc and everything worked again.
Note to self: Do not add Anaconda to your
PATH. Do not let it edit your
.bashrc (which it does when you use
conda init). Stupid snake!
server environments, one for port 80 (
http) and one for port 443 (
https). Have the
http environment do nothing but redirect to the other one:
server_name yesterdayscoffee.de www.yesterdayscoffee.de;
return 301 https://$server_name$request_uri;
listen 443 ssl;
listen [::]:443 ssl;
... all the rest of your configuration
First install Certbot on your computer using the instructions at https://certbot.eff.org/
Then you can create a certificate for the page
www.yesterdayscoffee.de (with and without
www) like this:
certbot -d yesterdayscoffee.de -d www.yesterdayscoffee.de --manual --preferred-challenges http certonly
During the proces, you will be asked to create a file with a specific content at a specific location on your web server (this is for the option
http, there are other ways of proving that you control the domain). Once you have done this and everything is fine, the certificate will be created.
The certificate consists of a bunch of files in a location the certbot tells you. You will probably need to put two files on the server: The private key in
privkey.pem and the certificate file
fullchain.pem. As a location, the folder
/etc/letsencrypt/live/ is suggested.
Now you have the certificate, the next step is to tell the web server to use them for your web page. We are using nginx with the configuration file for our web page
yesterdayscoffee.de at the default location
/etc/nginx/sites-available/. The only thing to do is to add the port 443 for the https protocol and specify the location of the certificate files. These are the lines:
listen 443 ssl;
listen [::]:443 ssl;
Restart nginx for the changes to take effect with:
sudo /etc/init.d/nginx restart
You may need to tell your firewall to open the https port for nginx:
sudo ufw allow 'Nginx HTTPS'
That’s it! Now it should work. Coming up: How to redirect
https and how to renew certificates (which with letsencrypt you have to do every 90 days).
After installing my brand new Kubuntu, I got the following error:
locale: Cannot set LC_ALL to default locale: No such file or directory
perl: warning: Setting locale failed.
Here is how to fix it.
The first step is to see the current settings with
locale. This should give an output similar to the following:
This output already might give you a hint about what is wrong. In my case, I have the entry
en_DE which looks fishy. The next step is, to see what locales are installed on your machine. This is done with the parameter
> locale -a
Here we already found the problem. The output does not contain the locale “en_DE”. In this case, it is because “en_DE” does not actually exist. I have no idea where it comes from. But somehow the combination of being in Germany and installing an English operating system caused it. So what I want to do is to set everything that has the wrong locale to the correct locale “de_DE” instead.
As the German locale is not installed on our system yet, we first have to create it. This is done with
> sudo locale-gen de_DE.utf8
Generating locales (this might take a while)...
Now we can set it as the default with the following:
sudo dpkg-reconfigure locales
You should restart the computer for the changes to take effect (just to be safe).
I have files copied from Windows computers in ancient times. The filenames contain special characters and they have been messed up somewhere along the way. For example I got a file named
9.5.2 Modelo de aceptaci??n (espa??ol).doc in the folder
9 Garant??a del Estado.
First, I want to find and list these files. Stackexchange tells us how to do that:
LC_ALL=C find . -name '*[! -~]*'
This will find all names that have non-ASCII letters, not only those that are broken. But in my case I have folders where ALL of the names are broken, so I don’t mind.
Second, I want to fix the names. I did it manually, but for future reference, if I ever were to do anything like that again, I might use one of the solutions proposed in this thread on serverfault.com.
Unison is a tool to compare and synchronize two folders. You can configure it by GUI, but at least for me (Kubuntu 18.04) not all settings work. Specifically, I cannot set the value “0”. But there is an easy way around the problem. Unison puts a file called
Profilename.prf (where “Profilename” should be replaced with the actual name of your profile) into the folder
.unison in your home directory. This is simply a text file with key-value pairs, that you can edit at your leisure.
Here are standard settings for comparing two directories without comparing the file permissions:
label = My first comparison
root = /home/test/FolderOne/
root = /home/test/FolderTwo/
perms = 0
dontchmod = true
Now for the coolest feature of Unison: It is written in OCaml!! OCaml was used in my third semester to teach functional programming. I remember clearly the teacher telling us about the “usefulness” of the language. She had one slide with examples of programs written in OCaml. And she must have looked very hard to find any. There were a grand total of three programs on the slide. Two formal logic resolvers or something to that effect (we were like “yeah, really useful”). And MLDonkey (peer-to-peer filesharing was BIG in those days before Netflix, Spotify and fast internet) which she clearly didn’t know what it was for. So now, if she still has that slide, I can add another program! And a really useful one at that!