From: Stefan ten Hoedt (stefth@sci.kun.nl)
Date: 09/29/92


From: stefth@sci.kun.nl (Stefan ten Hoedt (Contactpersoon Harry Duys))
Subject: Re: Kernel: I knew this would happen sooner or later.
Date: 29 Sep 1992 12:39:59 GMT

In article <1a2drcINN4nc@matt.ksu.ksu.edu> probreak@matt.ksu.ksu.edu (James Michael Chacon) writes:
>gt7080a@prism.gatech.EDU (Nathan Laredo) writes:
>
>>Well it finally happened to me for the first time when I went
>>and added in soundcard support to the kernel..
>
>>Boot sector 512 bytes.
>>Setup is 1576 bytes.
>>System is 327684 bytes.
>>System is too big
>>make: *** [Image] Error 1
>
>>Of course I can get rid of the scsi code and compile it, but
>>I don't think everyone would have that option.
>
>>Is it safe to just change SYS_SIZE in build.c? I assume it will
>>propigate itself to bootsect.s
>
>>Oh well.. I'll see what happens.. just felt like pointing out
>>a landmark.. at least for me...
>>--
>>|Nathan I. Laredo (this spot $9) gt7080a@prism.gatech.edu|tb |
>
>You shouldn't have any problem booting that kernal image, as my /vmlinux
>has been around 380k since 0.97.4 This is with all the base code, and a
>bunch of patches for things like ipc stuff and tcp/ip.
>
>James
>

That depends on the fact if you're using LILO or so. I remember that there
was another definition in bootsec.S or so. If you want to create a boot-disk
you still have to change that number there :-)

But I'm only an unknowing hacker...
        Are there any gurus around here who can give a definite answer?

Stefan ten Hoedt
stefth@sci.kun.nl -or-
stefth@zeus.cs.kun.nl