Hacker News new | comments | ask | show | jobs | submit login

What I want from a network-based file system is some level of control over the caching. What I've found with FUSE-based file systems (on Linux) is that often they lock up my terminal. All it takes is a "cd" or an "ls" and suddenly I can't type anything until the network responds, which is not always instantaneous -- can't even Ctrl-C, because the program is blocked in the driver.

I want to be able to tell when a command is going to block, or respond immediately with an error so that I can re-issue the command in a deferred manner. Having the command line lock-up because of filesystem latency is a bad user experience.




Elsewhere in the thread it's mentioned that it won't lock up directory traversal. Of course when catting a file it would, it'd be hard to get around that...




Applications are open for YC Summer 2019

Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact

Search: