Beware - kernel Newbie!
Hi all,
This is an typical mail from an experienced user-land programmer who wants to help in kernel development ;D.
I've been lurking for a while in this list and I'm wondering if this is the right list for asking stupid newbie questions. Is it?. If not, do you know one?. Where I can find documentation? (yeah, yeah, read the code. But
things are always better with an 'vi Doc.txt' in the processes tree :)
Thanks!
Pedro
Quoted 6 lines · Pedro Diaz Jimenez
This is an typical mail from an experienced user-land programmer who wants to help in kernel development ;D.
I've been lurking for a while in this list and I'm wondering if this is the right list for asking stupid newbie questions. Is it?. If not, do you know one?. Where I can find documentation?
We are always welcome to answer newbie -kernel hacking- questions... just ask specific ones. For example, ask "how does struct netdevice's last_rx member get used?", not "what do I need to do to write a network driver?"....
The documentation is in linux/Documentation/*
Quoted 2 lines
(yeah, yeah, read the code. But
things are always better with an 'vi Doc.txt' in the processes tree :)
Really. The code is the best documentation. Hone your code reading skills. Use the source, Luke.
Jeff
Thanks to all,
I've just found http://www.linuxnewbie.org to be a good start point
Pedro
Quoted 8 lines · Jeff Garzik
Quoted 6 lines · Pedro Diaz Jimenez
This is an typical mail from an experienced user-land programmer who wants to help in kernel development ;D.
I've been lurking for a while in this list and I'm wondering if this is the right list for asking stupid newbie questions. Is it?. If not, do you know one?. Where I can find documentation?
Quoted 7 lines
We are always welcome to answer newbie -kernel hacking- questions... just ask specific ones. For example, ask "how does struct netdevice's
last_rxmember get used?", not "what do I need to do to write a network driver?"....The documentation is in linux/Documentation/*
he he
Quoted 16 lines
Quoted 2 lines
(yeah, yeah, read the code. But
things are always better with an 'vi Doc.txt' in the processes tree :)Really. The code is the best documentation. Hone your code reading skills. Use the source, Luke.
Jeff
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/