folder structure
from stackoverflow
I like to prefix symbols to folders and files when I'm working in a file tree. Those symbols are {_,-,!,`,+}
. Apple's macOS Finder will sort a directories files by the File name, starting with the first character: these non-letter character allow sorting by a persistent file property rather than Finder's other, more malleable, options such as File Size or Date Modified, Additionally this doesnt modify the meaning of the name. Each of these prefixes are an operation on a name, each with different meanings:
_ a directory which holds fundamental files, README's Licenses, other crucial user files.
Dont use it too often, generally just when I'm sharing with other parties
-
this is a development top level directory and holds a mixture of file types` reserved for a file that is currently being worked
! for a file that I'm working on but have to leave
+ directory with a single filetype but is still being used for references
https://www.youtube.com/watch?v=HbgzrKJvDRw
linux follows unix tradition so backslashses are used and capitalization make filenames unique
FHS filesystem heirarchy standard
bin
binaries needed for single user mode or booting as rootsbin
system binaries mean for adminboot
all the things that are needed for bootloadersdev
where devices lives and all hardwareetc
et cetera or if a menonic edit to configurelib
32 and 64 where libaries live which are referned by biaries in bin and sbinmnt
other mounted drivesmedia
is an offshoot let linux worry about mediaopt
optional folder where manually installed can be putproc
or processes or pseudo files are shown by the kernel process named after pidroot
root users home folder and need special permissionsrun
newer which are used to store ram processessrv
server folder which are mounted usually emptysys
is systemtmp
temporaryvar
variable directory which are added such as logs and database kind of folderhome
Last updated