[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Installing an Alternative Init?



On 11/11/2014 02:16 PM, Brian wrote:
On Tue 11 Nov 2014 at 12:36:14 -0500, Marty wrote:

On 11/11/2014 12:07 PM, Laurent Bigonville wrote:
>
>There are no functional differences between an installation with
>sysvinit-core out of the box or an install where sysvinit-core is
>installed later, this is a fact.
>
>Allowing the user to choose this at install time from the interface is
>a "nice to have" feature (wishlist bug) not a RC bug like you were
>claiming earlier.

There is a potential practical consequence of not advertising an
init alternative during setup. It makes users less likely to be
aware of it, or even aware that the init system has changed.

New users do not need to be be aware of all the background to the
choosing of a default init. No advertisement is needed. By definition,
they do not care. They want Debian. Please let them have it.

They will not care "by definition" only if they are not aware of the change, and most won't be aware unless they are informed during the installation.

They won't know they lost the choice they didn't know they had. Capisce?

What choice have they lost?

They lost an *informed* choice. I think the installation program should not take sides but just inform the user. A choice that the user is not aware of is the same as no choice, and is potentially coercive and disrespectful. It makes Debian seem partial to Red Hat's business plan to take over the Linux ecosystem.

 Whatever it was, it didn't exist as you imply
in Wheezy.

It wasn't an issue in Wheezy because the default init option had not changed from the previous release, and any release before that.

They won't know, that is, until it bites them somewhere down the
line. Then they won't know where to look or who to blame, and will
blame Debian.

What bites them?

Individually, probably something that requires sysvinit or one many core services that got replaced. Collectively, getting trapped by vendor lock-in.

In both cases it could be the result of users being steered to the default init by the installation program, leaving alternatives to rot.


Installation time may be only means that most users (like me*) ever
would learn about it.

* Install instructions? We don't need no stinkin' instructions

Reading? You are right. Who wants it? Just spew out nonsense and hope
nobody notices.

Isn't that where the dumbed-down install is headed? Don't worry about the details silly, Windows tells you when it's time to reboot.


Reply to: