| 2016-01-13 11:58:41 |
Dustin Kirkland |
bug |
|
|
added bug |
| 2016-01-13 11:58:47 |
Dustin Kirkland |
livecd-rootfs (Ubuntu): status |
New |
Triaged |
|
| 2016-01-13 11:58:49 |
Dustin Kirkland |
livecd-rootfs (Ubuntu): importance |
Undecided |
High |
|
| 2016-01-13 11:58:57 |
Dustin Kirkland |
livecd-rootfs (Ubuntu): assignee |
|
Ben Howard (utlemming) |
|
| 2016-01-13 12:20:31 |
Ben Howard |
bug |
|
|
added subscriber Ubuntu Server Team |
| 2016-01-13 12:20:41 |
Ben Howard |
bug |
|
|
added subscriber James Page |
| 2016-01-13 12:46:02 |
Robie Basak |
bug |
|
|
added subscriber Robie Basak |
| 2016-01-13 15:20:10 |
Ryan Harper |
bug |
|
|
added subscriber Ryan Harper |
| 2016-01-13 23:00:07 |
Nobuto Murata |
bug |
|
|
added subscriber Nobuto Murata |
| 2016-01-13 23:07:53 |
Moshe Katz |
bug |
|
|
added subscriber Moshe Katz |
| 2016-01-14 10:30:09 |
Dustin Kirkland |
description |
In Ubuntu, we clear /tmp on every boot.
As such, on servers, by default /tmp should actually be a tmpfs entirely in RAM.
This has several advantages, mainly:
* Performance - much faster read/write access to data in /tmp
* Security - sensitive data would be cleared from memory on boot, rather than written (leaked) to disk -- important for encryption scenarios |
In Ubuntu, we clear /tmp on every boot.
As such, on servers, by default /tmp should actually be a tmpfs entirely in RAM.
This has several advantages, mainly:
* Performance - much faster read/write access to data in /tmp
* Security - sensitive data would be cleared from memory on boot, rather than written (leaked) to disk -- important for encryption scenarios
* Power consumption - storing information in memory is more energy efficient than reading and writing to disk |
|
| 2016-01-14 10:31:45 |
Dustin Kirkland |
description |
In Ubuntu, we clear /tmp on every boot.
As such, on servers, by default /tmp should actually be a tmpfs entirely in RAM.
This has several advantages, mainly:
* Performance - much faster read/write access to data in /tmp
* Security - sensitive data would be cleared from memory on boot, rather than written (leaked) to disk -- important for encryption scenarios
* Power consumption - storing information in memory is more energy efficient than reading and writing to disk |
In Ubuntu, we clear /tmp on every boot.
As such, on servers, by default /tmp should actually be a tmpfs entirely in RAM.
This has several advantages, mainly:
* Performance - much faster read/write access to data in /tmp
* Security - sensitive data would be cleared from memory on boot, rather than written (leaked) to disk -- important for encryption scenarios
* Power consumption - storing information in memory is more energy efficient than reading and writing to disk
In scenarios where more space in /tmp is needed than available, one can compliment that tmpfs with 'sudo apt-get install swapspace' which will dynamically create/delete swapfile as necessary. |
|
| 2016-01-14 11:12:14 |
Dustin Kirkland |
description |
In Ubuntu, we clear /tmp on every boot.
As such, on servers, by default /tmp should actually be a tmpfs entirely in RAM.
This has several advantages, mainly:
* Performance - much faster read/write access to data in /tmp
* Security - sensitive data would be cleared from memory on boot, rather than written (leaked) to disk -- important for encryption scenarios
* Power consumption - storing information in memory is more energy efficient than reading and writing to disk
In scenarios where more space in /tmp is needed than available, one can compliment that tmpfs with 'sudo apt-get install swapspace' which will dynamically create/delete swapfile as necessary. |
In Ubuntu, we clear /tmp on every boot.
As such, on servers, by default /tmp should actually be a tmpfs entirely in RAM, when there is enough memory in the system. This threshold should be configurable by the end user (in cloud-init?), and default threshold of ~2GB.
This has several advantages, mainly:
* Performance - much faster read/write access to data in /tmp
* Security - sensitive data would be cleared from memory on boot, rather than written (leaked) to disk -- important for encryption scenarios
* Power consumption - storing information in memory is more energy efficient than reading and writing to disk
In scenarios where more space in /tmp is needed than available, one can compliment that tmpfs with 'sudo apt-get install swapspace' which will dynamically create/delete swapfile as necessary. |
|
| 2016-01-14 11:19:55 |
Dustin Kirkland |
description |
In Ubuntu, we clear /tmp on every boot.
As such, on servers, by default /tmp should actually be a tmpfs entirely in RAM, when there is enough memory in the system. This threshold should be configurable by the end user (in cloud-init?), and default threshold of ~2GB.
This has several advantages, mainly:
* Performance - much faster read/write access to data in /tmp
* Security - sensitive data would be cleared from memory on boot, rather than written (leaked) to disk -- important for encryption scenarios
* Power consumption - storing information in memory is more energy efficient than reading and writing to disk
In scenarios where more space in /tmp is needed than available, one can compliment that tmpfs with 'sudo apt-get install swapspace' which will dynamically create/delete swapfile as necessary. |
In Ubuntu, we have always cleared /tmp on every boot.
As such, on servers, by default /tmp should actually be a tmpfs entirely in RAM, when there is enough memory in the system. This threshold should be configurable by the end user (in cloud-init?), and default threshold of ~2GB.
Read about tmpfs here: https://www.kernel.org/doc/Documentation/filesystems/tmpfs.txt
This has several advantages, mainly:
* Performance - much faster read/write access to data in /tmp
* Security - sensitive data would be cleared from memory on boot, rather than written (leaked) to disk -- important for encryption scenarios
* Power consumption - storing information in memory is more energy efficient than reading and writing to disk
In scenarios where more space in /tmp is needed than available, one can compliment that tmpfs with 'sudo apt-get install swapspace' which will dynamically create/delete swapfile as necessary. |
|
| 2016-01-14 13:49:13 |
Dustin Kirkland |
description |
In Ubuntu, we have always cleared /tmp on every boot.
As such, on servers, by default /tmp should actually be a tmpfs entirely in RAM, when there is enough memory in the system. This threshold should be configurable by the end user (in cloud-init?), and default threshold of ~2GB.
Read about tmpfs here: https://www.kernel.org/doc/Documentation/filesystems/tmpfs.txt
This has several advantages, mainly:
* Performance - much faster read/write access to data in /tmp
* Security - sensitive data would be cleared from memory on boot, rather than written (leaked) to disk -- important for encryption scenarios
* Power consumption - storing information in memory is more energy efficient than reading and writing to disk
In scenarios where more space in /tmp is needed than available, one can compliment that tmpfs with 'sudo apt-get install swapspace' which will dynamically create/delete swapfile as necessary. |
In Ubuntu, we have always cleared /tmp on every boot.
As such, on servers, by default /tmp should actually be a tmpfs entirely in RAM, when there is enough memory in the system. This threshold should be configurable by the end user (in cloud-init?), and default threshold of ~2GB.
Read about tmpfs here: https://www.kernel.org/doc/Documentation/filesystems/tmpfs.txt
This has several advantages, mainly:
* Performance - much faster read/write access to data in /tmp
- especially if your disk is spinning media
- and if you're on SSD, this feature extends the life of your flash by reducing your NAND flash writes
* Security - sensitive data would be cleared from memory on boot, rather than written (leaked) to disk -- important for encryption scenarios
* Power consumption - storing information in memory is more energy efficient than reading and writing to disk
In scenarios where more space in /tmp is needed than available, one can compliment that tmpfs with 'sudo apt-get install swapspace' which will dynamically create/delete swapfile as necessary. See: http://manpg.es/swapspace |
|
| 2016-01-14 14:04:38 |
Dustin Kirkland |
description |
In Ubuntu, we have always cleared /tmp on every boot.
As such, on servers, by default /tmp should actually be a tmpfs entirely in RAM, when there is enough memory in the system. This threshold should be configurable by the end user (in cloud-init?), and default threshold of ~2GB.
Read about tmpfs here: https://www.kernel.org/doc/Documentation/filesystems/tmpfs.txt
This has several advantages, mainly:
* Performance - much faster read/write access to data in /tmp
- especially if your disk is spinning media
- and if you're on SSD, this feature extends the life of your flash by reducing your NAND flash writes
* Security - sensitive data would be cleared from memory on boot, rather than written (leaked) to disk -- important for encryption scenarios
* Power consumption - storing information in memory is more energy efficient than reading and writing to disk
In scenarios where more space in /tmp is needed than available, one can compliment that tmpfs with 'sudo apt-get install swapspace' which will dynamically create/delete swapfile as necessary. See: http://manpg.es/swapspace |
In Ubuntu, we have always cleared /tmp on every boot.
As such, on servers, by default /tmp should actually be a tmpfs entirely in RAM, when there is enough memory in the system. This threshold should be configurable by the end user (in cloud-init?), and default threshold of ~3GB.
Read about tmpfs here: https://www.kernel.org/doc/Documentation/filesystems/tmpfs.txt
This has several advantages, mainly:
* Performance - much faster read/write access to data in /tmp
- especially if your disk is spinning media
- and if you're on SSD, this feature extends the life of your flash by reducing your NAND flash writes
* Security - sensitive data would be cleared from memory on boot, rather than written (leaked) to disk -- important for encryption scenarios
* Power consumption - storing information in memory is more energy efficient than reading and writing to disk
In scenarios where more space in /tmp is needed than available, one can compliment that tmpfs with 'sudo apt-get install swapspace' which will dynamically create/delete swapfile as necessary. See: http://manpg.es/swapspace |
|
| 2016-01-15 00:02:36 |
Andrea Corbellini |
bug |
|
|
added subscriber Andrea Corbellini |
| 2016-01-20 10:23:11 |
Haw Loeung |
bug |
|
|
added subscriber Haw Loeung |
| 2016-01-21 17:37:59 |
Jarno Suni |
bug |
|
|
added subscriber Jarno Suni |
| 2016-02-01 19:03:49 |
Ben Howard |
livecd-rootfs (Ubuntu): status |
Triaged |
Won't Fix |
|
