Comment 2 for bug 47145

Yea that would be nice as a short-term workaround. As a proper solution however, I would suggest:

1. Rewriting the GUI login process so that it does not write any additional data to the disk.

 OR

2. Making sure that the relevant files are stored separately; so that regardless of how many mp3s the user downloads or regardless of how big /var/log messages and other log files grow they will never interfer with system functionality.

Generally, I would prefer the second solution because I bet that there is a ton of other important programs that will crash and/or fail abruptly with zero bytes free. The login process if of course one of the most important programs... since most users can't use their computer at all when they can't login.