Re: [systemd-devel] About stable network interface names

2017-05-28 Thread Greg KH
On Mon, May 29, 2017 at 02:35:12AM +0200, Cesare Leonardi wrote: > I ask because I've done several tests, with different motherboards, adding > and removing PCI-express cards and that expectation was not satisfied in > many cases. > > For example, in one of those tests I initially had this setup:

Re: [systemd-devel] Systemd -- Using Environment variable in a Unit file from Environment File

2017-05-28 Thread Raghavendra. H. R
Guys, Any suggestions about this kind of problem ? -- Regards, Raghavendra. H. R (Raghu) On Fri, May 26, 2017 at 3:06 PM, Raghavendra. H. R wrote: > Hi All, > > I'm in the situation where path of my server changes due to version > change. I don't want to modify my

[systemd-devel] Systemd crash when trying to boot Angstrom image with systemd enabled

2017-05-28 Thread Sonu Abraham
Hi , I get the following kernel panic when trying to using system-console image from Angstrom distribution on imx28evk board [9.506682] UBIFS (ubi0:0): FS size: 236302336 bytes (225 MiB, 1861 LEBs), journal size 9023488 bytes (8 MiB, 72 LEBs) [9.517600] UBIFS (ubi0:0): reserved for

[systemd-devel] About stable network interface names

2017-05-28 Thread Cesare Leonardi
Hello, I've some dubts related to predictable network interface names. If I understand correctly the reference document about this topic is: https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/ Take this paragraph from that document: - We believe it is a good

Re: [systemd-devel] pid namespaces, systemd and signals on reboot(2)

2017-05-28 Thread Michał Zegan
W dniu 28.05.2017 o 20:43, Mike Gilbert pisze: > On Sat, May 27, 2017 at 2:51 PM, Michał Zegan > wrote: >> Hello. >> >> I came across the following: >> The manpage reboot(2) says, that inside of a pid namespace, a reboot >> call that normally would trigger restart

[systemd-devel] Group of temporary but related units?

2017-05-28 Thread Benno Fünfstück
Hey list, what would be a good way to manage temporary development environments with systemd? For example, if I quickly want to spawn up an environment where my service + perhaps some db or a queue or some other services are running. It would be nice to reuse systemd's service management