Bug#727708: Bits from linux.conf.au

[Adrian Bunk <bunk@stusta.de>]

On Mon, Jan 13, 2014 at 01:57:29PM -0700, Bdale Garbee wrote:
> Ian Jackson <ijackson@chiark.greenend.org.uk> writes:
> 
> > I'm coming round to the view that we should be planning to support
> > multiple systems indefinitely.
> 
> This has been my opinion all along.  Various assertions that it's
> somehow just too hard really haven't swayed me.  The tricky bit, I
> think, is to define just what "support" means in the context of
> non-default init systems.  

There are at least three tricky areas:

1. init systems will have to cope with packages supplying init scripts 
in several formats they support.

2. How to ensure that both systemd systems and non-systemd systems
work equally well?
If dependencies like "installing GNOME enforces systemd as init system"
would be legal, then after a few more such dependencies it would turn
out that systemd will be the only option available for virtually all 
users - and that all the hassle of supporting multiple init systems
was a waste of effort.

3. Switching init systems after installation.
Assume I am currently using systemd.
What is supposed to happen when I do "apt-get install sysvinit-core"?


> Bdale

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed