Am Mi, 25. Aug 2021, um 18:51, schrieb Andrei Borzenkov:
> On Wed, Aug 25, 2021 at 3:44 PM Andrei Borzenkov wrote:
> ...
> > > Here's the udev rule:
> > > ```
> > > ACTION=="add", SUBSYSTEMS=="usb", SUBSYSTEM=="block", KERNEL=="*[0-9]*",
> > > ENV{ID_FS_USAGE}=="filesystem", TAG+="systemd",
> >
On 18/08/21 12:24 pm, Amish wrote:
Hello
Further to my previous email:
I see that there is already an *extremely similar issue* reported on
July 12, 2021 and it has been fixed.
https://github.com/systemd/systemd/issues/20203
But I do not know if this fix exists in systemd v249.3 (Arch
On Wed, Sep 1, 2021 at 2:40 PM EpicLemon99
wrote:
> I am unable to boot up ISO files of Linux distributions that use systemd.
> My computer is a HP Pavilion TG01-2856no, it is recent hardware. The boot
> gets stuck when it tries to start systemd services, such as Network Time
> Synchronization.
Colin Guthrie wrote on 01/09/2021 14:30:
rpm -qa | xargs rpm --setugids >/dev/null 2>&1
Correction: --restore is actually needed over --setugids as although
only the latter is strictly needed, it seems without the former the
setuid bits on e.g. /usr/bin/su etc are also reset, so --restore
Hi,
So I didn't appreciate this before, but it seems a long standing RPM
issue where, when using --root the packages will be installed with the
uid/gid mappings from the host machine rather than the passwd/group
files from the root.
This makes for a problem using mkosi as it doesn't make
I am unable to boot up ISO files of Linux distributions that use systemd. My
computer is a HP Pavilion TG01-2856no, it is recent hardware. The boot gets
stuck when it tries to start systemd services, such as Network Time
Synchronization.
For example, there are the messages I get when trying to
Hi,
I am playing with the idea of using systemd mount to mount S3 bucket on
the system using s3fs.
To mount a bucket, an API key is required. s3fs can read the API key
from a file specified as an option:
s3fs $bucket_name $where -o passwd_file=${PATH_TO_PASSWORD_FILE} ...
I tried to set up a
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
