similar to: blksize option in tftp client?

Displaying 20 results from an estimated 8000 matches similar to: "blksize option in tftp client?"

2018 Dec 12
3
PXE boot img for both BIOS and EFI
On Wed, 2018-12-12 at 17:10 -0600, Carl Karsten 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. > > > On Wed, Dec 12, 2018 at 4:54 PM Joakim Tjernlund > <Joakim.Tjernlund at infinera.com> wrote: > > > While I am here, I want to ask: >
2018 Dec 12
4
efi config hang
On Wed, 2018-12-12 at 16:00 -0600, Carl Karsten 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. > > > On Tue, Dec 11, 2018 at 9:19 PM Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > > > > > You should be able to
2019 Feb 06
4
syslinux-6.04-pre2
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. > > > > > > Hi all, > > > > It has been the case for
2017 Dec 14
1
core_udp_sendto: no mapping
On Wed, 2017-12-13 at 10:34 -0500, Gene Cumm 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. > > > On Wed, Dec 13, 2017 at 7:03 AM, Joakim Tjernlund > <Joakim.Tjernlund at infinera.com> wrote: > > On Mon, 2017-12-11 at 08:59 +0100, Joakim
2017 Nov 28
2
core_udp_sendto: no mapping
On Tue, 2017-11-28 at 12:25 +0100, Julien Viard de Galbert 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, Le 28 nov. 2017 ? 00:39, Joakim Tjernlund via Syslinux <syslinux at zytor.com<mailto:syslinux at zytor.com>> a ?crit : On Mon, 2017-11-27 at 18:18
2019 Feb 06
4
syslinux-6.04-pre2
On Wed, 2019-02-06 at 11:34 -0800, H. Peter Anvin 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 not click links or open attachments
2019 Feb 07
2
syslinux-6.04-pre2
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
2017 Nov 27
3
core_udp_sendto: no mapping
On Mon, 2017-11-27 at 18:18 -0500, Gene Cumm wrote: > > On Mon, Nov 27, 2017 at 6:07 PM, Joakim Tjernlund > <Joakim.Tjernlund at infinera.com> wrote: > > On Mon, 2017-11-27 at 18:03 -0500, Gene Cumm wrote: > > > On Mon, Nov 27, 2017 at 2:14 PM, Gene Cumm <gene.cumm at gmail.com> wrote: > > > > On Mon, Nov 27, 2017 at 12:07 PM, Joakim Tjernlund >
2001 Mar 13
3
2 samba server in same computer?
Hi I am trying to find a way to run 2 samba PDC servers on the same computer. One samba server is the one in production and the other will be used for testing. So far I have not found a way to do this, is it possible at all? I only have one network card. Jocke
2018 Dec 18
2
PXE boot img for both BIOS and EFI
On Tue, 2018-12-18 at 14:10 -0500, Gene Cumm wrote: > On Wed, Dec 12, 2018 at 6:30 PM Joakim Tjernlund via Syslinux > <syslinux at zytor.com> wrote: > > On Wed, 2018-12-12 at 17:10 -0600, Carl Karsten 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
2019 Feb 06
2
syslinux-6.04-pre2
On Wed, 2019-02-06 at 11:56 -0800, H. Peter Anvin 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. > > > On 2/6/19 11:44 AM, Joakim Tjernlund wrote: > > On Wed, 2019-02-06 at 11:34 -0800, H. Peter Anvin wrote: > > > > Great, that tree now
2017 Nov 27
3
core_udp_sendto: no mapping
On Mon, 2017-11-27 at 18:03 -0500, Gene Cumm 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. > > > On Mon, Nov 27, 2017 at 2:14 PM, Gene Cumm <gene.cumm at gmail.com> wrote: > > On Mon, Nov 27, 2017 at 12:07 PM, Joakim Tjernlund > >
2017 Nov 28
2
core_udp_sendto: no mapping
On Mon, 2017-11-27 at 18:18 -0500, Gene Cumm 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. > > > On Mon, Nov 27, 2017 at 6:07 PM, Joakim Tjernlund > <Joakim.Tjernlund at infinera.com> wrote: > > On Mon, 2017-11-27 at 18:03 -0500, Gene Cumm
2018 Dec 18
1
efi config hang
On Mon, 2018-12-17 at 23:52 +0100, Lukas Schwaighofer 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. > > > Hi Joakim, > > On Wed, 12 Dec 2018 23:25:24 +0000 > Joakim Tjernlund via Syslinux <syslinux at zytor.com> wrote: > > > I
2017 Dec 06
4
core_udp_sendto: no mapping
On Wed, Nov 29, 2017 at 6:30 AM, Gene Cumm <gene.cumm at gmail.com> wrote: > On Tue, Nov 28, 2017 at 2:38 PM, Joakim Tjernlund > <Joakim.Tjernlund at infinera.com> wrote: >> On Mon, 2017-11-27 at 18:18 -0500, Gene Cumm wrote: > >>> On Mon, Nov 27, 2017 at 6:07 PM, Joakim Tjernlund >>> <Joakim.Tjernlund at infinera.com> wrote: >>> > On
2018 Dec 12
2
efi config hang
On Wed, 2018-12-12 at 17:05 -0600, Carl Karsten wrote: > On Wed, Dec 12, 2018 at 4:54 PM Joakim Tjernlund > <Joakim.Tjernlund at infinera.com> wrote: > > On Wed, 2018-12-12 at 16:00 -0600, Carl Karsten 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
2018 Oct 18
2
Is syslinux still worked on? No new commits in git for about one year
On Thu, 2018-10-18 at 12:14 +0200, Didier Spaier 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. > > > On 10/17/18 8:54 PM, KARBOWSKI Piotr via Syslinux wrote: > > Is syslinux still under active development? I do not see any new commit in
2008 Feb 08
2
pxelinux, pxe requesting bad filename from tftp
Hey, I have a problem booting certain machines with pxelinux. I have pxelinux.0 in the root of my tftp server and dhcp pointing to the right location: # dhcpd.conf authoritative; option domain-name "example.net"; ddns-update-style none; default-lease-time 3600; max-lease-time 86400; subnet 10.0.0.0 netmask 255.255.255.0 { range 10.0.0.3 10.0.0.20; server-name
2007 Mar 08
2
pxelinux never OACKs tftp server response
After the PXE PROM code downloads and runs the pxelinux.0 image and it tries to download config information the client stops acknowledging the server OACK packets from the server. pxelinux from syslinux 3.11 from Fedora RPM, accessing Solaris 10 in.tftpd The tftp client in pxelinux.0 sends a tftp file read request with extended options tsize \00 0 \00 blksize \00 1440 \00 and then the server
2002 Feb 04
3
Allwell doesn't respond to OACK with ACK in TFTP
I'm trying to network-boot a GCT Allwell set-top box without success. My frustration level is high. The problem seems to be that the Allwell is sending a RRQ with an option. tftp-hpa responds with an OACK, and waits for the corresponding ACK from the Allwell. The Allwell never sends that ACK, but instead continues with the same RRQ until timeout. Having read RFC1782, this makes me think