On 11/28/24 8:19 PM, Andrei Borzenkov wrote:
Try
systemctl -t device -a
Ok thanks. It missed the namespace part (n1):
# systemctl -t device -a | grep -iE '^dev-nvme'
dev-nvme0n1.device
loaded active plugged SAMSUNG MZQLB960HAJR-7
dev-nvme0n1p1.device
loade
28.11.2024 21:49, Thomas HUMMEL wrote:
On 11/25/24 3:07 PM, Thomas HUMMEL wrote:
On 11/25/24 2:50 PM, Andrei Borzenkov wrote:
On Mon, Nov 25, 2024 at 4:39 PM Thomas HUMMEL
wrote:
Hello,
I've got a somehow silly question:
Am I right to think that a service unit I wrote meant to format and
m
On 11/28/24 7:56 PM, Cristian Rodríguez wrote:
On Thu, Nov 28, 2024 at 3:50 PM Thomas HUMMEL
wrote:
Hello,
coming back to the topic (sorry, I had an actual physical issue with the
device which blurred my analysis):
1. On a system where /dev/nvme0, /dev/nvme0n1 and /dev/nvme0n1p1 files
exis
On Thu, Nov 28, 2024 at 3:50 PM Thomas HUMMEL
wrote:
>
>
> Hello,
>
> coming back to the topic (sorry, I had an actual physical issue with the
> device which blurred my analysis):
>
> 1. On a system where /dev/nvme0, /dev/nvme0n1 and /dev/nvme0n1p1 files
> exist, systemctl list-units --type=devic
On 11/25/24 3:07 PM, Thomas HUMMEL wrote:
On 11/25/24 2:50 PM, Andrei Borzenkov wrote:
On Mon, Nov 25, 2024 at 4:39 PM Thomas HUMMEL
wrote:
Hello,
I've got a somehow silly question:
Am I right to think that a service unit I wrote meant to format and
mount a localdisk at boot having the foll
Thank you for your comprehensive answer and your time. I have a good
understanding.
/proc/net/unix with xattr sounds like a good idea. I guess one caveat is that
it won’t show the activatable varlinks.
Maybe we are talking about 2 kinds of discovery, one of them is the service
discovery and th
Am 27.11.24 um 09:55 schrieb Lennart Poettering:
SIGABRT has a pretty clear usecase: to abnormally terminate a program
while creating a coredump. It seems you want to redefine what SIGABRT
is supposed to do? That's quite problematic I would say. What's the
rationale for that?
Note that systemd
On Mi, 27.11.24 19:01, Umut Tezduyar Lindskog (umut.tezdu...@axis.com) wrote:
> Hello systemd,
>
> We are closely observing the varlink development and excited about
> it. Our guys who were at the all systems go conference mentioned
> that the Resolver is not part of the systemd family. Ref: Resol
On Mi, 27.11.24 19:00, Umut Tezduyar Lindskog (umut.tezdu...@axis.com) wrote:
> Hello systemd,
>
> We are looking into systemd system extensions for quick patching our
> immutable images while we are updating and rolling out the patched
> immutable image.
>
> One thing that is stated in the docume
