From: Valdis.Kletnieks@vt.edu (Valdis.Kletnieks at vt.edu)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Kernel Development
Date: Mon, 24 Feb 2014 12:57:38 -0500 [thread overview]
Message-ID: <13457.1393264658@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Sun, 23 Feb 2014 22:54:31 +0530." <CAMQVM6o94p21BruTrFWdi3GhAyV7VucMxa5h11VQRpF5C=sr3A@mail.gmail.com>
On Sun, 23 Feb 2014 22:54:31 +0530, subham soni said:
> I am a newbie to kernel development. I would like to develop my own
> kernel from scratch. From where should I start from?
A large supply of caffeine, you're going to be writing a *lot* of code.
For example, linux-0.01 was 100 source files totalling 11,283 or so lines of code.
For linux 0.96, that jumped to 200 files and 35,000+ lines of code.
And 0.99.15 was 175,000 or so lines.
So figure you're going to be about a quarter million lines of code before you
get to a usable self-hosting environment.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 848 bytes
Desc: not available
Url : http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20140224/6c25f75c/attachment.bin
next prev parent reply other threads:[~2014-02-24 17:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-23 17:24 Kernel Development subham soni
2014-02-23 18:19 ` Kuldeep Singh Dhaka
2014-02-23 23:35 ` John de la Garza
2014-02-24 1:13 ` freeman
2014-02-24 4:36 ` Pranay Srivastava
2014-02-24 5:44 ` subham soni
2014-02-24 5:49 ` Manish Katiyar
2014-02-24 6:08 ` priyaranjan
2014-02-24 6:44 ` subham soni
2014-02-24 9:45 ` Anuz Pratap Singh Tomar
2014-02-24 17:57 ` Valdis.Kletnieks at vt.edu [this message]
2014-02-25 4:51 ` rakesh Bhaskar
-- strict thread matches above, loose matches on Subject: below --
2020-03-29 12:27 Harsh chopra
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=13457.1393264658@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--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).