my current kernel is:
497855 /boot/vmlinuz
and the only modules generated from the kernel build are
ppp_deflate.o
bsd_comp.o
soundcore.o
usually,i don't even include modules support in my kernel but i need them to
be able to use my sound card (alsa driver only compile as modules),i look
forwa
Kelly Lynn Martin wrote:
> >image plus initrd can fit on a floppy-sized image. In our case, the
> >limit to kernel size is about 520k or thereabouts.
>
> Is that the size after bzipping? My current kernel is 422k bzipped,
> and I don't have _everything_ moduled out that I possibly could,
> alth
On Tue, 21 Dec 1999 11:00:21 +1300, Jamie Walker <[EMAIL PROTECTED]> said:
>We have machines here booting via network card bootROMs from a Novell
>server, and we need as much as possible in modules so the kernel
>image plus initrd can fit on a floppy-sized image. In our case, the
>limit to kernel
Kelly Lynn Martin wrote:
> >You'll save some memory by saying 'm' to things you don't need too
> >much, but that's about it.
>
> Also, you will probably have to put some stuff in modules if you use a
> lot of devices because there's a limit to how large your final
> monolithic kernel image can b
On Sun, 19 Dec 1999 21:50:44 -0500, Jeff Dike <[EMAIL PROTECTED]> said:
>You'll save some memory by saying 'm' to things you don't need too
>much, but that's about it.
Also, you will probably have to put some stuff in modules if you use a
lot of devices because there's a limit to how large your
> Obviously you would select n for items that you don't need included in
> your kernel, but what is the difference in saying y to support for my
> scsi or m?
For the average user, it doesn't make any difference. You need to say 'y' to
anything that you need to boot the kernel (so if you're boot
On Sun, Dec 19, 1999 at 09:50:44PM -0500, Jeff Dike wrote:
> > Obviously you would select n for items that you don't need included in
> > your kernel, but what is the difference in saying y to support for my
> > scsi or m?
>
> For the average user, it doesn't make any difference. You need to say
Hey Theresa,
Using modules in the kernel is good for when you want a smaller
kernel and you don't use the module in question to operate the system. ie
-> vfat, ntfs support are better as modules. Scsi support you probably
want to compile in the kernel, unless its a card for a scanner or li
Hi again folks,
got another question for you, When running xconfig I know that the m stands for
module, but when would you select module over y? Obviously you would select n for
items that you don't need included in your kernel, but what is the difference in
saying y to support for my scsi o
