Lethalman

8 ms·

31.
by Lethalman 12y ago
repost https://news.ycombinator.com/item?id=9207999
32.
by Lethalman 12y ago
This is a nice algorithm and I thought about writing something that only depended on numbers and not on allocating nodes in a ring. It works well when adding nodes, but then how does it work when removing a node in the middle? When allocati
33.
NixOS, Consul, Nginx and containers(lethalman.blogspot.com)
3 points by Lethalman 12y ago|0 comments
34.
by Lethalman 12y ago
When there was no React.js, I had in mind something like that and implemented a very simple concept like this with ghcjs. Functional languages tend to let you write this kind of code. It felt very organized and just worked, then I looked at
35.
by Lethalman 12y ago
It's already like this, there's no initial sync.
36.
by Lethalman 12y ago
No I've just read about it on HN today. It's interesting. I guess for millions of files you finish inodes quickly if you don't cut the history periodically. But it's a good idea.
37.
by Lethalman 12y ago
You mean only one way from N machines to a single machine? Yes. When other machines add/change any file it will be uploaded to that single machine.
38.
by Lethalman 12y ago
Vagrant could run inotify+rsync periodically from both ends. It works for few files. SFS is when doing an rsync of a whole tree is not an option, in case of a big number of files.
39.
by Lethalman 12y ago
That's true. I've tried ceph, swift and riakcs. Our requirements were two servers, the storage is several terabytes, and losing data because of an unknown bug in the filesystem wasn't an option. Such filesystems are quorum-ba
40.
by Lethalman 12y ago
Glusterfs is for synchronous replication. Glusterfs asynchronous replication, at the time of writing SFS, only supported master-slave.
41.
by Lethalman 12y ago
Good, thanks for clarifying.
42.
by Lethalman 12y ago
lsyncd uses inotify. Also, it does rsync (or other backends) of the whole tree instead of single files AFAIK, but that's of course not a stopper as it would need few changes to implement. In addition, I don't think lsyncd has been
43.
by Lethalman 12y ago
Yes, we've thought a lot about using inotify, our first prototype was also using inotify. - Our system needs to cope with millions of directories. Millions of directories for inotify mean a lot of structures in the kernel. For large nu
44.
by Lethalman 12y ago
I'm an employee at Immobiliare.it and yesterday we've released for the first time some internal software to the public on github. Just wanting to share our work :)
45.
Asynchronous filesystem replication with FUSE and rsync(github.com)
76 points by Lethalman 12y ago|43 comments
46.
by Lethalman 12y ago
To my understanding, Ubuntu Core is much similar to the idea of Lennart: http://0pointer.net/blog/revisiting-how-we-put-together-linu... I don't feel saying them as either bad or good compared to Nix. Until you tr
47.
by Lethalman 12y ago
USE flags are just different inputs to the functions that build stuff in nix, which is most probably even more flexible in nix. Nix is mixed binary and source compilation when there's no cache.
48.
by Lethalman 12y ago
For using with nix-env, there's still -I, or -f. E.g. nix-env -f ~/nixpkgs -iA thepackage.
49.
by Lethalman 12y ago
Yes, in general you can't say "what version of X am I using?". You have to ask: "what version of X, the derivation Y is using?". You can see the contents of package X on your system, there's no index provided o
50.
by Lethalman 12y ago
Hi. I'd like to run NixOS on kimsufi as well. Do the servers work well? Is the cpu what they say on the page? Do they provide kvm?