On 09/09/14 22:18, Tollef Fog Heen wrote: > ]] Carlos Alberto Lopez Perez > >> But if you don't (Is not uncommon to have servers on remote locations >> that are only accessible via ssh) and the machine don't boots properly >> you can find yourself in trouble. > > Then surely you test the upgrade before making it live, using kvm > -snapshot or similar functionality? > That way of testing is completely unreliable when we are talking about low level stuff (kernel/udev/systemd). I'm talking about physical (bare-metal) servers. Testing the upgrade on a virtual machine does not help since the behavior of the system is hardware dependent, and kvm can't reproduce that. In any case, I'm not worried by the servers I manage. I know the current status quo is to replace sysvinit with systemd on upgrades without telling the user. So I'm ready to pin sysvinit if I think is a wiser choice. What I'm trying to improve is the experience of the Debian users that won't know that, and will upgrade their servers from Wheezy to Jessie. I truly believe that making systemd the default without asking the user to test it first, is going to cause more breakage and angry users than doing it the other way.
Attachment:
signature.asc
Description: OpenPGP digital signature