FW: [patch 01/02] vfs: variant symlinks
On 9/28/07 11:22 AM, "Jan Dittmer" <[EMAIL PROTECTED]> wrote: > Ken Schmidt wrote: >> Variant symlinks add the ability to embed variables in to the >> contents of symbolic links so their targets can change based on >> outside sources (user environment, uts, filesystems, etc.) > > Could you elaborate why this is needed and what part cannot > be solved in userspace (linkfarm on tmpfs or intelligent > scripts)? Several networked filesystems (i.e. afs) have similar concepts. This just moves it into the vfs layer so that it can be used on all of them and even local filesystems. The best example of how this can be useful is to allow a heterogeneous environment which uses a common filesystem. For example, both x86_64 and power systems could mount a root nfs share and execute with a common set of configurations and data, but the binary directories (bin and lib) could point to architecture specific directories. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
FW: [patch 01/02] vfs: variant symlinks
On 9/28/07 11:22 AM, Jan Dittmer [EMAIL PROTECTED] wrote: Ken Schmidt wrote: Variant symlinks add the ability to embed variables in to the contents of symbolic links so their targets can change based on outside sources (user environment, uts, filesystems, etc.) Could you elaborate why this is needed and what part cannot be solved in userspace (linkfarm on tmpfs or intelligent scripts)? Several networked filesystems (i.e. afs) have similar concepts. This just moves it into the vfs layer so that it can be used on all of them and even local filesystems. The best example of how this can be useful is to allow a heterogeneous environment which uses a common filesystem. For example, both x86_64 and power systems could mount a root nfs share and execute with a common set of configurations and data, but the binary directories (bin and lib) could point to architecture specific directories. - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
