Bug 2120 - [Tracker] Implement systemd in Mageia 2 - specifications
: [Tracker] Implement systemd in Mageia 2 - specifications
Status: RESOLVED FIXED
Product: Mageia
Classification: Unclassified
Component: RPM Packages
: Cauldron
: All Linux
: release_blocker Severity: critical
: Mageia 2
Assigned To: D Morgan
:
: https://bugs.mageia.org/buglist.cgi?c...
: QA
:
: 2246 2504 2521 2698 2703 2760 2767 2803 2804 2865 2983 2998 3068 3069 3074 3106 3129 3188 3220 3221 3223 3227 3251 3253 3386 3430 3512 3551 3577 3578 3581 3647 3648 3649 3658 3717 3719 3740 3744 3784 3800 3812 3817 3823 4003 4052 4131 4133 4166 4172 4186 4187 4198 4199 4205 4213 4233 4328 4339 4353 4475 4500 4504 4509 4510 4528 4541 4552 4557 4582 4588 4605 4672 4688 4744 4763 4772 4846 4863 4875 4892 4910 5122 5143 5148 5159 5184 5262 5381 5594
: 1994 3402 3656 3960
  Show dependency treegraph
 
Reported: 2011-07-12 14:05 CEST by Anne Nicolas
Modified: 2012-05-17 16:14 CEST (History)
10 users (show)

See Also:
Source RPM: systemd
CVE:
Status comment:


Attachments

Description Anne Nicolas 2011-07-12 14:05:56 CEST
Systemd is part of proposals for technical specifications fr Mageia2.

This bug is about question of its integration in cauldron and the way to do it
- make it smoothly: have both in parallel while it's not all integrated
- tests, QA, services modifications...
Comment 1 Chris Denice 2011-07-13 13:36:31 CEST
Hi guys, I read we can shout here so:

1) first thing to say from userland: motivations?

I hope systemd is no like another useless fashion program such as haldaemon and really brings an added value concerning usage of mga; or at least it's devel. Nobody seems to discuss this, maybe it is obvious?

2) On mandriva however, it deeply sucked. My own experience was that a lot of not-so-standard stuff were broken (like multi soundcards, modprobe config files no longer read and so on...) and nothing really cool happened on the user's side. So if this is going to happen on mga, it should not happen like this has been done on mdv.

3) Strongly against having both since it decreases the number of testers that would be forced to use systemd otherwise, and this will decrease our ability to debug it. Again, from the mdv move, I would even say that fixing issues in one may induce bugs in the other.

cheers,
chris.
Comment 2 Christiaan Welvaart 2011-07-22 00:33:23 CEST
(In reply to comment #1)

ad 1: systemd allows fast booting and shutdown, and cleaner shutdown. Dependencies between startup tasks can be evaluated cleanly (systemd simply makes the task that depends on something else wait, instead of systemd waiting itself and then notifying the task). I think it also provides powerful analysis tools, logging is more robust, etc.

ad 2: I hope someone can list these problems (in a bit more detail) and we should verify and if necessary solve each one.

ad 3: IMHO we should not try to support the old init system even though it will likely still be provided in mga2. If people have problems with it the advice should be to switch to systemd.


And one question of my own:

Is systemd supposed to be used for new installs only or also for upgrades? In other words, are we going to "force" people to switch from old-style init/scripts to systemd + a few old scripts?
Comment 3 Samuel Verschelde 2011-10-01 03:10:06 CEST
Assigning to maintainer now that our maintainers database has an entry for
this package. Please assign back to bugsquad@mageia.org in case of a mistake
from me.
Comment 4 Manuel Hiebel 2011-10-22 21:10:44 CEST
We don't know who really work on systemd so please look at depends bug. Thanks
Comment 5 D Morgan 2011-10-22 23:14:36 CEST
coling and I, are for now the more working on systemd but everybody can come to help :)
Comment 6 Thierry Vignaud 2011-12-07 11:10:04 CET
Adding a named query for systemd bugs (might be easier to manage systemd related issues)
Comment 7 Manuel Hiebel 2012-01-05 19:08:25 CET
General ping for Alpha 3
Comment 8 Colin Guthrie 2012-05-17 16:14:32 CEST
All bugs now fixed! \o/

Note You need to log in before you can comment on or make changes to this bug.