Am 10.07.2011 14:22, schrieb Sven Joachim: > On 2011-07-10 11:32 +0200, Michael Biebl wrote: > The problem seems to be something else, > namely systemd does apparently not like this combination: > > Architecture: i386 (x86_64) > > With the 2.6.39-2-686-pae kernel rather than a 64-bit one, systemd works > on my desktop as well.
Ah, interesting observation. Will forward this upstream. >> Please attach the full debug log (if you can use a serial line). >> Screenshot(s) >> would be fine too. > > Unfortunately I lack both a serial console and a digital camera ATM. > Might try to setup netconsole later. Not really necessary anymore, I'd say. With the information above it should be easy to reproduce the problem. > On a side note, I noticed two problems: tty1 is messed up, and > /dev/xconsole does not exist. Do you want to have bug reports for > those? - /dev/xconsole: This is a socket which needs to be created explictly, not a bug in systemd itself but rather rsyslog using native systemd service files. In the rsyslog sysv init script we have a mknod call, this should probably be added to the rsyslog.service too (or the rsyslog.conf log rules removed) - tty1 messed up: not quite sure what you mean with messed up. What you are probably seeing is, that with systemd the gettyS are started much earlier, basically as soon as possible, as whereas with sysv they are started last. Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
