On Mon, May 07, 2007 at 08:12:54PM +0100, Ganesh Sittampalam wrote: > This bug still appears to be present in the etch release and breaks > existing scripts that use chrootuid. The -i workaround is available at the > cost of a change in behaviour. Is there any plan to fix it?
Hmmmm... I've forgotten about this bug. I've sent a new package to sid fixing this behaviour but I'm afraid it cannot be fixed in etch "fast". It seems the introduction of getopt broke the use of arguments in the command line for the command that gets "chrootuided". The current workaround (for etch) is to place your command+arguments in an executable script and call *that script*, instead of trying to add arguments to the command being executed by chrootuid in the command line itself. Regards Javier
signature.asc
Description: Digital signature
