-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On 2016-11-14 05:35, Unman wrote: > 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. >> > That message is thrown by the qube itself. It's a standard free space > check, not a Qubes thing. >
Oh, I know. But nonetheless, it's there, and it warns about low disk space in the qube. - -- Andrew David Wong (Axon) Community Manager, Qubes OS https://www.qubes-os.org -----BEGIN PGP SIGNATURE----- iQIcBAEBCgAGBQJYKcHqAAoJENtN07w5UDAwENQQAMyfS2lsoZyEK/4KaJTyk2jw 9VIWykb3RLJW7sJ0ACmOFge31zxJg3ll4RH6v7NjH4xHIgY0ZCUbh58L/GXZOgod RiXbCmiruA6c869Hdjpb9bua+y9Ey32SSKY5i+pVDoPysiyXK38ZNNfIas6FGMjl ccbWduZBwbUvyvxaqxGNrzKU4BE91D1veQfGDZeF1rPt4BhtScQisXnu58DW6UjF ufVfLZhvMniOhgK73+S8yu+C2oI2hDGd9+gWjg+PGGfVrCR+w4LAGHhUql1MBGkI 8sgGlpHKmMmtNi9R4ZOSdsk3/rdSSuAB+ydfYCOr7N1gX5Uh8yEs02UBFkdL2qFA Fvg65AQCnW1fqrmw1X3eIiglTo8hEoyI5ElE7X8LpMAK/vkIHpMZxY6NBr7rFNcm s8SjP/VF5117Mf5n2rTQ3roQ9PXQF15anbxxglOKJ4cFMae3+ssnKyhhtaO435pX jfFgx3pS8P7RAGeWiz6EIcLU9zd+NWSKPzgbKkAdRmKxPwwVqXfmEpt6ekeuVkpR TluFrdZ6rMc8a1R734HpV7cPPcfQPUcDny4Q41cuNT2l81IZsTbYlk9Gaye1xj7k SifDaFGfbtWRQToyOGfO4A9cV7hQXHa48dKefQ22oxtoc3s2S/CxeJIIOd6XBhIz /m7Z3sqyMQRF2MSU8Iub =0MvA -----END PGP SIGNATURE----- -- 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/070c8fa8-6043-3d1b-7896-d534c06263e7%40qubes-os.org. For more options, visit https://groups.google.com/d/optout.
