lkml.org 
[lkml]   [1996]   [Mar]   [21]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: Jettisoning init code (was: nfsroot anyone?)
Date
Followup to:  <199603181437.OAA24618@snowcrash.cymru.net>
By author: Alan Cox <alan@cymru.net>
In newsgroup: linux.dev.kernel
>
> > I'm going to take a look into this ASAP. However, I don't think implemen-
> > ting BOOTP into the kernel (as with 1.3.75) is such a good idea. It blows
> > up the kernel binary for being used just once. This should instead go into
>
> This is part of a global Linux memory/segment planning problem. There is no
> way to put all the init code into a discardable memory area thrown after
> boot.
>

It seems to me that the way to do it would be to have another segment
for this. I *think* ELF can support more segments than .code and
.data. Is there any way to get gas/gcc to use them, and if not, how
hard would it be to hack them to support .initcode and .initdata
segments?

-hpa

--
PGP public key available - finger hpa@zytor.com
"The earth is but one country, and mankind its citizens." -- Bahá'u'lláh
I don't work for Yggdrasil, but they sponsor the linux.* hierarchy.


\
 
 \ /
  Last update: 2005-03-22 13:36    [W:0.142 / U:0.444 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site