From: geek@uniserve.com (Dave Stevens)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Need Suggestions
Date: Tue, 17 Jul 2018 21:10:05 -0700 [thread overview]
Message-ID: <20180717211005.403f54e9@user-Satellite-A100> (raw)
In-Reply-To: <c3429a8e-5864-e905-6c08-0edd058f2313@systemli.org>
On Wed, 18 Jul 2018 02:35:09 +0200
Richard Siegfried <richard_siegfried@systemli.org> wrote:
> On 14/07/18 18:04, Athul Joy wrote:
> > Dear friends, I am new to the Linux kernel development.
> > Can anyone help me how to start my journey in order to build my own
> > kernel?
> For me the debian kernel handbook was a great help especially chapter
> 4 and section 4.6.
> (https://kernel-team.pages.debian.net/kernel-handbook/ch-common-tasks.html#s-kernel-org-package)
>
> There also is a book from greg kroah hartmann about building your own
> kernel that has a good reputation.
>
> And I would recommend to start conservative, which means don't try out
> too many new/changed kernel options at once. Start with "make
> oldconfig" or even "make oldconfig". (If you don't know these two
> start with "make help").
$ make help
make: *** No rule to make target 'help'. Stop.
d
You can always read about new kernel options
> and features inside the "make menuconfig" application with pressing
> "?"
>
> Thanks,
> -- Richard
>
--
In modern fantasy (literary or governmental), killing people is the
usual solution to the so-called war between good and evil. My books are
not conceived in terms of such a war, and offer no simple answers to
simplistic questions.
----- Ursula Le Guin
next prev parent reply other threads:[~2018-07-18 4:10 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-14 16:04 Need Suggestions Athul Joy
2018-07-14 16:27 ` ozgur at goosey.org
2018-07-14 17:31 ` Cindy-Sue Causey
2018-07-14 18:07 ` ozgur at goosey.org
2018-07-15 13:39 ` valdis.kletnieks at vt.edu
2018-07-18 0:35 ` Richard Siegfried
2018-07-18 0:43 ` Richard Siegfried
2018-07-18 4:10 ` Dave Stevens [this message]
2018-07-18 4:41 ` valdis.kletnieks at vt.edu
2018-07-18 5:00 ` Dave Stevens
2018-07-18 4:39 ` inventsekar
2018-07-18 21:19 ` Daniel.
2018-07-18 21:29 ` Dave Stevens
2018-07-18 23:10 ` valdis.kletnieks at vt.edu
2018-07-19 1:16 ` Daniel.
2018-07-19 2:37 ` valdis.kletnieks at vt.edu
2018-07-19 2:42 ` Daniel.
2018-07-25 21:37 ` Himanshu Jha
2018-07-25 22:10 ` valdis.kletnieks at vt.edu
2018-08-01 21:29 ` Ruben Safir
2018-08-02 4:36 ` Himanshu Jha
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=20180717211005.403f54e9@user-Satellite-A100 \
--to=geek@uniserve.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).