[systemd-devel] systemd prerelease 245-rc2

A new systemd ☠️ pre-release ☠️ has just been tagged. Please download the tarball here: https://github.com/systemd/systemd/archive/v245-rc2.tar.gz NOTE: This is ☠️ pre-release ☠️ software. Do not run this on production systems, but please test this and report any issues you find to GitHu

[systemd-devel] "[Match]" section in systemd.link file doesn't match interface

Hello everybody, I'm failing to set an alias for a link using systemd-networkd. Am I doing something wrong? Is this a bug? I'm on this systemd version: systemd 244 (244.3-1~bpo10+1) +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +

Re: [systemd-devel] Unsubscribe from this list

Am 02.03.20 um 13:35 schrieb Lubor Kolář: > Hi,I am trying to unsubscribe for a couple of week using the unsubscribe > link from mail header but it is always rejected: > > Address not found > > Your message wasn't delivered to > systemd-devel-requ...@lists.freedesktop.org >

Re: [systemd-devel] sd-daemon documentation clarification

> AFAIK both stdout and stderr even get attached to the same journal pipe by > default, so they should also be interpreted in the same way. > > The description of SyslogLevelPrefix= in systemd.exec(5) also says: "This > only applies to log messages written to stdout or stderr.” THX, I must have

[systemd-devel] Unsubscribe from this list

Hi,I am trying to unsubscribe for a couple of week using the unsubscribe link from mail header but it is always rejected: Address not found Your message wasn't delivered to systemd-devel-requ...@lists.freedesktop.org because the address couldn't be found, or is unable to receive mail. The respons

Re: [systemd-devel] sd-daemon documentation clarification

On Mon, Mar 2, 2020 at 1:38 PM Łukasz Niemier wrote: > `man 3 sd-daemon` states that `SD_*` prefixes works with `stderr` logging: > > These prefixes are intended to be used in conjunction with stderr-based > logging as implemented by systemd. > > > But only if `StandardError=` is set to one of `j

[systemd-devel] sd-daemon documentation clarification

`man 3 sd-daemon` states that `SD_*` prefixes works with `stderr` logging: > These prefixes are intended to be used in conjunction with stderr-based > logging as implemented by systemd. But only if `StandardError=` is set to one of `journal`, `syslog`, or `kmsg`. Does that mean that these prefi

Re: [systemd-devel] Ask some questions about overlay+/dev/mtdblock?

If after uninstalling block4 and block5, I don't want overlay to have direct access to block4 or block5, what should I do? thanks， Byron At 2020-03-02 16:21:17, "www" wrote: Dear all, Systemd is used in the embedded system. and some mounting information is as follows: dev on /dev

Re: [systemd-devel] Ask some questions about overlay+/dev/mtdblock?

If after uninstalling block4 and block5, I don't want overlay to have direct access to block4 or block5, what should I do? thanks， Byron At 2020-03-02 16:21:17, "www" wrote: Dear all, Systemd is used in the embedded system. and some mounting information is as follows: dev on /dev

Re: [systemd-devel] Read-only /etc, machine-id with an overlay - journald failing

On Thu, Feb 27, 2020 at 05:39:27PM +0200, Mantas Mikulėnas wrote: > On Wed, Feb 26, 2020 at 11:59 AM Andreas Kempe > wrote: > > > Hello everyone, > > > > I'm working in a project with an embedded Linux system based on > > Openembedded using Systemd version 241 as our init process. We're > > using

Re: [systemd-devel] Read-only /etc, machine-id with an overlay - journald failing

On Thu, Feb 27, 2020 at 11:53:45PM +0100, Jérémy ROSEN wrote: > Le jeu. 27 févr. 2020 à 16:30, Andreas Kempe a > écrit : > > I was contemplating whether it could be acceptable having the same > > static machine-id file pre-generated for all systems. I'm not 100% sure > > what it's used for, TBH; w

[systemd-devel] Ask some questions about overlay+/dev/mtdblock?

Dear all, Systemd is used in the embedded system. and some mounting information is as follows: dev on /dev type devtmpfs (rw,relatime,size=221372k,nr_inodes=55343,mode=755) sys on /sys type sysfs (rw,relatime) proc on /proc type proc (rw,relatime) tmpfs on /run type tmpfs (rw,nosuid,nodev,mode