Re: Need Suggestions

[Daniel.]

>
> It's OK.. just remember to trim out the non-important stuff next time. :)
>

Okay! Thanks!

>
___
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

Re: Need Suggestions

[valdis . kletnieks]

On Wed, 18 Jul 2018 22:16:07 -0300, "Daniel." said:
> Sorry. Do I did something bad? I wasn't intended to.. I didn't think that
> trimming was a bad idea, I just want to reinforce the book suggestion ...
> Sorry

It's OK.. just remember to trim out the non-important stuff next time. :)


pgprhQKnEoGUb.pgp
Description: PGP signature
___
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

Re: Need Suggestions

[Daniel.]

Em qua, 18 de jul de 2018 20:10,  escreveu:

> On Wed, 18 Jul 2018 14:29:41 -0700, Dave Stevens said:
> > On Wed, 18 Jul 2018 18:19:05 -0300 "Daniel." 
> wrote:
> >
> > > > Hi Athul...
> > > > This is my collegemate's writing, ... This will solve all your
> > > > confusions
> > > >
> >
> > is it the policy on this list to trim?
>
> Only the irrelevant parts, leave the parts that are the context for the
> reply.
> So that *should* have been trimmed down to:
>
> ---
> > 4) Without hesitation buy, Robert Love's Linux Kernel Programming book.
> It is
> > one of the best beginner material and start reading it parallel to the
> OS book.
> > This is easier to read than the previous one and more practical. But the
> > previous one adds more value and is more theoretical. Handle (3) and (4)
> in
> > parallel without blocking on any of the other activities.
>
> I can confirm, this book is GOOD! Also check LDD3,  it's open and
> online
> available, you may find some of it's authors in this mailist! :-). http://
> www.makelinux.net/ldd3/ it's a outdated but it was a very valuable source
> to
> me. You can find the examples updated on the internet.
> ---
>
> Also, MUAs the encourage top-posting and allowing quoting without a '> ' or
> other indicator of quoting depth are a pox on email.
>

Sorry. Do I did something bad? I wasn't intended to.. I didn't think that
trimming was a bad idea, I just want to reinforce the book suggestion ...
Sorry

>
___
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

Re: Need Suggestions

[valdis . kletnieks]

On Wed, 18 Jul 2018 14:29:41 -0700, Dave Stevens said:
> On Wed, 18 Jul 2018 18:19:05 -0300 "Daniel."  wrote:
>
> > > Hi Athul...
> > > This is my collegemate's writing, ... This will solve all your
> > > confusions
> > >
>
> is it the policy on this list to trim?

Only the irrelevant parts, leave the parts that are the context for the reply.
So that *should* have been trimmed down to:

---
> 4) Without hesitation buy, Robert Love's Linux Kernel Programming book. It is
> one of the best beginner material and start reading it parallel to the OS 
> book.
> This is easier to read than the previous one and more practical. But the
> previous one adds more value and is more theoretical. Handle (3) and (4) in
> parallel without blocking on any of the other activities.

I can confirm, this book is GOOD! Also check LDD3,  it's open and online
available, you may find some of it's authors in this mailist! :-). http://
www.makelinux.net/ldd3/ it's a outdated but it was a very valuable source to
me. You can find the examples updated on the internet. 
---

Also, MUAs the encourage top-posting and allowing quoting without a '> ' or
other indicator of quoting depth are a pox on email.


pgpa79V4rBBP8.pgp
Description: PGP signature
___
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

Re: Need Suggestions

[Dave Stevens]

On Wed, 18 Jul 2018 18:19:05 -0300
"Daniel."  wrote:

> > Hi Athul...
> > This is my collegemate's writing, ... This will solve all your
> > confusions
> >

is it the policy on this list to trim?

D

-- 
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

___
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

Re: Need Suggestions

[Daniel.]

2018-07-18 1:39 GMT-03:00 inventsekar :

> Hi Athul...
> This is my collegemate's writing, ... This will solve all your
> confusions
>
> ---
>
> The most important quality that you need to inculcate if you want to do
> any kernel space programming is "Patience" (or persistence if you will).
> Though it is a good quality for any large scale project, it is a
> fundamental requirement for kernel programming. It is very easy to see
> progress and make an impact on userspace projects, but even simple changes
> in the kernel core will take a lot of time to get accepted, and will often
> require multiple rewrites. But fear not, as there are plenty of people who
> have conquered this mountain and it is not something to be worried about.
>
> The starting steps will be:
>
> 1) Try to understand how to use git . We were (are
> ?) not taught to use a version control system in our college and it is such
> a fundamental thing. So start using git for college assignments and get the
> hang of it.
>
> 2) Start writing a lot of C programs and get experienced with pointers,
> memory allocation, threading. You can start implementing things like Stack,
> Queue, Trees etc. (whatever you study in datastructures) in a simple,
> thread-safe way. Do not focus on how you can visualize these datastructures
> but how you can effectively implement their functionality and thread
> safety. Use pthreads for threading. Do not use any library (like Glib) for
> giving you convenient datastructures (like Strings). Implement each of the
> things on your own. (But when you are writing code for a product, use a
> standard library always instead of re-inventing the wheel)
>
> Write these C programs on Linux and compile using gcc. In our college days
> we were using turboc on windows and I hope things have changed. Use a linux
> distro (fedora , debian
> , openSUSE , Gentoo
>  etc.) exclusively; Do not use Windows (at least
> for a while) to make yourself aware of the sysadmin, shell-scripting parts
> of linux, which will come in handy.
>
> 3) Grab a (any) book on Operating Systems theory and read it. The dinosaur
> book  by
> Silberschatz et. al. is a good start.
>
> 4) Without hesitation buy, Robert Love's Linux Kernel Programming
>  book. It is one of the
> best beginner material and start reading it parallel to the OS book. This
> is easier to read than the previous one and more practical. But the
> previous one adds more value and is more theoretical. Handle (3) and (4) in
> parallel without blocking on any of the other activities.
>
I can confirm, this book is GOOD! Also check LDD3,  it's open and
online available, you may find some of it's authors in this mailist! :-).
http://www.makelinux.net/ldd3/ it's a outdated but it was a very valuable
source to me. You can find the examples updated on the internet.

>
>
> 5) After you are done with (1) and (2), and feel sufficiently confident
> with C and pointers, grab the  linux kernel sources from
> http://git.kernel.org/ and try to build the sources yourself. http://
> kernelnewbies.org/KernelBuild should help. Learn how to install and boot
> with the kernel that you have built.
>
> 6.1) Subscribe to Kernel Newbies mailing list http://kernelnewbies.org/
> MailingList and read every mail, *even* if you do not understand most of
> it.
>
> 6.2) Watch: https://www.youtube.com/watch?v=LLBrBBImJt4
>
> 6.3) Subscribe to http://lwn.net RSS feeds.
>
> After this, you should be able to fix and send any trivial, documentation,
> staging fixes. Once you have done this and get the hang of the process, you
> will know how to send patches for any parts of the kernel.
>
> By this time, you would have found your areas of interest in kernel
> (filesystems, memory management, io scheduler, CPU scheduling etc.). You
> will then have to dig deeper in those particular areas, by:
> a) subscribing to the individual mailing lists (such as fs-devel
> , etc.)
> b) reading about the bug reports for the individual component
> c) finding the literature that is relevant for your subsystem (The linux
> memory management book
> Mel Gorman, etc).
>
> Three other non-technical things that I would recommend are:
>
> 1) Create a new email address and use that for all your open source
> activities. That way you do not miss any important updates from your
> friends.
>
> 2) Kernel programming will not give you big money in the short and medium
> term (at least in India). If your motivation is not excellence in
> engineering, but becoming popular or rich (it is not wrong btw) then you
> should focus on some other areas of programming (developing apps, websites,
> solving user problems, making meaning etc.).
>
> It will