Hi Paul, Ron,
> One of the things I always bitch about here (and unfortunately don't
> help enough with) is improving on exactly this thing -- the packaging and
> installation of B-U along with the dev environment.
>
> If you feel the same way, it would be totally cool if you would be
> willing to
Ron Senykoff wrote:
> Sorry for the duplicate emails Eric...
>
>>> Instead of branching out, you could create a custom QOS, configdb and
>>> moddb package and a lwp plugin. The packages can be merged in an automatic
>>> way with the standard package to an image. This way you can just keep pace
>>>
Sorry for the duplicate emails Eric...
>>Instead of branching out, you could create a custom QOS, configdb and
>>moddb package and a lwp plugin. The packages can be merged in an automatic
>>way with the standard package to an image. This way you can just keep pace
>>with Bering-uClibc development
Hello Ron,
The nice thing about Bering-uClibc-3.0 is that you don't need to tune the
packages but only have to touch the configdb.lrp and moddb.lrp to have a
different configuration.
An other nice thing is that you can create an lwp web plugin specific for
QOS use, given it a specific webinterfac
On 3/29/06, Jorn Eriksen <[EMAIL PROTECTED]> wrote:
> Hey Maybe this could be another LEAF branch? Mike - did you not look for a
> new branch?
>
> Ron - is it a LRP package you have trouble with? In case which package is
> it?
I think I've found a solution for the init script problem based on
an
> at /var/webconf/www/lrcfg.cgi under the section "Daemon Status" for how other
> exceptions were handled.
Thanks for the pointer. Handling the exception is a good way to go IMO.
Cheers,
-Ron
---
This SF.Net email is sponsored by xPML, a groun
On Wednesday 29 March 2006 00:10, Ron Senykoff wrote:
> Hello all,
>
> Working on 2nd version of my qbox project
> http://www.cs.luc.edu/projects/comp412/q-box/
>
> I'm having trouble figuring out how to make lrp treat my init script
> as a script and not a daemon. At the end of running, it says "T
