Re: [9fans] how to access files out of acme-home in acme-sac
I see now. Thanks :-) On Sun, Mar 9, 2008 at 1:59 AM, hiro <[EMAIL PROTECTED]> wrote: > On 3/8/08, Hongzheng Wang <[EMAIL PROTECTED]> wrote: > > Thank you for your mail. But I still feel difficult to do this. > > Could you please give me an example? > > bind '#U*/homo' /n/local > > -- > hiro > -- HZ
Re: [9fans] how to access files out of acme-home in acme-sac
On 3/8/08, Hongzheng Wang <[EMAIL PROTECTED]> wrote: > Thank you for your mail. But I still feel difficult to do this. > Could you please give me an example? bind '#U*/homo' /n/local -- hiro
Re: [9fans] how to access files out of acme-home in acme-sac
Thank you for your mail. But I still feel difficult to do this. Could you please give me an example? On Sat, Mar 8, 2008 at 11:47 AM, Anant Narayanan <[EMAIL PROTECTED]> wrote: > > Hi, > > > I've just installed acme-sac in my debian box. After the first > > executing the program, a new directory ~/acme-home is created, which > > appears to be recognized as /usr/ in acme-sac. I searched > > the mailing list of acme-sac and found that such a setting exists for > > security. Then, how can I access other files out of acme-home > > directory? So that acme-sac could be used as a standalone editor on > > hosted OS. > > Your local filesystem should be mounted somewhere inside /n. > > -- > Anant > -- HZ
Re: [9fans] thoughs about venti+fossil
>> After this fact the colliding block is itself very interesting,
>> aand it is also very likely that theis block will be stored and
>> archived just for this reason.
>
> Which will increase the chance of a failure ;-O
by how much? the fact that something *could* happen is often
meaningless. what is
lim{x->∞} 1+1/x?
the εδ argument made to proove the result always says that
if i control the input of a function this much i can control the
output that much. in the real world there are limits (ha!)
to how small or large something can get before it is practically
infinite or zero. this is because, .e.g., there is no such thing as
1e24 bytes of storage.
theoretically, i don't think a collision by itself would be all that
interesting. the number of possible bit patterns in, say, 8k blocks
would be
2^(8*8192).
while the number of possible bit patterns in a sha1 hashs
2^(8*20).
assuming an even distribution, there would be
ceil(2^(8*8192)/2^(8*20) - 1) =
2^(8*8172) - 1
collisions on average per hash value. (that's ~1.37e4095, btw.)
the only way a collision would be interesting is if it exposed
a weakness in sha1.
- erik
Re: [9fans] thoughs about venti+fossil
as a purely intellectual problem — how could we recover from or perhaps avoid this remarkably unlikely event if our data stream just happened to trigger it — this is all very well. nevertheless, it still glosses over the hard fact that it really is the least of your worries if you are building a real system using it: data corruption is far more likely to occur in the networks, for instance, so if you really are building a system, you are wasting your time on this aspect (except to the extent you come to see the point).
Re: [9fans] thoughs about venti+fossil
perhaps a more sophisticated response would be to accept the fact that you don't know what you are doing and don't really want advice. we only mock you not because you have an idea that didn't pan out ... but because you won't shut up about "i don't know what i'm doing but i'll type another page of crap". we don't do that here. well the teenagers do. brucee On Sat, Mar 8, 2008 at 8:37 PM, Enrico Weigelt <[EMAIL PROTECTED]> wrote: > * Wilhelm B. Kloke <[EMAIL PROTECTED]> wrote: > > > After this fact the colliding block is itself very interesting, > > aand it is also very likely that theis block will be stored and > > archived just for this reason. > > Which will increase the chance of a failure ;-O > > > In practice though, a filesystem relying on venti could just > > change the block boundaries for this case or choose some other > > escape from needing to store these special blocks. > > hmm, let's assume, the scientists will come up with (maybe > artificially constructed) collissions long before they'll > happen in practice, we could handle them specially. All we > need to do is to leave enough room in the keyspace, so we > can assign them to these special blocks, once they've been > discovered. > > A simple way could simply be an additional bit, which tells > us that the key isn't the data's hash, but an explicitly > assigned dictionary entry. > > Maybe a more sophisticated approach: add an keytype prefix, > which allows dropping in several types of keys. Default might > be sha-1, but for special cases another keytype (eg. "dict") > can be used. > > > > cu > -- > - > Enrico Weigelt== metux IT service - http://www.metux.de/ > - > Please visit the OpenSource QM Taskforce: >http://wiki.metux.de/public/OpenSource_QM_Taskforce > Patches / Fixes for a lot dozens of packages in dozens of versions: >http://patches.metux.de/ > - >
Re: [9fans] thoughs about venti+fossil
* Wilhelm B. Kloke <[EMAIL PROTECTED]> wrote: > After this fact the colliding block is itself very interesting, > aand it is also very likely that theis block will be stored and > archived just for this reason. Which will increase the chance of a failure ;-O > In practice though, a filesystem relying on venti could just > change the block boundaries for this case or choose some other > escape from needing to store these special blocks. hmm, let's assume, the scientists will come up with (maybe artificially constructed) collissions long before they'll happen in practice, we could handle them specially. All we need to do is to leave enough room in the keyspace, so we can assign them to these special blocks, once they've been discovered. A simple way could simply be an additional bit, which tells us that the key isn't the data's hash, but an explicitly assigned dictionary entry. Maybe a more sophisticated approach: add an keytype prefix, which allows dropping in several types of keys. Default might be sha-1, but for special cases another keytype (eg. "dict") can be used. cu -- - Enrico Weigelt== metux IT service - http://www.metux.de/ - Please visit the OpenSource QM Taskforce: http://wiki.metux.de/public/OpenSource_QM_Taskforce Patches / Fixes for a lot dozens of packages in dozens of versions: http://patches.metux.de/ -
Re: [9fans] thoughs about venti+fossil
* Paul Lalonde <[EMAIL PROTECTED]> wrote: > Bruce Ellis wrote: > >If you stopped to pick up the penny you'd get hit by lightning and > >fail to cash in your lottery ticket while getting bitten by a moose! > > > > But thank god, there would be no collision. God doesn't exist. He vanished in a puff of logic ;-P > I hate getting hit by cars. Yeah, logic proofed that too much logic can be harmful ;-O cu -- - Enrico Weigelt== metux IT service - http://www.metux.de/ - Please visit the OpenSource QM Taskforce: http://wiki.metux.de/public/OpenSource_QM_Taskforce Patches / Fixes for a lot dozens of packages in dozens of versions: http://patches.metux.de/ -
