Hey there,
I believe Christian may have relayed some of this already but on my
side, as much as I can sympathize with the annoyance of having to
support both cgroup1 and cgroup2 side by side, I feel that we're sadly
nowhere near the cut off point.
>From what I can gather from various stats we
Vito,
You're correct - it's a typo due to Microsoft auto correction. It is
lib/systemd/system.
I just discovered that the systemd.mak file provided in Buildroot contains:
define SYSTEMD_INSTALL_SERVICE_AUTOVT
ln -sf ../../../lib/systemd/system/getty@.service \
On Thu, Jul 21, 2022 at 03:33:34PM +, Otten, Jeffrey wrote:
> I'm trying to build systemd 243.4 using Buildroot 2019.11. The lines listed
> below are generated during the build. I've googled but haven't come across
> any discussion of this issue.
> The directory
>
I'm trying to build systemd 243.4 using Buildroot 2019.11. The lines listed
below are generated during the build. I've googled but haven't come across any
discussion of this issue.
The directory
/home/ottenj/elinux/build/buildroot/fvlinux/target/lib/system/system listed in
the error below does
[Cc Stéphane and Serge]
On Thu, Jul 21, 2022 at 11:03:49AM +0200, Lennart Poettering wrote:
> Heya!
>
> It's currently a terrible mess having to support both cgroupsv1 and
> cgroupsv2 in our codebase.
>
> cgroupsv2 first entered the kernel in 2014, i.e. *eight* years ago
> (kernel 3.16). We
Heya!
It's currently a terrible mess having to support both cgroupsv1 and
cgroupsv2 in our codebase.
cgroupsv2 first entered the kernel in 2014, i.e. *eight* years ago
(kernel 3.16). We soon intend to raise the baseline for systemd to
kernel 4.3 (because we want to be able to rely on the