firmware-tools on SLES10: rug aborts with stacktrace
Michael E Brown
Michael_E_Brown at dell.com
Mon Feb 25 10:14:25 CST 2008
On Mon, Feb 25, 2008 at 03:34:52PM +0530, Charles_Rose at dell.com wrote:
> This probably has nothing to do with firmware tools, but I saw this 3
> out of 5 times on a SLES10 SP1 box. There were no problems during the
> other two runs. I plan to try this on another box and see what might be
> happening here.
Any help would be appreciated.
I dont do much with SLES and know very little about rug.
What you might try to figure out where this is coming from: Split out
the commands into two parts:
UPDATE_LIST=$( bootstrap_firmware | xargs -n1 -r rug --terse wp | cut -d'|' -f3 | grep -v "No matches")
rug install $UPDATE_LIST
That should at least tell you which rug command is having the problem.
If it is the first command, you can split it up as well, as it runs rug
multiple times. Something like this (untested):
for pkg in $( bootstrap_firmware )
do
echo "running pkg $pkg"
rug --terse wp $pkg
done
That would tell you if it is a specific package having a problem, or all
of them.
--
Michael
More information about the firmware-tools-devel
mailing list