The saga continues –
- When I removed the “fuse-exfat
” package, I noticed the following message – here the ‘/var/log/zypp/history’ content –
# 2021-12-29 10:07:10 fuse-exfat-1.2.8-bp153.1.17.x86_64 removed ok
# Additional rpm output:
# Deleted 'exfat' and 'exfat_fuse' from the file /etc/filesystems
#
I then forcibly re-installed the package which provides ‘/etc/filesystems’ – “util-linux” – no mention of “exfat” in ‘/etc/filesystems’ …
Next, examine the “fuse-exfat” package –
> rpm --query --scripts --package fuse-exfat-1.2.8-bp153.1.17.x86_64.rpm
postinstall scriptlet (using /bin/sh):
if ! grep -q -e '^exfat$' /etc/filesystems ; then
sed -i 's/*/exfat
*/g' /etc/filesystems
echo "Added 'exfat' to the file /etc/filesystems"
fi
if ! grep -q exfat_fuse /etc/filesystems ; then
sed -i 's/*/exfat_fuse
*/g' /etc/filesystems
echo "Added 'exfat_fuse' to the file /etc/filesystems"
fi
postuninstall scriptlet (using /bin/sh):
if "$1" == "0" ]; then
sed -i -e '/exfat_fuse/d' -e '/^exfat$/d' /etc/filesystems
echo "Deleted 'exfat' and 'exfat_fuse' from the file /etc/filesystems"
fi
>
Digging around, it seems that “mount” uses ‘/etc/filesystems’ – here the man page –
-t, --types fstype
[INDENT=2]The argument following the -t is used to indicate the filesystem type. The filesystem types which are currently supported depend on the running kernel. See /proc/filesystems and /lib/modules/$(uname -r)/kernel/fs for a complete list of the filesystems. The most common are ext2, ext3, ext4, xfs, btrfs, vfat, sysfs, proc, nfs and cifs.
[/INDENT]
[INDENT=2]The programs mount and umount support filesystem subtypes. The subtype is defined by a '.subtype' suffix. For example 'fuse.sshfs'. It's recommended to use subtype notation rather than add any prefix to the mount source (for example 'sshfs#example.com' is deprecated).
[/INDENT]
[INDENT=2]If no -t option is given, or if the auto type is specified, mount will try to guess the desired type. Mount uses the blkid library for guessing the filesystem type; if that does not turn up anything that looks familiar, mount will try to read the file /etc/filesystems, or, if that does not exist, /proc/filesystems. All of the filesystem types listed there will be tried, except for those that are labeled "nodev" (e.g. devpts, proc and nfs). If /etc/filesystems ends in a line with a single *, mount will read /proc/filesystems afterwards. While trying, all filesystem types will be mounted with the mount option silent.
[/INDENT]
For whatever reason, ‘/proc/filesystems’ isn’t indicating “exfat” – only “vfat” and “fuseblk” – ‘/lib/modules/$(uname -r)/kernel/fs/’ does have an “exfat” directory …
[HR][/HR]For now, I’ve added “exfat” to ‘/etc/filesystems’ on the line following “vfat”, which seems to work OK but, I need to remember that, a patch or update may well cause the entry to disappear …
