-----Original Message-----
> > > On Sunday 09 November 2003 14:07, Svetoslav Slavtchev wrote: > > [...] > > > > > > 2.4 with debuging (CONFIG_KSYMS=yes) > > > 1337954 Aug 25 17:47 /boot/vmlinuz-2.4.22-1mdk > > > > > > 2.4 without KSYMS (~ kernel tmb here) > > > 1035464 Nov 9 04:04 /boot/vmlinuz-2.4.22-21br.1mdk > > > > > > 2.6 without debuging > > > 1532105 Oct 29 19:37 /boot/vmlinuz-2.6.0-test9-bk2 > > > 1560749 Nov 4 04:42 /boot/vmlinuz-2.6.0-test9-bk8 > > > 1555036 Nov 5 13:11 /boot/vmlinuz-2.6.0-test9-bk9 > > > > > > isn't this a bit special :( > > > > > > > That is with standard mdk config? Yes it is bad if kernel does not fit on > > one > > floppy. > > if i didn't missed smth, it's a standard 2.4 mdk config [...] > in -mm i think there is config option to compile with -Os not -O2 > other alternatives to reduce the size are: > - to update/fix the bzip2 compression support patches > - to drop some of the schedulers, futexes, ... (CONFIG_EMBEDDED) > but i don't think the second is a good solution :( > I tried allmodconfig which resulted in ~1.2MB bzImage - same as 2.4.22-1mdk in your case. You have to add ELF support to it (as it is also module in this case) which apparently gives you bare minimum. It is likely that some features can be turned off, because allmodconfig actually tries to enable everything, either as "m" or as "y" (except CPU types support). Note that I am not even sure if it boots. I had at least one report about allmodconfig+devfs that could not mount IDE root but it may be due to other problems. Although modular IDE is "officially" not working (cf. post-halloween). Doing all as modules has practical problem - we must ensure that at least drivers for your keyboard available. I plan to add PNP hotplug support that should load drivers for on-board devices discovered via PNP BIOS but even then it will load serial chip driver only (i.e. i8042 in our case) - you still need explcitly load low level keyboard driver (atkbd or xtkbd). That is week point of current INPUT architecture :( This could be handled by initrd, sure - always add some standard driver unless correct one can be determined from user (drak?) config. Which adds yet another static configuration that can break :( Brave hearts can experiment with configuration starting from allmodconfig to see how much can be removed and how mauch has to be added for it to boot at all :) -andrey
