On 17/11/2014 15:14, Paul H wrote:
> My plan is that if I find myself depending on packages which no
> longer work under sysvinit-core, I'll rebuild those packages for
> myself as needed (and share the results, if that's helpful): I have
> to do this already now anyway, for example to use build opt
On 17/11/2014 14:12, Jean-Christian de Rivaz wrote:
> Why did you think that localhost sockets activation is not
> deterministic ? When local process use localhost sockets, there is no
> transmission media with risk of packet loss, alteration, random
> latency, or reordering.
I was thinking more i
On 17/11/2014 08:42, Andrei POPESCU wrote:
>> with systemd I have to have
>>
>> waitforgps.sh
>> waitforgps.service (Exec=waitforgps.sh)
>> service.service (After=waitforgps.service)
>>
>> Is this really the best way?
>
> Maybe ExecStartPre= would help? See systemd.service(5).
Oh yes, this is muc
ng a pile of rotting bitbake recipes uphill. xapt and dpkg-cross tools are
truly fantastic (not to mention the rest of debian, like
debhelper). Especially for those of us maintaining packages which need to run
in a bunch of different environments (not just embedded).
>> -
Le 16. 11. 14 19:52, Robert a écrit :
By choosing packages carefully, it is possible to use linux in
applications that need to meet SIL1 or SIL2 criteria [1]. I personally
don't have any applications that need to meet SIL2, but it is possible
to meet SIL1 by taking a normal installation and remov
> --
> Embedded with systemd: systemd and kernel upgrades
>
> This was recently posted on #systemd-devel:
>
> "To make this clear, we expect that systemd and kernels are updated in
> lockstep. We explicitly do not suppo
On Sun, Nov 16, 2014 at 08:52:37PM +0200, Robert wrote:
> This was recently posted on #systemd-devel:
>
> "To make this clear, we expect that systemd and kernels are updated in
> lockstep. We explicitly do not support really old kernels with really
> new systemd. So far we had the focus to support
On Sun, Nov 16, 2014 at 7:52 PM, Robert wrote:
> By choosing packages carefully, it is possible to use linux in
> applications that need to meet SIL1 or SIL2 criteria [1].
No. At least this is my understanding of the situation today. SIL, or
System Integrity Level, is something that needs to be
On Du, 16 nov 14, 20:52:23, Robert wrote:
> Sometimes you only want services to start based on a "weird" trigger.
> I have one use case where I only want a service to start once we have
> received a valid GPS lock. With /sbin/init it looked like this:
>
> #!/bin/bash
> while [ ]; do
>sleep 5;
On Du, 16 nov 14, 20:52:13, Robert wrote:
>
> To help with field debugging I currently check the state of one of the
> buttons at startup and if it is pressed, the unit starts the 802.11 in
> host (hostapd) mode and starts sshd.
>
> This was trivial to configure with /sbin/init calling a shellscr
nally had these as separate emails, but the listmaster has
requested that I combine them --- they are included below
---
Embedded with systemd: systemd and SIL
By choosing packages carefully, it is possible to use linux in
applications that need to meet SI
Given the existence of
(http://www.freedesktop.org/wiki/Software/systemd/MyServiceCantGetRealtime/),
it seems that realtime and systemd is problematic. Has anyone tried the
workarounds mentioned with a PREEMPT_RT kernel? How did it go?
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian
This was recently posted on #systemd-devel:
"To make this clear, we expect that systemd and kernels are updated in
lockstep. We explicitly do not support really old kernels with really
new systemd. So far we had the focus to support up to 2y old kernels
(which means 3.4 right now), but even that s
Sometimes you only want services to start based on a "weird" trigger.
I have one use case where I only want a service to start once we have
received a valid GPS lock. With /sbin/init it looked like this:
#!/bin/bash
while [ ]; do
sleep 5; #wait for lock
done;
service &
with systemd I have to
By choosing packages carefully, it is possible to use linux in
applications that need to meet SIL1 or SIL2 criteria [1]. I personally
don't have any applications that need to meet SIL2, but it is possible
to meet SIL1 by taking a normal installation and removing a bunch of
stuff (initramfs, udev an
I have a use case where I have a logging unit with a few buttons that
are available to the user. The buttons are read via the kernel GPIO
methods. There is no display, no keyboard, only 802.11.
Normally the unit starts a few daemons and starts the 802.11 in client
(wpa_supplicant) mode.
To help w
Hi
This is my first post to a debian-* list even though I have been a
(happy) user for many years, both on the desktop and on embedded
devices. I am currently looking at the implications that running systemd
on some of our products will have, and while many things seem like they
will get simpler,
17 matches
Mail list logo
