compiling the linux-2.6 kernel?

[sam111]

I have read thru the README file

decompressed the tar file to my a local home directory folder
then cd linux-2.6.38.2
then did issued

make O=/home/xxxx/testlinuxkernel/ menuconfig

which gave me the output

  HOSTCC  scripts/basic/fixdep
  HOSTCC  scripts/basic/docproc
  GEN     /home/nate/testlinuxkernel/Makefile
  HOSTCC  scripts/kconfig/conf.o
  HOSTCC  scripts/kconfig/kxgettext.o
  HOSTCC  scripts/kconfig/lxdialog/checklist.o
  HOSTCC  scripts/kconfig/lxdialog/inputbox.o
  HOSTCC  scripts/kconfig/lxdialog/menubox.o
  HOSTCC  scripts/kconfig/lxdialog/textbox.o
  HOSTCC  scripts/kconfig/lxdialog/util.o
  HOSTCC  scripts/kconfig/lxdialog/yesno.o
  HOSTCC  scripts/kconfig/mconf.o
  HOSTCC  scripts/kconfig/zconf.tab.o
  HOSTLD  scripts/kconfig/mconf
scripts/kconfig/mconf Kconfig

I then got into a blue .config screen but don't know what to push / from their so I just exited.

I went back to the testlinuxkernel top directory to see if anything other then the linux-2.6 kernel folder was in this directory I saw that it created included , script , and source (which is a shortcut/link back to linux-2.6 folder) , and one Makefile.

When I look in the include folder or any subfolders nothings their not even in the config folder.

any help would be great.

[jayd512]

Hello and Welcome!

Taken from The Linux Kernel HOWTO: How to actually configure the kernel

You are ready to answer the questions, usually with `y' (yes) or `n' (no). Device drivers typically have an `m' option. This means ``module,'' meaning that the system will compile it, but not directly into the kernel, but as a loadable module. A more comical way to describe it is as ``maybe.'' Some of the more obvious and non-critical options are not described here; see the section ``Other configuration options'' for short descriptions of a few others. With `make menuconfig', the space bar toggles the selection.

In other words, you have to decide which device drivers to include in your custom kernel. And you'll also need to include any file systems that you plan on using/accessing.

[hazel]

When configuring the kernel, do use the built-in help facility as much as possible; I can't recommend it too highly. Just press H or tab down to HELP at the bottom of the page.

Kernel help is not like any other help system you've ever seen: it not only tells you what each option does, but often tells you whether you should select it or not. It tells you things like: "If in doubt, say yes" or "If you don't know what this is, you don't need it".

There should be a default config file already present, so if you feel really nervous you can build your kernel from that the first time, then make incremental changes and customisations as you get more confident.

[Rubberman]

Myself, I prefer to use xconfig instead of menuconfig, though you have to be running on a GUI to do this. All the help stuff is automatically shown in the lower panel of the window, and navigating/searching for stuff is a lot easier. You can also run it in the background, as in make xconfig & so you can move the window around, reduce its size, minimize it, and do other stuff.

[jayd512]

I've never once had any luck with xconfig. But, as they say, your mileage may vary.

Either way, just make sure that you have a copy of your working config file saved before you start tinkering... can really save yourself a headache!