Tux, as originally drawn by Larry Ewing

Image via Wikipedia

Today I am thinking a little more about this perversion of nature CentOS. Inspired by the recently released CentOS 6 version, I have something to say. In itself, this nonsense is a development RedHat and is a server fork on their Red Had Enterprise Linux. Uses their rpm package manager (which is terribly great, yes but no).

Let me start with what made me start writing and thinking about what a freak this CentOS is and is there any ground in my servers. About a week ago, Veris came out 6 and I decided to update my current one 5.6 installation of our VPS hosting. I was quite unpleasantly surprised to see, that it did not report my update packages. I decided, that something I'm wrong and checked on the Internet. I was shocked to see the manufacturer's recommendation is to do a clean installation and distributive upgrade from 5.6 is not recommended and is done with a kilo of black magic and therefore not possible in the standard way. Hmmm, quite an interesting moment. 😆 And this is an enterprise distribution, very interesting. I don't see how he can even rank in this category except, that the manufacturer and put that loud name. Let's accept the following 2 script – one is doing a new install the other is not doing.

1. Scripts – I download the server, unplug it, it stops all the services it supports. I'm installing it for 1 an hour or more the business I work for suffers great losses as money. I'm losing my job as a system administrator, probably or I'll take hefty fines. Not to comment on all the hassle along with the settings and the correct archive of data and settings. The result of herniated nerves is that we have a clean system. Obviously, the option is not acceptable.

2. Scripts – We don't do a distribution upgrade, the system stays that way while security patches are running. Until at some point its maintenance is stopped, after a while it is hacked due to a breach in one of the services it offers., due to the inability to provide a distributive upgrade. Data is stolen or just the server is compromised – salty fines again or you lose your job.

Доста интересно и двата сценария завършват доста неприятно за системния им администратор заради капитална греша в дизайна на дистрибуцията подбора и мързела на компанията която я разработва за да не осигури съвместимост между пакетите. While on the other hand there are not so many enterprise distributions that are upgraded quietly and gently, without bearing loud names. I have Debian server which is from version 3 upgraded to the current version 6 he is currently experiencing 3 major upgrades and there was no denial of access to services. In principle, one of the main principles of the admin is – “If it works, it does not touch” but that's why people find holes, they patch, that's why new packages come out to improve stability or speed up productivity. In conclusion, apart from my personal opinion, but also the opinion of many of my friends, where CenOS is better than me is not worth it.

Enhanced by Zemanta

BackTrack 5 was issued on May 10th. For the first time an official version with Gnome probably the pressure of society said its word 🙂 and due to this fact I decided to install it on my EEE 1000H. After all, Gnome is my favorite graphical environment . Just like the 4th version again, the current one is based on Ubuntu 10.04LTS. Which, in my opinion, is not a disadvantage, let's say the target group is lama hahori 😀 . As usual the basic network manager is wicd, which is generally quite pleasant at least in my opinion it is preferred ( when I need 😉 ), but the eee bugs me that it can't connect to unencrypted wireless networks. Quite unpleasant definitely, with your normal Gnome network manager this problem is absent. The situation is already clear, I have a problem and I have a solution.

In general, I will not focus on the installation and removal of the main pitfall that will happen.. Otherwise the previous ones 2 операции по стандартния начин с apt-get или през synaptic както ви е най комфортно. Така споменах за подводен камък и тои е следния заради съдържанието в /etc/network/interfaces network-manager-a не може да инициализира мрежовите ви адаптери. Необходимо е да за коментирате всичко излишно, включително настройките с IP адреси. След като изчистих съдържанието на моя се получи нещо такова

auto loe th0 wlan0
allow-hotplug wlan0
allow-hotplug eth0

По този начин се решава проблема с не работещия network manager.

Enhanced by Zemanta