YOU ARE A GOD AT EXPLAINING! So detailed yet so comprehensive; I which more experts would make video series like this one, for other complicated topics :D
Are you related to the voice behind Casually Explained? Such a striking resemblance in voice and general manner of speaking in my opinion. Anyway, these videos are fantastic even over 13 years later, so thank you! In my case I was wondering about the "-t" flag (force pseudo terminal allocation) of the openssh client program, and why without it a command given as argument to the client would be left running on the remote end after closing the connection by pressing Ctrl+C. And also wondering about the pseudo terminal escape commands, which I didn't even realize have always been present in the typical use case of ssh. I believe these videos helped me understand this better. I still find similar program flags confusing sometimes and I run into them frequently, when executing programs inside containers for example.
Trivial but interesting, we actually had terminals even in the 70s that could display pictures. Intact, Linux servers still support these ancient protocals in case anyone wants to connect a old serial terminal. So terminals had graphics even before xwindows.
1:27 I kept looking at the diagram trying to figure out how the terminal device file is between the process and the "computer" .... only to remember as you just said that back in the days they used a centralized mainframe "computer " with the "keyboard & printer& CRT display" as one of the threads / terminals used by several users .... now and as i'm trying to a unix-like system ... aka gnu/linux they still implement the same principle
Why TTY? Because the created the whole system having only these. „Electronic“ terminals only got cheap after having microcontrollers and crt support chips.
Why must there be both a master and a slave with a pipe in the middle? wouldn't just a single terminal device work since they handle both read and write
Am I really dumb I dont get any of this? You use terminology and you dont explain them. You talk linear without a pause. Just a criticism but other than that. Maybe Im just dumb
He’s doing just fine. You are not dumb you just need to spend a little bit more time with the unix environment if you’re new. :) Ofc the comment is 2 years old, you might know by now.
@@linuxdeveloperuyI dont really think I was dumb, just frustrated is all. And my opinion of the video.I say it as it is, not pretending I get everything he said.
This channel should be shown in every elementary school around the world.
Had to watch it several times to fully grasp it. Truly quality content. Thank you!
This video filled in so many longstanding knowledge gaps for me. Thank you so much for putting this together!
props, sir...good series. I've been coding for 10 years and I learned a thing or two from the series -- much thanks.
This series is INCREDIBLE. Thank you
Videos like this deserve more views. Would benefit slot of self taught coders
It is actually the law that any screenshot illustrating what a GUI is must show the calculator app.
What country(s), why, and source?
r/whoosh
/r/whoosh
@@theterrarian591 r/whoosh there's always someone
I guess I'm kinda randomly asking but do anybody know of a good site to watch new series online ?
The best Explanation...❤️❤️
YOU ARE A GOD AT EXPLAINING! So detailed yet so comprehensive; I which more experts would make video series like this one, for other complicated topics :D
Great great stuff Brian ... I'm waiting on some C linux device driver programming tutorials from you - a sample or a short maybe
Are you related to the voice behind Casually Explained? Such a striking resemblance in voice and general manner of speaking in my opinion. Anyway, these videos are fantastic even over 13 years later, so thank you!
In my case I was wondering about the "-t" flag (force pseudo terminal allocation) of the openssh client program, and why without it a command given as argument to the client would be left running on the remote end after closing the connection by pressing Ctrl+C. And also wondering about the pseudo terminal escape commands, which I didn't even realize have always been present in the typical use case of ssh. I believe these videos helped me understand this better. I still find similar program flags confusing sometimes and I run into them frequently, when executing programs inside containers for example.
Excellent explanation. Best I've seen!
What does master slave solve?
Trivial but interesting, we actually had terminals even in the 70s that could display pictures. Intact, Linux servers still support these ancient protocals in case anyone wants to connect a old serial terminal. So terminals had graphics even before xwindows.
I love your voice, and I love your videos!
Thank you for uploading them :)
Incredible. Thank you.
Thx Brain for another great video 👍
1:27 I kept looking at the diagram trying to figure out how the terminal device file is between the process and the "computer" .... only to remember as you just said that back in the days they used a centralized mainframe "computer " with the "keyboard & printer& CRT display" as one of the threads / terminals used by several users .... now and as i'm trying to a unix-like system ... aka gnu/linux they still implement the same principle
6:16 now ......
great series. thank you
nicely done....I leaned a lot.
I leaned so much, I fell over.
My xorg runs on the first virtual thing.
I have successfully stopped it using systemd and when a stop it
.it reload itself
Why TTY?
Because the created the whole system having only these. „Electronic“ terminals only got cheap after having microcontrollers and crt support chips.
Why must there be both a master and a slave with a pipe in the middle? wouldn't just a single terminal device work since they handle both read and write
Multple terminals need towork together.
Awesome stuff
EBCDIC versus ASCII ... so painful
well ,as a new comer ,it is so difficult actually
王慕言 suggest you see the video in slow pace perhaps 0.25 or something?
This is a nice video bro but be more simple
that was the most simple lesson i ever saw
The "G" is silent in gnome.
stuff.mit.edu/afs/athena/astaff/project/aui/html/pronunciation.html
ua-cam.com/video/P9KkrHsp8cY/v-deo.html
Better one: dictionary.cambridge.org/us/pronunciation/english/gnome
Yes, the English word 'gnome' is pronounced with a silent G. The GNOME project officially pronounces the G, just like GNU.
I figured that was the case. Just hearing it pronounced with the G is weird and kind of annoying. Just doesn't sound right.
Am I really dumb I dont get any of this? You use terminology and you dont explain them. You talk linear without a pause. Just a criticism but other than that. Maybe Im just dumb
It's a confusing architecture. That's true. On the other hand maybe you are simply dumb.
He’s doing just fine. You are not dumb you just need to spend a little bit more time with the unix environment if you’re new. :)
Ofc the comment is 2 years old, you might know by now.
@@linuxdeveloperuyI dont really think I was dumb, just frustrated is all. And my opinion of the video.I say it as it is, not pretending I get everything he said.
@@minhajsixbyte thanks I work as a dev , I understand most of it now, but my critic of the vid stands. 👍
You talk slightly fast - as your conversations are dense I suggest seeing them at slow pace for those who are not as enlightened
You can adjust the speed of the vid to 0.75x by clicking on the settings wheel at the bottom of the video window :)