similar to: Build fixes...

On Wed, Feb 6, 2019 at 2:35 PM H. Peter Anvin via Syslinux <syslinux at zytor.com> wrote: > > On 2/6/19 9:17 AM, Joakim Tjernlund via Syslinux wrote: > > On Wed, 2019-02-06 at 16:00 +0100, Joakim Tjernlund wrote: > >> On Tue, 2019-02-05 at 14:07 -0800, H. Peter Anvin via Syslinux wrote: > >>> CAUTION: This email originated from outside of the organization. Do

Hey folks, This might be a daft idea, but is there any way to shut down solaris / zfs without flushing the slog device? The reason I ask is that we''re planning to use mirrored nvram slogs, and in the long term hope to use a pair of 80GB ioDrives. I''d like to have a large amount of that reserved for write cache (potentially 20-30GB), to facilitate rapid suspend to disk of

On Tue, Jul 23, 2019 at 1:30 PM Sebastian Herbszt <herbszt at gmx.de> wrote: > > hpa wrote: > > On July 7, 2019 8:37:10 AM PDT, Sebastian Herbszt <herbszt at gmx.de> > > wrote: > > >Gene, > > > > > >it looks like the syslinux master branch is broken since February > > >[1]. Peter created the wip.makefixes branch but I wasn't

As suggested, I have made a 6.04-pre3 release. In addition to updating gnu-efi to the latest version available (3.0.9 + a few patches) I wanted to make the tree compile with -Werror on my box, which resulted in pulling a thread which in turn caused a whole bunch of things to unravel :) The end result was that I ended up refactoring much of the tree so that it now avoids building a ton of

2015-10-15 12:53 UTC+02:00, Gene Cumm <gene.cumm at gmail.com>: > On Mon, Oct 5, 2015 at 2:15 PM, celelibi--- via Syslinux > <syslinux at zytor.com> wrote: >> From: Sylvain Gault <sylvain.gault at gmail.com> >> >> Some linker scripts were splitted into i386 and x86_64 versions in >> commit d8eede3f2a360163235fad222a0190cd7c5bef38 but older scripts

On Thu, 2019-02-07 at 06:12 -0500, Gene Cumm wrote: > On Wed, Feb 6, 2019 at 2:35 PM H. Peter Anvin via Syslinux > <syslinux at zytor.com> wrote: > > On 2/6/19 9:17 AM, Joakim Tjernlund via Syslinux wrote: > > > On Wed, 2019-02-06 at 16:00 +0100, Joakim Tjernlund wrote: > > > > On Tue, 2019-02-05 at 14:07 -0800, H. Peter Anvin via Syslinux wrote: > >

It looks like it is more like the issue in bug #26. In the tcpdump I can see the client attempt to RRQ the kernel but the client itself reports "No file found." I am having similiar issues as reported in both bug reports with getting Syslinux 6.02 to work as in syslinux64.efi gets pulled but then the client gets stuck on ldlinux.e64. Can I use http/nfs instead after syslinux64.efi gets

I have a pool with a single SLOG device rated at Y iops. If I add a second (non-mirrored) SLOG device also rated at Y iops will my zpool now theoretically be able to handle 2Y iops? Or close to that? Thanks, Ray

hpa wrote: > On July 7, 2019 8:37:10 AM PDT, Sebastian Herbszt <herbszt at gmx.de> > wrote: > >Gene, > > > >it looks like the syslinux master branch is broken since February > >[1]. Peter created the wip.makefixes branch but I wasn't able to get > >it working (yet) and it lacks activity since March. > > > >I think it might be time to revert

On 2/6/19 9:17 AM, Joakim Tjernlund via Syslinux wrote: > On Wed, 2019-02-06 at 16:00 +0100, Joakim Tjernlund wrote: >> On Tue, 2019-02-05 at 14:07 -0800, H. Peter Anvin via Syslinux wrote: >>> CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. >>>

Hello all... I''m seeing this behaviour in an old build (89), and i just want to hear from you if there is some known bug about it. I''m aware of the "picket fencing" problem, and that ZFS is not choosing right if write to slog is better or not (thinking if we have a better throughput from disks). But i did not find anything about 100% slog activity (~115MB/s) blocks

Sure, I don't mind testing it out on there for you, but, where do I find the pre releases to try then? At least we know it's between 2.13 and 3.00. That narrows it a bit I would think. Mind you, if it jumps up a major revision number, I guess that means a lot of changes went in. On 8/2/05, syslinux-request at zytor.com <syslinux-request at zytor.com> wrote: > Send SYSLINUX

So, when you add a log device to a pool, it initiates a resilver. What is it actually doing, though? Isn''t the slog a copy of the in-memory intent log? Wouldn''t it just simply replicate the data that''s in the other log, checked against what''s in RAM? And presumably there isn''t that much data in the slog so there isn''t that much to check? Or

> -----Original Message----- > From: Gene Cumm [mailto:gene.cumm at gmail.com] > Sent: Wednesday, January 20, 2016 1:14 PM > To: Tal Lubko > Cc: H. Peter Anvin; For discussion of Syslinux and tftp-hpa > Subject: Re: [syslinux] Embedding com32 modules and ldlinux.sys into > one file > > On Wed, Jan 20, 2016 at 2:05 AM, H. Peter Anvin via Syslinux > <syslinux at

hello everybody, i just commited a pkgsrc for dovecot nightly cvs-snapshots to the pkgsrc-wip repository for NetBSD - this will hopefully go into base pkgsrc, soon. please see http://pkgsrc-wip.sourceforge.net/ on how to obtain pkgsrc-wip. ----- Forwarded message from Tom Hensel <tomhensel at users.sourceforge.net> ----- Date: Sun, 22 Feb 2004 11:18:52 -0800 From: Tom Hensel

On 11/18/2014 10:20 AM, Didier Spaier wrote: > > On 18/11/2014 18:55, H. Peter Anvin wrote: >> On 11/17/2014 12:55 AM, Didier Spaier wrote: >>> So one more question: why can one boot with a GRUB EFI bootloader >>> but not with the SYSLINUX bootloader, using the same kernel? >>> >>> More accurately, I know why: because of the aforementioned patch,

Hi, Tal, could you answer to 2 questions: - what is amount of ROM you're intending to use? (actually 8 MB SPI or parallel NOR flash chip can contain some minimalist Linux distribution) - which chip do you plan to flash to, motherboard BIOS or option ROM? Also, ROMOS comes without a license, so you'll have to contact the author for commercial usage. On other hand, ROMDSK is GPLed, and you

Hi all... I'm looking once again at the Syslinux roadmap. It seems to me that we're going to have a very hard time making Syslinux 4.00 be the full-featured everything-in-C release I had hoped for, or perhaps more specifically, that it is justifiable to sit on the current filesystems-in-C code waiting for the rest. That would probably mean productizing the transitional COM32R module

I tried the patch from hpa directly on branch firmware and I get a different (non-working) behavior. syslinux.efi is correctly downloaded and my tftp server receive requests for ldlinux.e64 and acknowledge options, but receive no response at all. Actually, what happen is that before any packet is actually sent (and Transmit is called), GetModeData return a StationPort = 0. Leading to received

Hi, Out of pure curiosity, I was wondering, what would happen if one tries to use a regular 7200RPM (or 10K) drive as slog or L2ARC (or both)? I know these are designed with SSDs in mind, and I know it''s possible to use anything you want as cache. So would ZFS benefit from it? Would it be the same? Would it slow down? I guess it would slow things down, because it would be trying to