Sam Hartman, Jagoran Ayyukan Debian, don fahimtar bambance-bambancen da ke tattare da bayarwa na kunshin elogind a matsayin ɓangare na rarrabawa. A watan Yuli, ƙungiyar da ke da alhakin shirya abubuwan fitarwa hada elogind a cikin reshen gwaji, tunda wannan kunshin ya ci karo da libsystemd.
Ka tuna cewa yana ba da hanyoyin haɗin gwiwar da ake buƙata don gudanar da GNOME ba tare da shigar da tsarin ba. An kafa aikin a matsayin cokali mai yatsa na systemd-logind, an sanya shi a cikin wani fakitin daban kuma an 'yantar da shi daga ɗaure zuwa abubuwan da aka tsara. Daga cikin wasu abubuwa, elogind yana samar da nasa nau'in ɗakin karatu na libelogind, wanda ke ɗaukar ayyuka da yawa da aka bayar a cikin libsystemd kuma ya maye gurbin wannan ɗakin karatu yayin shigarwa.
Dalilan toshewa shine rikici tare da kunshin tsarin da kuma haɗarin maye gurbin tsarin libsystemd tare da madadin liberind, wanda bai dace da ainihin ɗakin karatu a matakin ABI ba.
Kunshin yana ba da alamar elogind azaman cin karo da ɗakunan karatu na tsarin, amma an tsara shi ta asali don yin aiki kawai ba tare da tsarin ba, kuma cin karo da systemd yana da fa'ida a zahiri saboda yana hana elogind shigar da kuskure. A gefe guda, a cikin nau'in sa na yanzu, ƙoƙarin ta hanyar APT don sabunta tsarin daga systemd zuwa sigar tare da sysvinit da sakamakon elogind a ciki. tare da APT ba ya aiki. Amma ko da an kawar da wannan gazawar, canji daga tsarin zuwa elogind ya kasance ba zai yiwu ba ba tare da share wuraren da aka riga aka shigar ba.
The elogind developers kasance daidaita elogind don yin aiki a saman daidaitaccen tsarin libpam-systemd, ba tare da amfani da nasa Layer libpam-elogind ba. Canjin elogind zuwa libpam-systemd yana fuskantar rashin tallafi ga ra'ayin yanka, amma masu haɓaka elogind ba sa son cimma cikakkiyar yarda da API kuma daidai da maimaita duk damar tsarin tsarin, tunda elogind kawai yana ba da ƙarancin ƙima. ayyuka don tsara shigar masu amfani kuma baya nufin kwafi duk tsarin tsarin.
Ya kamata a warware matsalar matsalolin fasaha da aka kwatanta a matakin hulɗar tsakanin ƙungiyar masu saki da masu tsarawa da masu kula da tsarin, amma an tilasta wa jagoran aikin shiga tsakani saboda ƙungiyoyin ba su yarda ba, aikin haɗin gwiwa ya ci gaba a cikin rikici da kuma warware matsalar. matsala ta kai ga ƙarshe, wanda kowane bangare ya yi daidai a hanyarsa. A cewar Sam Hartman, halin da ake ciki yana gabatowa jihar da ke buƙatar kada kuri'a na gaba ɗaya (GR, ƙuduri na gabaɗaya), inda al'umma za su yanke shawara kan wasu tsare-tsare na init da kuma tallafawa sysvinit tare da kaifin baki.
Idan membobin aikin sun kada kuri'a don bambanta tsarin shigar, duk masu kula za su shiga cikin aiki tare don magance wannan matsala ko kuma za a ba da takamaiman masu haɓakawa don yin aiki a kan wannan batu kuma masu kulawa ba za su iya yin watsi da wani tsarin shigar ba, yin shiru, ko jinkirta tsari.
A halin yanzu a cikin ma'ajiyar riga Fakiti 1033 waɗanda ke ba da sassan sabis don tsarin, amma ba su haɗa da rubutun init.d ba. Don magance wannan matsalar ba da fayilolin sabis ta tsohuwa, amma shirya mai sarrafa wanda zai rarraba umarni ta atomatik daga waɗannan fayilolin kuma ya samar da rubutun init.d bisa su.
Idan al'umma sun yanke shawarar cewa Debian yana da isasshen tallafi don tsarin init guda ɗaya, ba za mu iya ƙara damuwa game da sysvinit da elogind ba kuma mu mai da hankali kawai ga fayilolin naúrar da tsarin. Wannan shawarar za ta yi mummunan tasiri ga tashoshin jiragen ruwa waɗanda ba sa amfani da kernel Linux (, и ), amma babu irin waɗannan tashoshin jiragen ruwa a cikin babban tarihin har yanzu kuma ba su da matsayi .
Daure ga systemd kuma zai sa ya zama da wahala a canza hanyar rarrabawa a nan gaba kuma zai iyakance ƙarin gwaji a fagen farawa da sarrafa sabis. Kula da elogind a cikin sigar aiki ya fi sauƙi fiye da share shi sannan ƙoƙarin ƙarawa kuma. Kowane zaɓi na yanke shawara yana da ribobi da fursunoni, don haka za a buƙaci cikakken tattaunawa game da duk wata fa'ida da rashin amfani kafin jefa ƙuri'a.
source: budenet.ru