https://bugzilla.novell.com/show_bug.cgi?id=788282 https://bugzilla.novell.com/show_bug.cgi?id=788282#c1 --- Comment #1 from Frederic Crozat <fcrozat@suse.com> 2012-11-06 11:49:28 UTC --- (In reply to comment #0)

No idea what it means, but I better track it - this happens when starting the live cd (build157)

===> Calling pre-init stage in system image [ 6.859440] systemd[1]: Failed to open configuration file '/run/systemd/syslog.core': No such file or directory [ 6.890380] systemd[1]: Cannot add dependency job for unit syslog.service, ignoring: Unit syslog.service failed to load: No such file or directory. See system logs and 'systemctl status syslog.service' for details. [ 6.925761] systemd[1]: Cannot add dependency job for unit syslog.service, ignoring: Unit syslog.service failed to load: No such file or directory. See system logs and 'systemctl status syslog.service' for details.

syslog integration for systemd probably need some fixes

[ 6.912633] systemd[1]: Cannot add dependency job for unit display-manager.service, ignoring: Unit display-manager.service failed to load: No such file or directory. See system logs and 'systemctl status display-manager.service' for details.

Not really an issue, graphical.target wants display-manager.service (which is the way Fedora handles different display managers, rather than relying on a initscript to start display manager (xdm for us, prefdm for Fedora)

[ 7.373688] systemd-journald[517]: Failed to resolve 'adm' group: No such process

[ 7.387032] systemd-udevd[516]: specified group 'tape' unknown

journald is using "adm" group (when present) to give users in that group permission to read system journal. Maybe we should create this group by default ? this one has been in udev for 3 years.. Nothing new. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.