Comment 3 for bug 605831

The issue is not that jasper mangles the provided commandline, but that it completely ignores it, and sets hardcoded values. Better would be to parse and update the commandline, although this may require an additional tool, as string manipulation in busybox is a bit annoying.

The attached patch attempts to do some preservation of the prior commandline, using sed and expr, but it's fragile, and untested.