In debian conference , systemd topic was discussed , and in his point of view the current init system of wheezy and distros before that one could be fixed and speed up the process , but the guys from systemd did it first but changed all the way the init system works and not much people knows how the process is done , and this is not good .https://www.youtube.com/watch?v=c80yIJQJO8s
Why would installing prebuilt kernel deb packages bring in anything to do with systemd?
You dont break systemd using "apt-get" , you may break systemd if you install something from source code that requires more older libraries than the ones that systemd needs to work .
My friend , on my wheezy distro i do not do "apt-get install linux-headers-$(uname -r)" , and after all i dont even have on my sources.list the jessie repositories .
If i need to install some new kernel for some reason then i compile it from source , by getting the source code at kernel.org .
But since my hardware is working fine then i do not need to install some recent kernel .
By default new kernels have more drivers for new hardwares , you can install a new kernel to fix your driver issue , or you can build the driver from source and install it in your current kernel .
Prebuilt packages on apt repository is just to avoid the user to compile every update from every lib or tool from source code , and this is the reason why exists .
This next video shows the creators of systemd explaining it , and at first look it seems pratical , systemd uses less memory , when you kill a process in systemd , the service will kill everything connected to that process , witch in sometimes could be good or bad depending on what you are working .
Most of the detailed configurations of services were removed by systemd , a good example on the next video is the tftp example , where in system V (wheezy) you can setup the port on the daemon configuration , but on systemd you must make that change in the program configuration file .
One of the things that bothers me most is the way we start services with systemd and create services , witch was changed from top to bottom .
I agree that systemd have many good things , but a drastic change from an OS to another is complicated for users to adapt to new commands or even know their names .
Systemd will only be "the best" thing in 10 years , but in 10 years someone create anything better than systemd and change again everything how the init system works and how things must be configured , and it will be again a start from beginning .
A person that did not knew how sys V and start for the first time in systemd in linux it is just fine , but for someone that is already use to sys V and change to systemd "just like that" is complicated , and even when errors appear and we need to fix them , if you knew how to fix that particular error in Sys V , forget it because it will not work in systemd the same way .
They could do something more similar to old system in the way we interact with the OS on systemd commands .
These are some of the reasons i have debian 8 on 1 of my servers , but i rarely touch it (to not break things) , because the machine where i like to work and know how to deal with its problems it is a wheezy distro of debian , and witch i will not upgrade to jessie , and when wheezy repositories stop be updated , what i have to do is to do everything manually from source code , but since this wheezy machine is not exposed to the web , then i do not need to worry much about vulnerabilities except (web browser and plugins) , and these 2 i can do the upgrades manually without any issue .
After all i have a very tight iptables config that even if some intruder get to my hardware firewall , very difficulty will have to check any open port on the OS to get in .https://www.youtube.com/watch?v=S9YmaNuvw5U
a good solution to new users on systemd that arrived from sys v , is doing what i did for tar commands .
Everytime i wanted to extract some tar file with some different extention i needed to go to web to found the correct switches to apply , so , sick of going to web everyday , what i did was a batch file called "tarhelp" witch contains a bunch of "echo" lines with the switches i need to use for every type of extension i get in tar files .
Now when i need to extract a tar file on terminal , i call on shell "tarhelp" and it shows how i must do to that type of help .
Now if we apply this technique to systemd like "systemdhelp" , everytime we need to do anything on OS that interacts with systemd , like start a service or whatever , we call "systemdhelp" the batch file popup with the instructions .
It is simple and never breaks until you erase your partition and forget to copy that help file to somewhere so you can put it on your new installed linux os /usr/local/bin or sbin .