Displaying 8 results from an estimated 8 matches for "isoname".
Did you mean:
soname
2009 Dec 15
1
[PATCH] If the specified ISO does not exist, then the script dies.
...ith an explicit failure.
Signed-off-by: Darryl L. Pierce <dpierce at redhat.com>
---
autotest.sh | 4 ++++
1 files changed, 4 insertions(+), 0 deletions(-)
diff --git a/autotest.sh b/autotest.sh
index c67931a..904b961 100755
--- a/autotest.sh
+++ b/autotest.sh
@@ -723,6 +723,10 @@ done
isoname=$(basename $isofile)
isofile="$(cd `dirname $isofile`; pwd)/${isoname}"
+if ! [ -s "${isofile}" ]; then
+ die "Missing or invalid file: ${isofile}"
+fi
+
shift $(($OPTIND - 1))
set +u
--
1.6.5.2
2010 Mar 26
3
[PATCH node] Update autobuild and autotest scripts for new build structure
...{definition}\nPROMPT 0"
+ definition="${definition}\nLABEL pxeboot"
+ definition="${definition}\n KERNEL vmlinuz0"
+ definition="${definition}\n IPAPPEND 2"
+ definition="${definition}\n APPEND rootflags=loop initrd=initrd0.img root=/${isoname} rootfstype=auto console=tty0 check console=ttyS0,115200n8 $kernelargs"
+
+ debug "pxeboot definition=\n${definition}"
+ sudo bash -c "printf \"${definition}\" > $pxedefault"
+}
+
+# Starts a simple instance of dnsmasq.
+# $1 - the iface on which dnsmasq...
2008 Mar 28
1
3.0.0pre2 error on module, fine on subdir
Just tripped over this one today.
$ rsync --no-motd rsync://alphageek.dyndns.org/slackware
rsync: link_stat "." (in slackware) failed: No such file or directory (2)
rsync error: some files could not be transferred (code 23) at main.c(1498) [receiver=3.0.1pre2]
$ rsync --no-motd rsync://alphageek.dyndns.org/slackware/slackware-current
drwxr-xr-x 4096 2008/03/26 01:30:27
2009 Dec 15
1
[PATCH] The autotest timeout is now a command line configurable option.
...) tests=($OPTARG);;
- p) preserve_vm=true;;
+ p) preserve_vm=true;;
+ t) timeout_period=($OPTARG);;
v) set -v;;
w) show_viewer=true;;
h) usage; exit 0;;
@@ -738,6 +741,7 @@ log "Logging results to file: ${RESULTS}"
log "Begin Testing: ${isoname}"
log "Tests: ${tests}"
+ log "Timeout: ${timeout_period} ms"
for test in ${tests}; do
execute_test $test
--
1.6.5.2
2009 May 19
1
[PATCH node-image] Fixing the autotest script.
...5 +715,30 @@ set +u
if [ $# -gt 0 -a -n "$1" ]; then RESULTS=$1; else RESULTS=autotest.log; fi
set -u
+result_file=$(mktemp)
+debug "result_file=${result_file}"
+
log "Logging results to file: ${RESULTS}"
{
setup_for_testing
log "Begin Testing: ${isoname}"
+ log "Tests: ${tests}"
for test in ${tests}; do
execute_test $test
+ result=$?
+
+ if [ $result != 0 ]; then
+ echo "${result}" > $result_file
+ break
+ fi
done
log "End Testing: ${isoname}"
+
} | sudo tee --append $RESULTS
+...
2016 Mar 07
0
6.7 netinstall fails at insert cd to continue
<snip>
This it is a very easy process to create an installable usb key:
1. Download the iso file from a mirror.
2. Check the sha256sum with this from the command line:
sha256sum <isoname>
3. verify the output is the same as this list (for CentOS-6.7):
http://mirror.centos.org/centos-6/6.7/isos/x86_64/sha256sum.txt.asc
4. Find the name of your USB stick, from the command line (as root) you
can do:
fdisk -l | grep Disk | grep dev | grep -v mapper
You can also use the GUI dis...
2011 Dec 21
0
Trying to chainload from Syslinux to Grub with a custom config file
...iso images directly from syslinux, so I have been trying
to chainload to Grub with custom config files, but it has not been
working.
The way I have the liveCD image setup gives each iso it's own grub lst
file. When I try to boot to Grub I wind up at a Grub prompt. If I type
the contents of the isoname.lst file into the prompt I can boot the
iso without issue. This makes me think that there isn't any problem
with the way I'm booting Grub or the config file, but possibly with
the syntax I'm using to specify which config file to use in my
syslinux menu. A standard entry for this in my s...
2016 Mar 05
5
6.7 netinstall fails at insert cd to continue
On 03/05/16 09:04, Chris Murphy wrote:
> You don't say how you created the media.
>
--
true, i did not say how i created cd's.
i used k3b as it is easier, less to remember, than using command line.
usb's sticks were created using unetbootin and fedora-liveusb-creator.
yes, i did not mention that i tried with 2 usb sticks. failure was
same, did not feel it mattered. failure is