Looking for books & other references mentioned in this video? Check out the video description for all the links! Want early access to videos & exclusive perks? Join our channel membership today: ruclips.net/channel/UCs_tLP3AiwYKwdUHpltJPuAjoin Question for you: What’s your biggest takeaway from this video? Let us know in the comments! ⬇
UNIX was developed starting in 1969, by Ken Thompson, Dennis Ritchie and a couple other folks, not at Berkeley, but at AT&Ts Bell Labs. Berkeley university didn’t have anything to do with UNIX until 1977 when they created the Berkeley Source Distribution, or BSD. Fun fact, UNIX from V4 and on was rewritten in C, also developed by Dennis Ritchie, to make it more portable. It was previously written in PDP-11 assembly, for the first machine that ran UNIX. The first Bell Labs internal release was in 1971, and the first release outside of the Labs was 1973.
Dan knows his way around UNIX but still made a considerable slip-up regarding UNIX provenance. How long before some shady corporation will manage to get credit for UNIX, GNU and Linux?
Stopped watching the instant I heard him make this major gaffe. The guy doesn't clearly doesn't know what he's talking about. If you're going to present yourself as an expert on a topic you should at least know the very basic stuff.
I'm with David Jones on this one. Lost interest instantly early in the video after that serious mistake. Unix was initially developed on a PDP 7 Short : The Thompson and Ritchie Story ( ruclips.net/video/g3jOJfrOknA/видео.html ) Longer: VCF East 2019 -- Brian Kernighan interviews Ken Thompson ( ruclips.net/video/EY6q5dv_B-o/видео.html ) The second is a longer presentation, which is informative and highly entertaining.
The power of UNIX compelled me in 1990. UNIX is really that great that even the »UNIX HATERS Handbook« (Garfinkel/Weise/Strassmann, 1994) reads like a love letter.
Been using some variant of Unix since about 1991 and it's still the most powerful environment out there IMHO. It's also simple in concept and execution, which makes it wonderfully elegant.
it's funny you do the "echo cmd" technique. I've learn that a while back. BUT - instead of REMOVING the echo once you are assured the command is good, I just add "| bash" (or whatever shell you like) - and BOOM - it executes all the commands you created with text.
AT&T's Bell Labs created UNIX and C. Berkley just added stuff to it, called it "extensions" and gave away or sold its own version. that's why we have System V UNIX (AT&T) and Berkley UNIX or BSD.
He is not mistaking nothing, he gives 1970 as Unix birth, then jumps to BSD, and then showing Linux stuff as "Unix" - as informal as it is normal, and we all know what he is talking about. That's from a conference where attendees need not been told basics.
@@victordu7216 He (presenter Dan) already said he was using tmux, I think what Norio was asking was what was the markdown/markup or whatever "thing" that he was using for the text of the presentation... I'm intrigued - I could use something like that...
The program is vim and the way he opens the text is just code folding. When you are in vim press zf9j to fold 9 lines. Or zf100j for 100 lines. Also works with f and %
GNU/Linux gets more like Windows every day... I long for the simplicity of Unix before smart-ass developers decided they had infinite memory and processing speed.
@@edgeeffect You have the power to use simpler/more unixy programs on Linux with like 90% compatibility beyond maybe bloated garbage like steam requiring pulseaudio. All the bloat/windowsisms/redhat bullshit is just the result of Linux entering the public eye and the baby duck syndrome/refusal to adapt to something new from your average sheep consumer.
My first thought was that presentation was about the power of UNIX, wich is a canonical piece of technology. But the moment you start using VIM to present the content, I realized that the talk is about religion, not UNIX.
Rob Pike used the same pronunciation in a recent, very good talk. And yet sed is a single syllable. One thing I've always wondered is: if Rob Pike doesn't say /Ed/ (like the male name), then why were the next ones called jim and sam?
@la il "no one uses any of these Unix-like operating systems nowadays" are you serious ? Unix is almost on any device. What do you have in the pocket right now Android or iPhone ?
His system's battery backup is 4hr 10mins. Since when Linux machine started giving this much backup? The maximum I get on Lenovo Y50 is 2hrs. I tried TLP/PowerTop, disabled my Graphics card but it didn't help. If someone knows any other way please let me know.
Two things Apple did right: - I get over 14 hours of battery life on my Macbook Air (2015, 13") on the CLI. This is more than the claimed 12 hours. - Make the man pages better than linux. Or use the BSD ones and not change them. I don't care which one it is, only thing i know is with the Mac tar manpage i am able to extract an archive. The linux version tells me it is crap and i should use "info tar".
"Do all your logging through stdout." NO WAY. This is not good practice. stdout should be used for human consumption of messages or as information meant to be piped to other programs. Syslog is good. "Print"ing your log statements is bad. Use stderr for logging if you are using one of the normal piping mechanism. And also use proper exit codes. Otherwise, great overview.
+Chris K STDOUT can be easily rerouted to other destinations (log files, syslog, ...). It's also simpler, eliminating the need to guess what file(s) the application logs to. And lastly it works well with a container tool like Docker, which expects the primary process to log to STDOUT.
I agree for simple cases, except using stderr as the log channel. Also, stdout logging is synchronous, so if you are in an async environment, be aware of that.
It’s only synchronos if you fsync(2) all the time; else, it’s buffered like almost everything I/O. As I understand »daemonizing processes«, you are supposed to close all handles besides STDIO because then your daemon is compatible with foreground execution, syslog'ed or even rsyslog'ed/journald’ed background execution.
@@danschmidt5189 stderr can also be easily redirected in a typical shell. E.g. (bash): Redirect stderr to file: foocmd 2>/path/to/my/file Redirect both stdout and stderr to same file: foocmd &>/path/to/my/file Merge stderr into stdout (can be combined with a pipe, of course): foocmd 2>&1 Or, if you feel fancy, you can even swap stdout and stderr: foocmd 3>&2 2>&1 >&3 3>&-
I'll watch the video, but damn dude. Berkeley invented UNIX? Impetuously using VIM for a talk instead of a more suitable tool? My first UNIX prompt was in 1992, but I think you are the tool here.
I'm watching you having great difficulty navigating the VIM file you decided would be good for a presentation, I guess in order to look "hip" and let us know that vi can do anything. You dope.
And edit text files. How do you take the diff between two Control Panel configs? How do you make a config locally then email it to someone? How do you write a script that outputs a config?
"Unix was invented by very smart people..." True. "at Barkley (Berkeley) University..." ? Stunned silence, then ROFL. "in 1969." True. With this much of an error rate on such simple stuff so early, I think I'll pass.
learning a syntax such as "for f in *(.); do =${f%%.*}; mv }f }d/.;" or simply typing each number at the search bar and doing ctrl+a selecting everything and putting it into a folder? linux is a syntax hell and people also percieve if it was a good thing... all of these things can be done in windows gui without needing to know any commands. linux doesnt have a handful list of commands to begin with. a new user without internet can not do anything in terminal.
I can not understand a thing he is talking about. He talks too fast and skips around too much. I can not follow his logic. If Dan were to try to sell me a car, I would have been gone ten minutes ago.
CALL BULLSHIT...... UNIX was invented by Ken Thompson and Dennis Ritchie at Bell Labs a part of AT&T. Berkeley came along later. BUT THEY DID NOT INVENT UNIX. THEY INVENTED BSD versions.
Looking for books & other references mentioned in this video?
Check out the video description for all the links!
Want early access to videos & exclusive perks?
Join our channel membership today: ruclips.net/channel/UCs_tLP3AiwYKwdUHpltJPuAjoin
Question for you: What’s your biggest takeaway from this video? Let us know in the comments! ⬇
UNIX was developed starting in 1969, by Ken Thompson, Dennis Ritchie and a couple other folks, not at Berkeley, but at AT&Ts Bell Labs. Berkeley university didn’t have anything to do with UNIX until 1977 when they created the Berkeley Source Distribution, or BSD. Fun fact, UNIX from V4 and on was rewritten in C, also developed by Dennis Ritchie, to make it more portable. It was previously written in PDP-11 assembly, for the first machine that ran UNIX. The first Bell Labs internal release was in 1971, and the first release outside of the Labs was 1973.
Dan knows his way around UNIX but still made a considerable slip-up regarding UNIX provenance. How long before some shady corporation will manage to get credit for UNIX, GNU and Linux?
Stopped watching the instant I heard him make this major gaffe. The guy doesn't clearly doesn't know what he's talking about. If you're going to present yourself as an expert on a topic you should at least know the very basic stuff.
Thank you so much so many people don’t know and they don’t know they dont know.
I'm with David Jones on this one. Lost interest instantly early in the video after that serious mistake.
Unix was initially developed on a PDP 7
Short : The Thompson and Ritchie Story ( ruclips.net/video/g3jOJfrOknA/видео.html )
Longer: VCF East 2019 -- Brian Kernighan interviews Ken Thompson ( ruclips.net/video/EY6q5dv_B-o/видео.html )
The second is a longer presentation, which is informative and highly entertaining.
He says he and UNIX were both born 1970
One of the best videos I have ever seen on the Internet.
Right amount of humor, history and knowledge. Kudos.
The power of UNIX compelled me in 1990.
UNIX is really that great that even the »UNIX HATERS Handbook« (Garfinkel/Weise/Strassmann, 1994) reads like a love letter.
I still like to watch this again from time to time. Thanks @Daniel Terhorst-North
Same here
Been using some variant of Unix since about 1991 and it's still the most powerful environment out there IMHO. It's also simple in concept and execution, which makes it wonderfully elegant.
I'm a sane developer, when I see Unix I click like :)
Great talk. I was hoping he'd describe that python one liner he mentioned at 12:23
All presentation in plain text...cool!!! And very interesting this. Very nice!
it's funny you do the "echo cmd" technique. I've learn that a while back. BUT - instead of REMOVING the echo once you are assured the command is good, I just add "| bash" (or whatever shell you like) - and BOOM - it executes all the commands you created with text.
Niceeee
Friday night - this vid is way better than the tele!
Written by Jason Bourne. I almost spit coffee without having coffee in my mouth. 🤣 Wonderful.
_"Each command does one thing and it does it well."_ I really thought the exception will be _systemd._
hahaha, funny
systemd was inspired by microsoft technology
SystemD is not really a single executable or command
In Plan 9 you could just click on the output of the grep -n
AT&T's Bell Labs created UNIX and C. Berkley just added stuff to it, called it "extensions" and gave away or sold its own version. that's why we have System V UNIX (AT&T) and Berkley UNIX or BSD.
unix, invented at berkeley eh? 1:17
He's mistaking Unix by it's clone BSD.
It was built at Bell Labs led by Dennis and Ken Thomson.
Dennis Ritchie to be more precise.
That equivalent to Al Gore claiming he invented the Internet.
He is not mistaking nothing, he gives 1970 as Unix birth, then jumps to BSD, and then showing Linux stuff as "Unix" - as informal as it is normal, and we all know what he is talking about. That's from a conference where attendees need not been told basics.
That was _really_ nice. Thanks, Dan.
this talk is so good
'fish' shell is also worth considering
Jaw dropping, insane Unix
I expected this to be about the power draw Unix creates vs other OSs lol Still an interesting talk!
The messed up powerline bar in Vim drove me nuts.
What is the program he is using for his presentation? Is it vim? And what is the mode or add-on to show and hide the blocks?
Did you ever find out ? I like the idea of some kinda virtual markup/markdown in the shell...
@@victordu7216 He (presenter Dan) already said he was using tmux, I think what Norio was asking was what was the markdown/markup or whatever "thing" that he was using for the text of the presentation... I'm intrigued - I could use something like that...
I think it might be vim outliner.... ?
The program is vim and the way he opens the text is just code folding.
When you are in vim press zf9j to fold 9 lines. Or zf100j for 100 lines. Also works with f and %
The "dd" command was inspired by the IBM S/360 "DD" directive in JCL files.
Really great stuff. Most of it, I'll use at least once a week :-D
Btw, does anyone know what terminal emulator he is using? I can't identify it.
I never understood why Microsoft couldn't include these tools in MSDOS package, they are so easy to write.
easy, yeah right ^^
"easy"
But edlin was so great.....
Because you don't understand that MS-DOS is a direct descendant of the single-tasking CP/M OS.
Lookup Xenix ;-)
One OS to rule them all GNU/LINUX
GNU/Linux gets more like Windows every day... I long for the simplicity of Unix before smart-ass developers decided they had infinite memory and processing speed.
edgeeffect you long for the Minix 3?
Nasty.
@@edgeeffect go Void, or Artix
@@edgeeffect You have the power to use simpler/more unixy programs on Linux with like 90% compatibility beyond maybe bloated garbage like steam requiring pulseaudio. All the bloat/windowsisms/redhat bullshit is just the result of Linux entering the public eye and the baby duck syndrome/refusal to adapt to something new from your average sheep consumer.
Really enjoyable talk!
This has shown how heavily unused I’m using FreeBSD.
"Everything is a set"!
Rewatching after a few years. This is pure gold.
It's been a few years
@@ZakariaRabiai wow, I love this comment
The previous one was a few years after watching it the first time, maybe I should watch it again
Zee-Shell, or Zed-Shell, please decide.
Getafix! OMG I haven't seen that name in years. I think I'm going to go through my Asterix comic books! :D
My first thought was that presentation was about the power of UNIX, wich is a canonical piece of technology. But the moment you start using VIM to present the content, I realized that the talk is about religion, not UNIX.
Your awesome dude
you reminded me to watch Bourne series again!
Dan North.... Darth Non.
Does this work in linux
wow~very cool~ operation
According to Brian Kernighan, it's pronounced e d, not ed. Have a look at the computerphile interviews.
Rob Pike used the same pronunciation in a recent, very good talk.
And yet sed is a single syllable. One thing I've always wondered is: if Rob Pike doesn't say /Ed/ (like the male name), then why were the next ones called jim and sam?
Great session #unix
Great talk !!!
great video! but it was a zsh, not unix, video ):
Well, some UNIX basics, more Linux basics and then some shell basics. And I think everything he showed in the shell is POSIX compliant.
And Windows only trained server admins wonder why I install CygWin on all the servers for which I am responsible.
not everyone is trained, some people can learn for themselves.
You don’t have to any more with WSL
@la il "no one uses any of these Unix-like operating systems nowadays" are you serious ? Unix is almost on any device. What do you have in the pocket right now Android or iPhone ?
what unix is he actually using vim on? or is it a linux distro?
+Randy Tang He's using Ubuntu. I cannot tell you the version, but that (unfortunatly) was clearly ubuntu :)
Awesome talk!
Brian Kernighan did not write cc.
His system's battery backup is 4hr 10mins.
Since when Linux machine started giving this much backup?
The maximum I get on Lenovo Y50 is 2hrs. I tried TLP/PowerTop, disabled my Graphics card but it didn't help.
If someone knows any other way please let me know.
Two things Apple did right:
- I get over 14 hours of battery life on my Macbook Air (2015, 13") on the CLI. This is more than the claimed 12 hours.
- Make the man pages better than linux. Or use the BSD ones and not change them. I don't care which one it is, only thing i know is with the Mac tar manpage i am able to extract an archive. The linux version tells me it is crap and i should use "info tar".
12 hours on cheap Asus with Flash storage only. Your working machine need not be a server.
That's what I do everyday without any production..
You know you are a Unix guy if you a. use neither Apple nor x86(_64), b. use zsh and c. use vim for presentation!!! ^_^
If you're a unix guy you have installed zsh on your Apple UNIX (prior to current version because it's the default now)
Yes, zsh would be nowhere without Bash's GPL vs Apple, ie. zsh means you are Mac
The best
Nice talk
"Do all your logging through stdout." NO WAY. This is not good practice. stdout should be used for human consumption of messages or as information meant to be piped to other programs. Syslog is good. "Print"ing your log statements is bad. Use stderr for logging if you are using one of the normal piping mechanism. And also use proper exit codes.
Otherwise, great overview.
+Chris K STDOUT can be easily rerouted to other destinations (log files, syslog, ...). It's also simpler, eliminating the need to guess what file(s) the application logs to. And lastly it works well with a container tool like Docker, which expects the primary process to log to STDOUT.
I agree for simple cases, except using stderr as the log channel. Also, stdout logging is synchronous, so if you are in an async environment, be aware of that.
It’s only synchronos if you fsync(2) all the time; else, it’s buffered like almost everything I/O.
As I understand »daemonizing processes«, you are supposed to close all handles besides STDIO because then your daemon is compatible with foreground execution, syslog'ed or even rsyslog'ed/journald’ed background execution.
@@danschmidt5189 stderr can also be easily redirected in a typical shell. E.g. (bash):
Redirect stderr to file:
foocmd 2>/path/to/my/file
Redirect both stdout and stderr to same file:
foocmd &>/path/to/my/file
Merge stderr into stdout (can be combined with a pipe, of course):
foocmd 2>&1
Or, if you feel fancy, you can even swap stdout and stderr:
foocmd 3>&2 2>&1 >&3 3>&-
Where can I find a video like this but for Linux?
This is bash and on Linux.
Pietro Sammarco Sta utilizzando zsh non bash. though unix commands generally are the same for GNU/Linux, BSD and other UNIX-Like OS
I'll watch the video, but damn dude. Berkeley invented UNIX? Impetuously using VIM for a talk instead of a more suitable tool? My first UNIX prompt was in 1992, but I think you are the tool here.
I'm watching you having great difficulty navigating the VIM file you decided would be good for a presentation, I guess in order to look "hip" and let us know that vi can do anything. You dope.
A talk extolling the beauties of UNIX, and then push zsh so hard... disgrace. I HATE THIS WHOLE TALK.
Also, Bourne shell was written by _Jason Bourne_ ? His cheap joke depends on it, but the actual author is Stephen R. Bourne.
UNIX crash course
Please rename it "standard tools in Unix based shells". It is not about Unix, nor any powers besides knowing these tools or not.
I think Unix is better than Windows.
You sound like lewis from the Yogscast lol
Windows Admins click on cute icons. *nix Admins execute commands.
And edit text files. How do you take the diff between two Control Panel configs? How do you make a config locally then email it to someone? How do you write a script that outputs a config?
Windows is a toy compared to UNIX.
"Unix was invented by very smart people..." True.
"at Barkley (Berkeley) University..." ? Stunned silence, then ROFL.
"in 1969." True.
With this much of an error rate on such simple stuff so early, I think I'll pass.
My thoughts too.
@mem reflect Maybe he thinks his audience knows this and in advance
learning a syntax such as "for f in *(.); do =${f%%.*}; mv }f }d/.;" or simply typing each number at the search bar and doing ctrl+a selecting everything and putting it into a folder? linux is a syntax hell and people also percieve if it was a good thing... all of these things can be done in windows gui without needing to know any commands. linux doesnt have a handful list of commands to begin with. a new user without internet can not do anything in terminal.
He doesn't even know his Unix history.
I can not understand a thing he is talking about. He talks too fast and skips around too much. I can not follow his logic. If Dan were to try to sell me a car, I would have been gone ten minutes ago.
No one? Really?? Ok..
EMACS IS THE BEST
*worse then vim
CALL BULLSHIT...... UNIX was invented by Ken Thompson and Dennis Ritchie at Bell Labs a part of AT&T. Berkeley came along later. BUT THEY DID NOT INVENT UNIX. THEY INVENTED BSD versions.