similar to: Booting an ISO with FreeDOS over PXE with memdisk

Before any tests are run, the ISO is checked and if it doesn't exist then the script exits with 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

Hello, I have a simple shell script that I use to generate an iso installer depending on the release version that I want. The thing is that I extract isolinux and menu.c32 from the syslinux rpm of the latest redhat release. The reason I am doing it this way is because of the This is what does it: copymenu32() { # $ cat /local/kickstart/templates/os-updates.txt # RedHat-5.8|20120425

Autobuild has to be updated to call make in the recipe directory and move the resulting iso to the main build directory. Importing the existing autotest.sh script from ovirt-node-image Signed-off-by: Mike Burns <mburns at redhat.com> --- autobuild.sh | 7 + autotest.sh | 764 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 2 files changed, 771 insertions(+), 0 deletions(-)

If the -p option is provided, then no VMs are destroyed. Instead they, and their related networks, are left intact. Signed-off-by: Darryl L. Pierce <dpierce at redhat.com> --- autotest.sh | 11 ++++++++++- 1 files changed, 10 insertions(+), 1 deletions(-) diff --git a/autotest.sh b/autotest.sh index c9f8a2d..b72ec98 100755 --- a/autotest.sh +++ b/autotest.sh @@ -219,6 +219,9 @@

(FreeDOS developers, I apologize for the redundant parts of this message. But I want to bring the SYSLINUX folks into the discussion, and the SourceForge mailing list archives are broken.) Background: I have a little Sourceforge project (http://unattended.sourceforge.net/) for which I use SYSLINUX to provide CD-ROM and PXE boot support for my boot disk. And it works great with MS-DOS. However,

By default it's 120 ms, but can be changed through command line arguments. Signed-off-by: Darryl L. Pierce <dpierce at redhat.com> --- autotest.sh | 16 ++++++++++------ 1 files changed, 10 insertions(+), 6 deletions(-) diff --git a/autotest.sh b/autotest.sh index c67931a..bcd9bd5 100755 --- a/autotest.sh +++ b/autotest.sh @@ -62,6 +62,7 @@ Usage: $ME [-n test_name] [LOGFILE] -i:

Well you can all read the thread here for the technical details: http://lists.gnu.org/archive/html/qemu-devel/2010-08/threads.html#00133 but the bottom line for anyone who wasn't in that discussion or on IRC last week is that we have to change the way that the appliance is built in libguestfs so that we don't depend (as much) on the qemu -initrd option. The bad thing is this is loads of

Now that it appears that some folks are able to get the 5.4 downloads (and a GREAT BIG THANK YOU to all the centos team members who make this possible!) I'm wondering when the updates will begin flowing so that those of us running 5.3 can do "yum upgrade" and enjoy all the benefits too? Thanks in advance! -- ---- Fred Smith -- fredex at fcshome.stoneham.ma.us

Hi all, got this every time: Error: Device 5632 (vbd) could not be connected. Backend device not found. didn''t have any problem in b95 Any idea? thanks Philip xm info host : snv release : 5.11 version : snv_97 machine : i86pc nr_cpus : 2 nr_nodes : 1 sockets_per_node : 1

Dear, "Xenoppix-x86-64(Xen3.0.2+KNOPPIX-x86_64-5.0.1) CD size" is released. http://unit.aist.go.jp/itri/knoppix/xen/index-en.html Xenoppix-x86-64 exploits latest CPU (Intel Core2 Duo and AMD Athlon64). * Xenoppix-x86-64 boots both X86 and X86_64 linux kernel on HVM of Xen. * Xenoppix-x86-64 looks like KNOPPIX but all packages are replaced for X86_64. * Xenoppix-x86-64 also

Simple code motion, no behaviour changes. --- builder/builder.ml | 46 ++++++++++++++++++++++++++-------------------- 1 file changed, 26 insertions(+), 20 deletions(-) diff --git a/builder/builder.ml b/builder/builder.ml index 9c26573..ec9919f 100644 --- a/builder/builder.ml +++ b/builder/builder.ml @@ -75,6 +75,30 @@ let remove_duplicates index = false ) index +(* Look for the

Hi, I'm trying to get the above working, without success so far: UNDIS.DOS refuses to load with an invalid NDIS stack message (from memory). keeppxe has some effect: it reduces the available conventional memory by 140 kbytes or so... still, the packet driver doesn't seem to find the interface. Does anybody have a working setup I could look at? -- Thanks, Feri.

Add detection code for "FreeDOS (eXtended FDisk)" MBR to disklib. Signed-off-by: Gert Hulselmans <gerth at zytor.com> --- com32/gpllib/disk/mbrs.c | 4 +++- 1 files changed, 3 insertions(+), 1 deletions(-) diff --git a/com32/gpllib/disk/mbrs.c b/com32/gpllib/disk/mbrs.c index 37309e1..6150fcf 100644 --- a/com32/gpllib/disk/mbrs.c +++ b/com32/gpllib/disk/mbrs.c @@ -27,7 +27,6

Hi all :) that's my first post, he =) I need some help about having the IPAPPEND 3 in my freedos (odin) environnement after a PXE boot using PXELinux / Memdisk... i've been searching for few hours now, but didn't found anything.. Is there a way to get that done ? Thanks in advance J?r?mie 'ahFeel' BORDIER

Hello: I read the archive posting for September 2005, http://syslinux.zytor.com/archives/2005-September/005809.html, where you stated that you have a freedos diskette that allows you to download and run an iso like it was a cd in a drive. I am in need of the ability to have a freedos bootable cd that contains other Linux ISO's that I could mount and boot to. In your experience with

I am using FreeDOS kernel 2.0.34 with FAT32 support (ke2034_32), together with PXELINUX and memdisk from SYSLINUX 2.0.9-pre15. I am experiencing this problem on multiple test systems (Dell Precision 450 and IBM T22 so far). My pxelinux.cfg/default has these lines: label test kernel memdisk append initrd=test.img keeppxe ...which let me boot my 1.44M "test.img"

With the same configuration an ISOLINUX CD which boots a FreeDOS Floppy image via MEMDISK Syslinux-3.73 crashes in VMWare and also on several newer boxes just after the kernel loading with "invalid OPCODE ...". Same CD with Syslinux-3.72 is working fine. Build environment for 3.72 was gcc-4.3.2 for 3.73 gcc-4.3.3 - any idea what can cause the troubles? --

Hi all, I'm going to create an USB flash disk. Here's the partition structure. Device Boot Start End Blocks Id System /dev/sdb1 * 1 537911 268955+ 83 Linux /dev/sdb2 537912 1598793 530441 c W95 FAT32 (LBA) /dev/sdb1 I used for installing boot loader(syslinux) and other small standalone utilities. /dev/sdb2 is used for

Hi, I'd like to create a bootable CD to run Ghost. Before generating the .iso, I tested it on a system with a FAT partition and had syslinux-4.05 installed. However it failed. Here are the steps : 1. copied "memdisk" to the FAT partition. 2. as my copy of Ghost (v11.50 from solution suite v2.5) no longer fits on a single floppy, I created a "large" floppy image of size

On Fri, May 23, 2014 at 8:29 AM, Ady <ady-sf at hotmail.com> wrote: > Testing the DOS-based Syslinux installer, syslinux.com, with the "-m" > parameter, I found that it works as expected under MS-DOS and its DOS > variants, but it seems to fail under FreeDOS (please correct me if > I'm wrong). This sounds like either a bug in FreeDOS or another undesirable negative