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

To: debian-devel@lists.debian.org
Subject: Re: sysvinit is still here, and here to stay for jessie (was Re: systemd is here to stay, get over it now)
From: Adam Borowski <kilobyte@angband.pl>
Date: Fri, 4 Jul 2014 16:42:28 +0200
Message-id: <[🔎] 20140704144228.GA10058@angband.pl>
In-reply-to: <[🔎] 87y4w9o6a0.fsf@poker.hands.com>
References: <[🔎] 20140703110025.GB23801@smurf.noris.de> <[🔎] lp3fgb$36o$1@ger.gmane.org> <[🔎] 87ioney6pj.wl.jch@pps.univ-paris-diderot.fr> <[🔎] 2607970.5pBmWMVp2E@gyllingar> <[🔎] alpine.DEB.2.11.1407031652560.4173@tglase.lan.tarent.de> <[🔎] 20140703174017.GD23801@smurf.noris.de> <[🔎] 53B61CF4.6010800@fastmail.fm> <[🔎] 87iondpyo9.fsf@windlord.stanford.edu> <[🔎] 53B62C8D.5010005@fastmail.fm> <[🔎] 87y4w9o6a0.fsf@poker.hands.com>

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 acceptable.

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.

-- 
Gnome 3, Windows 8, Slashdot Beta, now Firefox Ribbon^WAustralis.  WTF is going
on with replacing usable interfaces with tabletized ones?

Reply to:

Follow-Ups:
- Re: sysvinit is still here, and here to stay for jessie (was Re: systemd is here to stay, get over it now)
  - From: Ondřej Surý <ondrej@sury.org>
- Re: sysvinit is still here, and here to stay for jessie (was Re: systemd is here to stay, get over it now)
  - From: The Wanderer <wanderer@fastmail.fm>
- Re: sysvinit is still here, and here to stay for jessie (was Re: systemd is here to stay, get over it now)
  - From: Matthias Urlichs <matthias@urlichs.de>

References:
- Re: Pinning vs. conflicting
  - From: Matthias Urlichs <matthias@urlichs.de>
- Re: Pinning vs. conflicting
  - From: Thorsten Glaser <tg@debian.org>
- Re: Pinning vs. conflicting
  - From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
- systemd is here to stay, get over it now (was: Re: Pinning vs. conflicting)
  - From: "Didier 'OdyX' Raboud" <odyx@debian.org>
- sysvinit is still here, and here to stay for jessie (was Re: systemd is here to stay, get over it now)
  - From: Thorsten Glaser <tg@debian.org>
- Re: sysvinit is still here, and here to stay for jessie (was Re: systemd is here to stay, get over it now)
  - From: Matthias Urlichs <matthias@urlichs.de>
- Re: sysvinit is still here, and here to stay for jessie (was Re: systemd is here to stay, get over it now)
  - From: The Wanderer <wanderer@fastmail.fm>
- Re: sysvinit is still here, and here to stay for jessie (was Re: systemd is here to stay, get over it now)
  - From: Russ Allbery <rra@debian.org>
- Re: sysvinit is still here, and here to stay for jessie (was Re: systemd is here to stay, get over it now)
  - From: The Wanderer <wanderer@fastmail.fm>
- Re: sysvinit is still here, and here to stay for jessie (was Re: systemd is here to stay, get over it now)
  - From: Philip Hands <phil@hands.com>

Prev by Date: GR - collecting proposals (was Re: systemd is here to stay, get over it now)
Next by Date: Re: sysvinit is still here, and here to stay for jessie (was Re: systemd is here to stay, get over it now)
Previous by thread: Re: sysvinit is still here, and here to stay for jessie (was Re: systemd is here to stay, get over it now)
Next by thread: Re: sysvinit is still here, and here to stay for jessie (was Re: systemd is here to stay, get over it now)
Index(es):
- Date
- Thread