On Thu, Jan 07, 2021 at 01:27:25PM +0100, Thomas Zimmermann wrote:
Hi
Am 07.01.21 um 13:12 schrieb Johannes Meixner:
Hello,
Happy New Year!
On 2021-01-05 17:03, Ludwig Nussel wrote:
https://github.com/lnussel/lnussel.github.io/blob/fs/_posts/2020-12-16-fslay...
I am really not an expert in this area but as far as I see you basically propose a new filesystem hierarchy that is different than the Filesystem Hierarchy Standard (FHS).
But you use the same directory names as in the old FHS. My gutt feeling is that this won't work in practice.
I think different things should have different names to be able to distinguish them and to have easier backward compatibility (old names mean the old stuff and new names mean the new one).
So I think a new filesystem hierarchy should use new names and then new directory names could be even comprehensible (what the heck does 'usr' mean and why does 'etc' mean "config").
E.g. names that tell the purpose, for example something like /os (or more explanatory /operating_system) /boot (or more explanatory /bootloader) /conf (or more explanatory /admin_config) /data (or more explanatory /system_data) /user (or more explanatory /user_data) /temp (or more explanatory /run_time_data) /apps (or more explanatory /applications)
Please, no. This reinvents names for no good reason, and breaks muscle memory. There is a good reason: readability.
If you are not bound by any standard the TLAs used in directory names are ridiculous. You can always add compatibility symlinks if you are so inclined. Thanks Michal
Best regards Thomas
...
Then step by thep things could be moved from FHS directories to the new ones and when (after some years) nothing uses the old FHS directories they can be dropped.
Kind Regards Johannes Meixner
-- Thomas Zimmermann Graphics Driver Developer SUSE Software Solutions Germany GmbH Maxfeldstr. 5, 90409 Nürnberg, Germany (HRB 36809, AG Nürnberg) Geschäftsführer: Felix Imendörffer