can anyone explain to me the steps of switching an already existing

>patch coreutils
>patch build libraries (libc/c++)
>basically patch everything with kernel calls

if you did that correctly, most programs should be recompilable on the new kernel.
that's also how you can run programs written on linux, also on bsd.

>>57804721
what do you mean by patch though, just rewrite it to make calls to hurd instead?

Arch Hurd? More like Arch TURD!

File: 12ed19b23ca011b5f6dd8e1b9986f287.jpg (93KB, 640x480px) Image search: [Google]

93KB, 640x480px

>>57804570
>arch hurd
Now that's something I should try out.

>>57804938
don't you ever compile me or my wife's kernel again.

>>57805012
imagine it was using openRC. it'd be the best.

small kernel
small init system
AUR

how is this not the best distro?

>>57805047
>openrc
archbang

>>57806053
yeah i know im just curious about hurd too since a microkernel seems to be better than a monolithic one for security and stability, but modern hardware doesn't cater to it well or something? i might be mistaken.

>>57804887
The calls are different. There is a table for Linux that has the system calls, their address and their arguments

If the calls on your OS are different, you'll need to let the compiler know what's where since the code standards rely on proper implementation

>>57806076
problem is microkernels have a higher performance hit than monolithic ones because you are doing way more context switches.
this was a problem in the past and all microkernel concepts were aborted or transformed into hybrid ones.

to this date l4 is the most successful microkernel and is used to run on top of linux called l4linux.
microkernels should be the future, since they are practically more crash safe and allow crazy things like runtime driver swapping.
since drivers are hardwired to the kernel it will unfortunately take a decade to make the jump to microkernels.

>>57804938
DELET

>>57804938
arch was already a turd.

>>57804938
Arch Turd? More like Turd Turd!