search for: nonlinux

....rpm fa4f85d17c37e6fc1613bd7636f4ad934a12270f646c9e6aaa2de3a96ec4caf3 syslinux-devel-4.02-16.el6_5.i686.rpm 4abed4270bd04cbc63a58a01a3244f9fdd486784aae8f45bf790fc12772afff0 syslinux-extlinux-4.02-16.el6_5.i686.rpm b84c49dd7f4a2ee35e343ba498c5bac8d8fe4fb99680e1d07ed04fd0d79993f9 syslinux-extlinux-nonlinux-4.02-16.el6_5.i686.rpm 9bdbb2fa167103b470772cea7163d527886e7a78e18fb0943f79bde6fb2e2636 syslinux-nonlinux-4.02-16.el6_5.i686.rpm bb8a0979253957bb70654a75a318c7a6f4aaa6dbb911d9cc6d15b11b4a3b41ba syslinux-perl-4.02-16.el6_5.i686.rpm c539a6047b728b29a095eebb13003879ff1ace6ddc0b8932ec86485f3a87e700...

...-20151218.b1388.g8873b17.noarch > > http://goo.gl/Gm4ffO > /syslinux efi64 > syslinux-6.04-0.22.20151210git721a0af.fc24.x86_64.rpm > syslinux-efi64-6.04-0.22.20151210git721a0af.fc24.x86_64.rpm > syslinux-extlinux-6.04-0.22.20151210git721a0af.fc24.x86_64.rpm > syslinux-extlinux-nonlinux-6.04-0.22.20151210git721a0af.fc24.noarch.rpm > syslinux-nonlinux-6.04-0.22.20151210git721a0af.fc24.noarch.rpm > > http://git.zytor.com/users/pcacjr/syslinux.git/log/?h=multifs-for-upstream without the last two patches: 0009-s-MultiFS-multifs.patch 0010-efi-multifs-correctly-enumerate-p...

...s: It will be very helpful if you can provide some help on the same ASAP. Thanks and Regards -Lalit Aggarwal root@sunisv-testbox:/export/home/lalit >wine --version wine: creating configuration directory '//.wine'... fixme:cdrom:CDROM_GetInterfaceInfo not implemented for nonlinux wine: could not load /.wine-l80wdh/dosdevices/c:/windows/rundll32.exe as L"C:\\windows\\rundll32.exe": ld.so.1: wine: fatal: rundll32.exe: open failed: No such file or directory wine: wineprefixcreate failed while creating '//.wine'. root@sunisv-testbox:/export/home/lalit &g...

....rpm fa4f85d17c37e6fc1613bd7636f4ad934a12270f646c9e6aaa2de3a96ec4caf3 syslinux-devel-4.02-16.el6_5.i686.rpm 4abed4270bd04cbc63a58a01a3244f9fdd486784aae8f45bf790fc12772afff0 syslinux-extlinux-4.02-16.el6_5.i686.rpm b84c49dd7f4a2ee35e343ba498c5bac8d8fe4fb99680e1d07ed04fd0d79993f9 syslinux-extlinux-nonlinux-4.02-16.el6_5.i686.rpm 9bdbb2fa167103b470772cea7163d527886e7a78e18fb0943f79bde6fb2e2636 syslinux-nonlinux-4.02-16.el6_5.i686.rpm bb8a0979253957bb70654a75a318c7a6f4aaa6dbb911d9cc6d15b11b4a3b41ba syslinux-perl-4.02-16.el6_5.i686.rpm c539a6047b728b29a095eebb13003879ff1ace6ddc0b8932ec86485f3a87e700...

...git - 9e0926b Built with gcc (GCC) 5.2.1 20150902 (Red Hat 5.2.1-2) ISOLINUX & EXTLINUX tested on baremetal & QEMU/SeaBIOS - both PASSED/BOOTABLE Packages: syslinux-6.04-4.gcc5.2.1.git20151016.fc24.x86_64.rpm syslinux-extlinux-6.04-4.gcc5.2.1.git20151016.fc24.x86_64.rpm syslinux-extlinux-nonlinux-6.04-4.gcc5.2.1.git20151016.fc24.noarch.rpm syslinux-nonlinux-6.04-4.gcc5.2.1.git20151016.fc24.noarch.rpm Tested-by: poma <pomidorabelisima at gmail.com>

...0-1.fc24.noarch edk2.git-ovmf-x64-0-20151218.b1388.g8873b17.noarch http://goo.gl/Gm4ffO /syslinux efi64 syslinux-6.04-0.22.20151210git721a0af.fc24.x86_64.rpm syslinux-efi64-6.04-0.22.20151210git721a0af.fc24.x86_64.rpm syslinux-extlinux-6.04-0.22.20151210git721a0af.fc24.x86_64.rpm syslinux-extlinux-nonlinux-6.04-0.22.20151210git721a0af.fc24.noarch.rpm syslinux-nonlinux-6.04-0.22.20151210git721a0af.fc24.noarch.rpm

...??? ldlinux ? ? ??? ldlinux.c32 ? ??? core ? ??? isolinux.bin ??? syslinux-5186539-origin ? ??? bios ? ??? com32 ? ? ??? elflink ? ? ??? ldlinux ? ? ??? ldlinux.c32 ? ??? core ? ??? isolinux.bin ??? syslinux-nonlinux-6.04-3.git20150627.fc23.noarch ? ??? usr ? ??? share ? ??? syslinux ? ??? isolinux.bin ? ??? ldlinux.c32 ??? syslinux-nonlinux-6.04-4.git20150627.fc23.noarch-dollar-sign-then-the-caret-patched ??? usr ??? share ??? syslinux...

On 13.07.2015 18:48, Gene Cumm wrote: > On Mon, Jul 13, 2015 at 10:20 AM, poma <pomidorabelisima at gmail.com> wrote: >> On 13.07.2015 15:19, Gene Cumm wrote: >>> On Mon, Jul 13, 2015 at 9:03 AM, poma <pomidorabelisima at gmail.com> wrote: >>>> On 13.07.2015 14:53, Gene Cumm wrote: >>>>> On Mon, Jul 13, 2015 at 6:42 AM, poma

Digging into this, as we rework it, here's a question: assuming the system being pxebooted is server 1, and the tftp server is server 2, on server 2, in the menu for pxeboot, is there any way to specify that the image to boot, and the initrd, are on a server 3? That is, MENU repoboot KERNEL repo://my/repo/images/vmlinuz APPEND repo://my/repo/images/initrd.img (or an IP address, like

From: Sylvain Gault <sylvain.gault at gmail.com> TL;DR: The section aligment in linker scripts messed-up the memory mapping needed for the compression / decompression to work. The bug with gcc 5 is not trivial, I'll do my best to explain it here. Basically, there are two memory mappings of the code. One in "virtual memory", and one in "load memory". The one in

So last week I was wondering if XFS was still working -- even with its last on-disk structure changes -- and it _suprisingly_ worked as expected. Right, now I can finally get rid of GRUB and use Syslinux to boot my Linux on EFI from a rootfs with xfs. Shit, I have two partitions (the first one being the required ESP) so there is no way to access the other partitions since because Syslinux does not

See this bug for background information: https://bugzilla.redhat.com/show_bug.cgi?id=1350465 Thanks: Tomáš Golembiovský --- v2v/virt-v2v.pod | 38 ++++++++++++++++++++++++++------------ 1 file changed, 26 insertions(+), 12 deletions(-) diff --git a/v2v/virt-v2v.pod b/v2v/virt-v2v.pod index e68d75cf8..0943bf305 100644 --- a/v2v/virt-v2v.pod +++ b/v2v/virt-v2v.pod @@ -1909,18 +1909,32 @@ that

See this bug for background information: https://bugzilla.redhat.com/show_bug.cgi?id=1350465 --- v2v/virt-v2v.pod | 39 +++++++++++++++++++++++++++------------ 1 file changed, 27 insertions(+), 12 deletions(-) diff --git a/v2v/virt-v2v.pod b/v2v/virt-v2v.pod index e68d75cf8..93d1a9ecd 100644 --- a/v2v/virt-v2v.pod +++ b/v2v/virt-v2v.pod @@ -1909,18 +1909,33 @@ that guest through the RHV-M UI,

If the connection is not local, paths of disks will refer to the remote host, which were mistakenly handled as local paths (in the best case failing to open a non-existing disk, and in the worst case opening a different disk!). In case the disks are remote resources like ssh or ceph, nothing guarantees that the hostname can be reached from the local machine, or even that it is actually the same on

Hopefully this time ...