linux-admin.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Glynn Clements <glynn@gclements.plus.com>
To: Alex <mysqlstudent@gmail.com>
Cc: linux-admin@vger.kernel.org
Subject: Re: Compiling 2.6 kernel questions
Date: Wed, 25 Nov 2009 04:07:12 +0000	[thread overview]
Message-ID: <19212.44400.48613.143756@cerise.gclements.plus.com> (raw)
In-Reply-To: <55e03a0a0911241518t622a90a4y1ed374eee8c4503d@mail.gmail.com>


Alex wrote:

> I'm trying to compile 2.6.32-pre8 and have some questions that I hoped
> someone could help me to answer. They aren't really specific to the
> kernel version, other than I'm using 2.6.
> 
> - Is it possible to compile a kernel with glibc-2.10.1 and run it on a
> system with a much older glibc version? Specifically, I'd like to
> upgrade a v2.4 kernel system to v2.6 with only the minimal amount of
> changes in order for it to run.

The version of glibc installed on the build system has no effect upon
the resulting kernel.

glibc tends to be quite independent of the kernel version. For the
most part, you can still run binaries linked against libc.so.5 on a
2.6 kernel.

> - Is it necessary to compile the IDE driver and ext2/3 filesystem
> driver into the kernel, or can that also be a module?

If you build either as a module, you need to use initrd or initramfs. 

> If so, and I put
> it in initrd,. how is it accessed? Isn't it a catch-22 without having
> support to access the very ramdisk that has the support that's
> necessary to access it?

To use initrd, the device driver and file system have to be built into
the kernel. 2.6 kernels support initramfs, which doesn't require a
separate device driver or filesystem module (the code is always built
into the kernel). See Documentation/filesystems/ramfs-rootfs-initramfs.txt
for details.

> If this can be done, where can I find info on the steps?

Unless you're particularly short for space, start by building a kernel
with IDE and ext2 built in, and deal with initrd/initramfs later.

> - Is there a general list of minimum requirements for compiling a
> recent 2.6 kernel? IOW,  module-init-tools, gcc, etc.

The file Documentation/Changes in the kernel source tree lists minimum
versions.

> - Does anyone use lilo anymore, or do all distros use grub?

Gentoo offers a choice of boot loaders; I use lilo.

-- 
Glynn Clements <glynn@gclements.plus.com>

  reply	other threads:[~2009-11-25  4:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-24 23:18 Compiling 2.6 kernel questions Alex
2009-11-25  4:07 ` Glynn Clements [this message]
2009-11-25  5:00   ` Alex
2009-11-25  9:02     ` Glynn Clements
2009-11-25 18:24       ` Alex
2009-11-25 22:51         ` Glynn Clements
2009-11-25 23:32           ` Alex
2009-11-26  4:35             ` Glynn Clements
2009-11-27  1:18               ` Alex
2009-11-28  0:27                 ` Glynn Clements

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=19212.44400.48613.143756@cerise.gclements.plus.com \
    --to=glynn@gclements.plus.com \
    --cc=linux-admin@vger.kernel.org \
    --cc=mysqlstudent@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).