Hi..again !
I've manged to solve my problems ! It seems I had to add an :
ExecStartPre=/bin/rm -f /var/run/messagebus.pid
to my dbus.target unit to ensure that dbus-daemon always starts correctly.
Now the system bus is healthy and I can use it properly.
Best !
2010/9/30 Cristian Axenie
2010/10/1 Cristian Axenie cristian.axe...@gmail.com:
Hi..again !
I've manged to solve my problems ! It seems I had to add an :
ExecStartPre=/bin/rm -f /var/run/messagebus.pid
to my dbus.target unit to ensure that dbus-daemon always starts correctly.
I hope you mean dbus.service here.
You do
@lists.freedesktop.org
Cc: Kay Sievers
Subject: Re: [systemd-devel] Systemd port on custom embedded linux
Sent: Oct 1, 2010 02:20
2010/10/1 Cristian Axenie cristian.axe...@gmail.com:
Hi..again !
I've manged to solve my problems ! It seems I had to add an :
ExecStartPre=/bin/rm -f /var/run
Hi !
I've managed to add the proper symlinks in sbin and the
reboot/halt/poweroff/shutdown are now handled by systemctl. I also removed
the INIT_VERSION environment entry from the corresponding units. Should I
consider to keep the entries in the current units (i.e.: /etc/init.d/reboot)
that are
On Thu, 23.09.10 14:09, Cristian Axenie (cristian.axe...@gmail.com) wrote:
Hi !
Any ideas about the following behavior?
~ # reboot
Broadcast message from root (ttyS0)
The system is going down for system halt NOW!
[ 296.08] systemd-initctl[698]: Received environment initctl
Hi and thanks for the quick reply !
I've added the
Environment=INIT_VERSION=sysvinit-1234
in my units and now I can control the reboot/poweroff/halt of my system !
Best !
2010/9/23 Andrey Borzenkov arvidj...@mail.ru
Thu, 23 Sep 2010 14:09:16 +0300 письмо от Cristian Axenie
Hi ! I've managed to boot my system with systemd although I still have some
problems with autofs.
[ 10.69] Freeing init memory: 152K
[ 11.05] systemd[1]: systemd 8 running in system mode. (+PAM +LIBWRAP
-AUDIT -SELINUX -IPV6 -SYSVINIT)
[ 11.07] systemd[1]: No hostname
On Fri, 17.09.10 16:49, Cristian Axenie (cristian.axe...@gmail.com) wrote:
Hi !
I've managed to solve some problems appearing during boot but some persist.
The current setup makes the system freeze in the current step :
[ 10.23] systemd[1]: systemd 8 running in system mode. (+PAM
Hi !
I've managed to solve some problems appearing during boot but some persist.
The current setup makes the system freeze in the current step :
[ 10.23] systemd[1]: systemd 8 running in system mode. (+PAM +LIBWRAP
-AUDIT -SELINUX -IPV6 -SYSVINIT)
[ 10.25] systemd[1]: No hostname
Am 17.09.2010 15:49, schrieb Cristian Axenie:
Hi !
I've managed to solve some problems appearing during boot but some
persist.
The current setup makes the system freeze in the current step :
[ 10.23] systemd[1]: systemd 8 running in system mode. (+PAM
+LIBWRAP -AUDIT -SELINUX -IPV6
Hi !
I've managed to patch the source code to eliminate the sysvinit and ipv6
problems during bootup but now I encountered some error messages that refer
to other issues.
Here is each line of the output and my ideas :
[ 18.76] Freeing init memory: 152K
[ 19.41] systemd[1]: systemd 8
On Tue, Sep 14, 2010 at 18:40, Lennart Poettering
lenn...@poettering.net wrote:
On Tue, 14.09.10 11:58, Gustavo Sverzut Barbieri (barbi...@profusion.mobi)
wrote:
Lennart, maybe we should make the kmod-setup take another flag MUST
and OPTIONAL, do modprobe for each module in separate and fail
12 matches
Mail list logo
