Earlier quoted context omitted.
You don’t need to use Karabiner for that: keyboard preferences has a modifier keys setting (per keyboard) that achieves this exact remapping with no kernel extensions.
Surprisingly not. You can't re-bind the FN key's function using normal settings. On a 2019 mac pro, catalina, btw, looking at Settings > Keyboard > Modifier Keys...
macOS extensions are moving away from the kernel
141–149 of 149 posts
Re: macOS extensions are moving away from the kernel
#142Earlier quoted context omitted.
> Are the capabilities of Apple's user-level APIs sufficient to replace most legitimate uses of kernel extensions? From what I remember reading from some macOS Application Firewall makers, no. (And that's ofcourse, intentional.) While it is true that poorly coded Kernel extensions can make an OS unstable, this is just another example of Apple taking away more control from its users and further crippling macOS to make…
After feedback from aforementioned firewall developers, changes were made to network extensions that allowed them to do what they wanted with their applications (for the most part, at least). I still think that it’s a worse in-practice system than kexts but they are responding to feedback at least. You can still load kernel extensions in Big Sur by disabling SIP, though.
Re: macOS extensions are moving away from the kernel
#143Earlier quoted context omitted.
BSD was actually grafted into Mach early on, it wasn't something NeXT did.
Wasn't Mach a re-implementation of the original 4.2BSD completely based on IPC in place of syscalls? I distinctly recall some documents saying that XNU achieved much better performances than plain OSFMK thanks to NeXT reworking the BSD parts as components of the kernel instead of being binaries in user space, like in the case of plain Mach.
So to your point: all NeXT was essentially doing was turning Mach 3 back into how Mach 2 worked lol
Thus XNU is a novel implementation of Mach 2: an up to date OSFMK kernel and all its IPC, plus all the BSD parts that used to live in it
Re: macOS extensions are moving away from the kernel
#144Re: macOS extensions are moving away from the kernel
#145Earlier quoted context omitted.
Why do you ask?
i was just curious people use metaphors with a lot of conotation (walled prison) so if there is a more neutral term, i was curious how to state it in either non-positive or non-negative way
Re: macOS extensions are moving away from the kernel
#146Earlier quoted context omitted.
Wasn't Mach a re-implementation of the original 4.2BSD completely based on IPC in place of syscalls? I distinctly recall some documents saying that XNU achieved much better performances than plain OSFMK thanks to NeXT reworking the BSD parts as components of the kernel instead of being binaries in user space, like in the case of plain Mach.
OSFMK is basically Mach 3 onward. That is the actual “microkernel” version. NeXT started with the versions before that, which still had memory management and a litany of other things living in the kernel and not user space. It was basically a gradual evolution of migrating things out. So to your point: all NeXT was essentially doing was turning Mach 3 back into how Mach 2 worked lol Thus XNU is a novel implementation…
Re: macOS extensions are moving away from the kernel
#147systemextensionsctl list yields 0 extensions on my system. Are there any users of these extensions at this point? It does seem a bit weird that installing these extensions supposedly doesn't require any user consent, even though stuff like screen recording or folder access does.
TripMode ( https://tripmode.ch/ ) for filtering application Internet access when you're running on mobile data uses a kernel extension.
Re: macOS extensions are moving away from the kernel
#148Earlier quoted context omitted.
OSFMK is basically Mach 3 onward. That is the actual “microkernel” version. NeXT started with the versions before that, which still had memory management and a litany of other things living in the kernel and not user space. It was basically a gradual evolution of migrating things out. So to your point: all NeXT was essentially doing was turning Mach 3 back into how Mach 2 worked lol Thus XNU is a novel implementation…
Thanks for your explanation, now it's much clearer. It puzzles me why NeXT went through the extra effort of patching OSFMK instead of just doing like everybody else was doing and just fork a monolithic BSD kernel - probably they were already too invested in Mach to pull back?
Re: macOS extensions are moving away from the kernel
#149Earlier quoted context omitted.
i was just curious people use metaphors with a lot of conotation (walled prison) so if there is a more neutral term, i was curious how to state it in either non-positive or non-negative way
Managed ecosystem, or even private ecosystem seem like candidates. Both seem more like factual statements rather than metaphors.