Given the size limits on vid/pid I don't think shell style wildcards would consume any more space. RE probably would and would certainly require significant text segment space.
The present implementation does a substring match but only if both the first and last character of the string in sd.conf are * which is very counter to expectations. Reg -------------------------------------------- On Sun, 3/30/14, Andrew Gabriel <[email protected]> wrote: Subject: Re: [OpenIndiana-discuss] sd-config-list= vid/pid string syntax in sd.conf To: [email protected] Date: Sunday, March 30, 2014, 11:55 AM On 29/03/2014 21:15, Reginald Beardsley wrote: > The string matching logic in sd_sdconf_id_match() in sd.c is odd and seems to cause a good bit of confusion. In particular it does not conform to shell wildcard rules which I think is what most people would expect. > > Can anyone point to why the current syntax and semantics were chosen? > > Does anyone know a reason why it should not conform to shell wildcard rules? The alternative is full regular expressions, but that seems a bit overkill and possibly confusing as well. Usually done to limit the potential stack usage in the kernel, which is a much more limited resource than in user space where RE and shell matching are found. -- Andrew _______________________________________________ OpenIndiana-discuss mailing list [email protected] http://openindiana.org/mailman/listinfo/openindiana-discuss _______________________________________________ OpenIndiana-discuss mailing list [email protected] http://openindiana.org/mailman/listinfo/openindiana-discuss
