> 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/[EMAIL PROTECTED]'
> 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/[EMAIL PROTECTED]' configure
>
> Any reason why we're not doing it this way?
The standard sed doesn't know the option -i to operate
on the same file in input and in output. As we cannot
suppose what is the sed installed on the original
system, I think it's the reason, until the new sed is
installed with this useful option.
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
_______________________________________________
Clfs-dev mailing list
[email protected]
http://ninja.linux-phreak.biz/mailman/listinfo/clfs-dev
