Názory k článku
Slackware Linux 12.0
-
anonymous (neregistrovaný)Ja som z toho trochu vedla. Doteraz slackware pouzival 2.4.x jadro a 2.6.x v testing/extra/experimental, ci ako sa to vola. Ani sa nenadame, vide RC1, o chvilocku RC2 a teraz FINAL verzia. Nezrychlili to tak trochu? A este mi nesedi jedna vec. Preco preboha presli az na 2.6.21.x? Ked napriklad debian ma v etchi 2.6.18.x. Fakt mi to nesedi a osobne by som na slackware 12 nepresiel, keby slapem na 11. A okrem ineho 2.4.x aspon nebol bordel ako je 2.6.x, ale na druhej strane musim uznat, ze zlepsenie je hlavne ohladne multimedii atd.
-
anonymníNo v 11.0 jsem pouzival 2.6.17 z extra, takze to na 2.6.21 az takovy skok nebude. Vsak starsi vydani jsou docela dlouho podporovany, pokud se nepletu. Takze neni problem pockat a kdyz to pujde bez problemu, tak povysit. Jinak je pro me oproti ostatnim distribucim rozhodujici predevsim ta stabilita a jednoduchost. Doufejme, ze se natom nic nemeni.
Keep Slack'in ;-) -
Viz changelog (http://slackware.com/changelog/current.php?cpu=i386):
Mon Nov 20 14:31:25 CST 2006
Thanks to everyone who provided valuable feedback on the question below. It
looks as if Slackware -current (future 12.0?) is going to charge into 2.6-only
territory, but it will be a conservative "charge". :-) The overwhelming
consensus is that the 2.6 series is now more than stable enough for production
use. Some folks expressed concern over the loss of Linux 2.4.x compatibility,
but they were a definite minority. Some suggested maintaining two -current
branches -- one following 2.4 and the other 2.6. The solution that'll be
taken concerning 2.4.x will be to make Slackware 11.0 better maintained than
simply security updates. It should see some other non-security updates as
well (perhaps the introduction of an /updates directory?), and will be a long
lived OS for those who swear by the stability of the 2.4.x kernel series.
Meanwhile, 2.4.x compatibility features (such as the, er, mess? going on in
the startup scripts) will be steadily eliminated in -current to focus on the
best possible 2.6.x support. With a lot of work, we should be able to make
the next Slackware release an excellent choice for both servers and desktops.
Again -- thanks for all the input! :-) -
Cm (neregistrovaný)No nevim, jestli 5. Ja davam na servery vyhradne Slack, protoze v nem na 100% vim, co se tam deje. Krasny a cisty init a diky absenci dependency hell mam jistotu, ze neprehlidnu nejakou neplechu pri upgradech. Cela strukruta systemu je "standardni" a konzervativni bez zadnych 'vychytavek' - ty dokazou poradne potrapit a u serveru muze byt velkou nevyhodou, kdyz system dela neco, o cem ani netusim.
Ze zacatku jsem na servery (hlavne na firewally) daval Vector linux (osekany slack). Minimalni instalace a ostatni pekne rucne - uptime v radu roku bey problemu. -
test (neregistrovaný)Dalsi duvod muze byt napriklad ten, ze Slackware je bezpecnejsi, nez Debilian. Take navic dodrzuje tradici KISS, obsahuje vse co na serveru potrebujete, nic co ne + autor Slackwaru je jen jeden, to znamena ze vsechny patche jednotlivych aplikaci jsou od nej stejne kvalitni. Kdezto u debianu je to hruza, co patch - to warning ci security hole. Mnoho tradicnich *NIXovych programu, bez kterych si zivot predstavit nedokazu na Debilianu proste jen tak nerozjedete, zacina to tim, ze nejsou v repozitari. Pokracuje to tak, ze po manualnim dohledani a rozbaleni nejdou zdrojove kody zkompilovat (binarky pro DEB nejsou funkcni), konci to zoufalou opravou zdrojovych kodu a prekopavani zavislosti. Priklad bude byt ntpd, nedavno byl pro zmenu problem s MySQL, protoze v Debilianu nekdo zmrsil knihovnu obsahujici funkcni CloseCursor() - proto neslo pomoci PHP provozovat PDO pro pristup k MySQL.
Security
-=-=-=-=-=
Slackware: http://secunia.com/product/13491/?task=statistics
Debilian: http://secunia.com/product/13844/?task=statistics -
test (neregistrovaný)Mimochodem problem s Debilianem a jeho zabugovanymi patchi lze vyresit pouze nasledovne: Download, Decompress, Patch & Compile manually source codes including all dependencies, make your package, install your package, Enjoy ! Zatimco ve Slackware nechybi ani jeden jediny tradicni *NIXovy nastroj a patche jsou tam precizni, ne zabugovane.
