search for: mailthreads

Hello, I'am trying to efi-netboot a HP ProLiant DL120 Gen9[1], that has multiple NICs, one embedded 2-port and an extra 4-port, so I got to the HP/EFI/multinic problem. I read through the multinic mailthreads and using current master[2], it booted successfully to syslinux but then another problem manifested: Syslinux for some reason asks the gateway and not next-server about ldlinux.e64 (I got this through tcpdumping the gw) Our setup is the following: 10.1.10.1: gw 10.1.10.105: client-to-be-booted 19...

..., > > I'am trying to efi-netboot a HP ProLiant DL120 Gen9[1], that has > multiple NICs, one embedded 2-port and an extra 4-port, so I got to the > HP/EFI/multinic problem. HP DL120 G9 versus HP DL160 G9. Sounds like they'll be awfully similar. > I read through the multinic mailthreads and using current master[2], it > booted successfully to syslinux but then another problem manifested: > Syslinux for some reason asks the gateway and not next-server about > ldlinux.e64 (I got this through tcpdumping the gw) OH? This has me thinking. Please look closer. Is it targetti...

Hi, I already mentioned this on #vorbis, but thought it good to create a mailthread on it for easier tracking. One of the OpenBSD developers (claudio at openbsd.org) found that ogg123 crashes on his machine with a SIGSEGV while playing tracks with unknown comments in the tags. He's running with special malloc flags that make the OpenBSD malloc(3) extra picky (manpage available online at

Hello, I have to update the BIOS of several hundreds of geographically distributed PCs. Since we are using PXELINUX for years to install the OS (Linux) on this PCs PXELINUX is my first choice for doing this job. The vendor of this PCs provides a bootable ISO image for the update. Because of the size of the firmware it is not possible to use a FD image (not even 2.88MB). But in the documentation

Package: xen-utils-4.17 Version: 4.17.1+2-gb773c48e36-1 Severity: important Dear Maintainers, On one of our domUs we discovered that the network interface names were wrongly assigned since recreating the domU after an upgrade to bookworm. If over 10 network interfaces are configured the mapping (dom0) vifX.10 <-> eth10 (domU) does not apply anymore. Instead the interfaces on dom0 are

Hi, This set of patches contains the initial implementation of the IEEE 802.1Qbg standard: code for the exchange of EVB TLVs in LLDP frames to negotiate VSI capabalities as well as VDP VSI TLVs between a host with virtual machines and an adjacent switch. It supports setting the parameters of the TLV exchange from the command line using lldptool. VDP profiles consisting of

Hi, This set of patches contains the initial implementation of the IEEE 802.1Qbg standard: code for the exchange of EVB TLVs in LLDP frames to negotiate VSI capabalities as well as VDP VSI TLVs between a host with virtual machines and an adjacent switch. It supports setting the parameters of the TLV exchange from the command line using lldptool. VDP profiles consisting of