πKey notes from systemd@meta speach
https://pretalx.devconf.info/devconf-cz-2025/talk/KNER89/
- systems is used everywhere. So there is special team to manage problems & contribute
- use different name spaces for different services
- minimize diff & stay sync with the upstream
- tests are heavy and not all of then can be executed inside containers
- systemd inside systemd is coming
- dbus will be replaced by varlink
#conf #linux #devconf
https://pretalx.devconf.info/devconf-cz-2025/talk/KNER89/
- systems is used everywhere. So there is special team to manage problems & contribute
- use different name spaces for different services
- minimize diff & stay sync with the upstream
- tests are heavy and not all of then can be executed inside containers
- systemd inside systemd is coming
- dbus will be replaced by varlink
#conf #linux #devconf
π2π₯1
π key notes from diagram as code
https://pretalx.devconf.info/devconf-cz-2025/talk/KDBZQ3/
- if more than 10s are required to read your diagram then simplify it
- in v1 approach there is fundamental issue with consistency of multiple diagrams because itβs like text
- v2 approach is about using code instead of text for diagrams. Like code or scripts
#conf #devconf
https://pretalx.devconf.info/devconf-cz-2025/talk/KDBZQ3/
- if more than 10s are required to read your diagram then simplify it
- in v1 approach there is fundamental issue with consistency of multiple diagrams because itβs like text
- v2 approach is about using code instead of text for diagrams. Like code or scripts
#conf #devconf
π1π€‘1
π OMG i can become root! Keynotes
https://pretalx.devconf.info/devconf-cz-2025/talk/LXBAUV/
- UAG(use after free) attack still actual in 2025
- use modern language = thereβs no the problem
- at least there 3 techniques to mitigate problems in c/c++
- however itβs better to detect it. Hopefully there are some methods to do that
- and prevent
#conf #linux #devconf
https://pretalx.devconf.info/devconf-cz-2025/talk/LXBAUV/
- UAG(use after free) attack still actual in 2025
- use modern language = thereβs no the problem
- at least there 3 techniques to mitigate problems in c/c++
- however itβs better to detect it. Hopefully there are some methods to do that
- and prevent
#conf #linux #devconf
π€2