Quote:
Originally Posted by elcore
How is it possible for kernel to be decompiled then?
It's engineered according to blueprint, not baked according to recipe.
Having a blueprint means one can unbuild ad rebuild it, while having a recipe does not mean one can uncook the chili.
Can't see how it's even relevant since the compiler's just logic and math rather than physics and chemistry.
|
Silicon is the 14th element in the periodic table...
Perhaps, on a technical forum, one should restrain from tools of figurative speech, such as metaphores or similes. But metaphores and similes can be fun ways to present certain topics. I wasn't being literal: of course I'm not putting my lenovo on my wood-fired stove to cook it.
But after I run make menuconfig in the kernel building process, I am presented with a pretty ncurses window with zillions of nested checkboxes, most of which represent bits of drivers or firmware that run the zillions of hardware devices on the market, from ham radio modems to joysticks and fancy game controllers, all those wireless antennas, whether 802.11*, bluetooth, infrared, etc, not to mention the processors themselves. Other checkboxes are features to turn on and off.
Cooking is an art, and so is building kernels. The art of cooking is knowing what ingredients mix well to create a pallete-satisfying dish. The art of building kernels is knowing which checkboxes need to be checked to satisfy your hardware's pallete (I know your hardware does not have taste buds).
I hereby claim the right to poetic expression even in technical forums.
Since users coping with 14.2 may be new to slackware or even to linux, I was hoping to present buiding a kernel in an undaunting light (though this too is already metaphorical, as I don't actually control their displays' brightness nor the light switches in their rooms, nor the sun or the moon).
