Operating System Basics

Essential concepts of operating systems. Part of a larger series teaching programming. Visit codeschool.org

[@Euquila]

If a CPU had a voice, this is it.

[@Microphunktv-jb3kj]

We need a Mr.Data Text-to-speech lol :D

[@m.a.156]

He has a good voice, it's clear and easy to listen to.

[@blinded6502]

And GPU would be his wife.

[@margaritashamrakov]

That is a great comment

[@appledoes6304]

**he sounds like technoblade**

[@AndriyLinnyk]

that is the best voice from tutorials I ever heard.

[@Oneworld87]

Deep voice is deep.

[@saveUyghurs]

...and monotone

[@nachocheese8344]

@@saveUyghurs yes

[@Verses01]

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.

[@kokorodokoro]

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!

[@voilin]

I love this video. I turn it on from time to time just to hear his voice and refresh my knowledge. Thanks Brian

[@odytrice]

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

[@lukegriffiths4333]

If you change the speed to 0.5, it gives the illusion that Brian sounds drunk! Great videos Brian, thanks!

[@邓有帮]

Luke Griffiths i

[@absconditus8660]

He was actually drunk recording this and sped it up later.

[@mrcobalt124]

This man actually sounds like he knows what he is talking about Unlike most random OSdev tutorials on KZbin

[@Artaxerxes.]

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

[@mankindspatience]

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.

[@tomerlevi8598]

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.

[@lukegriffiths4333]

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!

[@glueee2621]

Best CS video on the Internet. Period.

[@samrrocks]

A complete refresher on Operating Systems. Took me back to college days!

[@patturnweaver]

amazing. you are one of my favorite computer topic explainers you are gifted. keep sharing the gift

[@WindyHellLetsLoose]

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!

[@16yearoldwhiteboy]

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

[@mariusc6882]

Excellent presentation of OS Basics. Thank you!

[@stashatstake]

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

[@thotsi]

this video is good after you have studied the topic as a sort of checklist recap to make sure you understand everything

[@sagarkapasi099]

watched the whole thing in one sitting… Feeling High! Thanks For The Valuable Information!! Liked Your Voice.

[@HK-sw3vi]

bruh it's only 23 mins long lol

[@sagarkapasi099]

@@HK-sw3vi bruh it's a 3 year old comment :p

[@Sentom23]

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

[@coding3438]

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!

[@Yazan_Majdalawi]

A joy, this video is a joy.. And tge channel is a treasure.

[@briantwill]

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.

[@NeelSandellISAWESOME]

This is the same way the an OS can treat one disk as two "logical" disks.

[@markteague8889]

It is always better to have two separate physical cores than to interleave two threads on the same core.

[@studioussoul2303]

This is great, well presented and the voice was perfect for me to follow.

[@Skellingtor]

A great, condensed and clear summary. Thanks Brian

[@davidprock904]

The architecture I have been working on eliminates the need for pre-emptive multitasking

[@Ricky-zc8qm]

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.

[@jay1jayf]

thanks, fam. I was confused. Doing my individual research before heading to the proper IT fields.

[@Bakugantsuvai1]

What tutorials did you read? Mind linking a few you found useful? I am rusty on OS fundamentals.

[@haydengalloway5177]

This is really educational and well explained. I just wish your voice didn't make me so sleepy.

[@CanMetan]

You've explained everything pretty well. Thank you for the video.

[@thomascarlsen8097]

Bruh... Your videos are SO informative ! Really love them!

[@Tray2323FTW]

But when a stack overflow occurs on my computer, I usually solve my programming problems!

[@김장근-j8j]

great video!!' english is not my mother tongue however i managed to grasp your lecture by the plain and descriptive presentation

[@anteconfig5391]

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.

[@mrtpsoroush]

I wonder what it takes to know so much about computers. What level of formal education do you have?

[@jonassteinberg3779]

concise agnostic overview of OS (and some CPU) fundamentals. thank you.

[@StrangeIndeed]

I can't stress how helpful your videos are. I love u c:

[@TheRojo387]

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.

[@DominicVictoria]

Video Well made. Very on point. I love it when people put effort into their work.

[@jonathansera6134]

Awesome video, just as informative as any college lecture. Thanks for making!

[@nukkable]

best video on KZbin

[@pengyuanchen3080]

This is a really clear explanation. Thank you Brian!

[@CRadiusOfficial]

Great video. One of the best I've watched. Thank you.

[@bafanidus]

Nice explanation. You're definitely talented in knowledge sharing, thank you!

[@75hilmar]

Your audio quality is really nice.

[@gregs6178]

Great video. packed with information

[@s7362454]

thanks for this video. just today i started learning this course

[@dubzy21]

This is exactly what I was looking for thank you

[@DaneDuPlessis]

Big fan of Brain's. Informative. Pithy. Thanks.

[@kiennguyen1387]

Thank Brian for this awesome video, it helps me alot!

[@pedersen268]

Amazing summary! Thank you good sir!

[@smorrow]

"Still, creating multiple partitions serves some niche use-cases" Like running OpenBSD.

[@evidence-vs8bd]

You have covered at least 50 pages of 'How Linux Works'

[@khushbuagarwal2281]

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.

[@ryanarborist]

Brian Will make informative videos.

[@89Valkyrie]

Excellent fucking video. So many questions answered. Thanks a bunch!

[@XolisileBuqwana]

Can you further make videos about the type of operating systems more specifically Unix and LInux

[@petevenuti7355]

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?

[@BillEngwall]

Brian, you are doing god's work! Keep up :)

[@nikhilgumidelli6308]

Brilliantly explained !

[@aragorn420]

this is incredible

[@arkoraa]

You sound like a radio host lol. Great video!

[@w3w3w3]

Brian Will ... Amazing! you still about creating content? I see this video is from 2013

[@Alex2Buzz]

That C: drive is REALLY happy...

[@jayant9151]

:)

[@ahuttee]

:)

[@Skellingtor]

These videos are excellent

[@briantwill]

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]

God damn I love your videos, but one thing I have to criticize is that sometimes you talk too fast.

[@Abdullah-mg5zl]

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 :)

[@VenturaPiano]

+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.

[@rowanjugernauth5519]

Brian Will Thank you. Thank you, thank you, thank you! Very informational. Very detailed, very in depth yet quite understandable. I loved it.

[@ahmadsaeedkhattak20]

I think this video is perfect for preparing half a semester of an operating system course. Thank you, Sir.

[@MyFunnyWeekend]

Very nice, thank you for explanations!

[@GaneshNarvane]

Its a very nice and useful tutorial .. Thank You.!

[@انميانمي-ن7ن]

Why do we switch from the user's stack to a kernel stack when we enter the kernel ( e.g. for a system call ) ?

[@nekuuu]

This video is brilliant!

[@nicholaswjamrock]

you stated that linux dont use drive letters, that is not 100% accurate, it just dont present them like windows,eg. dev/sda2/user/cody/desktop. where "a" in sda is the first drive that is detected and the "2 " is the second partition.

[@cyrilemeka6987]

10:16 don't programming languages like C++ or C set the stack boundary?

[@anvilanvil1400]

This was very helpful. Thank you!

[@Mr.Nichan]

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.

[@amanisnotreal]

Still helpful till this day

[@anonymoussloth6687]

How is the program actually ran? U said that when we return from a stack frame, we use the return address to go back to the parent call. But the actual instructions are stored in the stack? Or does this return address reference memory to the instructions stored in the text area of the memory?

[@MaxPicAxe]

Wow this is great video and I learned so much thanks a lot! Keep it up

[@iexclusive4u]

@ 21:13 does it means that "partition 1" resides under "partition 2" and then "partition 3" resides under "partition 1" and therefore partition 1 & 3 are the subset of partition 2 ?

[@Felix-ve9hs]

so now i know what Java means with "stack overflow" ... all my minecraft Shader Mods were just producing too many system calls ...

[@grott0]

Awesome video. Thank you!

[@Bestietvcute]

Very good ! ... thanks for making this video

[@ntag411]

I need to look for a more basic understanding. Such as the computer only understands numbers. Inputs from the keyboard goes thru a translation into a group of number(s), I think.

[@LoTekkie]

Brilliant, thank you.

[@patrickmullen2914]

Great video 👍

[@piyushgarg3738]

Can we get access to the slides that are presented in this video, it's a very good and informative video ?

[@kundaimudzingwa5071]

GREAT, informative

[@vortyx090]

OMG DUDE THIS VIDEO IS SO COOL!! SO EDUCATIVEE! TY!! IF YOU CAN , please meake more videos like this :D they are so cool!

[@CristalCody]

You got one badass voice.

[@DominicVictoria]

How about machine learning code? Doesn’t those codes change on runtime?

[@scifregizmoguy]

I don't know if it's your deep voice or the video but my laptop speakers are having a hard time playing this at a good enough volume.

[@JournalKannada]

Should I learn operating system first computer organisation and architecture first in order to have to great understanding

[@melvin4524]

Read "Computer systems, a programmers perspective (2001)". Its got all fundamentals you need

[@homelessrobot]

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.

[@puritynganga4310]

great video

[@axel_r_]

Waiting for him to say "Hi folks, this is Rhykker".

[@lucasa8710]

I'm felling so old right now 😢 "the last version of windows, windows 8"

[@Pururin_Purin]

Amazing, I did not understand a single thing

[@chrissxMedia]

this is pretty awesome!

[@i512]

I heard that instruction pipeline allows one core to work with several instruction threads at the same time, I thought that those threads are the processes running simultaneously. But you say that one core is capable of executing one thread at a time. So a single process is actually divided into several threads or what?

[@MechanicaMenace]

The pipeline how stuff moves through the whole CPU, load store unit, control unit, mmu, alu, fpu, etc. Pipelining allows you to start say loading the next instruction while you're still running the last.

[@thomascarlsen8097]

Do you know about the Linux From Scratch (LFS) project, and can you pretty-please make a video about that? :)

[@AlantePowell]

Stackoverflow.com suddenly seems like a brilliant domain name.