Date: Tue, 7 Jul 1998 17:54:20 -0500 (CDT) From: peter@taronga.com (Peter da Silva) To: tlambert@primenet.com (Terry Lambert) Cc: peter@taronga.com, tlambert@primenet.com, hackers@FreeBSD.ORG Subject: Re: A really hoopy idea for variant symlinks. Message-ID: <199807072254.RAA24074@bonkers.taronga.com> In-Reply-To: <199807072050.NAA01036@usr04.primenet.com> from "Terry Lambert" at Jul 7, 98 08:50:07 pm
next in thread | previous in thread | raw e-mail | index | archive | help
> > > The enforcement depends on the procfs (kernel code) parsing and enforcing > > > against "absurd" values. > > Like the file system does already? It's just namei! > Multiple "//" within a path are treated as "/", unless it's the > first two characters in the path, in which case it's implementation > defined what it does. > That covers the full gamut on what is or isn't allowable semantically > in a path component. OK, which means that /proc/curproc/syms/osversion is allowed in a path. That was the point of my proposal, to avoid polluting the namespace by using part of it. > You would need name/value pair reduction; specifically, you would need > to seperate the token before and after the (initial) '=' token when > traversing the list of environment "name/value pair, '=' token seperator" > strings. You must be talking about someone else's hoopy idea. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199807072254.RAA24074>