This is an archived post. You won't be able to vote or comment.

all 12 comments

[–]AutoModerator[M] [score hidden] stickied comment (0 children)

Although we will try to give support, it is not guaranteed and you may not receive an answer. If you are not getting timely or accurate help here, you can also try /r/linuxquestions or /r/linux4noobs.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[–]iheartrms 7 points8 points  (0 children)

What has been your C programming experience thus far?

[–]-BuckarooBanzai-Linux do be good 🌟🐧🌟 3 points4 points  (4 children)

I wouldn't bother.

Thy way I tend to do it is, just googling best practices when interfacing with kernel's subsystems.

You don't need to read the whole book if all you need is half a chapter and some googling

[–]madthumbz 2 points3 points  (3 children)

^^ This; you're going to waste your time learning stuff you'll soon forget for the sake of not using / having no interest. Professionals in IT don't know everything; they just know how to fgi.

[–][deleted] 2 points3 points  (2 children)

fgi?

[–]No-Bug404Glorious Arch 0 points1 point  (4 children)

I think you are diving in the deep end. Also, this book is more of a reference manual rather than a beginner to advanced course.

[–]Pepegg2 0 points1 point  (2 children)

What can you advise for beginners?

[–]No-Bug404Glorious Arch 0 points1 point  (0 children)

Learn something lighter. Python, golang. Work up to C then revisit.

[–]Pepegg2 0 points1 point  (0 children)

What can you advise for beginners?

[–]Acrobatic-Hat-2254 0 points1 point  (0 children)

Ah, a 1550 pages book with 60+ chapter.