On Thu, 18 Sep 2014 10:53:21 +0100 Brian <a...@cityscape.co.uk> wrote:
> On Thu 18 Sep 2014 at 09:44:49 +0100, Joe wrote: > > > > > So we're looking for some kind of direction here, hoping that > > someone who actually knows for sure will tell us whether the use of > > systemd as init will be completely unavoidable in future Debian > > releases. If not, if it will only be the 'default', then it may be > > worth putting a bit of effort into making an alternative practical. > > For anyone intending to install Jessie, which is the only thing which > matters for Debian and the immediate future, the practical > alternatives and direction to take have been described many times > over the past few months. In fact, in the last few days: > > > https://lists.debian.org/12092014224057.ff13b66f7...@desktop.copernicus.demon.co.uk > > https://lists.debian.org/17092014175756.ef88cea78...@desktop.copernicus.demon.co.uk > > You definitely need to > do: > apt-get install > sysvinit-core > In addition you may also choose to > do: apt-get install > systemd-shim > if you decide your installation needs it. > > Yes, this is understood, but is it the final word? We have a 'technology preview' of systemd in Wheezy, it will be the default in Jessie. Will it remain the default in the forseeable future or is it expected to become mandatory in a later release? I'm aware that nothing can possibly be set in stone yet, but the people responsible for systemd-shim and other compatibility components must have a fair idea whether these are intended as temporary workarounds until 'all' packages are compatible with systemd, or whether they are expected to remain permanent parts of Debian. -- Joe -- JRE Trading Ltd Registered in England and Wales No.3558355 Registered Address: 50 Cranham Road RM11 2AA VAT Registration GB 420118116 -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140918170402.00000...@jretrading.com
