similar to: [ipxe-devel] Manual IP config does no pass 209:string to chain pxelinux.0

Hello list, I need understand more about cluster-size. Cluster size are small space when i create some file in ocfs2 disk, but when i read some data this size are small part that i can read? Or smal part are block-size to read? cluster-size are only to optimize fragmentation? I create my ocfs2 mounts with block-size 4k and cluster-size 1M and i have few files per filesystem with more than

A fancy pointers logic has been replaced with a plain old if / else branches. It was assigning only half of a 64 bits integer which is then assigned to a size_t. Thus leading to a bug on platform where size_t is 64 bits. Resolves bug #26 Signed-off-by: Celelibi <celelibi at gmail.com> --- Not sure if genec already issued a pull request for this patch or not. Anyway, here it is as

Hi list, I have some problems testing ocfs2. My test consist in: #server1: dd if=/dev/random of=/ocfs2_1/test & #server1: dd if=/dev/random of=/ocfs2_2/test & #server1: dd if=/dev/random of=/ocfs2_3/test & ... #server1: dd if=/dev/random of=/ocfs2_12/test & #server1:<Ctrl><Alt><SysRQ>B After that, another node begin recovery. After some time (+- 3min),

Hello Guys, After upgrade to 1.4.7-1 my FS does not mount anymore. Just after upgrade rpm, FS mount and works fine, but after reboot server, it does not work anymore. FS are created with ocfs2-1.4.4 and ocfs2-tools-1.4.3-1. If I downgrade to old version doesn't work too. Messages when trying to mount with new version: # mount /d01 mount.ocfs2: Device name specified was not found while

Hi, As requested on IRC, here are the step-by-step instructions to reproduce the failure I see: On http://rom-o-matic.net/gpxe/gpxe-1.0.1/contrib/rom-o-matic/build.php: output format: .dsk NIC type: e1000_82540 x CONSOLE_PCBIOS x CONSOLE_SERIAL BANNER_TIMEOUT: 20 COMCONSOLE: 0x3F8 _ COMPRESERVE COMSPEED: 57600 COMDATA: 8 COMPARITY: 0 COMSTOP: 1 x DOWNLOAD_PROTO_TFTP x DOWNLOAD_PROTO_HTTP _

Hello Peter, the following changes since commit 0620743d1e54cf48aa8e5cf5636739addae49d60: H. Peter Anvin (1): Merge remote-tracking branch 'mcb30/empty-tftp-ip' are available in the git repository at: git://repo.or.cz/syslinux/sherbszt.git gfxboot32 Sebastian Herbszt (4): gfxboot: use skipspace() gfxboot: don't use the bounce buffer gfxboot: remove

On Sat, Aug 30, 2014 at 6:40 AM, Michael Brown <mcb30 at ipxe.org> wrote: > and then just invoke wimboot as a UEFI binary (_not_ as a Linux kernel). I > don't know the configuration file syntax for this, sorry. > > Michael My understanding is that at this time there's no method to load an EFI binary from Syslinux. http://bugzilla.syslinux.org/show_bug.cgi?id=17

The behaviour of default ISRs as provided by the BIOS varies wildly between platforms. Some will simply iret, some will send EOI, some will send EOI and disable the interrupt at the PIC, some will crash the machine due to single-bit errors in the ISR address. When PXENV_UNDI_ISR_IN_START returns PXENV_UNDI_ISR_OUT_NOT_OURS, send the EOI ourselves rather than risking the unpredictable behaviour

If lwIP encounters a half-open connection (e.g. due to a restarted application reusing the same port numbers) it will correctly send a RST but will not resend the SYN until one retransmission timeout later (approximately three seconds). This can increase the time taken by lpxelinux.0 to fetch its configuration file from a few milliseconds to around 30 seconds. Fix by immediately retransmitting

The UDP binding logic will reuse local port numbers immediately. This causes problems for TFTP, which assumes a very low probability of a source port number being reused. The consequence is that lpxelinux.0 may end up downloading an incorrect file (e.g. attempting to download pxelinux.cfg/default but actually receiving a copy of ldlinux.c32, due to the port number having been reused). Fix by

> Date: Fri, 29 Aug 2014 13:02:10 +0100 > From: Michael Brown <mcb30 at ipxe.org> > To: Jason Jones <jason.s.jones at convergys.com>, "syslinux at zytor.com" > <syslinux at zytor.com> > Subject: Re: [syslinux] PXE booting WinPE with UEFI architecture > Message-ID: <54006BC2.3090703 at ipxe.org> > Content-Type: text/plain;

This got me closer, but it got to "Encapsulating winpe.wim..." and never went through the rest of the way. Ultimately PXELINUX apparently timed out and the machine rebooted. Here is relative portion of pxelinux: LABEL SCCM OSD Boot MENU LABEL ^2. SCCM OSD Boot com32 linux.c32 append wimboot initrdfile=bootmgr.exe,BCD,boot.sdi,winpe.wim TEXT HELP

Hi list, After upgrade my FreeBSD samba server from 3.0.5 to 3.0.6, my cifs client on my linux box stop. My linux kernel is 2.6.8.1 and samba* rpms is 3.0.6. But when try access any file (cat grupos.conf) on mounted point (smbfs) on freebsd server (3.0.6), this connection freeze. If samba on freebsd is 3.0.5 work's normally. This 2 logs generated with log level = 4 ---log on freebsd with

Signed-off-by: Julien Viard de Galbert <jviarddegalbert at online.net> --- efi/udp.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/efi/udp.c b/efi/udp.c index 1088f47..b0f13ad 100644 --- a/efi/udp.c +++ b/efi/udp.c @@ -163,7 +163,7 @@ void core_udp_connect(struct pxe_pvt_inode *socket, uint32_t ip, } else { udata.UseDefaultAddress = FALSE;

Trivial module to execute an arbitrary command. --- com32/modules/Makefile | 2 +- com32/modules/cmd.c | 42 ++++++++++++++++++++++++++++++++++++++++++ 2 files changed, 43 insertions(+), 1 deletions(-) create mode 100644 com32/modules/cmd.c diff --git a/com32/modules/Makefile b/com32/modules/Makefile index 2739a39..930e89b 100644 --- a/com32/modules/Makefile +++ b/com32/modules/Makefile

On Sat, Oct 24, 2015 at 6:15 PM, Michael Brown via Syslinux <syslinux at zytor.com> wrote: > Also, not a fork: http://git.ipxe.org/ipxe.git/commitdiff/8406115 A fork is a fork, regardless the reasons behind it (yes, I have some understanding in this case). iPXE is based off of forking further development as of a certain gPXE commit with some backporting of gPXE development to iPXE. --

On 30/08/14 02:00, Gene Cumm wrote: >> And then in the same location, I put this boot.ipxe file and all support >> files: >> >> #!ipxe >> kernel wimboot >> initrd bootmgr bootmgr >> initrd boot/bcd BCD >> initrd boot/boot.sdi boot.sdi >> initrd http://<SCCM-server>/boot.wim boot.wim >>

On 30/08/15 12:10, Gene Cumm via Syslinux wrote: > Those should produce debug text listing the original PxeBc handle and > its full MAC then proceed to list the UDPv4Sb handles and their MACs. > I'm still trying to figure out if there's a way to get the handle > numbers that the shells use. I looked into this for iPXE. From memory, it wasn't easily possible: the shell

On 02/03/16 22:47, Patrick Masotta via Syslinux wrote: > Not really, a virtual environment can easily emulate the BIOS_timer at 0x046C > but it has problems emulating a "real" timer interrupt to be hooked... > That's the real problem. The timer interrupt works fine in at least KVM, Xen, VMware, and Hyper-V. (I've tested iPXE in all of those virtual environments, and

On 28/08/14 19:38, Jason Jones wrote: > Anyone have luck with pxechn32 and bootmgfw.efi? > > I'm getting the "Unable to retrieve first package" issue as reported by others. > > Really, any advice for UEFI booting into a winpe environment off of pxelinux 6.03 would be beneficial. As it happens, I released a new version of wimboot with support for UEFI yesterday. The