Ƙirƙirar aikace-aikacen madadin da ke aiki akan kowane rarraba ba aiki mai sauƙi ba ne. Don tabbatar da Veeam Agent na Linux yana aiki akan rarrabawa daga Red Hat 6 da Debian 6, zuwa OpenSUSE 15.1 da Ubuntu 19.04, dole ne ku magance matsaloli da yawa, musamman la'akari da cewa samfurin software ya haɗa da ƙirar kwaya.
An ƙirƙiri labarin ne bisa kayan aiki daga jawabin da aka yi a taron .
Linux ba ɗaya daga cikin shahararrun tsarin aiki ba ne. Ainihin, wannan dandali ne a kan tushen da za ku iya yin wani abu na musamman, wani abu na ku. Godiya ga wannan, Linux yana da rabe-rabe da yawa waɗanda suka bambanta a cikin tsarin kayan aikin software. Kuma a nan matsala ta taso: don samfurin software ya yi aiki akan kowace rarraba, dole ne ku yi la'akari da fasalin kowane.
Manajan kunshin. .deb vs rpm
Bari mu fara da bayyananniyar matsala ta rarraba samfurin zuwa rarrabawa daban-daban.
Hanyar da ta fi dacewa don rarraba kayan aikin software ita ce sanya kunshin a kan ma'ajiya ta yadda mai sarrafa kunshin da aka gina a cikin tsarin zai iya shigar da shi daga can.
Koyaya, muna da shahararrun nau'ikan fakiti guda biyu: rpm и bashi. Wannan yana nufin kowa zai goyi bayansa.
A cikin duniyar fakitin bashi, matakin dacewa yana da ban mamaki. Fakiti ɗaya yana shigarwa kuma yana aiki daidai da kyau akan duka Debian 6 da Ubuntu 19.04. Ka'idodin tsarin ginin fakiti da aiki tare da su, waɗanda aka shimfida a cikin tsoffin rarrabawar Debian, sun kasance masu dacewa a cikin sabon Linux Mint da OS na farko. Don haka, a cikin yanayin Veeam Agent na Linux, kunshin bashi ɗaya na kowane dandamali na kayan masarufi ya wadatar.
Amma a cikin duniyar fakitin rpm, bambance-bambancen suna da kyau. Da fari dai, saboda gaskiyar cewa akwai masu rarraba gaba ɗaya masu zaman kansu guda biyu, Red Hat da SUSE, waɗanda dacewa gaba ɗaya ba lallai bane. Na biyu, waɗannan masu rarraba suna da kayan rarrabawa daga waɗannan. goyon baya da gwaji. Babu buƙatar daidaitawa tsakanin su ko. Ya juya cewa el6, el7 da el8 suna da nasu fakiti. Fakitin daban don Fedora. Fakiti don SLES11 da 12 da na daban don openSUSE. Babban matsalar ita ce dogara da sunayen kunshin.
Matsalar dogaro
Abin takaici, fakiti iri ɗaya sau da yawa suna ƙare ƙarƙashin sunaye daban-daban a cikin rabawa daban-daban. A ƙasa akwai jerin ɓangaren abubuwan dogaro na fakitin veeam.
Domin EL7:
Don SLES 12:
- liblkid
- libgcc
- libstdc++
- lanƙwasa-libs
- fuse-libs
- fayil-libs
- veeamsnap=3.0.2.1185
- liblkid1
- libgcc_s1
- libstdc++6
- libmagic1
- libfu2
- veeamsnap-kmp=3.0.2.1185
A sakamakon haka, jerin abubuwan dogaro na musamman ne don rarrabawa.
Abin da ya fi muni shine lokacin da sabuntawar sigar ta fara ɓoyewa ƙarƙashin sunan tsohon kunshin.
Alal misali:
An sabunta kunshin a cikin Fedora 24 jinya daga sigar 5 zuwa sigar 6. An gina samfurin mu tare da sigar 5 don tabbatar da dacewa tare da tsofaffin rarrabawa. Don amfani da tsohon sigar 5th na ɗakin karatu akan Fedora 24, dole ne in yi amfani da kunshin ncurses-compat-libs.
Sakamakon haka, akwai fakiti biyu don Fedora, tare da dogaro daban-daban.
Ƙari mai ban sha'awa. Bayan sabuntawa na rarraba na gaba, kunshin ncurses-compat-libs tare da sigar 5 na ɗakin karatu ya zama babu shi. Yana da tsada ga mai rarrabawa ya ja tsoffin ɗakunan karatu zuwa cikin sabon sigar rarrabawa. Bayan wani lokaci, matsalar ta sake maimaita kanta a cikin rarraba SUSE.
A sakamakon haka, wasu rarrabawa dole ne su daina dogaro da kai lanƙwasa-libs, da kuma gyara samfurin don ya iya aiki da kowane nau'i na ɗakin karatu.
Af, a cikin sigar 8 na Red Hat babu sauran fakitin meta python, wanda ke nufin tsohon mai kyau Python 2.7. Akwai Python2 и python3.
Madadin masu sarrafa fakiti
Matsalar dogara ta tsufa kuma ta daɗe a bayyane. Kawai tuna Dependency jahannama.
Don haɗa ɗakunan karatu daban-daban da aikace-aikace ta yadda duk su yi aiki da ƙarfi kuma ba sa rikici - a zahiri, wannan shine aikin da kowane mai rarraba Linux ke ƙoƙarin warwarewa.
Manajan kunshin yana ƙoƙarin magance wannan matsala ta wata hanya ta daban. Cirewa daga Canonical. Babban ra'ayi: aikace-aikacen yana gudana a cikin akwatin yashi wanda aka keɓe kuma an kare shi daga babban tsarin. Idan aikace-aikacen yana buƙatar ɗakunan karatu, ana kawo su tare da aikace-aikacen kanta.
Flatpak Hakanan yana ba ku damar gudanar da aikace-aikace a cikin akwatin yashi ta amfani da kwantena na Linux. Hakanan ana amfani da ra'ayin sandbox AppImage.
Waɗannan mafita suna ba ku damar ƙirƙirar fakiti ɗaya don kowane rarraba. Idan akwai Flatpak shigarwa da ƙaddamar da aikace-aikacen yana yiwuwa koda ba tare da sanin mai gudanarwa ba.
Babban matsalar ita ce, ba duk aikace-aikacen ba ne ke iya aiki a cikin akwatin yashi. Wasu mutane suna buƙatar shiga kai tsaye zuwa dandalin. Ba na ma magana game da na'urorin kwaya, waɗanda ke dogara sosai kan kwaya kuma ba su dace da ra'ayin sandbox ba.
Matsala ta biyu ita ce rarraba sananne a cikin mahallin kasuwanci daga Red Hat da SUSE har yanzu ba su ƙunshi tallafi ga Snappy da Flatpak ba.
Dangane da wannan, Wakilin Veeam na Linux baya samuwa ba akan .
Don kammala tambaya game da manajan fakiti, Ina so in lura cewa akwai zaɓi don watsar da manajan fakiti gaba ɗaya ta hanyar haɗa fayilolin binary da rubutun don shigar da su cikin fakiti ɗaya.
Irin wannan nau'in yana ba ku damar ƙirƙirar kunshin gama gari guda ɗaya don rarrabawa da dandamali daban-daban, aiwatar da tsarin shigarwa mai ma'amala, aiwatar da gyare-gyaren da ake buƙata. Na ci karo da irin waɗannan fakitin kawai don Linux daga VMware.
Ɗaukaka matsala
Ko da an warware duk abubuwan dogaro, shirin na iya gudana daban-daban akan rarraba iri ɗaya. Magana ce ta sabuntawa.
Akwai dabarun sabuntawa guda 3:
- Mafi sauƙaƙa shine kada a taɓa sabuntawa. Na saita uwar garken na manta da shi. Me yasa sabuntawa idan komai yayi aiki? Matsaloli suna farawa da farko lokacin da kuka tuntuɓar tallafi. Mahaliccin rarraba yana goyan bayan sabunta sabuntawa kawai.
- Kuna iya amincewa da mai rarrabawa kuma saita sabuntawa ta atomatik. A wannan yanayin, ƙila kiran goyan baya yana yiwuwa nan da nan bayan sabuntawar da bai yi nasara ba.
- Zaɓin sabunta aikin hannu kawai bayan gudanar da shi akan kayan aikin gwaji shine mafi abin dogaro, amma tsada da ɗaukar lokaci. Ba kowa ne ke iya ba.
Tun da masu amfani daban-daban suna amfani da dabarun sabuntawa daban-daban, ya zama dole a goyi bayan sabon saki da duk waɗanda aka saki a baya. Wannan yana rikitar da tsarin haɓakawa da gwajin gwaji kuma yana ƙara ciwon kai ga ƙungiyar tallafi.
Daban-daban na dandamali na hardware
Daban-daban dandamali na hardware matsala ce wacce ta keɓance musamman ga lambar asali. Aƙalla, dole ne ku tattara binaries don kowane dandamali mai goyan baya.
A cikin Wakilin Veeam don aikin Linux, har yanzu ba za mu iya tallafawa wani abu kamar wannan RISC ba.
Ba zan tsaya a kan wannan batu dalla-dalla ba. Zan fayyace manyan matsalolin kawai: nau'ikan dogaro da dandamali, kamar size_t, tsarin daidaitawa da odar byte.
A tsaye da/ko haɗin kai mai ƙarfi
Amma tambayar ita ce "Yadda za a haɗa tare da ɗakunan karatu - a zahiri ko a tsaye?" cancanci tattaunawa.
A matsayinka na mai mulki, aikace-aikacen C/C++ a ƙarƙashin Linux suna amfani da haɗin kai mai ƙarfi. Wannan yana aiki mai girma idan an gina aikace-aikacen musamman don takamaiman rarrabawa.
Idan aikin shine ya rufe rarrabawa daban-daban tare da fayil ɗin binary guda ɗaya, to dole ne ku mai da hankali kan rarraba tallafi mafi tsufa. A gare mu, wannan shine Red Hat 6. Ya ƙunshi gcc 4.4, wanda ko ma'aunin C ++ 11 ba ya goyan bayan .
Muna gina aikin mu ta amfani da gcc 6.3, wanda ke goyan bayan C++14 cikakke. A zahiri, a wannan yanayin, akan Red Hat 6 dole ne ku ɗauki libstdc++ kuma ku haɓaka ɗakunan karatu tare da ku. Hanya mafi sauƙi ita ce haɗi zuwa gare su a tsaye.
Amma kash, ba duk ɗakunan karatu ba ne za a iya haɗa su a tsaye.
Na farko, dakunan karatu na tsarin kamar libfus, liblkid wajibi ne a haɗa kai tsaye don tabbatar da dacewarsu tare da kernel da kayayyaki.
Na biyu, akwai wayo tare da lasisi.
Ainihin lasisin GPL yana ba ku damar haɗa ɗakunan karatu kawai tare da lambar buɗewa. MIT da BSD suna ba da damar haɗin kai tsaye kuma suna ba da damar haɗa ɗakunan karatu cikin aikin. Amma LGPL ba ya kama da ya saba wa haɗin kai tsaye, amma yana buƙatar a raba fayilolin da suka dace don haɗawa.
Gabaɗaya, yin amfani da haɗin kai mai ƙarfi zai hana ku samar da komai.
Aikace-aikacen Gina C/C++
Don gina aikace-aikacen C / C ++ don dandamali daban-daban da rarrabawa, ya isa ya zaɓi ko gina sigar da ta dace ta gcc da amfani da masu tara giciye don ƙayyadaddun gine-ginen gine-gine da tara duk ɗakunan karatu. Wannan aikin yana da yuwuwa, amma yana da wahala sosai. Kuma babu tabbacin cewa zaɓaɓɓen mai tarawa da ɗakunan karatu za su samar da sigar da za ta iya aiki.
Wani fa'ida a bayyane: kayan aikin an sauƙaƙe su sosai, tunda ana iya kammala aikin ginin gaba ɗaya akan na'ura ɗaya. Bugu da ƙari, ya isa ya tattara saitin binaries guda ɗaya don gine-gine ɗaya kuma zaka iya haɗa su cikin fakiti don rarrabawa daban-daban. Wannan shine yadda ake gina fakitin veeam don Wakilin Veeam don Linux.
Sabanin wannan zaɓi, zaku iya shirya gonakin gini kawai, wato, injuna da yawa don haɗuwa. Kowane irin wannan injin zai samar da tarin aikace-aikacen da haɗakar kunshin don takamaiman rarrabawa da takamaiman gine-gine. A wannan yanayin, ana yin tari ta amfani da hanyoyin da mai rarraba ya shirya. Wato an kawar da matakin shirya mai tarawa da zabar dakunan karatu. Bugu da ƙari, tsarin ginawa zai iya zama sauƙin daidaitawa.
Akwai, duk da haka, rashin daidaituwa ga wannan tsarin: ga kowane rarraba a cikin gine-gine iri ɗaya, dole ne ku tattara fayilolin binary na ku. Wani hasara kuma shi ne cewa irin wannan adadi mai yawa na inji yana buƙatar kiyayewa kuma dole ne a ware babban adadin sarari da RAM.
Wannan shine yadda ake tattara fakitin KMOD na veeamsnap kernel module don rarraba Red Hat.
Bude Sabis na Gina
Abokan aiki daga SUSE sun yi ƙoƙarin aiwatar da wasu tsaka-tsaki ta hanyar sabis na musamman don tattara aikace-aikace da harhada fakiti - .
Ainihin, hypervisor ne wanda ke ƙirƙirar injin kama-da-wane, yana shigar da duk fakitin da ake buƙata a ciki, ya haɗa aikace-aikacen kuma ya gina fakitin a cikin wannan keɓewar muhalli, bayan haka ana fitar da injin kama-da-wane.
Mai tsara jadawalin da aka aiwatar a cikin OpenBuildService zai ƙayyade injunan kama-da-wane da yawa da zai iya ƙaddamar don ingantaccen saurin ginin kunshin. Ginin tsarin sa hannu zai sanya hannu kan fakitin kuma a loda su zuwa ma'ajiyar da aka gina a ciki. Tsarin sarrafa sigar da aka gina a ciki zai adana tarihin canje-canje da ginawa. Abin da ya rage shine kawai ƙara tushen ku zuwa wannan tsarin. Ba lallai ne ku kafa uwar garken da kanku ba; kuna iya amfani da buɗaɗɗen.
Akwai, duk da haka, matsala: irin wannan mai girbi yana da wuyar shiga cikin abubuwan da ake da su. Misali, ba a buƙatar sarrafa sigar; mun riga mun sami namu don lambobin tushe. Hanyar sa hannun mu ta bambanta: muna amfani da sabar ta musamman. Hakanan ba a buƙatar ma'ajiyar ajiya.
Bugu da ƙari, goyon baya ga sauran rabawa - alal misali, Red Hat - an aiwatar da shi sosai mara kyau, wanda yake da fahimta.
Amfanin irin wannan sabis ɗin shine tallafi mai sauri don sigar gaba ta rarraba SUSE. Kafin sanarwar sakin a hukumance, ana buga fakitin da ake buƙata don taro akan ma'ajiyar jama'a. Wani sabo yana bayyana a cikin jerin samuwan rabawa akan OpenBuildService. Muna duba akwatin kuma an ƙara shi zuwa tsarin ginin. Don haka, ƙara sabon sigar rarraba ana yin shi a kusan dannawa ɗaya.
A cikin kayan aikin mu, ta amfani da OpenBuildService, duk nau'ikan fakitin KMP na veeamsnap kernel module don rarraba SUSE an tattara su.
Na gaba, Ina so in dakata kan batutuwan da suka shafi kernel modules.
kernel ABI
An rarraba nau'ikan kernel na Linux a tarihi a cikin sigar tushe. Gaskiyar ita ce, masu ƙirƙirar kwaya ba sa ɗaukar kansu da damuwa na tallafawa ingantaccen API don samfuran kwaya, kuma musamman a matakin binary, wanda ake kira kABI.
Don gina samfuri don kwaya na vanilla, tabbas kuna buƙatar kanun wannan kwaya ta musamman, kuma zai yi aiki akan wannan kwaya kawai.
DKMS yana ba ku damar sarrafa tsarin tsarin gini yayin sabunta kwaya. Sakamakon haka, masu amfani da ma'ajin Debian (da danginsa da yawa) suna amfani da kernel modules ko dai daga ma'ajiyar mai rabawa ko kuma an haɗa su daga tushe ta amfani da DKMS.
Koyaya, wannan yanayin bai dace da sashin Kasuwanci ba musamman. Masu rarraba lambar mallakar mallaka suna son rarraba samfurin azaman binaries da aka haɗa.
Masu gudanarwa ba sa son kiyaye kayan aikin haɓakawa akan sabar samarwa saboda dalilai na tsaro. Masu rarraba Linux na kasuwanci irin su Red Hat da SUSE sun yanke shawarar cewa za su iya tallafawa tsayayyen kABI ga masu amfani da su. Sakamakon shine fakitin KMOD don fakitin Red Hat da KMP don SUSE.
Ma'anar wannan bayani yana da sauƙi. Don takamaiman sigar rarrabawa, API ɗin kwaya ya daskare. Mai rarrabawa ya bayyana cewa yana amfani da kwaya, misali, 3.10, kuma yana yin gyare-gyare da gyare-gyare kawai waɗanda ba su shafi mu'amalar kwaya ba, kuma za'a iya amfani da na'urorin da aka tattara don kernel na farko ga duk masu zuwa ba tare da sakewa ba.
Red Hat yana da'awar dacewar kABI don rarrabawa a duk tsawon rayuwar sa. Wato, tsarin da aka haɗa don rhel 6.0 (sakin Nuwamba 2010) shima yakamata yayi aiki akan sigar 6.10 (saki Yuni 2018). Kuma wannan kusan shekaru 8 kenan. A zahiri, wannan aiki yana da wuyar gaske.
Mun yi rikodin lokuta da yawa inda tsarin veeamsnap ya daina aiki saboda matsalolin daidaitawar kABI.
Bayan samfurin veeamsnap, wanda aka harhada don RHEL 7.0, ya zama wanda bai dace da kernel daga RHEL 7.5 ba, amma an ɗora shi kuma an ba da tabbacin rushe uwar garken, mun watsar da amfani da daidaituwar kABI don RHEL 7 gaba ɗaya.
A halin yanzu, kunshin KMOD na RHEL 7 ya ƙunshi taro don kowane sigar saki da rubutun da ke loda tsarin.
SUSE ya kusanci aikin daidaitawar kABI a hankali. Suna ba da daidaituwar kABI a cikin fakitin sabis ɗaya kawai.
Misali, sakin SLES 12 ya faru a watan Satumba na 2014. Kuma SLES 12 SP1 ya riga ya kasance a cikin Disamba 2015, wato, ɗan fiye da shekara guda ya wuce. Duk da cewa duka abubuwan da aka saki suna amfani da kernel 3.12, ba su dace da kABI ba. Babu shakka, kiyaye daidaiton kABI na shekara guda ya fi sauƙi. Zagayowar sabuntawar kernel na shekara-shekara bai kamata ya haifar da matsala ga masu ƙirƙira module ba.
Sakamakon wannan manufar SUSE, ba mu rubuta matsala ko ɗaya ba tare da daidaitawar kABI a cikin tsarin mu na veeamsnap. Gaskiya ne, adadin fakitin SUSE kusan tsari ne na girma mafi girma.
Faci da baya
Kodayake masu rarraba suna ƙoƙarin tabbatar da daidaiton kABI da daidaiton kwaya, suna kuma ƙoƙarin inganta aikin da kawar da lahani na wannan tsayayyen kwaya.
A lokaci guda, ban da nasu "aiki akan kurakurai," masu haɓaka kernel na Linux suna lura da canje-canje a cikin kwaya na vanilla kuma suna tura su zuwa "kwanciyar hankali".
Wani lokaci wannan yana kaiwa ga sababbi .
A cikin sabon sakin Red Hat 6, an yi kuskure a ɗayan ƙaramin sabuntawa. Ya kai ga gaskiyar cewa samfurin veeamsnap ya sami tabbacin rushe tsarin lokacin da aka fitar da hoton. Bayan kwatanta tushen kernel kafin da bayan sabuntawa, mun gano cewa laifin baya ne. An yi irin wannan gyara a cikin sigar kernel ta vanilla 4.19. Kawai wannan gyaran ya yi aiki mai kyau a cikin kwaya na vanilla, amma lokacin canja wurin shi zuwa "barga" 2.6.32, matsala ta taso tare da spinlock.
Tabbas, kowa da kowa yana da kurakurai, amma shin ya cancanci jan lambar daga 4.19 zuwa 2.6.32, yana haɗarin kwanciyar hankali?... Ban tabbata ba ...
Mafi munin abu shine lokacin da tallace-tallace ya shiga cikin rikici tsakanin "kwanciyar hankali" da "zamani." Sashen tallan tallace-tallace yana buƙatar ainihin rarrabawar da aka sabunta don zama tsayayye, a gefe guda, kuma a lokaci guda ya zama mafi kyau a cikin aiki kuma yana da sababbin siffofi. Wannan yana haifar da rashin daidaituwa.
Lokacin da na yi ƙoƙarin gina module akan kernel 4.4 daga SLES 12 SP3, Na yi mamakin samun aiki daga vanilla 4.8 a ciki. A ganina, toshe I/O aiwatar da 4.4 kwaya daga SLES 12 SP3 ya fi kama da kwaya ta 4.8 fiye da sakin da ya gabata na barga kernel 4.4 daga SLES12 SP2. Ba zan iya yin hukunci da adadin adadin lambar da aka canjawa wuri daga kernel 4.8 zuwa SLES 4.4 don SP3 ba, amma ba zan iya kiran kernel daidai 4.4 ba.
Abu mafi ban sha'awa game da wannan shine lokacin rubuta tsarin da zai yi aiki daidai da kernels daban-daban, ba za ku iya dogaro da sigar kernel ba. Hakanan dole ne kuyi la'akari da rarrabawa. Yana da kyau cewa wani lokacin za ku iya shiga cikin ma'anar da ke bayyana tare da sababbin ayyuka, amma wannan damar ba koyaushe take bayyana ba.
Sakamakon haka, lambar ta zama ta cika girma tare da ƙa'idodi masu ban mamaki.
Hakanan akwai faci waɗanda ke canza bayanan kwaya API.
Na ci karo da rabon 5.16 kuma yayi mamakin ganin cewa lookup_bdev kira a cikin wannan sigar kernel ya canza jerin sigogin shigarwa.
Don haɗa shi, dole ne in ƙara rubutu a cikin makefile wanda ke bincika ko aikin lookup_bdev yana da ma'aunin abin rufe fuska.
Sa hannun kernel modules
Amma bari mu koma kan batun rarraba kunshin.
Ɗaya daga cikin fa'idodin tsayayyen kABI shine cewa za'a iya sanya hannu kan samfuran kernel azaman fayil na binary. A wannan yanayin, mai haɓakawa zai iya tabbata cewa ƙirar ba ta lalace ba da gangan ko kuma da gangan aka gyara ta. Kuna iya bincika wannan tare da umarnin modinfo.
Rarraba Red Hat da SUSE suna ba ku damar duba sa hannun module ɗin kuma ku loda shi kawai idan takardar shaidar da ta dace ta yi rajista akan tsarin. Takaddun shaida shine maɓalli na jama'a wanda aka sanya hannu akan tsarin da shi. Muna rarraba shi azaman kunshin daban.
Matsalar anan ita ce ana iya gina takaddun shaida a cikin kwaya (masu rarrabawa suna amfani da su) ko kuma dole ne a rubuta su zuwa EFI mara maras ƙarfi ta amfani da kayan aiki. mokutil. Amfani mokutil Lokacin shigar da takaddun shaida, yana buƙatar ka sake yin tsarin kuma, tun kafin loda kernel ɗin tsarin aiki, ya sa mai gudanarwa ya ba da izinin loda sabon takaddun shaida.
Don haka, ƙara takaddun shaida yana buƙatar samun dama ga mai gudanarwa na zahiri zuwa tsarin. Idan na'urar tana cikin wani wuri a cikin gajimare ko kuma kawai a cikin ɗakin uwar garken nesa kuma samun damar ta hanyar hanyar sadarwa ne kawai (alal misali, ta ssh), to ba zai yuwu a ƙara takaddun shaida ba.
EFI akan injunan kama-da-wane
Duk da cewa EFI ya daɗe yana goyon bayan kusan dukkanin masana'antun motherboard, lokacin shigar da tsarin, mai gudanarwa bazai yi tunani game da buƙatar EFI ba, kuma yana iya zama nakasa.
Ba duk masu haɓakawa suna goyan bayan EFI ba. VMWare vSphere yana goyan bayan EFI farawa daga sigar 5.
Microsoft Hyper-V kuma ya sami tallafin EFI farawa da Hyper-V don Windows Server 2012R2.
Koyaya, a cikin tsohowar saitin wannan aikin yana kashe don injunan Linux, wanda ke nufin ba za a iya shigar da takardar shaidar ba.
A cikin vSphere 6.5, saita zaɓi Kati mai tsabta mai yuwuwa ne kawai a cikin tsohuwar sigar gidan yanar gizo, wacce ke gudana ta Flash. Yanar gizo UI akan HTML-5 har yanzu yana baya.
Rarraba gwaji
Kuma a ƙarshe, bari mu yi la'akari da batun rarraba gwaji da rarrabawa ba tare da tallafin hukuma ba. A gefe guda, irin wannan rarraba ba zai yiwu a samu a kan sabar na kungiyoyi masu tsanani ba. Babu wani tallafi na hukuma don irin wannan rabon. Saboda haka, samar da wadanda. Ba za a iya tallafawa samfurin akan irin wannan rarraba ba.
Duk da haka, irin wannan rarraba ya zama dandamali mai dacewa don gwada sababbin hanyoyin gwaji. Misali, Fedora, OpenSUSE Tumbleweed ko Unstable versions na Debian. Suna da kwanciyar hankali. Kullum suna da sabbin nau'ikan shirye-shirye kuma koyaushe sabon kwaya. A cikin shekara guda, wannan aikin gwaji na iya ƙarewa a cikin RHEL, SLES ko Ubuntu da aka sabunta.
Don haka idan wani abu ba ya aiki akan rarraba gwaji, wannan shine dalilin da za a gano matsalar da magance shi. Kuna buƙatar yin shiri don gaskiyar cewa nan ba da jimawa ba wannan aikin zai bayyana akan sabar samar da masu amfani.
Kuna iya nazarin jerin abubuwan da ake tallafawa a hukumance don sigar 3.0 . Amma ainihin jerin rarrabawa wanda samfurinmu zai iya aiki ya fi fadi.
Da kaina, Ina sha'awar gwaji tare da Elbrus OS. Bayan kammala kunshin veeam, an shigar da samfurin mu yana aiki. Na rubuta game da wannan gwaji akan Habré in .
To, ana ci gaba da tallafawa sabbin rabawa. Muna jiran fitowar sigar 4.0. Beta na gab da bayyana, don haka a sa ido !
source: www.habr.com