This man page was created for libblkid.so.1.0 from e2fsprogs-1.24.
This file may be copied under the terms of the GNU Public License.
Created Wed Sep 14 12:02:12 2001, Andreas Dilger
Block device information is normally kept in a cache file /etc/blkid.tab and is verified to still be valid before being returned to the user (if the user has read permission on the raw block device, otherwise not). The cache file also allows unprivileged users (normally anyone other than root, or those not in the "disk" group) to locate devices by label/id. The standard location of the cache file can be overridden by the environment variable BLKID_FILE.
In situations where one is getting information about a single known device, it does not impact performance whether the cache is used or not (unless you are not able to read the block device directly). If you are dealing with multiple devices use of the cache is highly recommended (even if empty) as devices will be scanned at most one time, and the on-disk cache will be updated if possible. There is rarely a reason not to use the cache.
In some cases (modular kernels), block devices are not even visible until after they are accessed the first time, so it is critical that there is some way to locate these devices without enumerating only visible devices, so the use of the cache file is required in this situation.
/etc/blkid.tab Caches data extracted from each recognized block device.
Free Software Foundation, Inc.
59 Temple Place
Suite 330
Boston, MA 02111-1307 USA
or visit R http://www.gnu.org/licenses/licenses.html#LGPL http://www.gnu.org/licenses/licenses.html#LGPL E