If a CPU had a voice, this is it.

that is the best voice from tutorials I ever heard.

This is THE best OS intro I found so far in youtube.

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.

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.

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

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!

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

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

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

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

Deep voice is deep.

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.

Best CS video on the Internet. Period.

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!

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.

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!

Oh so that's what "stack overflow" means, I feel like I'm in on a very nerdy joke now

This dude's videos are the fundamentals that all these coding boot camps don't teach you, but should know.

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.

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

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

Excellent presentation of OS Basics. Thank you!

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

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!

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

A great, condensed and clear summary. Thanks Brian

What a clear straight forward video, really good

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.

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

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.

wow thanks this really helped my find out whether to get a Manuel or auto transmission in my new ute.

Exactly the kind of content I was looking for! Thanks a lot :)

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

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

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

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

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

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

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

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.

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

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

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

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

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

Thanks; This is the best OS intro. vid.

This is a really clear explanation. Thank you Brian!

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

best video on KZfaq

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.

Great video. packed with information

This is exactly what I was looking for thank you

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

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

You sound like a radio host lol. Great video!

Your audio quality is really nice.

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

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

Absolutely phenomenal , loved it , thanks much

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

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

Amazing summary! Thank you good sir!

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?

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?

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

Brilliantly explained !

That C: drive is REALLY happy...

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.

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

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

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

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

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.

These videos are excellent

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

Hi Brian, The linked url for the full series seems to be down. Is there any alternative site for the series?

Very nice, thank you for explanations!

This video is brilliant!

@ 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 ?

This was very helpful. Thank you!

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

this is incredible

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

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.

Brilliant, thank you.

Awesome video. Thank you!

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

Brian Will make informative videos.

Still helpful till this day

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.

uhhh if i have C:/house/window.txt and let say C is partition 1 does that mean file window.txt is a file in partition 1 that can only be access by house directory right? but if in the house directory I have another file call door.exe does that mean door.exe is a file in partition 1 and can be access by house directory too? that mean directory house can link to 2 file?? Im pretty sure i misunderstand something. help pls Im confuse.

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

Hello Brian, nice video, rly gave me the understanding of the basics. However nearly at 13:49 you are saying that each process can only access the RAM that was specifically mapped to it by an OS. Then how do cheat engine and similar programs work? They are able to access the memory of other processes or?

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

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.

Very good ! ... thanks for making this video