On Mon, Nov 14, 2016 at 04:16:37AM -0800, Andrew David Wong wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA512 > > On 2016-11-14 04:03, Salmiakki wrote: > > On Monday, November 14, 2016 at 10:31:25 AM UTC+1, Robert Mittendorf wrote: > >> On 2016-11-11 14:58, Marek Marczykowski-Górecki wrote: > >>> > >>>>> Actually I don't think it is a good idea. File copy protocol is > >>>>> intentionally very simple, including being unidirectional. We don't > >>> want > >>>>> to add any non-essential features there, to keep it as simple as > >>>>> possible. > >>> > >>>> BTW None of file copying tools I know do that (cp, rsync, scp, ...). > >> Well, I somewhat understand the first argument, but not the second. To > >> have a bad usability and waste poeple's time just because other tools do > >> is not a good argument I think. > >> > >> Obviously it is not unidirectional, otherwise the source would not know > >> "out of disk space". This does not have to be an interactive feature, > >> though. > >> Why not give the "out of disk space" error before accepting the > >> transfer? The communication from sink to source would be the same, but > >> less time would be wasted. > > > > Maybe it could be done more general by just popping up a warning saying > > "this VM is low on disk space". > > It would not work for cases where you transfer extremely large files (or at > > least it would only display the warning after transferring quite a large > > chunk). > > However, it would also work for everything else! > > For example I once had a problem because I decided to sync my entire imap > > folder for my mail VM and that is larger than 2 GB. The problem was > > actually kind of hard to spot. Ideally of course, the warning would be > > accompanied by an option to just extend the space (since it seems to be > > possible to do that while the VM is running anyway). > > > > I've actually seen such a warning in 3.1 and earlier (haven't had cause to > see it yet in 3.2), so it must already exist in some sense (or did exist). I > never bothered to look into how the threshold is calculated, though. > > - -- > Andrew David Wong (Axon) > Community Manager, Qubes OS > https://www.qubes-os.org
That message is thrown by the qube itself. It's a standard free space check, not a Qubes thing. On the question of "bad usability" it looks like horses for courses. I personally don't want a warning if I've already started to clear out space on the target. And if I'm transferring files as they are being written, what use would the measure of free disk space be? It isn't the TOOL here that will "waste people's time". They waste their own time by not checking beforehand. There are some OS and tools that try to fix this, but you see plenty of users baffled by the way they work, and unsure why the warning arise. Best to keep it simple imo. unman -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/20161114133538.GA9627%40thirdeyesecurity.org. For more options, visit https://groups.google.com/d/optout.
