Greg Kroah Hartman on the Linux Kernel

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.

Category:

People & Blogs

Tags:

• google
• techtalks
• techtalk
• engedu
• talk
• talks
• googletechtalks
• education

[jeroeniskoning]

"The future will be open."

[untseac]

at first I was thinking "god.. 50min... I'm not going to listen to all this crap" but then it turned out to interesting to miss lol

[nealmcb]

Thanks. The comments on testing start at 14:20

[Monkeymanmoog]

@untseac Yeah Greg is really easy to listen too and never seems to get bogged down into the yawn inducing stuff!

[zungaloca]

He has some open source sparkle of steve jobs..

T~T

[balkiprasanna1984]

yeah.. I am interested in robotics developed on linux drivers... Can anyone tell me if they worked on it ...

[GiedriusJ1]

@TheDeadlyPythonTube what you say would be true, if Linux Kernel would be Microkernel, or even Hybrid kernel. Since you can put drivers/file system stuff, inside the kernel, thigs usually become even more stable/fast. Btw, have you ever compiled your own Linux kernel? I gues no, because you would've known that you can make extremely lightweight kernel, by not compiling stuff you don't use.

[TheDeadlyPythonTube]

This guy has no idea what he's talking about. The purpose of the kernel is just to talk to the hardware and manage all the resources. And this goal should be archived by a small and fast kernel. Saying 'Bring your code into the kernel' is a dumb thing to say. It's just going to bloat the kernel and make it slow.

[goodkill1]

@gnulinux540 on linux right now ^^

[Bitwzyze]

@Gyula9999 Nice catch. That's just like Greg.

[Bitwzyze]

@joanindo Canonical submits almost nothing. They don't do shit for the kernel.

[Bitwzyze]

@martinmartiini He doesn't mean snapping chips in two. Say person X submits a patch, dealing with graphics cards. That patch makes the output of the graphics cards behave erratically - they're not being controlled properly by the kernel. Person X is said to have "broken" the graphics card - with that kernel, it no longer functions as it should.