bluesky AT lists.ibiblio.org
Subject: Global-Scale Distributed Storage Systems
List archive
- From: Richard Clayton <richard AT highwayman.com>
- To: Global-Scale Distributed Storage Systems <bluesky AT franklin.oit.unc.edu>
- Subject: Re: a global fs
- Date: Fri, 10 Aug 2001 12:11:05 +0100
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
In message <>, Josh <josh AT mercuryfs.net> writes
>In an attempt to jumpstart this dead email list, I put forth the following
>statement:
>
>The essence of a global file system is a globally unique file identifier
>(file handle),
not always ... I can say "I'd like a copy of the PGP source please"
then, when a system (or a friend with email) delivers me a copy then I
will check that what I have received is acceptable by checking a
signature on the source. If I trust the signature then I will accept the
source as being valid. There may be many files with such a signature on,
and I may be happy to accept any of them.
>and a globally unique user identification/authentication
>method.
I can see no obvious requirement for this in a simple file system.
Many people think they want this for other reasons (political control or
money collection), but it doesn't have much to do with file handling.
>Nail those 2, and the rest is easy.
there's no evidence for this
>I'm not interested in anything other than technical responses.
the list is run for other reasons than just your benefit. Wait and see
whether a fruitful discussion comes along rather than just stirring.
- --
richard @ highwayman . com "Nothing seems the same
Still you never see the change from day to day
And no-one notices the customs slip away"
-----BEGIN PGP SIGNATURE-----
Version: PGPsdk version 1.7.1
iQA/AwUBO3PBSRfnRQV/feRLEQKN0ACfasvsbpU2NbePXFIu0Ym50BDD3Z4AoN/1
rZub7k02t0XpdU0adG397/b7
=OUIX
-----END PGP SIGNATURE-----
-
a global fs,
Josh, 08/10/2001
- <Possible follow-up(s)>
- Re: a global fs, Richard Clayton, 08/10/2001
- Re: a global fs, Brandon Wiley, 08/10/2001
- RE: a global fs, Josh, 08/10/2001
Archive powered by MHonArc 2.6.24.