If you need (as I do) multitab support in mintty, you can have it with the help of ... wait for it ... SCREEN!
It was always there but I haven't got this brilliant idea to use it.
Also, do not get fulled about the title as this works in any linux like environment.
Some of you already know that Windows zip combines several different functionalities:
- compression (like gzip),
- archiving multiple files into one (like tar),
- encryption (like gpg),
- plus some other.
Unix and Unix-like operating systems tend to split them so do not be surprised to have gzip for compression, tar for archiving files into one and gpg to encrypt.
I use Maintenance app to do some checks and cache cleanup from time to time. Today I got a message that my disk should be checked and repaired while in recovery.
So I did and I was surprised to find out this error while checking/repairing /: snap_metadata_val object: invalid extentref_tree_oid
Apparently this is related to local snapshots of time machine and one of them is in weird state indeed:
You know how to pull and create custom images; do whatever with them.
But if you need the same custom image on multiple servers in your network, you will have to copy that image on them. Here comes docker registry: a local repository of your images.
And the installation of a local repository is done via (guess?) a container :).
Basically, all you have to do is to pull the registry image and run a container on top of it. As simple as that!
So I finally got a bit into docker because everybody is talking about it.
I will pass over the installation part because it is not that difficult (easier than windows install actually: next, next, finish) and go straight to the interesting part: using docker commands.
I recently upgraded the debian version from 8 to 9 and my surprise was to not being able to connect to the newly upgraded server with my usual ssh key.
It turns out that beyond OpenSSH version 6.6, the "unsafe algorithms" have been removed, including my kinda old dss key.
All you have to do is to create a new one. I choose ecdsa: $ ssh-keygen -t ecdsa
Do not forget to put the newly pub key (e.g. the content of ~/.ssh/id_ecdsa.pub) in ~/.ssh/authorized_keys of the upgraded server.
Note: this does not removes the file. It only clears the content, which is very useful if you want to clear a log on which an application writes continuously. This will ensure the filesystem's space is cleared (especially when cleaning huge logs) and the log is still accessible by the application. PS C:\> Clear-Content file
Almost all operating system have command line commands. They are always there, even if we do not know about them.
Actually, the GUI programs that provide us ways to do things, like Disk Util for example, are just a graphical wrap over the command line tool. And they do not provide all the features.
Today, I will show you how to update your MacOS via command line. Benefits: you only need to restart once and the first phase of the installation can be done while you do your stuff so no need to wait for the progress bar to fill up and then reboot.
The error I got today was related to speedtest-cli:
Traceback (most recent call last):
File "/opt/local/bin/speedtest", line 6, in <module>
from pkg_resources import load_entry_point
ModuleNotFoundError: No module named 'pkg_resources'
The macports package speedtest-cli is a terminal port for the popular speedtest.net. The source is available here.
You have upgraded to macOS High Sierra and found this error while trying to upgrade macports via command line?
fmbp:~ florian$ sudo port -v selfupdate
Error: Current platform "darwin 17" does not match expected platform "darwin 16"
Error: If you upgraded your OS, please follow the migration instructions: https://trac.macports.org/wiki/Migration
OS platform mismatch
"mportinit ui_options global_options global_variations"
I had this problem the other day: my macbook pro was not sleeping when closing the lid.
I was 100% sure I have not modified any power settings nor installed new applications so I had to dig up a bit more.
Reading few websites about similar problems got me to a tool which helped me find the source of this problem.
The command pmset -g was showing me several applications that could prevent my system from going to sleep (line in red).