Hacker News new | past | comments | ask | show | jobs | submit login

well, at least you can choose from text or graphical user interfaces to browse and select the options needed to build a kernel!



I haven't compiled a kernel for over a decade, however back then it was

* make config

* make menuconfig

* make xconfig

Only one of those was of any use, the others were dumb.


Same here, only used menuconfig since both config and xconfig were unpractical. I'd be curious to read how many people still compile their kernel today for normal use (ie not for testing or kernel development). Back in the day I did because a new card often meant the driver (if any) was available as source only, while today nearly everything has been already built into modules and can be installed as such.


I compile my own ... for fun mostly. There are performance gains in selecting the correct CPU architecture for your machine. I have some old machines and it really makes a difference vs. distro stock kernels.

The modern procedure (for upgrading) is pretty straightforward:

make oldconfig; make; make modules_install; make install; reboot


Even modules that aren't distributed with the kernel are compiled via dkms, which apparently came out in 2003.

It means when I install a new kernel (as a deb), proprietary drivers like the blackmagic decklink ones are automatically recompiled.

It's very different now than in 2000.




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: