From: riel@surriel.com (Rik van Riel)
To: kernelnewbies@lists.kernelnewbies.org
Subject: one thing at a time
Date: Mon, 18 Aug 2014 22:06:04 -0400 [thread overview]
Message-ID: <53F2B10C.8010504@surriel.com> (raw)
In-Reply-To: <CAPDOMVjp7a5XSZ=6XxspUqKeC+aCvd7oYwH840J6KYzPUSxqAg@mail.gmail.com>
On 08/18/2014 01:13 PM, Nick Krause wrote:
> Valdis,
> I was interested in both at the same time, just asked about Beagle-boards first.
> I aren't having any difficulty with it , I just wanted to known more about this
> area as the docs out there are terrible and not worth reading on this part of
> the networking stack.
Nick,
the Linux kernel requires a lot of focus.
I have no doubt that you are smart enough to learn
things about the Linux kernel, but nobody is smart
enough to learn everything at once. Nobody.
If you are serious about learning Linux kernel internals,
it would be good to focus on one thing at a time.
One thing. Learn everything about it, before moving on
to the next topic.
Kernel hacking is much more about attitude than about
aptitude. Focus is the key.
next prev parent reply other threads:[~2014-08-19 2:06 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-18 16:25 TCP/UDP Nick Krause
2014-08-18 16:51 ` TCP/UDP Afonso Bordado
2014-08-18 16:54 ` TCP/UDP Nick Krause
2014-08-18 16:57 ` TCP/UDP Valdis.Kletnieks at vt.edu
2014-08-18 17:13 ` TCP/UDP Nick Krause
2014-08-18 17:21 ` TCP/UDP Nick Krause
2014-08-18 17:26 ` TCP/UDP Manish Katiyar
2014-08-18 17:29 ` TCP/UDP Nick Krause
2014-08-19 2:06 ` Rik van Riel [this message]
2014-08-19 2:55 ` one thing at a time Nick Krause
2014-08-19 2:59 ` Nick Krause
2014-08-19 4:25 ` Nick Krause
2014-08-19 6:29 ` Jason Ball
2014-08-19 12:13 ` Greg Freemyer
2014-08-19 16:41 ` Nick Krause
2014-08-18 17:31 ` TCP/UDP Denis Kirjanov
2014-08-18 17:33 ` TCP/UDP Nick Krause
2014-08-18 19:43 ` TCP/UDP Nick Krause
2014-08-19 0:46 ` fd type from number Loris Degioanni
2014-08-19 12:04 ` Greg Freemyer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53F2B10C.8010504@surriel.com \
--to=riel@surriel.com \
--cc=kernelnewbies@lists.kernelnewbies.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).