A guy on an IBM seminar educated me that /usr was indeed "Unix System Resources". It used to bug me that some books and folks called it "user" when clearly the contents aren't user specific but from the other comments I see it used to be that in legacy times! So glad you've shared that, used to really bug me as a noobie. Also a hard lesson I've learnt is whenever you're poking around in /etc always make of copy of any file you edit or one day you'll be sorry if you didn't. Great video as ever!
I was today old when i learned that. I can see why that would be confusing for Linux users who might expect it to be called "LSR" -- but Unix Sys Resources makes so much more sense given what resides in it (aside from installed binaries)
@@GradyBroyles I mean, let's not forget that Linux is a Unix-like system after all, so I find it fine to be called usr instead of lsr, it keeps the legacy alive in a way
@@stargirl3352 totally, i just mean that a new Linux user could be easily forgiven for not realizing that usr was a acronym with the U meaning Unix. Then again, most people don't know that it was "really" called UNICS and not even Dennis Ritchie knows how it became "UNIX" ps: the story that it sounded too much like "eunuch" is likely just urban-nerd-legend
@@GradyBroyles yeah, most people even don't know what Unix is/was. I think it probably was an accident because cs make the same sound as x, so someone could have written down Unix and everyone just dealt with it
The /usr folder really does mean 'user'. It's historical. It actually used to serve the same function as the more modern '/home' folder. There was even a user named 'bin' who was the owner of all the executables. The IBM guy is backronyming it, and he's wrong. Or, at least, he's not giving you the historical context. I mean, it's faintly possible that I'm wrong. But, I was using Unix systems back in the mid-80s and I recall my home directory being in /usr and there being no /home. It wasn't until Solaris (aka SVR4) that I saw a /home folder. In order for an official answer you'd have to ask Dennis Ritchie.
Chris is Da GOAT for this... Most of us are coming from Windows and actually like the simplicity of it as a point and click operating system. Most Linux and Mac enthusiast don't keep this in mind.
You missed out the /opt directory. This tends to be used for "optional" installations which aren't really native Linux programs. E.g. most Mono programs install here.
I didn't expect that someone is able to make such topics which seem to be kind a dull this interesting. I like how you enjoy your videos and the linux os :D
Chris just wanted to say thanks I'm getting ready to take my CCNA and trying to get ahead of the curve with Linux and Python and you've made it very easy for novice like me to understand so much appreciated for everything you do been reccomending your vids to anyone who needs a nice crash course
Thank you so much for this video, Chris. This video was exactly what I needed. I am even going to download a copy of it and keep it saved in my HD just in case RUclips goes the way of the Dodo. Wonderful job. Really appreciate it. Cheers.
Create a statefulset of 2 pods, where we log disk space on an hourly basis, in an even odd fashion(use df -h / for getting space). Logger file should stored in the respective pv of pod only. PV should be of size 10Mi. Example - pod-0 (even hours) 2023-01-12T00:00:00 -> /dev/nvme0n1p2 234G 190G 33G 86% / 2023-01-12T02:00:00 -> /dev/nvme0n1p2 234G 191G 32G 87% / and so on pod-1 (odd hours) 2023-01-12T01:00:00 -> /dev/nvme0n1p2 234G 190G 33G 86% / 2023-01-12T03:00:00 -> /dev/nvme0n1p2 234G 191G 32G 87% / and so on
would like to mention that there is a folder in /usr where you can add custom resources and binaries and scripts and that is /usr/local this is meant to contain all your custom scripts in /usr/local/bin the other folders are rarely used to my knowledge but serve the same function as their equally named counterpart in / most people only use it to contain custom scripts and binaries they need to have system wide access to :)
I always recreated a bin directory at my home/user/bin and just put ~/bin in my $PATH. I guess I do this so I don't have to be root at that other location you mention.
@@gimcrack555 yeah thats if you need it to be accessible only by your user, /usr/local/bin is for custom binaries and scripts you want to be accessible system wide without having every user edit their $PATH :)
HikariKnight In FreeBSD, almost everything other than the base install goes in /usr/local/, so for example, configuration files for anything installed from ports would be in /usr/local/etc
I use to put all my alias in .bashrc. But I started using .bash_aliases for all my alias to keep my .bashrc a little clearer. You touch everything that needed to be said here. A lot of people always wonder where to put all their scripts they created or a clone github files, binary and other applications that they get outside their repositories. Me I just created a /home/user/bin directory to add all that stuff to. Of course have sub-directories in your ~/bin directory to keep it neat and tidy. I always add ~/bin in my $PATH that way I can run those scripts by simply typing out the files name and don't have to use ./ to run those applications. Something worth mention, in your later videos maybe.
You don't must exit terminal after change something in .bashrc just write source .bashrc and that will reload settings. Second tip cd ../.. takes you 2 folders up ;) thx for upload!
When I first time saw Unix folder tree, I thought, it's so accurate: each folder has own purpose, not that junk mix like in MS-DOS. But when I was kid, it was difficult to remember all those commands, so I started to learn DOS. In 2019 I see how nice Unix folder structure is. So useful, so intuitive, looks like ideal naming and order. Windows folder + mix of crap is so ugly compared to this. I like how easily can I mount new drives to folder, create links to files, folders, and these special files which connected to devices. When I see filesystem word I think about ext4, xfs etc., not about folder structure. On SSD it doesnt matter which of them You use, they have similar performance.
GoogleName> each folder has own purpose, not that junk mix like in MS-DOS What? 🤨 Folders in DOS/Windows have purposes too. The "\Windows" folder is for Windows, programs go in "\Program Files", photos go in "...\pictures", and so on. The only thing that *nix systems have over DOS/Windows is the everything-is-a-file paradigm, otherwise everything else you said applies to them too. ¬_¬
18:07 That is not applicaions that it's showing. Those are Application Menu shortcuts. .desktop files are shortcuts to applications which are in the App Menu.
5 лет назад+5
Hey Chris. This video was super useful. Thanks for it! I wanted to know, is there a terminal command on Ubuntu / Debian distros that lists me all of my installed apps and programs so I can see it clearly and uninstall things I don´t want on my system? Thanks!
not really. apt-get may have a way to list installed (tracked) packages. Check the man page for apt-get. On any Linux distro you can ls (list) your /usr/local/bin/ to see what user-land binaries you've got installed, or /usr/share/applications/ to see all the .desktop files (which are launchers for your GUI-based apps) so that's a good way. Check the Ubuntu user forums, it's a common question. When I used Ubuntu, no such app existed but things might have changed since then. Ar at the least there's a script someone's written.
@6:01 Exactly and permanent mounts are done in the fstab. The easiest way is to use the UID. That is particularly useful if you have a steam library on a separate drive and don't want to rely on automount.
protip: you only need to use UUID's in fstab for the boot volume because you want to ensure that the boot-loader won't look for a /boot on a drive not specifically designated by unique identifier. Your personal files volumes can be loaded in the fstab as /dev/sdx in the SAME fstab as UUID's for the boot volume. Here's what I mean: (mine) # /dev/sda3 UUID=ed6d43fd-2cea-4f26-9697-d8ed8f11b60f / ext4 rw,relatime 0 1 # /dev/sda4 UUID=0816bfc2-75b3-4fac-9c7b-f6567a9c7638 /boot ext4 rw,relatime,stripe=4 0 2 # /dev/sda5 UUID=fe7e5499-3bcf-43d9-8efd-8265db15bfc5 /home ext4 rw,relatime 0 2 # /dev/sda2 UUID=a10b9909-f090-4fed-8b5d-ea55d819f8d8 none swap defaults 0 0 /dev/sdd3 /home/lucifer/.storage ext4 rw,relatime 0 1 /dev/sdb1 /home/lucifer/Games ext4 rw,relatime 0 2 /dev/sdc1 /home/lucifer/Windows ext4 rw,relatime 0 2 /dev/sdd1 /home/lucifer/Videos/Cinema ext4 rw,relatime 0 2 /dev/sdd2 /home/lucifer/Videos/TV ext4 rw,relatime 0 2
Great info. I would like to know about drive/data organization. what is the best practices for disaster recovery? Such as should i isolate the different primary folders on different drives and access them using sym links? Like system, swop, home?
I also have a 2TB HDD as a second disk drive...you state that you have yours mounted in media soooo... do I use the systemctl command to mount it to media on boot? I'm sure you've made a video on it so I'll get diggin' :)
Fun fact: The /usr directory was the user directory on old unix systems, it later had personal directories of each user in it, they got moved much later to /home. /home was just created to keep the /usr directory clean c:
TBF having people keep their personal files in the same place as installed binaries and critical system files is a recipe for disaster. A sequestered /home seems like a safe happy-place by comparison
@@GradyBroyles it is, it wasn't even planed to be that way, in the early days of Unix, the few people who used it were mostly working in /usr so they assumed it was a good idea to keep user directories there as well, the other stuff like system libraries and such followed. Tbf stuff that the system needs in order to provide minimal functionality is in /sys, /bin, /dev, /etc, /lib And, unlike in this video, the /lib directory is not usually symlinked to /usr/lib
source will not remove the old things, just replace them, so if you did delete some alias, it will stay until you exit the current shell instance. restarting shell is sort of more bullet proof, although I guess you will rarely run into real issue with "source"-only way.
A lot of this has gone over my head, is there an introduction to the tech jargon used in this video? It was helpful to get an overview of how to access the file system and maneuver through it. But the details went over my head. Thanks so much, this is helping me. I’ve made the decision to switch to Ubuntu and am in the process of backing up files. For the reason that on my Inspiron 15 3000 Dell, windows has been the biggest pain in my ass I’ve ever experienced with technology. In all of my research this is non-fixable, and stumps all techies that have attempted to “fix” just how bogged down the OS makes this computer. I purchased it to be a nice middle priced computer that was supposed to be fast for writing/photography/music production/gaming, but it’s just had me on the verge of tears for many many reasons, between the unexpected/forced updates, resetting of settings that I’ve manually adjusted with almost every frequent update with absolutely no explanation, I’ve just decided I’m done. Now, if I use a Virtual Machine to run Windows on so I can use Studio one for example, is that doable? Because I’ve got Studio one as a music production software, and it’s frankly amazing. That’s my only hang up and I need to know if this is possible before actually making the switch. I definitely do not want to dual boot with this, I’m sure for obvious reasons, it’s just too much. I have a 1 tb hard drive, intel core i5 10th gen. I was pleased when I initially chose this machine because of the specs, but had NO idea the challenges that accompanied the insane amount of background processing without the ability to solidify a customizable background app control. Despite disabling background functions they continued to run. I’m excited to shift, and learn Linux, and become much more tech savvy. I grew up in the tech age and feel I can pick up on it pretty quickly. These videos help greatly! Any tips or warnings would be greatly appreciated! Thanks so much!
Traditionally on Unix systems, the executables would be split as follows: /bin ... User utilities that can be run in either single or multi-user environments (not going to get into 'run-levels' here ). In some systems, like OpenBSD, these are statically linked (so they don't need the libraries to run). Examples: ls, shells like bash, csh, tcsh and so on. /sbin ... System utilities that can be run in either single or multi-user environments. Again in some systems these are statically linked. Examples: mkfs, fsck and friends, in Linux you'll also find lsmod, modprobe and so on. /usr/bin .. User utilities, programs and so on. In Linux that's pretty much anything you install as a user that isn't, say, a server app, and that comes from the vendor (i.e. from your distros standard repositaries). On BSDs this is a bit more restricted, since most 'ported' apps, end up in /usr/local/bin instead. /usr/sbin.. System daemons and such. If you run say a web server, than the daemon service will end up here. To make that maybe a bit clearer, if you have the ssh-server installed, you'll find sshd here, but your ssh 'client' (what you use to connect to another machine) will end up in /usr/bin. Again BSDs tend to put the user-added ported stuff in /usr/local (so /usr/local/sbin). As hinted above, you'll find the equivalent to /usr/bin and /usr/sbin in /usr/local. For the most part, Linux pretty much ignores this, except it *does* typically add /usr/local/??? to the various paths as a convenience. If you compile your own stuff, say from upstream, it's usually a good idea to put it there, so you can avoid conflicts with the distro's own version of the same package (and it will avoid headaches if you try and have both at the same time). Hope this helps.
@@michelderosa2695 Very nice description, even if i find it a little bit too complicated for my taste (the folders, not your answer :P). it's all i needed to know, thanks.
Great video, I have been using Ubuntu as my main working OS for the past year and a half and this video has helped me understand what all these folders are, BTW I always assumed that usr was a user data folder (besides home). The .bashrc tip is super handy. Thanks a lot!
Almost everything I do is with tty. Although I mainly work headless in a tty console, so I'm always switching between multiple tty consoles and fg and bg jobs on each. Some people think I'm weird but I have always preferred to work linearly with keyboard and prompt rather than mouse and an event driven GUI. For me I seem to be able to work faster and for my left brain it's beautiful because I control everything that happens based on what I've typed and the options used. No mystery just straight to the action. I get so lost sometimes inside a GUI program with menus and sub menus and windows and child windows and all that jazz. Everyone has experienced this -> imagine trying to find a setting in a gui program and you just can't seem to find it in the event driven sea of menus and windows. You just want to change the theme to dark and stop the spell check from putting a squiggle under your text for example. Is it under options? Is it under preferences? is it under edit->options or project->options or file->preferences? Little side rant... Why options and preferences grrr I hate when programs do that. Well now you have to Google and they tell you it's under options but you don't see it there because your version is newer and has moved it or has it eliminated it? Now you have to find out that. Instead I would rather just type theme=dark; spellcheck=false for a pseudo example. Hahaha I just did all that to see if I could make a case for no GUI and it was a fun little argument to put together. But it's all true. I use tty unless I absolutely can't, like if I need to photoshop or something. Btw ima software programmer and reverse engineer so I write gui based software all the time which is funny.
Can you make a more detailed video on mounting devices and checking what's mounted? I have my old 3TB NTFS formatted HDD in my system and it's currently in /media with the directory called what I called the drive while I was still on windows, but it never properly mounts by itself after a boot; I usually have to open Dolphin and click on the HDD there for it to mount at which point my wallpaper shows up and the drive works in terminal. I also heard of people edited something in /etc/fstab to make proton have less issues with NTFS, but couldn't find my HDD there, so I think it's not mounted correctly currently. I'm on Kubuntu 19.04 and it automatically set up the drive in this seemingly weird way, if that helps to know.
I had some flashbacks during this video, I remembered the old SUNOS / SGI (Irix) workstations during my UNI days in the research departments (64 MB RAM was huge, 16 MB was normal) but they actually did have a folder called /users, the equivalent of /home. I must admit I always pronounce /usr/bin as "user bin" 👽, Good reminder 👏
also i cant understand why linux users always use nano or vim or sth like that... i think its just overcomplicated... why not just use gedit or any "normal" editor? and could you please make a video about the differences between the linux "file systems", with that i mean ext4, reiserfs and so on... and what is best for which use? because i first thought this video would be about that ^^
/lost+found is *NOT* a recycle bin! It's a directory where fsck (filesystem check) puts parts of recovered files when checking that filesystem after an unclean shutdown. And you seem to have some files in it. Then, /media and /mnt serve different purposes: the former is a place where volatile (removable) media is mounted, and the latter is where permanent media (like your 2 TB hard disk) is mounted.
A little sidenote, you can log in as administrator by simply entering "su" instead of "sudo su", at least on Manjaro. However, there is one use-case-scenario in which "sudo su" is more convenient, when you just used sudo and it hasn't timed out yet, then entering "sudo" first spares you from typing your password one more time.
you can make ssh shortcuts and store them in ~/.ssh/config (config is a text file) an example: Host Odin HostName 192.168.0.1 User admin add that to the config file and you can do : ssh Odin it will ask for a password if you dont have authorized keys set up, then connect you. this keeps all your ssh sessions you use in one tidy place. note: caps is important. Odin is different then odin.
often closed-source (or packaged by 3rd party, not being part of your distro repositories) SW installs there, or sometimes (rarely) it is used as default prefix when building SW from source. It's a bit like "Program Files" in windows (but lot less used by anything, as most of the stuff comes usually from the distro and goes into /usr/...).
Re: /media and why it's not ideal... i have a single SD broken into 2- 1tb partitions. One contains my movies and the other TV shows. Instead of mounting the whole drive to /media (I don't want it mounted into the root. I really don't like arbitrarily changing the structure of /) I create 2 mount-points under what will be the ~/Videos/ that is automatically created at the first log-in to my DE (KDE, but it's the same in Gnome and others too) ~/Videos/Cinema ~/Videos/TV I then mount to THEM using corresponding entries in /etc/fstab. ez pz and much safer than mounting user data to root. (Bonus tip): i also create 2 invisible folders under ~/Videos for use by downloaders like bit-torrent clients: ~/Videos/.torrents ~/Videos/.incomplete they're self-explanatory. I use them when setting preferences in Ktorrent (rtorrent or w/evs) to drop .torrent files and incomplete videos into, yeah you get the idea. Regarding ~/.bash_profile This file is similar to ~/.bashrc but instead of loading with every new terminal session, it loads with every USER session. This is where you want to put your "environment variables" that you want set across your user session from log-in to log-out. A super-duper common and useful one for gamers is WINEPREFIX. In order to set WINEPREFIX=~/.wine you would open ~/.bash_profile (with vim b/c you *need* to learn vim *shameless vim plug) and append the following line: export WINEPREFIX="$HOME/.wine" and save and quit (in vim that's [esc] to exit edit mode and "ZZ" to save and quit) For new Linux users re: .bash_profile: If you''ve ever been confused when someone says "add it to your $PATH". $PATH, like $WINEPREFIX and even $HOME and $USER are just "environment variables" so ~/.bash_profile is generally where you'd do that. You can re-define $PATH to include any arbitrary paths (for executables) you'd like to add and make available to the current users session, simply adding this to .bash_profile will do it: export PATH=$PATH;/your/path/here; What that does is appends your path to the existing $PATH environment variable . It's like saying PATH = PATH + a new path. "export" makes it available to the user's session at log-in. You will need to log-out (or reboot) and log-in to a new session for the effect to take. I use this to add ~/Scripts where I keep my BASH scripts to my $PATH so that I can just type the name of a script to run it just like it was a binary. (w/o the .sh even) In order to check to see if it worked, just type: echo $WINEPREFIX it should return /home/username/.wine if it returns nothing, you did it wrong or did not start a new session. Make sure you have "start with an empty session" set in whatever DE you use so when you log-out and back in, you'll have a new session and the changes to bash_profile will be in effect.
Topic suggestion: find info about hardware with dmidecode (for example useful to verify that the RAM is clocked at the set frequency, motherboard often are weird with that after a BIOS-reset), lm-sensors and other tools. Clock-frequency of CPU and RAM, voltage, wattage, temperatures... After that of course how to manually set a fancurve (unfortunately required for many graphics cards, in the case of AMD you need to enter a Matrix in Python in a certain path), undervolt, overclock...
Hi, Good guide. You might want to change files in /bin, if, for instance you need to temporarily downgrade gcc (some time ago the latest gcc compiler had problems with the kernel source). Go to /bin (or /usr/bin) remove the symbolic link and re-create it pointing to the particular version you need. Also temporarily disabling a program by removing its executable bit can be useful. /var/tmp is a useful place to temporary files that you'd like to survive a reboot. /usr/local/bin is where to install locally-created programs that are system-wide.
Yes, or if it was /user/loginname It might have been HPUX though. But most migrated to /home/loginname (or subfolders for sites with 10000 users, like the uni I work at).
I believe the collection of OS's with this type of similar filesystem layout (including the BSD's, Solaris, macOS, AIX and other Unix's, and many more) are called *POSIX* based OS's. Basically everything that's not Windows.. because, you know, they're special..
@@SMJSmoK Yes, compliant. Or POSIX-certified if they're actually certified to conform to one of the POSIX standards. Most linux distro's are actually just "mostly POSIX-compliant"
Actually, POSIX compliance is a bit different, since it relates to programming ABIs and such. OpenVMS is a POSIX compliant OS, and it definitelly does not share the Unix file hierarchy. You are probably thinking about the Single Unix Specification (SUSVn, we're up to SUSV4 right now), which, among other things, specifies a few must-have directories, in order to be compliant. Those are / , /dev and /tmp . In addition, /dev must have entries for /dev/console, /dev/null and /dev/tty.
@@michelderosa2695 Oh, ok. But don't you mean "programming *APIs* " (not ABIs)? I've just always heard them referred to as POSIX. But thanks for the correction.
@@fourdotsYT Ah yes my bad.. POSIX does indeed define the API, not the ABI. The two are a bit different (but both do exist, but explaining the difference would lead us wayyy off topic).
1979: The GUI was invented. 1984: Machintosh introduced GUI in their computers 1985: Microsoft introduced GUI on Windows 1 ... 2021: Let's use the terminal because is easier to show the file system... Are you serious? Computers moved from command-line environments to GUI because it's easier for people to See graphically what's going on instead of reading awkward text symbols.
The stock installations, like /var/www is just stock. You are supposed to change that in the configuration when you run it for real. /srv/ is the directory where you actually are supposed to store data for servers. So /srv/www/www.my-site.com/www would be a good place for the webserver virtual site www.my-site.com/ (I don't run my editor with sudo(1), because the makes my home directory stored with config files own by root. I use Emacs and open this filen with Tramp using sudo (Just start emacs and type: C-x C-f /sudo:root@localhost:/etc/packman.conf ), which will open the file as root with sudo on the local machine. It I want to open a file with ssh, I open the file "sft:login@machine:filename.txt" or "ssh:login@machine:filename.txt") About removing the wrong fingerprint, you the command instead that is recommended when your ssh are stoped. As the IP-number and name usually are encrypted in the known_hosts file and not in clear text like in your command. It is usually better to save the hosts keys and restore them after the new installation. :-)
just know ... this is the basic of linux File system .. just know that there is a lot of folders, just know there is links and files ;P just know this is funny ;P
Or "sudo su -" which has the same effect. It will start a root session as a login shell (meaning that it will force the shell to execute its startup scripts (like e.g. .bashrc etc).
When this popped up in my recommendations and I saw that you were using Manjaro, I thought, "great, maybe he'll explain why Arch-based distros use /run/media for mounts but Debian-based use /media". Instead, you skipped /run and went ahead and created /media instead. :-(
The title of this video should be "Linux Directory Structure" instead of "Linux File Sytems". All of the directories you have shown could be in the same file system or in different file systems.
Whaaat? /sbin -> /usr/bin ? BIN? Not SBIN ? Is it systemd people trying to make Linux the same mess as Windows? Yeah, trolling I know. But seriously, where's the old compartment gone? I mean... why?
Too complex of an explanation, just a suggestion but limiting the file structure to what people would use in the GUI, instead of command line would be useful, for instance this is what this folder is used for here is what types of files it contains, and movie on, there is no need for advanced functions on what you would use the folder/directory for.
A guy on an IBM seminar educated me that /usr was indeed "Unix System Resources". It used to bug me that some books and folks called it "user" when clearly the contents aren't user specific but from the other comments I see it used to be that in legacy times! So glad you've shared that, used to really bug me as a noobie. Also a hard lesson I've learnt is whenever you're poking around in /etc always make of copy of any file you edit or one day you'll be sorry if you didn't. Great video as ever!
I was today old when i learned that. I can see why that would be confusing for Linux users who might expect it to be called "LSR" -- but Unix Sys Resources makes so much more sense given what resides in it (aside from installed binaries)
@@GradyBroyles I mean, let's not forget that Linux is a Unix-like system after all, so I find it fine to be called usr instead of lsr, it keeps the legacy alive in a way
@@stargirl3352 totally, i just mean that a new Linux user could be easily forgiven for not realizing that usr was a acronym with the U meaning Unix. Then again, most people don't know that it was "really" called UNICS and not even Dennis Ritchie knows how it became "UNIX"
ps: the story that it sounded too much like "eunuch" is likely just urban-nerd-legend
@@GradyBroyles yeah, most people even don't know what Unix is/was.
I think it probably was an accident because cs make the same sound as x, so someone could have written down Unix and everyone just dealt with it
The /usr folder really does mean 'user'. It's historical. It actually used to serve the same function as the more modern '/home' folder. There was even a user named 'bin' who was the owner of all the executables. The IBM guy is backronyming it, and he's wrong. Or, at least, he's not giving you the historical context.
I mean, it's faintly possible that I'm wrong. But, I was using Unix systems back in the mid-80s and I recall my home directory being in /usr and there being no /home. It wasn't until Solaris (aka SVR4) that I saw a /home folder. In order for an official answer you'd have to ask Dennis Ritchie.
Chris is Da GOAT for this... Most of us are coming from Windows and actually like the simplicity of it as a point and click operating system. Most Linux and Mac enthusiast don't keep this in mind.
lost+found is not a 'recycle bin'. It is where files sometimes go ('lost' files with no name) after a file system repair (fsck).
Thank you, Chris. This is Knowledge all users should have.
You missed out the /opt directory. This tends to be used for "optional" installations which aren't really native Linux programs. E.g. most Mono programs install here.
yeah and some ruby gems and python stuff too. It really can give me gas and the grumpies sometimes
I didn't expect that someone is able to make such topics which seem to be kind a dull this interesting. I like how you enjoy your videos and the linux os :D
Chris just wanted to say thanks I'm getting ready to take my CCNA and trying to get ahead of the curve with Linux and Python and you've made it very easy for novice like me to understand so much appreciated for everything you do been reccomending your vids to anyone who needs a nice crash course
Thank you so much for this video, Chris. This video was exactly what I needed. I am even going to download a copy of it and keep it saved in my HD just in case RUclips goes the way of the Dodo. Wonderful job. Really appreciate it. Cheers.
Thanks chris for making this video, really helps. Absolutely love the way you explained every folder. Thanks again
Very good video, Chris. This is a nice overview. Thank you for your time.
Create a statefulset of 2 pods, where we log disk space on an hourly basis, in an even odd fashion(use df -h / for getting space). Logger file should stored in the respective pv of pod only. PV should be of size 10Mi.
Example -
pod-0 (even hours)
2023-01-12T00:00:00 -> /dev/nvme0n1p2 234G 190G 33G 86% /
2023-01-12T02:00:00 -> /dev/nvme0n1p2 234G 191G 32G 87% /
and so on
pod-1 (odd hours)
2023-01-12T01:00:00 -> /dev/nvme0n1p2 234G 190G 33G 86% /
2023-01-12T03:00:00 -> /dev/nvme0n1p2 234G 191G 32G 87% /
and so on
You don't need 2 foam pop filters, you can choose between the one on the mic and the one in front.
Thank you so much , Chris Keep up and THUMBS up
would like to mention that there is a folder in /usr where you can add custom resources and binaries and scripts and that is /usr/local
this is meant to contain all your custom scripts in /usr/local/bin
the other folders are rarely used to my knowledge but serve the same function as their equally named counterpart in /
most people only use it to contain custom scripts and binaries they need to have system wide access to :)
I always recreated a bin directory at my home/user/bin and just put ~/bin in my $PATH. I guess I do this so I don't have to be root at that other location you mention.
@@gimcrack555 yeah thats if you need it to be accessible only by your user, /usr/local/bin is for custom binaries and scripts you want to be accessible system wide without having every user edit their $PATH :)
HikariKnight
In FreeBSD, almost everything other than the base install goes in /usr/local/, so for example, configuration files for anything installed from ports would be in /usr/local/etc
I use to put all my alias in .bashrc. But I started using .bash_aliases for all my alias to keep my .bashrc a little clearer. You touch everything that needed to be said here. A lot of people always wonder where to put all their scripts they created or a clone github files, binary and other applications that they get outside their repositories. Me I just created a /home/user/bin directory to add all that stuff to. Of course have sub-directories in your ~/bin directory to keep it neat and tidy. I always add ~/bin in my $PATH that way I can run those scripts by simply typing out the files name and don't have to use ./ to run those applications. Something worth mention, in your later videos maybe.
Type in one terminal: ( man hier ) and read.
cool
In the original Unix implementations, /usr was where the home directories of the users were placed instead of /home.
Yep you are right. It also contains additional unix commands and data files. I put my own executables in /usr/bin instead of /bin
@@squadramunter they're symlinked in most distros. is: same folder. you're looking for /usr/local/
This videi helped me the most to learn the Linux file system
You don't must exit terminal after change something in .bashrc just write source .bashrc and that will reload settings. Second tip cd ../.. takes you 2 folders up ;) thx for upload!
When I first time saw Unix folder tree, I thought, it's so accurate: each folder has own purpose, not that junk mix like in MS-DOS. But when I was kid, it was difficult to remember all those commands, so I started to learn DOS. In 2019 I see how nice Unix folder structure is. So useful, so intuitive, looks like ideal naming and order. Windows folder + mix of crap is so ugly compared to this.
I like how easily can I mount new drives to folder, create links to files, folders, and these special files which connected to devices.
When I see filesystem word I think about ext4, xfs etc., not about folder structure. On SSD it doesnt matter which of them You use, they have similar performance.
GoogleName> each folder has own purpose, not that junk mix like in MS-DOS
What? 🤨 Folders in DOS/Windows have purposes too. The "\Windows" folder is for Windows, programs go in "\Program Files", photos go in "...\pictures", and so on. The only thing that *nix systems have over DOS/Windows is the everything-is-a-file paradigm, otherwise everything else you said applies to them too. ¬_¬
Thanks Chris great and important video.
Thank you for this very instructive video. Keep it up! Cheers.
Chris, could you do a video on how to install and configure NVIDIA proprietary drivers. Configuring multi monitor displays is very difficult.
18:07 That is not applicaions that it's showing. Those are Application Menu shortcuts. .desktop files are shortcuts to applications which are in the App Menu.
Hey Chris. This video was super useful. Thanks for it! I wanted to know, is there a terminal command on Ubuntu / Debian distros that lists me all of my installed apps and programs so I can see it clearly and uninstall things I don´t want on my system? Thanks!
Certainly, Type: apt list --installed
not really. apt-get may have a way to list installed (tracked) packages. Check the man page for apt-get. On any Linux distro you can ls (list) your /usr/local/bin/ to see what user-land binaries you've got installed, or /usr/share/applications/ to see all the .desktop files (which are launchers for your GUI-based apps) so that's a good way.
Check the Ubuntu user forums, it's a common question. When I used Ubuntu, no such app existed but things might have changed since then. Ar at the least there's a script someone's written.
What's that widget called that's on his desktop? Looks really good
@6:01 Exactly and permanent mounts are done in the fstab. The easiest way is to use the UID. That is particularly useful if you have a steam library on a separate drive and don't want to rely on automount.
protip: you only need to use UUID's in fstab for the boot volume because you want to ensure that the boot-loader won't look for a /boot on a drive not specifically designated by unique identifier. Your personal files volumes can be loaded in the fstab as /dev/sdx in the SAME fstab as UUID's for the boot volume. Here's what I mean: (mine)
# /dev/sda3
UUID=ed6d43fd-2cea-4f26-9697-d8ed8f11b60f / ext4 rw,relatime 0 1
# /dev/sda4
UUID=0816bfc2-75b3-4fac-9c7b-f6567a9c7638 /boot ext4 rw,relatime,stripe=4 0 2
# /dev/sda5
UUID=fe7e5499-3bcf-43d9-8efd-8265db15bfc5 /home ext4 rw,relatime 0 2
# /dev/sda2
UUID=a10b9909-f090-4fed-8b5d-ea55d819f8d8 none swap defaults 0 0
/dev/sdd3 /home/lucifer/.storage ext4 rw,relatime 0 1
/dev/sdb1 /home/lucifer/Games ext4 rw,relatime 0 2
/dev/sdc1 /home/lucifer/Windows ext4 rw,relatime 0 2
/dev/sdd1 /home/lucifer/Videos/Cinema ext4 rw,relatime 0 2
/dev/sdd2 /home/lucifer/Videos/TV ext4 rw,relatime 0 2
Great info. I would like to know about drive/data organization. what is the best practices for disaster recovery? Such as should i isolate the different primary folders on different drives and access them using sym links? Like system, swop, home?
Excellent presentation!!!
I would like to know why we use filesystem both in terms of FHS and for actual filesystems like btrfs. That probably confuses newer users.
I also have a 2TB HDD as a second disk drive...you state that you have yours mounted in media soooo... do I use the systemctl command to mount it to media on boot? I'm sure you've made a video on it so I'll get diggin' :)
just know that a lot of the config files is in /etc/ ;p
Fun fact: The /usr directory was the user directory on old unix systems, it later had personal directories of each user in it, they got moved much later to /home. /home was just created to keep the /usr directory clean c:
TBF having people keep their personal files in the same place as installed binaries and critical system files is a recipe for disaster. A sequestered /home seems like a safe happy-place by comparison
@@GradyBroyles it is, it wasn't even planed to be that way, in the early days of Unix, the few people who used it were mostly working in /usr so they assumed it was a good idea to keep user directories there as well, the other stuff like system libraries and such followed.
Tbf stuff that the system needs in order to provide minimal functionality is in /sys, /bin, /dev, /etc, /lib
And, unlike in this video, the /lib directory is not usually symlinked to /usr/lib
If you change your .bashrc you don't need to log out then log in, you can 'source .bashrc' to enable the changes.
source will not remove the old things, just replace them, so if you did delete some alias, it will stay until you exit the current shell instance. restarting shell is sort of more bullet proof, although I guess you will rarely run into real issue with "source"-only way.
A lot of this has gone over my head, is there an introduction to the tech jargon used in this video? It was helpful to get an overview of how to access the file system and maneuver through it. But the details went over my head. Thanks so much, this is helping me. I’ve made the decision to switch to Ubuntu and am in the process of backing up files. For the reason that on my Inspiron 15 3000 Dell, windows has been the biggest pain in my ass I’ve ever experienced with technology. In all of my research this is non-fixable, and stumps all techies that have attempted to “fix” just how bogged down the OS makes this computer. I purchased it to be a nice middle priced computer that was supposed to be fast for writing/photography/music production/gaming, but it’s just had me on the verge of tears for many many reasons, between the unexpected/forced updates, resetting of settings that I’ve manually adjusted with almost every frequent update with absolutely no explanation, I’ve just decided I’m done. Now, if I use a Virtual Machine to run Windows on so I can use Studio one for example, is that doable? Because I’ve got Studio one as a music production software, and it’s frankly amazing. That’s my only hang up and I need to know if this is possible before actually making the switch. I definitely do not want to dual boot with this, I’m sure for obvious reasons, it’s just too much. I have a 1 tb hard drive, intel core i5 10th gen. I was pleased when I initially chose this machine because of the specs, but had NO idea the challenges that accompanied the insane amount of background processing without the ability to solidify a customizable background app control. Despite disabling background functions they continued to run. I’m excited to shift, and learn Linux, and become much more tech savvy. I grew up in the tech age and feel I can pick up on it pretty quickly. These videos help greatly! Any tips or warnings would be greatly appreciated! Thanks so much!
what exactly is the difference between the bin and sbin folders? i know both contain programs but...
Traditionally on Unix systems, the executables would be split as follows:
/bin ... User utilities that can be run in either single or multi-user environments (not going to get into 'run-levels' here ). In some systems, like OpenBSD, these are statically linked (so they don't need the libraries to run). Examples: ls, shells like bash, csh, tcsh and so on.
/sbin ... System utilities that can be run in either single or multi-user environments. Again in some systems these are statically linked. Examples: mkfs, fsck and friends, in Linux you'll also find lsmod, modprobe and so on.
/usr/bin .. User utilities, programs and so on. In Linux that's pretty much anything you install as a user that isn't, say, a server app, and that comes from the vendor (i.e. from your distros standard repositaries). On BSDs this is a bit more restricted, since most 'ported' apps, end up in /usr/local/bin instead.
/usr/sbin.. System daemons and such. If you run say a web server, than the daemon service will end up here. To make that maybe a bit clearer, if you have the ssh-server installed, you'll find sshd here, but your ssh 'client' (what you use to connect to another machine) will end up in /usr/bin. Again BSDs tend to put the user-added ported stuff in /usr/local (so /usr/local/sbin).
As hinted above, you'll find the equivalent to /usr/bin and /usr/sbin in /usr/local. For the most part, Linux pretty much ignores this, except it *does* typically add /usr/local/??? to the various paths as a convenience. If you compile your own stuff, say from upstream, it's usually a good idea to put it there, so you can avoid conflicts with the distro's own version of the same package (and it will avoid headaches if you try and have both at the same time).
Hope this helps.
@@michelderosa2695 Very nice description, even if i find it a little bit too complicated for my taste (the folders, not your answer :P). it's all i needed to know, thanks.
As always this is an epic video!! Thanks for explaining.
Great video, I have been using Ubuntu as my main working OS for the past year and a half and this video has helped me understand what all these folders are, BTW I always assumed that usr was a user data folder (besides home). The .bashrc tip is super handy. Thanks a lot!
Almost everything I do is with tty. Although I mainly work headless in a tty console, so I'm always switching between multiple tty consoles and fg and bg jobs on each. Some people think I'm weird but I have always preferred to work linearly with keyboard and prompt rather than mouse and an event driven GUI. For me I seem to be able to work faster and for my left brain it's beautiful because I control everything that happens based on what I've typed and the options used. No mystery just straight to the action. I get so lost sometimes inside a GUI program with menus and sub menus and windows and child windows and all that jazz. Everyone has experienced this -> imagine trying to find a setting in a gui program and you just can't seem to find it in the event driven sea of menus and windows. You just want to change the theme to dark and stop the spell check from putting a squiggle under your text for example. Is it under options? Is it under preferences? is it under edit->options or project->options or file->preferences? Little side rant... Why options and preferences grrr I hate when programs do that. Well now you have to Google and they tell you it's under options but you don't see it there because your version is newer and has moved it or has it eliminated it? Now you have to find out that. Instead I would rather just type theme=dark; spellcheck=false for a pseudo example. Hahaha I just did all that to see if I could make a case for no GUI and it was a fun little argument to put together. But it's all true. I use tty unless I absolutely can't, like if I need to photoshop or something. Btw ima software programmer and reverse engineer so I write gui based software all the time which is funny.
Can you make a more detailed video on mounting devices and checking what's mounted? I have my old 3TB NTFS formatted HDD in my system and it's currently in /media with the directory called what I called the drive while I was still on windows, but it never properly mounts by itself after a boot; I usually have to open Dolphin and click on the HDD there for it to mount at which point my wallpaper shows up and the drive works in terminal.
I also heard of people edited something in /etc/fstab to make proton have less issues with NTFS, but couldn't find my HDD there, so I think it's not mounted correctly currently. I'm on Kubuntu 19.04 and it automatically set up the drive in this seemingly weird way, if that helps to know.
I had some flashbacks during this video, I remembered the old SUNOS / SGI (Irix) workstations during my UNI days in the research departments (64 MB RAM was huge, 16 MB was normal) but they actually did have a folder called /users, the equivalent of /home.
I must admit I always pronounce /usr/bin as "user bin" 👽, Good reminder 👏
Manjaro and Arch put their media in /run/, why?
You're doing God's work.
Thanks Chris. Great video
Do ya know how I would change a raspberry pi 3 into a server which I can leave on and ssh into it anytime? How would I go about doing that?
I am trying to figure out the equivalent to Windows' Drive C. etc. Is that SDA? You skipped over that part.
also i cant understand why linux users always use nano or vim or sth like that... i think its just overcomplicated... why not just use gedit or any "normal" editor?
and could you please make a video about the differences between the linux "file systems", with that i mean ext4, reiserfs and so on... and what is best for which use? because i first thought this video would be about that ^^
/lost+found is *NOT* a recycle bin! It's a directory where fsck (filesystem check) puts parts of recovered files when checking that filesystem after an unclean shutdown. And you seem to have some files in it.
Then, /media and /mnt serve different purposes: the former is a place where volatile (removable) media is mounted, and the latter is where permanent media (like your 2 TB hard disk) is mounted.
A little sidenote, you can log in as administrator by simply entering "su" instead of "sudo su", at least on Manjaro. However, there is one use-case-scenario in which "sudo su" is more convenient, when you just used sudo and it hasn't timed out yet, then entering "sudo" first spares you from typing your password one more time.
I used to call usr as user but I know it is called Unix System Resources thx Chris! Lol the info stored has now updated as recently like just now XD
It was actually user from beginning. But can also be read as you wrote.
you can make ssh shortcuts and store them in ~/.ssh/config (config is a text file)
an example:
Host Odin
HostName 192.168.0.1
User admin
add that to the config file and you can do : ssh Odin
it will ask for a password if you dont have authorized keys set up, then connect you.
this keeps all your ssh sessions you use in one tidy place.
note: caps is important. Odin is different then odin.
same thing applies to vim as well.
It's often worthwhile to add a new line to /etc/hosts
So that the machine name is recognized by all programs, not just SSH.
You also left out /opt. Can't remember I've seen many commands referencing it. So it might be there just for legacy.
It's there for "optional" stuff, some programs will install themselves into it
often closed-source (or packaged by 3rd party, not being part of your distro repositories) SW installs there, or sometimes (rarely) it is used as default prefix when building SW from source. It's a bit like "Program Files" in windows (but lot less used by anything, as most of the stuff comes usually from the distro and goes into /usr/...).
Thanks you for share your knowledge.
I use mx Linux now, any recommendations? Best regards from Uruguay
Re: /media and why it's not ideal...
i have a single SD broken into 2- 1tb partitions. One contains my movies and the other TV shows. Instead of mounting the whole drive to /media (I don't want it mounted into the root. I really don't like arbitrarily changing the structure of /)
I create 2 mount-points under what will be the ~/Videos/ that is automatically created at the first log-in to my DE (KDE, but it's the same in Gnome and others too)
~/Videos/Cinema
~/Videos/TV
I then mount to THEM using corresponding entries in /etc/fstab. ez pz and much safer than mounting user data to root.
(Bonus tip): i also create 2 invisible folders under ~/Videos for use by downloaders like bit-torrent clients:
~/Videos/.torrents
~/Videos/.incomplete
they're self-explanatory. I use them when setting preferences in Ktorrent (rtorrent or w/evs) to drop .torrent files and incomplete videos into, yeah you get the idea.
Regarding ~/.bash_profile
This file is similar to ~/.bashrc but instead of loading with every new terminal session, it loads with every USER session. This is where you want to put your "environment variables" that you want set across your user session from log-in to log-out. A super-duper common and useful one for gamers is WINEPREFIX. In order to set WINEPREFIX=~/.wine you would open ~/.bash_profile (with vim b/c you *need* to learn vim *shameless vim plug) and append the following line:
export WINEPREFIX="$HOME/.wine"
and save and quit (in vim that's [esc] to exit edit mode and "ZZ" to save and quit)
For new Linux users re: .bash_profile: If you''ve ever been confused when someone says "add it to your $PATH". $PATH, like $WINEPREFIX and even $HOME and $USER are just "environment variables" so ~/.bash_profile is generally where you'd do that. You can re-define $PATH to include any arbitrary paths (for executables) you'd like to add and make available to the current users session, simply adding this to .bash_profile will do it:
export PATH=$PATH;/your/path/here;
What that does is appends your path to the existing $PATH environment variable . It's like saying PATH = PATH + a new path. "export" makes it available to the user's session at log-in.
You will need to log-out (or reboot) and log-in to a new session for the effect to take. I use this to add ~/Scripts where I keep my BASH scripts to my $PATH so that I can just type the name of a script to run it just like it was a binary. (w/o the .sh even)
In order to check to see if it worked, just type:
echo $WINEPREFIX
it should return
/home/username/.wine
if it returns nothing, you did it wrong or did not start a new session. Make sure you have "start with an empty session" set in whatever DE you use so when you log-out and back in, you'll have a new session and the changes to bash_profile will be in effect.
Thank you! Beautifull video!
Chris, how can you change your /home to be on another drive as I'm using an SSD and space is at a premium.
It depends on what you want to ship to another drive.
i read "complete *overhaul* " and almost fainted
dear god
Topic suggestion: find info about hardware with dmidecode (for example useful to verify that the RAM is clocked at the set frequency, motherboard often are weird with that after a BIOS-reset), lm-sensors and other tools. Clock-frequency of CPU and RAM, voltage, wattage, temperatures...
After that of course how to manually set a fancurve (unfortunately required for many graphics cards, in the case of AMD you need to enter a Matrix in Python in a certain path), undervolt, overclock...
Fantastic, thank you, please lots of follow up, thank you.
You didn't mention opt and you didn't mention where regular programs like Firefox get installed.
Hi,
Good guide.
You might want to change files in /bin, if, for instance you need to temporarily downgrade gcc (some time ago the latest gcc compiler had problems with the kernel source). Go to /bin (or /usr/bin) remove the symbolic link and re-create it pointing to the particular version you need. Also temporarily disabling a program by removing its executable bit can be useful.
/var/tmp is a useful place to temporary files that you'd like to survive a reboot.
/usr/local/bin is where to install locally-created programs that are system-wide.
I think new user often get confused about the diff between mnt and media and when to use which
Hello sir, unable to disable compilers in Ubuntu 21.04
"MAGA" & OK!!! Thanks, Chris Titus Tech for Your FILE SYSTEM Efforts!!!
I think IRIX places home directories on /extra/people.
Yes, or if it was /user/loginname It might have been HPUX though. But most migrated to /home/loginname (or subfolders for sites with 10000 users, like the uni I work at).
How does /var/www/ compare to localhost:xxxx?
I believe the collection of OS's with this type of similar filesystem layout (including the BSD's, Solaris, macOS, AIX and other Unix's, and many more) are called *POSIX* based OS's. Basically everything that's not Windows.. because, you know, they're special..
* POSIX compliant
@@SMJSmoK Yes, compliant. Or POSIX-certified if they're actually certified to conform to one of the POSIX standards. Most linux distro's are actually just "mostly POSIX-compliant"
Actually, POSIX compliance is a bit different, since it relates to programming ABIs and such. OpenVMS is a POSIX compliant OS, and it definitelly does not share the Unix file hierarchy.
You are probably thinking about the Single Unix Specification (SUSVn, we're up to SUSV4 right now), which, among other things, specifies a few must-have directories, in order to be compliant.
Those are / , /dev and /tmp . In addition, /dev must have entries for /dev/console, /dev/null and /dev/tty.
@@michelderosa2695 Oh, ok. But don't you mean "programming *APIs* " (not ABIs)? I've just always heard them referred to as POSIX. But thanks for the correction.
@@fourdotsYT Ah yes my bad.. POSIX does indeed define the API, not the ABI. The two are a bit different (but both do exist, but explaining the difference would lead us wayyy off topic).
why does my systems file system always go read only so I have to reboot and do an fsck all the time
my guess is that you are dual boot with Windows Right?
you gracefully skipped mnt, opt, proc (mentioned, but then skipped anyway), run, srv, sys....
tip you can simply user@ip for ssh to hostname with a ssh config file
1979: The GUI was invented.
1984: Machintosh introduced GUI in their computers
1985: Microsoft introduced GUI on Windows 1
...
2021: Let's use the terminal because is easier to show the file system... Are you serious?
Computers moved from command-line environments to GUI because it's easier for people to See graphically what's going on instead of reading awkward text symbols.
What about the opt directory ?
Sorry for the late reply, the opt directory is for certain software. Like Google Chrome or zoom.
The stock installations, like /var/www is just stock. You are supposed to change that in the configuration when you run it for real. /srv/ is the directory where you actually are supposed to store data for servers. So /srv/www/www.my-site.com/www would be a good place for the webserver virtual site www.my-site.com/
(I don't run my editor with sudo(1), because the makes my home directory stored with config files own by root. I use Emacs and open this filen with Tramp using sudo (Just start emacs and type: C-x C-f /sudo:root@localhost:/etc/packman.conf ), which will open the file as root with sudo on the local machine. It I want to open a file with ssh, I open the file "sft:login@machine:filename.txt" or "ssh:login@machine:filename.txt")
About removing the wrong fingerprint, you the command instead that is recommended when your ssh are stoped. As the IP-number and name usually are encrypted in the known_hosts file and not in clear text like in your command.
It is usually better to save the hosts keys and restore them after the new installation. :-)
just know ... this is the basic of linux File system .. just know that there is a lot of folders, just know there is links and files ;P just know this is funny ;P
Mac OS "TEN". Not Mac OS "EX". The "X" means TEN in roman numerals.
yes as confirmed by Apple here - support.apple.com/kb/TA22541?locale=en_US
No X means decem in Roman numerals.
So please call it OS Decem.
@@stargirl3352 Decem is root for December which is the 12th month. So it's actually Mac OS 12 😜
Anyone can help me with steam in Linux mint 19.2 cinnamon 64bit
Iam having all kinds of slowing issue
did you skipped /opt? I am sleepy, its 12am here in India
/opt as I understand is where "optional" software with non-standard install locations gets installed. The standard place is under /usr
@@fourdotsYT Thanks, I am too a GNU/Linux guy. Just watched this video anyway.
Don't use sudo su. Use sudo -i
Or "sudo su -" which has the same effect. It will start a root session as a login shell (meaning that it will force the shell to execute its startup scripts (like e.g. .bashrc etc).
I wont to download it to my Samsung tablet but it wont can anyone help
i like your intro !! pretty neay...
You should remake this video with a better approach, like using a sort of nice directory's structure slide, and then explaining every directory there.
Great!
When this popped up in my recommendations and I saw that you were using Manjaro, I thought, "great, maybe he'll explain why Arch-based distros use /run/media for mounts but Debian-based use /media". Instead, you skipped /run and went ahead and created /media instead. :-(
The title of this video should be "Linux Directory Structure" instead of "Linux File Sytems". All of the directories you have shown could be in the same file system or in different file systems.
interesting thanks
Can i put two thumbs Up for this post ? Or only one ☹️ RUclips gave only one thumbs Up button
I use to alias "ls -ol" to "lol", so it's funnier to list mi directories.. :V
I Always Work with root beacause I often have to change system files
You skipped a few and some of the ones you mentioned you didn't really explain. You should read this en.wikipedia.org/wiki/Unix_filesystem
FreeBSD is not based on Linux
Whaaat? /sbin -> /usr/bin ? BIN? Not SBIN ? Is it systemd people trying to make Linux the same mess as Windows? Yeah, trolling I know. But seriously, where's the old compartment gone? I mean... why?
I didnt understand one word you said.
Grub man config? WTF? Who are you even talking to?
He finally got away from Chrome!
10:09 my life is a lie
Like 5
/opt
Bookmarked
TYTY
"Don't run any programs as root" while running the ls program as root
Too complex of an explanation, just a suggestion but limiting the file structure to what people would use in the GUI, instead of command line would be useful, for instance this is what this folder is used for here is what types of files it contains, and movie on, there is no need for advanced functions on what you would use the folder/directory for.