Re: Building a 2.6.30 kernel that does NOT require initrd

To: debian-user@lists.debian.org
Subject: Re: Building a 2.6.30 kernel that does NOT require initrd
From: Alex Samad <alex@samad.com.au>
Date: Wed, 30 Sep 2009 07:34:03 +1000
Message-id: <[🔎] 20090929213403.GA10653@samad.com.au>
Mail-followup-to: debian-user@lists.debian.org
In-reply-to: <[🔎] alpine.DEB.2.00.0909291333210.20418@perrin.socsci.unc.edu>
References: <[🔎] alpine.DEB.2.00.0909272135160.12897@perrin.socsci.unc.edu> <[🔎] alpine.DEB.2.00.0909280837150.27567@p34.internal.lan> <[🔎] alpine.DEB.2.00.0909281309080.12897@perrin.socsci.unc.edu> <[🔎] alpine.DEB.2.00.0909281334570.27567@p34.internal.lan> <[🔎] alpine.DEB.2.00.0909281352270.12897@perrin.socsci.unc.edu> <[🔎] alpine.DEB.2.00.0909281406280.22508@p34.internal.lan> <[🔎] alpine.DEB.2.00.0909291216180.20418@perrin.socsci.unc.edu> <[🔎] alpine.DEB.2.00.0909291227290.3085@p34.internal.lan> <[🔎] alpine.DEB.2.00.0909291333210.20418@perrin.socsci.unc.edu>

Hi

question question to both of you guys, any reason not to use a initrd ?

doesn't it limit your options a lot, I can understand a monolithic
kernel - but a partial one ?

Alex

On Tue, Sep 29, 2009 at 01:33:57PM -0400, Andrew Perrin wrote:
> I'm using grup-pc, which is grub2:
> 
> che:/home/aperrin# dpkg -l | grep grub
> ii  grub-common
> 1.97~beta3-1 GRand Unified Bootloader, version 2 (common files)
> ii  grub-pc
> 1.97~beta3-1 GRand Unified Bootloader, version 2 (PC/BIOS version)

[snip]

Attachment: signature.asc
Description: Digital signature

Reply to:

Follow-Ups:
- Re: Building a 2.6.30 kernel that does NOT require initrd
  - From: Justin Piszcz <jpiszcz@lucidpixels.com>
- Re: Building a 2.6.30 kernel that does NOT require initrd
  - From: Niu Kun <haoniukun@gmail.com>

References:
- Building a 2.6.30 kernel that does NOT require initrd
  - From: Andrew Perrin <clists@perrin.socsci.unc.edu>
- Re: Building a 2.6.30 kernel that does NOT require initrd
  - From: Justin Piszcz <jpiszcz@lucidpixels.com>
- Re: Building a 2.6.30 kernel that does NOT require initrd
  - From: Andrew Perrin <clists@perrin.socsci.unc.edu>
- Re: Building a 2.6.30 kernel that does NOT require initrd
  - From: Justin Piszcz <jpiszcz@lucidpixels.com>
- Re: Building a 2.6.30 kernel that does NOT require initrd
  - From: Andrew Perrin <clists@perrin.socsci.unc.edu>
- Re: Building a 2.6.30 kernel that does NOT require initrd
  - From: Justin Piszcz <jpiszcz@lucidpixels.com>
- Re: Building a 2.6.30 kernel that does NOT require initrd
  - From: Andrew Perrin <clists@perrin.socsci.unc.edu>
- Re: Building a 2.6.30 kernel that does NOT require initrd
  - From: Justin Piszcz <jpiszcz@lucidpixels.com>
- Re: Building a 2.6.30 kernel that does NOT require initrd
  - From: Andrew Perrin <clists@perrin.socsci.unc.edu>

Prev by Date: Suggestions for desktop manager: [was Re: Fast booting for a Debian system - and suggestions for said system]
Next by Date: Re: Building a 2.6.30 kernel that does NOT require initrd
Previous by thread: Re: Building a 2.6.30 kernel that does NOT require initrd
Next by thread: Re: Building a 2.6.30 kernel that does NOT require initrd
Index(es):
- Date
- Thread