Compile Kernel: Konfigurasi Kernel - Revision history

Onnowpurbo: /* Hasil Konfigurasi */

2014-04-18T23:29:26Z

Hasil Konfigurasi

← Older revision		Revision as of 23:29, 18 April 2014
Line 23:		Line 23:

	* Sebuah file bernama .config di top level directory berisi semua pilihan kita.		* Sebuah file bernama .config di top level directory berisi semua pilihan kita.
	* Sebuah file bernama autoconf.h di directory include/linux/ mendefinisikan (~~atai~~ tidak mendefinisikan) directory simbol CONFIG_* sehingga preprocessor C mengetahui apakah simbol tertentu akan di on-kan atau di off-kan.		* Sebuah file bernama autoconf.h di directory include/linux/ mendefinisikan (atau tidak mendefinisikan) directory simbol CONFIG_* sehingga preprocessor C mengetahui apakah simbol tertentu akan di on-kan atau di off-kan.

	Jika kita mempunyai file .config untuk mesin kita, copy saja itu ke directory kernel source dan jalankan		Jika kita mempunyai file .config untuk mesin kita, copy saja itu ke directory kernel source dan jalankan
Line 40:		Line 40:

	akan mengcopy default file ppc config ke .config.		akan mengcopy default file ppc config ke .config.


	==Tip untuk konfigurasi kernel==		==Tip untuk konfigurasi kernel==

Onnowpurbo: /* Pranala Menarik */

2013-05-08T22:41:01Z

Pranala Menarik

← Older revision		Revision as of 22:41, 8 May 2013
Line 85:		Line 85:
	* [[Linux: Skema Partisi di Linux]]		* [[Linux: Skema Partisi di Linux]]
	* [[Linux: Instalasi Sistem Operasi]]		* [[Linux: Instalasi Sistem Operasi]]
			* [[Membuat Repository Ubuntu Lokal menggunakan debmirror]]

	===Compile Kernel===		===Compile Kernel===
Line 121:		Line 122:
	* [[OpenWRT: Flash Buffalo WZRHP300N]]		* [[OpenWRT: Flash Buffalo WZRHP300N]]
	* [[OpenWRT: Flash UBNT NanoStation2]]		* [[OpenWRT: Flash UBNT NanoStation2]]
			* [[OpenWRT: Flash Linksys WRT160NL]]

	====Beberapa Tip====		====Beberapa Tip====

Onnowpurbo: /* Pranala Menarik */

2013-04-07T06:41:05Z

Pranala Menarik

@@ Line 74: / Line 74: @@
 * [[Linux]]
 * [[Ubuntu]]
 * [[Linux: CLI untuk Survival]]
-* [[Sistem Operasi]]
+* [[Linux: Skema Partisi di Linux]]
 * [[Linux: Instalasi Sistem Operasi]]
-* [[Linux: Skema Partisi di Linux]]
 * [[Kernel]]
 * [[Compile Kernel]]
 * [[Compile Kernel: Konfigurasi Kernel]]
-* [[Kernel: Anatomi Kernel Source]]
-* [[OS: Linux Kernel]]
+===Remaster Linux===
 * [[OS: Parameter Kernel Default]]
 * [[OS: Kernel Scheduler]]
 * [[OS: Complete Teori Tuning Kernel Scheduler]]
 * [[OS: Complete Teori Tuning I/O Performance]]
 * [[OS: Tuning Manajemen Memory]]
-* [[OS: Tuning Kernel Scheduler]]
-* [[OS: Tuning Completely Fair Queueing CFQ I/O scheduler]]
+===Android===
-* [[OS: Tuning Completely Fair scheduler CFS]]
 * [[OS: Build in Monitoring Tool]]
 * [[Linux Benchmarking]]
 * [[OS: Benchmarking menggunakan UnixBench]]
 * [[OS: Benchmarking menggunakan LLCBench]]

Onnowpurbo: /* Pranala Menarik */

2013-04-03T06:03:28Z

Pranala Menarik

← Older revision		Revision as of 06:03, 3 April 2013
Line 74:		Line 74:
	* [[Linux]]		* [[Linux]]
	* [[Ubuntu]]		* [[Ubuntu]]
			* [[Linux: CLI untuk Survival]]
	* [[Sistem Operasi]]		* [[Sistem Operasi]]
			* [[Linux: Instalasi Sistem Operasi]]
			* [[Linux: Skema Partisi di Linux]]
	* [[Kernel]]		* [[Kernel]]
	* [[Compile Kernel]]		* [[Compile Kernel]]
	* [[Compile Kernel: Konfigurasi Kernel]]		* [[Compile Kernel: Konfigurasi Kernel]]
			* [[Kernel: Anatomi Kernel Source]]
	* [[OS: Linux Kernel]]		* [[OS: Linux Kernel]]
	* [[OS: Parameter Kernel Default]]		* [[OS: Parameter Kernel Default]]
Line 83:		Line 87:
	* [[OS: Complete Teori Tuning Kernel Scheduler]]		* [[OS: Complete Teori Tuning Kernel Scheduler]]
	* [[OS: Complete Teori Tuning I/O Performance]]		* [[OS: Complete Teori Tuning I/O Performance]]
			* [[OS: Tuning Manajemen Memory]]
	* [[OS: Tuning Kernel Scheduler]]		* [[OS: Tuning Kernel Scheduler]]
	* [[OS: Tuning Completely Fair Queueing CFQ I/O scheduler]]		* [[OS: Tuning Completely Fair Queueing CFQ I/O scheduler]]
Line 90:		Line 95:
	* [[OS: Benchmarking menggunakan UnixBench]]		* [[OS: Benchmarking menggunakan UnixBench]]
	* [[OS: Benchmarking menggunakan LLCBench]]		* [[OS: Benchmarking menggunakan LLCBench]]
			* [[OS: Mengerti System Call]]
	* [[OS: Membuat Kernel Modul]]		* [[OS: Membuat Kernel Modul]]
			* [[OS: Android - Download]]

Onnowpurbo: /* Tip untuk konfigurasi kernel */

2013-04-03T04:47:34Z

Tip untuk konfigurasi kernel

← Older revision		Revision as of 04:47, 3 April 2013
Line 44:		Line 44:
	==Tip untuk konfigurasi kernel==		==Tip untuk konfigurasi kernel==

	* ~~Always turn on~~ "Prompt for development... drivers".		* Selalu aktifkan "Prompt for development... drivers".
	* ~~From~~ kernel 2.6.8, ~~you can add your own~~ string (~~such as your initials~~) at "Local version - append to kernel release" ~~to personalize your~~ kernel ~~version string~~ (~~for older~~ kernel ~~versions~~, ~~you have to edit the~~ EXTRAVERSION ~~line in the~~ Makefile).		* Sejak kernel 2.6.8, kita dapat menambahkan string sendiri (seperti inisial anda) di "Local version - append to kernel release" untuk personalisasi string versi kernel (untuk kernel yang lama, kita harus mengedit kalimat EXTRAVERSION di Makefile).
	* ~~Always turn off~~ module versioning, ~~but always turn on~~ kernel module loader, kernel modules ~~and~~ module unloading.		* Selalu matikan module versioning, tapi selalu nyalakan kernel module loader, kernel modules dan module unloading.
	* ~~In the~~ kernel hacking ~~section~~, ~~turn on all options except for~~ "Use 4Kb for kernel stacks instead of 8Kb". ~~If you have a slow machine~~, ~~don't turn on~~ "Debug memory allocations" ~~either~~.		* Di bagian kernel hacking, nyalakan semua opsi kecuali "Use 4Kb for kernel stacks instead of 8Kb". Jika kita menggunakan mesin yang pelan, jangan nyalakan "Debug memory allocations".
	* ~~Turn off features you don't need~~.		* Matikan fitur yang tidak kita butuhkan.
	* ~~Only use modules if you have a good reason to use a~~ module. ~~For example~~, ~~if you are working on a~~ driver, ~~you'll want to~~ load ~~a new version of it without~~ rebooting.		* Hanya gunakan module, jika kita mempunya alasan yang kuat untuk menggunakan module. Contoh, kita sedang mengerjakan sebuah driver, kita ingin me-load versi baru tanpa rebooting.
	* ~~Be extra sure you selected the right~~ processor ~~type~~. ~~Find out what~~ processor ~~you have now with~~ cat /proc/cpuinfo.		* Pastikan secara teliti kita memilih tipe processor yang benar. Cari tahu jenis processor yang kita pakai menggunakan perintah
	* ~~Find out what~~ PCI ~~devices you have installed with~~ lspci -v.
	* ~~Find out what your current~~ kernel ~~has compiled in with~~ dmesg \| less. ~~Most~~ device ~~drivers~~ print out ~~messages when they detect a~~ device.		cat /proc/cpuinfo.

			* Cari tahu PCI device apa yang kita install, gunakan perintah

			lspci -v.

			* Cari tahu kernel yang kita buat apakah sudah di compile dengan baik menggunakan perintah

			dmesg \| less.

			Kebanyakan device driver akan print out message ketika dia mendeteksi sebuah device.

	Jika semua gagal, copy file .config dari teman.		Jika semua gagal, copy file .config dari teman.

Onnowpurbo: /* Hasil Konfigurasi */

2013-04-03T04:38:58Z

Hasil Konfigurasi

← Older revision		Revision as of 04:38, 3 April 2013
Line 35:		Line 35:
	Jika kita tidak mempunyai .config, kita dapat membuat-nya dengan masuk ke setiap submenu dan men-on-kan atau meng-off-kan opsi yang kita butuhkan. menuconfig dan xconfig mempunyai opsi "Help" yang dapat memperlihatkan apa yang akan kita konfigurasi. Help untuk opsi tertentu, akan menolong kita dapat menentukan apakah opsi tersebut perlu di on atau di off-kan. RedHat dan berbagai distribusi seringkali memberikan contoh file .config di distribusi kernel source di subdirectory dengan nama configs di top-level source directory.		Jika kita tidak mempunyai .config, kita dapat membuat-nya dengan masuk ke setiap submenu dan men-on-kan atau meng-off-kan opsi yang kita butuhkan. menuconfig dan xconfig mempunyai opsi "Help" yang dapat memperlihatkan apa yang akan kita konfigurasi. Help untuk opsi tertentu, akan menolong kita dapat menentukan apakah opsi tersebut perlu di on atau di off-kan. RedHat dan berbagai distribusi seringkali memberikan contoh file .config di distribusi kernel source di subdirectory dengan nama configs di top-level source directory.

	~~If you are compiling for~~ PowerPC, ~~you have a variety of~~ default ~~configs to choose from in~~ arch/ppc/configs. ~~make defconfig will copy the default ppc config file to .config. If you know another source of default configuration files, let us know.~~		Jika kita mengcompile untuk PowerPC, kita mempunyai banyak sekali config default dari arch/ppc/configs. Perintah

	~~Tips for configuring a~~ kernel:		make defconfig

			akan mengcopy default file ppc config ke .config.


			==Tip untuk konfigurasi kernel==

	* Always turn on "Prompt for development... drivers".		* Always turn on "Prompt for development... drivers".
Line 50:		Line 55:

	Jika semua gagal, copy file .config dari teman.		Jika semua gagal, copy file .config dari teman.


	==Referensi==		==Referensi==

Onnowpurbo at 04:33, 3 April 2013

2013-04-03T04:33:44Z

← Older revision		Revision as of 04:33, 3 April 2013
Line 1:		Line 1:
	Sumber: http://www.linuxchix.org/content/courses/kernel_hacking/lesson2		Sumber: http://www.linuxchix.org/content/courses/kernel_hacking/lesson2


			==Konfigurasi Kernel==

	Linux kernel mempunyai beberapa tool konfigurasi. Setiap tool dapat di jalankan dengan menulis		Linux kernel mempunyai beberapa tool konfigurasi. Setiap tool dapat di jalankan dengan menulis
Line 7:		Line 9:

	di directory top-level dari source kernel. Semua perintah make harus di jalankan dari directory top-level dari source kernel.		di directory top-level dari source kernel. Semua perintah make harus di jalankan dari directory top-level dari source kernel.


	* '''make config''' - ini merupakan kerangka dasar dari tool konfigurasi. Ini akan menanya satu per satu dari pertanyaan konfigurasi secara berurut. Kernel Linux mempunyai amat sangat banyak pertanyaan konfigurasi. Jangan gunakan ini kecuali kita kurang kerjaan.		* '''make config''' - ini merupakan kerangka dasar dari tool konfigurasi. Ini akan menanya satu per satu dari pertanyaan konfigurasi secara berurut. Kernel Linux mempunyai amat sangat banyak pertanyaan konfigurasi. Jangan gunakan ini kecuali kita kurang kerjaan.
Line 16:		Line 17:

	* '''make xconfig, make gconfig''' - jika kita menjalankan Xwindows, maka ini lebih cantik, lebih di klik dari menuconfig. Konfigurator ini tampaknya tidak sebaik menuconfig karena lebih sensitif pada input file konfigurasi yang ada bug-nya (di samping, karena memang lebih banyak orang menggunakan menuconfig). xconfig menggunakan library qt, sedang gconfig menggunakan library gtk.		* '''make xconfig, make gconfig''' - jika kita menjalankan Xwindows, maka ini lebih cantik, lebih di klik dari menuconfig. Konfigurator ini tampaknya tidak sebaik menuconfig karena lebih sensitif pada input file konfigurasi yang ada bug-nya (di samping, karena memang lebih banyak orang menggunakan menuconfig). xconfig menggunakan library qt, sedang gconfig menggunakan library gtk.

			==Hasil Konfigurasi==

	Setiap program konfigurasi akan menghasilkan file berikut.		Setiap program konfigurasi akan menghasilkan file berikut.

	* Sebuah file bernama .config di top level directory berisi semua pilihan kita.		* Sebuah file bernama .config di top level directory berisi semua pilihan kita.
	* Sebuah file bernama autoconf.h di directory include/linux/ mendefinisikan (atai tidak mendefinisikan) directory simbol CONFIG_* sehingga ~~symbols so that the~~ C ~~preprocessor knows whether or not they are turned~~ on.		* Sebuah file bernama autoconf.h di directory include/linux/ mendefinisikan (atai tidak mendefinisikan) directory simbol CONFIG_* sehingga preprocessor C mengetahui apakah simbol tertentu akan di on-kan atau di off-kan.

			Jika kita mempunyai file .config untuk mesin kita, copy saja itu ke directory kernel source dan jalankan

			make oldconfig

			Kita dapat mencek ulang konfigurasu dengan perintah

			make menuconfig

	~~If you have a working~~ .config ~~file for your machine~~, just copy it into your kernel source directory and run make oldconfig. You should double check the configuration with make menuconfig. If you don't already have a .config file, you can create one by visiting each submenu ~~and turning~~ on or off ~~the options you need~~. menuconfig ~~and~~ xconfig ~~have a~~ "Help" ~~option that shows you the Configure~~.~~help entry for that option~~, ~~which may help you decide whether or not it should be turned~~ on. RedHat ~~and other distributions often include sample~~ .config ~~files with their distribution specific~~ kernel source ~~in a~~ subdirectory ~~named~~ configs ~~in the~~ top-level source directory. If you are compiling for PowerPC, you have a variety of default configs to choose from in arch/ppc/configs. make defconfig will copy the default ppc config file to .config. If you know another source of default configuration files, let us know.		Jika kita tidak mempunyai .config, kita dapat membuat-nya dengan masuk ke setiap submenu dan men-on-kan atau meng-off-kan opsi yang kita butuhkan. menuconfig dan xconfig mempunyai opsi "Help" yang dapat memperlihatkan apa yang akan kita konfigurasi. Help untuk opsi tertentu, akan menolong kita dapat menentukan apakah opsi tersebut perlu di on atau di off-kan. RedHat dan berbagai distribusi seringkali memberikan contoh file .config di distribusi kernel source di subdirectory dengan nama configs di top-level source directory.

			If you are compiling for PowerPC, you have a variety of default configs to choose from in arch/ppc/configs. make defconfig will copy the default ppc config file to .config. If you know another source of default configuration files, let us know.

	Tips for configuring a kernel:		Tips for configuring a kernel:
Line 37:		Line 50:

	Jika semua gagal, copy file .config dari teman.		Jika semua gagal, copy file .config dari teman.

Onnowpurbo at 04:25, 3 April 2013

2013-04-03T04:25:20Z

← Older revision		Revision as of 04:25, 3 April 2013
Line 17:		Line 17:
	* '''make xconfig, make gconfig''' - jika kita menjalankan Xwindows, maka ini lebih cantik, lebih di klik dari menuconfig. Konfigurator ini tampaknya tidak sebaik menuconfig karena lebih sensitif pada input file konfigurasi yang ada bug-nya (di samping, karena memang lebih banyak orang menggunakan menuconfig). xconfig menggunakan library qt, sedang gconfig menggunakan library gtk.		* '''make xconfig, make gconfig''' - jika kita menjalankan Xwindows, maka ini lebih cantik, lebih di klik dari menuconfig. Konfigurator ini tampaknya tidak sebaik menuconfig karena lebih sensitif pada input file konfigurasi yang ada bug-nya (di samping, karena memang lebih banyak orang menggunakan menuconfig). xconfig menggunakan library qt, sedang gconfig menggunakan library gtk.

	~~Each of the configuration programs produces these end products:~~		Setiap program konfigurasi akan menghasilkan file berikut.

	* A file ~~named~~ .config ~~in the~~ top-level directory ~~containing all your configuration choices~~.		* Sebuah file bernama .config di top level directory berisi semua pilihan kita.
	* A file ~~named~~ autoconf.h ~~in the~~ include/linux/ ~~directory defining~~ (~~or not defining~~) ~~the~~ CONFIG_* symbols so that the C preprocessor knows whether or not they are turned on.		* Sebuah file bernama autoconf.h di directory include/linux/ mendefinisikan (atai tidak mendefinisikan) directory simbol CONFIG_* sehingga symbols so that the C preprocessor knows whether or not they are turned on.

	If you have a working .config file for your machine, just copy it into your kernel source directory and run make oldconfig. You should double check the configuration with make menuconfig. If you don't already have a .config file, you can create one by visiting each submenu and turning on or off the options you need. menuconfig and xconfig have a "Help" option that shows you the Configure.help entry for that option, which may help you decide whether or not it should be turned on. RedHat and other distributions often include sample .config files with their distribution specific kernel source in a subdirectory named configs in the top-level source directory. If you are compiling for PowerPC, you have a variety of default configs to choose from in arch/ppc/configs. make defconfig will copy the default ppc config file to .config. If you know another source of default configuration files, let us know.		If you have a working .config file for your machine, just copy it into your kernel source directory and run make oldconfig. You should double check the configuration with make menuconfig. If you don't already have a .config file, you can create one by visiting each submenu and turning on or off the options you need. menuconfig and xconfig have a "Help" option that shows you the Configure.help entry for that option, which may help you decide whether or not it should be turned on. RedHat and other distributions often include sample .config files with their distribution specific kernel source in a subdirectory named configs in the top-level source directory. If you are compiling for PowerPC, you have a variety of default configs to choose from in arch/ppc/configs. make defconfig will copy the default ppc config file to .config. If you know another source of default configuration files, let us know.

Onnowpurbo at 04:18, 3 April 2013

2013-04-03T04:18:15Z

← Older revision		Revision as of 04:18, 3 April 2013
Line 1:		Line 1:
	Sumber: http://www.linuxchix.org/content/courses/kernel_hacking/lesson2		Sumber: http://www.linuxchix.org/content/courses/kernel_hacking/lesson2

	~~Kernel Hacking Lesson #2: Configure Your Kernel~~

	~~The~~ Linux kernel ~~comes with several configuration tools~~. ~~Each one is run by typing make <something>config in the top-level kernel source directory. (All make commands need to be run from the top-level kernel directory.)~~		Linux kernel mempunyai beberapa tool konfigurasi. Setiap tool dapat di jalankan dengan menulis

	make config		make <something>config

	~~This is the barebones configuration tool~~. ~~It will ask each and every configuration question in order. The Linux~~ kernel ~~has a LOT of configuration questions~~. ~~Don't use it unless you are a masochist.~~		di directory top-level dari source kernel. Semua perintah make harus di jalankan dari directory top-level dari source kernel.
	~~make oldconfig~~

	This will take the config file named .config and only ask the configuration questions which are not already answered in that file. This is most often used when upgrading to a more recent version of the kernel.
	~~make menuconfig~~

	~~This is the kernel hacker mainstay~~. ~~This command pops up a text-based menu-style configurator using the ncurses library~~. ~~You can descend into the menus that interest you and change only the configuration options you care about~~.		* '''make config''' - ini merupakan kerangka dasar dari tool konfigurasi. Ini akan menanya satu per satu dari pertanyaan konfigurasi secara berurut. Kernel Linux mempunyai amat sangat banyak pertanyaan konfigurasi. Jangan gunakan ini kecuali kita kurang kerjaan.
	make ~~xconfig, make gconfig~~
			* '''make oldconfig''' - ini akan membaca file konfigurasi .config dan akan bertanya konfigurasi yang belum di jawab di file tersebut. Cara ini biasanya digunakan untuk upgrade ke versi kernel yang lebih baru.

	~~If you~~'~~re running~~ Xwindows, ~~these are prettier~~, ~~clickable versions of~~ menuconfig. ~~They tends to work less often than~~ menuconfig ~~since they are more sensitive to buggy configuration~~ input ~~files than menuconfig~~ (~~and because more people use~~ menuconfig). xconfig ~~uses the~~ qt ~~libraries~~, ~~and~~ gconfig ~~uses the~~ gtk ~~libraries~~.		* '''make menuconfig''' - ini merupakan konfigurasi yang banyak digunakan oleh kernel hacker. Perintah ini menggunakan pop up berbasis text dan konfigurator menu-style menggunakan library ncurses. Kita bisa masuk ke satu menu yang kita tertarik dan mengubah hanya konfigurasi yang kita inginkan saja.

			* '''make xconfig, make gconfig''' - jika kita menjalankan Xwindows, maka ini lebih cantik, lebih di klik dari menuconfig. Konfigurator ini tampaknya tidak sebaik menuconfig karena lebih sensitif pada input file konfigurasi yang ada bug-nya (di samping, karena memang lebih banyak orang menggunakan menuconfig). xconfig menggunakan library qt, sedang gconfig menggunakan library gtk.

	Each of the configuration programs produces these end products:		Each of the configuration programs produces these end products:

	A file named .config in the top-level directory containing all your configuration choices.		* A file named .config in the top-level directory containing all your configuration choices.
	A file named autoconf.h in the include/linux/ directory defining (or not defining) the CONFIG_* symbols so that the C preprocessor knows whether or not they are turned on.		* A file named autoconf.h in the include/linux/ directory defining (or not defining) the CONFIG_* symbols so that the C preprocessor knows whether or not they are turned on.

	If you have a working .config file for your machine, just copy it into your kernel source directory and run make oldconfig. You should double check the configuration with make menuconfig. If you don't already have a .config file, you can create one by visiting each submenu and turning on or off the options you need. menuconfig and xconfig have a "Help" option that shows you the Configure.help entry for that option, which may help you decide whether or not it should be turned on. RedHat and other distributions often include sample .config files with their distribution specific kernel source in a subdirectory named configs in the top-level source directory. If you are compiling for PowerPC, you have a variety of default configs to choose from in arch/ppc/configs. make defconfig will copy the default ppc config file to .config. If you know another source of default configuration files, let us know.		If you have a working .config file for your machine, just copy it into your kernel source directory and run make oldconfig. You should double check the configuration with make menuconfig. If you don't already have a .config file, you can create one by visiting each submenu and turning on or off the options you need. menuconfig and xconfig have a "Help" option that shows you the Configure.help entry for that option, which may help you decide whether or not it should be turned on. RedHat and other distributions often include sample .config files with their distribution specific kernel source in a subdirectory named configs in the top-level source directory. If you are compiling for PowerPC, you have a variety of default configs to choose from in arch/ppc/configs. make defconfig will copy the default ppc config file to .config. If you know another source of default configuration files, let us know.
Line 37:		Line 36:
	* Find out what your current kernel has compiled in with dmesg \| less. Most device drivers print out messages when they detect a device.		* Find out what your current kernel has compiled in with dmesg \| less. Most device drivers print out messages when they detect a device.

	~~If all else fails~~, copy a .config ~~file from someone else. The grrls-only list is a good place to ask~~.		Jika semua gagal, copy file .config dari teman.

Onnowpurbo at 04:06, 3 April 2013

2013-04-03T04:06:55Z

← Older revision		Revision as of 04:06, 3 April 2013
Line 27:		Line 27:
	Tips for configuring a kernel:		Tips for configuring a kernel:

	Always turn on "Prompt for development... drivers".		* Always turn on "Prompt for development... drivers".
	From kernel 2.6.8, you can add your own string (such as your initials) at "Local version - append to kernel release" to personalize your kernel version string (for older kernel versions, you have to edit the EXTRAVERSION line in the Makefile).		* From kernel 2.6.8, you can add your own string (such as your initials) at "Local version - append to kernel release" to personalize your kernel version string (for older kernel versions, you have to edit the EXTRAVERSION line in the Makefile).
	Always turn off module versioning, but always turn on kernel module loader, kernel modules and module unloading.		* Always turn off module versioning, but always turn on kernel module loader, kernel modules and module unloading.
	In the kernel hacking section, turn on all options except for "Use 4Kb for kernel stacks instead of 8Kb". If you have a slow machine, don't turn on "Debug memory allocations" either.		* In the kernel hacking section, turn on all options except for "Use 4Kb for kernel stacks instead of 8Kb". If you have a slow machine, don't turn on "Debug memory allocations" either.
	Turn off features you don't need.		* Turn off features you don't need.
	Only use modules if you have a good reason to use a module. For example, if you are working on a driver, you'll want to load a new version of it without rebooting.		* Only use modules if you have a good reason to use a module. For example, if you are working on a driver, you'll want to load a new version of it without rebooting.
	Be extra sure you selected the right processor type. Find out what processor you have now with cat /proc/cpuinfo.		* Be extra sure you selected the right processor type. Find out what processor you have now with cat /proc/cpuinfo.
	Find out what PCI devices you have installed with lspci -v.		* Find out what PCI devices you have installed with lspci -v.
	Find out what your current kernel has compiled in with dmesg \| less. Most device drivers print out messages when they detect a device.		* Find out what your current kernel has compiled in with dmesg \| less. Most device drivers print out messages when they detect a device.

	If all else fails, copy a .config file from someone else. The grrls-only list is a good place to ask.		If all else fails, copy a .config file from someone else. The grrls-only list is a good place to ask.