653
all 13 comments
sorted by: hot top controversial new old
[-] Mubelotix@jlai.lu 44 points 1 year ago

permission

the power of free/libre software

[-] psud@lemmy.world 44 points 1 year ago

Compiling your own kernel, configured for your hardware and use, was normal in the early days

This happens on Mac as well btw. kexts are kernel extensions

[-] alonely0@programming.dev 23 points 1 year ago

You're not really changing anything, you're adding functionalities. Also, it appears that apple has limited their capabilities and doesn't even recommend them anymore, so it wouldn't be crazy if they just deprecated them in favor of system extensions, which sadly they don't call sexts. On the surface, kexts appear to be basically userland ioctls, which you have on windows too.

[-] Espi@lemmy.world 3 points 1 year ago
[-] AffineConnection@lemmy.world 1 points 1 year ago

Maybe about 4-5 years ago, I read through the source to find obscure undocumented features of a couple system calls that allowed me to write a detailed system/process monitor utility that does things that nothing else seems to know about.

[-] Tschuuuls@feddit.de 2 points 1 year ago

10+ year Mac user here. It's a bit sad but better for system stability. A lot of weird hardware and software used to just inject kexts instead of doing stuff in userspace. This can cause weird issues like battery drain, crashes etc. which are hell to debug as a "average user". I don't really miss running "Entre Check" to figure out weird issues :D

As a mac-first guy I wasn’t aware of mimicked (really bothers me this word is spelled with a ‘k’) functionality on windows. I simply mean that by adding a kext you are, by design, changing the code of the kernel. More of a particulars in speech thing.

[-] LazaroFilm@lemmy.world 18 points 1 year ago

You have to say sudo first.

[-] mvirts@lemmy.world 6 points 1 year ago

Gimme that CAP_SYS_MODULE

this post was submitted on 01 Oct 2023
653 points (98.4% liked)

linuxmemes

21280 readers
1164 users here now

Hint: :q!


Sister communities:


Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack members of the community for any reason.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
  • These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
  • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn. Even if you watch it on a Linux machine.
  • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.
  •  

    Please report posts and comments that break these rules!


    Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't fork-bomb your computer.

    founded 1 year ago
    MODERATORS