Results 1 to 3 of 3

Thread: Geeky stuff part 2 : Making your own kernel compiling & configuring

  1. #1
    Jedi knight Luke Skywalker's Avatar
    Join Date
    Jul 2009
    Age
    23
    Liked
    0 times
    Posts
    2,175

    Default Geeky stuff part 2 : Making your own kernel compiling & configuring

    Now when you type this:
    sudo make menuconfig

    You will get lot of options but first you should press the second last option of load an alternative configurations which will be in your /boot partition.

    e.g. For fedora latest:
    /boot/config-2.6.31.9-174.fc12.x86_64

    In that you will see that many options are by <M> or <*> or by < >
    M=modules. When you do this options load at boot time as modules.
    *= built-in. Options are build as part of the kernel.
    You can safely switch between them.
    E.g.
    In file-systems:
    Choose which apply to you. No need for xfs or reiserfs or ext2 ( if you are not using them.
    Choose which apply to you as built in. Pressing space you can change M to none <> or builtin. If you don't know what the hell that option is. Press shift +/. It will show.
    In Device Drivers & Firmware Drivers apply to you as built in which is you need no need for including amd when you have intel & ATI when you have nvidia.
    See all the options. Wherever applicable made them built-in .
    If don't know ask here or some where.


    Type
    make

    It will compile a kernel in
    /usr/src/linux/arch/< whatever your arch is like x86 or x86_64 or sparc>/boot/bzImage
    BzImage is your kernel.
    Now copy kernel to /boot
    Create a link to boot & put it into boot.
    So that it look like /boot/boot



    Now in /boot/grub.conf or /boot/menu.lst ( depending upon your distro ubuntu have menu.lst & fedora have grub.conf. In future grub.conf will be standard as it have already been chosen for grub 2)
    You don't need initrd or intrafs.
    At last entry put all line except # (commented one) which are explanation:


    # Partition where the boot & root both partition is located If your kernel is located
    #/dev/sda then do as I have done
    title My own kernel
    root (hd0,2)
    kernel /boot/bzImage root=/dev/sda2
    #If not then asked me. Or try to understand if boot is at /dev/sdanumber Then
    #first line is root (hd0,number-1)
    # If / partition is at /dev/sdanumber than second line is
    #kernel /boot/bzImageroot root=/dev/sdanumber
    History is on the move,my friends.Those who cannot keep up will be left behind, to watch from distance.And those who stand in its way will not watch at all.
    To view links or images in signatures your post count must be 100 or greater. You currently have 0 posts.

    People are going to tell stories about me none of which change who I really am.

  2. #2
    Silver Member
    Join Date
    Dec 2008
    Liked
    0 times
    Posts
    370

    Default

    Though you are giving right instruction, it seems nobody is interested!! as most pre-compiled will satisfy their need so why bother about this? only some resource will be wasted.

  3. #3
    Jedi knight Luke Skywalker's Avatar
    Join Date
    Jul 2009
    Age
    23
    Liked
    0 times
    Posts
    2,175

    Default

    Some are just like that. They want all power they can get. & sometime people might need some feature like obscure filesystems then you will have to. Like ufs2. Also a custom kernel just run at 60% time the configured kernel

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Similar Threads

  1. Geeky stuff Part 1: Optimizing your compiler
    By Luke Skywalker in forum Linux
    Replies: 2
    Last Post: 02-04-10, 10:30 PM
  2. Replies: 0
    Last Post: 02-04-10, 10:26 PM