>>I don't see any advantage in using a kit to develop >>the monitor though. What we're developing is very >>custom. What does OSKit have that you anticipate >>using for the monitor? >First and simpliest, there are some nice header files. >For example elf.h with definitions and data structures. >Then there are libs with one or another function we >could use - for example to help to load elf binaries. >(Well, perhaps this isn't such a good example, because >I write my own elf loading code... ;) I don't say, that >we must use OSKit, but we could if there is work done >in it for use which we don't want to implement a second >time. May be someone stubles over such a function - or not. >For now and first time, the question is if I could use >the elf.h from OSKit or if somebody says: oh no, I don't >want to get OSKit only for compiling FreeMWare. We can always "steal" and modify useful header files (that's what GPL is all about). I don't think there's a lot of other stuff that's useful for this project in the OSKit, that is worth using it for (a static ELF loader is pretty simple, y'know... anyway, once it starts working decently you should simply be able to use an existing bootloader, such as GRUB). Ramon
