Today I wanted to install a game 😀 but I needed some Windows libraries. I decided to fill them with winetricks and when I started the script I received the following bucket message –

$ ./winetricks
 wineserver not found!

Quite a fun situation and at the same time extremely obvious. Winetricks does not find the wineserver binary file. Generally normal because I use x64 Debian Linux and the packages I use are not from the official source. The solution is elementary in 2 steps

1. We find the path to the wineserver

$ locate wineserver

And we create a symbolic link to /usr/local/bin/wineserver where the script in question looks for the default file but in my case it is /usr/lib32/wine-unstable/wineserver

#ln -s /usr/lib32/wine-unstable/wineserver /usr/local/bin/wineserver

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 = 10k3JwZUXlc

Debian OpenLogo

Last day a friend wrote me that he had a problem with Debian your server. Exactly did not keep his sessions more than 30 minutes no matter how much is set session.gc_maxlifetime. In general, the problem is that Debian has decided to rewrite the behavior of the sessions as instead garbage collector-and a cron is started every 9th and 39th minute that clears the old sessions. Тои се намира в /etc/cron.d/php5

generally a simple script that starts / usr / lib / php5 / maxlifetime and contains the variable how long the life of the cookie is 1440 seconds or 24 minutes 😉 From now on there are 2 option or to stop the cron and thus stop the automatic cleaning which can later be reconfigured by php.ini or directly in the script to change the lifespan of the sessions with the variable max. I personally prefer the second option. It is much cleaner in general but there is a drawback – if the file is overwritten, our changes will be lost, which is an unpleasant fact.

ps. Now that you think about it, if you define another place to store your information via php itself, it should go beyond the scope of the script and thus be used again in a normal session without interrupting it roughly..

ini_set('session.gc_maxlifetime', 14400);
 ini_set('session.gc_probability', 1);
 ini_set('session.gc_divisor', 100);
 session_save_path(APP_PARENT_DIR . '/sessions');

Enhanced by Zemanta