El 21/7/25 a las 20:10, Dale escribió:
At first, I wasn't to big on the idea of directories instead of files. My thinking, one file, one place to look. If you have a setting for some option, it was in one file and you looked in that one file. Then directories came along. I tried it. I realized that when I want to set something temporary, I can name the file as to what is in it. That way I know where to look. When I want to remove that option, I just move or delete that file. For example, with this system setting to disable IPv6, I named the file with IP and disable. In this case, I can just remove the .conf part or add .old to the file name and it is no longer read. I hope at some point, my VPN will support IPv6 and I can enable it again. I guess for some things, files are better. For some things, directories are better. Some depends on the use case and some on personal thinking. Either way, usually either will work so use what suites you best. Just glad to get this set so that it disables IPv6 but I can enable it again pretty easy. Dale :-) :-)
I agree with you, but I suppose that from the maintainer point of view is better to get ordered, a lot of tiny files better than one big big file that could be unmaintanable.
It's something like programming, better having a lot of source files than get one of one million lines of code...
OpenPGP_0x57E64E0B7FC3BEDF.asc
Description: OpenPGP public key
OpenPGP_signature.asc
Description: OpenPGP digital signature
