The Journal - a proposed syslog replacement

I don't understand why there are no way to allow {,u}mount only if answer to private key challenge is known. Block device layer could be modified the way that only file read, create and append are passed to file system. Additionally allowing rename might be sane, but not across file system. Basically that would make block device to be something in between traditional read-write & read-only.

This might enable extra security with existing file systems and utilities, and would perhaps be suitable ftp file archive. Logs are more difficult, they are often compressed which does not work without being able to delete uncompressed file. I guess to overcome this choosing a file system that supports transparent compression is the way to go.

The Journal proposal sounds interesting. I understand the proposal breaks old ways of working, and I am not worried about that; sometimes old bad habits has to go to give room for new generation of solution. That is in align with Hume's (is-ought) Law. More importantly it is easy to defend what is, and tell old must not break, without really contributing how thing ought to be. If it is unclear I am aside of study how things ought to be, including intuitively wrong and crazy ideas. People who abandon alternatives without careful thinking are not thinking, and therefore their opinion is less important.

p.s. For people who do not read old philosophers; the Hume's Law can be expressed many ways, and here is two 'you cannot determining how things ought to be from how they are', or 'how things are is not necessarily how they ought to be'.