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. 😀 If I'm not mistaken Debian works best- 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

For a long time I had a lame problem on a server, that when the pppoe adapter fell off, it didn't hook itself. The decision, as usual, is trivial, it was just a matter of laziness and a few magical movements. 5 minutes


PPP_DEV=$(ifconfig | grep -c ppp)

if [ $PPP_DEV -gt 0 ]
 echo -e "\n PPPoE still connected \n"
 echo -e "\n PPPoE is dropped \n"

 if  ! ping -c 2 -q '' &> /dev/null
    /usr/sbin/pppoe-stop &
    sleep 4

 /usr/sbin/pppoe-start &

The script is absolutely spartan but it works. Otherwise, in principle, the slackware itself has an option in the conf of the pppoe to reconnect only when the line breaks down, but a chance.

Over the weekend I found time to play again with “favorite” my slackware or to be exact with a few slax derivatives 🙂 in general one was Backtrack3 and the other Language which our cattle plus two more that were not so interesting 🙂 . After the installation of both I noticed a very interesting problem 😉 when setting up static IPs the system was still firmly on DHCP. I'm checking rc.inet1.conf all right hmmmm. I start rc.inet1 my monkey starts again DHCP search for the corresponding LAN interface 😎 I quickly drew a script to pick them up automatically as I need, but curiosity gnaws at me, why 🙂 hmmmm I call this to look what's in rc.inet1 😮 completely new structure when looking at an angle quickly I see that things are not rosy at all or it has been quite modified by the authors of the distros or…. in Slax itself it comes like this (the second I will test it today). Overall, the solution to the problem was clear. I took one off rc.inet1 from slackware and everything falls into place. Later I will read why people have changed things like that and if there is something interesting I will add it here. Only for the orange I will add that our boy has done an extremely good job and my distro is suitable for desktop work and for beginners.

I haven't clicked for a while slackware so I have a little skill to lift and see what people have done 😉 I put it on 12.1 the last I believe and in general nothing surprising as always slaka was a stable and fast distribution 🙂 A lot of changes have been made for example it comes with the ntfs-3g driver built, they are glued to the lilac picture for a more beautiful 😉 black and white gray typical colors 🙂 In general, everything works as it should. Then I started looking for a package manager generally the choice was limited to slack-get and slackpkg. Following the advice of the old slacker ShadowX, I chose slackpkg, as he put it “slapt-get smells”, which I saw for myself 😉 managed to break the system extremely well with various packages 🙂 separately that it does not handle the names of the packages very well. In contrast, slackpkg works extremely correctly and flawlessly. Then the dilemma was which Gnome to install whether droplone or GSB in general I was advised to put dropline even though it is beta but I chose the second white from where it comes and my experience with slapt-get 🙂 generally the system broke and I had to rub with slackpkg hihihihi I will listen to the advice in the future 😉 In general its quite well done and everything works without bugs and errors in general it remains only to play a compiz to enjoy the colorful 😎 As a slack society has a tool good enough and reliable as apt without dealing with redundant compilations and filling in dependencies. I was extremely pleased and may rethink my favorite distro policy