Re: [Oslib-devel] Outsourcing the extender?

[Paolo G. <pao...@ti...>]

Hi Luca, Hi Peter,

I see no problem if the extender continues to be coded as a part of 
OSLib... As Luca already said, they can be thought as independent parts 
of the same projects...

The only reason why I could imagine that splitting the extender is a 
good reason is to make it more visible to people that do not want to use 
OSLib but that can anyway get advantages in using the extender...

I could suggest probably to make the eXtender page a lot more visible in 
the web page, actually it is somehow more hidden than the rest... (it is 
not cited in the Project Overview, but can be found in the 
subproject)... probably the weight of the web site should be half 
libraries/half extender...

>>And OSLIb should ignore, by which loader it was booted.

Yes and no... I would say the converse... X should be able to boot 
multiboot images that are not written knowing that they will be booted 
by the extender...

But if I boot with the extender, I got some nice features like the 
return to DOS, and the X_CallBIOS feature... that for example we use 
heavily inside the shark kernel (http://shark.sssup.it) to get support 
for the VESA graphic cards using BIOS calls...

Actually I tried to boot with X also another OS, called MarteOS 
(http://marte.unican.es) , and it worked fine... apart of course for the 
return to dos...

bye

PJ