On 29.11.2014 19:15, Svante Signell wrote:
> Since there is no interest in adding a debconf message on new installs,
> I wish for a menu entry in the advanced part of the installer to be able
> to install a new system with sysvinit-core or upstart!
+1
--
mit freundlichen Grüßen
--
Enrico Wei
On Fri, 2014-11-28 at 12:56 +0100, Svante Signell wrote:
> Hello,
> In summary:
> a) Upgrades should _not_ change init: whatever is installed should be
> kept.
> b) New installs should get systemd-sysv as default init with a debconf
> message about alternative init systems.
>
> More detailed:
> 1
* Darren Salt [141130 14:17]:
> I demand that Stephan Seitz may or may not have written...
>
> > On Fri, Nov 28, 2014 at 02:41:23PM +0100, Marco d'Itri wrote:
> >> On Nov 28, Svante Signell wrote:
> >>> a) Upgrades should _not_ change init: whatever is installed should be
> >>> kept.
> >> I disa
I demand that Stephan Seitz may or may not have written...
> On Fri, Nov 28, 2014 at 02:41:23PM +0100, Marco d'Itri wrote:
>> On Nov 28, Svante Signell wrote:
>>> a) Upgrades should _not_ change init: whatever is installed should be
>>> kept.
>> I disagree: upgrades should get the default init sy
One claim is changed, see below.
On Fri, 2014-11-28 at 12:56 +0100, Svante Signell wrote:
> Hello,
> In summary:
> a) Upgrades should _not_ change init: whatever is installed should be
> kept.
> b) New installs should get systemd-sysv as default init with a debconf
> message about alternative ini
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
Am 28.11.2014 15:55, schrieb Marco d'Itri:
> > I have a system where the network connection is so important that the pppd
> > is invoked via the
inittab, which is a published interface of the init system and has been
for decades. When an upgrade
Matthias Urlichs writes:
> Non-standard inittab entries should surely be displayed and warned about,
> but IMHO that's not sufficient reason to not switch the other 99.99%
> who never touched their inittab.
In the server world, I'm pretty sure you are significantly underestimating
the number of
On Fri, 28 Nov 2014, Stephan Seitz wrote:
> On Fri, Nov 28, 2014 at 04:00:42PM +0100, Thorsten Glaser wrote:
> > On Fri, 28 Nov 2014, Stephan Seitz wrote:
> > > Of course not. syslog-ng was not replaced by rsyslog when Debian changed
> > > the default syslog.
> > Note that syslog-ng was not the de
On Fri, Nov 28, 2014 at 04:00:42PM +0100, Thorsten Glaser wrote:
On Fri, 28 Nov 2014, Stephan Seitz wrote:
Of course not. syslog-ng was not replaced by rsyslog when Debian
changed the default syslog.
Note that syslog-ng was not the default, but sysklogd (which was)
wasn’t replaced either. Thank
On Fri, 28 Nov 2014, Stephan Seitz wrote:
> Of course not. syslog-ng was not replaced by rsyslog when Debian changed the
> default syslog.
Note that syslog-ng was not the default, but sysklogd (which was)
wasn’t replaced either. Thankfully.
> The grub1 bootloader was not replaced when Debian cha
On Nov 28, Simon Richter wrote:
> I disagree: This is not safe and can break systems.
Everything is not safe and can break systems, so this is not a very
compelling argument.
> I have a system where the network connection is so important that the
> pppd is invoked via the inittab, which is a pu
On Fri, Nov 28, 2014 at 03:24:18PM +0100, Thorsten Glaser wrote:
> On Fri, 28 Nov 2014, Ansgar Burchardt wrote:
>
> > No, the ctte did not say that. We had a flamewar about that
> > interpretation before.
>
> That was almost word by word from
> https://lists.debian.org/debian-devel-announce/2014/
On 11/28/2014 03:24 PM, Thorsten Glaser wrote:
> On Fri, 28 Nov 2014, Ansgar Burchardt wrote:
>> No, the ctte did not say that. We had a flamewar about that
>> interpretation before.
>
> That was almost word by word from
> https://lists.debian.org/debian-devel-announce/2014/11/msg0.html
See [
On Fri, Nov 28, 2014 at 02:41:23PM +0100, Marco d'Itri wrote:
On Nov 28, Svante Signell wrote:
a) Upgrades should _not_ change init: whatever is installed should be
kept.
I disagree: upgrades should get the default init system unless the
system administrator chooses otherwise.
Of course not.
On Fri, 28 Nov 2014, Ansgar Burchardt wrote:
> No, the ctte did not say that. We had a flamewar about that
> interpretation before.
That was almost word by word from
https://lists.debian.org/debian-devel-announce/2014/11/msg0.html
bye,
//mirabilos
--
>> Why don't you use JavaScript? I also
On 11/28/2014 03:16 PM, Thorsten Glaser wrote:
> On Fri, 28 Nov 2014, Marco d'Itri wrote:
>> I disagree: upgrades should get the default init system unless the
>> system administrator chooses otherwise.
>
> I disagree with you, and so does CTTE, this time: they said
> that existing installations
Hi,
Simon Richter:
> I have a system where the network connection is so important that the
> pppd is invoked via the inittab, which is a published interface of the
> init system and has been for decades. When an upgrade installs
> systemd, this machine will simply drop off the network.
>
> Other
On Fri, 28 Nov 2014, Marco d'Itri wrote:
> On Nov 28, Svante Signell wrote:
>
> > a) Upgrades should _not_ change init: whatever is installed should be
> > kept.
> I disagree: upgrades should get the default init system unless the
> system administrator chooses otherwise.
I disagree with you,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
On 28.11.2014 14:41, Marco d'Itri wrote:
>> a) Upgrades should _not_ change init: whatever is installed
>> should be kept.
> I disagree: upgrades should get the default init system unless the
> system administrator chooses otherwise.
I disagre
On 2014-11-28 14:41, Marco d'Itri wrote:
> On Nov 28, Svante Signell wrote:
>
> [...]
>> b) New installs should get systemd-sysv as default init with a debconf
>> message about alternative init systems.
> It would be totally unacceptable to waste the time of every Debian user
> with pointless ad
On 28/11/14 11:56, Svante Signell wrote:
3) Add information in release-notes on how to:
- Upgrade from stable/testing/sid to jessie to avoid getting
systemd-sysv installed (this should not strictly be needed if the ctte
chooses to decide that upgrades will _not_ switch init)
This part has alrea
On Nov 28, Svante Signell wrote:
> a) Upgrades should _not_ change init: whatever is installed should be
> kept.
I disagree: upgrades should get the default init system unless the
system administrator chooses otherwise.
> b) New installs should get systemd-sysv as default init with a debconf
>
On Fri, 28 Nov 2014, Svante Signell wrote:
> the order of pre-depends for int init package should change from
> Pre-Depends: systemd-sysv | sysvinit-core | upstart
> to
> Pre-Depends: sysvinit-core | systemd-sysv | upstart
That would probably require changes in d-i to ensure that
systemd is, inde
23 matches
Mail list logo
