Package: e2fsprogs Version: 1.43~WIP.2016.03.15-2 Severity: wishlist File: /sbin/e2fsck
If in fstab one has lines like UUID=c4414db0-65ee-4b6b-bb78-f672474821e5 /mnt/usb/cf auto noauto,errors=remount-ro 0 0 UUID=0000-006F /mnt/usb/s1mp3 vfat iocharset=ascii,shortname=mixed,noauto,noatime,nodiratime,user,fmask=133,uid=jidanni,gid=jidanni 0 0 but such devices are not plugged in, one will get fsck.ext2: Unable to resolve 'UUID=c4414db0-65ee-4b6b-bb78-f672474821e5' fsck.fat 3.99.0 (2015-05-16) open: No such file or directory 1. One thinks "Hey, I spend a whole week researching how to make that an ext4 drive, and now you are calling it a ext2!", Same with vfat / fat. (Yes even though we haven't detected exactly which version of ext the user has on the disk, which might still be in his cupboard, not plugged in to the computer.) Yes, even though they are just links to the same program, wouldn't it be better to call them a more neutral name in the error message? 2. by the way, I later did mkdir /mnt/usb/s1mp3 but the message stayed the same. So at least it should admit there is a directory there, even if I didn't plug in a corresponding device. Ah maybe it is talking about trying to open UUID=0000-006F, well then the message should be updated to be the same as fsck."ext2"'s. I suppose I should clone this to dosfstools...
