Hi,

The argument of those who support protecting the hardware against a
probable breakage are logically sound: I support them.

Let us look at it differently and let us consider the switching power
supply that supplies stable voltages to the various circuits of a
computer.

Would anyone agree that design engineers do not prevent any
possibility in the negative feedback loops and pulsewidth modulation
circuitry, to safeguard against voltage outputs that are harmful to
the hardware?

Then, why on Flat Earth should anyone accept that software should NOT
be prevented from damaging hardware?

Now, I am waiting for the usual counter pseudo-argument, namely, that
this is another scenario that has nothing to do with the subject being
discussed.

Oh, I have wasted enough of my time.

Edward


On 05/02/2016, Rainer H. Rauschenberg <rainerh@???> wrote:
> On Thu, 4 Feb 2016, Simon Hobson wrote:
>
>> Yes, in an ideal world where everyone is a "full time admin". But in the
>> real world, more systems are used by "average users" who just expect
>> "stuff to work". So IMO, you either build stuff that works (or at least
>> is up-front about what's wrong), or you leave these people stuck with
>> "stuff that's broken" and regardless of how right you are, the pi**ed
>> off user will be moaning about how "rubbish and complicated this Linux
>> is - best go back to Windows".
>
> I think this is the road that led to systemd -- if you think Linux needs
> to be "as easy as Windows" you tend to take away all the aspects that made
> it superior (in my view).
>
> Most of the people in the Linux community who shout so loud focus on this
> kind of target, so devuan better should focus on the people who want less
> automagic and more control.
>
> Besides that I don't think mounting EFI-vars r/w is a good idea as a
> system default and I don't think the user not having read all the
> relevant documentation (spread out over various places) is to blame when
> system behaviour *changes* in such a drastic way (bricking hardware by
> deleting "files").
> _______________________________________________
> Dng mailing list
> Dng@???
> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
>