From: freeman.zhang1992@gmail.com (freeman)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Kernel Development
Date: Mon, 24 Feb 2014 09:13:42 +0800 [thread overview]
Message-ID: <530A9CC6.6010608@gmail.com> (raw)
In-Reply-To: <CAMQVM6o94p21BruTrFWdi3GhAyV7VucMxa5h11VQRpF5C=sr3A@mail.gmail.com>
Hi,
2014-02-24 01:24, subham soni :
> Hello,
> I am a newbie to kernel development. I would like to develop
> my own kernel from scratch. From where should I start from? I have a
> good experience of the commands in Linux
> (Ubuntu,Fedora,Debian,Slackware). I googled out and I came to know
> that I should start from Device Drivers. Now which device driver
> should I code? Or should I master Shell Scripting? For developing a
> kernel (my aim here would be to increase the battery life, since most
> laptops have only 1.30 hrs or 2.00 hrs in Linux OS) and 3.00 hrs in
> Windows Environment. How should I start and from where?
>
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
I read some books about how to DIY an OS . Of course it's simple and
crude, but it's a good start, I think.
Hidemi Kawai, Homemade Operating System Within 30 Days
Yuan Yu, Operating System From Scratch (I don't know if there is an
English edition. The project from thisbook is on GitHub:
https://github.com/yyu/osfs00)
"
<http://www.amazon.com/Homemade-Operating-System-Chinese-Edition/dp/7115287961>There
are many ways to learn OS, but I believe the best way is to learn by
practice. There are many open source OS code, but the code bases are
huge. You will get lost in the source code labyrinth.
There are good books, /Operating System: Design and
Implementation/ by A.S. Tanenbaum and A.S. Woodhull for example, but
they don't teach you where to begin either.
That's why you should come here. If Tanenbaum's book is a reference,
my project series is a tutorial. Prof. Tanenbaum tells you what.
I'll tell you how."
<http://www.amazon.com/Homemade-Operating-System-Chinese-Edition/dp/7115287961>
Above are two funny books involving me into coding and learning about
OS. However, if you're serious, please just ignore :-P
All the best,
Freeman Zhang
<http://www.amazon.com/Homemade-Operating-System-Chinese-Edition/dp/7115287961>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20140224/969ab64d/attachment.html
next prev parent reply other threads:[~2014-02-24 1:13 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 [this message]
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
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=530A9CC6.6010608@gmail.com \
--to=freeman.zhang1992@gmail.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).