search for: ppokorni

I see that there seems to be patches being accepted... Please consider committing these two: You should be able to cherry pick them from my syslinux repo at http://github.com/ppokorny/syslinux I would think? commit 64fb71b87a625d70ea8c6127f18fe96d3f4fdc89 Author: Philip Pokorny <ppokorny at penguincomputing.com> Date: Sun Mar 5 21:07:48 2017 -0800 Fix PATH parsing to match the

Phil, I gave a presentation last month on how to set up a DHCP + TFTP server. Using syslinux 6.03-pre* to support both Legacy and EFI PXE boot. Here's the link to the presentation. My slides are there. http://2014.texaslinuxfest.org/content/creating-legacy-efi-pxe-server-using-pxelinux The presentation models a small lab-sized env. I start simple; supporting legacy PXE boot only. Then

I am trying to use rsync (3.0.6) to keep two directories as exact duplicates. I would normally run: rsync -av -S --delete /path/to/src/ /path/to/dst/ to do this. Unfortunately, the directories have become rather large (2TB, a million files) and so the tree walk has become a prohibitively time consuming part of the operation. However, I have a way to generate a list of file changes

I've been trying to get syslinux.efi working in my environment again... Found what look like a bunch of little bugs that are very frustrating... First, the documentation on the Wiki says that as of 5.11, the list separator is space, not colon. But I can find no evidence that 5.11 was ever officially released or that a commit to git was made to make this change. 6.00 and following still use

Hello, I'm looking for and offering help. I know this has been an on-going problem and I thought I had seen a fix go by, but I'm compiling from the latest github.com/geneC/syslinux and syslinux.cz repositories and I've got a system which doesn't work. It does DHCP and gets a filename "efi/syslinux.efi" and downloads that correctly. It then executes it which clears the

> > Date: Mon, 8 Aug 2016 15:05:17 +1000 > From: Michael Davies <nemykal at nrv-linux.io> > To: syslinux at zytor.com > Subject: [syslinux] Syslinux Aarch64 porting > Message-ID: <05476825-bf5e-9898-4aaa-3eaa927bbd0c at nrv-linux.io> > Content-Type: text/plain; charset=utf-8; format=flowed > > Hi, > > Is there any information available on porting

> > I need to create one bootable UEFI disk partition that contains all the > space on the disk. The steps must work in a shell script. Ideally with > syslinux/extlinux but if not possible then grub. > > > > echo format file system > sudo mkfs.ext4 -F /dev/${DISK_DEVICE_NAME_CURRENT_OS}1 > EFI requires a FAT filesystem. Ideally FAT32 but that might be encumbered

> Attached is a patch for the latest tftp-hpa. > This patch add support for named pipes. > > Named pipes are 0 byte files which can be read by a PXE boot process. > They provide the necessary informations for the boot process and are > deleted afterwards. > This PXE boot is a single event and won't interact until another named > pipe is created for the client.

Sounds like we should change the "and cx" mask to 5 so that if either EHDD support or LBA is announced by the bios, the correct EHDD path will be taken. Phil P. -- Philip Pokorny, RHCE Chief Technology Officer PENGUIN COMPUTING, Inc www.penguincomputing.com Changing the world through technical innovation

Hello, I see lots of current activity trying to get EFI PXE working both with new and "old" kernels (RHEL 6.5) and lots of failures. I've got several real pieces of hardware (AMD APU, Intel E5-2600, etc.) with a variety of BIOS and NIC that have EFI PXE stacks to test with. But I find zero documentation that's up to date on the wiki of how to configure a DHCP server to send

This document: http://www.iana.org/assignments/dhcpv6-parameters/dhcpv6-parameters.xml Has the same (plus expanded) list of cpu arch values for parameter 0x93. This list matches RFC 4578 except for values 7 and 9 which are EFI ByteCode and x86-64. Turns out RFC 4578 is wrong https://www.rfc-editor.org/errata_search.php?rfc=4578 And 00:07 *is* the correct value for 64-bit x86 clients and the

> > Here is a bit of an odd request... II'm in a large company with lots of > politics getting in the way of things. We were able to convince the main IT > team to let us take over a subnet and run our own DHCP server. This lets us > create a really nice PXE environment where we can build servers and ship > them out. However, now we are in need to rebuild servers already

I asked before about config_cwd and after some more digging, it looks like it could be removed... Specifically, the documentation http://www.syslinux.org/wiki/index.php?title=Config#CONFIG says: ---------- * CONFIG config_file [new_WD] Load a new configuration file. The new configuration file is read, the Working Directory is optionally changed (if specified via an optional second parameter),