[email protected]
Cc: Kay Sievers
Subject: Re: [systemd-devel] Systemd port on custom embedded linux
Sent: Oct 1, 2010 02:20
2010/10/1 Cristian Axenie :
> Hi..again !
>
> I've manged to solve my problems ! It seems I had to add an :
> ExecStartPre=/bin/rm -f /var/run/
2010/10/1 Cristian Axenie :
> 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 know that dbus upstr
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
> Hi al
Hi all!
Next a failing context for DBus daemon is described both when using
systemctl enable dbus.service to generate links in the specific
.target.wants dirs or by using the default unit configuration after building
systemd.
So, after enabling the dbus unit and booting the board I get :
9.50
2010/9/27 Andrey Borzenkov :
> Mon, 27 Sep 2010 17:39:15 +0200 письмо от Lennart Poettering
> :
>> On Mon, 27.09.10 13:07, Cristian Axenie ([email protected]) wrote:
>> > I've managed to add the proper symlinks in sbin and the
>> > reboot/halt/poweroff/shutdown are now handled by systemct
On Mon, 27.09.10 13:07, Cristian Axenie ([email protected]) wrote:
> 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
> con
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 unm
1;2591;0cOn Thu, 23.09.10 16:26, Andrey Borzenkov ([email protected]) wrote:
> It could be related to the fact that this is not enough. Standard halt command
> from sysvinit behaves differently depending whether it is called by user or
> by /sbin/init. When called by user it simply pokes init via
On Thu, 23.09.10 14:09, Cristian Axenie ([email protected]) 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 initct
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
>
> Thu, 23 Sep 2010 14:09:16 +0300 письмо от Cristian Axenie <
> [email protected]
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 request.
This is not implemented in systemd.
And then the system freezes !
It seems that t
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 configured.
On Fri, 17.09.10 16:49, Cristian Axenie ([email protected]) 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
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 -SYS
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 confi
On Tue, Sep 14, 2010 at 18:40, Lennart Poettering
wrote:
> On Tue, 14.09.10 11:58, Gustavo Sverzut Barbieri ([email protected])
> wrote:
>
>> Lennart, maybe we should make the kmod-setup take another flag "MUST"
>> and "OPTIONAL", do modprobe for each module in separate and fail if
>> "MUST
On Tue, 14.09.10 11:58, Gustavo Sverzut Barbieri ([email protected])
wrote:
> Lennart, maybe we should make the kmod-setup take another flag "MUST"
> and "OPTIONAL", do modprobe for each module in separate and fail if
> "MUST" are not present? Right now it is confusing for users.
Well, I d
On Tue, 14.09.10 16:47, Cristian Axenie ([email protected]) wrote:
> [ 19.59] systemd[1]: Failed to open /dev/autofs: No such file or
Seems the automounter is not compiled in. Either don't use .automount
units or enable it in the kernel. My recommendation is the latter.
> Here the
On Tue, Sep 14, 2010 at 10:47 AM, Cristian Axenie
wrote:
> 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.
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 r
20 matches
Mail list logo
