Version: 2.13.1-rc2, without any changes. It is not necessarily bug of util-linux itself. However, since there is no other well known tool to make arbitrary `mount' system call, and specify to it as many options as `mount' program from util-linux allows, this program is the only way to reproduce the failure. And even determining that it is something outside `mount' program is broken requires full- blown debugging of the program. File system may contain data not to let any logged in user read. Wish to specify more restrictive mode of files in it. This certainly must occur on mount itself, not in subsequent `chmod' calls. There is at least one obvious reason to avoid explicit `chmod', just as many other uses of it: possible race condition between it and other process opening the file. Seeing no way to have `mount' do that. When mounting read- only iso9660 file system, `mount' ignores `mode=400' file system option. More precisely, mount -nv -t iso9660 -o ro,norock,mode=400,uid=ID_OF_REGULAR_USER DEVICE DIR completes without error messages and leaves DIR mounted, but with mode `r-xr-xr-x'. DIR uid is as specified. - To unsubscribe from this list: send the line "unsubscribe util-linux-ng" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
