On Wed, 2024-05-22 at 17:42 +0200, Lennart Poettering wrote:
> On Mi, 22.05.24 17:13, Nop ([email protected]) wrote:
>
> > Hello folks,
> > I have a question about what you guys considers to be the
> > right/expect way.
> >
> > I read documentation a bit about INVOCATION_ID and JOURNAL_STREAM and,
To me, just like you, it all started with me trying to detect if
running as part of systemd service or not.
And by that I really mean: user clicked somewhere, or typed in some
command in an input box or a TE, without having to be aware that
systemd is involved under the hood or not.
I do get that i
On 23.05.2024 09:18, Nop wrote:
From my terminal emulator that I start by clicking in the menu:
echo "kitty: $(pidof kitty) - $INVOCATION_ID" && echo "plasmashell:
$(pidof plasmashell) - $(sudo strings /proc/$(pidof
plasmashell)/environ | grep INVOCATION_ID)"
kitty: 4441 - e3ec804609094a139948a1
On Do, 23.05.24 10:54, Mikko Rapeli ([email protected]) wrote:
> Hi,
>
> I'm running in circles and failing to start optee userspace daemon
> tee-supplicant
> correctly with systemd in initrd.
>
> In certain firmware/HW configurations with optee and firmware TPM trusted
> application,
> th
Hi,
I'm running in circles and failing to start optee userspace daemon
tee-supplicant
correctly with systemd in initrd.
In certain firmware/HW configurations with optee and firmware TPM trusted
application,
the setup needs tee-supplicant to start in initrd userspace before the fTPM
kernel
modu
