This and Hardware basics are the only things you need to see to know how computers work. I learned this all at university but often I missed forest for the trees. These series rounded all the things in my head nicely. I think I'll have to watch every single video on this channel.
When this video started out, I thought it was going to be a sleeping pill. I was wrong, I have a LOT more confidence in what an operating system is and the components of. Thank you, Mr. Will.
These are fantastic. Clear explanation, dense yet succinct and non-redundant. I am taking notes and rewatching. Finally the mystery of the computer is starting to disentagle!
Hey Brian, Just seeing this video and I have to say, there is a need for more content like this. Most high level developers don't understand some of these fundamentals and its really important
I had my final today in an Operating Systems class and all of this stuff would've been so useful to see earlier. When I watched this, I was able to follow very well. It was nice to see the order you presented everything, it had a nice flow to it :3
Brian these videos are great. I've just discovered your channel and I hope I end up watching them all. It's good to have a theoretical understanding of the things that underlie my own work which is coding in a scripting language. Keep 'em coming!
I agree. Its rare to find people with expertise that make such videos. Him, Ben Eater, and 3B1B are the smartest and most knowledgable when it comes to math and computer science in general
Oops. At around 20:00, I say that, within a directory, you can have both a file and directory of the same name, e.g. a file named foo and a directory named foo. This is wrong: every file/directory name must be unique within the containing directory.
PENDANTturnips I agree. He chooses his words very carefully to pack a lot of information into a single sentence. I have to pause once in a while to absorb what he says, you could try that out :)
+Brian I like the speed at which you explain things. I'm sick of videos that have little information and worse of all repeat the exact same things over and over again. Sure sometimes instructors talk too fast, but I prefer informative versus redundant.
Man I wish you would regularly make videos you come up with awesome, important and interesting content people working in tech these days really need to know
12:30 Damn I remember having to restart flash games back in the day because they would crash after a while because of memory leaks, nice to somewhat understand why now
This is a good video. I like the fact that you put the word "Basics" into the title. You are describing an OS using a monolithic structure. This is an understandable prejudice since Windows, Unix, Linux and Mac OS use this structure, however it is not the only possible OS architecture.
What a fantastic video. I’ll have to make a point though. Although this video says basics, it’s not for beginners. It’s for those who already know most of these concepts, although not clearly and thoroughly, and can use this video as a guide to strengthen basic concepts. Once again, fantastic video!
It's a 23 minute video, but since I've only watched this video of yours as a standalone, you've spewed so much information that it took me over two hours to just decipher it all Especially since you speak so fast, and there's little graphic description to accompany the verbal barrage
Intel's Hyperthreading adapts superscaling to run multiple threads (usually 2) on one core. Effectively, the OS can treat one core as 2 'logical' cores'. I've seen conflicting reports of how effective this is, so I can't say whether it's better to run two threads on the same physical core, or on separate physical cores, or whether it doesn't matter.
You need quite a bit of knowledge already to really make much use of this video. For anyone who wants to really understand this video I recommend watching ISA MIPS, OS process handling (interrupts and process control blocks), device drivers vs. device controllers, Filesystems and Partitions tutorials before watching this.
When he explained how the stack memory and heap and everything was allocated and mapped I started thinking that it just seemed very inefficient. I know that's how it works but still, I think there's a better way. Also I think those fragmented heaps could be handled. Maybe not prevented but definitely handled by without human intervention.
The bottom-up address space seems to make sense for the little-endian storage of data...especially to an Irish viewer (as Ogham script is literally just etched upward along a sharp edge on a rock or a post). Except...execution of code progresses up the addresses too, and Logisim, for one thing, shows data addresses increasing DOWN the ROM and RAM.
According to my understanding, page fault is when cpu generates an address whose page is not on ram and we need to bring that page to ram from hard disk.
Modern computers rely so heavily on the hardware not messing up any numbers. I suppose sometimes they have error correction with stuff like Hamming codes.
How does this all work when it involves virtual machines? How does a hypervisor deal with an os that is demanding direct hardware access? How was it accomplished before CPU's gave extra support for such? Nested hypervisors?
Swap made more sense when the difference between the speed of system memory and disks was much smaller, and there were hard logical limits to the size of system memory that could be exhausted easily. Most modern computers should not use swap. They should instead use something like an oom killer to detect which processes are incapable of gracefully handling OOM conditions, and start slaying them based on how poorly they handle the state. On top of this, system critical software needs to be able to detect and gracefully handle OOM conditions. It is almost never acceptable to start swapping memory to disk for modern systems. It's effectively no different than just powering the system down and leaving it off. A swapping system cannot respond in time to be considered functional in almost any instance.
If a CPU had a voice, this is it.
We need a Mr.Data Text-to-speech lol :D
He has a good voice, it's clear and easy to listen to.
And GPU would be his wife.
That is a great comment
**he sounds like technoblade**
that is the best voice from tutorials I ever heard.
This is THE best OS intro I found so far in youtube.
still the best one?
This and Hardware basics are the only things you need to see to know how computers work. I learned this all at university but often I missed forest for the trees. These series rounded all the things in my head nicely. I think I'll have to watch every single video on this channel.
don't listen to this guy, this video doesn't even summarily scratch the surface of the subject.
@@mrb180don’t listen to this guy, this comment doesn’t even summarily scratch the surface of intelligence
When this video started out, I thought it was going to be a sleeping pill. I was wrong, I have a LOT more confidence in what an operating system is and the components of. Thank you, Mr. Will.
I love this video. I turn it on from time to time just to hear his voice and refresh my knowledge. Thanks Brian
Deep voice is deep.
...and monotone
@@saveUyghurs yes
These are fantastic. Clear explanation, dense yet succinct and non-redundant. I am taking notes and rewatching. Finally the mystery of the computer is starting to disentagle!
Hey Brian, Just seeing this video and I have to say, there is a need for more content like this. Most high level developers don't understand some of these fundamentals and its really important
My eyes were begging me to let them rest, but I had to finish the video. Unreal clarity in your explanations! Most would need 1h to do the same.
I had my final today in an Operating Systems class and all of this stuff would've been so useful to see earlier. When I watched this, I was able to follow very well. It was nice to see the order you presented everything, it had a nice flow to it :3
Brian these videos are great. I've just discovered your channel and I hope I end up watching them all. It's good to have a theoretical understanding of the things that underlie my own work which is coding in a scripting language. Keep 'em coming!
Best CS video on the Internet. Period.
This man actually sounds like he knows what he is talking about
Unlike most random OSdev tutorials on UA-cam
I agree. Its rare to find people with expertise that make such videos. Him, Ben Eater, and 3B1B are the smartest and most knowledgable when it comes to math and computer science in general
It feels like I'm connected through the matrix and your voice is like Morpheus injecting information into my head
I like it, subscribed.
thanks champ.
Oops. At around 20:00, I say that, within a directory, you can have both a file and directory of the same name, e.g. a file named foo and a directory named foo. This is wrong: every file/directory name must be unique within the containing directory.
God damn I love your videos, but one thing I have to criticize is that sometimes you talk too fast.
PENDANTturnips I agree. He chooses his words very carefully to pack a lot of information into a single sentence. I have to pause once in a while to absorb what he says, you could try that out :)
+Brian I like the speed at which you explain things. I'm sick of videos that have little information and worse of all repeat the exact same things over and over again. Sure sometimes instructors talk too fast, but I prefer informative versus redundant.
Brian Will Thank you. Thank you, thank you, thank you! Very informational. Very detailed, very in depth yet quite understandable. I loved it.
I think this video is perfect for preparing half a semester of an operating system course. Thank you, Sir.
A complete refresher on Operating Systems. Took me back to college days!
It’s a really really enjoyable thing to listen to your voice. I mean, the tone and fluency of your voice exaggerate the effect of my study. Thank you!
Man I wish you would regularly make videos you come up with awesome, important and interesting content people working in tech these days really need to know
If you change the speed to 0.5, it gives the illusion that Brian sounds drunk! Great videos Brian, thanks!
Luke Griffiths i
He was actually drunk recording this and sped it up later.
amazing.
you are one of my favorite computer topic explainers
you are gifted. keep sharing the gift
12:30 Damn I remember having to restart flash games back in the day because they would crash after a while because of memory leaks, nice to somewhat understand why now
wow thanks this really helped my find out whether to get a Manuel or auto transmission in my new ute.
What a clear straight forward video, really good
This is a good video. I like the fact that you put the word "Basics" into the title. You are describing an OS using a monolithic structure. This is an understandable prejudice since Windows, Unix, Linux and Mac OS use this structure, however it is not the only possible OS architecture.
Excellent presentation of OS Basics. Thank you!
What a fantastic video. I’ll have to make a point though. Although this video says basics, it’s not for beginners. It’s for those who already know most of these concepts, although not clearly and thoroughly, and can use this video as a guide to strengthen basic concepts.
Once again, fantastic video!
A great, condensed and clear summary. Thanks Brian
watched the whole thing in one sitting… Feeling High! Thanks For The Valuable Information!! Liked Your Voice.
bruh it's only 23 mins long lol
@@HK-sw3vi bruh it's a 3 year old comment :p
This is great, well presented and the voice was perfect for me to follow.
A joy, this video is a joy..
And tge channel is a treasure.
This dude's videos are the fundamentals that all these coding boot camps don't teach you, but should know.
The architecture I have been working on eliminates the need for pre-emptive multitasking
It's a 23 minute video, but since I've only watched this video of yours as a standalone, you've spewed so much information that it took me over two hours to just decipher it all
Especially since you speak so fast, and there's little graphic description to accompany the verbal barrage
this video is good after you have studied the topic as a sort of checklist recap to make sure you understand everything
You've explained everything pretty well.
Thank you for the video.
This is really educational and well explained. I just wish your voice didn't make me so sleepy.
Intel's Hyperthreading adapts superscaling to run multiple threads (usually 2) on one core. Effectively, the OS can treat one core as 2 'logical' cores'. I've seen conflicting reports of how effective this is, so I can't say whether it's better to run two threads on the same physical core, or on separate physical cores, or whether it doesn't matter.
This is the same way the an OS can treat one disk as two "logical" disks.
It is always better to have two separate physical cores than to interleave two threads on the same core.
Bruh... Your videos are SO informative ! Really love them!
You need quite a bit of knowledge already to really make much use of this video. For anyone who wants to really understand this video I recommend watching ISA MIPS, OS process handling (interrupts and process control blocks), device drivers vs. device controllers, Filesystems and Partitions tutorials before watching this.
thanks, fam. I was confused. Doing my individual research before heading to the proper IT fields.
What tutorials did you read? Mind linking a few you found useful? I am rusty on OS fundamentals.
concise agnostic overview of OS (and some CPU) fundamentals. thank you.
I can't stress how helpful your videos are. I love u c:
Video Well made. Very on point. I love it when people put effort into their work.
Exactly the kind of content I was looking for! Thanks a lot :)
great video!!' english is not my mother tongue however i managed to grasp your lecture by the plain and descriptive presentation
When he explained how the stack memory and heap and everything was allocated and mapped I started thinking that it just seemed very inefficient. I know that's how it works but still, I think there's a better way.
Also I think those fragmented heaps could be handled. Maybe not prevented but definitely handled by without human intervention.
Your audio quality is really nice.
This is a really clear explanation. Thank you Brian!
best video on UA-cam
Oh so that's what "stack overflow" means, I feel like I'm in on a very nerdy joke now
same haha
thanks for this video.
just today i started learning this course
Awesome video, just as informative as any college lecture. Thanks for making!
Great video. One of the best I've watched. Thank you.
The bottom-up address space seems to make sense for the little-endian storage of data...especially to an Irish viewer (as Ogham script is literally just etched upward along a sharp edge on a rock or a post). Except...execution of code progresses up the addresses too, and Logisim, for one thing, shows data addresses increasing DOWN the ROM and RAM.
But when a stack overflow occurs on my computer, I usually solve my programming problems!
This is exactly what I was looking for thank you
Nice explanation. You're definitely talented in knowledge sharing, thank you!
Amazing summary! Thank you good sir!
Great video. packed with information
Brilliantly explained !
Absolutely phenomenal , loved it , thanks much
Big fan of Brain's. Informative. Pithy. Thanks.
These videos are excellent
Excellent fucking video. So many questions answered. Thanks a bunch!
This video is brilliant!
Thank Brian for this awesome video, it helps me alot!
this is incredible
I wonder what it takes to know so much about computers. What level of formal education do you have?
Brian, you are doing god's work! Keep up :)
Brian Will make informative videos.
You sound like a radio host lol. Great video!
According to my understanding, page fault is when cpu generates an address whose page is not on ram and we need to bring that page to ram from hard disk.
i don't understand what you said...but i love your voice.. :D
Very nice, thank you for explanations!
Great video 👍
Its a very nice and useful tutorial ..
Thank You.!
"Still, creating multiple partitions serves some niche use-cases"
Like running OpenBSD.
Still helpful till this day
This was very helpful. Thank you!
This is awesome.
Can you further make videos about the type of operating systems more specifically Unix and LInux
Awesome video. Thank you!
You got one badass voice.
Wow this is great video and I learned so much thanks a lot! Keep it up
You have covered at least 50 pages of 'How Linux Works'
great video
Very good ! ... thanks for making this video
Brilliant, thank you.
Brian Will ... Amazing! you still about creating content? I see this video is from 2013
Really informative one....but your voice requires a lot of focus to understand
Modern computers rely so heavily on the hardware not messing up any numbers. I suppose sometimes they have error correction with stuff like Hamming codes.
GREAT, informative
Amazing !!!
How does this all work when it involves virtual machines? How does a hypervisor deal with an os that is demanding direct hardware access? How was it accomplished before CPU's gave extra support for such? Nested hypervisors?
OMG DUDE THIS VIDEO IS SO COOL!! SO EDUCATIVEE! TY!! IF YOU CAN , please meake more videos like this :D they are so cool!
That C: drive is REALLY happy...
:)
:)
Why do we switch from the user's stack to a kernel stack when we enter the kernel ( e.g. for a system call ) ?
this is pretty awesome!
nice video!
Swap made more sense when the difference between the speed of system memory and disks was much smaller, and there were hard logical limits to the size of system memory that could be exhausted easily. Most modern computers should not use swap. They should instead use something like an oom killer to detect which processes are incapable of gracefully handling OOM conditions, and start slaying them based on how poorly they handle the state.
On top of this, system critical software needs to be able to detect and gracefully handle OOM conditions. It is almost never acceptable to start swapping memory to disk for modern systems. It's effectively no different than just powering the system down and leaving it off. A swapping system cannot respond in time to be considered functional in almost any instance.
Can we get access to the slides that are presented in this video, it's a very good and informative video ?