aboutsummaryrefslogtreecommitdiff
path: root/en_US.ISO8859-1/captions/2006/mckusick-kernelinternals/mckusick-kernelinternals-1.sbv
diff options
context:
space:
mode:
Diffstat (limited to 'en_US.ISO8859-1/captions/2006/mckusick-kernelinternals/mckusick-kernelinternals-1.sbv')
-rw-r--r--en_US.ISO8859-1/captions/2006/mckusick-kernelinternals/mckusick-kernelinternals-1.sbv72
1 files changed, 36 insertions, 36 deletions
diff --git a/en_US.ISO8859-1/captions/2006/mckusick-kernelinternals/mckusick-kernelinternals-1.sbv b/en_US.ISO8859-1/captions/2006/mckusick-kernelinternals/mckusick-kernelinternals-1.sbv
index f094452547..16dcca9e84 100644
--- a/en_US.ISO8859-1/captions/2006/mckusick-kernelinternals/mckusick-kernelinternals-1.sbv
+++ b/en_US.ISO8859-1/captions/2006/mckusick-kernelinternals/mckusick-kernelinternals-1.sbv
@@ -393,14 +393,14 @@ broad brush high level
description of what's going on
0:05:50.569,0:05:54.719
-and then I will go back and i'll go through the
+and then I will go back and I'll go through the
same material again but at a lower level of
0:05:54.719,0:05:55.300
detail
0:05:55.300,0:05:59.939
-then i finally go back and go through a very nittily
+then I finally go back and go through a very nittily
low-level of detail
0:05:59.939,0:06:04.649
@@ -419,7 +419,7 @@ when I get to the end of one of those nearly
low level niggly details
0:06:14.190,0:06:17.900
-i'll give you a clue as i will say ""Brain
+I'll give you a clue as I will say ""Brain
reset, I'm starting a new topic"" so even if
0:06:17.900,0:06:19.330
@@ -464,7 +464,7 @@ outline of what we're going to try and do here
here
0:06:56.919,0:07:01.169
-As i said we're going to go roughly
+As I said we're going to go roughly
0:07:01.169,0:07:03.270
just about two-and-an-half hours of lecture
@@ -506,7 +506,7 @@ and then
you have to sort of layout terminology
0:07:29.739,0:07:32.080
-although we use normal english words
+although we use normal English words
0:07:32.080,0:07:34.419
they have
@@ -848,7 +848,7 @@ is
0:12:28.660,0:12:33.440
one well let me just give it as a bit
-of advice to the class esspecially those of
+of advice to the class especially those of
0:12:33.440,0:12:36.780
you who work in system administration.
@@ -1013,7 +1013,7 @@ because that just leads to trouble.
0:14:59.390,0:15:03.390
But Filesystems think they have buffers and so
-there's this manouver where we make
+there's this maneuver where we make
0:15:03.390,0:15:06.149
these things that look like what historically
@@ -1054,7 +1054,7 @@ which is %uh more commonly used
for example what is used by ext3
0:15:39.630,0:15:41.179
-and so i'll go through soft updates and
+and so I'll go through soft updates and
0:15:41.179,0:15:45.260
a lot of the issues in soft updates are the
@@ -1091,7 +1091,7 @@ if
0:16:12.500,0:16:15.920
you've worked with things like the network
-appilance box you're probably quite
+appliance box you're probably quite
0:16:15.920,0:16:19.640
aware of what snapshots are and how they do
@@ -1302,7 +1302,7 @@ read that paper if you say yeah yeah yeah
yeah yeah you are done with Week 8.
0:19:18.279,0:19:20.590
-on the other hand if you dont come to Week
+on the other hand if you don't come to Week
8
0:19:20.590,0:19:22.790
@@ -1449,7 +1449,7 @@ iteration of what the actual protocols
are
0:21:22.440,0:21:24.940
-i'll talk primarily about IPv4
+I'll talk primarily about IPv4
0:21:24.940,0:21:31.940
but I will also try and talk a bit about
@@ -1540,7 +1540,7 @@ or is it
0:22:37.309,0:22:42.220
being overrun because we're simply trying
-to do too much on this machine?,etc.
+to do too much on this machine? etc.
0:22:42.220,0:22:45.440
so that's the sort of level of thing that we're
@@ -1721,7 +1721,7 @@ for the core processor and the one which
should be the floating point unit and several
0:25:20.030,0:25:24.080
-of them that would be the memory the core momory
+of them that would be the memory the core memory
literally the core memory
0:25:24.080,0:25:29.110
@@ -1993,10 +1993,10 @@ what the interfaces that they had there
0:28:52.669,0:28:58.660
was one that had these characteristics
- had a a paged virtual address space
+had a paged virtual address space
0:28:58.660,0:29:02.980
-so you din't have to know as in the old days how much physical
+so you didn't have to know as in the old days how much physical
memory is on the machine and make your application
0:29:02.980,0:29:04.740
@@ -2148,7 +2148,7 @@ time
AT&T bell laboratories
0:31:17.129,0:31:19.750
-the big industrial labratory at that time
+the big industrial laboratory at that time
0:31:19.750,0:31:21.380
and MIT
@@ -2357,7 +2357,7 @@ what it references in order to be able to read
and write that thing
0:34:07.940,0:34:11.290
-so if i hand you a descriptor
+so if I hand you a descriptor
you can read from that the descriptor or you can write
0:34:11.290,0:34:13.259
@@ -2391,7 +2391,7 @@ file, close a file
0:34:33.419,0:34:37.429
and there was another set of system calls which
-would open a terminal,read a terminal, write terminal,
+would open a terminal, read a terminal, write terminal,
0:34:37.429,0:34:38.089
close terminal
@@ -2400,7 +2400,7 @@ close terminal
and yet another one
0:34:39.210,0:34:42.409
-which was create a pipe,read a pipe,
+which was create a pipe, read a pipe,
write a pipe and so on.
0:34:42.409,0:34:47.699
@@ -2415,11 +2415,11 @@ my input a terminal which in case I need to
use the read terminal
0:34:53.159,0:34:57.419
-or is it a file which in case i need
+or is it a file which in case I need
to use read file or is it a pipe in which in case
0:34:57.419,0:34:59.189
-i need to use read pipe
+I need to use read pipe
0:34:59.189,0:35:01.860
and so the program itself had to have all
@@ -2533,7 +2533,7 @@ virtual machines
Okay? so far so good?
0:36:22.499,0:36:24.719
-all right so i said that there were
+all right so I said that there were
0:36:24.719,0:36:27.160
two key ideas that UNIX had
@@ -2691,7 +2691,7 @@ get your deck pull out the card, and type the
new one, put it back in and re-submit it
0:38:25.239,0:38:28.729
-As heaven forbid you couldnt touch that
+As heaven forbid you couldn't touch that
card reader you know, it had to be done by
0:38:28.729,0:38:29.970
@@ -2893,7 +2893,7 @@ behind you those pipes were actually implemented
as files
0:41:15.809,0:41:19.319
-but you didn't have atleast to remember to create
+but you didn't have at least to remember to create
them and delete them
0:41:19.319,0:41:20.200
@@ -3049,7 +3049,7 @@ or it may in fact be things that the program
is bringing down upon itself
0:43:22.339,0:43:25.590
-such as a segment fault,a divide by zero
+such as a segment fault, a divide by zero
0:43:25.590,0:43:26.910
and some other
@@ -3122,10 +3122,10 @@ it just compute something all we really care
about is how long it takes them to compute
0:44:23.249,0:44:24.959
-we dont actually care what the answer is
+we don't actually care what the answer is
0:44:24.959,0:44:26.019
-In theory we dont
+In theory we don't
0:44:26.019,0:44:29.779
I personally like my benchmark stop with
@@ -3342,7 +3342,7 @@ I'll go more into some detail about how that
actually gets implemented
0:47:18.899,0:47:22.729
-but in essense you can think of it
+but in essence you can think of it
is is there sort of this whaling Wall and these little
0:47:22.729,0:47:24.990
@@ -3455,7 +3455,7 @@ it looks a lot like any other library that
you would write if you look at top half kernel
0:48:45.539,0:48:49.640
-code you know you see all read,come in
+code you know you see all read, come in
it's got these parameters we Mark around we
0:48:49.640,0:48:53.719
@@ -3576,7 +3576,7 @@ and if you actually
then go to sleep.oh man
0:50:17.219,0:50:20.469
-you didnt tell us you're going to do this we
+you didn't tell us you're going to do this we
have to go off to do a whole lot of other work
0:50:20.469,0:50:23.029
@@ -3715,7 +3715,7 @@ and they try to allocate memory and it's not
available
0:52:01.689,0:52:05.049
-they historically coudnt wait for memory to be
+they historically couldn't wait for memory to be
available
0:52:05.049,0:52:08.380
@@ -3934,7 +3934,7 @@ that is what you normally use there are other
schedulers like the real time scheduler
0:55:01.360,0:55:02.869
-where what I'm saying isnt that true
+where what I'm saying isn't that true
0:55:02.869,0:55:05.709
we'll talk about some of the schedulers was
@@ -4110,7 +4110,7 @@ address space
this of course is desirable because
0:57:23.759,0:57:27.059
-when you're running in this unprevileged
+when you're running in this unprivileged
mode
0:57:27.059,0:57:28.300
@@ -4176,7 +4176,7 @@ to do whatever they want
0:58:13.109,0:58:16.730
whereas when you're running in unprivileged
-mode you cant write those kinds of
+mode you can't write those kinds of
0:58:16.730,0:58:20.179
of things
@@ -4186,7 +4186,7 @@ so modern versions of Windows anything from about
2000 on
0:58:24.119,0:58:26.630
-now run with privileged and unprevileged mode
+now run with privileged and unprivileged mode
0:58:26.630,0:58:28.649
but UNIX has always required that
@@ -4198,7 +4198,7 @@ and so when you're running an
user process
0:58:31.319,0:58:33.389
-you cannot block i mean
+you cannot block I mean
0:58:33.389,0:58:37.969
you cannot execute the instructions which