Comments by "Cestarian Inhabitant" (@cestarianinhabitant5898) on "Структура файловой системы Linux!" video.

  1. 18
  2. Feel like you should have mentioned some things, like how the lib equivalent on windows is C:\Windows\System which can be used to host .dll (dynamically linked library) files which are the primary format windows uses for libraries. On windows those dll files are always either buried somewhere in C:\Windows or shipped with the program that uses them on an individual basis, whereas on Linux, in general, all software refers to the lib/lib32/lib64 directories to find their library files which has some notable pros and cons over the windows method. Also, in /boot you didn't explain what bootloader is, which is the same as 'bootmgr' in windows; it allows the bios to detect that there is an operating system on a hard drive when it attempts to boot it. Also in /boot is the actual linux kernel. Apt was possibly not the best example for a program that requires system-wide configuration. Xorg, Alsa, Pulse or Systemd all would have made somewhat better choices probably. A really quick way to explain the /home folder would have been "this is exactly the same as C:\Users" (because it is, it is exactly the same) Overall a great vid though, definitely favoriting this one and sharing it around. This is one aspect of linux that is a real struggle for superusers from windows to figure out. It remained a head scratcher for me for years until I realized it had a structure of some kind and even after reading up on what's what I still managed to learn new things from this video. I didn't know /run was tmpfs, i ddin't know what /proc was, I didn't know the difference between /bin and /usr/bin, or /lib and /usr/lib... Honestly, if I really think about it.... It seems like an outdated filesystem structure in some regards, the entire /usr directory and it's subdirectories only create needless confusion to be completely honest, especially /usr/local it's like a redundancy within a redundancy for like no reason,´and thanks to that whenever you're looking for something, you have to search in 3 directories instead of just one (program files) on windows, why do we have /usr/share when we already have /opt? After looking deeper into FHS I found out that there's an OS called GoboLinux, it's filesystem structure is beautiful compared to this ugly mess; why hasn't something like that been adopted by now?
    1
  3. 1
  4. 1
  5. 1
  6. 1
  7. 1
  8. 1