Re: sysvinit is still here, and here to stay for jessie (was Re: systemd is here to stay, get over it now)

2014-07-05 Thread Gunnar Wolf
The Wanderer dijo [Thu, Jul 03, 2014 at 11:18:12PM -0400]: It must work without systemd well enough to be able to cleanly reboot the system from the GUI, after upgrading. Anything beyond that is nice-to-have, but definitely NOT required. I, for one, would be highly displeased if a

Re: sysvinit is still here, and here to stay for jessie (was Re: systemd is here to stay, get over it now)

2014-07-04 Thread Philip Hands
The Wanderer wande...@fastmail.fm writes: ... particularly because I use rather fewer things than many other people, and don't use most fancy GUI elements. (For example, I don't have a graphical power button at all; I shut down by exiting my window manager, logging out of the console where I

Re: sysvinit is still here, and here to stay for jessie (was Re: systemd is here to stay, get over it now)

2014-07-04 Thread Ondřej Surý
On Thu, Jul 3, 2014, at 16:59, Thorsten Glaser wrote: Besides, it’s not that the TC made a decision. Rather, the TC was split, and the chairman threw in his weight. This is absolutely not what I’d call a project(!) decision. No! The TC has made the decision with full adherence to Debian

Re: sysvinit is still here, and here to stay for jessie (was Re: systemd is here to stay, get over it now)

2014-07-04 Thread Didier 'OdyX' Raboud
That will be my last contribution to this pointless discussion. Le jeudi, 3 juillet 2014, 16.59:25 Thorsten Glaser a écrit : or without systemd btw). Given that the technical committee has made a decision which stayed unchallenged (so far), I've now come to think that No, there just has

Re: sysvinit is still here, and here to stay for jessie (was Re: systemd is here to stay, get over it now)

2014-07-04 Thread Rens Houben
In other news for Thu, Jul 03, 2014 at 04:59:25PM +0200, Thorsten Glaser has been seen typing: No, there just has not been any challenge that met the form and other requirements… and I am at a bit of loss at what to do here. Besides, it’s not that the TC made a decision. Rather, the TC was

Re: sysvinit is still here, and here to stay for jessie (was Re: systemd is here to stay, get over it now)

2014-07-04 Thread The Wanderer
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 07/04/2014 04:52 AM, Philip Hands wrote: The Wanderer wande...@fastmail.fm writes: ... particularly because I use rather fewer things than many other people, and don't use most fancy GUI elements. (For example, I don't have a graphical

Re: sysvinit is still here, and here to stay for jessie (was Re: systemd is here to stay, get over it now)

2014-07-04 Thread Adam Borowski
On Fri, Jul 04, 2014 at 09:52:07AM +0100, Philip Hands wrote: So, let me get this straight: You're saying that if, having decided to postpone rebooting after an upgrade where any reasonable person would expect to reboot This is Debian, not Windows or Red Hat, forced reboots are not

Re: sysvinit is still here, and here to stay for jessie (was Re: systemd is here to stay, get over it now)

2014-07-04 Thread Ondřej Surý
On Fri, Jul 4, 2014, at 16:42, Adam Borowski wrote: On Fri, Jul 04, 2014 at 09:52:07AM +0100, Philip Hands wrote: So, let me get this straight: You're saying that if, having decided to postpone rebooting after an upgrade where any reasonable person would expect to reboot This is

Re: sysvinit is still here, and here to stay for jessie (was Re: systemd is here to stay, get over it now)

2014-07-04 Thread The Wanderer
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 07/04/2014 10:42 AM, Adam Borowski wrote: On Fri, Jul 04, 2014 at 09:52:07AM +0100, Philip Hands wrote: So, let me get this straight: You're saying that if, having decided to postpone rebooting after an upgrade where any reasonable

Re: sysvinit is still here, and here to stay for jessie (was Re: systemd is here to stay, get over it now)

2014-07-04 Thread Matthias Urlichs
Hi, Adam Borowski: There was enough trouble when udev needed an in-lockstep upgrade with the kernel a few releases back. If systemd components are going to need such forced reboots on a repeated basis, I don't like where this is going. systemd and its components can re-exec themselves,

Re: sysvinit is still here, and here to stay for jessie (was Re: systemd is here to stay, get over it now)

2014-07-04 Thread Scott Kitterman
On Friday, July 04, 2014 17:28:05 Matthias Urlichs wrote: Hi, Adam Borowski: There was enough trouble when udev needed an in-lockstep upgrade with the kernel a few releases back. If systemd components are going to need such forced reboots on a repeated basis, I don't like where this is

Re: sysvinit is still here, and here to stay for jessie (was Re: systemd is here to stay, get over it now)

2014-07-04 Thread The Wanderer
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 07/04/2014 11:28 AM, Matthias Urlichs wrote: Hi, Adam Borowski: There was enough trouble when udev needed an in-lockstep upgrade with the kernel a few releases back. If systemd components are going to need such forced reboots on a

Re: sysvinit is still here, and here to stay for jessie (was Re: systemd is here to stay, get over it now)

2014-07-04 Thread Marco d'Itri
On Jul 04, The Wanderer wande...@fastmail.fm wrote: This part is precisely what I'm objecting to. I don't consider being expected to reboot *in order to maintain existing functionality* after an upgrade to be reasonable. Tough luck for you then, I fear that this is a perception issue. At the

Re: sysvinit is still here, and here to stay for jessie (was Re: systemd is here to stay, get over it now)

2014-07-04 Thread Jakub Wilk
* The Wanderer wande...@fastmail.fm, 2014-07-04, 12:00: Zurg (Jessie+1), Has that name actually been formalized in any way? No. But no worries, if RT chooses a different name, we'll have a GR to override them. :-P -- Jakub Wilk -- To UNSUBSCRIBE, email to

Re: sysvinit is still here, and here to stay for jessie (was Re: systemd is here to stay, get over it now)

2014-07-03 Thread Matthias Urlichs
Hi, Thorsten Glaser: A lot of Debian systems even run without dbus! Yeah. So? systemd doesn't force you to run a dbus daemon. No, there just has not been any challenge that met the form and other requirements… and I am at a bit of loss at what to do here. You get to do the same thing the

Re: sysvinit is still here, and here to stay for jessie (was Re: systemd is here to stay, get over it now)

2014-07-03 Thread The Wanderer
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 07/03/2014 01:40 PM, Matthias Urlichs wrote: Hi, Thorsten Glaser: Can we get over this now and start making Jessie the most awesome stable release we've ever prepared together? To do that, it MUST work without systemd, if alone for

Re: sysvinit is still here, and here to stay for jessie (was Re: systemd is here to stay, get over it now)

2014-07-03 Thread Russ Allbery
The Wanderer wande...@fastmail.fm writes: I, for one, would be highly displeased if a routine dist-upgrade to testing required me to reboot to avoid having things break. I generally dist-upgrade my primary computer to testing about once a week, give or take, but I don't reboot it more often

Re: sysvinit is still here, and here to stay for jessie (was Re: systemd is here to stay, get over it now)

2014-07-03 Thread Matthias Urlichs
Hi, The Wanderer: I, for one, would be highly displeased if a routine dist-upgrade to testing required me to reboot to avoid having things break. We're talking about an upgrade from one release to the other here, with many intrusive changes (not just systemd). If you do that upgrade not in

Re: sysvinit is still here, and here to stay for jessie (was Re: systemd is here to stay, get over it now)

2014-07-03 Thread The Wanderer
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 07/03/2014 11:53 PM, Russ Allbery wrote: The Wanderer wande...@fastmail.fm writes: I, for one, would be highly displeased if a routine dist-upgrade to testing required me to reboot to avoid having things break. I generally dist-upgrade