[openbeosnetteam] Re: PPP homepage

> > I do not understand what you mean here. Calling load_image() from 
> > kernel-land?  
>  
> Yep. 

Evil!!! :)
Where do we get the environment pointer from?

> > Is that possible for apps that link against libbe.so? What will 
> > happen if that app crashes? Or is it possible to request the start of an 
> > app 
> > from kernel-land, but let it run as a userland app logged-in under a 
> specific 
> > user? 
>  
> Multi-user issue aside, I bet load_image() always create a new team. So it 
> can't be a kernel-land *team*, which is a special team that the kernel 
> self-create. 

Right, then let's try that. And Axel will have to think of something that makes 
this still work with multi-user support. ;)

> However, I never tried (yet!) to call load_image() from a driver or kernel 
> module, but if it works as expected, it would be great. 

This would be interesting to know.

> But a regular userland app (GUI or not) can perfectly do to that. 
> Even kernel drivers and modules can do files creation/modification/deletion, 
> in fact. 
> No need here for a daemon/permanent process waiting ad vitam eternam for 
> something net-related to do...  

A daemon could remove the entries on shutdown. If there was a B_SHUTTING_DOWN 
kernel message so PPP could know when to disconnect and remove the DNS entry it 
would work okay, too, but this can only be done by us.

Anyway, if that works I will create an app that is executed each time a 
connection is being established so it can check if the user must enter a 
password or if he wants to be asked before dialing.
Still, for immediate updating of the PPP settings (like default connection) I 
need kernel-land node-monitoring support (when will the kernel finally be 
usable?).

> > Which features do I plan for the preflet? :) I only remember a settings 
> > add-on for the modem driver (when it is finished) and finishing the 
> > error-checking stuff (and some UI improvements). Is there something missing 
> > that you would like to have? 
>  
> Well, displaying dial up interface(s) status and live statistics, like R5's 
> "Dial Up Networking" preflet. Which is also the one behind the deskbar 
> replicant... 

Oh, I did not plan to use the whole preflet for showing so little information. 
Also, there is no code in the preflet that handles the statistics.

> But it's not a mandatory design to follow. 
> I just guess users are used to such small GUI in Windows... and BeOS R5.0.x. 

Yes, a small window showing only the most important information is better than 
having loads of stuff the user is not interested in, but this does not have to 
be done by the preflet code.

> > The preflet will not be used for showing PPP stats. The PPPServer plug-in 
> > will add a Deskbar replicant that shows the stats and allows to disconnect. 
>  
> Deskbar replicants can be host in any app, not only permanent/background 
> ones. 
> The Deskbar app (his BShelf powering the deskbar tray view) will 
> reinstanciate 
> the deskbar item from the binary file where the object come from, thanks to 
> app signature. 

Right, but I would like to change the R5 design and add one symbol per 
connection. It will be possible to make the symbol always active for each 
interfaces individually, but that will not be the default.

Bye,
Waldemar

Other related posts: