From 1be510f9529cb082f802408b472a77d074b394c0 Mon Sep 17 00:00:00 2001 From: Nicolas Vigier Date: Sun, 14 Apr 2013 13:46:12 +0000 Subject: Add zarb MLs html archives --- zarb-ml/mageia-dev/2012-January/011506.html | 111 ++++++++++++++++++++++++++++ 1 file changed, 111 insertions(+) create mode 100644 zarb-ml/mageia-dev/2012-January/011506.html (limited to 'zarb-ml/mageia-dev/2012-January/011506.html') diff --git a/zarb-ml/mageia-dev/2012-January/011506.html b/zarb-ml/mageia-dev/2012-January/011506.html new file mode 100644 index 000000000..2412da735 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-January/011506.html @@ -0,0 +1,111 @@ + + + + [Mageia-dev] ConsoleKit vs systemd session tracking for Mageia 2 + + + + + + + + + +

[Mageia-dev] ConsoleKit vs systemd session tracking for Mageia 2

+ Michael Scherer + misc at zarb.org +
+ Mon Jan 23 16:12:17 CET 2012 +

+
+ +
Le lundi 23 janvier 2012 à 15:51 +0100, Olav Vitters a écrit :
+> FYI,
+
+> These seem to be compile time checks. Meaning: if --enable-systemd is
+> added to ./configure, the functionality won't work on sysvinit. I am not
+> sure exactly what will break under sysvinit. The bugreports to contain
+> some discussion though.
+> 
+> 
+> Could a systemd expert look into this and suggest what is best for
+> Mageia 2?
+
+Since we decided to keep non systemd boot as fully supported for mageia
+2 : https://www.mageia.org/pipermail/mageia-dev/2011-July/006532.html
+
+and to have both usable side by side : 
+https://bugs.mageia.org/show_bug.cgi?id=2120
+
+I guess it is best to keep the old system for the time being.
+So do not use --enable-systemd until mageia 3.
+
+-- 
+Michael Scherer
+
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ -- cgit v1.2.1