Is there some detailed notes on why upstart is still used for user
sessions instead of systemd? Is it just lack of time or there are some
technical reasons not to switch to systemd here as well?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
gravy45, this sounds like bug 953875 (or similar). Please file a new
bug, this is unrelated to this FFE and doesn't affect all installations
(i. e. it's specific to your system).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
The previous post is where it sits for about 30 seconds or so. Here is
another screenshot.
** Attachment added: Screenshot-2.png
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1427654/+attachment/4357544/+files/Screenshot-2.png
--
You received this bug notification because you
Switching to systemd for Ubuntu MATE 15.04 (Beta 2) seems to have
resulted in extended boot time in a Virtualbox guest (approximately 45
seconds longer).
** Attachment added: Screenshot-1.png
As stated on the mailing list few months ago
(https://lists.ubuntu.com/archives/ubuntu-devel-
discuss/2014-December/015154.html), Ubuntu never offered a choice of
init system, and won't start doing that. systemd is mandatory to be the
supported ubuntu path. That's the reason why ubuntu-standard
See also bug 1399766. I guess the question is whether having a non-
systemd installation is going to be supported and I hope the answer will
be yes.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to init-system-helpers in
would it be possible to have ubuntu-standard depend on systemd|upstart
instead of systemd only? I'd like to avoid systemd while having ubuntu-
standard installed for a fully supported system.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
Being able to run a script like this over SSH:
apt-get -y remove openssh-server
shutdown -h now
Can be extremely useful in automation tooling, but the switch to systemd
breaks this:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1429938
--
You received this bug notification because
This bug was fixed in the package init-system-helpers - 1.22ubuntu4
---
init-system-helpers (1.22ubuntu4) vivid; urgency=medium
* init: Switch preferred alternative to systemd, and update package
description to make sense for Ubuntu. (LP: #1427654)
-- Martin Pitt
This bug was fixed in the package ubuntu-meta - 1.332
---
ubuntu-meta (1.332) vivid; urgency=medium
* Refreshed dependencies
* Added systemd-sysv to standard (LP: #1427654)
-- Martin Pitt martin.p...@ubuntu.com Mon, 09 Mar 2015 06:20:44 +0100
** Changed in: ubuntu-meta
** Changed in: init-system-helpers (Ubuntu Vivid)
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to init-system-helpers in
Ubuntu.
https://bugs.launchpad.net/bugs/1427654
Title:
** Branch linked: lp:ubuntu/vivid-proposed/init-system-helpers
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to init-system-helpers in
Ubuntu.
https://bugs.launchpad.net/bugs/1427654
Title:
FFE: switch system init to
** Branch linked: lp:~ubuntu-core-dev/ubuntu-seeds/platform.vivid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to init-system-helpers in
Ubuntu.
https://bugs.launchpad.net/bugs/1427654
Title:
FFE: switch system init to
** Branch linked: lp:ubuntu/vivid-proposed/ubuntu-meta
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to init-system-helpers in
Ubuntu.
https://bugs.launchpad.net/bugs/1427654
Title:
FFE: switch system init to systemd [not
** Changed in: ubuntu-meta (Ubuntu Vivid)
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to init-system-helpers in
Ubuntu.
https://bugs.launchpad.net/bugs/1427654
Title:
FFE: switch
** Changed in: ubuntu-meta (Ubuntu Vivid)
Status: Confirmed = In Progress
** Changed in: ubuntu-meta (Ubuntu Vivid)
Assignee: (unassigned) = Martin Pitt (pitti)
** Also affects: init-system-helpers (Ubuntu)
Importance: Undecided
Status: New
** Changed in:
Filed a bug on apache2 where stop; start on systemd fails:
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1428796
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to init-system-helpers in
Ubuntu.
Pursuant to many conversations on the topic, this is a formal approval
of the FFe, with an assumption that it will land early in the week of
March 9th.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
** Changed in: ubuntu-meta (Ubuntu Vivid)
Milestone: None = ubuntu-15.03
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1427654
Title:
FFE: switch system init to
I just downloaded today's lubuntu desktop, did an ubiquity install under
it (boot the live system with init=/bin/systemd), and also tested the
installed system under systemd. No problems encountered.
** Description changed:
As per
** Description changed:
As per https://blueprints.launchpad.net/ubuntu/+spec/core-1411-systemd-
migration we aimed for switching the system (not session) init from
upstart to systemd this cycle. As this was by and large a 1.2 man show,
this took a little longer. One of the remaining
** Description changed:
As per https://blueprints.launchpad.net/ubuntu/+spec/core-1411-systemd-
migration we aimed for switching the system (not session) init from
upstart to systemd this cycle. As this was by and large a 1.2 man show,
this took a little longer. One of the remaining
** Description changed:
As per https://blueprints.launchpad.net/ubuntu/+spec/core-1411-systemd-
migration we aimed for switching the system (not session) init from
upstart to systemd this cycle. As this was by and large a 1.2 man show,
this took a little longer. One of the remaining
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ubuntu-meta (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
I got confirmation from Xubuntu (Unit193) and MATE (Martin Wimpress)
that switching to systemd works fine and is OK for them. I mailed Julien
for Lubuntu.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
25 matches
Mail list logo
