Without looking at the specific problem, but here are some general remarks:
On Wed, Aug 08, 2007 at 09:46:21PM +0200, Mathieu GELI wrote: > > sed: -e expression #1, char 13: unterminated `s' command > > should be fixed in soon to be uploaded ~a22-1. > > The problem is supposed to be triggered by the fact that : > 1) sed doesn't like mutliline strings in script fragment sed supports N, P and D commands which can be used for limited multi-line work. http://www.opengroup.org/onlinepubs/009695399/utilities/sed.html > 2) dash's echo builtin doesn't escape \n as other shells do. Presumably this is because dash is SUSv3 but not XSI compliant, otherwise it's a bug in dash. http://www.opengroup.org/onlinepubs/009695399/utilities/echo.html As a quick comparison, both posh and Solaris' /bin/sh (which is notoriously limited) recognize \n. If you want to emit literal newlines, you can use printf(1). > So easy fix, is to use GNU echo (/bin/echo) were builtin echo is used. That should work fine for systems running GNU coreutils, but don't forget it won't work in the busybox environment used when bootstrapping the live image. -- Trent W. Buck
signature.asc
Description: Digital signature
_______________________________________________ debian-live-devel mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/debian-live-devel
