From: Ezra Buehler <ezra@easyb.ch>
To: Abhijit Paul <coder.abhijit90@gmail.com>
Cc: kernelnewbies <kernelnewbies@kernelnewbies.org>
Subject: Re: Enquiry for contribute in Linux Kernel
Date: Fri, 5 Feb 2021 14:29:46 +0100 [thread overview]
Message-ID: <BFA212DB-6498-4CB6-B2DD-83288EC1F3ED@easyb.ch> (raw)
In-Reply-To: <CAGzpWioVjQMK+mtWhp_nqpw8c5exw4tKMazSacHOd4KZAGs3JA@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1000 bytes --]
Hi Abhijit Paul,
On 5 Feb 2021, at 08:00, Abhijit Paul <coder.abhijit90@gmail.com> wrote:
> But I don't know what to learn. I know the C/C++ programming language.
C and C++ are two different languages that are (normally) used very
differently. So, you might want to start with getting more familiar with
how code in a C project like Linux is written. In general, I believe
that the only way to learn software development is to find yourself a
project/problem you would like to work on/solve. If you cannot find
anything within the Linux project, maybe also consider a user space
application that is written in C, there are many of those out there.
> Do I need to learn about operating systems and how they work?
I would say it depends on what you plan to do. E.g. to get started with
driver development, I don't think you need to know in depth how an
operating system/kernel works. But, of course you should be a proficient
GNU/Linux user, or you won't get very far.
Good look!
Cheers,
Ezra.
[-- Attachment #1.2: Type: text/html, Size: 2091 bytes --]
[-- Attachment #2: Type: text/plain, Size: 170 bytes --]
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next parent reply other threads:[~2021-02-05 13:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAGzpWioVjQMK+mtWhp_nqpw8c5exw4tKMazSacHOd4KZAGs3JA@mail.gmail.com>
2021-02-05 13:29 ` Ezra Buehler [this message]
2021-02-05 14:29 ` Enquiry for contribute in Linux Kernel Krishna Deshpande
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=BFA212DB-6498-4CB6-B2DD-83288EC1F3ED@easyb.ch \
--to=ezra@easyb.ch \
--cc=coder.abhijit90@gmail.com \
--cc=kernelnewbies@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).