Yes, I complained to this effect to Nick explaining that despite my laptop having 3G of RAM, I couldn't create an UME VM because it was larger than 1.5 G -- this despite having the disk space.
I first guessed tmpfs had perf improvements, but Nick pointed me at this bug with the nodev, nosuid /tmp issue.
One option would be to claim that one of /tmp or the target fs need to be mounted without these flags and report a failure otherwise.
Another option might be to loop mount a file, but it requires guessing the filesystem size; you could use a sparse 8 GB ext3 and copy over to the target fs, but that wouldn't be elegant, or you could try to loop mount the target fs.
In all cases I think tmpfs is an interesting /option/ and proposed Nick to simply not make it the default.
Yes, I complained to this effect to Nick explaining that despite my laptop having 3G of RAM, I couldn't create an UME VM because it was larger than 1.5 G -- this despite having the disk space.
I first guessed tmpfs had perf improvements, but Nick pointed me at this bug with the nodev, nosuid /tmp issue.
One option would be to claim that one of /tmp or the target fs need to be mounted without these flags and report a failure otherwise.
Another option might be to loop mount a file, but it requires guessing the filesystem size; you could use a sparse 8 GB ext3 and copy over to the target fs, but that wouldn't be elegant, or you could try to loop mount the target fs.
In all cases I think tmpfs is an interesting /option/ and proposed Nick to simply not make it the default.