Date: Sun, 16 Feb 2014 23:47:07 -0500 From: Jason Hellenthal <jhellenthal@dataix.net> To: Perry Hutchison <perryh@pluto.rain.com> Cc: "freebsd-filesystems@freebsd.org" <freebsd-filesystems@freebsd.org>, "freebsd-hackers@freebsd.org" <freebsd-hackers@freebsd.org>, "jordan.hubbard@gmail.com" <jordan.hubbard@gmail.com> Subject: Re: Thoughts on Multi-Symlink Concept Message-ID: <1D850D2F-4E1F-4958-8EC9-1774A1793C60@dataix.net> In-Reply-To: <530049a1.XXZ1PjZFgRyCu9X6%perryh@pluto.rain.com> References: <CAO2cuEMC==HstC4VkkiFpHyo6LA_xyCjYKvCEECXneVLNnZpZg@mail.gmail.com> <A31B3F88-861F-459B-AD67-F146D5514594@mail.turbofuzz.com> <530049a1.XXZ1PjZFgRyCu9X6%perryh@pluto.rain.com>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --]
That is a rather lovely example. Going a bit beyond my initial thoughts. . . . this could be really handy if done correctly. For ports, source, object tree's . . . obviously bin directories and even lib directories. Call it the poor-mans replication system but with some pretty big benifits.
My initial thoughts were to just point directly to files, excluding using globing as a way to just include files in a massive config sort of fashion but if globing comes into play that would be awesome.
--
Jason Hellenthal
Voice: 95.30.17.6/616
JJH48-ARIN
> On Feb 16, 2014, at 0:16, perryh@pluto.rain.com (Perry Hutchison) wrote:
>
> Jordan Hubbard <jordan.hubbard@gmail.com> wrote:
>
>> Even variant symlinks (/bin -> /${ARCH}/bin), which can expand
>> differently depending on the user context, have clearly
>> understandable semantics - you know that the symlink is going
>> to expand to exactly one file no matter what ARCH is set to.
>
> s/file/pathname/
>
> Depending on what ARCH is set to, the expanision may or may not
> point to any actual file (or directory, or ...)
[-- Attachment #2 --]
0 *H
010 + 0 *H
90000
*H
010 UIL10U
StartCom Ltd.1+0)U"Secure Digital Certificate Signing1806U/StartCom Class 1 Primary Intermediate Client CA0
130518085048Z
140519220947Z0H10Ujhellenthal@dataix.net1%0# *H
jhellenthal@dataix.net0"0
*H
0
'`TmfkܨJ5u+c'Upb`zv)&ȸXZ*VN6JvLoVoh}g
pQDŽKf/tZA˳("4Ԅ˻'d2h|IBl'^v^;'e8S99ۿVm|k8_UQtC"5l!kjZ]އQGn\Bh!FTsD%pV^Eӑd¨x"9
г"f 00 U0 0U0U%0++0UڔfmVʢ$䟓0U#0Sr풜\|~5NԸQ0!U0jhellenthal@dataix.net0LU C0?0;+70*0.+"http://www.startssl.com/policy.pdf0+00' StartCom Certification Authority0This certificate was issued according to the Class 1 Validation requirements of the StartCom CA policy, reliance only for the intended purpose in compliance of the relying party obligations.06U/0-0+)'%http://crl.startssl.com/crtu1-crl.crl0+009+0-http://ocsp.startssl.com/sub/class1/client/ca0B+06http://aia.startssl.com/certs/sub.class1.client.ca.crt0#U0http://www.startssl.com/0
*H
{0Ӹ,52W{Ey8b[{7 _+P"n["-,@ŽpJ-W$ݍjWA-6z( RdIZ.KzXє[K6}{s+v.Qh0PͅKhTw 0I73lz*Kv4Kkگ63;p1:ױ@)]ok>:W%XwC1þL/o8~#oP0400
*H
0}10 UIL10U
StartCom Ltd.1+0)U"Secure Digital Certificate Signing1)0'U StartCom Certification Authority0
071024210155Z
171024210155Z010 UIL10U
StartCom Ltd.1+0)U"Secure Digital Certificate Signing1806U/StartCom Class 1 Primary Intermediate Client CA0"0
*H
0
-).2AUGo#G
B|NDRpM-B=o-we5JQpa>O.#._<V
[~**pz~3WG .ᘟMlr[<Ce6fqO"uxfWN#uicgkv$Lb%y`_{`xK'GN 00U00U0USr풜\|~5NԸQ0U#0N@[i04hCA0f+Z0X0'+0http://ocsp.startssl.com/ca0-+0!http://www.startssl.com/sfsca.crt0[UT0R0'%#!http://www.startssl.com/sfsca.crl0'%#!http://crl.startssl.com/sfsca.crl0U y0w0u+70f0.+"http://www.startssl.com/policy.pdf04+(http://www.startssl.com/intermediate.pdf0
*H
}x,\c^#wMq}>UK/^yX֏y frMIŲB61ymQҨݬZ0&