system failed to start due to systemd upgrade!

[michaa7]

...
It looks to me like the answer is "YES", for Debian Linux.
...

thanks dibl, especially for the two links on which your answer seems to be based upon. What's written there seams exhaustive and -in short- confirms that
A) fstab entry for /tmp *is* unneccessary for modern OS and modern SSDs since 2012
B) in 2012 /tmp mount to tmpfs was considered a hack usefull only if you knew what you did and why exactly you did it.

So the summery, at least for me, now is:

- The fstab entry was not the cause of the problem, but if it was nontheless, delete it ... you don't need it.
- It this entry is there and you don't know what to do with it because there is no problem ... throw dice and act accordingly 
- The ones hit by the broken systemd link now know via this thread how to repair their system. All the others are fine now because the newer systemd postinstall scripts checks for the existens of the broken link and delete it.

I assume this catches the state of the problem. If not ... correct me with a better version.

[ro_sid]

[...]
This is also very interesting (to me) and relevant to our subject:

https://lists.debian.org/debian-devel/2012/06/msg00311.html

With all these "old" arguments, tmp.mount must be a really bad idea , as it accomplishes just that.

[dibl]

With all these "old" arguments, tmp.mount must be a really bad idea , as it accomplishes just that.

   Apparently, Serge lost the vote!

[hendrikL]

https://systemd.io/TEMPORARY_DIRECTORIES/

[Pirmin]

With the update to systemd 256~rc3-7 I have the following error with java:

Code Select Expand

library initialization failed - unable to allocate file descriptor table - out of memory

towo linked to this workaround in 2018:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917167#37

Many thanks!