From: "Valentin Vidić" <vvidic@valentin-vidic.from.hr>
To: kernelnewbies@kernelnewbies.org
Subject: Re: Kernel developer proccess
Date: Tue, 25 Apr 2023 20:32:02 +0200 [thread overview]
Message-ID: <ZEgcot3PGQ9/0rxn@valentin-vidic.from.hr> (raw)
In-Reply-To: <CAFroS2aOs4=75d2WY9biD=913fZqxf83wO6bdrnfUBXKUnopSQ@mail.gmail.com>
On Wed, Mar 22, 2023 at 01:20:45AM +0200, Panagiotis Filippakopoulos wrote:
> Hello. I would like to ask, what your advise would be to a person that
> wants to get in the kernel development industry, without having a coputer
> science degree. I attended some classes for computer science, but due to
> some difficulties i left after the first semester. During that time we
> learned a little bit about operating systems and the basics of programming.
> Is learning operating systems C and Assembly, for a specific architecture,
> (e.g. x86) a good start? What should my steps be after that? Thank you in
> advance.
I think it will take a lot of time and work. To check if you really want
to do it here is a recent article:
https://people.kernel.org/linusw/the-arm32-scheduling-and-kernelspace-userspace-boundary
Try to read and understand it. It links to some code, so try to read and
understand that too. If you get stuck on something, do some research and
ask questions. After that you should have a better idea if you like it
and want to continue.
--
Valentin
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
prev parent reply other threads:[~2023-04-25 18:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-21 23:20 Kernel developer proccess Panagiotis Filippakopoulos
2023-04-24 23:32 ` jim.cromie
2023-04-25 7:40 ` Denis Kirjanov
2023-04-25 15:22 ` Aruna Hewapathirane
2023-04-25 18:32 ` Valentin Vidić [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=ZEgcot3PGQ9/0rxn@valentin-vidic.from.hr \
--to=vvidic@valentin-vidic.from.hr \
--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 read-only IMAP folder(s) and NNTP newsgroup(s).