Just finished reading the entire operating systems book with the dinosaurs on the cover, and watching these video lectures is helping me memorize and understand the concepts from the book. I appreciate it, thanks
The fork() followed by exec() paradigm seems extremely wasteful, why copy all the data (heap, stack etc.) just to start a completely different program that doesn't need any of that?
at 46:00 after exec() is run , will the pid of the program loaded be same as the child. If it is will the parent stop execution till the loaded program finishes execution?
while(1){ fork() I get that in first iteration it will print 2 because fork duplicates the process. So why in the next iteration are we getting 4 processes? since the while condition while(1) is not met its not 1 after the first iteration it's 2 so why is it spitting out 4?
You should think of the 1 as just true. if it was while(processes == 1) then that would apply now it just runs forever. and since after the first iteration there are now 2 processes so it duplicates those 2 processes which becomes 4.
Just finished reading the entire operating systems book with the dinosaurs on the cover, and watching these video lectures is helping me memorize and understand the concepts from the book. I appreciate it, thanks
hi bro how much time did it take you read the book? I was thinking whether I can directly jump to this playlist or not
@@mango-strawberry hi Aqua, eh I took my time so about a months time
@@CarlC9898 i see. Thanks
@@mango-strawberry you're welcome!
Can I watch the playlist without reading the book, how effective would that be?
Thanks for sharing. He's so much better than my instructor.
Did you pass?
hello beautiful
Thank you for sharing! Amazing resource for studying.
After reading the textbook, the lecture becomes very straight-forward to understand.
which text book did you read ?
which book
@@coding3438 operating system concepts
@@huned786 operating system concepts
@@tedthebed7877 hi bro how much time did it take you read the book? I was thinking whether I can directly jump to this playlist or not
Legendary professor.
The fork() followed by exec() paradigm seems extremely wasteful, why copy all the data (heap, stack etc.) just to start a completely different program that doesn't need any of that?
at 46:00 after exec() is run , will the pid of the program loaded be same as the child. If it is will the parent stop execution till the loaded program finishes execution?
Θα περάσουμε Ξυλωμένο, που θα πάει?
at 5:10 shouldn't th static data segment be below stack??
Great Lecture, Thanks for sharing.
while(1){
fork()
I get that in first iteration it will print 2 because fork duplicates the process.
So why in the next iteration are we getting 4 processes? since the while condition while(1) is not met
its not 1 after the first iteration it's 2 so why is it spitting out 4?
You should think of the 1 as just true. if it was while(processes == 1) then that would apply now it just runs forever. and since after the first iteration there are now 2 processes so it duplicates those 2 processes which becomes 4.
1 is boolean True.
At 44:45.
I guess exec overwrites everyhting in the child PCB EXCEPT the parent process ID, yes?
W
seems like a shared buffer and shared memory are the same
can't see the code...
refer this lass.cs.umass.edu/~shenoy/courses/fall16/lectures/Lec04.pdf
@@piyushpasari4806 thank you!
Much better than the lectures in my school! The lecturer stopped saying "you know". Hopefully, he will stop shaking soon :)
Lol what the heck
k