How to avoid creating tmp-files on linux?

@johann 

There are several ways to avoid creating temporary files on Linux:

1. Use the /tmp directory: By default, most Linux systems provide a /tmp directory for temporary file storage. It is meant to be used for short-term storage and can be cleaned out periodically. To avoid creating files in other directories, use the /tmp directory explicitly for temporary file operations.
2. Utilize RAM-based temporary file systems: Linux provides the ability to create and use RAM-based file systems, such as tmpfs. These file systems are stored in memory and do not require writing to disk, offering faster access and eliminating the need for physical temporary files. You can create a tmpfs mountpoint and use it for temporary file storage.
3. Utilize a RAM disk: Similar to tmpfs, a RAM disk is a portion of your system memory that is used as a disk drive. By creating a RAM disk and mapping it to a directory, you can avoid writing temporary files to disk and achieve faster access times.
4. Use volatile storage: If your Linux system supports it, you can designate a portion of your system's main memory as volatile storage specifically for temporary file operations. This directly allocates memory to temporary file storage and ensures that no disk writes occur.
5. Modify application configurations: Some applications allow configuration changes to control the location or creation of temporary files. By modifying application settings, you can redirect temporary file creation to the /tmp directory or use other RAM-based options.
6. Disable unnecessary services: Certain services or applications may create their temporary files in specific directories. If these services are not needed or can be disabled, you can prevent the creation of temporary files altogether.

Remember that preventing the creation of temporary files completely may not always be practical or desirable, as many applications rely on temporary file operations for proper functioning. It is essential to consider the implications and requirements of your specific use case before implementing any changes.