Every single part of this is wrong. - You generally don't want the configuration in a venti.conf file. You want it inside of one of the venti partitions, which have space reserved for it. The venti/conf tool is good for this. - venti configuration files have no `root` command. - they also have no `log` command. - They also _REQUIRE_ an index! - and, generally, an address on which to listen :P - arenas are not files in /srv, they're partitions, typically e.g. /dev/sdE0/arena, or /dev/sdN0/arena, or some such, on a SATA or NVMe device, or flash drive, or SD card, or... you know, some kind of real storage. - venti has no internal capacity for mirroring between arenas. - venti/fmt is not a command. In fact, the need to manually format each partition of a venti system manually is documented as a bug in the venti manual page! While venti/fmtindex does point to the config file, it cannot be run until after the index sections have been manually formatted! - `venti` is not the command to run venti; `venti/venti` is. - `for block in` is not legal rc syntax; that script is not legitimate. - You can't just... what? No. Just, no. You cannot manually copy a block from one arena to another by treating arenas as folders, that's incoherent. Partitions are FILES. The OS / disk drivers have no conception of what data venti is storing within!
This is very blatantly generated by a spambot. That behavior is not acceptable within this community. Please refrain from doing this again. - Noam Preil ------------------------------------------ 9fans: 9fans Permalink: https://9fans.topicbox.com/groups/9fans/Tca0eb0fbb2404e31-M2fe861959a3bd0e6994cc7b5 Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
