mike007 wrote: ↑Sat May 04, 2019 16:16
Yeah pasting it from the Wiz into here was the part I thought I'd need the connection for. Anyway, I'll learn how to do that if and when I have another problem.
The generic way to do it is to create a shell script file, copy it onto a USB stick, plug the USB stick into the Beyonwiz, and run the command there using the FileCommander (MENU>Files / Sources).
The script must have extension
.sh (FileCommander requirement) & it should redirect command output into a file on the USB stick.
Here's a basic framework for a script that does this. This one is useful in itself: it reports on the Ethernet device status without needing the network to be running
Code: Select all
#!/bin/sh
# Try to put the output in a file named after the script, in
# the same directory as the script (assuming being run from
# FileCommander)
outfile=script.out
dirname=`dirname $0`
basename=`basename $0 .sh`
[ -n "$basename" ] && outfile=$basename.out
outfile=$dirname/$outfile
# Run stuff with the stderr and stdout going into the file
# and also to stdout
{
# Put whatever commands you want to run in here
echo ==== ethtool ===
ethtool eth0
echo ==== ifconfig ===
ifconfig eth0
} 2>&1 | tee $outfile
If the script is called
xxx.sh, the output file will be in
xxx.out, and if you run the script from FileCommander, the output file will be in the same directory as the script.
The
{ ... } groups commands together so that their outputs can be conveniently redirected to the same place, the
2>&1 | redirects stderr to stdout and then redirects stdout to a pipes into
tee which copies its stdin to a file and to its stdout.
Using
tee means you can also see the output of the commands in the FileCommander's Console output screen.
