[lixquid]

Isn't that the whole point of this post though? They've allowed you to edit files marked as "system files" despite a multitude of warnings, and now so many people have fucked up doing so that they've issued a stronger warning.

What's the solution? Put less warnings? Then you'd get even more people destroying their data. Put more warnings? Then you'd get more people complaining that "Windows doesn't let you edit what you want!".

It doesn't really seem like they can win.

[vacri]

I'm more talking about the culture between the two types of OS than this specific occurrence. The whole attitude of "well, why the fuck were you in there anyway?" is not something I've encountered in *nix.

[Karunamon]

Windows at least has the decency to warn you that you're about ready to trash something. Every -nix ever will let me blow /sbin/init away with a carelessly placed file operation without so much as a "hey".

Uneducated users should be responded to with "WTF were you doing?" as computer is a precision machine and it is not unreasonable to expect some basic level of literacy.

[vacri]

    vacri@thingy:~$ rm /sbin/init
    rm: cannot remove ‘/sbin/init’: Permission denied

I don't seem to be able to blow away /sbin/init.

If I've elevated myself to be a global administrative user, then I should be able to do global administrative things, without being treated as an 'uneducated user'.

> it is not unreasonable to expect some basic level of literacy

I think it's perfectly reasonable to expect some level of literacy for administrative-level tasks, and that's what nix does.