similar to: no menu.c32, no problem...

I am trying to build a distribution without having to be root. The SYSLINUX installer typically needs root to do loopback mounting, but if you have MTOOLS, you can use that instead. This seems to work so far: #!/bin/sh # A minimal replacement for /usr/bin/syslinux; assumes that ldlinux.sys # and ldlinux.bss are available in the current directory. You must # specify locations of mkdosfs and

This patch builds a floppy image with contains HDT, so users of GRUB or GRUB4DOS can use HDT too, without installing Syslinux. When you compile Syslinux, this floppy image isn't build automatically. To build it, runthe following from the extracted Syslinux source: $ cd ./com32/hdt $ make hdt.img As suggested by Pierre-Alexandre Meyer, all extra files required for building the floppy

Hi, I've got a couple of questions, I'm trying to get syslinux 2.10 to work on my Apacer Handy Steno TN202 128MB flash drive, I'm getting... root at will # syslinux /dev/sdb1 Total number of sectors not a multiple of sectors per track! Add mtools_skip_check=1 to your .mtoolsrc file to skip this test ...but if I try the same command on a mandrake box the syslinux command is

Hello, I need help in setting up tftpd-hpa to send a kernel to a client, on a debian woody installation. I did manage the feat when using tftpd to send a kernel to a client which had a separate network interface card, but I would like to do it with integrated LAN. Trials with tftpd failed with error messages starting with 'PXE', and later I learned that tftpd-hpa is needed for the PXE

Hello! ethersel.c32 does not seem to work with all PCs. I have prepared a floppy that uses ethersel.c32 to load a NIC-specific file (etherboot .zlilo image). See http://etherboot.anadex.de for details. It works with every NIC and every PC I own, but not with VMWare. I know VMWare has some problems, so that did not bother me at all and I published it anyway but I have received several e-mails

Having looked at some of the discussions circulating before, I tried the recipe that Bruce Bryne suggested to make a memory stick to be a RedHat EL bootable file system for RedHat installation, but then hit a "missing operating system" problem. Below are the steps I took: a. mkdosfs /dev/sdc1 b. mount /dev/sdc1 /mnt/stick c. cp rhas3u2/isolinux/* /mnt/stick where rhas3u2 is the

On Fri, Sep 27, 2002 at 05:00:35PM +0200, Steve wrote: > check you network, sounds like a hardware problem. > ARP is the Address Resolution Protocol and is a low level ethernet protocol. > > check this site out for more info > http://whatis.techtarget.com/definition/0,,sid9_gci213780,00.html > > Thanks for the comment. I got the same error (PXE E11 ARP timeout) with two

Hi, I'm sorry to bring this up again but I can't quit get this too work. I'm trying to build a 2.88 floppy image so that I can use PXE to load Ghost. I'm useing the following to get a copy of the bootsector: dd if=/dev/fd0 of=bootblock bs=512 count=1 Then I build the image file with: mformat -C -t 160 -s 18 -h 2 -B bootblock x: Then use mcopy to put the required

PXE-On-A-Disk from (ftp://ftp.scyld.com/private/jlehan/pxe-on-a-disk.html) was posted on syslinux mailing list: http://syslinux.zytor.com/archives/2005-December/006222.html. It is being mentioned by syslinux wiki, or some other documentation of syslinux that I currently can't find. I tried etherboot2ethersel.pl from PXE-On-A-Disk (ftp://ftp.scyld.com/private/jlehan/pxe-on-a-disk.html)

I seem to be having trouble getting the NFS root filesystem to mount after the kernel boots. As per thread from 2002 16 January (http://www.zytor.com/pipermail/syslinux/2002-January/000028.html), I double checked my DHCP config files, but to no avail. It cannot seem to attach to the mountd port on the bootserver. Here is some output from the kernel: loop: loaded (max 8 devices) Intel(R) PRO/1000

Hi, I've got the same Problem. Not with WinMe but Win 98SE. But what I figured out is, that it doesn't realy apply to the Command.com rather to the Way the BootImage was created. It took me a long time to get my Hands on a Image with 2.8MB that's working. Since creating one my self, was allways failling. I downloaded the Bootutils 4.3 from 3com and used the Imageedit tools. With these

Hello! I have been successful using SYSLINUX and Etherboot to create a generic "PXE-on-a-disk" package, a floppy image and CD image that support as many Ethernet cards as possible. These have support for all of Etherboot's modules that support real PCI cards: about 25-or-so drivers and 250-or-so cards. I've built Etherboot ZLILO images, one for each driver, set up to boot

On Thu, Dec 13, 2018 at 10:57 AM Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > @Carl, > > I'll repeat what I said in my prior email: you don't have to keep > looking, we already achieved what you want (considering that you are > willing to "disregard" the screen problems and similar issues, at least > for now, according to your own emails).

The device name is only used by guestfish (when using the -N option to prepare drives). We constructed the device name very naively, basically ‘sprintf ("/dev/sd%c", next_drive)’. This stores the device index instead, and only constructs the device name in guestfish. Also the device name is constructed properly using guestfs_int_drive_name so it can cope with #drives > 26. ---

Improve the error messages produced by C-based tools in case of issues with the command line options: - explicitly mention to use -a/-d (and -A/-D in virt-diff) - when extra arguments are found, mention the correct way to pass options to certain command line switches (like --format) - in virt-inspector, give a cleaner error message when neither -i nor any -m is specified In all the cases,

Hi.. Well i've tried each and every method to insert any winme command.com into any bootable image and its really giving me problems.... I even further tested the same image with reinserting the 98 command.com and the image worked just fine.. So acc to me the problem has to lie in me command.com as there is no real mode dos in ME.. Also try using umbpci.sys and lowdma.sys for managing

--autosysroot option uses suggestions to user on how to mount filesystems and change root suggested by --suggest option in virt-rescue. Commands are passed on kernel command line in format guestfs_command=command;. Command ends with a semicolon and there can be multiple commands specified. These are executed just before bash starts. On successfull run user is presented directly with bash in

On 06/09/2016 03:18 PM, Pino Toscano wrote: > In data mercoledì 1 giugno 2016 02:04:33, Maros Zatko ha scritto: >> --autosysroot option uses suggestions to user on how to mount filesystems >> and change root suggested by --suggest option in virt-rescue. > IMHO it should be called -i, like in the other tools, as what > --autosysroot does is basically the same. We can call it

This follows (tails) a log file within a guest, rather like the regular 'tail -f' command. For example: virt-tail -d guest /var/log/messages --- .gitignore | 3 + bash/Makefile.am | 4 +- bash/virt-alignment-scan | 6 + cat/Makefile.am | 47 ++++- cat/tail.c | 498 +++++++++++++++++++++++++++++++++++++++++++++++ cat/test-docs.sh

On Monday, 3 October 2016 13:27:13 CEST Richard W.M. Jones wrote: > This follows (tails) a log file within a guest, rather like > the regular 'tail -f' command. For example: > > virt-tail -d guest /var/log/messages > --- > .gitignore | 3 + > bash/Makefile.am | 4 +- > bash/virt-alignment-scan | 6 + > cat/Makefile.am |