<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On 5 December 2016 at 21:48, Haris Okanovic <span dir="ltr"><<a href="mailto:haris.okanovic@ni.com" target="_blank">haris.okanovic@ni.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div id=":17u" class="a3s aXjCH m158d11760704c566">Opkg can defer running postinst scripts to first boot, which can take<br>
a while on some systems. The output of `opkg configure` (or whatever pm<br>
is used) is redirected to a file when logging is enabled<br>
(I.e. $POSTINST_LOGGING == 1), making the machine appear hung during<br>
this process. This change simply prints a wait message on the console<br>
to inform the user of this potentially long and silent operation so<br>
that they do not mistakenly reboot their machine.<br></div></blockquote><div><br></div><div>This isn't opkg specific, all backends can do it.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div id=":17u" class="a3s aXjCH m158d11760704c566">
Why not simply `tee` the output instead?<br>
Tee might be provided by BusyBox in some distros, which may need to run<br>
update-alternatives in the very postinst scripts being executed by this<br>
process. It's therefore not safe to assume Tee (or any other packaged<br>
util) is available until the configure process finishes.</div></blockquote></div><br>Are the alternatives not configured at rootfs time, so it should be fine to run tee? (as if tee isn't safe, then neither is sed).</div><div class="gmail_extra"><br></div><div class="gmail_extra">Ross</div></div>