It's been rolling over the past weekend TuxCon 2017. Most people think I've done pretty well with my lecture. Personally, I'm not entirely happy, there are definitely a lot of things to work on, because I plan not to have my last such event in the future. If I have to be honest about most of the presentation, I hardly remember it, it was like a trance. I remember sporadic moments when I look at my watch and find out, that a decent amount of time has elapsed.

It was definitely not easy, even with that in mind, that the audience was extremely narrowly focused and there was no big barrier with the audience.

 

One of the things that annoys me the most is when I copy / move a great director in cli I have no idea what percentage of the total size I have rolled over. Unfortunately, cp / mv do not have such forces and we have to resort to alternatives. There are a lot of possibilities, but I personally like the use of rsync instead of pc / mv. It has everything built-in – preserve rights over files and directories, progress bar as well as the ability to delete copied files.

In general, I did 2 alias that do more than wonderful work:

alias cpi='rsync -a --info=progress2'
alias mvi='rsync -a --info=progress2 --remove-source-files'

From time to time I have to use Bitcoin URI and when I need my client has not associated it is annoying, that I have to do everything by hand. The procedure is extremely trivial for the association in question. It can be synthesized in the following 5 points

  1. Open your address bar about:config
  2. Create a new boolean key (right-click clip -> new -> boolean)
  3. Enter a name: network.protocol-handler.expose.bitcoin
  4. Select a false value
  5. The next time you click on the Bitcoin URI you will be asked to choose the path to your Bitcoin client. Be sure it has enforceable rights.

I personally use MultiBit the customer who has all the necessary functionality and is agile enough

When you make the RAID layer above it, do it on the LVM, so you will save a lot of trouble if you set not very well estimated partition sizes.. The idea is that if you don't use XFS or ZFS or some other FS that allows resizing partitions like EXT2 / 3/4 for example things become a big hassle when you realize, that you didn't do the most- good division. In general, you get maximum plasticity if you need to reduce or increase the size of the partition and at the same time you are protected against unpleasant events of your data. In general, something of this kind is obtained

| / | /var | /usr | /home  |
 --------------------------
|       LVM Volume         |
 --------------------------
|       RAID Volume        |
 --------------------------
| Disk 1 | Disk 2 | Disk 3 | 

In the last few days we have been talking to a friend sis admin the egg or hen type – Debian vs Slackware. As usual when we debate with him there is no winner I love my religion he his, we both have enough reasons to do so. But in addition to all the chatter, I wondered again why. Why I use Debian on desktop and desktop servers ( I had even run a chroot on my android). Here I also remember the statement of one of my former bosses:

Do you know which is the best Linux?

– The one you managed to install first.

In the interest of truth Slackware 9 I think it was my first distribution that I installed myself 😀 But things are changing. So here are some of my reasons why Debian:

1. Because it is easy to maintain – the dependencies between the packages. I give this is the obvious minus of slackware or the plus depends on how it is viewed. The dependencies between the packages is “extra” which greatly facilitates the installation, maintenance and management of a system. When I want to install php I don't need to know if I have the other libraries needed to run normally. I remember a case a few years ago when I installed on a web server and all the trouble while filling in the dependencies to compile the necessary modules on the php. Dam on the other hand you get a binary package compiled with some options that may not work properly for your case or just lack the necessary options. There is an Emmy for this case apt-get source you pull your sorsk from which the package is built plus all the patches that are put. Modifications and moderations are always possible by personal taste and discretion.

2. Because there is a netinstall cd – minimal image with basic packages. I'm a little surprised how useful it would be for new users, but for any system administrator the minimum installation is an advantage.. Few packages are installed, few service stations. The system is built almost from 0. This way you are sure that it will work exactly the way you expect – neither a little nor more. A few days ago I wanted to download slackware cd1 for x64 system and I was unpleasantly surprised that there is only a dvd version of their x64 version. Only for x86 there is an option to download cd1 enough for minimal installation. Not that it is a pain to die during the installation will select the necessary packages but still a whole dvd for the skeleton of a server 😀 WTF??? Debian netinstall image offers you the opportunity to choose again what additional packages to download from the Internet as a positive is, that they will be the latest version in the mirror stable / testing / unstable.

3. Because there is a super basic installer – the console is not scary. Things are few here 50/50 because Slackware also has an extremely easy installer with the only exception which is the key partitioning of the disk it is necessary to write a few commands in the console which is scary for some users. fdisck or cfdisk are not so scary but the fact that it is not built into the installer is in itself a drawback. Once created, the partition is then formatted by the installer, but by then you should have read a bit. With Debian, things are easier in this regard, by default the installer helps you with this , but if you want to control the process more closely, you can always call the shell.

4. Because the debian team are open to strange ideas. Hmmm, some slacker here would laugh at me rudely, that such nonsense as cross-linux with BSD kernel is not needed, but why not. People used to laugh at the claim that, the earth is rounded. 😀 Ако не се лъжа Debian работи на най- large collection of hardware 😉

5. Not with KDE by default – we really hate KDE. And as you know, Patrick is a big supporter of KDE and this has always been the default graphical environment in Slack.. From my first meeting with KDE, I realized that this is not my type of GUI, among other things, it reminded me a lot of Windows

http://www.youtube.com/watch?v = 10k3JwZUXlc