this post was submitted on 29 Jan 2026
17 points (90.5% liked)

linux4noobs

3498 readers
21 users here now

linux4noobs


Noob Friendly, Expert Enabling

Whether you're a seasoned pro or the noobiest of noobs, you've found the right place for Linux support and information. With a dedication to supporting free and open source software, this community aims to ensure Linux fits your needs and works for you. From troubleshooting to tutorials, practical tips, news and more, all aspects of Linux are warmly welcomed. Join a community of like-minded enthusiasts and professionals driving Linux's ongoing evolution.


Seeking Support?

Community Rules

founded 2 years ago
MODERATORS
 

One point of user-hostility you face when configuring Linux is all the config files in /etc. Be it crontab, fstab, or iptables, every project has its own ad-hoc config file format and as a rookie user you're left guessing what the rules for editing each one are. Must you separate entries with tabs or can it be spaces? Does the number of tabs matter? Does this file use # to comment or ;? Can you put a space after = or would that become part of the string? Some projects use their own half-baked implementation of .INI that breaks down the moment you try to escape a string. What's worse is that since it's background processes whose files you are editing, the response to a syntax error is nothing happening. The way to test whether you guessed the rules right is to wait and see 🤷

What I'm trying to say is that IMHO, the Linux Kernel and surrounding utilities should agree on a widespread, standardized config format and all migrate to it (prefarably sharing the same C library). The obvious option would be JSON, although it feels a little clunky and doesn't officially support comments. My preference would be TOML, since it's like INI which many projects kinda use already, but it's standardized and has native support for things like arrays (especially useful for fstab/crontab).

you are viewing a single comment's thread
view the rest of the comments
[–] SubArcticTundra@lemmy.ml 2 points 1 day ago* (last edited 1 day ago) (1 children)

As a newbee to Linux (I guess, a lot in EU want to switch to Linux nowadays) it is really hard to learn which config file will how be used for which tool.

Yep

Are there any tools around to create config files easier?

Hmm, I don't know what you mean by 'tools for creating config files'... If you don't want to have to type the syntax of config files manually then there are programs like DConf Editor, which in an ideal world all the system settings would fall under. But the files that I'm talking about are specifically those that haven't been moved to use DConf for whatever reason.

[–] sloelk@piefed.social 1 points 6 hours ago

ok, I look into DConf. maybe this helps.

But I get it, that the most projects because of no or not much income, can’t jump onto this to improve their tools. Whereas I think usability is a big big feature for most people. Mostly better a low feature set easy to use instead of a big feature set which are not much people can use.