Use ftp://80.133.138.104:12121
sorry, but I get 'no route to host' every time.
80.133.138.104 is owned by the 'Deutsche Telekom AG'
(An ISP in Germany).
Looks like a dynamic IP, currently not in use - No route
-- Adrian
On Friday 11 February 2005 08:54, you wrote:
Hello
On Fri, 2005-02-11 at 10:38, Christian Placzek wrote:
On Thursday 10 February 2005 16:25, you wrote:
On Thursday 10 February 2005 18:02, Christian Placzek wrote:
what if you zero the first 64K with
dd conv=notrunc if=/dev/zero
Hi
I have an application where I want to make relatively frequent copies of
a large file, and the copies will remain largely similar to the original.
It seems to me that a file-level copy-on-write would support this well.
So, does reiserfs support anything like this?
If not, can I implement this
after rebuilding the tree, does 'reiserfsck --check device' see these
files?
Yes, see my original email from 08.02.2005 23:21. The original output has a
length of about 13000 lines. A extract looks like this:
...
rebuild_semantic_pass: The entry [741258 1025777] (www.firstname.de.ico)
Hello
On Fri, 2005-02-11 at 11:18, Roland Paterson-Jones wrote:
Hi
I have an application where I want to make relatively frequent copies of
a large file, and the copies will remain largely similar to the original.
It seems to me that a file-level copy-on-write would support this well.
Anyone ever given a though to adding support to reiserfs to store a
cryptographic checksum along with a file?
The idea is that files get a hidden attribute that contains their SHA1 hash.
If the file is modified, the hash is marked as 'unclean'. A trusted
cleaner comes by eventually and hashes
I think this is a great idea. Solaris ZFS is supposed to have a similar
feature, but reiser4 metas would allow application-level access.
The purpose of checksumming in ZFS is more like Gregory's 2nd point,
except Solaris takes it one step further. If you have RAID, ZFS will fix
the corruption
On Fri, Feb 11, 2005 at 01:58:59PM -0500, Gregory Maxwell wrote:
1. Lots of applications today (such a P2P sharing systems) need the
hashes of files.. it's inefficient to keep recomputing them. The file
system always knows when a file changes, so it can be setup to always
return the correct
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Vladimir Saveliev wrote:
[...]
|If not, can I implement this easily (how easily ;) ) with a plugin.
|
|
| I guess you mean plugin for reiser4?
| You probably can but I do not think that it would be easy.
But, AFAIK it's in the long-term plans, as it's
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
First, let me second the original idea. So long as the hash isn't
updated until that attribute is read, it should be fine.
Tom Vier wrote:
| On Fri, Feb 11, 2005 at 01:58:59PM -0500, Gregory Maxwell wrote:
|
|1. Lots of applications today (such a P2P
10 matches
Mail list logo
