Gentoo ended up incorporating a lot of the functionality that the Kororaa project provided (mainly a GUI installer). The creator started a new project after a hiatus and kept the name, I guess because he liked it.
The systemd controversy is linux wide. Systemd is a replacement for the old SysV init system. An init system is the software deamon that kicks everything else off and acts as a service manager. It's the first service to start at boot and the last to be killed during shutdown.
Systemd is controversial because it is not just an init system, it's a software suite that controls a wide variety of system functions. It manages user logins, event logging, network configuration, time settings, and device management. Its developers are also in the midst of replacing the kernel-based virtual terminal with their own console. This means that systemd doesn't follow the unix principle of doing one thing and doing it well. Some people don't like this, and believe that systemd "gets in their way." Others look forward to the change, as they hope it will stream line system management, making it more user friendly.
The truth is, unless you're a serious power user or sysadmin (I'm not), you probably won't interact with your OS on a level that it will get in your way. I've found it to be more intuitive, if anything. I'm not really concerned about it violating the unix principle. Most *nix operating systems have gotten way past the point of no return in that regard. See: Unix doesn't follow unix philosophy.
Gentoo ended up incorporating a lot of the functionality that the Kororaa project provided (mainly a GUI installer). The creator started a new project after a hiatus and kept the name, I guess because he liked it.
Regarding Gentoo: What about all that systemd stuff? Why is it good/terrible?
The systemd controversy is linux wide. Systemd is a replacement for the old SysV init system. An init system is the software deamon that kicks everything else off and acts as a service manager. It's the first service to start at boot and the last to be killed during shutdown.
Systemd is controversial because it is not just an init system, it's a software suite that controls a wide variety of system functions. It manages user logins, event logging, network configuration, time settings, and device management. Its developers are also in the midst of replacing the kernel-based virtual terminal with their own console. This means that systemd doesn't follow the unix principle of doing one thing and doing it well. Some people don't like this, and believe that systemd "gets in their way." Others look forward to the change, as they hope it will stream line system management, making it more user friendly.
The truth is, unless you're a serious power user or sysadmin (I'm not), you probably won't interact with your OS on a level that it will get in your way. I've found it to be more intuitive, if anything. I'm not really concerned about it violating the unix principle. Most *nix operating systems have gotten way past the point of no return in that regard. See: Unix doesn't follow unix philosophy.