Am 26.08.23 um 18:41 schrieb Cecil Westerhof:
Replying on google does not work as I am used to. It sends to the sender
instead of the group.
Op za 26 aug 2023 om 18:36 schreef Cecil Westerhof
mailto:cldwester...@gmail.com>>:
Op za 26 aug 2023 om 14:46 schreef Michael Biebl
Am 16.02.23 um 11:17 schrieb Lennart Poettering:
On Mi, 15.02.23 17:59, Jacopo (fingolfi...@gmail.com) wrote:
udev rule:
ACTION=="add", SUBSYSTEM=="block", KERNEL=="sd*", SUBSYSTEMS=="usb",
ENV{DEVTYPE}=="partition", IMPORT{builtin}="blkid",
ENV{ID_FS_TYPE}=="ext4",
Am 13.07.22 um 00:11 schrieb Leon Fauster:
Am 12.07.22 um 18:55 schrieb Thomas HUMMEL:
Hello,
I'm using systemd-239-45 on RHEL 8.4 x86_64 AMD nodes on which I
disable Turbo Core/Turbo Boost by writing '0' into the following file:
Uups, the AMD string was not recognized. So, my comments
Am 12.07.22 um 18:55 schrieb Thomas HUMMEL:
Hello,
I'm using systemd-239-45 on RHEL 8.4 x86_64 AMD nodes on which I disable
Turbo Core/Turbo Boost by writing '0' into the following file:
/sys/devices/system/cpu/cpufreq/boost
What about /sys/devices/system/cpu/intel_pstate/no_turbo ?
And
Am 09.04.22 um 10:00 schrieb Yolo von BNANA:
--- Original Message ---
On Friday, April 8th, 2022 at 13:49, Lennart Poettering
wrote:
This could be done better. Plugging in just a "kill" here, means the
reload is async. i.e. "systemctl reload" will basically return
immediately without
Am 29.10.21 um 07:47 schrieb Andrei Borzenkov:
On 28.10.2021 16:04, Olaf Hering wrote:
There is A.timer and its A.service, and B.timer and B.service.
Both A and B do not know about each other per default.
Both timers fire in their own cadence.
Both services have their unpredictable time until
On 28.09.21 23:13, Lennart Poettering wrote:
On Di, 28.09.21 19:44, Leon Fauster (leonfaus...@googlemail.com) wrote:
Hallo Lennart, corresponding to your last post about FDE:
On an EFI system - would an encrypted "/boot" or /boot on
an encrypted "/" filesystem eliminat
Hallo Lennart, corresponding to your last post about FDE:
On an EFI system - would an encrypted "/boot" or /boot on
an encrypted "/" filesystem eliminate the mentioned main
attack vector? The whole chain would be authenticated.
firmware->shim->bootloader/grub2->{manual
On 02.09.21 15:12, Andrei Borzenkov wrote:
On 02.09.2021 15:10, Leon Fauster wrote:
On 02.09.21 08:00, Andrei Borzenkov wrote:
On 02.09.2021 01:19, Leon Fauster wrote:
Example:
a@.service
b.service
a@.service is started as a@host1.service and b.service must be started
after a@host1.service
On 02.09.21 08:00, Andrei Borzenkov wrote:
On 02.09.2021 01:19, Leon Fauster wrote:
Example:
a@.service
b.service
a@.service is started as a@host1.service and b.service must be started
after a@host1.service but the unit will be differently parameterized
(depended of the region). So I want
Dear list,
following requirement exists here (systemd-239 installed):
Applying a "Requires" statement with an instantiated service.
Example:
a@.service
b.service
a@.service is started as a@host1.service and b.service must be started
after a@host1.service but the unit will be differently
11 matches
Mail list logo
