SSD stuck in UMDA5 mode, Timing cached reads equal to normal hard drives

[bonkers]

You don't need anything in fstab. /run is dyamically created and mounted by the system when it boots. You can see this in the ouput of cat /proc/mounts in your post #11 here -- look at line 6. You also don't need to make any changes to /etc/sysctl.conf.

First, just create a subdirectory in the correct place under /run. I'll call this subdirectory ffcache here:

mkdir /run/user/1000/ffcache

Then, create the new string value and set its value to the directory you just created. Following the example, that will be /run/user/1000/ffcache.


http://www.linux.com/learn/tutorials...le-permissions

This is the problem, I am the ONLY user of this box, yet others has r-x permissions set to it and I can't turn them off, should I worry? Thank you for the FF explanation.

[dibl]

There is a bit more detail about SSD setups in the article on the siduction blog here, along with references. I use both firefox and chromium so I make the cache directories at /run/user/1000 automatically at each KDE login with the script I posted earlier. I guess Steve is saying that firefox will remember and recreate its cache there automatically after the first setup, so that's good to know too.

[SteveRiley]

This is the problem, I am the ONLY user of this box, yet others has r-x permissions set to it and I can't turn them off, should I worry? Thank you for the FF explanation.

It's mostly a historical artifact on Unix (and Linux) that some new directories are set with mode 775 (rwxrwxr-x) and files are set with mode 664 (rw-rw-r--), while other directories are set with mode 755 (rwxr-xr-x) and other files are set with mode 644 (rw-r--r--). In Debian and its derivatives, the convention is to create user-private groups: each user is placed into his/her own group, where the group name is the same as the user. The default umask is 002, and the default modes are 775/664. Most other Linux distros put all users into a "users" group, configure the default umask at 022, and the default modes to 755/644. However, Ubuntu makes certain exceptions to what I wrote previously, and some directories/files are set to 775/664 to make it easier do file sharing (this change happened in late 2010).

I honestly don't know why the default for the world bit isn't 0. I tried Googling around for some explanation of this and didn't find anything. Nevertheless, the various scripts that manage the system (and well known best practices for hardening things like web servers) do make changes to certain files and apply more restrictive mode bits.