Also, there is actually a limit to what you can load internally and your kernel can get to big.. Least in the lilo days.. I don't remember if that was one of the things grub fixed or not..
But I remember in the 2.2 days, people were having that problem a lot.. > -----Original Message----- > From: brett holcomb [mailto:[EMAIL PROTECTED] > Sent: Thursday, October 02, 2003 10:57 AM > To: [EMAIL PROTECTED] > Subject: Re: [gentoo-user] modules vs. compiled in > > > Because you might now want to load it at boot so you leave > it as a module. When it's needed it is loaded - in some > cases automatically if I remember correctly. > > On Thu, 02 Oct 2003 09:48:09 -0400 > gabriel <[EMAIL PROTECTED]> wrote: > >on a recent thread, someone explained how to get your > >linux box to read > >a windows partition by compiling your kernel for > >vfat/ntfs support. > >they then went on to explain how to set it up so that > >your kernel can > >either (a) compile this stuff in, or (b) compile them as > >modules and > >load them automatically. > > > >so my question then is: why compile something as a > >module if you're > >going to load it into the kernel at boot anyway? what > >are the > >(dis)advantages? > > > >thanks > > > > > >-- > >[EMAIL PROTECTED] mailing list > > > > > -- > [EMAIL PROTECTED] mailing list > > -- [EMAIL PROTECTED] mailing list
