[systemd-devel] [PATCH 1/2] timedated: gather timezone from /etc/localtime sym target
/etc/localtime - /usr/share/zoneinfo/...
or
/etc/localtime - ../usr/share/zoneinfo/...
(note, ../usr is not the same if /etc is a symlink, as this isn't
using canonicalize_file_name())
keep other method for now, consider dropping later.
Supporting relative links here are problematic as timezones in
/usr/share/zoneinfo are often themselves symlinks (and symlinks to
symlinks), so this implamentation only supports absolute symlinks
/usr/share/zoneinfo/ and relative symlinks starting with
../usr/share/zoneinfo/
From TODO (kay sievers):
* kill /etc/timezone handling entirely? What does it provide?
- /etc/localtime carries the same information already:
$ ls -l /etc/localtime; cat /etc/timezone
lrwxrwxrwx 1 root root 33 Jul 27 09:55 /etc/localtime -
/usr/share/zoneinfo/Europe/Berlin
Europe/Berlin
- systemd enforces /usr to be available at bootup, so we can
enforce the use of the symlink
---
src/timedate/timedated.c | 52 +-
1 file changed, 42 insertions(+), 10 deletions(-)
diff --git a/src/timedate/timedated.c b/src/timedate/timedated.c
index 09fd808..b11acae 100644
--- a/src/timedate/timedated.c
+++ b/src/timedate/timedated.c
@@ -74,6 +74,9 @@
BUS_GENERIC_INTERFACES_LIST \
org.freedesktop.timedate1\0
+/* Must start and end with '/' */
+#define ZONEINFO_PATH /usr/share/zoneinfo/
+
const char timedate_interface[] _introspect_(timedate1) = INTERFACE;
typedef struct TZ {
@@ -127,7 +130,7 @@ static bool valid_timezone(const char *name) {
if (slash)
return false;
-t = strappend(/usr/share/zoneinfo/, name);
+t = strappend(ZONEINFO_PATH, name);
if (!t)
return false;
@@ -151,17 +154,17 @@ static void verify_timezone(void) {
if (!tz.zone)
return;
-p = strappend(/usr/share/zoneinfo/, tz.zone);
+p = strappend(ZONEINFO_PATH, tz.zone);
if (!p) {
log_oom();
return;
}
-j = read_full_file(/etc/localtime, a, l);
k = read_full_file(p, b, q);
-
free(p);
+j = read_full_file(/etc/localtime, a, l);
+
if (j 0 || k 0 || l != q || memcmp(a, b, l)) {
log_warning(/etc/localtime and /etc/timezone out of sync.);
free(tz.zone);
@@ -174,9 +177,34 @@ static void verify_timezone(void) {
static int read_data(void) {
int r;
+char *t = NULL;
free_data();
+r = readlink_malloc(/etc/localtime, t);
+if (r 0) {
+if (r == -EINVAL)
+log_warning(/etc/localtime should be a symbolic link
to a timezone data file in ZONEINFO_PATH);
+else
+log_warning(Failed to get target of %s: %s,
/etc/localtime, strerror(-r));
+} else {
+/* we only support the trivial relative link of
(/etc/)..$ABSOLUTE */
+int rel_link_offset = startswith(t, ..) ? strlen(..) : 0;
+
+if (!startswith(t + rel_link_offset, ZONEINFO_PATH))
+log_warning(/etc/localtime should be a symbolic link
to a timezone data file in ZONEINFO_PATH);
+else {
+tz.zone = strdup(t + rel_link_offset +
strlen(ZONEINFO_PATH));
+free(t);
+if (!tz.zone)
+return log_oom();
+
+goto have_timezone;
+}
+}
+
+free(t);
+
r = read_one_line_file(/etc/timezone, tz.zone);
if (r 0) {
if (r != -ENOENT)
@@ -192,6 +220,7 @@ static int read_data(void) {
#endif
}
+have_timezone:
if (isempty(tz.zone)) {
free(tz.zone);
tz.zone = NULL;
@@ -207,6 +236,7 @@ static int read_data(void) {
static int write_data_timezone(void) {
int r = 0;
char *p;
+struct stat st;
if (!tz.zone) {
if (unlink(/etc/timezone) 0 errno != ENOENT)
@@ -218,19 +248,21 @@ static int write_data_timezone(void) {
return r;
}
-p = strappend(/usr/share/zoneinfo/, tz.zone);
+p = strappend(ZONEINFO_PATH, tz.zone);
if (!p)
return log_oom();
-r = symlink_or_copy_atomic(p, /etc/localtime);
+r = symlink(p, /etc/localtime);
free(p);
if (r 0)
-return r;
+return -errno;
-r = write_one_line_file_atomic(/etc/timezone, tz.zone);
-if (r 0)
-return r;
+if (stat(/etc/timezone, st) == 0 S_ISREG(st.st_mode)) {
+r = write_one_line_file_atomic(/etc/timezone, tz.zone);
+if (r 0)
+return r;
+}
return 0;
}
--
1.7.9.5
[systemd-devel] [PATCH v9002 1/2] timedated: gather timezone from /etc/localtime sym target
/etc/localtime - /usr/share/zoneinfo/...
or
/etc/localtime - ../usr/share/zoneinfo/...
(note, ../usr is not the same if /etc is a symlink, as this isn't
using canonicalize_file_name())
keep other method for now, consider dropping later.
Supporting relative links here are problematic as timezones in
/usr/share/zoneinfo are often themselves symlinks (and symlinks to
symlinks), so this implamentation only supports absolute symlinks
/usr/share/zoneinfo/ and relative symlinks starting with
../usr/share/zoneinfo/
From TODO (kay sievers):
* kill /etc/timezone handling entirely? What does it provide?
- /etc/localtime carries the same information already:
$ ls -l /etc/localtime; cat /etc/timezone
lrwxrwxrwx 1 root root 33 Jul 27 09:55 /etc/localtime -
/usr/share/zoneinfo/Europe/Berlin
Europe/Berlin
- systemd enforces /usr to be available at bootup, so we can
enforce the use of the symlink
---
src/timedate/timedated.c | 52 +-
1 file changed, 42 insertions(+), 10 deletions(-)
diff --git a/src/timedate/timedated.c b/src/timedate/timedated.c
index 09fd808..b11acae 100644
--- a/src/timedate/timedated.c
+++ b/src/timedate/timedated.c
@@ -74,6 +74,9 @@
BUS_GENERIC_INTERFACES_LIST \
org.freedesktop.timedate1\0
+/* Must start and end with '/' */
+#define ZONEINFO_PATH /usr/share/zoneinfo/
+
const char timedate_interface[] _introspect_(timedate1) = INTERFACE;
typedef struct TZ {
@@ -127,7 +130,7 @@ static bool valid_timezone(const char *name) {
if (slash)
return false;
-t = strappend(/usr/share/zoneinfo/, name);
+t = strappend(ZONEINFO_PATH, name);
if (!t)
return false;
@@ -151,17 +154,17 @@ static void verify_timezone(void) {
if (!tz.zone)
return;
-p = strappend(/usr/share/zoneinfo/, tz.zone);
+p = strappend(ZONEINFO_PATH, tz.zone);
if (!p) {
log_oom();
return;
}
-j = read_full_file(/etc/localtime, a, l);
k = read_full_file(p, b, q);
-
free(p);
+j = read_full_file(/etc/localtime, a, l);
+
if (j 0 || k 0 || l != q || memcmp(a, b, l)) {
log_warning(/etc/localtime and /etc/timezone out of sync.);
free(tz.zone);
@@ -174,9 +177,34 @@ static void verify_timezone(void) {
static int read_data(void) {
int r;
+char *t = NULL;
free_data();
+r = readlink_malloc(/etc/localtime, t);
+if (r 0) {
+if (r == -EINVAL)
+log_warning(/etc/localtime should be a symbolic link
to a timezone data file in ZONEINFO_PATH);
+else
+log_warning(Failed to get target of %s: %s,
/etc/localtime, strerror(-r));
+} else {
+/* we only support the trivial relative link of
(/etc/)..$ABSOLUTE */
+int rel_link_offset = startswith(t, ..) ? strlen(..) : 0;
+
+if (!startswith(t + rel_link_offset, ZONEINFO_PATH))
+log_warning(/etc/localtime should be a symbolic link
to a timezone data file in ZONEINFO_PATH);
+else {
+tz.zone = strdup(t + rel_link_offset +
strlen(ZONEINFO_PATH));
+free(t);
+if (!tz.zone)
+return log_oom();
+
+goto have_timezone;
+}
+}
+
+free(t);
+
r = read_one_line_file(/etc/timezone, tz.zone);
if (r 0) {
if (r != -ENOENT)
@@ -192,6 +220,7 @@ static int read_data(void) {
#endif
}
+have_timezone:
if (isempty(tz.zone)) {
free(tz.zone);
tz.zone = NULL;
@@ -207,6 +236,7 @@ static int read_data(void) {
static int write_data_timezone(void) {
int r = 0;
char *p;
+struct stat st;
if (!tz.zone) {
if (unlink(/etc/timezone) 0 errno != ENOENT)
@@ -218,19 +248,21 @@ static int write_data_timezone(void) {
return r;
}
-p = strappend(/usr/share/zoneinfo/, tz.zone);
+p = strappend(ZONEINFO_PATH, tz.zone);
if (!p)
return log_oom();
-r = symlink_or_copy_atomic(p, /etc/localtime);
+r = symlink(p, /etc/localtime);
free(p);
if (r 0)
-return r;
+return -errno;
-r = write_one_line_file_atomic(/etc/timezone, tz.zone);
-if (r 0)
-return r;
+if (stat(/etc/timezone, st) == 0 S_ISREG(st.st_mode)) {
+r = write_one_line_file_atomic(/etc/timezone, tz.zone);
+if (r 0)
+return r;
+}
return 0;
}
--
1.7.9.5
[systemd-devel] [PATCH v9002 2/2] man: remove timezone(5) and add localtime(5)
--- Makefile.am|2 +- man/localtime.xml | 93 man/timezone.xml | 90 -- units/systemd-timedated.service.in |2 +- 4 files changed, 95 insertions(+), 92 deletions(-) create mode 100644 man/localtime.xml delete mode 100644 man/timezone.xml diff --git a/Makefile.am b/Makefile.am index e6bfc1f..1996956 100644 --- a/Makefile.am +++ b/Makefile.am @@ -468,7 +468,7 @@ MANPAGES = \ man/systemd.conf.5 \ man/tmpfiles.d.5 \ man/hostname.5 \ - man/timezone.5 \ + man/localtime.5 \ man/machine-id.5 \ man/locale.conf.5 \ man/os-release.5 \ diff --git a/man/localtime.xml b/man/localtime.xml new file mode 100644 index 000..09df161 --- /dev/null +++ b/man/localtime.xml @@ -0,0 +1,93 @@ +?xml version='1.0'? !--*-nxml-*-- +?xml-stylesheet type=text/xsl href=http://docbook.sourceforge.net/release/xsl/current/xhtml/docbook.xsl;? +!DOCTYPE refentry PUBLIC -//OASIS//DTD DocBook XML V4.2//EN +http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd; + +!-- + This file is part of systemd. + + Copyright 2010 Lennart Poettering + Copyright 2012 Shawn Landden + + systemd is free software; you can redistribute it and/or modify it + under the terms of the GNU Lesser General Public License as published by + the Free Software Foundation; either version 2.1 of the License, or + (at your option) any later version. + + systemd is distributed in the hope that it will be useful, but + WITHOUT ANY WARRANTY; without even the implied warranty of + MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU + Lesser General Public License for more details. + + You should have received a copy of the GNU Lesser General Public License + along with systemd; If not, see http://www.gnu.org/licenses/. +-- + +refentry id=localtime +refentryinfo +title/etc/localtime/title +productnamesystemd/productname + +authorgroup +author +contribDeveloper/contrib +firstnameLennart/firstname +surnamePoettering/surname +emaillenn...@poettering.net/email +/author +author +contribDeveloper/contrib +firstnameShawn/firstname +surnameLandden/surname +emailshawnland...@gmail.com/email +/author +/authorgroup +/refentryinfo + +refmeta +refentrytitlelocaltime/refentrytitle +manvolnum5/manvolnum +/refmeta + +refnamediv +refnamelocaltime/refname +refpurposeLocal time zone configuration file/refpurpose +/refnamediv + +refsynopsisdiv +parafilename/etc/localtime/filename - filename/usr/share/zoneinfo/…/filename/para +/refsynopsisdiv + +refsect1 +titleDescription/title + +paraThe filename/etc/localtime/filename file +configures the system-wide time zone of the local +system that is used by applications for presentation +to the user. It should be an absolute symbolic link +with a destination of filename/usr/share/zoneinfo//filename, +fallowed by a time zone identifier such as +literalEurope/Berlin/literal or literalEtc/UTC/literal. +The resulting link should point to the corresponding binary + citerefentryrefentrytitletzfile/refentrytitlemanvolnum5/manvolnum/citerefentry +time zone data for the configured time zone./para + +paraAs the time zone identifier is extracted from the name of +the target of filename/etc/localtime/filename this file may +not be a normal file or hardlink./para + +paraThe time zone may be overridden for individual +programs by using the TZ environment variable. See + citerefentryrefentrytitleenviron/refentrytitlemanvolnum7/manvolnum/citerefentry./para +/refsect1 + +refsect1 + titleSee Also/title + para + citerefentryrefentrytitletzset/refentrytitlemanvolnum3/manvolnum/citerefentry + citerefentryrefentrytitlelocaltime/refentrytitlemanvolnum3/manvolnum/citerefentry + citerefentryrefentrytitlesystemd/refentrytitlemanvolnum1/manvolnum/citerefentry + /para +/refsect1 + +/refentry diff --git a/man/timezone.xml b/man/timezone.xml deleted file mode 100644 index
Re: [systemd-devel] systemd hackfest on Developer Conference 2013
Lennart Poettering píše v Út 21. 08. 2012 v 17:15 +0200: On Tue, 14.08.12 17:32, Václav Pavlín (vpav...@redhat.com) wrote: Heya, Either would be fine with me, with a slight preference of before. Ok, so I would suggest to do it before. Another question is, if we should plan it for two days (Thu, Fri) or for just one day (Fri)? I will let You and Kay decide this and then pass it to the organizers of conference. I would love this. We should have a Google+ Event for this for people to sign up. G+ Event is great idea. I will create it and send you a link as soon as I will have confirmed dates of conference (and so the hackfest). Vaclav ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Xorg freeze totally with systemd-188
2012/8/21 Jeremy Allard elvis4...@gmail.com 2012/8/21 Jeremy Allard elvis4...@gmail.com 2012/8/21 Lennart Poettering lenn...@poettering.net On Tue, 21.08.12 19:21, Jeremy Allard (elvis4...@gmail.com) wrote: Hello ! I'm currently in the process of porting systemd to slackware. systemd is not much fun without PAM. AFAIK Slackware doesn't do PAM. Hence systemd is probably not much fun either. Everything work great, except that when I try to start xorg (as root or as a normal user, it does not change anything), there is visual output (I can see the graphical interface of my wm) but everything else is frozen. I can't switch to TTY, I can't move my mouse and even the magicsysk combination for killing xorg does not work. It seems to kill xorg, but then I just have a black screen. Well, this is too little information to say anthing about this, but did you make sure to install a libudev enabled X and that you enabled logind in systemd? (requires PAM). Lennart -- Lennart Poettering - Red Hat, Inc. I installed pam and rebuild my packages with pam support, and I still have the same issue. Xorg is build with udev support too. Here's a more informations about my configuration to help you figure what's wrong. Here's the version of severals core components of my system. udev: 165 kernel: 3.2.28 (totally vanilla) dbus: 1.4.1 xorg-server: 1.9.5 I know with my first post I did not include a lot information, I'll try to be more clear now. I don't think it matters, but I do not use graphic login manager. I log myself in a tty, and I start Xorg with xinit. I use a really simple tiling wm. My .xinitrc file go like this setxkbmap ca exec spectrwm and that's it. So, I log in into the tty, I do xinit, and I CAN see the graphical interface of my windows manager, but I can't move the mouse, and the keyboard is frozen. As I said before, the magicsysk combination for killing xorg seems to work at 50%. When I do it, I can't see anymore the graphical interface of my windows manager, it's just a black screen. Then, I have no choice, I have to press on the reboot button, but I noticed that when I press on the reboot button just one time, without holding it, I can see the shutdown process going on with systemd. I can't think of what detail I could forget about. I hope I gave enough information. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Xorg freeze totally with systemd-188
Here's a more informations about my configuration to help you figure what's wrong. Here's the version of severals core components of my system. udev: 165 kernel: 3.2.28 (totally vanilla) dbus: 1.4.1 xorg-server: 1.9.5 I know with my first post I did not include a lot information, I'll try to be more clear now. I don't think it matters, but I do not use graphic login manager. I log myself in a tty, and I start Xorg with xinit. I use a really simple tiling wm. My .xinitrc file go like this setxkbmap ca exec spectrwm and that's it. So, I log in into the tty, I do xinit, and I CAN see the graphical interface of my windows manager, but I can't move the mouse, and the keyboard is frozen. As I said before, the magicsysk combination for killing xorg seems to work at 50%. When I do it, I can't see anymore the graphical interface of my windows manager, it's just a black screen. Then, I have no choice, I have to press on the reboot button, but I noticed that when I press on the reboot button just one time, without holding it, I can see the shutdown process going on with systemd. I can't think of what detail I could forget about. I hope I gave enough information. Did you try this with another init system? To be sure that it's a systemd issue... I remember having the same issue when HAL support was not compiled into the XServer but was needed. However I guess that HAL is not an issue anymore. You might also try to figure out the autorun things of your Windowmanager and run a program (glxgears or something else that moves) to figure out whether or not the system is frozen or you just lack possibility of input. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Xorg freeze totally with systemd-188
On Tue, 21.08.12 20:46, Jeremy Allard (elvis4...@gmail.com) wrote: Yes, because pam is not avalaible by default with slackware, I disabled it with --disable-pam since it said in the ./configure --help that it is optional. I guessed it shouldn't be a problem if I disable it. I did not touch logind, so it should be enable afaik. It's to very hard to install PAM on slackware, so I'll try to install it and build my systemd package with pam support and I'll tell you if it work. For libudev support in xorg, there is no --enable-config-udev is not present by default in the build script. The default of this is set to auto, so I guess it is enable anyway even if you don't specify it exactly. logind requires PAM to work. Maybe Slackware is not a good choice to run systemd on if PAM is not available. Lennart -- Lennart Poettering - Red Hat, Inc. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Xorg freeze totally with systemd-188
On Wed, 22.08.12 03:00, Jeremy Allard (elvis4...@gmail.com) wrote: Here's a more informations about my configuration to help you figure what's wrong. Here's the version of severals core components of my system. udev: 165 udev is now part of systemd. You cannot use an external udev. So, I log in into the tty, I do xinit, and I CAN see the graphical interface of my windows manager, but I can't move the mouse, and the keyboard is frozen. That sounds as if X didnt enumerate the input devices. Lennart -- Lennart Poettering - Red Hat, Inc. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] diverting HandlePowerKey
Op 16 aug. 2012, om 16:37 heeft Lennart Poettering lenn...@poettering.net het volgende geschreven: On Thu, 16.08.12 14:47, Mantas Mikulėnas (graw...@gmail.com) wrote: On Thu, Aug 16, 2012 at 2:23 PM, Robin Becker ro...@reportlab.com wrote: However, on my netbooks I like to use the power button to launch oblogout which brings up a bunch of buttons that allow me to logout/suspend/restart/halt etc etc. I can of course continue to use acpid to handle the power button, but that seems opposed to the spirit of systemd. acpid is still okay, I believe. Even though it comes with a single shell script for all actions, it is not part of boot process, and it's not a required part of acpid either – acpid actually has a built-in filtering mechanism in /etc/acpi/events, and the shell script is just default configuration. However, running X11 programs from a daemon, regardless whether it it is logind or acpid, is not recommended. Sure, it might be okay for a single-user machine, but I have ended up with two, three X servers fairly often even on my personal laptop. It'd be a bit better if the button/lid events were handled by a program running inside the Openbox session (the events can be read from /run/acpid.socket). No, nobody should use the acpid client protocol for this. On Linux ACPI key presses are processed like any other keys, and thus are propagated to the X server. The desktop environment should handle these keys and then do whatever is necessary (show a dialog box, react immediatey, ...). And ACPI is x86 only, so you should really focus on catching the KEY_POWER event ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Xorg freeze totally with systemd-188
2012/8/22 Lennart Poettering lenn...@poettering.net On Wed, 22.08.12 03:00, Jeremy Allard (elvis4...@gmail.com) wrote: Here's a more informations about my configuration to help you figure what's wrong. Here's the version of severals core components of my system. udev: 165 udev is now part of systemd. You cannot use an external udev. Oh, yeah, I forgot about this.. Does the fact that udev is installed side by side with systemd can cause this? So, I log in into the tty, I do xinit, and I CAN see the graphical interface of my windows manager, but I can't move the mouse, and the keyboard is frozen. That sounds as if X didnt enumerate the input devices. Hmm, okay. Lennart -- Lennart Poettering - Red Hat, Inc. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Xorg freeze totally with systemd-188
2012/8/22 Franz Dietrich enau...@googlemail.com Here's a more informations about my configuration to help you figure what's wrong. Here's the version of severals core components of my system. udev: 165 kernel: 3.2.28 (totally vanilla) dbus: 1.4.1 xorg-server: 1.9.5 I know with my first post I did not include a lot information, I'll try to be more clear now. I don't think it matters, but I do not use graphic login manager. I log myself in a tty, and I start Xorg with xinit. I use a really simple tiling wm. My .xinitrc file go like this setxkbmap ca exec spectrwm and that's it. So, I log in into the tty, I do xinit, and I CAN see the graphical interface of my windows manager, but I can't move the mouse, and the keyboard is frozen. As I said before, the magicsysk combination for killing xorg seems to work at 50%. When I do it, I can't see anymore the graphical interface of my windows manager, it's just a black screen. Then, I have no choice, I have to press on the reboot button, but I noticed that when I press on the reboot button just one time, without holding it, I can see the shutdown process going on with systemd. I can't think of what detail I could forget about. I hope I gave enough information. Did you try this with another init system? To be sure that it's a systemd issue... I remember having the same issue when HAL support was not compiled into the XServer but was needed. However I guess that HAL is not an issue anymore. You might also try to figure out the autorun things of your Windowmanager and run a program (glxgears or something else that moves) to figure out whether or not the system is frozen or you just lack possibility of input. Yes, I tried with sysvinit and it work perfectly. Yes, I'll try the trick with glxgears. Thanks for your help. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Xorg freeze totally with systemd-188
'Twas brillig, and Jeremy Allard at 22/08/12 18:45 did gyre and gimble: 2012/8/22 Lennart Poettering lenn...@poettering.net mailto:lenn...@poettering.net On Wed, 22.08.12 03:00, Jeremy Allard (elvis4...@gmail.com mailto:elvis4...@gmail.com) wrote: Here's a more informations about my configuration to help you figure what's wrong. Here's the version of severals core components of my system. udev: 165 udev is now part of systemd. You cannot use an external udev. Oh, yeah, I forgot about this.. Does the fact that udev is installed side by side with systemd can cause this? So, I log in into the tty, I do xinit, and I CAN see the graphical interface of my windows manager, but I can't move the mouse, and the keyboard is frozen. That sounds as if X didnt enumerate the input devices. Well potentially. Also consider that latest systemd-udev ships libudev with a major of 1 not 0, so everything needing libudev needs to be recompiled too. Better to ensure that you don't have two versions installed (and neither two versions of the lib). Col -- Colin Guthrie gmane(at)colin.guthr.ie http://colin.guthr.ie/ Day Job: Tribalogic Limited http://www.tribalogic.net/ Open Source: Mageia Contributor http://www.mageia.org/ PulseAudio Hacker http://www.pulseaudio.org/ Trac Hacker http://trac.edgewall.org/ ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] [ANNOUNCE] systemd v189
Heya! http://www.freedesktop.org/software/systemd/systemd-189.tar.xz CHANGES WITH 189: * Support for reading structured kernel messages from /dev/kmsg has now been added and is enabled by default. * Support for reading kernel messages from /proc/kmsg has now been removed. If you want kernel messages in the journal make sure to run a recent kernel (= 3.5) that supports reading structured messages from /dev/kmsg (see above). /proc/kmsg is now exclusive property of classic syslog daemons again. * The libudev API gained the new udev_device_new_from_device_id() call. * The logic for file system namespace (ReadOnlyDirectory=, ReadWriteDirectoy=, PrivateTmp=) has been reworked not to require pivot_root() anymore. This means fewer temporary directories are created below /tmp for this feature. * nspawn containers will now see and receive all submounts made on the host OS below the root file system of the container. * Forward Secure Sealing is now supported for Journal files, which provide cryptographical sealing of journal files so that attackers cannot alter log history anymore without this being detectable. Lennart will soon post a blog story about this explaining it in more detail. * There are two new service settings RestartPreventExitStatus= and SuccessExitStatus= which allow configuration of exit status (exit code or signal) which will be excepted from the restart logic, resp. consider successful. * journalctl gained the new --verify switch that can be used to check the integrity of the structure of journal files and (if Forward Secure Sealing is enabled) the contents of journal files. * nspawn containers will now be run with /dev/stdin, /dev/fd/ and similar symlinks pre-created. This makes running shells as container init process a lot more fun. * The fstab support can now handle PARTUUID= and PARTLABEL= entries. * A new ConditionHost= condition has been added to match against the hostname (with globs) and machine ID. This is useful for clusters where a single OS image is used to provision a large number of hosts which shall run slightly different sets of services. * Services which hit the restart limit will now be placed in a failure state. Contributions from Bertram Poettering, Dave Reisner, Huang Hang, Kay Sievers, Lennart Poettering, Lukas Nykryn, Martin Pitt, Simon Peeters, Zbigniew Jędrzejewski-Szmek Lennart -- Lennart Poettering - Red Hat, Inc. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Xorg freeze totally with systemd-188
It was really a problem with some component of xorg not linked to the good udev, or something like that. I deleted udev, and recompiled all the xorg packages and now it work pretty well. Thanks you very much for all your help. :) ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
