okay. So now it looks as though I actually lose functionality by using a ramdisk to gain multi-system flexibility. Perhaps I need to go back and look at compiling my own kernel now as opposed to learning mkinitrd...
But why is a ram disk now a standard part of the kernel-image? There must be a reason somewhere... now my curiosity is peaked. - Steve -----Original Message----- From: Michael Heldebrant [mailto:[EMAIL PROTECTED] Sent: Monday, August 06, 2001 4:08 PM To: Stephen Nosal Cc: debian-user@lists.debian.org Subject: RE: dist upgrade potato to woody 2.2 to 2.4 kernel I'm interested to see if that fixes it. I'm not sure why you would need the ramdisk but I'm sure it's there for a reason. Making kernels the debian way is actually really easy. Then you can install the new kernel as a package and remove etc like a package. Get fakeroot and kernel-package. Making kernels is as easy as one command (after config of course). You can even try and get the .config from the precompiled kernel so you only have to edit a few things. --mike On 06 Aug 2001 15:10:28 -0400, Stephen Nosal wrote: > Mike - > > so the initrd showed up in the kernel-image package along with instructions. > > Perhaps I should try this again and see if I'm missing something. Otherwise, > I guess I'll just have to compile my own... > > - Steve > > -----Original Message----- > From: Michael P. Soulier [mailto:[EMAIL PROTECTED] > Sent: Monday, August 06, 2001 2:11 PM > To: debian-user@lists.debian.org > Subject: Re: dist upgrade potato to woody 2.2 to 2.4 kernel > > > On Mon, Aug 06, 2001 at 12:49:09PM -0400, Stephen Nosal wrote: > > so, is it possible that the standard build requires a ramdisk, but if you > > 'roll your own' it is not necessary? > > > > If the above is true, and I wish to install the standard build kernel, how > > do I go about putting together this ramdisk and configuring it correctly? > is > > it as simple as an additional line in lilo? What creates the > > 'initrd-2.4.4-686' file? > > The file came with the kernel. In fact, the lilo line was made known to > me > during the install by a debconf message. > > Mike > > -- > Michael P. Soulier <[EMAIL PROTECTED]> > "With sufficient thrust, pigs fly just fine. However, this is not > necessarily a > good idea. It is hard to be sure where they are going to land, and it could > be > dangerous sitting under them as they fly overhead." -- RFC 1925 > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
