/tmp is always a dir of /, you need to have a mount point to mount the
filesystem.
--
Temporary /tmp and /var/tmp
https://bugs.launchpad.net/bugs/18661
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bu
/tmp was a subdir of / in Karmic on my systems.
--
Temporary /tmp and /var/tmp
https://bugs.launchpad.net/bugs/18661
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.u
As I see in Lucid Lynx current, /tmp is now just a subdir of /.
In Karmic /tmp was actually tmpfs mount, was this an intended change in Lucid?
--
Temporary /tmp and /var/tmp
https://bugs.launchpad.net/bugs/18661
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Hrm... I could have SWORN that /tmp was already mounted as a tmpfs, but
it appears it's just /var/run and /var/lock that are. /tmp only gets
mounted as a tmpfs by /etc/init.d/mountoverflowtmp if there is less than
1 meg of free space on /.
--
Temporary /tmp and /var/tmp
https://bugs.launchpad.ne
per discussion, its been decided that only /tmp should be mounted to
tmpfs. /var/tmp should not be, since the data should persist beyond
reboots. /tmp on the other hand, can be deleted on boot, since programs
shouldn't expect files in /tmp to persist beyond the life of the
program's process.
**
@Philip
This bug (or feature request) is having /tmp and /var/tmp in ram instead of
disk. This has never been the default (or an installation option).
** Changed in: debian-installer (Ubuntu)
Status: Invalid => New
--
Temporary /tmp and /var/tmp
https://bugs.launchpad.net/bugs/18661
You
This is already done by default, and has been at least as far back as
breezy AFAIK, so marking as invalid.
** Changed in: debian-installer (Ubuntu)
Status: Triaged => Invalid
--
Temporary /tmp and /var/tmp
https://bugs.launchpad.net/bugs/18661
You received this bug notification because y
** Changed in: debian-installer (Ubuntu)
Status: New => Triaged
--
Temporary /tmp and /var/tmp
https://bugs.launchpad.net/bugs/18661
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubu
> OK, so I go to edit /etc/fstab. Whoops. It is read-only too! OK,
> so I go to unmount / and mount rw. Except... yes, / cannot be
> unmounted because it is busy! OK, so I go to use a livecd to
> edit fstab to remove this fscking ro thing
A quick tip for you, since this bit you: you don't want
I actually ran into a situation where a ramfs /tmp would have been an
absolute life-saver. As it was, my experience was very unpleasant until
I managed to wipe and reinstall Ubuntu.
---
So I went and installed 8.04 on my desktop. It was fairly difficult as I
was using a CD-ROM drive which is anci
So, basically if the Nautilus temporary directory can be set manually -
using tmpfs for /tmp (but not /var/tmp) is a reasonable setup for most
desktops?
Sounds especially important for laptops - where frequent disk access
significantly reduces battery and hard drive strain.
--
Temporary /tmp and
I don't think tmpfs is appropriate for /var/tmp. Having it disappear
after reboot violates the FHS, and along with it, many admins'
expectations.
/var/tmp : Temporary files preserved between system reboots
Purpose
The /var/tmp directory is made available for programs that require
temporary files
Having sensitive data in swap is no better than having it on a normal
partition. If you employ encryption, you can do it the same way for both
swap and regular file systems (you could even use random keys for /tmp
and create the filesystem on boot), so nothing's gained (w.r.t.
confidentiality) by u
I believe that you may find other issues. You can fill up / this way
too; I use a several gigabyte / and a separarte /home, because I
reinstall ubuntu a lot (due to me breaking it with hackery) and it does
NOT SUPPORT WIPING SYSTEM DIRECTORIES BUT LEAVING /home ALONE. (we can
ignore running 32/64
I'm running ALL of my systems successfully with a tmpfs as /tmp. Applications
that need loads of space usually can be configured to use a different directory
(on my system /cdtemp, which is a separate LV so it won't disturb anything
else).
Systems with a "real", but small /tmp (like all my syste
This is not a problem just with burning DVDs. I assume that writing 10
mp3s as an audio disc would also be problematic. IMVHO, it's unwise to
expect people to have that much RAM for tmpfs.
The issue you describe with nautilus is well known. Temporary file
handling in Gnome isn't ideal and affects
16 matches
Mail list logo
