You are not logged in.
Hello
I am new here, thank you for having me ![]()
I am pretty sure it does not exist, but I would love to have a map of the basic directory structure of a functional Arch OS.
The structure that allows all the hardware to function as expected.
It would serve as a roadmap in this jungle of, for me, new concepts.
The biggest issue for learning I find is that there are many ways to do things and if one tries them out one leaves traces everywhere in the system. It becomes messy like that and I would like to clean it up. Yet I got to be careful not to break things.
I learn a lot but it's also a mess.
A map would do wonders. I could then delete anything that is redundant/useless and make sure that everything that needs to be there will be there (but also not more than that)
Any chance anyone has made such a map of his/hers working setup for fun and would want to share it with me?
Thank you!
Regards
afriaen
Offline
The structure that allows all the hardware to function as expected.
That requirement is not simple to fulfill. All hardware covers a massive amount. Some just needs a kernel module from the linux package, may also require firmware a lot of which is contained in linux-firmware.
Beyond that you may need to build a kernel module from AUR or there may be no driver in existence.
You also have tools to control the hardware such numerous Network managers.
For untracked system files see Tips_and_tricks#Identify_files_not_owned_by_any_package
For untracked user files, I would suggest using a temporary user for experiments.
Offline