{"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 \u00ebsht\u00eb shum\u00ebshkalla: si t\u00eb punoni n\u00eb \u00e7do distribucion","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p><img decoding=\"async\" alt=\"Linux \u00ebsht\u00eb shum\u00ebshkalla: si t\u00eb punoni n\u00eb \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 detyr\u00eb e v\u00ebshtir\u00eb. P\u00ebr t\u00eb siguruar funksionimin e Veeam Agent p\u00ebr Linux n\u00eb distribucione 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, ve\u00e7an\u00ebrisht n\u00ebse merret parasysh se produkti p\u00ebrfshin nj\u00eb modul b\u00ebrthamor.<\/p>\n<p>Artikulli \u00ebsht\u00eb krijuar sipas materialeve t\u00eb prezantimit n\u00eb konferenc\u00eb <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 nuk \u00ebsht\u00eb vet\u00ebm nj\u00eb nga sistemet operative m\u00eb t\u00eb njohura. N\u00eb thelb, ajo \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 distribucione q\u00eb dallohen nga grupi i komponenteve softuerike. Dhe k\u00ebtu shfaqet nj\u00eb problem: p\u00ebr t\u00eb siguruar q\u00eb produkti t\u00eb funksionoj\u00eb n\u00eb \u00e7do distribucion, duhet t\u00eb merret parasysh 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 shp\u00ebrndarjes s\u00eb produktit p\u00ebr distribucione t\u00eb ndryshme.<br \/>\nM\u00ebnyra m\u00eb tipike e shp\u00ebrndarjes s\u00eb produkteve softuerike \u00ebsht\u00eb t\u00eb ngarkohet nj\u00eb paket\u00eb n\u00eb repository, n\u00eb m\u00ebnyr\u00eb q\u00eb menaxheri i paketave i p\u00ebrfshir\u00eb n\u00eb sistem t\u00eb mund ta instaloj\u00eb at\u00eb nga aty.<br \/>\nMegjithat\u00eb, formatet popullore t\u00eb paketave q\u00eb kemi jan\u00eb dy: <i>rpm<\/i> dhe <i>deb<\/i>. Pra, do t\u00eb duhet t\u00eb mb\u00ebshtesim secilin.<\/p>\n<p>N\u00eb bot\u00ebn e pakove deb, niveli i kompatibilitetit \u00ebsht\u00eb mbres\u00ebl\u00ebn\u00ebs. E nj\u00ebjta paket\u00eb funksionon po aq mir\u00eb si n\u00eb Debian 6 ashtu edhe n\u00eb Ubuntu 19.04. Standardet e procesit t\u00eb nd\u00ebrtimit t\u00eb pakove dhe pun\u00ebs me to, t\u00eb vendosura n\u00eb distribucionet e vjetra t\u00eb Debian, mbeten t\u00eb vlefshme edhe n\u00eb Linux Mint dhe elementary OS. Prandaj, p\u00ebr Veeam Agent for Linux mjafton nj\u00eb deb-paket\u00eb p\u00ebr secil\u00ebn platform\u00eb harduerike.<\/p>\n<p>Nd\u00ebrkoh\u00eb, n\u00eb bot\u00ebn e pakove rpm, ndryshimet jan\u00eb t\u00eb m\u00ebdha. S\u00eb pari, p\u00ebr shkak se ekzistojn\u00eb dy distribues krejt\u00ebsisht t\u00eb pavarur, Red Hat dhe SUSE, p\u00ebr t\u00eb cil\u00ebt nuk nevojitet aspak kompatibiliteti. S\u00eb dyti, k\u00ebta distribues kan\u00eb distribucione me mb\u00ebshtetje teknike dhe eksperimentale. Midis tyre, gjithashtu nuk \u00ebsht\u00eb e nevojshme t\u00eb ket\u00eb kompatibilitet. Ne kemi arritur q\u00eb p\u00ebr el6, el7 dhe el8 t\u00eb kemi paketa t\u00eb ve\u00e7anta. Nj\u00eb paket\u00eb ve\u00e7mas p\u00ebr Fedora. Paketa 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 pakove. <\/p>\n<h2>Problemi i var\u00ebsive<\/h2>\n<p>\nFatkeq\u00ebsisht, t\u00eb nj\u00ebjtat paketa shpesh ndodhen me emra t\u00eb ndrysh\u00ebm n\u00eb distribucionet e ndryshme. M\u00eb posht\u00eb \u00ebsht\u00eb nj\u00eb list\u00eb jo t\u00eb plot\u00eb 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 rezultat, lista e var\u00ebsive rezulton e ve\u00e7ant\u00eb p\u00ebr distribucionin. <\/p>\n<p>N\u00eb raste m\u00eb t\u00eb k\u00ebqija, nj\u00eb version i ri fshihet pas emrit t\u00eb vjet\u00ebr t\u00eb paket\u00ebs. <\/p>\n<p><b>Shembuj:<\/b><\/p>\n<p>N\u00eb Fedora 24, paketa u p\u00ebrmir\u00ebsua <i>ncurses<\/i> nga versioni 5 n\u00eb versionin 6. Produkti yn\u00eb u nd\u00ebrtua pik\u00ebrisht me versionin e 5-t\u00eb, p\u00ebr t\u00eb siguruar p\u00ebrputhshm\u00ebrin\u00eb me distribucionet e vjetra. P\u00ebr t\u00eb p\u00ebrdorur versionin e vjet\u00ebr t\u00eb 5-t\u00eb t\u00eb bibliotek\u00ebs n\u00eb Fedora 24, duhej t\u00eb p\u00ebrdorej paketa <i>ncurses-compat-libs<\/i>. <\/p>\n<p>Si rezultat, p\u00ebr Fedora shfaqen dy paketa, me var\u00ebsi t\u00eb ndryshme. <\/p>\n<p>M\u00eb pas b\u00ebhet m\u00eb interesante. Pas nj\u00eb azhurnimi tjet\u00ebr t\u00eb distribucionit, paketa <i>ncurses-compat-libs<\/i> me versionin e 5-t\u00eb t\u00eb bibliotek\u00ebs b\u00ebhet e paaksesueshme. P\u00ebr distribuitorin, \u00ebsht\u00eb e kushtueshme t\u00eb ruaj\u00eb bibliotekat e vjetra n\u00eb versionin e ri t\u00eb distribucionit. Pas disa koh\u00ebsh, problemi u p\u00ebrs\u00ebrit edhe n\u00eb distribucionet SUSE.<\/p>\n<p>Si rezultat, p\u00ebr disa distribucione duhej t\u00eb hiqej var\u00ebsia e drejtp\u00ebrdrejt\u00eb nga <i>ncurses-libs<\/i>, dhe produkti t\u00eb p\u00ebrmir\u00ebsohej n\u00eb m\u00ebnyr\u00eb q\u00eb t\u00eb funksiononte me \u00e7do version t\u00eb bibliotek\u00ebs.<\/p>\n<p>Kujdes, n\u00eb versionin 8 t\u00eb Red Hat nuk ka m\u00eb meta-paket\u00ebn <i>python<\/i>, e cila i referohej t\u00eb vjet\u00ebr i mir\u00eb <i>python 2.7<\/i>. Ekziston <i>python2<\/i> dhe <i>python<\/i>3. <\/p>\n<h2>Alternativa p\u00ebr menaxher\u00ebt e paketave<\/h2>\n<p>\nProblemi me var\u00ebsit\u00eb \u00ebsht\u00eb i vjet\u00ebr dhe i njohur. Mjafton t\u00eb kujtojm\u00eb 'Dependency hell'. <br \/>\nT\u00eb kombinojn\u00eb biblioteka dhe aplikacione t\u00eb ndryshme n\u00eb m\u00ebnyr\u00eb q\u00eb t\u00eb funksionojn\u00eb stabilisht dhe pa konflikte \u2014 pozita e k\u00ebsaj detyre p\u00ebrpiqet t\u00eb zgjidh\u00eb \u00e7do shp\u00ebrndar\u00ebs Linux.<\/p>\n<p>Ndryshe e trajton k\u00ebt\u00eb problem menaxheri i paketave <b>Snappy<\/b> nga Canonical. Ideja kryesore: aplikacioni ekzekutohet n\u00eb nj\u00eb sandbox t\u00eb izoluar dhe t\u00eb mbrojtur nga sistemi kryesor. N\u00ebse aplikacionit i nevojiten biblioteka, ato vijn\u00eb s\u00eb bashku me aplikacionin.<\/p>\n<p><b>Flatpak<\/b> po ashtu lejon ekzekutimin e aplikacioneve n\u00eb sandbbox duke p\u00ebrdorur Linux Containers. Ideja e sandbbox-it 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 e <b>Flatpak<\/b> instalimi dhe ekzekutimi i aplikacionit \u00ebsht\u00eb e mundur edhe pa dijen e administratorit.<\/p>\n<p>Problemi kryesor \u00ebsht\u00eb se jo t\u00eb gjitha aplikacionet mund t\u00eb punojn\u00eb n\u00eb sandbbox. Disa kan\u00eb nevoj\u00eb p\u00ebr qasje t\u00eb drejtp\u00ebrdrejt\u00eb n\u00eb platform\u00eb. Nuk po flas p\u00ebr modulet e b\u00ebrtham\u00ebs, t\u00eb cilat varen drejtp\u00ebrdrejt nga b\u00ebrthama dhe nuk integrohen n\u00eb konceptin e sandbbox-it. <\/p>\n<p>Problemi i dyt\u00eb \u00ebsht\u00eb se distribucionet popullore n\u00eb ambientin 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 ndodhet as n\u00eb <noindex><a rel=\"nofollow\" href=\"https:\/\/snapcraft.io\/\">snapcraft.io<\/a><\/noindex> as n\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 paketave, do t\u00eb theksoj se ka nj\u00eb mund\u00ebsi p\u00ebr t\u00eb hequr dor\u00eb krejt\u00ebsisht nga menaxher\u00ebt e paketave, duke bashkuar n\u00eb nj\u00eb paket\u00eb skedar\u00ebt binar\u00eb dhe skriptin p\u00ebr instalimin e tyre. <\/p>\n<p>Nj\u00eb bundle e till\u00eb lejon krijimin e nj\u00eb pakete t\u00eb vetme p\u00ebr distribucionet dhe platformat e ndryshme, duke realizuar nj\u00eb proces interaktiv instalimi duke b\u00ebr\u00eb personalizimin e nevojsh\u00ebm. Kam hasur n\u00eb k\u00ebto paketa p\u00ebr Linux vet\u00ebm nga VMware.<\/p>\n<h2>Problemi i p\u00ebrdit\u00ebsimeve<\/h2>\n<p>\n<img decoding=\"async\" alt=\"Linux \u00ebsht\u00eb shum\u00ebshkalla: si t\u00eb punoni n\u00eb \u00e7do distribucion\" src=\"\/wp-content\/uploads\/2019\/10\/aa14b10a434c28541574421d97807de7.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nMadje n\u00ebse t\u00eb gjitha problemet me var\u00ebsit\u00eb zgjidhen, programi mund t\u00eb funksionoj\u00eb ndryshe n\u00eb t\u00eb nj\u00ebjtin sistem distribucioni. Kjo ndodh p\u00ebr shkak t\u00eb p\u00ebrdit\u00ebsimeve.<\/p>\n<p>Ekzistojn\u00eb 3 strategji p\u00ebr p\u00ebrdit\u00ebsimin:<\/p>\n<ul>\n<li>E th simplest \u2013 kurr\u00eb mos p\u00ebrdit\u00ebso. E konfigurove serverin dhe e harrove. Pse p\u00ebrdit\u00ebsime, n\u00ebse gjith\u00e7ka funksionon? Problemet fillojn\u00eb me kontaktin e par\u00eb n\u00eb sh\u00ebrbimin e mb\u00ebshtetjes. Krijuesi i distribucionit mb\u00ebshtet vet\u00ebm versionin e p\u00ebrdit\u00ebsuar. <\/li>\n<li>Mund t\u00eb besoni distributorin dhe t\u00eb konfiguroni p\u00ebrdit\u00ebsimin automatike. N\u00eb k\u00ebt\u00eb rast, telefonata n\u00eb sh\u00ebrbimin e mb\u00ebshtetjes \u00ebsht\u00eb e mundshme menj\u00ebher\u00eb pas nj\u00eb p\u00ebrdit\u00ebsimi t\u00eb d\u00ebshtuar.<\/li>\n<li>Opsioni i p\u00ebrdit\u00ebsimit manual pas prov\u00ebs n\u00eb infrastruktur\u00ebn testuese \u00ebsht\u00eb m\u00eb i sigurt, por i shtrenjt\u00eb dhe k\u00ebrkon shum\u00eb pun\u00eb. Jo t\u00eb gjitha mund ta lejojn\u00eb veten.<\/li>\n<\/ul>\n<p>\nDukeq\u00eb p\u00ebrdorues t\u00eb ndrysh\u00ebm p\u00ebrdorin strategji t\u00eb ndryshme p\u00ebr p\u00ebrdit\u00ebsimin, duhet t\u00eb mb\u00ebshtetet si versioni m\u00eb i ri, ashtu edhe t\u00eb gjitha versionet e m\u00ebparshme t\u00eb l\u00ebshuara. Kjo komplikon procesin e zhvillimit dhe testimit, duke shtuar dhimbje koke p\u00ebr sh\u00ebrbimin e mb\u00ebshtetjes.<\/p>\n<h2>Diferenca e platformave harduerike<\/h2>\n<p>\nPlatformat e ndryshme harduerike jan\u00eb nj\u00eb problem, kryesisht i ve\u00e7ant\u00eb p\u00ebr kodin native. T\u00eb pakt\u00ebn, duhet t\u00eb grumbullohen binar\u00ebt p\u00ebr \u00e7do platform\u00eb t\u00eb mb\u00ebshtetur.<\/p>\n<p>N\u00eb projektin Veeam Agent p\u00ebr Linux ende nuk mund t\u00eb mb\u00ebshtesim asgj\u00eb t\u00eb till\u00eb si RISC.<\/p>\n<p>Nuk do t\u00eb ndalem n\u00eb k\u00ebt\u00eb \u00e7\u00ebshtje n\u00eb detaje. Do t\u00eb theksoj vet\u00ebm problemet kryesore: llojet e varura nga platforma, si <code>size_t<\/code>, p\u00ebrputhja e strukturave dhe rendi i bajtave.<\/p>\n<h2>Lidhja statike dhe\/apo dinamike<\/h2>\n<p>\n<img decoding=\"async\" alt=\"Linux \u00ebsht\u00eb shum\u00ebshkalla: si t\u00eb punoni n\u00eb \u00e7do distribucion\" src=\"\/wp-content\/uploads\/2019\/10\/dc473aad4ea0818940af7eafdbc641fd.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nPoroshtja \"Si t\u00eb lidhemi me bibliotekat - n\u00eb m\u00ebnyr\u00eb dinamike apo statike?\" ia vlen t\u00eb diskutohet.<\/p>\n<p>Si rregull, aplikacionet C\/C++ n\u00ebn Linux p\u00ebrdorin lidhjen dinamike. Kjo funksionon mir\u00eb n\u00ebse aplikacioni \u00ebsht\u00eb nd\u00ebrtuar posa\u00e7\u00ebrisht p\u00ebr nj\u00eb distribucion t\u00eb caktuar.<\/p>\n<p>N\u00ebse q\u00ebllimi \u00ebsht\u00eb t\u00eb p\u00ebrfshihet nj\u00eb gam\u00eb e gjer\u00eb distribuimesh me nj\u00eb skedar binar, at\u00ebher\u00eb duhet t\u00eb fokusohemi n\u00eb distribucionin m\u00eb t\u00eb vjet\u00ebr t\u00eb mb\u00ebshtetur. P\u00ebr ne, ky \u00ebsht\u00eb Red Hat 6. Ai p\u00ebrmban gcc 4.4, i cili as nuk mb\u00ebshtet 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 nj\u00eb rast t\u00eb till\u00eb, p\u00ebr Red Hat 6 duhet t\u00eb sjellim bibliotek\u00ebn libstdc++ dhe boost me vete. M\u00eb e thjeshta \u00ebsht\u00eb t\u00eb lidhemi me to n\u00eb m\u00ebnyr\u00eb statike.<\/p>\n<p>Por fatkeq\u00ebsisht, jo t\u00eb gjitha bibliotekat mund t\u00eb lidhen statikisht.<\/p>\n<p>S\u00eb pari, bibliotekat sistemore, si <i>libfuse<\/i>, <i>libblkid<\/i> duhen lidhur n\u00eb m\u00ebnyr\u00eb dinamike, p\u00ebr t'u siguruar n\u00eb p\u00ebrputhshm\u00ebrin\u00eb e tyre me b\u00ebrtham\u00ebn dhe modulat 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 biblioteka vet\u00ebm me kod opensource. MIT dhe BSD lejojn\u00eb lidhjen statike dhe ndezin biblioteka n\u00eb projekt. Nd\u00ebrsa LGPL duket se nuk e kund\u00ebrshton lidhjen statike, por k\u00ebrkon q\u00eb t\u00eb ofrohen n\u00eb publik skedar\u00ebt e nevojsh\u00ebm p\u00ebr lidhje. <\/p>\n<p>N\u00eb p\u00ebrgjith\u00ebsi, p\u00ebrdorimi i lidhjes dinamike do t\u00eb siguroj\u00eb q\u00eb t\u00eb mos keni nevoj\u00eb t\u00eb ofroni asgj\u00eb.<\/p>\n<h2>Nd\u00ebrtimi i aplikacioneve C\/C++<\/h2>\n<p>\nP\u00ebr t\u00eb nd\u00ebrtuar aplikacione C\/C++ p\u00ebr platforma dhe distribuime t\u00eb ndryshme, mjafton t\u00eb zgjidhni ose t\u00eb grumbulloni gcc-n\u00eb e duhur dhe t\u00eb p\u00ebrdorni kompilator\u00eb t\u00eb kryq\u00ebzuar p\u00ebr arkitekturat specifike, dhe t\u00eb grumbulloni t\u00eb gjith\u00eb setin e bibliotikave. Ky \u00ebsht\u00eb nj\u00eb proces i realizuesh\u00ebm, por mjaft i mundimsh\u00ebm. Dhe nuk ka ndonj\u00eb garanci q\u00eb kompilatori dhe bibliotekat e zgjedhura do t\u00eb sigurojn\u00eb nj\u00eb version funksional. <\/p>\n<p>Pika e dukshme: infrastruktura ndjesh\u00ebm thjeshtohet, pasi e gjith\u00eb procedura e nd\u00ebrtimit mund t\u00eb realizohet n\u00eb nj\u00eb makin\u00eb. P\u00ebr m\u00eb tep\u00ebr, mjafton t\u00eb krijoni nj\u00eb set t\u00eb vet\u00ebm t\u00eb skedar\u00ebve binar\u00eb p\u00ebr nj\u00eb arkitektur\u00eb dhe mund t'i paketoni ato n\u00eb paketa p\u00ebr distribuime t\u00eb ndryshme. K\u00ebshtu krijohen paketat veeam p\u00ebr Veeam Agent p\u00ebr Linux.<\/p>\n<p>N\u00eb vend t\u00eb k\u00ebtij varianti, mund t\u00eb p\u00ebrgatiten thjesht fermat e build-it, dometh\u00ebn\u00eb disa makina p\u00ebr nd\u00ebrtimin. \u00c7do makin\u00eb e till\u00eb do t\u00eb siguroj\u00eb kompaktimin e aplikacionit dhe nd\u00ebrtimin e paket\u00ebs p\u00ebr shp\u00ebrndarjen e caktuar dhe arkitektur\u00ebn e caktuar. N\u00eb k\u00ebt\u00eb rast, kompaktimi b\u00ebhet me mjete q\u00eb ka p\u00ebrgatitur shp\u00ebrndar\u00ebsi. K\u00ebshtu, faza e p\u00ebrgatitjes s\u00eb kompajlerit dhe p\u00ebrzgjedhja e bibliotekave eliminohen. P\u00ebr m\u00eb tep\u00ebr, procesi i nd\u00ebrtimit mund t\u00eb parajtohet leht\u00ebsisht. <\/p>\n<p>Ka, p\u00ebr t\u00eb v\u00ebrtet\u00eb, edhe 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 set i ve\u00e7ant\u00eb i skedar\u00ebve binar\u00eb. Nj\u00eb tjet\u00ebr disavantazh \u00ebsht\u00eb se duhet t\u00eb sh\u00ebrbehet nj\u00eb num\u00ebr i till\u00eb makinerish, duke alokuar nj\u00eb sasi t\u00eb madhe hap\u00ebsire disk dhe memorie operative. <\/p>\n<p>K\u00ebshtu krijohen paketat KMOD t\u00eb modulit t\u00eb kernelit veeamsnap p\u00ebr shp\u00ebrndarjet Red Hat.<\/p>\n<h2>Open Build Service<\/h2>\n<p>\nKoleg\u00ebt nga SUSE kan\u00eb provuar t\u00eb realizojn\u00eb nj\u00eb mesatare t\u00eb art\u00eb n\u00eb form\u00ebn e sh\u00ebrbimit 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, \u00ebsht\u00eb nj\u00eb hipervizor q\u00eb krijon nj\u00eb makin\u00eb virtuale, instalon n\u00eb t\u00eb t\u00eb gjitha paketat e nevojshme, ekzekuton compilimin e aplikacionit dhe nd\u00ebrtimin e paket\u00ebs n\u00eb k\u00ebt\u00eb ambient t\u00eb izoluar, pas s\u00eb cil\u00ebs kjo makin\u00eb virtuale lirohet.<\/p>\n<p><img decoding=\"async\" alt=\"Linux \u00ebsht\u00eb shum\u00ebshkalla: si t\u00eb punoni n\u00eb \u00e7do distribucion\" src=\"\/wp-content\/uploads\/2019\/10\/93d2a70c589a7186ecef85a7863e59e8.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nPlanifikuesi i implementuar n\u00eb OpenBuildService do t\u00eb p\u00ebrcaktoj\u00eb se sa makina virtuale mund t\u00eb aktivizohen p\u00ebr nj\u00eb shpejt\u00ebsi optimale t\u00eb nd\u00ebrtimit t\u00eb paketave. Mekanizmi i integruar i n\u00ebnshkrimit do t\u00eb n\u00ebnshkruaj\u00eb automatikisht paketat dhe do t'i publikoj\u00eb ato n\u00eb nj\u00eb depot t\u00eb integruar. Sistemi i brendsh\u00ebm i kontrollit t\u00eb versioneve do t\u00eb ruaj\u00eb historikun e ndryshimeve dhe nd\u00ebrtimeve. Mjafton thjesht t\u00eb shtoni burimet tuaja brenda k\u00ebtij sistemi. As q\u00eb \u00ebsht\u00eb e nevojshme t\u00eb ngrihet nj\u00eb server, mund t\u00eb p\u00ebrdorni nj\u00eb t\u00eb hapur.<\/p>\n<p>Megjithat\u00eb, k\u00ebtu ka nj\u00eb problem: nj\u00eb kombinat i till\u00eb \u00ebsht\u00eb i v\u00ebshtir\u00eb p\u00ebr t'u integruar n\u00eb infrastruktur\u00ebn ekzistuese. P\u00ebr shembull, kontrolli i versioneve nuk \u00ebsht\u00eb i nevojsh\u00ebm, ne tashm\u00eb kemi nj\u00eb p\u00ebr burimet tona. Mekanizmi i n\u00ebnshkrimit ndryshon: p\u00ebrdoret nj\u00eb server i ve\u00e7ant\u00eb. Nj\u00eb depo gjithashtu nuk \u00ebsht\u00eb e nevojshme. <\/p>\n<p>P\u00ebr m\u00eb tep\u00ebr, mb\u00ebshtetje p\u00ebr distribucione t\u00eb tjera \u2014 p\u00ebr shembull, Red Hat \u2014 \u00ebsht\u00eb e implementuar mjaft dob\u00ebt, e cila \u00ebsht\u00eb krejt\u00ebsisht e kuptueshme.<\/p>\n<p>Avantazhi i k\u00ebtij sh\u00ebrbimi \u00ebsht\u00eb mb\u00ebshtetje e shpejt\u00eb p\u00ebr versionin e radh\u00ebs t\u00eb distribucionit SUSE. Deri n\u00eb shpalljen zyrtare t\u00eb lansimit, paketat e nevojshme p\u00ebr nd\u00ebrtimin publikohen n\u00eb depo publike. Nj\u00eb i ri shfaqet n\u00eb list\u00ebn e distribucioneve t\u00eb disponueshme n\u00eb OpenBuildService. Aktivizojm\u00eb kutin\u00eb, dhe ai shtohet n\u00eb planin e nd\u00ebrtimit. K\u00ebshtu, shtimi i nj\u00eb versioni t\u00eb ri t\u00eb distribucionit realizohet praktikisht me nj\u00eb klikim.<\/p>\n<p>N\u00eb infrastruktur\u00ebn ton\u00eb, duke p\u00ebrdorur OpenBuildService, nd\u00ebrtohen t\u00eb gjitha llojet e paketave KMP t\u00eb modulit t\u00eb b\u00ebrtham\u00ebs veeamsnap p\u00ebr distribucionet SUSE.<\/p>\n<p>N\u00eb vazhdim, do t\u00eb doja t\u00eb ndalesha te \u00e7\u00ebshtjet q\u00eb jan\u00eb specifike p\u00ebr modul\u00ebt e b\u00ebrtham\u00ebs.<\/p>\n<h2>kernel ABI<\/h2>\n<p>\nModul\u00ebt e b\u00ebrtham\u00ebs Linux historikisht jan\u00eb shp\u00ebrndar\u00eb n\u00eb form\u00ebn e kodit burimor. Kjo pasi krijuesit e b\u00ebrtham\u00ebs nuk shqet\u00ebsohen p\u00ebr mb\u00ebshtetje t\u00eb nj\u00eb API stabil p\u00ebr modul\u00ebt e b\u00ebrtham\u00ebs, e as n\u00eb nivelin binar, m\u00eb pas kABI.<\/p>\n<p>P\u00ebr t\u00eb nd\u00ebrtuar nj\u00eb modul p\u00ebr b\u00ebrtham\u00ebn vanilla, nevojiten patjet\u00ebr header-at e k\u00ebtij b\u00ebrthame, dhe ai do t\u00eb funksionoj\u00eb vet\u00ebm mbi k\u00ebt\u00eb b\u00ebrtham\u00eb. <\/p>\n<p>DKMS automatizojn\u00eb procesin e 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 shum\u00eb llojeve t\u00eb saj) p\u00ebrdorin modulet e b\u00ebrtham\u00ebs, ose nga depozita e shp\u00ebrndar\u00ebsit, ose t\u00eb nd\u00ebrtuara nga burimi me ndihm\u00ebn e DKMS.<\/p>\n<p>Megjithat\u00eb, kjo situat\u00eb nuk i k\u00ebnaq shum\u00eb segmentin Enterprise. Shp\u00ebrndar\u00ebsit e kodeve t\u00eb pron\u00ebsishme d\u00ebshirojn\u00eb t\u00eb shp\u00ebrndajn\u00eb produktin n\u00eb form\u00ebn e binar\u00ebve t\u00eb nd\u00ebrtuar. <\/p>\n<p>Administratoret nuk duan t\u00eb mbajn\u00eb mjete zhvillimi n\u00eb server\u00ebt production p\u00ebr arsye sigurie. Shp\u00ebrndar\u00ebsit e Enterprise Linux \u2014 si Red Hat dhe SUSE \u2014 kan\u00eb vendosur se p\u00ebr p\u00ebrdoruesit e tyre mund t\u00eb mb\u00ebshtesin nj\u00eb kABI t\u00eb q\u00ebndrueshme. Si rezultat, u krijuan paketat KMOD p\u00ebr Red Hat dhe paketat KMP p\u00ebr SUSE.<\/p>\n<p>Thelbi i nj\u00eb zgjidhjeje t\u00eb till\u00eb \u00ebsht\u00eb mjaft i thjesht\u00eb. P\u00ebr nj\u00eb version t\u00eb caktuar t\u00eb shp\u00ebrndarjes, API i b\u00ebrtham\u00ebs ngrihet. Shp\u00ebrndar\u00ebsi deklaron se p\u00ebrdor b\u00ebrtham\u00ebn, p\u00ebr shembull, 3.10, dhe b\u00ebn vet\u00ebm korrigjime dhe p\u00ebrmir\u00ebsime q\u00eb nuk ndikon aspak n\u00eb nd\u00ebrfaqet 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 t\u00eb ardhshmet pa nevoj\u00ebn e rip\u00ebrpunimit.<\/p>\n<p>Red Hat deklaron kABI p\u00ebrputhshm\u00ebrin\u00eb p\u00ebr shp\u00ebrndarjen gjat\u00eb t\u00eb gjith\u00eb ciklit t\u00eb saj t\u00eb jet\u00ebs. Kjo do t\u00eb thot\u00eb q\u00eb moduli i nd\u00ebrtuar p\u00ebr rhel 6.0 (l\u00ebshimi n\u00eb n\u00ebntor 2010) gjithashtu duhet t\u00eb funksionoj\u00eb n\u00eb versionin 6.10 (l\u00ebshimi n\u00eb qershor 2018). Dhe kjo \u00ebsht\u00eb pothuajse 8 vjet. Sigurisht, kjo \u00ebsht\u00eb nj\u00eb detyr\u00eb mjaft e komplikuar. <br \/>\nNe kemi regjistruar disa raste kur moduli veeamsnap ndaloi s\u00eb funksionuari p\u00ebr shkak t\u00eb problemeve me p\u00ebrshtatshm\u00ebrin\u00eb e kABI. <\/p>\n<p>Pasi q\u00eb moduli veeamsnap, i nd\u00ebrtuar p\u00ebr RHEL 7.0, u tregua i pap\u00ebrshtatsh\u00ebm me b\u00ebrtham\u00ebn nga RHEL 7.5, por p\u00ebrkundrazi ngarkohej dhe garantonte r\u00ebnien e serverit, ne hoq\u00ebm dor\u00eb nga p\u00ebrdorimi i p\u00ebrshtatshm\u00ebris\u00eb kABI p\u00ebr RHEL 7 n\u00eb t\u00ebr\u00ebsi. <\/p>\n<p>Aktualisht, paketa KMOD p\u00ebr RHEL 7 p\u00ebrmban nj\u00eb nd\u00ebrtim p\u00ebr \u00e7do version l\u00ebshimi dhe nj\u00eb skript q\u00eb siguron ngarkimin e modulit.<\/p>\n<p>SUSE e q\u00ebndroi ndaj problemit t\u00eb p\u00ebrshtatshm\u00ebris\u00eb kABI me m\u00eb shum\u00eb kujdes. Ata sigurojn\u00eb p\u00ebrshtatshm\u00ebrin\u00eb kABI vet\u00ebm brenda nj\u00eb service pack. <\/p>\n<p>P\u00ebr shembull, publikimi i SLES 12 ndodhi n\u00eb shtator 2014. Nd\u00ebrsa SLES 12 SP1 doli n\u00eb dhjetor 2015, q\u00eb do t\u00eb thot\u00eb se kaluan pak m\u00eb shum\u00eb se nj\u00eb vit. Megjithat\u00eb, edhe pse t\u00eb dy publikimet p\u00ebrdorin kernelin 3.12, ato jan\u00eb t\u00eb papajtueshme me kABI. \u00cbsht\u00eb e qart\u00eb se mbajtja e kABI t\u00eb pajtuesh\u00ebm p\u00ebr vet\u00ebm nj\u00eb vit \u00ebsht\u00eb shum\u00eb m\u00eb e leht\u00eb. Cikli vjetor i p\u00ebrdit\u00ebsimeve t\u00eb modulit t\u00eb kernelit 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 p\u00ebrcoll\u00ebm asnj\u00eb problem me pajtueshm\u00ebrin\u00eb e kABI n\u00eb modulit ton\u00eb veeamsnap. Megjithat\u00eb, numri i paketave p\u00ebr SUSE \u00ebsht\u00eb pothuajse nj\u00eb rend m\u00eb i madh.<\/p>\n<h2>Patch dhe backport<\/h2>\n<p>\nMegjith\u00ebse distributor\u00ebt p\u00ebrpiqen t\u00eb sigurojn\u00eb pajtueshm\u00ebrin\u00eb kABI dhe stabilitetin e kernelit, ata gjithashtu p\u00ebrpiqen t\u00eb p\u00ebrmir\u00ebsojn\u00eb performanc\u00ebn dhe t\u00eb eliminojn\u00eb defektet e k\u00ebtij kernelit stabil. <\/p>\n<p>N\u00eb t\u00eb nj\u00ebjt\u00ebn koh\u00eb, p\u00ebrve\u00e7 \"pun\u00ebs s\u00eb tyre mbi gabimet\", zhvilluesit e kernelit enterprise linux ndjekin ndryshimet n\u00eb kernelin vanilla dhe i transferojn\u00eb ato n\u00eb kernelin e tyre \"stabil\".<\/p>\n<p>ndonj\u00ebher\u00eb kjo \u00e7on n\u00eb <noindex><a rel=\"nofollow\" href=\"https:\/\/access.redhat.com\/solutions\/3658111\">gabime<\/a><\/noindex>.<\/p>\n<p>N\u00eb versionin e fundit t\u00eb Red Hat 6, nj\u00ebra nga azhornimet minor kishte nj\u00eb gabim. Kjo shkaktoi q\u00eb moduli veeamsnap t\u00eb \u00e7onte gjithmon\u00eb n\u00eb r\u00ebnie t\u00eb sistemit kur shp\u00ebrndante snapshotin. Duke krahasuar burimet e b\u00ebrtham\u00ebs p\u00ebrpara dhe pas azhornimit, zbuluam se shkaku ishte backport. Nj\u00eb rregullim i ngjash\u00ebm ishte b\u00ebr\u00eb n\u00eb b\u00ebrtham\u00ebn vanilla versioni 4.19. Por n\u00eb b\u00ebrtham\u00ebn vanilla, ky rregullim funksiononte normalisht, nd\u00ebrsa gjat\u00eb transferimit t\u00eb tij n\u00eb b\u00ebrtham\u00ebn 'stabile' 2.6.32 u shfaq nj\u00eb problem me bllokimin spin.<\/p>\n<p>Sigurisht, gabime ndodhin te t\u00eb gjith\u00eb dhe gjithmon\u00eb, por a ishte v\u00ebrtet e nevojshme t\u00eb merrej kodi nga 4.19 n\u00eb 2.6.32, duke rrezikuar stabilitetin?.. Nuk jam i sigurt...<\/p>\n<p>M\u00eb e keqja \u00ebsht\u00eb kur reklamimi p\u00ebrfshihet n\u00eb t\u00ebrheqjen e telas\u00eb 'stabilitet'  'modernizim'. Departamenti i marketingut ka nevoj\u00eb q\u00eb b\u00ebrthama e distribucionit t\u00eb azhornuar t\u00eb jet\u00eb e q\u00ebndrueshme, nga nj\u00ebra an\u00eb, dhe n\u00eb t\u00eb nj\u00ebjt\u00ebn koh\u00eb t\u00eb jet\u00eb m\u00eb e mir\u00eb n\u00eb performanc\u00eb dhe t\u00eb ket\u00eb tipare t\u00eb reja. Kjo sjell kompromise t\u00eb \u00e7uditshme. <\/p>\n<p>Kur b\u00ebra p\u00ebrpjekjen p\u00ebr t\u00eb grumbulluar modul n\u00eb b\u00ebrtham\u00ebn 4.4 t\u00eb SLES 12 SP3, me \u00e9tonim zbulova se kishte funksionalitete nga b\u00ebrthama e past\u00ebr 4.8. Sipas mendimit tim, implementimi i hyrjes\/dalitjes bllok t\u00eb b\u00ebrtham\u00ebs 4.4 t\u00eb SLES 12 SP3 m\u00eb shum\u00eb i ngjan 4.8 sesa l\u00ebshimi i m\u00ebparsh\u00ebm t\u00eb b\u00ebrtham\u00ebs stabil 4.4 t\u00eb SLES 12 SP2. Sa p\u00ebrqindje e kodit t\u00eb transferuar nga b\u00ebrthama 4.8 n\u00eb 4.4 t\u00eb SLES-\u00ebs p\u00ebr SP3, nuk mund ta gjykoj, por nuk m\u00eb vjen mir\u00eb ta quaj b\u00ebrtham\u00ebn ende t\u00eb stabil 4.4. <\/p>\n<p>M\u00eb e pak\u00ebndshmja n\u00eb k\u00ebt\u00eb \u00ebsht\u00eb se gjat\u00eb shkruarjes s\u00eb nj\u00eb moduli q\u00eb do t\u00eb punonte nj\u00ebsoj mir\u00eb n\u00eb b\u00ebrthama t\u00eb ndryshme, nuk mund t\u00eb mb\u00ebshtetesh m\u00eb n\u00eb versionin e b\u00ebrtham\u00ebs. Duhet t\u00eb marr\u00ebsh parasysh gjithashtu distribuimin. Mir\u00eb q\u00eb ndonj\u00ebher\u00eb mund t\u00eb lidhesh me nj\u00eb definicion q\u00eb shfaqet me funksionalitetin e ri, megjithat\u00eb kjo mund\u00ebsi nuk \u00ebsht\u00eb gjithmon\u00eb e pranishme. <\/p>\n<p>Si pasoj\u00eb, kodi mbushet me direktiva kur \u00ebsht\u00eb e nevojshme p\u00ebr kompilimin e kusht\u00ebzuar.<\/p>\n<p>Takohen gjithashtu dhe patch-e q\u00eb ndryshojn\u00eb API-n\u00eb e dokumentuar t\u00eb b\u00ebrtham\u00ebs. <br \/>\nKisha r\u00ebn\u00eb n\u00eb prangat e nj\u00eb distribuimi <noindex><a rel=\"nofollow\" href=\"https:\/\/neon.kde.org\/\">KDE neon<\/a><\/noindex> 5.16 dhe isha shum\u00eb i habitur kur pash\u00eb se thirja lookup_bdev n\u00eb k\u00ebt\u00eb version t\u00eb b\u00ebrtham\u00ebs kishte ndryshuar list\u00ebn e parametrave hyr\u00ebs.<\/p>\n<p>P\u00ebr t'u mbledhur, duhej t\u00eb shtohej nj\u00eb skript n\u00eb makefile q\u00eb kontrollon n\u00ebse ka nj\u00eb paramet\u00ebr mask n\u00eb funksionin lookup_bdev.<\/p>\n<h2>N\u00ebnshkrimi i moduleve t\u00eb b\u00ebrtham\u00ebs<\/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 e kABI-t stabil \u00ebsht\u00eb q\u00eb modulet e b\u00ebrtham\u00ebs n\u00eb formatin binar mund t\u00eb n\u00ebnshkruhen. N\u00eb k\u00ebt\u00eb rast, zhvilluesi mund t\u00eb jet\u00eb i sigurt se moduli nuk \u00ebsht\u00eb d\u00ebmtuar aksidentalisht ose ndryshuar q\u00ebllimisht. K\u00ebt\u00eb mund ta kontrolloni me komand\u00ebn modinfo. <\/p>\n<p>Distribucionet Red Hat dhe SUSE lejojn\u00eb t\u00eb kontrollohet n\u00ebnshkrimi i modulit dhe ta ngarkoni at\u00eb vet\u00ebm n\u00ebse sistemi ka regjistruar certifikat\u00ebn p\u00ebrkat\u00ebse. Certifikata \u00ebsht\u00eb \u00e7el\u00ebsi publik me t\u00eb cilin n\u00ebnshkruhet moduli. Ne e shp\u00ebrndajm\u00eb at\u00eb si nj\u00eb paket\u00eb t\u00eb ve\u00e7ant\u00eb.<\/p>\n<p>Problemi k\u00ebtu \u00ebsht\u00eb se certifikatat mund t\u00eb jen\u00eb ose t\u00eb p\u00ebrfshir\u00eb n\u00eb b\u00ebrtham\u00eb (ato p\u00ebrdoren nga shp\u00ebrndar\u00ebsit), ose duhet t\u00eb regjistrohen n\u00eb memorin\u00eb jo-volatile EFI me ndihm\u00ebn e utilitarit <i>mokutil<\/i>. Utilitari <i>mokutil<\/i> gjat\u00eb instalimit t\u00eb certifikat\u00ebs k\u00ebrkon nj\u00eb rinisje t\u00eb sistemit dhe para ngarkimit t\u00eb b\u00ebrtham\u00ebs s\u00eb sistemit operativ i propozon administratorit t\u00eb lejoj\u00eb ngarkimin e certifikat\u00ebs s\u00eb re. <\/p>\n<p>Pra kjo, shtimi i nj\u00eb certifikate k\u00ebrkon qasje fizike t\u00eb administratorit n\u00eb sistem. N\u00ebse makina ndodhet diku n\u00eb re ose thjesht n\u00eb nj\u00eb server t\u00eb larg\u00ebt me qasje vet\u00ebm p\u00ebrmes rrjetit (p\u00ebr shembull, p\u00ebrmes ssh), at\u00ebher\u00eb do t\u00eb jet\u00eb e pamundur t\u00eb shtoni certifikat\u00ebn. <\/p>\n<h2>EFI n\u00eb makina virtuale<\/h2>\n<p>\nPavar\u00ebsisht se EFI mb\u00ebshtetet gjer\u00ebsisht nga prodhuesit e pllakave n\u00ebn\u00eb p\u00ebr nj\u00eb koh\u00eb t\u00eb gjat\u00eb, gjat\u00eb instalimit t\u00eb sistemit, administratori mund t\u00eb mos mendoj\u00eb p\u00ebr nevoj\u00ebn e EFI-s\u00eb, dhe ai mund t\u00eb jet\u00eb i \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 parazgjedhur, ky funksionalitet p\u00ebr makinat Linux \u00ebsht\u00eb i \u00e7aktivizuar, q\u00eb do t\u00eb thot\u00eb se certifikata nuk mund t\u00eb instalohet. <\/p>\n<p>N\u00eb vSphere 6.5, vendosni opsionin <b>Secure Boot<\/b> mund t\u00eb b\u00ebhet vet\u00ebm n\u00eb versionin e vjet\u00ebr t\u00eb nd\u00ebrfaqes s\u00eb uebit, e cila punon p\u00ebrmes Flash. UI-u Web n\u00eb HTML-5 ende \u00ebsht\u00eb shum\u00eb prapa.<\/p>\n<h2>Distribucione eksperimentale<\/h2>\n<p>\nN\u00eb fund, le t\u00eb shqyrtojm\u00eb \u00e7\u00ebshtjen e distribucioneve eksperimentale dhe atyre pa mb\u00ebshtetje zyrtare. N\u00eb nj\u00ebr\u00ebn an\u00eb, \u00ebsht\u00eb e v\u00ebshtir\u00eb t\u00eb gjejm\u00eb k\u00ebto distribucione n\u00eb server\u00ebt e organizatave serioze. K\u00ebto distribucione nuk kan\u00eb mb\u00ebshtetje zyrtare. Prandaj, nuk \u00ebsht\u00eb e mundur t\u00eb sigurohet mb\u00ebshtetje teknike p\u00ebr produktin n\u00eb nj\u00eb distribuim t\u00eb till\u00eb. <\/p>\n<p>Megjithat\u00eb, k\u00ebto distribucione sh\u00ebrbejn\u00eb si 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 paq\u00ebndrueshme t\u00eb Debian. Ato jan\u00eb mjaft t\u00eb q\u00ebndrueshme. Aty 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 p\u00ebrdit\u00ebsuar. <\/p>\n<p>Prandaj, n\u00ebse di\u00e7ka nuk funksionon n\u00eb nj\u00eb distribuim eksperimental, kjo \u00ebsht\u00eb nj\u00eb mund\u00ebsi p\u00ebr t\u00eb hetuar problemin dhe p\u00ebr ta zgjidhur at\u00eb. Duhet t\u00eb jemi t\u00eb gatsh\u00ebm q\u00eb ky funksionalitet do t\u00eb shfaqet s\u00eb shpejti n\u00eb server\u00ebt e prodhimit t\u00eb p\u00ebrdoruesve.<\/p>\n<p>Lista e aktualizuar e distribucioneve zyrtarisht t\u00eb mb\u00ebshtetur p\u00ebr versionin 3.0 mund t\u00eb studiohet <noindex><a rel=\"nofollow\" href=\"https:\/\/helpcenter.veeam.com\/docs\/agentforlinux\/userguide\/system_requirements.html?ver=30\">k\u00ebtu<\/a><\/noindex>. Por lista e v\u00ebrtet\u00eb e distribucioneve n\u00eb t\u00eb cilat produkti yn\u00eb mund t\u00eb funksionoj\u00eb \u00ebsht\u00eb shum\u00eb m\u00eb e gjer\u00eb.<\/p>\n<p>Mua p\u00ebr mua, eksperimenti me sistemin operativ \u00abElbrus\u00bb ishte i interesant. Pasi u p\u00ebrmir\u00ebsua paketa veeam, produkti yn\u00eb u instalua dhe filloi t\u00eb punoj\u00eb. P\u00ebr k\u00ebt\u00eb eksperiment shkruajta n\u00eb Habra n\u00eb <noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/veeam\/blog\/447960\/\">artikullin<\/a><\/noindex>. <\/p>\n<p>Nd\u00ebrkoh\u00eb, mb\u00ebshtetja p\u00ebr distribucione t\u00eb reja vazhdon. Po presim t\u00eb dal\u00eb versioni 4.0. Padyshim q\u00eb duhet t\u00eb shfaqet beta, prandaj q\u00ebndroni t\u00eb informuar p\u00ebr <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 4.9.10 - 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 \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\" \/>\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) 4.9.10\" \/>\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 \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\" \/>\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 \u00ebsht\u00eb i larmish\u00ebm: si t\u00eb punoni n\u00eb \u00e7do distribucion | ProHoster","description":"Krijimi i nj\u00eb aplikacioni p\u00ebr backup q\u00eb punon n\u00eb \u00e7do distribucion \u00ebsht\u00eb nj\u00eb detyr\u00eb e v\u00ebshtir\u00eb. P\u00ebr t\u00eb siguruar 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 gam\u00eb problemi, ve\u00e7an\u00ebrisht duke pasur parasysh se produkti p\u00ebrmban nj\u00eb modul b\u00ebrtham\u00ebs. Artikulli \u00ebsht\u00eb krijuar mbi materialet e fjalimit n\u00eb","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 \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","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"},"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}]}}