What's in a Name? - Linux Namespaces 

Great explanation, thank you!

thank you for sharing your knowledge

Very good explanation, thanks for sharing!

For a user point og view, namespaces are largely invisible. Now snaps may use namespaces and other packaging systems, flatpaks, etc may use them. In the case of snaps the odd loopbacks are visible. The details are not exposed. Until one digs into containers or snaps or similar technology, much of this is hidden. It just works. Or [perhaps it does not. I have had odd bugs appear in a snap based application. This caused me to compile it myself. Now I know they exist, I can be ready to dig in and use them. This is very important. The only encapsulation I had known before this video was the VM. I had been worried because my hardware had few cores and limited memory. Knowing the power namespaces give containers, I now understand I can run containers, in place of entire VMs. The lighter demands of container versus VMs mean they can run on desktops, in the background.. You gave us the reason you no longer need to run an entire OS to run a web server, for example. Many thanks.

How is it everytime I need very niche learning materials you're always there to deliver hahah

amazing explaining !

Thanks DJ! It would be great to know your views on performance benchmarking and optimization.

Thanks man.

Thanks a lot, very well-explained. I am kinda wondering why mount namespace is more secure than chroot?. Is it because changing the root will delegate permission for the whole file system hierarchy, including /etc, /dev ...etc while when you mount x disk you are just appending that specific directory (or volume) to the file system hierarchy, hence, permission is limited to that specific volume? ( As I did understand ). Thanks in advance.

Was Bela Lugosi the first mascot???