On Thu, 2013-08-29 at 06:14 -0700, H. Peter Anvin wrote:> One of the main reasons for the code restructuring into ELF libraries is > that we should be able to set up configurations in memory. There are > two ways we could do that... either by manipulating the menu data > structures and just making them persistent, or by introducing a concept > of "in-memory files" which persist across modules. > > Which one would you think would be easier? The downside of the latter > is that the existing menu structure would not be available, but the > upside is that we wouldn't be introducing a whole new interface...It would also provide considerable flexibility for other uses...
On 08/29/2013 07:47 AM, Jeffrey Hutzelman wrote:> On Thu, 2013-08-29 at 06:14 -0700, H. Peter Anvin wrote: > >> One of the main reasons for the code restructuring into ELF libraries is >> that we should be able to set up configurations in memory. There are >> two ways we could do that... either by manipulating the menu data >> structures and just making them persistent, or by introducing a concept >> of "in-memory files" which persist across modules. >> >> Which one would you think would be easier? The downside of the latter >> is that the existing menu structure would not be available, but the >> upside is that we wouldn't be introducing a whole new interface... > > It would also provide considerable flexibility for other uses...Which one? -hpa
On Thu, 2013-08-29 at 13:19 -0700, H. Peter Anvin wrote:> On 08/29/2013 07:47 AM, Jeffrey Hutzelman wrote: > > On Thu, 2013-08-29 at 06:14 -0700, H. Peter Anvin wrote: > > > >> One of the main reasons for the code restructuring into ELF libraries is > >> that we should be able to set up configurations in memory. There are > >> two ways we could do that... either by manipulating the menu data > >> structures and just making them persistent, or by introducing a concept > >> of "in-memory files" which persist across modules. > >> > >> Which one would you think would be easier? The downside of the latter > >> is that the existing menu structure would not be available, but the > >> upside is that we wouldn't be introducing a whole new interface... > > > > It would also provide considerable flexibility for other uses... > > Which one?In-memory files could be used for things unrelated to the menu system. I don't have any examples immediately at hand.