Date: Mon, 25 Mar 2013 22:44:11 +0200 From: Andriy Gapon <avg@FreeBSD.org> To: FreeBSD Current <freebsd-current@FreeBSD.org>, freebsd-hackers@FreeBSD.org Subject: Fwd: kern/122838: [devfs] devfs doesn't handle complex paths (like zvol/pool/vms) good Message-ID: <5150B71B.6060106@FreeBSD.org> In-Reply-To: <5150B598.7050700@FreeBSD.org> References: <5150B598.7050700@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Would like to ask for opinions on this topic... Please read this PR for context: http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/122838 Especially Jaakko's insightful description of the problem. -------- Original Message -------- Message-ID: <5150B598.7050700@FreeBSD.org> Date: Mon, 25 Mar 2013 22:37:44 +0200 From: Andriy Gapon <avg@FreeBSD.org> Subject: Re: kern/122838: [devfs] devfs doesn't handle complex paths (like zvol/pool/vms) good Can't believe that we are still where we were more than two years ago... I think that we have to make this change even if it _might_ break some existing rulesets. Rationale: - current behavior is contrary to any documentation - current behavior is contrary to common sense - current behavior is very hard to describe and account for - I presume that very few people actually fully understand the current behavior - I presume that even fewer people made a conscious choice to depend or make use of its non-trivial features of the current behavior So, we should make the behavior of devfs pattern consistent with the documentation and the common sense. In addition to Jaakko's patch I propose that we pass FNM_PATHNAME to fnmatch(9), so that the matching is indeed consistent with glob(3) / shell glob-ing rules for filesystem paths. -- Andriy Gapon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5150B71B.6060106>