| Summary: | System V style init programs 2.88 | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Anderson Carvalho <frateraec> |
| Component: | New RPM package request | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | mageia |
| Version: | 2 | ||
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | CVE: | ||
| Status comment: | |||
|
Description
Anderson Carvalho
2012-07-25 01:11:53 CEST
This is not bugfixes only version. Changelog is quite long and they change functionality as well. I don't see how we can update such an important part of stable Mageia. So i will mark it as won't fix. Status:
NEW =>
RESOLVED So I have to make a new RPM package request to the cauldron? I had to uninstall systemd and install sysvinit-legacy, because systemd has several small bugs that do not want to have to be resolving on the nail. Now that I went back to sysvinit-legacy everything works on drakxservice and I can configure the services that will go up on boot. Systemd may be mature and integrated in Mageia 3 or maybe Mageia 4, per hour is a solution still immature. What you can do is report bugs against systemd. There is no big point to request another init on cauldron as sysvinit is now obsolete and removed from cauldron. For Mageia 3 there will be only systemd. So you better find and report bugs. Many major distributions are using it and it won't go away.. I already reportei 2: This: https://bugs.mageia.org/show_bug.cgi?id=6842 and This: https://bugs.mageia.org/show_bug.cgi?id=6843 There are 7 more, just search. Fedora no worries about home user, just a novelty testing for distro Red Hat, Mandriva now follows this terrible trend. Novelty that feel good, without worrying about users. If the community Mageia is facing community because following this terrible trend? |