=== himcesjf_ is now known as him-cesjf
=== zyga_ is now known as zyga
=== TJ_Remix is now known as TJ-
[18:20] <Tathagat2006> i am asecond year student a have read galvin for operating systems
[18:21] <Tathagat2006> now i want to start learning linux kernel dev from scratch
[18:21] <Tathagat2006> i have started reading linux kernel development by robert love
[18:21] <Tathagat2006> which books to follow and in which order??
[18:22] <Tathagat2006> are there any online resources which can help me learning linux kernel dev from scratch??
[18:22] <TJ-> Tathagat2006: you'll not see a lot going on here especially at weekends; in the week the kernel devs discuss kernel/package development but it's not massively busy - most dev's aren't looking at IRC. there's a mainline channel ##kernel but that's the same
[18:22] <Tathagat2006> i dont have any prior knowledge about linux kernel dev
[18:23] <TJ-> Tathagat2006: best thing is to start reading the kernel's ./Documentation/ directory
[18:23] <Tathagat2006> TJ: so what to refer?
[18:23] <Tathagat2006> which channel will be helpfull?
[18:24] <TJ-> Tathagat2006: start here https://www.kernel.org/doc/html/latest/index.html
[18:25] <TJ-> best bet is to subscribe to 1 or more of the various kernel mailing lists where you'll see patches discussed and refined and get to know the development process. See also https://www.kernel.org/ and the "Kernel Mailing Lists" and other resources links
[18:26] <Tathagat2006> i have joined newbies mailing list
[18:26] <Tathagat2006> but tbh i dont understand the stuff going on there
[18:26] <Tathagat2006> like wht are they discussing
[18:27] <TJ-> Tathagat2006: it takes time to get context. Reading the source and the commit logs helps a lot
[18:28] <Tathagat2006> cool
[18:29] <Tathagat2006> so continuing to read robert love and mailing list and the links provided by you would be good for the begining?
[18:31] <TJ-> Tathagat2006: yes... eventually, if you combine with reading source-code and patches and commits you'll get the context and it'll start to make sense. Remember, it's one of the biggest software projects there is - over 30 million lines of code - so no one can know it all. It's split inot sub-systems each of which has it's own maintainers so you could choose to focus on a smaller, quieter, sub-system to
[18:31] <TJ-> begin with whilst still staying 'aware' of what is happening overall
[18:32] <TJ-> Tathagat2006: I find reading git log's of commmits is really helpful
[18:34] <Tathagat2006> TJ: Thank you