search for: bleazard

...ieve_before, can I have it "include :personal"? If so, what's going to happen with the script compilation? From what I understand, it can't be compiled globally, since each user has a different custom rule set. Am I trying to do the impossible here? Thanks for any ideas, Jason Bleazard

...ncluded in the final list. I agree that the local domain could be merged into the DomanSearch list. To maintain compatibility with the current semantics it would be at the end of the list. I searched the code for other usages of LocalDomain but didn't find any. Thanks for the feedback Steve Bleazard On 7 January 2016 at 18:19, Celelibi <celelibi at gmail.com> wrote: > 2016-01-07 11:25 UTC+01:00, Stephen Bleazard via Syslinux <syslinux at zytor.com>: >> Currently it appears that when PXE booting the domain search option is >> ignored >> and only the domain nam...

...earch option (119) - When resolving names via dns_resolv uses the search path if there's no dot in the name. - Reverts to the previous behaviour in the absence of a search path, if the name contains a dot or if no addresses are found when searching the domain search path. Steve Bleazard -- diff -upr syslinux-6.03.orig/core/fs/pxe/dhcp_option.c syslinux-6.03/core/fs/pxe/dhcp_option.c --- syslinux-6.03.orig/core/fs/pxe/dhcp_option.c 2014-10-06 17:27:44.000000000 +0100 +++ syslinux-6.03/core/fs/pxe/dhcp_option.c 2016-01-04 07:58:18.158206039 +0000 @@ -7,6 +7,11 @@ #include "px...

2016-01-07 11:25 UTC+01:00, Stephen Bleazard via Syslinux <syslinux at zytor.com>: > Currently it appears that when PXE booting the domain search option is > ignored > and only the domain name option used for name resolution. > > The following patch adds support for domain search path usage when PXE > booting: > -...