When I try to download an ISO file from linuxiso.org using mozilla-firefox, I run out of space on the /tmp partition. It's my understanding that Arch maps /tmp to the swap partition, which after taking the Arch default duriing install, is about half the size of my RAM = 256M.
Is there a way to re-direct /tmp to another partition (like from within fstab), or increase the size of my swap file? I'm afraid my PC wont boot if I guess wrong on the swap file configuration.
Use /var/tmp, as I do, or read this post: http://bbs.archlinux.org/viewtopic.php? … =space+tmp.
If ou really want /tmp to be big, you could always not mount /dev/shm in /tmp .
Or download the iso with wget.
I have discovered that all of mans unhappiness derives from only one source, not being able to sit quietly in a room
- Blaise Pascal
How would I go about using /var/tmp? I'm a newby, is that just changing an entry in the /etc/fstab file? If so, change it to what? VMWare is also complaining I don't have enough /tmp space, so I need to figure out something. I have 512MB, a 80GB boot drive, and 2 x160GB data drives.
ree showed me how to fix this, I just put a # in front of the "tempfs" line in my /etc/fstab file. Now I dont run out of /tmp space anymore.
I had this problem also, I found that Moz is broken, as a FTP client. Use the HTTP repos or use a "real" FTP client
Big Al in Seattle
Very N00b Friendly Group of people
You can raise the size limit in /etc/fstab:
tmpfs /tmp tmpfs size=2G,nr_inodes=10k 0 0
Then remount it:
# mount -o remount /tmp
Be careful with the size, though. Since it exists in RAM, you don't want a tmpfs partition to be bigger than your RAM, otherwise the big bad OOM killer will come along and start assassinating your processes.
i found this a problem also when i first started using arch.
but i don't blame arch as it sounds like something linux users of all kinds wanted and it was created using part of your valuable ram . I never liked that idea from the start so i fixed it by doing the following:
i usually make a large partition to do dirty work like things that change alot. the /var directory sounded like the a perfect place to store temporary files like /tmp and doing kernel rebuilds.
take the /var/tmp directory and symbolic link it to / (root) as /tmp. i also put the /usr/src directory into /var and linked it back to /usr. that is where i do software builds along of cource kernel builds.
i also believe that the /usr and / partition don't get fragmented as much this way.
take that silly tmpfs thing out of fstab.
i know this isn't kosher to the linux folks and there directory laws, but that is why i use linux.
freedom of choice .
Joey: If a cow passes away from natural causes can I eat it.
Pheobe: Not if I get there first.
Actually I almost never don't care what is in my RAM as far as non usable pages are swapped to disk so they can be there even forever. The nice feature of tmpfs is that /tmp after reboot will be cleaned up without doing any magical hacks like rm :-)
Lenovo ThinkPad X1 Carbon 3 20BS006DPB - Core i7 5500U / 14,1 WQHD / 8192 RAM / 512 SSD SATA PCIe / Intel HD 5500
Lenovo ThinkPad T400, model 647314G / Core2 Duo CPU P8700@ 2.53GHz / 8 GB DDR RAM / 223,6 GiB HDD SSD OCZ-AGILITY3 / Intel GM45 Chipset
11 years, is that a record?
Mods are just community members who have the occasionally necessary option to move threads around and edit posts. -- Trilby
11 years, is that a record?
Seem like it.
Kitarek, please let dead topics rest in peace.
Mobo: ASUS P8Z77-V PRO // Processor: Intel Core i7-3770K 3.4GHz // GFX: nVidia GeForce GTX 970 Ti // RAM: 32GB (4x 8GB) Corsair DDR3 (@ 2133MHz) // Storage: 1x 3TB Seagate SATAII 5x 1TB Samsung SATAII, 2x 120GB Corsair SSD