On Do, 12.11.20 20:05, Andrei Enshin (b...@bk.ru) wrote:
>
> Hello systemd folks,
>
> I have a k8s cluster on CoreOS which uses systemd.
> There are few nodes after k8s update started to have (maybe it was before) a
> problem with the following mount:
>
> mount ID 2826
> parent ID
Hello.
On Thu, Nov 12, 2020 at 08:05:34PM +0300, Andrei Enshin wrote:
> There are few nodes after k8s update started to have (maybe it was
> before) a problem with the following mount:
What exact problem do you see?
> It was taken from /proc/self/mountinfo
What was 'self'?
> May I ask, does sys
Am Do., 12. Nov. 2020 um 18:13 Uhr schrieb Zbigniew Jędrzejewski-Szmek
:
> The tags change is probably limited in effect, and the lack of handling
> of "bind" in rules will be more important. But, as you said, that change
> was already happening since kernel 4.2. So it's possible that the biggest
Hey,
This is next attempt to create firmware and bootloader log specification.
Due to high interest among industry it is an extension to the initial
bootloader log only specification. It takes into the account most of the
comments which I got up until now.
The goal is to pass all logs produced by
On 11/13/20 3:52 PM, Daniel Kiper wrote:
> Hey,
>
>
> Here is the description (pseudocode) of the structures which will be
> used to store the log data.
>
> Anyway, I am aware that this is not specification per se.
Yes, you have caveats here. I'm sure that you either already know
or would lear
