Re: Building a 2.6.30 kernel that does NOT require initrd

2009-09-30 Thread Andrew Perrin
On Wed, 30 Sep 2009, Alex Samad wrote: On Tue, Sep 29, 2009 at 09:51:12PM -0400, Andrew Perrin wrote: On Wed, 30 Sep 2009, Alex Samad wrote: On Tue, Sep 29, 2009 at 05:46:47PM -0400, Justin Piszcz wrote: [snip] I was just seeing if I was missing something, it just seems like a pain to hav

Re: Building a 2.6.30 kernel that does NOT require initrd

2009-09-30 Thread Tixy
On Tue, 2009-09-29 at 17:34 -0400, Justin Piszcz wrote: > Anyone else with grub2 have any advice for Andrew? Is it normal for grub2 > to show a blank screen when booting a kernel? When I upgraded to Grub2 last week I was getting a completely blank screen during kernel boot. Eventually I fixed th

Re: Building a 2.6.30 kernel that does NOT require initrd

2009-09-30 Thread Alex Samad
On Tue, Sep 29, 2009 at 09:51:12PM -0400, Andrew Perrin wrote: > On Wed, 30 Sep 2009, Alex Samad wrote: > > >On Tue, Sep 29, 2009 at 05:46:47PM -0400, Justin Piszcz wrote: [snip] > >I was just seeing if I was missing something, it just seems like a pain > >to have to recompile, although with all

Re: Building a 2.6.30 kernel that does NOT require initrd

2009-09-29 Thread Andrew Perrin
On Wed, 30 Sep 2009, Alex Samad wrote: On Tue, Sep 29, 2009 at 05:46:47PM -0400, Justin Piszcz wrote: [snip] Alex, How does having an initrd prove more or less beneficial than not having one? IMO I like simplicity and a straight forward boot configuration: 1. /boot/kernel 2. /boot/S

Re: Building a 2.6.30 kernel that does NOT require initrd

2009-09-29 Thread Alex Samad
On Wed, Sep 30, 2009 at 08:39:07AM +0800, Niu Kun wrote: > Alex Samad 写道: > >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,

Re: Building a 2.6.30 kernel that does NOT require initrd

2009-09-29 Thread Niu Kun
Alex Samad 写道: 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:

Re: Building a 2.6.30 kernel that does NOT require initrd

2009-09-29 Thread Alex Samad
On Tue, Sep 29, 2009 at 05:46:47PM -0400, Justin Piszcz wrote: > > [snip] > >>> > >> > >>Alex, > >> > >>How does having an initrd prove more or less beneficial than not > >>having one? > >> > >>IMO I like simplicity and a straight forward boot configuration: > >> > >>1. /boot/kernel > >>2. /boo

Re: Building a 2.6.30 kernel that does NOT require initrd

2009-09-29 Thread Justin Piszcz
On Wed, 30 Sep 2009, Alex Samad wrote: On Tue, Sep 29, 2009 at 05:36:38PM -0400, Justin Piszcz wrote: On Wed, 30 Sep 2009, Alex Samad wrote: 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 kern

Re: Building a 2.6.30 kernel that does NOT require initrd

2009-09-29 Thread Alex Samad
On Tue, Sep 29, 2009 at 05:36:38PM -0400, Justin Piszcz wrote: > > > On Wed, 30 Sep 2009, Alex Samad wrote: > > >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 o

Re: Building a 2.6.30 kernel that does NOT require initrd

2009-09-29 Thread Alex Samad
On Tue, Sep 29, 2009 at 05:34:57PM -0400, Justin Piszcz wrote: > Hi, > > Anyone else with grub2 have any advice for Andrew? Is it normal for > grub2 to show a blank screen when booting a kernel? I think grub2 add quiet to the kernel options and thus blank screen, edit the grub line on reboot and

Re: Building a 2.6.30 kernel that does NOT require initrd

2009-09-29 Thread Justin Piszcz
On Wed, 30 Sep 2009, Alex Samad wrote: 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 g

Re: Building a 2.6.30 kernel that does NOT require initrd

2009-09-29 Thread Justin Piszcz
Hi, Anyone else with grub2 have any advice for Andrew? Is it normal for grub2 to show a blank screen when booting a kernel? Justin. On Tue, 29 Sep 2009, Andrew Perrin wrote: I'm using grup-pc, which is grub2: che:/home/aperrin# dpkg -l | grep grub ii grub-common

Re: Building a 2.6.30 kernel that does NOT require initrd

2009-09-29 Thread Alex Samad
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/aper

Re: Building a 2.6.30 kernel that does NOT require initrd

2009-09-29 Thread Andrew Perrin
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, vers

Re: Building a 2.6.30 kernel that does NOT require initrd

2009-09-29 Thread Justin Piszcz
On Tue, 29 Sep 2009, Andrew Perrin wrote: On Mon, 28 Sep 2009, Justin Piszcz wrote: Hi, I have not used grub2, however- I will ask others on the list-- If you are compiling (most) everything into the image itself, you probably don't need the insmod line below and I am not sure you want t

Re: Building a 2.6.30 kernel that does NOT require initrd

2009-09-29 Thread Andrew Perrin
On Mon, 28 Sep 2009, Justin Piszcz wrote: Hi, I have not used grub2, however- I will ask others on the list-- If you are compiling (most) everything into the image itself, you probably don't need the insmod line below and I am not sure you want the search line either. menuentry "Debian GNU

Re: Building a 2.6.30 kernel that does NOT require initrd

2009-09-28 Thread Justin Piszcz
Hi, I have not used grub2, however- I will ask others on the list-- If you are compiling (most) everything into the image itself, you probably don't need the insmod line below and I am not sure you want the search line either. menuentry "Debian GNU/Linux, Linux 2.6.30 (recovery mode)" { ins

Re: Building a 2.6.30 kernel that does NOT require initrd

2009-09-28 Thread Andrew Perrin
Thanks for your continued interest. Answers below. -- Andrew J Perrin - andrew_perrin (at) unc.edu - http://perrin.socsci.unc.edu Associate Professor of Sociology; Book Review Editor, _Social Forces_ University of North Carolina

Re: Building a 2.6.30 kernel that does NOT require initrd

2009-09-28 Thread Justin Piszcz
On Mon, 28 Sep 2009, Andrew Perrin wrote: On Mon, 28 Sep 2009, Andrew Perrin wrote: Greetings- Using a .config file based on past kernels that have worked fine (posted at http://perrin.socsci.unc.edu/stuff/config), I am trying to compile kernel 2.6.30 for an amd64 machine and NOT using

Re: Building a 2.6.30 kernel that does NOT require initrd

2009-09-28 Thread Andrew Perrin
On Mon, 28 Sep 2009, Andrew Perrin wrote: Greetings- Using a .config file based on past kernels that have worked fine (posted at http://perrin.socsci.unc.edu/stuff/config), I am trying to compile kernel 2.6.30 for an amd64 machine and NOT using initrd. The essentials I know of - sata, ext3

Re: Building a 2.6.30 kernel that does NOT require initrd

2009-09-28 Thread Justin Piszcz
On Mon, 28 Sep 2009, Andrew Perrin wrote: Greetings- Using a .config file based on past kernels that have worked fine (posted at http://perrin.socsci.unc.edu/stuff/config), I am trying to compile kernel 2.6.30 for an amd64 machine and NOT using initrd. The essentials I know of - sata, ext3

Building a 2.6.30 kernel that does NOT require initrd

2009-09-28 Thread Andrew Perrin
Greetings- Using a .config file based on past kernels that have worked fine (posted at http://perrin.socsci.unc.edu/stuff/config), I am trying to compile kernel 2.6.30 for an amd64 machine and NOT using initrd. The essentials I know of - sata, ext3, e1000e - are built into the kernel, so I don