I am trying to build my own kernel. I was wondering if choosing to make modules would still use a little space? Can you save space in the kernel by not making the module?

If you make a module it will take disk space, because it's a file laying around but it won't make your kernel any larger - or, if it does, it would be by an utterly insignificant degree. I don't know if it needs a little bit of code as a "plug" so to speak, or not. If you compile it in, then your kernel will be larger. If you do without the capacity altogether, it saves space both ways. If it's something you need, compile it in; if it's something you just want access to, make it a module; if it's something you don't need, leave it out. And, to an extent, this translates into RAM usage. If you compile everything in its going to use more RAM than a stripped kernel while loading it as a module will only use the RAM while its loaded.

At least that's how I understand it. Hope that's right and that it helps.

Thanks, thats what I figured. I was just wondering how much of an insignificant amount of kernel space it takes up. The problem is self made kernel isnt working yet because I am not absolutly positive of what modules are needed and so forth. So I have a lot of things [M] and I was wondering if that would make my kernel larger. Right now it is about 900kB I would like to see it around 700kB

Thanks for the reply its appreciated

M will make your kernel smaller and faster but modules will be created on the hd and you'll have to load these modules if you need it (well wrong most of time since kernel load them by itself)