On Sat, 2007-09-29 at 12:40 -0700, Schmidt, Kenneth P wrote:
> 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
>
On Sat, Sep 29, 2007 at 12:40:23PM -0700, Schmidt, Kenneth P wrote:
> 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
>
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
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
On Sat, Sep 29, 2007 at 12:40:23PM -0700, Schmidt, Kenneth P wrote:
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
On Sat, 2007-09-29 at 12:40 -0700, Schmidt, Kenneth P wrote:
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
On Fri, Sep 28, 2007 at 10:16:01AM -0700, 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.)
NAK - it's too ugly to live.
-
To
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
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.)
Signed-off-by: Ken Schmidt <[EMAIL PROTECTED]>
---
diff -urN linux-2.6.22.5.orig/include/linux/variant.h
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
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.)
Signed-off-by: Ken Schmidt [EMAIL PROTECTED]
---
diff -urN linux-2.6.22.5.orig/include/linux/variant.h
On Fri, Sep 28, 2007 at 10:16:01AM -0700, 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.)
NAK - it's too ugly to live.
-
To unsubscribe
12 matches
Mail list logo
