{"id":38929,"date":"2019-10-31T22:26:48","date_gmt":"2019-10-31T19:26:48","guid":{"rendered":"https:\/\/prohoster.info\/blog\/linux-mnogolikij-kak-rabotat-na-lyubom-distributive\/"},"modified":"2019-10-31T22:26:48","modified_gmt":"2019-10-31T19:26:48","slug":"linux-mnogolikij-kak-rabotat-na-lyubom-distributive","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/linux-mnogolikij-kak-rabotat-na-lyubom-distributive","title":{"rendered":"Linux shum\u00ebform\u00ebsh: si t\u00eb punoni me \u00e7do distribucion","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p><img decoding=\"async\" alt=\"Linux shum\u00ebform\u00ebsh: si t\u00eb punoni me \u00e7do distribucion\" src=\"\/wp-content\/uploads\/2019\/10\/ee1aaad566204532c974a3ce8f13b915.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nKrijimi i nj\u00eb aplikacioni p\u00ebr backup q\u00eb funksionon n\u00eb \u00e7do distribucion \u00ebsht\u00eb nj\u00eb sfid\u00eb e v\u00ebshtir\u00eb. P\u00ebr t\u00eb garantuar funksionimin e Veeam Agent p\u00ebr Linux n\u00eb distribucionet nga Red Hat 6 dhe Debian 6, deri n\u00eb OpenSUSE 15.1 dhe Ubuntu 19.04, duhet t\u00eb zgjidhen nj\u00eb s\u00ebr\u00eb problemesh, sidomos duke pasur parasysh se produkti p\u00ebrmban nj\u00eb moduli t\u00eb b\u00ebrtham\u00ebs.<\/p>\n<p>Artikulli \u00ebsht\u00eb krijuar sipas materialeve t\u00eb prezantimit n\u00eb konferenc\u00ebn <noindex><a rel=\"nofollow\" href=\"https:\/\/linuxpiter.com\/materials\/2636\"> LinuxPiter 2019<\/a><\/noindex>.<br \/>\n<noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><br \/>\nLinux-i nuk \u00ebsht\u00eb vet\u00ebm nj\u00eb nga sistemet operative m\u00eb t\u00eb njohura. N\u00eb thelb, \u00ebsht\u00eb nj\u00eb platform\u00eb mbi t\u00eb cil\u00ebn mund t\u00eb krijoni di\u00e7ka unike, di\u00e7ka tuaj\u00ebn. Fal\u00eb k\u00ebsaj, Linux ka shum\u00eb distribuime q\u00eb dallohen p\u00ebr nga grupi i komponenteve programore. Dhe k\u00ebtu lind problemi: p\u00ebr t\u00eb siguruar q\u00eb produkti programor t\u00eb funksionoj\u00eb n\u00eb \u00e7do distribucion, \u00ebsht\u00eb e nevojshme t\u00eb merren n\u00eb konsiderat\u00eb ve\u00e7orit\u00eb e secilit.<\/p>\n<h2>Menaxher\u00ebt e paketave. .deb vs .rpm<\/h2>\n<p>\nLe t\u00eb fillojm\u00eb me problemin e duksh\u00ebm t\u00eb p\u00ebrhapjes s\u00eb produktit p\u00ebr distribuime t\u00eb ndryshme.<br \/>\nM\u00ebnyra m\u00eb tipike e shp\u00ebrndarjes s\u00eb produkteve programore \u00ebsht\u00eb t\u00eb ngarkohet nj\u00eb paket\u00eb n\u00eb nj\u00eb depo, n\u00eb m\u00ebnyr\u00eb q\u00eb menaxheri i paketave e nd\u00ebrtuar n\u00eb sistem t\u00eb mund ta instaloje at\u00eb nga aty.<br \/>\nMegjithat\u00eb, formatet e njohura t\u00eb paketave jan\u00eb dy: <i>rpm<\/i> dhe <i>deb<\/i>. K\u00ebshtu, do t\u00eb duhet t\u00eb mb\u00ebshtetet \u00e7do nj\u00eb.<\/p>\n<p>N\u00eb bot\u00ebn e paketave deb, niveli i p\u00ebrputhshm\u00ebris\u00eb \u00ebsht\u00eb mbres\u00ebl\u00ebn\u00ebse. I nj\u00ebjti paket\u00eb instalohet dhe funksionon po nj\u00ebsoj mir\u00eb si n\u00eb Debian 6 ashtu edhe n\u00eb Ubuntu 19.04. Standardet e procesit t\u00eb nd\u00ebrtimit t\u00eb paketimeve dhe pun\u00ebs me to, t\u00eb vendosura n\u00eb distribuime t\u00eb vjetra Debian, mbeten aktuale edhe n\u00eb distribucionet m\u00eb moderne si Linux Mint dhe elementary OS. Prandaj, p\u00ebr Veeam Agent p\u00ebr Linux, mjafton nj\u00eb paket\u00eb deb p\u00ebr \u00e7do platform\u00eb harduerike.<\/p>\n<p>Nd\u00ebrsa n\u00eb bot\u00ebn e paketave rpm, dallimet jan\u00eb t\u00eb m\u00ebdha. S\u00eb pari, p\u00ebr shkak se ekzistojn\u00eb dy distributora krejt\u00ebsisht t\u00eb pavarur, Red Hat dhe SUSE, p\u00ebr t\u00eb cil\u00ebt nuk nevojitet p\u00ebrputhshm\u00ebri. S\u00eb dyti, k\u00ebta distributora kan\u00eb distribuime me mb\u00ebshtetje teknike dhe eksperimentale. Midis tyre, p\u00ebrputhshm\u00ebria gjithashtu nuk \u00ebsht\u00eb e nevojshme. Kemi p\u00ebrfunduar se p\u00ebr el6, el7 dhe el8 ka paketat e veta. Nj\u00eb paket\u00eb e ve\u00e7ant\u00eb p\u00ebr Fedora. Paketat p\u00ebr SLES11 dhe 12 dhe nj\u00eb e ve\u00e7ant\u00eb p\u00ebr openSUSE. Problemi kryesor \u00ebsht\u00eb n\u00eb var\u00ebsit\u00eb dhe emrat e paketave. <\/p>\n<h2>Problemi i var\u00ebsive<\/h2>\n<p>\nP\u00ebr fat t\u00eb keq, shum\u00eb her\u00eb paketat e nj\u00ebjta shfaqen me emra t\u00eb ndrysh\u00ebm n\u00eb distribuime t\u00eb ndryshme. M\u00eb posht\u00eb \u00ebsht\u00eb nj\u00eb list\u00eb e pak\u00ebt e var\u00ebsive t\u00eb paket\u00ebs veeam.<\/p>\n<p>P\u00ebr EL7:<br \/>\nP\u00ebr SLES 12:<\/p>\n<ul>\n<li>libblkid<\/li>\n<li>libgcc<\/li>\n<li>libstdc++<\/li>\n<li>ncurses-libs<\/li>\n<li>fuse-libs<\/li>\n<li>file-libs<\/li>\n<li>veeamsnap = 3.0.2.1185<\/li>\n<\/ul>\n<ul>\n<li>libblkid1<\/li>\n<li>libgcc_s1<\/li>\n<li>libstdc++6<\/li>\n<li>libmagic1<\/li>\n<li>libfuse2<\/li>\n<li>veeamsnap-kmp = 3.0.2.1185<\/li>\n<\/ul>\n<p>\nSi pasoj\u00eb, lista e var\u00ebsive rezulton t\u00eb jet\u00eb unik p\u00ebr shp\u00ebrndarjen. <\/p>\n<p>Ka raste kur nj\u00eb version i ri i p\u00ebrdit\u00ebsuar fshihet pas emrit t\u00eb vjet\u00ebr t\u00eb paket\u00ebs. <\/p>\n<p><b>Shembulli:<\/b><\/p>\n<p>N\u00eb Fedora 24, paketa u p\u00ebrdit\u00ebsua <i>ncurses<\/i> nga versioni 5 n\u00eb versionin 6. Produkti yn\u00eb \u00ebsht\u00eb nd\u00ebrtuar pik\u00ebrisht me versionin 5, p\u00ebr t\u00eb siguruar p\u00ebrputhshm\u00ebri me shp\u00ebrndarjet m\u00eb t\u00eb vjetra. P\u00ebr t\u00eb p\u00ebrdorur versionin e vjet\u00ebr 5 t\u00eb bibliotek\u00ebs n\u00eb Fedora 24, duhej t\u00eb p\u00ebrdorej paketa <i>ncurses-compat-libs<\/i>. <\/p>\n<p>Si pasoj\u00eb, p\u00ebr Fedora shfaqen dy paketa, me var\u00ebsi t\u00eb ndryshme. <\/p>\n<p>M\u00eb pas b\u00ebhet m\u00eb interesante. Pas p\u00ebrdit\u00ebsimit t\u00eb fundit t\u00eb shp\u00ebrndarjes, paketa <i>ncurses-compat-libs<\/i> me versionin 5 t\u00eb bibliotek\u00ebs nuk \u00ebsht\u00eb e dispozueshme. P\u00ebr distributorin \u00ebsht\u00eb nj\u00eb ngarkes\u00eb p\u00ebr t\u00eb sjell\u00eb bibliotekat e vjetra n\u00eb versionin e ri t\u00eb shp\u00ebrndarjes. Pas nj\u00eb kohe, problemi u p\u00ebrs\u00ebrit edhe n\u00eb shp\u00ebrndarjet SUSE.<\/p>\n<p>Si pasoj\u00eb, p\u00ebr disa shp\u00ebrndarje duhej t\u00eb heqeshim dor\u00eb nga var\u00ebsia e qart\u00eb nga <i>ncurses-libs<\/i>, dhe produkti u p\u00ebrmir\u00ebsua n\u00eb m\u00ebnyr\u00eb q\u00eb t\u00eb funksiononte me \u00e7do version t\u00eb bibliotek\u00ebs.<\/p>\n<p>P\u00ebr m\u00eb tep\u00ebr, n\u00eb versionin 8 t\u00eb Red Hat nuk ka m\u00eb paket\u00ebn meta <i>python<\/i>, e cila referohej n\u00eb t\u00eb vjetrin e mir\u00eb <i>python 2.7<\/i>. Ka <i>python2<\/i> dhe <i>python<\/i>3. <\/p>\n<h2>Alternativa p\u00ebr menaxher\u00ebt e pakot<\/h2>\n<p>\nProblemi me var\u00ebsit\u00eb \u00ebsht\u00eb i vjet\u00ebr dhe prej koh\u00ebsh i duksh\u00ebm. Kujtojm\u00eb pak nga concepti Dependency hell. <br \/>\nT\u00eb bashkosh bibliotekat dhe aplikacionet n\u00eb nj\u00eb m\u00ebnyr\u00eb q\u00eb t\u00eb gjitha t\u00eb funksionojn\u00eb q\u00ebndrojn\u00eb pa probleme dhe pa konflikt \u2013 kjo \u00ebsht\u00eb detyra q\u00eb \u00e7do distributor Linux p\u00ebrpiqet ta zgjidh\u00eb.<\/p>\n<p>Tejet ndryshe e trajton k\u00ebt\u00eb problem menaxheri i pakove <b>Snappy<\/b> i Canonical. Ideja kryesore: aplikacioni ekzekutohet n\u00eb nj\u00eb r\u00ebr\u00eb t\u00eb izoluar dhe t\u00eb mbrojtur nga sistemi kryesor. N\u00ebse aplikacionit i nevojiten biblioteka, ato ofrohen s\u00eb bashku me vet\u00eb aplikacionin.<\/p>\n<p><b>Flatpak<\/b> po ashtu lejon ekzekutimin e aplikacioneve n\u00eb r\u00ebr\u00eb duke p\u00ebrdorur Linux Containers. Ideja e r\u00ebr\u00ebs p\u00ebrdoret gjithashtu nga <b>AppImage<\/b>.<\/p>\n<p>K\u00ebto zgjidhje lejojn\u00eb krijimin e nj\u00eb pakete p\u00ebr \u00e7do shp\u00ebrndarje. N\u00eb rastin me <b>Flatpak<\/b> instalimi dhe ekzekutimi i aplikacionit \u00ebsht\u00eb i mundur edhe pa dijen e administratorit.<\/p>\n<p>Problemi kryesor \u00ebsht\u00eb q\u00eb jo t\u00eb gjitha aplikacionet mund t\u00eb funksionojn\u00eb n\u00eb r\u00ebr\u00eb. Disa kan\u00eb nevoj\u00eb p\u00ebr qasje direkte n\u00eb platform\u00eb. Nuk flas p\u00ebr modulet e kernelit, t\u00eb cilat jan\u00eb ngusht\u00ebsisht t\u00eb lidhura me kernelin dhe nuk p\u00ebrshtaten n\u00eb konceptin e r\u00ebr\u00ebs. <\/p>\n<p>Problemi i dyt\u00eb \u2013 shp\u00ebrndarjet e njohura n\u00eb mjedisin enterprise nga Red Hat dhe SUSE ende nuk p\u00ebrmbajn\u00eb mb\u00ebshtetje p\u00ebr Snappy dhe Flatpak. <\/p>\n<p>P\u00ebr k\u00ebt\u00eb arsye, Veeam Agent for Linux nuk \u00ebsht\u00eb as n\u00eb <noindex><a rel=\"nofollow\" href=\"https:\/\/snapcraft.io\/\">snapcraft.io<\/a><\/noindex> asnj\u00eb <noindex><a rel=\"nofollow\" href=\"https:\/\/flathub.org\/home\">flathub.org<\/a><\/noindex>.<\/p>\n<p>N\u00eb p\u00ebrfundim t\u00eb \u00e7\u00ebshtjes p\u00ebr menaxher\u00ebt e paketeve, dua t\u00eb theksoj se ekziston nj\u00eb mund\u00ebsi p\u00ebr t'u hequr plot\u00ebsisht nga menaxher\u00ebt e paketeve, duke kombinuar n\u00eb nj\u00eb paket\u00eb skedar\u00ebt binar\u00eb dhe skriptet p\u00ebr instalimin e tyre. <\/p>\n<p>Nj\u00eb bundle i till\u00eb lejon krijimin e nj\u00eb pakete t\u00eb vetme p\u00ebr distribucione dhe placa t\u00eb ndryshme, duke ofruar nj\u00eb proces interaktiv instalimi me p\u00ebrshtatje t\u00eb nevojshme. Kam hasur n\u00eb k\u00ebto paketa p\u00ebr Linux vet\u00ebm nga VMware.<\/p>\n<h2>Problemi i azhurnimeve<\/h2>\n<p>\n<img decoding=\"async\" alt=\"Linux shum\u00ebform\u00ebsh: si t\u00eb punoni me \u00e7do distribucion\" src=\"\/wp-content\/uploads\/2019\/10\/aa14b10a434c28541574421d97807de7.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nEdhe n\u00ebse t\u00eb gjitha problemet me var\u00ebsit\u00eb jan\u00eb zgjidhur, programi mund t\u00eb funksionoj\u00eb ndryshe n\u00eb t\u00eb nj\u00ebjtin shp\u00ebrndarje. Problemi q\u00ebndron te azhurnimet.<\/p>\n<p>Ka 3 strategji azhurnimi:<\/p>\n<ul>\n<li>Strategjia m\u00eb e thjesht\u00eb \u2013 t\u00eb mos azhurnosh kurr\u00eb. E ke konfiguruar serverin dhe harrove. Pse azhurnimet, n\u00ebse gjith\u00e7ka funksionon? Problemet fillojn\u00eb sapo b\u00ebhet nj\u00eb thirrje n\u00eb sh\u00ebrbimin e mb\u00ebshtetjes. Krijuesi i shp\u00ebrndarjes mb\u00ebshtet vet\u00ebm versionin e azhurnuar. <\/li>\n<li>Mund t\u00eb besosh shp\u00ebrndar\u00ebsin dhe t\u00eb konfigurosh azhurnim automatik. N\u00eb k\u00ebt\u00eb rast, nj\u00eb telefonat\u00eb n\u00eb sh\u00ebrbimin e mb\u00ebshtetjes \u00ebsht\u00eb e mundur menj\u00ebher\u00eb pas nj\u00eb azhurnimi t\u00eb d\u00ebshtuar.<\/li>\n<li>Mund\u00ebsia e azhurnimit manual vet\u00ebm pas provave n\u00eb infrastruktur\u00ebn testuese \u2013 \u00ebsht\u00eb m\u00eb e sigurt, por e kushtueshme dhe e pun\u00ebs shum\u00eb. Larg t\u00eb gjith\u00ebve \u00ebsht\u00eb e mundur ta p\u00ebrballojn\u00eb at\u00eb.<\/li>\n<\/ul>\n<p>\nP\u00ebrsaq\u00eb p\u00ebrdorues t\u00eb ndrysh\u00ebm aplikojn\u00eb strategji t\u00eb ndryshme azhurnimi, \u00ebsht\u00eb e nevojshme t\u00eb mb\u00ebshteten si versioni m\u00eb i ri, ashtu edhe t\u00eb gjitha versionet e l\u00ebshuara m\u00eb par\u00eb. Kjo e komplikon procesin e zhvillimit dhe testimit, duke shtuar dhimbje koke p\u00ebr sh\u00ebrbimin e mb\u00ebshtetjes.<\/p>\n<h2>Larmia e platformave harduerike<\/h2>\n<p>\nPlatforma t\u00eb ndryshme harduerike \u2013 kjo \u00ebsht\u00eb nj\u00eb problem, p\u00ebr shum\u00eb arsye specifik p\u00ebr kodin native. T\u00eb pakt\u00ebn, duhet t\u00eb mblidhen binar\u00eb p\u00ebr \u00e7do platform\u00eb t\u00eb mb\u00ebshtetur.<\/p>\n<p>N\u00eb projektin Veeam Agent for Linux ne ende nuk mund t\u00eb mb\u00ebshtesim ndonj\u00eb gj\u00eb t\u00eb till\u00eb RISC-ove.<\/p>\n<p>Nuk do t\u00eb ndalem n\u00eb k\u00ebt\u00eb \u00e7\u00ebshtje. Do t\u00eb theksoj vet\u00ebm problemet kryesore: llojet e varura nga platforma, si\u00e7 jan\u00eb <code>size_t<\/code>, p\u00ebrputhshm\u00ebria e strukturave dhe rendi i byte.<\/p>\n<h2>Lidhja statike dhe\/apo dinamike<\/h2>\n<p>\n<img decoding=\"async\" alt=\"Linux shum\u00ebform\u00ebsh: si t\u00eb punoni me \u00e7do distribucion\" src=\"\/wp-content\/uploads\/2019\/10\/dc473aad4ea0818940af7eafdbc641fd.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nPor pyetja \"Si t\u00eb lidhen me bibliotekat - dinamike ose statike?\" meritojn\u00eb t\u00eb diskutohet.<\/p>\n<p>N\u00eb pergjith\u00ebsi, aplikacionet C\/C++ p\u00ebr Linux p\u00ebrdorin lidhje dinamike. Kjo funksionon shk\u00eblqyesh\u00ebm n\u00ebse aplikacioni mbledh p\u00ebr specificisht p\u00ebr nj\u00eb shp\u00ebrndarje t\u00eb ve\u00e7ant\u00eb.<\/p>\n<p>N\u00ebse q\u00ebllimi \u00ebsht\u00eb t\u00eb mbulohet nj\u00eb gam\u00eb e ndryshme distributionsh me nj\u00eb skedar binar, at\u00ebher\u00eb duhet t\u00eb p\u00ebrqendrohemi n\u00eb distribution-in m\u00eb t\u00eb vog\u00ebl t\u00eb mb\u00ebshtetur. P\u00ebr ne, kjo \u00ebsht\u00eb Red Hat 6. Ai p\u00ebrmban gcc 4.4, i cili nuk e mb\u00ebshtet as standardin C++11. <noindex><a rel=\"nofollow\" href=\"https:\/\/gcc.gnu.org\/projects\/cxx-status.html\">plot\u00ebsisht<\/a><\/noindex>.<\/p>\n<p>Ne e nd\u00ebrtojm\u00eb projektin ton\u00eb me gcc 6.3, i cili mb\u00ebshtet plot\u00ebsisht C++14. Natyrisht, n\u00eb k\u00ebt\u00eb rast, n\u00eb Red Hat 6 na duhet t\u00eb sjellim bibliotek\u00ebn libstdc++ dhe boost bashk\u00eb. M\u00eb e leht\u00eb \u00ebsht\u00eb t\u00eb lidhemi me to n\u00eb m\u00ebnyr\u00eb statike.<\/p>\n<p>Por fatkeq\u00ebsisht, jo me t\u00eb gjitha bibliotekat mund t\u00eb lidhemi n\u00eb m\u00ebnyr\u00eb statike.<\/p>\n<p>S\u00eb pari, biblioteka sistemore, t\u00eb tilla si <i>libfuse<\/i>, <i>libblkid<\/i> duhet t\u00eb lidhen n\u00eb m\u00ebnyr\u00eb dinamike, p\u00ebr t'u siguruar n\u00eb p\u00ebrputhshm\u00ebri me b\u00ebrtham\u00ebn dhe modulet e saj. <\/p>\n<p>S\u00eb dyti, ka nj\u00eb nuanc\u00eb me licencat. <\/p>\n<p>Licenca GPL n\u00eb parim lejon lidhjen e bibliotekave vet\u00ebm me kod opensource. MIT dhe BSD lejojn\u00eb lidhjen statike dhe lejojn\u00eb p\u00ebrfshirjen e bibliotekave n\u00eb projekt. Nd\u00ebrsa LGPL, duket se nuk e kund\u00ebrshton lidhjen statike, por k\u00ebrkon q\u00eb t\u00eb ofrohen n\u00eb akses t\u00eb p\u00ebrgjithsh\u00ebm skedar\u00ebt e nevojsh\u00ebm p\u00ebr lidhjen. <\/p>\n<p>N\u00eb p\u00ebrgjith\u00ebsi, p\u00ebrdorimi i lidhjes dinamike do t\u00eb siguroj\u00eb nga nevoja p\u00ebr t\u00eb ofruar di\u00e7ka.<\/p>\n<h2>Nd\u00ebrtimi i aplikacioneve C\/C++<\/h2>\n<p>\nP\u00ebr nd\u00ebrtimin e aplikacioneve C\/C++ p\u00ebr platforma dhe distributionsh t\u00eb ndryshme, mjafton t\u00eb zgjedhim ose t\u00eb nd\u00ebrtuam gcc-n\u00eb e duhur dhe t\u00eb p\u00ebrdorim cross-compilers p\u00ebr arkitektur\u00ebn specifike, si dhe t\u00eb nd\u00ebrtosh t\u00eb gjith\u00eb setin e bibliotekave. Ky proces \u00ebsht\u00eb i realizuesh\u00ebm, por mjaft i lodhsh\u00ebm. Dhe nuk ka asnj\u00eb garanci q\u00eb kompiliatori dhe bibliotekat e zgjedhura do t'u ofrojn\u00eb nj\u00eb variant funksional. <\/p>\n<p>Nj\u00eb p\u00ebrpar\u00ebsi e dukshme: infrastruktura thjeshtohet ndjesh\u00ebm, pasi i gjith\u00eb procesi i nd\u00ebrtimit mund t\u00eb kryhet n\u00eb nj\u00eb makin\u00eb t\u00eb vetme. P\u00ebr m\u00eb tep\u00ebr, mjafton t\u00eb nd\u00ebrtojm\u00eb nj\u00eb grup skedash binar\u00ebsh p\u00ebr nj\u00eb arkitektur\u00eb dhe mund t'i paketojm\u00eb n\u00eb paketat p\u00ebr distributionsh t\u00eb ndryshme. K\u00ebshtu krijohen paketat veeam p\u00ebr Veeam Agent for Linux.<\/p>\n<p>N\u00eb vend t\u00eb k\u00ebtij varianti, mund t\u00eb p\u00ebrgatisim nj\u00eb ferm\u00eb nd\u00ebrtimi, q\u00eb do t\u00eb thot\u00eb disa makina p\u00ebr nd\u00ebrtim. \u00c7do makin\u00eb e till\u00eb do t\u00eb siguroj\u00eb kompaktimin e aplikacionit dhe nd\u00ebrtimin e paket\u00ebs p\u00ebr nj\u00eb shp\u00ebrndarje t\u00eb caktuar dhe nj\u00eb arkitektur\u00eb t\u00eb ve\u00e7ant\u00eb. N\u00eb k\u00ebt\u00eb rast, kompaktimi kryhet me mjetet q\u00eb p\u00ebrgatiti shp\u00ebrndar\u00ebsi. K\u00ebshtu, faza e p\u00ebrgatitjes s\u00eb kompjuterit dhe p\u00ebrzgjedhjes s\u00eb bibliotekave hiqet. P\u00ebr m\u00eb tep\u00ebr, procesi i nd\u00ebrtimit mund t\u00eb shp\u00ebrndahet leht\u00ebsisht. <\/p>\n<p>Megjithat\u00eb, ka nj\u00eb disavantazh t\u00eb k\u00ebtij qasjeje: p\u00ebr \u00e7do shp\u00ebrndarje brenda nj\u00eb arkitekture do t\u00eb duhet t\u00eb nd\u00ebrtohet nj\u00eb grup i ve\u00e7ant\u00eb skedar\u00ebsh binar\u00eb. Nj\u00eb disavantazh tjet\u00ebr \u00ebsht\u00eb se nj\u00eb num\u00ebr kaq i madh makinash duhet t\u00eb mbikqyret, duke alokuar nj\u00eb sasi t\u00eb madhe hap\u00ebsire disku dhe memories operative. <\/p>\n<p>K\u00ebshtu nd\u00ebrtohen pakot KMOD t\u00eb modulit t\u00eb b\u00ebrtham\u00ebs veeamsnap p\u00ebr shp\u00ebrndarjet Red Hat.<\/p>\n<h2>Open Build Service<\/h2>\n<p>\nKoleg\u00ebt nga SUSE p\u00ebrpoq\u00ebn t\u00eb realizojn\u00eb nj\u00eb mesatare t\u00eb art\u00eb n\u00eb form\u00ebn e nj\u00eb sh\u00ebrbimi t\u00eb ve\u00e7ant\u00eb p\u00ebr kompaktimin e aplikacioneve dhe nd\u00ebrtimin e pakove \u2014 <noindex><a rel=\"nofollow\" href=\"https:\/\/openbuildservice.org\/\">openbuildservice<\/a><\/noindex>.<\/p>\n<p>N\u00eb thelb, ky \u00ebsht\u00eb nj\u00eb hipervizor q\u00eb krijon nj\u00eb makin\u00eb virtuale, instalon n\u00eb t\u00eb t\u00eb gjith\u00eb paketat e nevojshme, kryen kompaktimin e aplikacionit dhe nd\u00ebrtimin e paket\u00ebs n\u00eb k\u00ebt\u00eb mjedis t\u00eb izoluar, pas s\u00eb cil\u00ebs kjo makin\u00eb virtuale lirohet.<\/p>\n<p><img decoding=\"async\" alt=\"Linux shum\u00ebform\u00ebsh: si t\u00eb punoni me \u00e7do distribucion\" src=\"\/wp-content\/uploads\/2019\/10\/93d2a70c589a7186ecef85a7863e59e8.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nPlanifikuesi i realizuar n\u00eb OpenBuildService vet\u00eb do t\u00eb p\u00ebrcaktoj\u00eb se sa makina virtuale mund t\u00eb filloj\u00eb p\u00ebr shpejt\u00ebsin\u00eb optimale t\u00eb nd\u00ebrtimit t\u00eb pakove. Mekanizmi i nd\u00ebrtuar p\u00ebr n\u00ebnshkrim do t\u00eb n\u00ebnshkruaj\u00eb vet\u00eb paketat dhe do t\u2019i ngarkoj\u00eb ato n\u00eb depozitat e integruara. Sistemi i nd\u00ebrtuar i kontrollit t\u00eb versioneve do t\u00eb ruaj\u00eb historikun e ndryshimeve dhe nd\u00ebrtimit. Ngelen vet\u00ebm t'i shtosh k\u00ebtij sistemi burimet e tua. Nuk \u00ebsht\u00eb e nevojshme t\u00eb ngre nj\u00eb server vet\u00eb, por mund t\u00eb shfryt\u00ebzosh at\u00eb t\u00eb hapur.<\/p>\n<p>Megjithat\u00eb, k\u00ebtu ka nj\u00eb problem: nj\u00eb makin\u00eb e till\u00eb \u00ebsht\u00eb e v\u00ebshtir\u00eb t\u00eb integrohet n\u00eb infrastruktur\u00ebn ekzistuese. P\u00ebr shembull, kontrolli i versioneve nuk \u00ebsht\u00eb i nevojsh\u00ebm, ne tashm\u00eb kemi tonin p\u00ebr burimet. Mekanizmi i n\u00ebnshkrimit \u00ebsht\u00eb ndryshe: p\u00ebrdoret nj\u00eb server i ve\u00e7ant\u00eb. Depozita gjithashtu nuk \u00ebsht\u00eb e nevojshme. <\/p>\n<p>P\u00ebrve\u00e7 k\u00ebsaj, mb\u00ebshtetja p\u00ebr shp\u00ebrndarje t\u00eb tjera \u2014 p\u00ebr shembull, Red Hat \u2014 \u00ebsht\u00eb realizuar mjaft dob\u00ebt, gj\u00eb q\u00eb \u00ebsht\u00eb plot\u00ebsisht e kuptueshme.<\/p>\n<p>Pik\u00eb e fort\u00eb e k\u00ebtij sh\u00ebrbimi \u00ebsht\u00eb suporti i shpejt\u00eb p\u00ebr versionin e radh\u00ebs t\u00eb distribucionit SUSE. Para shpalljes zyrtare t\u00eb l\u00ebshimit, paketat e nevojshme p\u00ebr nd\u00ebrtim publikohen n\u00eb depo t\u00eb hapura. Nj\u00eb e re shfaqet n\u00eb list\u00ebn e distribucioneve t\u00eb disponueshme n\u00eb OpenBuildService. Vendosim shenj\u00ebn dhe ajo shtohet n\u00eb planin e nd\u00ebrtimit. K\u00ebshtu, shtimi i nj\u00eb versioni t\u00eb ri t\u00eb distribucionit kryhet praktikisht me nj\u00eb klik t\u00eb vet\u00ebm.<\/p>\n<p>N\u00eb infrastruktur\u00ebn ton\u00eb, duke p\u00ebrdorur OpenBuildService, nd\u00ebrtohet t\u00ebr\u00eb varianti i paketave KMP p\u00ebr modul\u00ebn e b\u00ebrtham\u00ebs veeamsnap p\u00ebr distribucionet SUSE.<\/p>\n<p>Tani do t\u00eb doja t\u00eb ndalesha te \u00e7\u00ebshtjet q\u00eb jan\u00eb specifike p\u00ebr modulet e b\u00ebrtham\u00ebs.<\/p>\n<h2>kernel ABI<\/h2>\n<p>\nModulet e b\u00ebrtham\u00ebs Linux historikisht shp\u00ebrndaheshin n\u00eb form\u00ebn e teksteve t\u00eb burimit. Kjo \u00ebsht\u00eb p\u00ebr shkak se krijuesit e b\u00ebrtham\u00ebs nuk e shqet\u00ebsojn\u00eb veten me p\u00ebrkushtimin p\u00ebr t\u00eb mb\u00ebshtetur nj\u00eb API t\u00eb q\u00ebndruesh\u00ebm p\u00ebr modulet e b\u00ebrtham\u00ebs, e aq m\u00eb pak n\u00eb nivelin binar, q\u00eb quhet kABI.<\/p>\n<p>P\u00ebr t\u00eb nd\u00ebrtuar nj\u00eb modul p\u00ebr b\u00ebrtham\u00ebn vanilje, nevojiten patjet\u00ebr header-a t\u00eb k\u00ebsaj b\u00ebrthame, dhe ai do t\u00eb funksionoj\u00eb vet\u00ebm n\u00eb k\u00ebt\u00eb b\u00ebrtham\u00eb. <\/p>\n<p>DKMS lejon automatizimin e procesit t\u00eb nd\u00ebrtimit t\u00eb moduleve gjat\u00eb p\u00ebrdit\u00ebsimit t\u00eb b\u00ebrtham\u00ebs. Si rezultat, p\u00ebrdoruesit e depozit\u00ebs Debian (dhe t\u00eb af\u00ebrm t\u00eb saj) p\u00ebrdorin modulet e b\u00ebrtham\u00ebs ose nga depoja e distribuesit, ose t\u00eb nd\u00ebrtuara nga burimet me ndihm\u00ebn e DKMS.<\/p>\n<p>Megjithat\u00eb, kjo situat\u00eb nuk e k\u00ebnaq shum\u00eb segmentin Enterprise. Shp\u00ebrndar\u00ebsit e kodit proprietar d\u00ebshirojn\u00eb t\u00eb shp\u00ebrndajn\u00eb produktin n\u00eb form\u00ebn e binar\u00ebve t\u00eb nd\u00ebrtuar. <\/p>\n<p>Administruesit nuk duan t\u00eb mbajn\u00eb mjete zhvillimi n\u00eb serverat e prodhimit p\u00ebr arsye sigurie. Distribuesit e Enterprise Linux \u2014 si Red Hat dhe SUSE \u2014 kan\u00eb vendosur se p\u00ebr p\u00ebrdoruesit e tyre, ata do t\u00eb mb\u00ebshtesin nj\u00eb kABI t\u00eb q\u00ebndruesh\u00ebm. Si rezultat, jan\u00eb shfaqur paketat KMOD p\u00ebr Red Hat dhe paketat KMP p\u00ebr SUSE.<\/p>\n<p>Thelbi i k\u00ebtij zgjidhjeje \u00ebsht\u00eb mjaft i thjesht\u00eb. P\u00ebr nj\u00eb version t\u00eb caktuar t\u00eb distribucionit, API i b\u00ebrtham\u00ebs ngrihet. Distribuesi shpall se po p\u00ebrdor vet\u00eb b\u00ebrtham\u00ebn, p\u00ebr shembull, 3.10, dhe b\u00ebn vet\u00ebm rregullime dhe p\u00ebrmir\u00ebsime q\u00eb nuk prekin ndonj\u00eb m\u00ebnyr\u00eb interface-t e b\u00ebrtham\u00ebs, dhe modulet e nd\u00ebrtuara p\u00ebr b\u00ebrtham\u00ebn e par\u00eb mund t\u00eb p\u00ebrdoren p\u00ebr t\u00eb gjitha ato t\u00eb m\u00ebvonshme pa i ripunuar.<\/p>\n<p>Red Hat deklaron se mb\u00ebshtetja p\u00ebr kABI do t\u00eb jet\u00eb e disponueshme p\u00ebr shp\u00ebrndarjen gjat\u00eb gjith\u00eb ciklit t\u00eb jet\u00ebs. Kjo do t\u00eb thot\u00eb se moduli i nd\u00ebrtuar p\u00ebr rhel 6.0 (l\u00ebshimi n\u00eb n\u00ebntor 2010) duhet t\u00eb funksionoj\u00eb gjithashtu edhe n\u00eb versionin 6.10 (l\u00ebshimi n\u00eb qershor 2018). Kjo \u00ebsht\u00eb pothuajse 8 vjet. Natyrisht, ky \u00ebsht\u00eb nj\u00eb detyr\u00eb mjaft e komplikuar. <br \/>\nNe kemi regjistruar disa raste kur p\u00ebr shkak t\u00eb problemeve me p\u00ebrputhshm\u00ebrin\u00eb e kABI, moduli veeamsnap ka ndaluar s\u00eb funksionuari. <\/p>\n<p>Pas k\u00ebtij rasti, moduli veeamsnap, i nd\u00ebrtuar p\u00ebr RHEL 7.0, rezultoi se nuk ishte i p\u00ebrputhsh\u00ebm me kern\u00ebn nga RHEL 7.5, por megjithat\u00eb ngarkohej dhe garantonte r\u00ebnien e serverit, ne u t\u00ebrhoq\u00ebm nga p\u00ebrdorimi i p\u00ebrputhshm\u00ebris\u00eb s\u00eb kABI p\u00ebr RHEL 7 n\u00eb p\u00ebrgjith\u00ebsi. <\/p>\n<p>Aktualisht, paketa KMOD p\u00ebr RHEL 7 p\u00ebrmban nj\u00eb nd\u00ebrtim p\u00ebr \u00e7do version t\u00eb l\u00ebshimit dhe nj\u00eb skript q\u00eb garanton ngarkimin e modulit.<\/p>\n<p>SUSE iu qas detyr\u00ebs s\u00eb p\u00ebrputhshm\u00ebris\u00eb s\u00eb kABI m\u00eb me kujdes. Ata ofrojn\u00eb p\u00ebrputhshm\u00ebri t\u00eb kABI vet\u00ebm brenda nj\u00eb pakete sh\u00ebrbimi. <\/p>\n<p>P\u00ebr shembull, l\u00ebshimi SLES 12 u b\u00eb n\u00eb n\u00ebntor 2014. Nd\u00ebrsa SLES 12 SP1 u publikua n\u00eb dhjetor 2015, q\u00eb do t\u00eb thot\u00eb se kaloi pak m\u00eb shum\u00eb se nj\u00eb vit. Megjith\u00ebse t\u00eb dy l\u00ebshimet p\u00ebrdorin kernin 3.12, ato jan\u00eb t\u00eb pap\u00ebrputhshme me kABI. \u00cbsht\u00eb e qart\u00eb se mb\u00ebshtetja e p\u00ebrputhshm\u00ebris\u00eb s\u00eb kABI vet\u00ebm p\u00ebr nj\u00eb vit \u00ebsht\u00eb duksh\u00ebm m\u00eb e leht\u00eb. Cikli vjetor i p\u00ebrdit\u00ebsimit t\u00eb modulit t\u00eb kernit nuk duhet t\u00eb shkaktoj\u00eb probleme p\u00ebr krijuesit e moduleve. <\/p>\n<p>Si rezultat i k\u00ebsaj politike t\u00eb SUSE, ne nuk kemi regjistruar ndonj\u00eb problem me p\u00ebrputhshm\u00ebrin\u00eb e kABI p\u00ebr modulin ton\u00eb veeamsnap. Megjithat\u00eb, numri i paketave p\u00ebr SUSE \u00ebsht\u00eb pothuajse nj\u00eb rend m\u00eb i lart\u00eb.<\/p>\n<h2>Patch-e dhe bckport-e<\/h2>\n<p>\nMegjith\u00ebse shp\u00ebrndar\u00ebsit p\u00ebrpiqen t\u00eb ofrojn\u00eb p\u00ebrputhshm\u00ebri t\u00eb kABI dhe stabilitet t\u00eb kernit, ata gjithashtu p\u00ebrpiqen t\u00eb p\u00ebrmir\u00ebsojn\u00eb performanc\u00ebn dhe t\u00eb eliminojn\u00eb defektet e k\u00ebtij kerni stabil. <\/p>\n<p>Po ashtu, p\u00ebrve\u00e7 \"pun\u00ebs mbi gabimet\" vetjake, zhvilluesit e kernit enterprise linux ndjekin ndryshimet n\u00eb kernin vanilla dhe i \u043f\u0435\u0440\u0435\u043d\u043e\u0441in ato n\u00eb \"stabilin\" e tyre.<\/p>\n<p>Ndonj\u00ebher\u00eb kjo shkakton gabime t\u00eb reja. <noindex><a rel=\"nofollow\" href=\"https:\/\/access.redhat.com\/solutions\/3658111\">Gabime<\/a><\/noindex>.<\/p>\n<p>N\u00eb l\u00ebshimin m\u00eb t\u00eb fundit t\u00eb Red Hat 6, nj\u00eb nga p\u00ebrdit\u00ebsimet m\u00eb t\u00eb vogla kishte nj\u00eb defekt. Kjo \u00e7oi n\u00eb at\u00eb q\u00eb moduli veeamsnap garantonte r\u00ebnien e sistemit gjat\u00eb \u00e7lirimit t\u00eb snapshot-it. Duke krahasuar burimet e kernit para dhe pas p\u00ebrdit\u00ebsimit, ne zbuluam se problemin e shkaktonte backport-i. Nj\u00eb korrektim i ngjash\u00ebm u b\u00eb n\u00eb kernin vanilla version 4.19. Megjithat\u00eb, n\u00eb kernin vanilla ky korrektim funksionoi si\u00e7 duhet, por gjat\u00eb transferimit n\u00eb \"stabilin\" 2.6.32 u shfaq nj\u00eb problem me bllokimin e spin.<\/p>\n<p>Sigurisht, gabimet ndodhin te gjith\u00ebve dhe gjithmon\u00eb, por a kishte vler\u00eb t\u00eb t\u00ebrhiqnim kodin nga 4.19 n\u00eb 2.6.32, duke rrezikuar stabilitetin?.. Nuk jam i sigurt...<\/p>\n<p>M\u00eb e keqja \u00ebsht\u00eb se kur marketingu lidhet me t\u00ebrheqjen e litarit \"stabilitet\"  \"modernizim\". Departamenti i marketingut ka nevoj\u00eb q\u00eb b\u00ebrthama e distribucionit t\u00eb p\u00ebrdit\u00ebsuar t\u00eb jet\u00eb e stabilizuar, nga nj\u00ebra an\u00eb, dhe n\u00eb t\u00eb nj\u00ebjt\u00ebn koh\u00eb t\u00eb ket\u00eb performanc\u00eb m\u00eb t\u00eb mir\u00eb dhe funksione t\u00eb reja. Kjo \u00e7on n\u00eb kompromise t\u00eb \u00e7uditshme. <\/p>\n<p>Kur provova t\u00eb nd\u00ebrtoja nj\u00eb modul n\u00eb b\u00ebrtham\u00ebn 4.4 t\u00eb SLES 12 SP3, u befasova kur zbulova funksionalitetin nga b\u00ebrthama e zakonshme 4.8. Sipas mendimit tim, realizimi i hyrjes\/shtypjes bllok \u00ebsht\u00eb shum\u00eb m\u00eb i af\u00ebrt me b\u00ebrtham\u00ebn 4.8, sesa me l\u00ebshimin e m\u00ebparsh\u00ebm t\u00eb stabilizuar 4.4 nga SLES 12 SP2. Nuk guxoj t\u00eb gjykoj se cila ishte p\u00ebrqindja e kodit t\u00eb transferuar nga b\u00ebrthama 4.8 n\u00eb SLES-in 4.4 p\u00ebr SP3, megjithat\u00eb, nuk mund ta quaj b\u00ebrtham\u00ebn ende si 4.4 t\u00eb stabilizuar. <\/p>\n<p>M\u00eb e pak\u00ebndshme \u00ebsht\u00eb se kur krijoni nj\u00eb modul q\u00eb funksionon nj\u00ebsoj mir\u00eb n\u00eb b\u00ebrthama t\u00eb ndryshme, nuk mund t\u00eb mb\u00ebshteteni m\u00eb n\u00eb versionin e b\u00ebrtham\u00ebs. Duhet t\u00eb merrni parasysh edhe distribucionin. Fatmir\u00ebsisht, ndonj\u00ebher\u00eb mund t\u00eb lidhni nj\u00eb definicion q\u00eb shfaqet n\u00eb t\u00eb nj\u00ebjt\u00ebn koh\u00eb me funksionalitetin e ri, por kjo mund\u00ebsi nuk shfaqet gjithmon\u00eb. <\/p>\n<p>Si rezultat, kodi mbushet me direktiva t\u00eb \u00e7uditshme t\u00eb kompilimit t\u00eb kushteve.<\/p>\n<p>Takohen edhe patch-e q\u00eb ndryshojn\u00eb API-n\u00eb e dokumentuar t\u00eb b\u00ebrtham\u00ebs. <br \/>\nNatyra e distribucionit <noindex><a rel=\"nofollow\" href=\"https:\/\/neon.kde.org\/\">KDE neon<\/a><\/noindex> 5.16 dhe u befasova shum\u00eb q\u00eb thirrja lookup_bdev n\u00eb k\u00ebt\u00eb version b\u00ebrthame ndryshoi list\u00ebn e parametrave hyr\u00ebs.<\/p>\n<p>P\u00ebr t'u nd\u00ebrtuar, m\u00eb duhej t\u00eb shtoja n\u00eb makefile nj\u00eb skenar q\u00eb kontrollonte n\u00ebse ekzistonte parametri mask tek funksioni lookup_bdev.<\/p>\n<h2>N\u00ebnshkrimi i moduleve t\u00eb b\u00ebrthames<\/h2>\n<p>\nPor le t\u00eb kthehemi te \u00e7\u00ebshtja e shp\u00ebrndarjes s\u00eb pakove.<\/p>\n<p>Nj\u00eb nga p\u00ebrfitimet kryesore t\u00eb kABI t\u00eb stabilizuar \u00ebsht\u00eb se modulet e b\u00ebrthames n\u00eb form\u00eb skedari binar mund t\u00eb n\u00ebnshkruhen. N\u00eb k\u00ebt\u00eb rast, zhvilluesi mund t\u00eb jet\u00eb i sigurt q\u00eb moduli nuk \u00ebsht\u00eb d\u00ebmtuar rast\u00ebsisht ose ndryshuar q\u00ebllimisht. K\u00ebt\u00eb mund ta kontrolloni me komand\u00ebn modinfo. <\/p>\n<p>Distribucionet Red Hat dhe SUSE lejojn\u00eb kontrollin e n\u00ebnshkrimit t\u00eb modulit dhe ngarkimin e tij vet\u00ebm n\u00ebse n\u00eb sistem \u00ebsht\u00eb regjistruar certifikata p\u00ebrkat\u00ebse. Certifikata p\u00ebrb\u00ebhet nga nj\u00eb \u00e7el\u00ebs publik, i cili n\u00ebnshkruan modulit. Ne e shp\u00ebrndajm\u00eb at\u00eb n\u00eb form\u00ebn e nj\u00eb pakete t\u00eb ve\u00e7ant\u00eb.<\/p>\n<p>Problemi k\u00ebtu \u00ebsht\u00eb se certifikatat mund t\u00eb jen\u00eb ose t\u00eb integruara n\u00eb b\u00ebrtham\u00eb (ato p\u00ebrdoren nga distributor\u00ebt), ose duhet t\u00eb shkruhen n\u00eb memorie jo fragile EFI me an\u00eb t\u00eb nj\u00eb utilitari. <i>mokutil<\/i>. Vegla <i>mokutil<\/i> kur instaloni certifikat\u00ebn k\u00ebrkon q\u00eb t\u00eb riblokuhet sistemi dhe madje para se t\u00eb ngarkohet b\u00ebrthama e sistemit operativ ofron administratorit mund\u00ebsin\u00eb p\u00ebr t\u00eb lejuar ngarkimin e nj\u00eb certifikate t\u00eb re. <\/p>\n<p>Pra, shtimi i certifikat\u00ebs k\u00ebrkon qasje fizike t\u00eb administratorit n\u00eb sistem. N\u00ebse makineria ndodhet diku n\u00eb cloud ose thjesht n\u00eb nj\u00eb server t\u00eb larg\u00ebt dhe qasja b\u00ebhet vet\u00ebm p\u00ebrmes rrjetit (p.sh., p\u00ebrmes ssh), at\u00ebher\u00eb do t\u00eb jet\u00eb e pamundur t\u00eb shtoni certifikat\u00ebn. <\/p>\n<h2>EFI n\u00eb makinat virtuale<\/h2>\n<p>\nMegjith\u00ebse EFI \u00ebsht\u00eb mb\u00ebshtetur p\u00ebr nj\u00eb koh\u00eb t\u00eb gjat\u00eb nga shumica e krijuesve t\u00eb pllakave t\u00eb n\u00ebn\u00ebm\u00ebrtes\u00ebs, gjat\u00eb instalimit t\u00eb sistemit, administratori mund t\u00eb mos e ket\u00eb menduar nevoj\u00ebn p\u00ebr EFI, dhe ai mund t\u00eb jet\u00eb \u00e7aktivizuar. <\/p>\n<p>Nuk t\u00eb gjith\u00eb hipervizor\u00ebt mb\u00ebshtesin EFI. VMWare vSphere mb\u00ebshtet EFI q\u00eb nga versioni 5. <br \/>\nMicrosoft Hyper-V gjithashtu ka marr\u00eb mb\u00ebshtetje p\u00ebr EFI, q\u00eb nga Hyper-V p\u00ebr Windows Server 2012R2. <\/p>\n<p>Megjithat\u00eb, n\u00eb konfigurimin e defolt, kjo funksionalitet p\u00ebr makinat Linux \u00ebsht\u00eb \u00e7aktivizuar, k\u00ebshtu q\u00eb nuk \u00ebsht\u00eb e mundur t\u00eb instalohet certifikata. <\/p>\n<p>N\u00eb vSphere 6.5, mund t\u00eb caktoni opsionin <b>Secure Boot<\/b> vet\u00ebm n\u00eb versionin e vjet\u00ebr t\u00eb nd\u00ebrfaqes p\u00ebr internet, e cila funksionon p\u00ebrmes Flash. UI n\u00eb HTML-5 p\u00ebr momentin \u00ebsht\u00eb shum\u00eb mbrapa.<\/p>\n<h2>Distribucione eksperimentale<\/h2>\n<p>\nDhe p\u00ebr fund, le t\u00eb shqyrtojm\u00eb \u00e7\u00ebshtjen e distribucioneve eksperimentale dhe atyre q\u00eb nuk kan\u00eb mb\u00ebshtetje zyrtare. Nga nj\u00eb an\u00eb, \u00ebsht\u00eb e v\u00ebshtir\u00eb t\u00eb hasim n\u00eb k\u00ebto distribucione n\u00eb server\u00ebt e organizatave serioze. Nuk ka mb\u00ebshtetje zyrtare p\u00ebr k\u00ebto distribucione. Prandaj, nuk \u00ebsht\u00eb e mundur t\u00eb ofrohet mb\u00ebshtetje teknike p\u00ebr produktin n\u00eb nj\u00eb distribucion t\u00eb till\u00eb. <\/p>\n<p>Megjithat\u00eb, k\u00ebto distribucione b\u00ebhen nj\u00eb platform\u00eb e p\u00ebrshtatshme p\u00ebr t\u00eb provuar zgjidhje t\u00eb reja eksperimentale. P\u00ebr shembull, Fedora, OpenSUSE Tumbleweed ose versionet e Pamundura t\u00eb Debian. Ato jan\u00eb mjaft stabile. N\u00eb to gjithmon\u00eb ka versione t\u00eb reja t\u00eb programeve dhe gjithmon\u00eb nj\u00eb b\u00ebrtham\u00eb t\u00eb re. Pas nj\u00eb viti, ky funksionalitet eksperimental mund t\u00eb p\u00ebrfshihet n\u00eb RHEL, SLES ose Ubuntu t\u00eb azhurnuar. <\/p>\n<p>Pra, n\u00ebse di\u00e7ka nuk funksionon n\u00eb nj\u00eb distribucion eksperimental - kjo \u00ebsht\u00eb nj\u00eb arsyetim p\u00ebr t\u00eb kuptuar problemin dhe p\u00ebr ta zgjidhur. Duhet t\u00eb jeni t\u00eb gatsh\u00ebm q\u00eb ky funksionalitet shpejt do t\u00eb shfaqet n\u00eb server\u00ebt e prodhimit t\u00eb p\u00ebrdoruesve.<\/p>\n<p>Lista aktuale e distribucioneve t\u00eb mb\u00ebshtetura zyrtarisht p\u00ebr versionin 3.0 mund ta shikoni <noindex><a rel=\"nofollow\" href=\"https:\/\/helpcenter.veeam.com\/docs\/agentforlinux\/userguide\/system_requirements.html?ver=30\">k\u00ebtu<\/a><\/noindex>. Por lista reale e distribucioneve n\u00eb t\u00eb cilat produkti yn\u00eb \u00ebsht\u00eb i aft\u00eb t\u00eb punoj\u00eb \u00ebsht\u00eb shum\u00eb m\u00eb e gjer\u00eb.<\/p>\n<p>M\u00eb interesonte eksperimenti me OS \u00abElbrus\u00bb. Pas p\u00ebrmir\u00ebsimit t\u00eb paket\u00ebs Veeam, produkti yn\u00eb u instalua dhe punoi. P\u00ebr k\u00ebt\u00eb eksperimento kam shkruar n\u00eb Habr n\u00eb <noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/veeam\/blog\/447960\/\">artikulli yn\u00eb<\/a><\/noindex>. <\/p>\n<p>Nd\u00ebrkoh\u00eb, mb\u00ebshtetja p\u00ebr distribucionet e reja vazhdon. Priten versioni 4.0. Po shfaqet nj\u00eb beta, k\u00ebshtu q\u00eb mbajini syt\u00eb nga <noindex><a rel=\"nofollow\" href=\"https:\/\/www.veeam.com\/whats-new-linux-agent.html\">whats-new<\/a><\/noindex>!<br \/>\n<br \/>Burimi: <a content=\"nofollow\" rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/veeam\/blog\/471226\/\">habr.com<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"<p>\u0421\u043e\u0437\u0434\u0430\u0442\u044c \u043f\u0440\u0438\u043b\u043e\u0436\u0435\u043d\u0438\u0435 \u0434\u043b\u044f \u0440\u0435\u0437\u0435\u0440\u0432\u043d\u043e\u0433\u043e \u043a\u043e\u043f\u0438\u0440\u043e\u0432\u0430\u043d\u0438\u044f, \u0440\u0430\u0431\u043e\u0442\u0430\u044e\u0449\u0435\u0435 \u043d\u0430 \u043b\u044e\u0431\u043e\u043c \u0434\u0438\u0441\u0442\u0440\u0438\u0431\u0443\u0442\u0438\u0432\u0435 \u2014 \u0437\u0430\u0434\u0430\u0447\u043a\u0430 \u043d\u0435\u043f\u0440\u043e\u0441\u0442\u0430\u044f. \u0427\u0442\u043e\u0431\u044b \u043e\u0431\u0435\u0441\u043f\u0435\u0447\u0438\u0442\u044c \u0440\u0430\u0431\u043e\u0442\u0443 Veeam Agent for Linux \u043d\u0430 \u0434\u0438\u0441\u0442\u0440\u0438\u0431\u0443\u0442\u0438\u0432\u0430\u0445 \u043e\u0442 Red Hat 6 \u0438 Debian 6, \u0434\u043e OpenSUSE 15.1 \u0438 Ubuntu 19.04 \u043f\u0440\u0438\u0445\u043e\u0434\u0438\u0442\u0441\u044f \u0440\u0435\u0448\u0430\u0442\u044c \u0441\u043f\u0435\u043a\u0442\u0440 \u043f\u0440\u043e\u0431\u043b\u0435\u043c, \u043e\u0441\u043e\u0431\u0435\u043d\u043d\u043e \u0435\u0441\u043b\u0438 \u0443\u0447\u0435\u0441\u0442\u044c, \u0447\u0442\u043e \u0432 \u0441\u043e\u0441\u0442\u0430\u0432 \u043f\u0440\u043e\u0433\u0440\u0430\u043c\u043c\u043d\u043e\u0433\u043e \u043f\u0440\u043e\u0434\u0443\u043a\u0442\u0430 \u0432\u0445\u043e\u0434\u0438\u0442 \u043c\u043e\u0434\u0443\u043b\u044c \u044f\u0434\u0440\u0430. \u0421\u0442\u0430\u0442\u044c\u044f \u0441\u043e\u0437\u0434\u0430\u043d\u0430 \u043f\u043e \u043c\u0430\u0442\u0435\u0440\u0438\u0430\u043b\u0430\u043c \u0432\u044b\u0441\u0442\u0443\u043f\u043b\u0435\u043d\u0438\u044f \u043d\u0430 [&hellip;]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":29206,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-38929","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-administrirovanie"],"aioseo_notices":[],"aioseo_head":"\n\t\t<!-- All in One SEO 5.0.2 - aioseo.com -->\n\t<meta name=\"description\" content=\"\u0421\u043e\u0437\u0434\u0430\u0442\u044c \u043f\u0440\u0438\u043b\u043e\u0436\u0435\u043d\u0438\u0435 \u0434\u043b\u044f \u0440\u0435\u0437\u0435\u0440\u0432\u043d\u043e\u0433\u043e.\" \/>\n\t<meta name=\"robots\" content=\"max-image-preview:large\" \/>\n\t<meta name=\"author\" content=\"Yuri Gagarin\"\/>\n\t<link rel=\"canonical\" href=\"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/linux-mnogolikij-kak-rabotat-na-lyubom-distributive\" \/>\n\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.2\" \/>\n\t\t<meta property=\"og:locale\" content=\"sq_AL\" \/>\n\t\t<meta property=\"og:site_name\" content=\"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b\" \/>\n\t\t<meta property=\"og:type\" content=\"article\" \/>\n\t\t<meta property=\"og:title\" content=\"\ud83e\udd47Linux \u043c\u043d\u043e\u0433\u043e\u043b\u0438\u043a\u0438\u0439: \u043a\u0430\u043a \u0440\u0430\u0431\u043e\u0442\u0430\u0442\u044c \u043d\u0430 \u043b\u044e\u0431\u043e\u043c \u0434\u0438\u0441\u0442\u0440\u0438\u0431\u0443\u0442\u0438\u0432\u0435 | ProHoster\" \/>\n\t\t<meta property=\"og:description\" content=\"\u0421\u043e\u0437\u0434\u0430\u0442\u044c \u043f\u0440\u0438\u043b\u043e\u0436\u0435\u043d\u0438\u0435 \u0434\u043b\u044f \u0440\u0435\u0437\u0435\u0440\u0432\u043d\u043e\u0433\u043e.\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/linux-mnogolikij-kak-rabotat-na-lyubom-distributive\" \/>\n\t\t<meta property=\"og:image\" content=\"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg\" \/>\n\t\t<meta property=\"og:image:secure_url\" content=\"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg\" \/>\n\t\t<meta property=\"og:image:width\" content=\"350\" \/>\n\t\t<meta property=\"og:image:height\" content=\"350\" \/>\n\t\t<meta property=\"article:published_time\" content=\"2019-10-31T19:26:48+00:00\" \/>\n\t\t<meta property=\"article:modified_time\" content=\"2019-10-31T19:26:48+00:00\" \/>\n\t\t<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/prohoster\" \/>\n\t\t<meta property=\"article:author\" content=\"https:\/\/www.facebook.com\/prohoster\" \/>\n\t\t<!-- All in One SEO -->\n\n","aioseo_head_json":{"title":"\ud83e\udd47Linux i shum\u00ebansh\u00ebm: si t\u00eb punoni n\u00eb \u00e7do shp\u00ebrndarje | ProHoster","description":"Krijoni nj\u00eb aplikacion p\u00ebr rezervim.","canonical_url":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/linux-mnogolikij-kak-rabotat-na-lyubom-distributive","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"sq_AL","og:site_name":"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b","og:type":"article","og:title":"\ud83e\udd47Linux \u043c\u043d\u043e\u0433\u043e\u043b\u0438\u043a\u0438\u0439: \u043a\u0430\u043a \u0440\u0430\u0431\u043e\u0442\u0430\u0442\u044c \u043d\u0430 \u043b\u044e\u0431\u043e\u043c \u0434\u0438\u0441\u0442\u0440\u0438\u0431\u0443\u0442\u0438\u0432\u0435 | ProHoster","og:description":"\u0421\u043e\u0437\u0434\u0430\u0442\u044c \u043f\u0440\u0438\u043b\u043e\u0436\u0435\u043d\u0438\u0435 \u0434\u043b\u044f \u0440\u0435\u0437\u0435\u0440\u0432\u043d\u043e\u0433\u043e.","og:url":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/linux-mnogolikij-kak-rabotat-na-lyubom-distributive","og:image":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:secure_url":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:width":350,"og:image:height":350,"article:published_time":"2019-10-31T19:26:48+00:00","article:modified_time":"2019-10-31T19:26:48+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"38929","title":null,"description":null,"keywords":null,"keyphrases":null,"primary_term":null,"canonical_url":null,"og_title":null,"og_description":null,"og_object_type":"default","og_image_type":"default","og_image_url":null,"og_image_width":null,"og_image_height":null,"og_image_custom_url":null,"og_image_custom_fields":null,"og_video":null,"og_custom_url":null,"og_article_section":null,"og_article_tags":null,"twitter_use_og":false,"twitter_card":"default","twitter_image_type":"default","twitter_image_url":null,"twitter_image_custom_url":null,"twitter_image_custom_fields":null,"twitter_title":null,"twitter_description":null,"schema":{"blockGraphs":[],"customGraphs":[],"default":{"data":{"Article":[],"Course":[],"Dataset":[],"FAQPage":[],"Movie":[],"Person":[],"Product":[],"ProductReview":[],"Car":[],"Recipe":[],"Service":[],"SoftwareApplication":[],"WebPage":[]},"graphName":"","isEnabled":true},"graphs":[]},"schema_type":null,"schema_type_options":null,"pillar_content":false,"robots_default":true,"robots_noindex":false,"robots_noarchive":false,"robots_nosnippet":false,"robots_nofollow":false,"robots_noimageindex":false,"robots_noodp":false,"robots_notranslate":false,"robots_max_snippet":null,"robots_max_videopreview":null,"robots_max_imagepreview":"large","priority":null,"frequency":null,"local_seo":null,"seo_analyzer_scan_date":"2026-01-23 23:59:19","breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-03-01 01:00:26","updated":"2026-01-23 23:59:19","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts\/38929","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/comments?post=38929"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts\/38929\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media\/29206"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media?parent=38929"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/categories?post=38929"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/tags?post=38929"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}