Re:Writing a BIOS bootloader for 64-bit mode from scratch
by Brian_K_White on Sunday July 14, 2024 @12:36PM
(#40961847)
Sure the facility to fork still exists. So what? Observing that the kernel still provides fork() is like observing that the cpu still provides JMP.
It won't fork random processes you don't explicitly tell it to. I thought it was obvious that if you don't want unsolicited processes, then don't specify /bin/init as /bin/foo. The practical example is /bin/sh, but it could be any other executable.
Up to you to specify a binary that does what you want, and doesn't require a bunch of other processes like gdbus to function itself.
init=/bin/sh is more or less like ms-dos loading command.com
Re:Writing a BIOS bootloader for 64-bit mode from scratch
by gtirloni on Sunday July 14, 2024 @02:59PM
(#40962601)
It's obvious but many people here seem to be confusing the Linux kernel with kernel+systemd and complaining Linux has many processes like it's not customizable.
It won't fork random processes you don't explicitly tell it to. I thought it was obvious that if you don't want unsolicited processes, then don't specify /bin/init as /bin/foo. The practical example is /bin/sh, but it could be any other executable.
Up to you to specify a binary that does what you want, and doesn't require a bunch of other processes like gdbus to function itself.
init=/bin/sh is more or less like ms-dos loading command.com