[a / b / c / d / e / f / g / gif / h / hr / k / m / o / p / r / s / t / u / v / vg / vm / vmg / vr / vrpg / vst / w / wg] [i / ic] [r9k / s4s / vip] [cm / hm / lgbt / y] [3 / aco / adv / an / bant / biz / cgl / ck / co / diy / fa / fit / gd / hc / his / int / jp / lit / mlp / mu / n / news / out / po / pol / pw / qst / sci / soc / sp / tg / toy / trv / tv / vp / vt / wsg / wsr / x / xs] [Settings] [Search] [Mobile] [Home]
Board
Settings Mobile Home
/g/ - Technology


Thread archived.
You cannot reply anymore.


[Advertise on 4chan]


File: IMG_1374.jpg (56 KB, 600x600)
56 KB
56 KB JPG
What will I know after reading picrel?
>>
Just install Slackware and patch and compile your own kernel. You'll learn everything you need to know.
>>
>>108539762
You'll understand the kernel
>>
>>108539762
I am going to go out on a metaphorical limb, one just about 3 feet off the ground, and say you won't even read it, let alone make it past the first chapter if you begin.
>>
>>108539799
What if I told you I already read it?
>>
File: homo_say_what.gif (234 KB, 220x164)
234 KB
234 KB GIF
>>108539812
>What will I know if I already read it?
>>
>>108539762
nothing
whatever is in print is outdated anyway if you actually need to know kernel internals because e.g. you're going to write a driver or do extremely in-depth debugging or optimization, you better be able to read the code to learn it or you won't get anywhere anyway
if you just want to compile something you don't need to know internals at all and the book is just for masturbating



[Advertise on 4chan]

Delete Post: [File Only] Style:
[Disable Mobile View / Use Desktop Site]

[Enable Mobile View / Use Mobile Site]

All trademarks and copyrights on this page are owned by their respective parties. Images uploaded are the responsibility of the Poster. Comments are owned by the Poster.