Am 01.06.2012 20:14, schrieb Simo Sorce:
On Fri, 2012-06-01 at 12:58 -0500, Chris Adams wrote:
> Once upon a time, Simo Sorce <simo(a)redhat.com> said:
>> On Fri, 2012-06-01 at 11:02 -0500, Chris Adams wrote:
>>> Once upon a time, Reindl Harald <h.reindl(a)thelounge.net> said:
>>>> thank you for breaking setups of well thought virtual machines
>>>> on expensive SAN storages with a as small as possible rootfs
>>>> with a own virtual disk for /tmp with new defaults
>>> If you are mounting a filesystem on /tmp, it'll be in /etc/fstab and
>>> still work exactly as before (if not, that's a bug and should be treated
>>> as such).
>> Chris, the problem is that now you have to add a /tmp filesystem,
>> before /tmp was just a normal directory in root.
> Did you read what I was replying to? My understanding of it was about
> already using a separate /tmp filesystem.
I read it but I have misunderstood. I would hope people that already
have /tmp in fstab see no changes.
but they do and this is was Chris Adams do not understand because he only
reads what he has quoted and not what was the reason for my reply which
gives "Did you read what I was replying to" a special taste
patching applications for "/var/tmp rather than /tmp" is a real problem
for people which are smart enough to know why they introduced a seperated
disk for /tmp
this changes means that the crap no longer goes to /tmp and will hit in
the future rootfs because switch to /var/tmp
HERE AGAIN THE FULL QUTOE TO GET BACK CONTEXT!
> So I'll patch sort to default to /var/tmp rather than /tmp
thank you for breaking setups of well thought virtual machines
on expensive SAN storages with a as small as possible rootfs
with a own virtual disk for /tmp with new defaults