installer creates /tmp/ as HAMMER pfs instead of tmpfs
Shouldn't we default to having /tmp/ as tmpfs instead of HAMMER?
Updated by alexh over 2 years ago
On 07/01/11 08:34, Peter Avalos (via DragonFly issue tracker) wrote:
> New submission from Peter Avalos <firstname.lastname@example.org>:
> Shouldn't we default to having /tmp/ as tmpfs instead of HAMMER?
I don't think that's a good idea. If someone wants their /tmp as tmpfs,
then they can do so easily enough by changing the fstab entry.
The main reason against this is, imo, that tmpfs is a memory file
system and can hence be problematic on machines with limited RAM and/or
large files in the /tmp directory.
Updated by ftigeot over 1 year ago
- Status changed from New to Feedback
- Assignee deleted (
Wouldn't that be a non-issue if the installer configures the machine with enough swap ?
Updated by pavalos over 1 year ago
I think for new installations we should default to tmpfs, but maybe add some logic in there that detects low RAM/swap situations. This could be similar to the way we handle HAMMER installs. We don't want people to install a HAMMER fs if their disk is too small, which is comparable to the issue of having too little memory for tmpfs.