>>6 Yeah, I don't mind it. It was really annoying at first, but once you're used to it it has a lot of convenience features that KDE doesn't have. There are some irritating pieces, like the fact that you basically can't get rid of the bar at the top of the screen, but for the most part it's ok. I'm running it on a powerful machine, so performance isn't awful.
I'm not a typical Linux user, though; I don't really care much about configuring my machine. I use Linux instead of Windows because it's easier to use and because when you get down to it, it runs a lot faster - you can arge about whether Windows is faster or slower in a "fair test," but in the real world there are a billion things that slow Windows down, and boot takes forever. The freedom thing is a definite plus as well.
Name:
Anonymous2014-10-13 15:07
Gentoo is my favourite distro, although I've never tried funtoo. I probably will on future machines. I don't know what anyone has against it, unless you really don't want to wait a few minutes for things to compile.
Name:
Anonymous2014-10-13 18:19
>>12 When you're working with low-powered devices, compiling a kernel doesn't take just ``a few minutes''. I use it on my desktop PC, but there's no way I'm using it on the Celerons I've got at work.
it is a replacement for sysv-rc, not for sysv-init.
Name:
Anonymous2014-10-19 5:25
Systemd is well designed. It was conceived from the top, not just to fix bugs, but to be a correct implementation for the base system services.
Systemd makes the boot process much simpler, entirely removing the need to specify dependencies in many cases thanks to D-Bus activation, socket activation, file/inotify activation and udev integration. Systemd can handle the boot process from head to toe, without needing to use any of the existing shell scripts. Systemd is straightforward. The command-line interface is probably the best existing for service management. The unit file format (like .desktop or “ini” files) is completely declarative, can be parsed using standard tools, and is a breeze to maintain. Systemd unit files, unlike SysV scripts, can usually be shipped by upstream, or at least shared with other distributions (already more than 1000 existing unit files in Fedora) without any changes, the Debian specifics being handled by systemd itself. Systemd is incredibly fast (1 second to boot). It was not designed with speed in mind, but doing things correctly avoids all the delays currently incurred by the boot process. The transition plan is easy, since existing init scripts are treated as first-class services: scripts can depend (using LSB headers) on units, units can depend on scripts. More than 99% of init scripts can be used without a modification.
>>23 In the dens of wretched villany in which I am most comfortable, I actually never come across anyone who supports systemd. I'm curious: as >>24 has pointed out, shell scripts are used for extensibility. How is this handled in systemd?