Re: Debian system modifications tmpfs
On Fri, Sep 24, 2010 at 11:34 AM, Timo Juhani Lindfors
<timo.lindfors@iki.fi> wrote:
> Peter Smith <peter.smith3882100@gmail.com> writes:
>> tmpfs /tmp tmpfs noatime,nodev,noexec,nosuid,mode=1777 0 0
>
> noexec /tmp will surely break applications, no?
So far no applications have been malfunction as a result of the noexec
flag on /tmp, but i guess that i could change it to exec just to be
sure that problems do not suddenly arise.
>> Iceweasel is modified to use /tmp as cache, so when Iceweasel is
>> loaded after a reboot it creates a folder named Cache in /tmp.
>
> How does this work with multiple users in a safe way?
Good point, but in my case it won't be a problem as i am the only user
of the system. What if a security problem was found in Iceweasel,
would it be worse that the cache is placed in /tmp instead of the home
folder?
Today when reading the "Filesystem Hierarchy Standard" i found out
that mounting /var/tmp as tmpfs is not a good idea:
"The /var/tmp directory is made available for programs that require
temporary files or directories that are preserved between system
reboots. Therefore, data stored in /var/tmp is more persistent than
data in /tmp.
Files and directories located in /var/tmp must not be deleted when the
system is booted. Although data stored in /var/tmp is typically
deleted in a site-specific manner, it is recommended that deletions
occur at a less frequent interval than /tmp."
Until now i have not found any information that talks against mounting
/var/cache/apt/archives as tmpfs
Reply to: