!DBFhtjpqmJNENpLDOv:nixos.org

NixOS Systemd

309 Members
NixOS ❤️ systemd98 Servers

Load older messages


SenderMessageTime
7 Dec 2022
@jkarlson:kapsi.fiEmil Thorsøestat /boot/loader/random-seed or similar14:25:35
@jkarlson:kapsi.fiEmil Thorsøenot sure, if this would be a thing that would work with stage1 systemd14:26:09
@elvishjerricco:matrix.orgElvishJerriccoIn theory that should be irrelevant. systemd-boot should be updating the random-seed14:28:52
@elvishjerricco:matrix.orgElvishJerricco
In reply to @jkarlson:kapsi.fi
stat /boot/loader/random-seed or similar
Looks like it was modified last time I booted.
14:32:00
@jkarlson:kapsi.fiEmil Thorsøethanks14:47:00
@jkarlson:kapsi.fiEmil Thorsøedo you use stage1 systemd?14:47:17
@elvishjerricco:matrix.orgElvishJerriccoI do, but I am pretty confident that doesn't have anything to do with it14:51:28
@elvishjerricco:matrix.orgElvishJerriccobtw the code in systemd-random-seed I was looking at is apparently new: https://github.com/systemd/systemd/pull/2531914:52:02
@elvishjerricco:matrix.orgElvishJerriccoSo right now, systemd-boot is supposed to update the ESP random-seed if you have a "system token" efi variable (which I think is supposed to be setup by bootctl)14:52:46
@elvishjerricco:matrix.orgElvishJerricco And in the future, on shutdown, systemd-random-seed.service will cause the ESP random seed to be updated as well 14:53:05
@elvishjerricco:matrix.orgElvishJerricco * And in a future version, on shutdown, systemd-random-seed.service will cause the ESP random seed to be updated as well 14:53:24
@threedee:matrix.orgthreedee joined the room.20:18:03
8 Dec 2022
@frostman:matrix.orgSergei Lukianov joined the room.03:05:59
@frostman:matrix.orgSergei Lukianovhi, not sure if it's a best/right place to ask about it, but I've faced an issue with permissions that need to be granted to a systemd service to be able to run smartctl for nvme drives. I've specifically talking about prometheus-smartctl-exporter. It was recently fixed and work correctly for HDDs but it's not working for NVMe in my setup. Thank you in advance if there are some ideas! https://github.com/NixOS/nixpkgs/blob/96d7f290878dec43e2688940467d24499c208cd9/nixos/modules/services/monitoring/prometheus/exporters/smartctl.nix#L4203:10:50
@nam3l33ss:matrix.org★.¸¸¸. •°´Nameless☆*´¨`*☽ changed their profile picture.05:11:54
@nam3l33ss:matrix.org★.¸¸¸. •°´Nameless☆*´¨`*☽ changed their profile picture.06:32:46
@nam3l33ss:matrix.org★.¸¸¸. •°´Nameless☆*´¨`*☽ changed their profile picture.06:37:30
@nam3l33ss:matrix.org★.¸¸¸. •°´Nameless☆*´¨`*☽ changed their profile picture.06:39:22
@jkarlson:kapsi.fiEmil Thorsøe
In reply to @elvishjerricco:matrix.org
I do, but I am pretty confident that doesn't have anything to do with it
maybe you are on unstable that maybe has new systemd?
06:39:29
@elvishjerricco:matrix.orgElvishJerricco Emil Thorsøe: I am on a very recent unstable but it's still only on 251.7, not 252 yet 06:40:47
@elvishjerricco:matrix.orgElvishJerricco * Emil Thorsøe: I am on a very recent nixos-unstable but it's still only on 251.7, not 252 yet 06:41:26
@jkarlson:kapsi.fiEmil Thorsøeack06:42:20
@frostman:matrix.orgSergei LukianovFixed by adding services.udev.extraRules = '' SUBSYSTEM=="nvme", KERNEL=="nvme[0-9]*", GROUP="disk" '';10:03:39
@hexa:lossy.networkhexaI was wondering why systemd didn't provide that rule10:15:50
@hexa:lossy.networkhexaso right now nvme0 is owned by root:root, but the namespaces aber owned by root:disk10:16:25
@nam3l33ss:matrix.org★.¸¸¸. •°´Nameless☆*´¨`*☽ changed their profile picture.14:22:18
@nam3l33ss:matrix.org★.¸¸¸. •°´Nameless☆*´¨`*☽ changed their profile picture.14:28:15
@frostman:matrix.orgSergei Lukianov hexa yeah, I wasn't able to find any reasoning for it, but at least it works :) and doesn't look too bad 18:42:24
@hexa:lossy.networkhexa😄18:50:52
@terrestrialpedestrian:cat.casaterrestrialpedestrian joined the room.19:09:11

There are no newer messages yet.


Back to Room ListRoom Version: 6