From: Stefano Brivio <sbrivio@redhat.com>
To: Soumyajit Deb <debsoumyajit100@gmail.com>
Cc: Julia Lawall <julia.lawall@inria.fr>, outreachy-kernel@googlegroups.com
Subject: Re: [Outreachy kernel] Question regarding installation of kernel
Date: Wed, 11 Mar 2020 12:07:51 +0100 [thread overview]
Message-ID: <20200311120751.2fdfb9b5@elisabeth> (raw)
In-Reply-To: <alpine.DEB.2.21.2003110724100.2439@hadrien>
On Wed, 11 Mar 2020 07:25:13 +0100 (CET)
Julia Lawall <julia.lawall@inria.fr> wrote:
> On Wed, 11 Mar 2020, Soumyajit Deb wrote:
>
> > Hii
> > This is my first mail to the outreachy-kernel list. I am Soumyajit Deb.
> > I am currently following the first patch tutorial and accordingly I have
> > downloaded the Kernel source tree.
> > I have doubt whether I have to build the kernel source code I have
> > downloaded as I am using ubuntu already?
>
> You should start with modifying a driver in the kernel you downloaded and
> checking that it is executed. For that you will need to compile and
> install the kernel you downloaded.
Also note that, while this is not mentioned in the tutorial (I plan to
add some notes when I have a bit more time), it might be a good idea to
set up a Linux virtual machine (running in your existing Linux system)
so that you can test any non-trivial changes by installing (and also
building, if you wish) your kernel there.
This way, you'll need to reboot your virtual machine instead of the
system you're working on, especially in case it's your primary/only
system or if you're using it to communicate, without having the concern
that your new kernel might not boot up.
--
Stefano
prev parent reply other threads:[~2020-03-11 11:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-11 2:19 Question regarding installation of kernel Soumyajit Deb
2020-03-11 6:07 ` [Outreachy kernel] " Greg KH
2020-03-11 6:25 ` Julia Lawall
2020-03-11 11:07 ` Stefano Brivio [this message]
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=20200311120751.2fdfb9b5@elisabeth \
--to=sbrivio@redhat.com \
--cc=debsoumyajit100@gmail.com \
--cc=julia.lawall@inria.fr \
--cc=outreachy-kernel@googlegroups.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.