On Thu, 02 Jan 2014, Steve Langasek wrote: > our users. If we decide for systemd, what do you think is the right way to > mitigate such problems for jessie? Some of these issues are only going to > be seen once people start making use of systemd in anger with their existing > server configs (e.g., an ec2 VM with a simple disk and network config is not > going to expose these problems), and I don't really think we want to do this > by way of switching the default in unstable and waiting for the bugs to roll > in.
Why not? I have been happily using systemd on my laptops for multiple months now and while this probably doesn't cover some of the problems you expect in complex server environment, I fail to see why unstable integration would not be the right path forward. > Perhaps you're right that there is such a night and day difference between > systemd and upstart that it warrants us redoing the integration work on top > of systemd that has already been done on top of upstart in Ubuntu. But in > that case I would still want to know that, while redoing that integration, > we aren't leaving our users in the lurch. What users? It seems to me that the desktop case is not so problematic as to warrant special measure. The server case is not really concerned with unstable (most servers run stable). The real question is how to discover those potential bugs affecting servers precisely when those users are not using unstable? Cheers, -- Raphaël Hertzog ◈ Debian Developer Discover the Debian Administrator's Handbook: → http://debian-handbook.info/get/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
