At any rate, for those who actually want to use the capabilities of their OS and protect their SSD, I have posted a method here which works around this bug in mountall to some extent. http://ubuntuforums.org/showpost.php?p=8232599&postcount=11
I guess in these days of Microsoft's... excuse me, CANONICAL's higher level devs being hostile to its users, this is kind of thing we have to work with. That mounts /var/tmp in rc.local, a little later than fstab, but still before KDE and Gnome are started. (All of the data in my /var/tmp belongs to KDE.) /var/log is more of a problem because the system logs are opened in it before rc.local is run (even in runlevel 0). The best I think that can be done until this mountall bug is actually addressed (as in something actually being DONE on it and an explanation of why it suddenly broke between karmic alpha3 and final) is to have rc.local create symlinks in /var/log for some of the log folders. That won't protect the SSD from the system logs writes, though. Also, eventually I'll post a more polished version of that SSD script here... http://igurublog.wordpress.com/ -- separate /var and /var/tmp tmpfs dependency loop https://bugs.launchpad.net/bugs/431040 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
