4 ms·
> Second, I dare you to run "ls /etc" and claim it's not a mess... In principle, sure. But in practice, using /etc to edit configuration data is not that hard,
by OskarS 4y ago
> Second, I dare you to run "ls /etc" and claim it's not a mess...
In principle, sure. But in practice, using /etc to edit configuration data is not that hard, and every Linux user does it all the time. Different software uses different configuration formats, sure (though it's worth nothing that NixOS is doing really clever things to solve that problem), but it's really not that hard or scary.
Manually editing the registry though... That way lies madness. It's much scarier and it's much more fragile.
- izacus 4y ago> Manually editing the registry though... That way lies madness. It's much scarier and it's much more fragile. How... exactly? There's no way to create a syntax error as trivial as you can in config files. How is using regedit or powershell commands more fragile (I understand "scarier" in a way everything you're not used to is scary).
- cycomanic 4y agoWell the article points to a way of preventing following entries to be read by having an entry in non alphabetical order. But how often have you ran into syntax errors for system configuration files in Linux? I can't say that this has been much of an issue in my experience.
- dwattttt 4y agoStart making raw edits directly to an ext4 disk rather than using published libs/APIs, and you'll soon find some new horrors to be scared about.
- magicalhippo 4y agoThat's because the article is about doing binary edits to to the registry files themselves, something no application or user should ever do. Instead changes should be done through the API or the regedit program.