Hello all,
I just wanted to touch base and let you know I'm starting a cycle to
get QBox updated, and will be using Bering-uClibc 3.0.
I may actually branch out QBox into 2 'versions.' One will be a
regular leaf package that can be installed normally. The other would
be that I branch off and
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
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 without
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
with
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 take