search for: alfh

...d/vmlinuz" or "tftp://<my-server>/shared/vmlinuz" in your > configs instead of "../shared/vmlinuz" (which is prone to issues). Because pxelinux.0, bootia32.efi and bootx64.efi are different names, so I can put them in the same path, no problem for this, i.e. $ ls -alFh /tftpboot/nbi_img/{*.0,*.efi} -rw-r--r-- 1 root root 157K Apr 22 15:30 /tftpboot/nbi_img/bootia32.efi -rw-r--r-- 1 root root 160K Apr 22 15:30 /tftpboot/nbi_img/bootx64.efi -rw-r--r-- 1 root root 105K Apr 22 15:30 /tftpboot/nbi_img/gpxelinux.0 -rw-r--r-- 1 root root 74K Apr 22 15:30 /tftpboot/nbi_...

...quot;tftp://<my-server>/shared/vmlinuz" in your > > configs instead of "../shared/vmlinuz" (which is prone to issues). > Because pxelinux.0, bootia32.efi and bootx64.efi are different names, so > I can put them in the same path, no problem for this, i.e. > $ ls -alFh /tftpboot/nbi_img/{*.0,*.efi} > -rw-r--r-- 1 root root 157K Apr 22 15:30 /tftpboot/nbi_img/bootia32.efi > -rw-r--r-- 1 root root 160K Apr 22 15:30 /tftpboot/nbi_img/bootx64.efi > -rw-r--r-- 1 root root 105K Apr 22 15:30 /tftpboot/nbi_img/gpxelinux.0 > -rw-r--r-- 1 root root 74K Apr 22...

Dear Syslinux developers, I'd like to continue the discussion about this: http://www.syslinux.org/archives/2014-February/021659.html i.e. different directories for *.c32 files of BIOS, EFI32, and EFI64. I am wondering why we can not have *.c32 for the COMBOOT files of BIOS, *.e32 for the COMBOOT files of EFI32 *.e64 for the COMBOOT files of EFI64 As now the ldlinux file of syslinux 6.0x has,

On 2014?03?07? 23:05, Ady wrote: > I understand that these remarks might seem not the main issue, but I > tend to think that once you are successful while using only "default" > > values and in a minimalistic case, you could add complexity > (different paths, multiple firmwares, additional kernels, multiple > cfg files...). Ady, Thanks. I will follow your advice to

...=== My /etc/default/atftpd is: ==================== USE_INETD=false OPTIONS="--tftpd-timeout 300 --retry-timeout 5 --mcast-port 1758 --mcast-addr 239.255.0.0-255 --mcast-ttl 1 --maxthread 100 --verbose=5 --port 69 /tftpboot/nbi_img/" ==================== Files are in the correct path: ls -alFh /tftpboot/nbi_img/{*.efi,*e64} -rw-r--r-- 1 root root 179K Mar 7 21:41 /tftpboot/nbi_img/bootx64.efi -rw-r--r-- 1 root root 137K Mar 7 21:41 /tftpboot/nbi_img/ldlinux.e64 and they were extracted from prebuilt binary 6.03-pre7 tarball on kernel.org: sha1sum /tftpboot/nbi_img/{*.efi,*e64} d0ca7d52...

...che dovecot: Jan 22 10:10:55 Error: dict: Failed to initialize dictionary 'expire' dovecot: Jan 22 10:10:55 Error: IMAP(xxxxxxxxxx): read(/var/dovecot/dict-server) failed: Remote disconnected Anyone know how to fix this? I do not want to use SQL as backend, that would be overkill. # ls -alFh /var/dovecot/dict-server srwxrwxrwx 1 root wheel - 0B Jan 22 10:08 /var/dovecot/dict-server= # dovecot -n # 1.1.8: /etc/dovecot.conf # OS: OpenBSD 4.4 sparc64 ffs base_dir: /var/dovecot/ log_path: /var/log/dovecot.log protocols: imaps pop3s listen: xxxxxxxxxxxx ssl_ca_file: /etc/ssl/xxxxxx...