 |
Greg Kroah Hartman on the Linux Kernel
Uploaded by: googletechtalks
Video Description:
Google Tech Talks
June, 5 2008
ABSTRACT
The Linux Kernel, who is developing it, how they are doing it,
and why you should care.
This talk describes the rate of development for the Linux
kernel, and how the development model is set up to handle such a
large and diverse developer population and huge rate of change.
It will detail who is doing the work, and what companies, if
any, are sponsering it. Finally, it will go into why companies
like Google, and any other that uses or depends on Linux, should
care about this development. Lots of numbers and pretty graphs
will be shown to keep the audience awake.
Speaker: Greg Kroah Hartman
Greg Kroah-Hartman is a Linux kernel maintainer for the USB,
driver core, sysfs, and debugfs portions of the kernel as well
as being one half of the -stable kernel release team. He
currently works for Novell as a Fellow doing various kernel
related things and has written a few books from O'Reilly about
Linux development in the past.
Tags for this video: education engedu google googletechtalks talk talks techtalk techtalks
Find more videos in the "People" category
See more videos uploaded by googletechtalks
| IBM Linux ad: Prodigy | Tech Talk: Linus Torvalds on git | Novell Linux, Mac, PC |
 |  |  |
| Fedora Linux on PS3 w/ Voiceover | Ubuntu Linux | Sabayon Linux |
 |  |  |
Share This Video:
Comments for this video: Show || Hide
Tell a friend:
Even more so with stripping the kernel & modding it (eg for an embedded stuff).
I recon you have tried a microkernel OS, if so, is it good? As I understand it, multitasking is a bit more "difficult" (In the terms of speed and stability).
Though I really like the idea that each device driver isn't included in the kernel itself, Linux and *BSD has traces of that (Graphic cards for instance).
*if Windows' core could be called one, then Linux certainly is one
BSOD's are caused by (usually) bugs in device drivers, whereas in Linux and *BSD, only the drivers fail, not the entire system.
But if you go to wiki, you'll get Win NT kernel is hybrid. That's meaningless. Hybrid means nothing. That's probably 90% monolithic & 10% micro-like.
Everything is "hybrid". But I was talking about real hybrids. Linux is closer, but I meant those more micro-like ones.
Incorporating everything in the kernel might be fast, but it's on the expense of stability and security, something I don't like.
How to not give a presentation!
Quit moving around.
Quit waving your hands, you're not steve jobs.
Quit rambling.
Write out the presentation.