From: priyaranjan45678@gmail.com (priyaranjan)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Kernel Development
Date: Mon, 24 Feb 2014 11:38:10 +0530 [thread overview]
Message-ID: <CAE_iR+ip-RtAu1apNghjAEvwofvg5RAr62HTVH82_QM=i4v6MA@mail.gmail.com> (raw)
In-Reply-To: <CAMQVM6o94p21BruTrFWdi3GhAyV7VucMxa5h11VQRpF5C=sr3A@mail.gmail.com>
On Sun, Feb 23, 2014 at 10:54 PM, subham soni <sonikernel1@gmail.com> wrote:
> 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).
You can start with reading Linux kernel development by Robert Love.
Also look at minix3 microkernel and its feature. You need to understand the
various modules of OS before writing a one....
> 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?
>
I don't think drivers is the good place to start.
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>
next prev parent reply other threads:[~2014-02-24 6:08 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 [this message]
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
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='CAE_iR+ip-RtAu1apNghjAEvwofvg5RAr62HTVH82_QM=i4v6MA@mail.gmail.com' \
--to=priyaranjan45678@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).