sed syntax

Jeremy Huntwork jhuntwork at
Wed May 10 08:42:28 PDT 2006

Hey Guys,

Had a question about some of the sed syntax in the first half of the
book. Often, we're doing something like this:

cp -v configure{,.orig}
sed -e 's@/usr/include@/tools/include at g' configure.orig > configure

Just curious why we're running the sed on the 'configure.orig' file and
outputting to configure. We've already copied the file as a backup, so
we should be safe to sed the 'configure' file itself and shorten the
command, ie:

cp -v configure{,.orig}
sed -e 's@/usr/include@/tools/include at g' configure

Any reason why we're not doing it this way?


More information about the cross-lfs mailing list